Got Leopard? Post your problems/joys/thoughts here

If you are one of the brave souls who just purchased OSX Leopard and can't wait to install (of course you are between projects, right?) post everything Leopard here in this thread.

This sticky will remain up for a few months and your post will be of great value to all who read it.

We are really looking for how it plays with Final Cut Studio, but anything you have to say is valuable to us all.

Please post your computer, Ram, Storage System and whatever Capture Cards you might use. Give us more information about your system than you think we might need.

Thanks for your help

Michael Horton
-------------------

Someone on my local Mac usergroup posted yesterday that his keychain with all his passwords was deleted as a result of installing Leopard.

He solved the problem by using text edit to view the contents of a file, and found that his keychain had been renamed. Renamed the keychain back to login.keychain and everything was fine again.

Not sure if this is a common anomaly, but worth posting all these things for those that might come looking.


UPDATE 28th Oct : Apparently there is now an update for Leopard that addresses this issue.

a post over on the COW highlights an apparently "known issue" with FxPlug's and Leopard:
[forums.creativecow.net]

plus another thread regarding (possible) problems with a BMD card, and also a problem witha Highpoint RAID card that may be relevant to some FCP users:
[forums.creativecow.net]

Got this from the Cow. Reposting it here, because it deals with the Matrox MXO and our favorite FCP repair tool:

[forums.creativecow.net]

The Matrox MXO 2.0 drivers also don't work in Leopard. The MXO box is dead. FCP Rescue 6 is broken. Mac Janitor broken. All Adobe apps seem to be opening up fine, but I will have to actually do some work in them to see if they are really stable. Repair permissions does take forever, and what I find amusing is the only warning it gives is the remote access update file from software update I received after installing Leopard! Fortunately I am leaving my main editing system alone for quite awhile until all the bugs are ironed out!


www.shanerosseditor.com

Listen to THE EDIT BAY Podcast on iTunes
[itunes.apple.com]

From Apple's Motion discussion group:

People have a short memory: the same thing was encountered when Tiger came out. As you might be aware, Final Cut Studio (especially Motion) uses a number of shared frameworks which are not stored in the app (being shared and all) but in the /System/Library and /Library directories.

When you do an Archive & Install, the OS installer just copies over your home folder and the contents of the /Applications directory. This leaves the frameworks stranded. You'll probably run into similar issues with the newer Adobe stuff.

You'll need to reinstall Motion. Just make sure you delete it from the /Applications directory, first, or you'll end up with the missing presets problem.

Great info, mark

IMHO with a major OS upgrade, to avoid unforseen incompatibilities & wipe out unnecessary software you should "Carbon Copy Clone" your current HD to an external / separate drive, wipe / reformat your boot drive and do a fresh install of Leopard. Then fresh install all apps & plug-ins. You can pull frameworks & any other settings over to your boot drive afterwards.

