View Full Version : "An unexpecter error occurred" - Audio
Dylan Reeve
08-04-2008, 08:47 PM
On Batch importing clips into Avid from REDline generated proxies, I get the following message:
An unexpected error occurred while importing the Quicktime Audio Tracks.
The imported audio tracks may be unusable.
Would you like to continue the import?
[Continue] [[Abort]]
This happens even when I:
Modify Avid clips in bin so no Audio track is required.
Use --avidAudio option in REDline
Chant random good luck spells found on the internet.
Looking at the files in Quicktime they report:
Without --avidAudio
32bit Integer (Big Endian), Mono, 48.000kHz
With --avidAudio
24bit Integer (Big Endian), Mono, 48.000kHz
The actual files were shot with no audio on the day.
If I use Quicktime Pro's Movie Properties control and delete the Audio track, then they import fine.
So - anyone else?
I'd like to suggest that REDline include a '--noAudio' option perhaps?
MichaelP
08-05-2008, 04:45 AM
The next version of MC (Q3) allows the 32bit packed audio to pass through. In the meantime, REDruhes (and probably REDline) has an Avid Audio compataibility mode to allow the audio to be 48 as expected in current versins.
Michael
Dylan Reeve
08-05-2008, 04:50 AM
I tried with both modes - indeed with the Avid compatible audio flags I do get a 24-bit Audio track. 48kHz Mono. It is mute as far as I can tell, and actually may contain nothing at all?
In this case no audio was recorded on the camera (I'm not sure what the camera settings were, but there were certainly no audio devices plugged in.
Also with the previous 32-bit audio I found that if I removed the Audio tracks from my offline clips in the Avid bin before importing then I was able to import without a problem. In this case Avid seems to be spotting a problem with the Quicktime file itself, despite the fact it's not even being asked to link any Audio tracks.
MichaelP
08-05-2008, 08:27 AM
There can always be silence recorded at 24/48khz which would explain the audio piece. If you remove the audio tracks, then there are no issues since it is in refernce to the 32bit packed audio.
Anyone else having success with audio? I have two clips that have sync audio from the camera, and they come in fine - albeit levels are low, but the shoot was not about audio, but we grabbed it anyway - so it could be bad levels at time of production.
Michael
Dylan Reeve
08-05-2008, 02:08 PM
I'll play around a bit more when I get a chance and see if I can find anything else.
Do you know of any tools that might help me check the validity of a Quicktime file and show up any likely problems that might be confusing Media Composer?
Also, any way to delete the Audio tracks in multiple QT files easily? Automator doesn't have a track delete action (it has enable/disable but that doesn't help).
MichaelP
08-05-2008, 07:39 PM
That would be a nice request for REDrushes. let me see what I can find as well as find out when the release of MC comes out that supports the 32 bit packing.
Jason Diamond
08-05-2008, 07:48 PM
yeah weird. i remember when i came across this the first time and i removed the audio and it worked fine but haven't had this prob since.
are you choosing "PCM" as your audio format when you convert?
FlorianDehmel
04-27-2009, 04:32 AM
Hello,
got the same issue. When I am batch importing the clips into Avid Adrenaline I get an error for every clip. Enabling Avidcompatible Audio in Redrushes does not change anything. Also to deactivate Audiotracks within the Avid does not help.
Is there another solution than removing the Audio from every single clip, which means to get through another app like MpegStreamclip for about 120 Clips...
Greets, Flo
MichaelP
04-27-2009, 05:59 AM
You can always process the clips through MPEG Streamclip for picture and sound after creating the ALE in REDline or REDrushes.
Michael
FlorianDehmel
04-27-2009, 06:09 AM
yes, but it would be nice without this step. Like a "disable audio " option in redrushes or something similar...
M Forrest
04-28-2009, 12:29 AM
I had the same error, bringing them in on a Mac Adrenaline solved it for me.