Failed to initialise audio extractor with default
- ScoularImage
- Offline
- Fresh Boarder
Less
More
- Posts: 5
- Thank you received: 0
- randylarcombe
- Topic Author
- Visitor
8 years 5 months ago #4027
by randylarcombe
randylarcombe replied the topic: Failed to initialise audio extractor with default
Hi, you are on the right track. When I last had problems it was with same thing. Either clips that were timelapses or where I had used speed ramping on a clip. In most cases, I exported just just that clip and brought it back in a pro res clip and took the original out of the timeline and that fixed it.
Please Log in to join the conversation.
- ScoularImage
- Offline
- Fresh Boarder
Less
More
- Posts: 5
- Thank you received: 0
8 years 5 months ago #4026
by ScoularImage
ScoularImage replied the topic: Failed to initialise audio extractor with default
I purchased this because Wildwood Sound told me is was the easiest solution. I'm out of time. First problem was I had two time lapses that were compound clips I exported them and brought them back in as video . Now it tells me I have something completely different wrong. Please!!!!!
Writing AAF file
Adding assets to AAF file
Adding essence for asset [A065C058_160410L4_CANON] to AAF file
Opening audio extractor for portion 0 of asset [A065C058_160410L4_CANON]
Failed to initialise audio extractor with default bit depth of 24
Failed to create QT movie
No AAF file has been generated.
X2Pro Audio Convert 3.0.13
Writing AAF file
Adding assets to AAF file
Adding essence for asset [A065C058_160410L4_CANON] to AAF file
Opening audio extractor for portion 0 of asset [A065C058_160410L4_CANON]
Failed to initialise audio extractor with default bit depth of 24
Failed to create QT movie
No AAF file has been generated.
X2Pro Audio Convert 3.0.13
Please Log in to join the conversation.
- Jeremy Norwood
- Visitor
8 years 6 months ago #3986
by Jeremy Norwood
Jeremy Norwood replied the topic: Failed to initialise audio extractor with default
If you can, try upgrading to OS X 10.11.4 and giving it another try.
We have seen this problem get resolved by something Apple updated in the latest Os X update.
Let us know and many thanks.
We have seen this problem get resolved by something Apple updated in the latest Os X update.
Let us know and many thanks.
Please Log in to join the conversation.
- randylarcombe
- Topic Author
- Visitor
- Graeme Robinson
- Visitor
- randylarcombe
- Topic Author
- Visitor
Time to create page: 0.151 seconds