Carbon Copy Cloner is now v.3 and is UB (it's also a free download):

[www.bombich.com]

We would love to hear your success / horror stories related to Leopard so please share them with us!

When life gives you dilemmas...make dilemmanade.

Installed Leopard last night; had absolutely no install problems (took less than an hour). So far everything seems to working as should be. My projects are minimal, so storage is not a problem. After Leopard was installed, I turned on TimeMachine and backed up my entire 250GB internal system disk (had about 82GB and took about 45 minutes) to the G-Raid external on FireWire 400.

Thanks goodness I did!

Today, I wanted to experiment with BootCamp. Big mistake...!!!.

The problems it caused required I erase the Mac system drive and reinstall Leopard as the only resolution. After I had a fresh copy of Leopard installed, I used the utilities from the install CD and the option to reinstall the operating system from backup. TimeMachine worked flawless and I was back operating just as I was before I fiddled with the darned BootCamp. I'd say more about that, but this isn't the place. I'm going back to Paralles (which I had working fine before) as I can run it in a window within Leopard. Apparently, you can't do that with BootCamp. You either start in OS X or Windows and have to "restart" each time you switch....!! Will report back if I encounter any problems working with FCP while TimeMachine is "on". If it causes any slow down or other problems, it can be manually turned off for the times you don't want it to operate.

So far, am happy with the upgrade. Just need to get used to doing somethings a bit differently and learn to recognize the visual changes.

Regards, Cyrus
iMac 27" Intel i7 Quad-Core; 16GB RAM; 2TB HD
Final Cut Studio, FCP X, Photoshop CS5, After Effects, etc.

Finding lots of good articles out there on installing Leopard and solving problems after you install.

Macworld dot com has an excellent article on "How to install Leopard" including options to install. Find it here:
[www.macworld.com]

Apple has posted good Applecare docs on Leopard

Mac OS X 10.5 Leopard Installation requirements
[docs.info.apple.com]

Installing Mac OS X 10.5 Leopard
[docs.info.apple.com]

Mac OS X 10.4, 10.5: About installation options
[docs.info.apple.com]

Mac OS X: About the Archive and Install feature
[docs.info.apple.com]

Mac OS X 10.5: "Blue screen" appears after installing Leopard and restarting
[docs.info.apple.com]

Mac OS X 10.5: Unable to log in to account after an upgrade install
[docs.info.apple.com]

Mac OS X 10.4, 10.5: Where is StuffIt Expander?
[docs.info.apple.com]

Mac OS X 10.5 Leopard: Information to collect before an Erase and Install
[docs.info.apple.com]

Mac OS X 10.5 Leopard: Installing on a UFS-formatted volume
[docs.info.apple.com]

Mac OS X 10.5 Leopard: Using Apple Hardware Test after erasing your disk
[docs.info.apple.com]

Mac OS X 10.5: Included printer drivers
[docs.info.apple.com]

Mac OS X 10.5: Unable to log in to account after an upgrade install
[docs.info.apple.com]

Mac OS X 10.5: Unable to start up after installing Apogee audio drivers
[docs.info.apple.com]

Mac OS X keyboard shortcuts
[docs.info.apple.com]

Michael Horton
-------------------

Adobe has issued a statement about compatibility between its products and Leopard:

Thanks to close collaboration between Adobe and Apple, most of the CS3 applications and associated technologies, such as Adobe Bridge CS3, Version Cue CS3, and Device Central CS3, are compatible with Mac OS X Leopard without requiring additional updates.

However, the following CS3 applications will require updates for full compatibility with Leopard: Adobe Acrobat 8 Professional and our professional video applications, including Adobe Premiere Pro CS3, After Effects CS3 Professional, Encore CS3, and Soundbooth CS3.

We expect to publish free Leopard compatibility updates for the video applications in December 2007 and for Acrobat 8 Professional and Adobe Reader 8 in January 2008.

While older Adobe applications may install and run on Mac OS X Leopard, they were designed, tested, and released to the public several years before this new operating system became available. You may, therefore, experience a variety of installation, stability, and reliability issues for which there is no resolution. Older versions of our creative software will not be updated to support Mac OS X Leopard.

For complete info go to Adobe and click on "Compatibility with Leopard"

Michael Horton
-------------------

Thanks Mike.

Posting that last bit, you probably just saved me (and other After Effects CS3 Pro users) a ton of problems. Well...I won't be going to Leopard until next year then (at least until the AE CS3 Pro Leopard patch is posted).

When life gives you dilemmas...make dilemmanade.

I'm in between projects but still doing some finishing work on them. I've upgraded and have had absolutely no problems with two separate films, but I'm just doing simple feature editing using firewire drives. Dialogue films, no VFX of any consequence.

If you do Boot Camp, absolutely print out the installation instructions. There are a bunch of exact things you have to do during the Windows installation that if you don't do correctly will hose your drive. Once it's installed it works fine, though it does require a reboot. I have not tried Parallels yet, but found the emulation very slow in Tiger compared to Boot Camp, and expect it'll be the same in Leopard.

Hope this is not off topic, it shouldn't be......

CalDigit products are fully compliant with Leopard, FireWireVR to HDPro and everything in between.

Just FYI. We'll be posting a press release very soon on this.

From TidBits, via local usergroup

"
Back to My Mac Security Warning** -- Alan Oppenheimer and Open Door
Networks are cautioning Leopard users to turn off the Back to My Mac
feature due to a security vulnerability that enables anyone with
access to your .Mac account password to control your Mac remotely.
Back to My Mac is located in the .Mac preference pane, and is
enabled by default. [Open Door has now posted more details.]

[www.isfym.com]
[www.isfym.com]

They write: "The problem came in when we selected the server Mac in
the client's sidebar. Instead of either connecting to that Mac's
File Sharing as a guest, or asking us for that Mac's password, Back
to My Mac automatically connected to the server Mac's File Sharing
as that Mac's owner without ever asking for the owner's name and
password. Worse yet, the same thing happened when then clicking on
'Share Screen...' giving us full remote control of the Mac without
ever entering its password.""

I just read this on Google news titled --Blue screen of death-- Ouch

click here

[docs.info.apple.com]

Wireless problems

FCP Rescue 6 does not work with 10.5

Compressor 2 no longer works once I upgraded to Leopard. I've pin-pointed my specific issue for the cause of this error: "qmasterd is crashing at startup". Since this Qmaster daemon is not running on my machine compressor won't submit batches. I strongly believe it is crashing because of the new OS. I've tried just about everything including a lot of the work-arounds on the web to get Qmaster to star manually as well as Apple's fix to reinstall the apps...I followed every step on this detailed website [www.kashum.com] and nothing...I was referred to this forum by a friend hopping someone here can help with this issue and get Qmaster running again! Any help is greatly appreciated.

I thank you in advance!

Dax

I"m Using FCP 5, Compressor 2 and Apple Qmaster 2 on Leopard.

Here's the Crash Log:

Process: qmasterd 712
Path: /usr/sbin/qmasterd
Identifier: qmasterd
Version: ??? (???)
Code Type: PPC (Native)
Parent Process: qmasterd 711

Date/Time: 2007-10-30 20:42:06.061 -0700
OS Version: Mac OS X 10.5 (9A581)
Report Version: 6

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x00000000931cd418
Crashed Thread: 0

Application Specific Information:
single-threaded process forked ***

snip

So far I've just updated a Drive to Leopard (ie: NOT a clean install)

No problems with any software apart from Techtool doesnt support Leopard yet and iShowU crashes the system when you try and screen record.

All Microsoft 2004 apps, All Adobe CS2 apps, Adobe After Effects 6.5 & 7 work, All Apple FCS2 work fine as does a number of utility apps like MPEG Streamclip.

Skype also works.

Apple Motion 3 works without reinstalling



For instant answers to more than one hundred common FCP questions, check out the LAFCPUG FAQ Wiki here : [www.lafcpug.org]

This from MacinTouch today

Monday, November 5, 2007 16:20 EST
Notes and Tips

In a quick test here at MacInTouch, we have confirmed a critical data-loss bug in Leopard's Finder.
In our test, we used Command-drag to move several large folders from a MacBook internal drive to an attached FireWire 800 external drive. While the folders were copying, we disconnected the FireWire cable. The folders disappeared from both drives!
When we tested the same operation using the "mv" command from the Terminal command line in Leopard, the source folders were not deleted prematurely. A quick test of Command-drag moving in Mac OS X 10.4 Tiger's Finder also failed to duplicate the Leopard Finder bug, which was documented initially by Tom Karpik:

Massive Data Loss Bug in Leopard
Leopard's Finder has a glaring bug in its directory-moving code, leading to horrendous data loss if a destination volume disappears while a move operation is in action. I first came across it when Samba crashed while I was moving a directory from my desktop over to a Samba mount on my FreeBSD server.
I've now run tests on a Windows XP SP2 SMB mount, as well as a local HFS+ formatted USB drive, and the bug surfaces every time the destination disappears while the Finder is moving something to the destination.

___________________________________________________________

Also apparently QT 7.3 blocks up the Britney Porn Trojan Horse hole. Um. That probably could have been worded better.

Quote

Also apparently QT 7.3 blocks up the Britney Porn Trojan Horse hole. Um. That probably could have been worded better.

I was chewing on a jordan almond when I read that line...just coughed half of it through my nose. Owie...

Back on topic...YIKES!!! Won't be upgrading until AT LEAST 08 or until the first .x bug releaase. I can't wait to see what else pops up. Awesome work, guys.

When life gives you dilemmas...make dilemmanade.

I first did an install on new Mac Book Pro - all went great - MBP feels faster, looks sharper - FCP 6 et all fine. so for INEL based computers it seems like you DO feel more of the power of the CPUs' and the RAM from Leopard.

Then ventured to G5 Quad, 8 gigs RAM 12 terabyte RAID 5 arrays, and all went to hell. I use HIGHPOINT array Cards and they had an update but it does not work properly in i think talking to the caching/indexing function of the new Spotlight. Also run Blackmagic HD LINK and DECK link Extreme - and after update from them everything seems ok on the HD monitor front.

As others have said ARCHIVE and INSTALL will cause you to reinstall FCP, MOTION etc., but it appears not to be worth it as i did it both ways with the same result.
Spotlight never properly indexes my drives - internal or external - it never finishes. You can see MDS and another indexing processes running at up to 100% (or 25% of total load) for days. I turned off Spotlight for all but the home drive and i am stable, but not good.

FCP 6 DOES run - but it loads slow, and i have reproducible issues with files that are brought in - which i assume is due to no DB or index file of where that file lived yesterday. (but i am no engineer - just my gut)

The Apple boards are full of Leopard 'Spotlight/indexing' issues so I assume there is an issue here somewhere.

These are my subjective findings, and i hope Apple engineers are not all back on the iPhone. This upgrade was delayed 6 months due to them all being moved to get the iPhone out, and I guess i mistakenly had high expectations that with 6 extra months we would get stable code.

Thanks,

Art Bell

www.dreamlikepictures.com

I don't know if I missed something and I've been trying to find an answer to this question, but are there (supposed to be) any benefits for FCS2 users when upgrading to Leopard?

It's obvious now that Leopard is not ready for FCS2 (and third party vendors) or viceversa but was the new engine actually supposed to speed up some processes ie facilitate working with the FCS2 apps?

I'm fine with Tiger and use my Quad purely as an editing machine. I have a PC for surfing/email and all the clutter...

So... was there supposed to be a good reason for me to 'upgrade' to Leopard?

Jeroen Wolf
Imagine Video
www.imaginevideo.nl

Probably not. If you don't need or want its features don't buy it.

I believe the issue is more in overall performance. Prior to Leopard, there may be performance left unused to do 32 bit addressing limits and the subsequent inability to address more than 2 GIGS of RAM, regardless if you installed 8 - as i did.

Activity Monitor now shows all 8 being used when I have say both FCP, MOTION and CS3 open at the same time.

So i think you are correct technically - FCP is not getting faster - but in full on production mode you should feel less latency. And as a result of the 64 bit addressing finally native in Leopard one would expect updates to all the Pro apps to utilize this soon.


Just my view from waaay outside Cupertino.

.../Art Bell


www.dreamlikepictures.com

Walker Wrote:
-------------------------------------------------------

> Activity Monitor now shows all 8 being used when I
> have say both FCP, MOTION and CS3 open at the same
> time.
>
> So i think you are correct technically - FCP is
> not getting faster - but in full on production
> mode you should feel less latency. And as a result
> of the 64 bit addressing finally native in Leopard
> one would expect updates to all the Pro apps to
> utilize this soon.
>
>
> Just my view from waaay outside Cupertino.
>
> .../Art Bell
>

So maybe FCP is not getting any faster, but FCS is. So technically that WOULD be a legit reason to upgrade, right?

If I could go again - i would wait til Leopard 10.5.1 comes out and FCP 6.02.

I am up and running - but today for example iChat won't open and i still have NO search function.

You have no search function in the Finder? Sounds like you have a bad installation. iChat is part of the OS and should load correctly. Yours is the first machine I've heard of with these specific problems.

Well ...it appears the iChat is an Apple network issue so that was just a co incidence, but as for the Spotlight /indexing issues - there are currently over 500 hundred folks on the Apple boards with exactly the same issue.