Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Error importing Red Epic files in Avid Media Composer 6

Brian Merlen

Well-known member
Joined
Jul 31, 2010
Messages
3,185
Reaction score
0
Points
0
Age
40
Location
Stamford CT
Website
vestadalux.com
It should be noted I am new to Avid entirely and a non epic owner, so please have some patience with my ignorance, I am a total newb on the NLE.

I made a new sequence/project, went to my bin, right clicked import and I got the following error message when trying to import "the file format of (file name) is not supported for import"

So then I decided "well I'll try it using AMA"

Right click, link to AMA, and it says "There were errors linking AMA files, see console for details".

The console says:

" p, li { white-space: pre-wrap; }
------ AMA Link To File(s) ------

Trying to open a RED file with the QuickTime AMA plug-in failed. [ Plugin Name = QuickTime Plug-In Avid Technology, Inc. Version = 1.2 ] does not support /Volumes/Seagate 500GB HD/r3d files/A001_C003_0929N5_001.R3D"


It should be noted that I am using a core 2 duo Mac, 8gbs ram, with my media and project file on an external and that the files I have are r3ds that no longer have the file structure of the mag intact. meaning I downloaded them from the Reducation class I took via Reds site and they are only R3d files without the file structure of the mag formatting in place (quicktime ref files like on the red one if i remember right, its been a while since May when i took the class? i dont have a mag or epic and cant remember what those little files are in the mag structure, but you know what i mean, the non .r3d stuff in the mag? or maybe i am thinking of the red one mag structure not sure about this entirely).



I am really not sure where exactly my trouble is coming from, whether I am missing a plug in, or my HDD's are too slow (that is what my guess is), or that my external drive is USB2 only so the port is too slow? I know my HDD's/USB 2 port could very well be the problem, simply too slow perhaps? I am going to try using a faster external with firewire and see if the error still happens, but any helpful advice would be appreciated! Like I said I am a total newb to Avid and I totally understand my system is barely passing the minimum specs. Its not like I am looking for real time performance here, I was just trying to play around with some footage and see how it performed on my ancient mac while dabbling on an NLE I am not entirely familiar with quite yet. The problem could also be the NLE needs the file structure of the mag in place and since I don't have that, its causing a problem? I am not really sure which is causing this though, definitively speaking and would highly appreciate any advice you can spare? Thanks in advance guys!

PS I understand I can use Redcine X Pro to convert to proxy files to edit in MC6, but I was attempting to check out how poorly my set up would run natively with r3d files being imported and cut in MC6...I am going to load the files in RedCine X Pro just to make sure they aren't corrupted, I am downloading the newest version now
 
Last edited:
Your quite sure it's the very latest version? Epic support is from 15 November, so if it's more than a week old that could be your problem.

It should be noted I am new to Avid entirely and a non epic owner, so please have some patience with my ignorance, I am a total newb on the NLE.

I made a new sequence/project, went to my bin, right clicked import and I got the following error message when trying to import "the file format of (file name) is not supported for import"

So then I decided "well I'll try it using AMA"

Right click, link to AMA, and it says "There were errors linking AMA files, see console for details".

The console says:

" p, li { white-space: pre-wrap; }
------ AMA Link To File(s) ------

Trying to open a RED file with the QuickTime AMA plug-in failed. [ Plugin Name = QuickTime Plug-In Avid Technology, Inc. Version = 1.2 ] does not support /Volumes/Seagate 500GB HD/r3d files/A001_C003_0929N5_001.R3D"


It should be noted that I am using a core 2 duo Mac, 8gbs ram, with my media and project file on an external and that the files I have are r3ds that no longer have the file structure of the mag intact. meaning I downloaded them from the Reducation class I took via Reds site and they are only R3d files without the file structure of the mag formatting in place (quicktime ref files like on the red one if i remember right, its been a while since May when i took the class? i dont have a mag or epic and cant remember what those little files are in the mag structure, but you know what i mean, the non .r3d stuff in the mag? or maybe i am thinking of the red one mag structure not sure about this entirely).



