VP16 Problem with Canon EOS R 4K MP4 ALL-I Video File

fr0sty wrote on 4/26/2019, 7:17 AM

Try updating your GPU drivers. If that fails, see if going into preferences and disabling timeline GPU acceleration helps (not ideal, but good for troubleshooting the cause). If that works, we know it is something with the GPU causing the problem. You can then try to disable so4compoundplug.dll to see if that is the cause... so4 is a new decoding plugin Vegas uses that has some issues with certain codecs, so sometimes disabling it and forcing Vegas to use another decoder works. To do this, hold shift while clicking on preferences, then go to the "internal" tab that pops up. Do a search for "so4" and change the second line's "true"'s to "false". Reboot Vegas, and see if that helps.

If all of the above fails, try converting the clip to another format, your cam should come with some conversion utilities.

terry54321 wrote on 4/26/2019, 1:58 PM

I tried the so4 2nd line FALSE suggestion but then could not open the MP4 files at all. Both Premiere CC and Resolve 15 can open these same files without resulting in intermittent black frames on the timeline. Hopefully, Magix will fix this problem with MP4 files from the Canon EOS R.

Kinvermark wrote on 4/27/2019, 2:12 PM

@terry54321

Might need fixing; but maybe not. How about try uploading a SMALL sample file for others to try. Also, post the MEDIAINFO listing for the file so we can look for anomalies.

terry54321 wrote on 4/28/2019, 5:10 PM

https://my.pcloud.com/publink/show?code=kZr86O7ZDvDg3njitG0lLM6CK4RYtkb0bLTV I just shot this clip you can download. I have not checked the entire clip but the second frame from the beginning is a black frame on my VP16 timeline but not on my Premiere Pro CC timeline.

terry54321 wrote on 4/28/2019, 5:16 PM

However, I closed VP16 and restarted it and put the clip on a new timeline and the second frame no longer shows up as a black frame but now there is another black frame a little further into the clip. So it looks like a random problem with VP16 reading the file and not something wrong with the clip.

Kinvermark wrote on 4/28/2019, 5:38 PM

@terry54321

Says it's over 3 GB - that's a little too big for me to download. Can you post something smaller - around 1/2 GB or less? Also suggest you google MEDIAINFO, install that utility and upload a report.

john_dennis wrote on 4/28/2019, 5:54 PM

I downloaded the file and tried it in Vegas 13, 14 and 15.

13 and 14 won't open it. From the Vegas Pro 15 timeline, I set the playback rate to 0.1 and haven't seen a black frame. I'm rendering using AMD VCE at the moment with some fX applied.

2019-04-29 1613

Finished render and shared on my Google drive. I had my way with your colors.

You find the pony...

Mediainfo

Kinvermark wrote on 4/28/2019, 5:56 PM

OK, I'llgive it a go in V16 - downloading now.

Former user wrote on 4/28/2019, 6:21 PM

Checked it out on my laptop, no black frames.

Your file is 57s;2f duration in VP16

I rendered out to an Nvenc file, same frame rate, UHD file, it was then 57s;1f duration, could be an Nvenc render issue. No black frames on rendered file.

Update, I had created a hevc file version without realising it.

I then made MC versions of cpu only and Nvenc, they both show the same duration as the original, also no black frames.

If I load any other of the files with the hevc file, the project duration reverts to the correct one of 57s,2f.

I think I can see why this is happening. When I zoom in at the end of the clips the hevc one is a small fraction of a frame shorter than the other 3 clips, i.e. original, cpu only and nvenc.

So when the hevc clip loads in by itself only, vp looks at the length, sees it doesn’t quite make 57s,2f and sets it to 57s,1f.

Kinvermark wrote on 4/28/2019, 6:21 PM

Problem confirmed in Vegas 16 build 361. Starts with a single black frame, then more appear the longer playback continues.

@terry54321

I suggest you open a support ticket ASAP and offer to send the developers a sample file so they can re-create the problem. That is the only way only will get fixed soon.

In the meanwhile you will need to convert it to an intermediate suitable for editing in Vegas.

Nigel wrote on 4/28/2019, 6:27 PM

Works fine on Vegas Pro 16.0.361 no problems, no black frames. Renders great.

On older quad core pc with nVidia 750ti gpu. GPU On in Vegas.

Allow legacy GPU On. Enable QSV Encoding ON.

terry54321 wrote on 4/28/2019, 7:00 PM

I sent in a report to Magix support. For those who did not see the black frames, there may only be a few isolated black frames in the entire clip so I wonder if you may have missed the problem or if this problem only occurs with certain GPUs. As you watch the clip play on the timeline there will just be an occasional single black frame that you will have to watch for and then go back and expand the timeline to find the one black frame.

Kinvermark wrote on 4/28/2019, 7:07 PM

