So, I just tested this on both 3.5.4 and 4.0.2 on a Mojo DX...not Nitris...and could not replicate the problem. Here's what I did in a 1080i 59.94 project:

1. Took a single pre-built sequence and cut it into a new sequence. I then cut a second sequence behind it and separated them by 1 min.

2. Auto nested sequence one into a 3D warp effect. Set Scaling to 50%

3. Moved sequence 1 up to V2

4. Added Graphic background (bright red still) on V1

5. Jumped into V2, added a video layer

6. Add title to V2 and use the Fade Effect button to fade it up and down for 30 frames.

7. Step out and play effect.

In both 3.5.4 (I did not apply the .11 patch) and 4.0.3, the effect played back normally.

Are you seeing it both in your client monitor and in your Avid S/R monitor the same way?

Yes,seeing this "bad effect"on both source and record monitors the same way.

Again,this is with DX Nitris,and this applies because we are dragging in and duplicating the sequence from Interplay.If I file-open-bin the same sequence from its original project (which one shouldnt do wihen running Interplay), I am able to duplicate and revise the same sequence,no problem. ONLY WHEN dragging the seq in from Interplay and duplicating-revising the sequence does this bug pop up.

Thanks very much for trying this out. BY the way,this workflow I described is our tagging workflow,and it is only regarding SD (MPEG 50) sequences. The OTHER problem with our longform outputting is with 1080i outputting.

I will test your console suggestion for THAT later today,if I get the chance.

Rob

Interesting. I did not have MPEG 50 material to try but I did try 30i SD and it worked fine there too.

I'm still not thinking that this is related to the DX boxes themselves. If it were, the problem would not appear in the S/R monitor, only the Client monitor and, since you can work around it using File/Open Bin, that tells me that the DX isn't causing the issue.

I'm going to forward this string to the workflow manager who handles your site just to make sure he knows what's going on and to see if he may have some ideas for us.

There was a bug with MPEG 50 with 3.5.1. It was fixed with 3.5.4 but this might be specific to this codec. As a test could you transcode to a different codec and see how it performs?

They are running 3.5.4.11 Bob but you are right. A lot of these issues seem to be pointing to codec problems.

Yea, I see that. I'm wondering if this is a different but somehow related bug.

Kind Avid folks:

I just tried the solution a few responses above:

Typing ToggleHWDecode in the console, which apparently disables the DNX encoder.

Same problem: 6 or so minutes into yet another 1080i output (different movie,different room), the output ceased once again ...

different message THIS time:

SWDecodeCvtr::ExecuteFrame()  CONSISTENCY CHECK FAILURE !?! : [<idNum>}

Nothing would enable me to continue:rebooting,re-enabling the encoder through the console,re-placeing the video in the sequence with its orig source once again, parking earlier in the sequence and outputting from that point,longer pre-roll.etc etc. Stuck again! My engineer Bernie is going to email Kelly to see if anything has come up since she and I last spoke.

Thanks again for any advice!

Rob

Thanks Rob. I forwarded that info on to the people in CS working on this and they should be in touch shortly.

Update:

After many reboots,the Avid allowed me to continue outputting my 1080i longform sequence,and it hasn’t stopped in 10 minutes!
What worked for the latest stopping point was:

I redigitized the short clip where the sequence stopped,and put the video back into the sequence. Then I was allowed to continue.
But this is a pain to workaround: should we have to stop outputting every time there’s a stop-error,and,when rebooting doesn’t work, redigitize the media so it can safely play down in the sequence? Etc etc.
What good then is digitizing the media in the first place?

There’s something obviously wrong with our 1080i and how the DX Nitris percieves it.

Rob