• Apple Final Cut Pro Legacy

  XML Bug or Maybe a Quirk?

  Posted by Mark Maness on May 26, 2010 at 4:41 pm

  OK…. Here’s something that I hope I’m missing.

  We have two Intel systems running Snow Leopard and FCP 7.0.2. We have ONE G5 running Leopard 10.5.8 using FCP 6.0.6.

  In order to exchange projects between versions, we have to pass them as XML version 4 files. Works great for the most part, BUT… There is an issue that is a real pain in the a… The projects are formatted DVCProHD 1080i29.97. All clips that have been digitized are 2 channel mono audio.

  When I export an XML version 4 file, and then import this file into the G5 with FCP 6.0.6, all of my digitized clips are now 16 channel mono audio. PROBLEM!

  Now, every time a clip is used, we have to manually delete the extra channels of audio. This sucks.

  By the way, you can send an XML version 5 file to FCP 6.0.6, it doesn’t support it. The lower the version of XML you use, the more metadata you loose, too.

  _______________________________

  Wayne Carey
  Schazam Productions
  https://web.mac.com/schazamproductions
  sc****************@*ac.com

  Mark Maness replied 15 years, 11 months ago 2 Members · 2 Replies
• 2 Replies

• 

  Doug Beal

  May 27, 2010 at 1:23 pm

  What if you do the easy setup on the G5 go into the capture tool, modify the clip settings to shut off the extra tracks then exit out. If you go back in the capture tool and the clip settings are still showing 16 tracks, it’s possible that permissions are not being updated.
  Just a thought. I’ve seen this when unbeknownst to me someone has trashed the prefs and not said anything about it, nor restored them via pref manager. worth trying.

  Doug Beal
  Editor / Engineer
  Rock Creative Images
  Nashville TN
• 

  Mark Maness

  May 27, 2010 at 1:32 pm

  Normally, this is what we would do. But in this case everything is already digitized and the program was partially edited.

  I’m going over to that system now and trashing the prefs while the editor is on a quick shoot. But my quandary with this issue is that this issue pops up from time to time, not all of the time, but some of the time and usually trashing the prefs is the solution.

  My reason for posting this is to find out if others have seen this issue and hopefully, with a lot of positive thinking, maybe Apple will fix this, if its a common bug.

  _______________________________

  Wayne Carey
  Schazam Productions
  https://web.mac.com/schazamproductions
  schazamproductions@mac.com

Reply to this Discussion! Login or Sign Up