I am really not sure where exactly my trouble is coming from, whether I am missing a plug in, or my HDD's are too slow (that is what my guess is), or that my external drive is USB2 only so the port is too slow? I know my HDD's/USB 2 port could very well be the problem, simply too slow perhaps? I am going to try using a faster external with firewire and see if the error still happens, but any helpful advice would be appreciated! Like I said I am a total newb to Avid and I totally understand my system is barely passing the minimum specs. Its not like I am looking for real time performance here, I was just trying to play around with some footage and see how it performed on my ancient mac while dabbling on an NLE I am not entirely familiar with quite yet. The problem could also be the NLE needs the file structure of the mag in place and since I don't have that, its causing a problem? I am not really sure which is causing this though, definitively speaking and would highly appreciate any advice you can spare? Thanks in advance guys!
 
I only did a very quick test and was unable to access my 4k HD files using AMA using the new Media Composer 6.0 on an iMac. Not sure what the deal is. More testing later.
 
Everyone, you need to install the latest AMA R3D plugin for this with MC6, AFAIK. www.avid.com/ama. This is NOT installed by default.


Thanks, will try this out and report the results once I am home in front of my NLE machine again in a few hours. I am positive I am using MC 6, but I didn't download that plugin so that is probably my issue. Much appreciated guys!
 
Last edited:
I downloaded the plug in and was able to import most of my r3d files successfully. Some of them didn't import, I suspect because they were cut down in Redcine Pro X and weren't the complete r3d files, and from what I skimmed over in the pdf about the Red AMA plug in you can't cut the files down in RedCine X Pro and then try to import them. It could even be the extensions of those files, they ended with the word "r3d.part" not ".r3d" and since I downloaded them off the Reducation link I suspect they were cut down already and that is why it says part at the end of the r3d extensions. It might work if I remove that word, I will try that later...