FYI, my system specs are in my signature. Converting to Prores using Vegasaur Smart trim (FFMPEG) gets rid of black frames.

terry54321 wrote on 5/3/2019, 8:54 PM

I contacted Magix support and got the following response: "We did have some noted issues of black frames in our previous build. Some of these were addressed with the latest update. Let's have you update to build 424 and let us know the results..." I tried updating VP16 to the new build 424 but I still see single black frames in the Canon EOS R 4K All-I 29.97P MP4 video file.

Eagle Six wrote on 5/4/2019, 8:39 AM

Converting to Prores using Vegasaur Smart trim (FFMPEG) gets rid of black frames.

@Kinvermark not wanting to nick pick, but are you converting his Canon files to ProRes?

Kinvermark wrote on 5/4/2019, 10:44 AM

Yes. As a temporary workaround. Can't just render from Vegas as it doesn't read file correctly. So used ffmpeg via Vegasaur. Other solutions are possible.

Eagle Six wrote on 5/4/2019, 10:49 AM

Yes. As a temporary workaround. Can't just render from Vegas as it doesn't read file correctly. So used ffmpeg via Vegasaur. Other solutions are possible.

I wasn't questioning converting, rather that you can convert to ProRes using ffmpeg.

Gediminas wrote on 5/4/2019, 11:21 AM

I downloaded the file and tried it in Vegas 13, 14 and 15.

13 and 14 won't open it. From the Vegas Pro 15 timeline, I set the playback rate to 0.1 and haven't seen a black frame. I'm rendering using AMD VCE at the moment with some fX applied.

2019-04-29 1613

Finished render and shared on my Google drive. I had my way with your colors.

You find the pony...

Mediainfo

Colors of the flowers is so beautiful!

j-v wrote on 5/4/2019, 11:22 AM

I tried updating VP16 to the new build 424 but I still see single black frames in the Canon EOS R 4K All-I 29.97P MP4 video file.

I tried your file in VPro 16 latest update.
Because of the very high bitrate (471 Megabit/second) it is very difficult to play these AVC coded file. Why the hell that cam make for an advanced coded video such high bitrates while 40 Mb p/s should be enough.
I don't see any black frame but it is very difficult for my laptop (processor) to play this file fluently ( after a few seconds in begins to stutter in preview full after showing a 1 second black preview) so I have to switch to another preview than I'm used to.
Better is to make proxy files for this as the default for VPro 16 and heavy 4K sourcefiles and than it plays normal ( at preview) and good without any problem.

j-v wrote on 5/4/2019, 11:48 AM

I also rendered your file to a default Magix AVC 4K rendertemplate and than played it in my VPro 16 preview full without any problem.
MediaInfo of the rendered file

Screengrap of playing that rendered file in VPro full preview

Kinvermark wrote on 5/4/2019, 11:53 AM

I wasn't questioning converting, rather that you can convert to ProRes using ffmpeg.

Yes, bit unexpected. Caveat: I don't work with prores, and have not tested this workflow, but the file does open in various apps including Vegas, and reports itself as "prores."

The ffmpeg command line is from one of the Vegasaur presets:

Eagle Six wrote on 5/4/2019, 12:17 PM

I wasn't questioning converting, rather that you can convert to ProRes using ffmpeg.

Yes, bit unexpected. Caveat: I don't work with prores, and have not tested this workflow, but the file does open in various apps including Vegas, and reports itself as "prores."

The ffmpeg command line is from one of the Vegasaur presets:

Thank You @Kinvermark for the information. I was not aware that you could get full/compliant ProRes from ffmpeg as I thought it was a cost licensing issue to get the codec from Apple. I know Premier Pro recently added ProRes as a render option by licensing direct from Apple, and there are a couple other pay for converters, and of course a few others converters that say it is ProRes but is actually no compliant. So, just wanted to question and figure out how ffmpeg (open source) can afford the licensing! Maybe Vegasaur is absorbing the cost.

Kinvermark wrote on 5/4/2019, 1:05 PM

Maybe Vegasaur is absorbing the cost.

Welcome! I very much doubt there is any money involved. I would guess this is an open source, reverse-engineered solution (like Magix Intermediate). Technical "compliance" versus legal trademarking are, of course two different issues, but I don't know why FFMPEG are allowed to call it "prores" except perhaps thier open sourse status, plus maybe jurisdiction, or just that the Apple Sherrifs haven't caught up with them yet. :)

Eagle Six wrote on 5/4/2019, 2:02 PM

@Kinvermark I would agree with that. I tried the command (for HQ 422) and as far as Mediainfo is concerned it is ProRes. I have also read that it appears some are using it, so if it ingest in FCPX without complaints that is good enough for me. I would like to hear from someone with a Mac and FCPX to confirm, but that is not likely here. I hesitated to question you, but glad I did, as you have provided the lead. Thank You for the information.