Do I need to update?
- debesch
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 4
- Thank you received: 0
9 years 2 weeks ago #2837
by debesch
debesch replied the topic: Do I need to update?
Thanks, Gents!
We're still not sure what went wrong, but I got my finished tracks from the audio mixer this afternoon, and I'm currently exporting out final revised masters!
If there's time someday, I may take my project on a laptop over to the audio studio and see if we can't hammer out the problem.
But if anyone has encountered weirdness exporting XMLs from FCPX going through X2Pro Audio Convert to ProTools 10, please chime in!
Thanks again,
deb
We're still not sure what went wrong, but I got my finished tracks from the audio mixer this afternoon, and I'm currently exporting out final revised masters!
If there's time someday, I may take my project on a laptop over to the audio studio and see if we can't hammer out the problem.
But if anyone has encountered weirdness exporting XMLs from FCPX going through X2Pro Audio Convert to ProTools 10, please chime in!
Thanks again,
deb
Please Log in to join the conversation.
- angus.anderson
- Offline
- Expert Boarder
Less
More
- Posts: 92
- Thank you received: 6
9 years 2 weeks ago #2836
by angus.anderson
angus.anderson replied the topic: Do I need to update?
Hi
Any easy way to see the sample rate of all clips is to use "Producers Best Friend",use it all the time and its very helpful, (also shows "effected" clips, so retimes as well).
cheers angus
Any easy way to see the sample rate of all clips is to use "Producers Best Friend",use it all the time and its very helpful, (also shows "effected" clips, so retimes as well).
cheers angus
Please Log in to join the conversation.
- James Carrick
- Offline
- Moderator
Less
More
- Posts: 807
- Thank you received: 35
9 years 2 weeks ago #2832
by James Carrick
James Carrick replied the topic: Do I need to update?
Hi Debesch,
No you don't need an update and I would agree with you that you shouldn't update unnecessarily in the middle of a project.
When you perform the conversion in X2Pro it will tell you about any retimed clips that it encountered and the time that they appear in the project n.b. we will transfer the clip without any speed/timing applied, in the AFF, the Start time for such a clip will be exact but the end time will be dependent on the actual length of the clip prior to retiming.
You can look in FCP for the clips at the times that X2Pro reports, and you can show the retiming bar for clips in the timeline by selecting them and pressing CMD+R (this works when you have multiple clips selected).
To confirm different samples shouldn't cause sync issues as long as you don't tell Pro Tools to apply SRC when it is importing. Personally like yourself I would like to harmonise the rate used in a given project as your never 100% sure where its going to go afterwards, but its not essential.
If you want to convert everything to 48K, then the details of what clip is what can be seen in the FCPXML if you search for "audioRate", bit tedious to do with a big sequence but I cannot think of an easier way of getting the info for all clips.
Hope the above helps.
Yours Sincerely
James.
No you don't need an update and I would agree with you that you shouldn't update unnecessarily in the middle of a project.
When you perform the conversion in X2Pro it will tell you about any retimed clips that it encountered and the time that they appear in the project n.b. we will transfer the clip without any speed/timing applied, in the AFF, the Start time for such a clip will be exact but the end time will be dependent on the actual length of the clip prior to retiming.
You can look in FCP for the clips at the times that X2Pro reports, and you can show the retiming bar for clips in the timeline by selecting them and pressing CMD+R (this works when you have multiple clips selected).
To confirm different samples shouldn't cause sync issues as long as you don't tell Pro Tools to apply SRC when it is importing. Personally like yourself I would like to harmonise the rate used in a given project as your never 100% sure where its going to go afterwards, but its not essential.
If you want to convert everything to 48K, then the details of what clip is what can be seen in the FCPXML if you search for "audioRate", bit tedious to do with a big sequence but I cannot think of an easier way of getting the info for all clips.
Hope the above helps.
Yours Sincerely
James.
The following user(s) said Thank You: debesch
Please Log in to join the conversation.
- debesch
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 4
- Thank you received: 0
9 years 2 weeks ago #2831
by debesch
debesch replied the topic: Do I need to update?
One more thing to add...
I whiffed the audio conversion for the temp music from the audio post house. Usually I convert to 48kHz AIFFs before I import music. I made the AIFFs, but apparently I neglected to convert from 44.1kHz to 48kHz.
Any change this is part of the issue, or is that a non-problem these days and my adherence to conversion merely shows how far back I go... :-P
I whiffed the audio conversion for the temp music from the audio post house. Usually I convert to 48kHz AIFFs before I import music. I made the AIFFs, but apparently I neglected to convert from 44.1kHz to 48kHz.
Any change this is part of the issue, or is that a non-problem these days and my adherence to conversion merely shows how far back I go... :-P
Please Log in to join the conversation.
- debesch
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 4
- Thank you received: 0
9 years 2 weeks ago - 9 years 2 weeks ago #2830
by debesch
debesch replied the topic: Do I need to update?
Also, I got this string in my report, if it helps/matters. The retimings are things like freezes that shouldn't affect the audio, Also, I thought I had turned noise reduction off, but apparently I missed some:
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:28.19 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:31.36 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:03.51 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:34.28 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:36.87 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:35.36 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:04:09.18 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:59.71 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:00:03.93 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:32.90 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:29.86 has been ignored.
• Retiming is not supported. The retiming at 00:05:37.80 has been ignored.
• Retiming is not supported. The retiming at 00:05:36.84 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:00:04.73 has been ignored.
• Retiming is not supported. The retiming at 00:05:32.87 has been ignored.
• Retiming is not supported. The retiming at 00:05:46.97 has been ignored.
• Retiming is not supported. The retiming at 00:03:15.28 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:27.27 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:28.19 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:31.36 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:03.51 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:34.28 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:36.87 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:35.36 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:04:09.18 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:59.71 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:00:03.93 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:32.90 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:29.86 has been ignored.
• Retiming is not supported. The retiming at 00:05:37.80 has been ignored.
• Retiming is not supported. The retiming at 00:05:36.84 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:00:04.73 has been ignored.
• Retiming is not supported. The retiming at 00:05:32.87 has been ignored.
• Retiming is not supported. The retiming at 00:05:46.97 has been ignored.
• Retiming is not supported. The retiming at 00:03:15.28 has been ignored.
• Noise reduction is not supported The Noise Reduction adjustment at 00:02:27.27 has been ignored.
Last Edit: 9 years 2 weeks ago by debesch.
Please Log in to join the conversation.
- debesch
- Topic Author
- Offline
- Fresh Boarder
Less
More
- Posts: 4
- Thank you received: 0
9 years 2 weeks ago - 9 years 2 weeks ago #2829
by debesch
debesch created the topic: Do I need to update?
I'm trying to export out an AAF for an audio mixer using ProTools10. I'll spare you the gory details, but it took six tries before I could generate something that at least filled his timeline. But even then, the clips were apparently not where they were supposed to be. He had to leave to go do another session, so I was left to fend for myself trying to make files that he could read.
I even went old-school and made AIFFs for him in case we can't solve the XML-AAF translation problem. (one of the first problems we had was the clips in his timeline were not coming from the right part of the original media. Where a man should have been showering us with his wisdom, instead we heard the producer asking him a question.)
About a week or so ago, I updated X2Pro because I was between projects. I now see that there is another update. I'm on OS X Yosemite 10.10.5, running FCPX 10.2.1. My installed X2Pro Audio Convert is 2.5.1.
I'm wary of running an update willy-nilly in the middle of a project, but if this is a known problem, and the update fixes it, then YaY! If it's not, I can give you more details about the FCPX project, my XML export settings, and/or the X2Pro settings I tried. It was a mis-mash of trying things, so I don't know how useful it would be for you. But I'm willing to try.
And, of course, we're on a bit of a deadline. It's due Friday.
I even went old-school and made AIFFs for him in case we can't solve the XML-AAF translation problem. (one of the first problems we had was the clips in his timeline were not coming from the right part of the original media. Where a man should have been showering us with his wisdom, instead we heard the producer asking him a question.)
About a week or so ago, I updated X2Pro because I was between projects. I now see that there is another update. I'm on OS X Yosemite 10.10.5, running FCPX 10.2.1. My installed X2Pro Audio Convert is 2.5.1.
I'm wary of running an update willy-nilly in the middle of a project, but if this is a known problem, and the update fixes it, then YaY! If it's not, I can give you more details about the FCPX project, my XML export settings, and/or the X2Pro settings I tried. It was a mis-mash of trying things, so I don't know how useful it would be for you. But I'm willing to try.
And, of course, we're on a bit of a deadline. It's due Friday.
Last Edit: 9 years 2 weeks ago by debesch.
Please Log in to join the conversation.
Time to create page: 0.153 seconds