Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

Avid MXF Clip error

CJ Roy

CJ Roy

REDuser Sponsor
Joined
Dec 28, 2006
Messages
1,008
Reaction score
0
Points
0
Age
48
Location
Portland
Website
www.cjroy.net
So in creating MXF's (175) & bins for editorial in RocketCine b.1735, I'm getting a strange and sporadic error on some of the clips.

"Audio:PMM_INSUFFICIENT_MEDIA()
Player version of frame duration is longer than actual
[5580] (5579)"

The error message pops up every time you double click on the clip. Now in the composer window you can scrub the clip, but it won't let you play it. Out of 212 clips this is happening on about 20-25 of them.

Any ideas?!?! We're dead in the water on the MXF workflow without a solution for this.

Thanks.

-CJ
 
that error is a corrupt clip i believe. try to unlink or delete those clips and re-transcode one of them that wasn't working and see if that works.

Also how many clips are in your AvidMediaFiles>MXF>1 folder. i believe there is a 2000 file limit or so.

Also could be corruption from RocketCine as well which is why i suggested re-transcoding 1 clip to test.
 
Can you try build 1740?
We improved some avid mxf specific things since 1735.
 
CJ Roy said:
Deanan- The render time for MXF's seems to be significantly slower on 1740. Any reason why?
Click to expand...

It shouldn't be.
send me the logs and i can have a look.
what format are you going from/to?
 
I'm seeing the same problem with some clips I just converted.

I've seen this problem before with P2 footage from a Firestore.

You can work around the problem, the 2 numbers (eg [5580] (5579)) represent the difference in length of the video and audio, trim the clip at the head or tail by this amount ( 1 frame ) drag out a subclip and it will play.

Hopefully between Avid and Red a fix can happen because you don't see the problem until you try to use the clip.
 
I'm actually just transcoding from regular RED Cine-X with no rocket. I am getting the same exact error. Thanks for the subclip work around. It still is annoying that every time I click the source side that error pops up. I can play it, though, if I trim a few frames with the subclip. However, I am hoping for a better fix. Is there something I can do in the transcoding process, or am I SOL until RED fixes the problem in Cine-X?
 
I have asked this question in two threads to no avail. I went on to the Avid user forums and found out that if you cut a few frames off of the source clip and create a subclip, then consolidate that subclip so it becomes a source clip, the problem goes away. However, I now find that my newly created source clip is out of sync by four to five frames. This would make sense since the original error is pretty much saying the audio or video portion of a clip is four frames short. I am guessing this is a RedCine-X problem, and I hope they fix it soon. I'm surprised not more avid users are chiming in about it.
 
Ralph Wong said:
I have asked this question in two threads to no avail. I went on to the Avid user forums and found out that if you cut a few frames off of the source clip and create a subclip, then consolidate that subclip so it becomes a source clip, the problem goes away. However, I now find that my newly created source clip is out of sync by four to five frames. This would make sense since the original error is pretty much saying the audio or video portion of a clip is four frames short. I am guessing this is a RedCine-X problem, and I hope they fix it soon. I'm surprised not more avid users are chiming in about it.
Click to expand...

We're getting a new Avid SDK in a few days that has some improvement to the audio handling.
 
That's great to hear. I understand Cine-X is still in its beta form, and I appreciate that RED continues to perfect the program. I really prefer Cine-X to any of the other programs crated so far and look forward to the finished product.
 
Ugh - same problem on all clips

Ugh - same problem on all clips

Deanan said:
We're getting a new Avid SDK in a few days that has some improvement to the audio handling.
Click to expand...

Trying to make 1080p23.976 DNxHD 115 with latest build 104 of Redcine-X.

Does Rocketcine-X fare any better? Does it handle build 30?

This is on Build 30 footage that they (yikes!) used on a big spot, so a liiiiiitle bit of pressure to get this figured out.
 
MikeCurtis said:
Trying to make 1080p23.976 DNxHD 115 with latest build 104 of Redcine-X.

Does Rocketcine-X fare any better? Does it handle build 30?

This is on Build 30 footage that they (yikes!) used on a big spot, so a liiiiiitle bit of pressure to get this figured out.
Click to expand...

Both support build 30 footage.
 
Any updates on this audio issue? I have a quick turn around project coming in March 23rd and I just want to have my ducks in a row, if at all possible. I was hoping to use Redcine-X on our Xserve to process the shoot over night, but if this audio issue is still present I guess I'll have to import the QT proxies as backup, or something.
 
Ralph Wong said:
I have asked this question in two threads to no avail. I went on to the Avid user forums and found out that if you cut a few frames off of the source clip and create a subclip, then consolidate that subclip so it becomes a source clip, the problem goes away. However, I now find that my newly created source clip is out of sync by four to five frames. This would make sense since the original error is pretty much saying the audio or video portion of a clip is four frames short. I am guessing this is a RedCine-X problem, and I hope they fix it soon. I'm surprised not more avid users are chiming in about it.
Click to expand...

Consider this chiming in. Same issues, same workaround. And it happens a lot, especially to clips at the beginning or end of a roll. And it's just as prone to Rocketcine-X as Redcine-X.
 
Last edited:
Scott Yarbrough said:
Consider this chiming in. Same issues, same workaround. And it happens a lot, especially to clips at the beginning or end of a roll. And it's just as prone to Rocketcine-X as Redcine-X.
Click to expand...

This was fixed in the later avid SDK we got. Try RCX 183 and see if you're still getting the same thing?
 
You must log in or register to reply here.
Back
Top