b2031 - Playback issue

I had something happen today that I have been unable to find a reason for. Currently, this is ONLY happening with USER content. This is the same content I have been running for approximately 6 months. No new content has been added...and this just started happening today!

When I play my content from the console (H3 running direct DMX from DP8000), it shows up as, what I'd like to describe, NTSC garbage. It's static, rgb squares, all completely jumbled. Now, here's the weird part. It stays this way through the first loop and then plays normally as soon as it crosses the loop point! I am using trigger opacity on all layers and only 1 layer is up at a time (basic verse, chorus, bridge layers).

When I first noticed it today, I was running 1.5.0. I went ahead and upgraded to 1.5.2 this afternoon, but it is still happening.

Like I mentioned above, it's ONLY user content that this is affecting. On the initial 1.5, all of this media scanned ok and is "black" in the CMA...no errors. The CMA is also showing the thumbnails and giving no errors.

Any ideas anyone????

After this weekend is done, I'll go ahead and try re-uploading my content. But it's just strange that once it loops, it's fine.
Parents
  • Ok...I figured it out....

    No, it's not a server issue per-se.

    When I run the list manually, I couldn't get it to fail. When I ran in conjunction with everything else going in, I could get it to fail. I started going back through everything and here's what I found.

    The clips I'm having issues with WILL NOT ALLOW ME TO SCRUB IN/OUT Frames. I get the "noise" screen that I posted above. Even though these clips report no errors on the CMA.

    The PREVIOUS list from where I was coming from had an IN frame set for the clip that it was running. Turns out that it was the same layer that I was starting on the second list. Normally, it just jumps to the new clip. However, because the IN Frame hadn't released yet (I had a delay on it), it tried to play from the current IN frame and caused the "noise" screen. This is why it only had issues until the first full loop. Once it looped through, there were no issues.

    This still doesn't answer why some of my clips can't scrub frames and get the noise, but it answer why this was happening. All of my content has been encoded the same, using the same profile on Episode (created from the HES site). So now, it looks like I have to jump over to Episode and see if it's creating the problem.

    Scott...I'm uploading a piece that's causing issues to you on the upload.highend.com to check and see if there's something I'm missing.
Reply
  • Ok...I figured it out....

    No, it's not a server issue per-se.

    When I run the list manually, I couldn't get it to fail. When I ran in conjunction with everything else going in, I could get it to fail. I started going back through everything and here's what I found.

    The clips I'm having issues with WILL NOT ALLOW ME TO SCRUB IN/OUT Frames. I get the "noise" screen that I posted above. Even though these clips report no errors on the CMA.

    The PREVIOUS list from where I was coming from had an IN frame set for the clip that it was running. Turns out that it was the same layer that I was starting on the second list. Normally, it just jumps to the new clip. However, because the IN Frame hadn't released yet (I had a delay on it), it tried to play from the current IN frame and caused the "noise" screen. This is why it only had issues until the first full loop. Once it looped through, there were no issues.

    This still doesn't answer why some of my clips can't scrub frames and get the noise, but it answer why this was happening. All of my content has been encoded the same, using the same profile on Episode (created from the HES site). So now, it looks like I have to jump over to Episode and see if it's creating the problem.

    Scott...I'm uploading a piece that's causing issues to you on the upload.highend.com to check and see if there's something I'm missing.
Children
No Data