HELP! Exporting MPEG2-DVDs causes flashing black and white bar on right side of screen

[opticalsounds]

I've been trying to publish some DVDs for a client, and recently when I do, I get an intermitant black bar (which sometimes flashes white). It seems to do it when I use lumetri color to correct it. Exporting h.264 mp4s seem to go great, it's only when I try to export an mpeg2-DVD file, and it does show up in the export window. I called Adobe, and they told me that it might be a problem with my CUDA cores etc, and to update my video card's drivers. That didn't work, so I just purchased a brand new GeForce 1060 Strix, thinking something could have been wrong physically with my old card, but I'm still getting the same issue. They change and move, and glitch around when I change any setting, but never get better or worse. If I "scale to fill" the usual black bars on the sides go away, but the flashing black and white bars just lay against the right side.
Any help would be GREATLY appreciated, as my clients are waiting!

[opticalsounds]

It does seem to only do so when I color my videos with "Lumetri Color"
I would gladly just use a fast color corrector, but I already have multiple, very large projects colored with Lumetri, and don't have much time to recolor them all without it

[R Neil Haugen]

Are you on a laptop? I'm wondering if the rig is using any onboard video/graphics chip ...

Neil

[opticalsounds]

nope, on a desktop
And if I go into project settings and turn off CUDA Acceleration to just use Mercury Playback Engine only, the glitching bars goes away, but it takes ten times longer to export my footage

[R Neil Haugen]

There's something screwy there in how your computer, the GPU, and PrPro are getting along ... or not. Typically this kind of thing is most often solved by either making sure you have the latest driver for the card by going to the manufacturer's site and checking numbers ... or at times, rolling back a driver or two.

Other than that ... hmmm ...

Neil

[opticalsounds]

That's what I figured, and why I just went and bought a brand new GPU, got the latest drivers for it, and still get the same result 😕

[Ann Bens]

Looking at your timeline I see some unusually format: .ts

What is the origin of these files.

[opticalsounds]

They're Transport Stream files, made from muxing MTS files together, for when you record long enough that your camera splits footage into multiple 4GB clips. Have been using that for years with no problem, but I tested that out by trying just a regular mp4 ripped from YouTube in the other screenshot

[Ann Bens]

Premiere does not support .ts files

Premiere supports spanned clips.

mts is mpeg4. .ts is mpeg2 so I am wondering if this is the correct way to go.

[SAFEHARBOR11]

"They're Transport Stream files, made from muxing MTS files together, for when you record long enough that your camera splits footage into multiple 4GB clips."

Not recommended or necessary. Create a New Folder on hard drive, then copy ALL CONTENTS of SD card to that folder. Include all folders from card. Then in Premiere, use Media Browser to Import and that will combine spanned clips into a single clip in Premiere. Not physically joining or creating new files, but the spanned clips APPEAR as a single clip in Premiere with no glitch or gaps to deal with. Edits as one big clip, seamlessly.

Thanks

Jeff Pulera

Safe Harbor Computers

[opticalsounds]

I can sure do that in the future, but I'm getting the same thing with avi, mp4, and any other format I try
Everything seems to work fine until I combine Lumetri Color and exporting as mpeg2-DVD
Adobe rep says it's my GPU even though I've tried different ones, bought new cards, updated drivers, etc

[Ann Bens]

Does the issue also occur when GPU set to software?

[opticalsounds]

Nope, only when using CUDA Acceleration. Though when it's only on software, it leaves rendering time at like 9 hours, then another ~7 hour exporting time, when it's less than a tenth that with CUDA utilized.

[SAFEHARBOR11]

No need to pre-render timeline, just export to MPEG-2 DVD straight away. Uncheck Max Render Quality when using GPU Acceleration, not needed and may be adding to export time. Depending on the Preview format being used, Use Previews may be reducing quality of export. Certainly adding an additional generation of compression. Use CBR encoding for short vids, no need to use 2-Pass VBR (if you are), just adds encoding time.

Lastly, using a fast, dedicated video drive may speed things up a bit rather than using the C: drive for everything.

Thanks

Jeff

[opticalsounds]

Well, I just spent all day removing Lumetri and re-color correcting my entire project with Fast Color Corrector and it's encoding in 30 minutes instead of 9 hours. I've never given much thought to Max Render Quality, have always just thrown it on because I film full 90 minute dance performances and like them to have the highest quality possible on both DVDs and mp4s, but I'll look into that and Use Previews, which I thought also improved image quality by using the pre-rendered videos.
Although I did find a workaround, I would like to figure out how to use Adobe's main coloring effect they're pushing instead of obsolete effects that I'm worried they may eventually phase out

Thanks for the advice

-Christopher

[Ann Bens]

If you preview codec is I frame only mpeg then the Preview files use in export will be of lower quality.

[R Neil Haugen]

A lot of the options don't actually do what ... from looking at the names ... you think they'd do. You only want to render using previews if you've manually set your previews to the same codec you're exporting to.

Max Render Quality, well, obviously you want max quality, right? Most of the time, this is of no help, as Jeff noted above, especially if you've got a decent GPU in your rig. PrPro will automatically do what it does best if left off.

Max Depth ... unless you're exporting something with color work in a high bit-depth codec, say 10/12 bit, this probably doesn't help either, and can slow exports.

Two-pass is also of little use for most exports.

Neil

[SAFEHARBOR11]

As a follow-up to great points by Neil, I think to just boil it down to one simple statement is that things are in a default configuration for a reason, meaning for most users, it will work fine "as is". The user would only start checking off boxes if there was a specific need, and more importantly, only if the user fully understands what each tick box really does. Often does more harm than good to just start checking a bunch of boxes.

Thanks

Jeff