Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Mac OS 10.5.7 is here people!

Kommentare

9 Kommentare

  • Brian Eaves
    The new Mac OS X.5.7 DOES fix the the memory Leak caused by Apples Image Capture extension.
    Installed it on (Test Mule) 2009 White MacBook 6 Gig of Ram. Shot Tethered with my Canon 1Ds MK III via USB2 Cable, using Canon's EOS Utility !!!
    To confirm the fix, have the activity monitor open.
    You will notice that the Image Capture Ext doesn't eat up ram as the files come in. Software doesn't lockup
    The USB 2 Shooting speed is faster that Mac OS X.5.5 and under.

    Next I'll test it with Capture 4.8 and report findings when I have time.

    I assume this also fixes the Nikon tether USB2 problem as well.
    I don't own a Nikon camera, thus I CAN NOT confirm it fixes their problem with 10.5.6

    Cheers


    Brian Eaves
    Digital Tech
    Chicago, IL
    0
  • Brian Eaves
    Capture 4.8 does work tethered USB2 W/ my Canon 1Ds MK III with Mac OS X.5.7 !!
    Apple fixed appears to have fixed the memory leak.
    I've shot 500+ files , still shoots fast and no crashes.

    Now on to testing 10.5.7 with all of the other applications that make money for my business. (Photoshop CS 4, Chronsync, Better finder rename, Image Print, etc)

    Brian
    0
  • Permanently deleted user
    I'm a bit confused as to where I should be looking in Activity monitor. If I watch the free memory in system memory it keeps getting smaller as I do shots. I thought that was the memory that gets used up. The preview seems faster in 4.8 with 10.5.7 on my Macbook Pro Canon 5D Marl II. I had gone the route of installing Windows and running C1Pro Windows but really hate the way that OS works. Is it safe to assume that the lockup issue is resolved?
    0
  • Bert2
    Dear,

    Since the update to 10.5.7 I haven't been able to work with 4.8
    It became very unstable, a crop of 99991 single picture causes a message: Application out of memory Please restart
    After that it crashes. I already deleted pref files and restarted Mac several times but no luck.
    On my MacBook Pro with 10.5.6 and C14.8 I don't have these problems.

    Please Phase One get us a solution asap.

    Kind greetings,

    Bert Balcaen
    0
  • Mikkel Selsøe
    [quote="Bert2" wrote:
    Dear,

    Since the update to 10.5.7 I haven't been able to work with 4.8
    It became very unstable, a crop of 99991 single picture causes a message: Application out of memory Please restart
    After that it crashes. I already deleted pref files and restarted Mac several times but no luck.
    On my MacBook Pro with 10.5.6 and C14.8 I don't have these problems.

    Please Phase One get us a solution asap.

    Kind greetings,

    Bert Balcaen


    Have you tried starting a new session file?
    0
  • Gareth
    With C1 4.6 I was having the same problems under 10.5.6.

    Without warning, C1 would freeze, sometime the whole computer would freeze. On a few occasions I had that Apple multi language warning to restart my computer using the power button. The system log would always mention C1 around the time of the crash.

    I rang Applecare and they advised to unplug every single wire to the computer for about 2 min's (sounded stupid to me), reboot the machine resetting the PRAM until I heard three chimes and more interestingly trash my entire user cache folder.

    Trashing the cache folder worried me but was assured it would be fine.

    I can now report that both my Mac Pro and C1 has never crashed since (had to watch for the memory leak though in 10.5.6) and couldn't be happier with the stability of 4.8 under 10.5.7.
    0
  • NN264907UL
    I just updated to OS 10.5.7 and C1 Pro ( 3.7.9 ) will no longer work.
    The upgrade seems to be the culprit.

    David
    0
  • Brian Eaves
    Have tried deleting the prefs or trying it in a new user?

    Brian
    0
  • NN264907UL
    I call the folks at Digital Transitions in NYC and their suggestion was to delete the prefs and Phase -one cache files. IT worked like a charm.

    David
    0

Post ist für Kommentare geschlossen.