The following line is this cryptic message is: MPEGMapper::CalcTemporalOffset: Did not find first temporal sample.
Skipped update of PMR (Media Database)

Now, in context. I have sent this same clip to squeeze 3 times this afternoon. Same clip, same settings, minor changes to the sequence (typos in titles to be exact).

Now, after adding 4 closing slides it gives me this. What does it mean?

I have left the program and restarted, I have rebooted the computer. I have sacrificed a live chicken.

No results. And I have changed setting for the send. Nothing. And I have been unable to find any relevant information anywhere.

any suggestions or ideas will be greatly appreciated.

And anyone suggesting I call Avid and pay them money to support software I bought less than one month ago, well, there are surgeries to correct cranial-rectolitis.

Oh, and the next attempt caused the Media Composer to shut down entirely.

Nice work fellows. Here's a helpful suggestion; make it work BEFORE you raise the price again.

join the club we are all having trouble with this release i cant even do a video mix down of sd material without a sdwc error or a dv underrun it really blows

joined the club along time ago. im better off with 4 now.

Well, I found the answer, no thanks to anyone at Avid.

it seems if you import a still into program set to XDCam you can't export the final sequence with that graphic attached. It can't create a "long gop" for that still, so the export can't find the beginning of that still to finish the sequence. why would the software allow you to import a still that can't be exported?

Alas, another Avid failure. So much is so good, but the little details.................

Maybe if they actually cared about what their customers do for a living?

Documentation might be nice as well. A great product poorly served by its makers. 

I had the same problem but it was not related to slides or stills.  I had a sequence made up of a two-camera group interspersed with slides.  I found a couple of sections where two group clips were side by side.  This was because one XDCAM camera's SxS card filled up requiring me to create a second group clip to maintain continuity.  I found if I replaced the last segment in the first group with a video mixdown of itself, I did not get the error message.

Damned if I know why but my general troubleshooting principle is "When trouble goes, you never ask where"

TrainerDave:

I had the same problem but it was not related to slides or stills.  I had a sequence made up of a two-camera group interspersed with slides.  I found a couple of sections where two group clips were side by side.  This was because one XDCAM camera's SxS card filled up requiring me to create a second group clip to maintain continuity.  I found if I replaced the last segment in the first group with a video mixdown of itself, I did not get the error message.

Damned if I know why but my general troubleshooting principle is "When trouble goes, you never ask where"

Dave your problem sounds like Avid could not recalculate the GOP over the cut. I group clip a lot with XDCAM EX material and have never run into this - and yes I've had plenty of group clips where they are matchframed across cuts. .

The actual error message the OP refers to in his first post can be related to corrupt frames in the XDCam file.

parkerfilms:

Well, I found the answer, no thanks to anyone at Avid.

it seems if you import a still into program set to XDCam you can't export the final sequence with that graphic attached. It can't create a "long gop" for that still, so the export can't find the beginning of that still to finish the sequence. why would the software allow you to import a still that can't be exported?

Alas, another Avid failure. So much is so good, but the little details.................

Maybe if they actually cared about what their customers do for a living?

Documentation might be nice as well. A great product poorly served by its makers. 

There are standard workflows - if you break them you won't always find the issues that creates in the documentation. Avid's default selection when importing stills is DNxHD (for HD) so it sounds like you made a conscious decision to change that to XDCam which is a LongGOP format? I can't really say because you never really tell us what your exact workflow was.. It also sounds like you worked the problem out for yourself because you realised you did something that stopped the timeline from exporting and tracked it back from there. So you did something wrong, worked out what it was and then fixed it. Excellent. Sometimes you will find answers like that in the documentation, sometimes you won't. I guarantee you that is normal for all software, not just Avid.

Glad you figured out your problem but now it would really help other users if you explained your exact workflow and what exactly stopped the export. That way  the next user with this problem will find hte answer on an internet search.

For example - I was working on a (raster, framerate) project - my timeline was in x codec on a media drive / AMA linked. When I imported some stills in X codec and added them to my timeline I got hte following error message when I tried to Send to Sorenson - Importing the stills in DNxHD solved the issue.

BTW - the reason you had the problem is that Avid does not support QT ref export of LongGOP media. When you use the send to command in Avid you are sending the timeline via QTRef to Sorenson. You'll see that LongGOP message if you try to export any timeline with XDCam footage to a QT Ref file.

*** UPDATE ***

Project is 1080i/50 originated on Sony EX-1 cameras.  Material conslidated at XDCAM EX 35Mb/s

Two cameras synced together and "multicammed"

I was getting this error when I attempted to export a QuickTime Reference for Squeeze.  To cut a long story short, because the camera angles were so long (27min) when they were consolidated, TWO video files were created for the ONE master clip.  If I included the portion of that master clip where the first video file transitioned into the second, I would get the error.  If that transition was not included, the export was OK. 

The workaround was to create and subsequently overwrite a video mixdown from the point of that transition to the next shot (which was a graphic).  It seems that as long as that transition point from video file #1 to video file #2 was not included in the edit then all was well.

Hmmm...