Upon playback of the clips that I was able to import successfully there was quite a bit of flickering in both the left window viewer or the right window timeline, I suspect this is a render or playback setting issue. All I did was grab the files that imported and throw them in the timeline with no cuts or effects. It flickers on playback and then gives me an error message saying the following when I try to play them in the timeline (it doesn't give me this error when I play them in the left window viewer):

p, li { white-space: pre-wrap; } @ Tue Nov 22 23:43:51 2011
• Exception: ADM_COREAUDIO_UNDERRUN


Not really sure what that means, but at least I am slowly progressing here! I have no idea what resolution (pretty sure they are all 5k) or frame rates these were shot at, they are files I grabbed offline after all my own r3d files were lost when one of my drives went down. I will try messing with settings and reading up on what this new error message is, but if someone wants to give me some more tips I would greatly appreciate it. I am a total Avid newb so I am just trying to figure this out as I go along. I am probably making errors on a consistent basis, but hey at least I am slowly learning a new NLE! Thanks guys, much appreciated!

PS my timeline is all light green with dark green dots on it, so I am rendering now to see if that gets rid of the play back flickering and error message, will update you guys if this fixes everything for me.

UPDATE

same error still when playing the timeline and same flicker in both the previewer and timeline. The clips are still all light green with dark green dots on them after rendering. when i scrub the timeline without playback going all of them show me the frame besides one or two that say "fatal error" and are black with no frame showing during the scrub. its possible those one or two clips could be corrupted, perhaps. I will try those same clips in RedCine X Pro and see if they work there.

UPDATE 2

Apparently I am not the only one with this issue, and its not limited to only r3d files either...

http://cstest.avid.com/forums/t/102761.aspx?PageIndex=5
 
Last edited:
Audio Underrun errors mean that media is not coming through the system fast enough (audio not necessarily being the culprit).

The green dots mean that your files are a different frame rate than your project/sequence. Avid will auto-apply a motion adapter, basically doing a frame rate conversion.

Click on the bin, choose Bin->Choose Columns, and select the FPS column. It will tell you the frame rate of the clips. Make sure you then create a project with the appropriate frame rate.

You mentioned a Core 2 Duo machine. Avid won't guarantee any RT playback of R3D on such systems. They explicitly mention that R3D needs a LOT of horsepower. More like 12-core Macs and z800's, like they qualify.

External USB2 drives won't help you much either. You need faster CPU's and RAID drives to pull off smoother R3D performance.

That said, you can try to lower the strain on your system by clicking the yellow/green button to the lower left of the Avid timeline. In yellow/yellow mode, it will decrease Debayer to 1/16th or so. Yellow/Green is something like 1/4, green/green is like 1/2.
 
I have had the Fatal Error Reports also, though mostly when native Red AMA files are stacked on top of each other -i.e. on V1 and V2. But I have had this audio underrun and I've got a top spec'd Mac Pro with Atto R380 and 12GB Ram...they know it's an issue and a patch should be coming.

Play with your RCXPro export settings -I did have some crazy flicker on one clip out of perhaps 100 when I used a different export setting. When I use my default the clip came into Avid fine.
 
I decided to step it down a notch and try some DSLR 1080HD video to see if that worked (though for the record I can playback r3ds in CS5 on my lame duck core2duo just fine at 1/16th and was hoping to do the same in Avid).

The link to AMA worked but I got the same Audio underrun error upon playback in both the left and right player windows....

Maybe AMA is the bug, or maybe its my usb2 external source drive? So I am trying to import it the old fashion way right now to see if that works. If it doesn't I am going to try using a raid 0 firewire 8 drive as my source drive to see if that fixes the issue. If all else fails I will wait for Avid to patch the bug, but until I try these last few tests I refuse to admit if its the bug everyone else is getting, or its my hardware. I think it could be either, so I am going to test for either...
 
USB2 is most likely the culprit as they are not very fast as it is for sustained playback, and if the media is scattered with lots of cuts, it may not be able to keep up with that either. Sound files are much smaller and can have more of them scattered all around. Download the Blackmagic Disk Speed application (free) or similar type application to get true speed of the drive and what it can support in the best of conditions.

Michael
 
I didn't even make cuts, I used AMA to link it, dropped one clip in the timeline and attempted to play back. I set it to yellow yellow and i still get that same error...

So I tried importing it instead of using the AVCHD AMA route, it takes a long time to convert it to DNXHD 45 and at the end it gives me an error message. I did the import with 9 files and am halfway through but when each clip ends importing I get an error and it moves to the next or asks me to abort. Next time there is an error I will tell you guys what it says, will update shortly... when its done and I can copy paste off my console...

USB2 could very well be my problem or maybe my 5400rpm internal hdd? I have a broken firewire 8 raid 0 that I am in the process of getting replaced, when possible I will try to use that. If that doesn't fix it I am considering upgrading my internal drive to SSD or getting a new system if needed.

Im just trying to dabble with Avid and CS5, I just gave up on FCP recently. I have gotten my head around Ppro cs5, and wanted to learn Avid but these workflow problems are cramping my style. I will keep trying to diagnose the problem myself while I await software patches... Lots of people been having issues with this, its a .0 release and we deserve every bit of trouble we get until some patches are out. I just want to make sure its not my hardware exacerbating the buggyness and I have nothing to do I might as well try and play around with the software and see if I can get it to bare bones function!

Tomorrow I am even considering trying to run some SD mini dv footage through it to see if I still have problems with playback! Its gonna take a while to get my fast 7200 raid back from hitachi so I got time on my hands to try and play around with the settings and see if I can make anything work at all in Avid MC6...
 
Last edited:
Here is what my console gave me as an error when I tried to import instead of using AMA... at least the AMA got the files in my bin! This didn't result in anything being in my bin and took 1000 times longer to process! I think its just buggy, or that I need to get my raid back and invest in an SSD or a 12 core... or both....

p, li { white-space: pre-wrap; } ---- Channel: input buffer ------
Channel V_Dec_vc3454_ss32: ExecuteStream failed on Codec
CChannel: error: CMError_Codec, function ExecuteStream, line 398, internal codec error string: H264IBPCODEC ERROR NO FREE IMAGE
Exception caught in APlayer::Play - Exception: FATAL_ERROR, msg:Assertion failed: CMError_No_Error == cmErr, file:/Snapshots/relengsnow5_1319677901/coresw/ame/Projects/Mac/../../src/Consumers/Imports/AvchdVideoImpConsumer.cpp, line:1031
Exception:
@ Thu Dec 1 20:20:03 2011
• Exception: FATAL_ERROR, msg:Assertion failed: CMError_No_Error == cmErr, file:/Snapshots/relengsnow5_1319677901/coresw/ame/Projects/Mac/../../src/Consumers/Imports/AvchdVideoImpConsumer.cpp, line:1031
Exception:
@ Thu Dec 1 21:12:39 2011
• Exception: DISK_DIR_NOT_FOUND, filename:00002.MTS
Exception:
@ Thu Dec 1 21:43:52 2011
• Exception: DISK_DIR_NOT_FOUND, filename:00003.MTS
Exception:
@ Thu Dec 1 22:15:52 2011
• Exception: DISK_DIR_NOT_FOUND, filename:00004.MTS
Exception caught in APlayer::Play - Exception: NEMFileWriter::ExecuteInternal TIMEOUT - NEMFileWriter has detected upstream pipe stall...
Exception:
@ Fri Dec 2 01:45:39 2011
• Exception: NEMFileWriter::ExecuteInternal TIMEOUT - NEMFileWriter has detected upstream pipe stall...
Exception:
@ Fri Dec 2 02:17:44 2011
• Exception: DISK_DIR_NOT_FOUND, filename:00006.MTS
 
The upstream pipe stalling most likely indicates the disk is not serving up the files fast enough. If these clips are on the timeline, are you seeing spans of blue lines in the timecode bar? Also, 5400 is quite slow as well for HD. Download a disk speed test application to see what it feels the true speed of the drive is after OS system overhead.

Michael
 
When using import, nothing happens but an error at the end and the clip doesn't get in the bin...

When using AMA it gets in my bin, no blue lines, but it won't playback...plays a few frames in either the left or right window and then has that first error I was posting about.

I am going to start by replacing my external, then either replace my internal or the whole system.... probably will get an SSD internal and wait for Ivy or Haswell to get a new computer... I still have a year and 2 months of Applecare so I am not trying to get a new system unless I really need it....
 
Have you tried a transcode to DNXHD from the AMA link to the HDSLR files? What is the error at the end of import process? Is there enough room on the target drive of the import? What resolution are you importing to?

Michael
 
I just got it to import successfully via DNXHD45 using small short clips. Maybe my clip duration had something to do with the problem? Dont think it was a storage issue, I got plenty of space...

Still having that playback issue everyone else is having, but I think that one is just a software glitch. I see lots of high end systems reporting that error on many message forums...

Thanks for the help guys but I think this issue is resolved until that software patch comes along. If the patch comes out and I still have the error I will upgrade my internal to SSD as a stop gap measure until I buy a new system in the future...
 
Last edited:
USB2 is not enough for anything high end, period. Get a faster drive, use a faster connection (eSata, SAS USB3, thunderbolt) and see if the errors still remain. I doubt that editing in Premierer at 1/16th resolution with R3D-files is something you can work fluidly. Two cores is also not really optimal.

I cannot help but see that you are trying to make your system into something it's not. My backup editing machine is around your specs and I know I need to transcode to be able to edit, even though I can barely get playback at yellow/green with eSata connection.

If you are going to edit something and not just play it back, then transcode the files, there's no reason not to. Load all AMA's into a bin and transcode to DNxHD 36 or do it in Redcine, don't know how many files you have but just let the computer do it's thing and then you can edit with ease instead. I do this even on my high end system, you don't want to be set back by playback choppyness or other errors when editing, you don't.
 
I have a raid 0 firewire 8/esata 4tb drive out for replacement at the moment. I will have it back soon. The CS5 r3d stuff I did was on that drive and it worked fairly well natively with few dropped frames, it wasn't great though but it played back at least. The audio underrun errors I am having during playback in Avid are happening to lots of people with higher end systems and I am not fully convinced if its a software bug or my pathetic external HDD that I want to throw out my window. This drive I am using isn't even mine, I wouldn't own anything slower then firewire 8. Its my partners half cocked attempt at keeping me complacent while he tries to recover the data he lost when he broke my raid. Believe me I am not pleased to be using this external, but with the prices of HDD's where they are from the crisis I am not anxious to buy another drive when I will get my 4tb raid back shortly.

I am going to buy an internal SSD and use my raid when it comes in, I am sure my system will work more fluidly at that juncture, even if its only using DNxHD. The fact that so many high end systems are reporting audio underrun errors makes me think its a software bug related issue. Believe me I can't wait to get this USB2 drive out of my studio, everything I am doing is taking so long and I am furious that this data recovery is taking forever. I didn't even lose any data I needed, and I wanted to send this drive out 3 months ago but I was stuck dealing with insurance companies and this process has dragged out so long I am just really bummed out on the whole process. I just keep trying to wait on getting a new system because the new mac pros and ivy bridge is around the corner, and most of what I do is only HD work anyway. R3d stuff is more of a hobby for me at this point and a learning experience.

If I was going to buy another raid I would get a r6 thunderbolt or a usb3. At this point I feel compelled to get them, but not until the crisis is over. My raid will be back here before I multicam edit a gig on the 13th or I am going to really start getting annoyed
 
Last edited:
Back
Top