Canon 5D Mark IV ALL-I Files MisBehaving In VP18 New Laptop

Peter-Riding wrote on 9/14/2021, 4:52 AM

Hi, I recently added a laptop from the Dell UK Outlet. Since you ask - it was classified as "scratch and dent" but I cannot see any issues like that on it at all :- ) It was just £1100 including tax. It is an Alienware M15 Ryzen Edition R5. AMD Ryzen 7 5800H 8 core up to 4.40GHz 20MB cache 45W. 16GB (2X8GB) Up to 3200MHz DDR4 SoDIMM Non-ECC. 1TB PCIe M.2 NVMe Class 40 Solid State Drive. NVIDIA GeForce RTX 3060 6GB GDDR6 (n.b. not the Ti and not the 12GB).It renders like grease lightning compared to my ancient desktop whose GPU Vegas has long since stopped supporting.

The problem I have is that Canon 5D-IV MOV files at 1920x1080p 25fps specifically in the ALL-I mode do not play properly on this laptop. Video and audio play for a few seconds and then the video goes black but the audio stays fine. This problem does not occur if in the IPB mode nor in the 4k MJPG mode. The codec in the ALL-I mode is so4compoundplug.dll The codec in the IPB mode is compoundplug.dll The codec in the 4k mode is qt7plug.dll

The ALL-I files play fine on my old desktop as do the other codecs (4k being very slow obviously). All the codecs are identical.

I checked the Preferences to ensure that in Deprecated Features I ticked Enable Quicktime Plugin and also tried Allow Legacy GPU Rendering. I have a registered copy of Quicktime and I checked I can play these ALL-I files direct in Quicktime.

I uninstalled VP18 using the standard Windows 10 method then reinstalled it. I did the Export - Import facility now in Vegas and the Preferences etc on the new laptop are identical those on the old desktop. Great addition by Magix as previously I had to copy and paste various AppData files and also Export - Import using Vegasaur!

I have tried the APP-I files on the laptop both with and without the GPU running. No good. I am using the latest Nvidia Studio driver 471.68

I've read up on various threads including Nick Hope's extensive info thread:
https://www.vegascreativesoftware.info/us/forum/faq-how-to-convert-mov-video-e-g-iphone-to-mp4-for-vegas-pro--106154/

Any suggestions please? I really don't want to have to either switch from ALL-I to IPB or transcode the ALL-I files before I can edit on the laptop. Is it perhaps a known bug? Has it been addressed in VP19?

Thanks.

Comments

Reyfox wrote on 9/14/2021, 6:02 AM

How about a sample file to download and try?

RogerS wrote on 9/14/2021, 7:20 AM

It's probably a bug with NVIDIA decoding or with Radeon graphics. Which is enabled for decoding in file i/o?

I'd start with updating the Radeon one: https://www.amd.com/en/support/apu/amd-ryzen-processors/amd-ryzen-7-mobile-processors-radeon-graphics/amd-ryzen-7-5800h

MediaInfo for your file would also be helpful: https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

A sample (a few seconds of anything via Google Drive, Box, Dropbox, etc.) would also help.

Peter-Riding wrote on 9/14/2021, 9:18 AM

Thanks. Here are links via Google Drive for a file, a PDF showing the Media Info and a PDF showing the Vegas Properties:

MOV file link 414A7079
https://drive.google.com/file/d/18cd99Q21lv7CdjfvNAW5E216HQU02CO2/view?usp=sharing

PDF file link media info
https://drive.google.com/file/d/1CJvxxvrHhq8akIwTj4nG2U4WCJx1ijqY/view?usp=sharing

PDF file link vegas properties
https://drive.google.com/file/d/1hfQV340HlBn6ovLud7_yLcG_ZTu8EKqO/view?usp=sharing

The MOV file is 300mb and is 27 seconds long. Shorter files are not good examples as sometimes the video element stays showing. Longer ones do show the issue. I was about to stabilise this file with Mercalli when I found there is a fly buzzing around in the foreground. Drat!

First I updated the Radeon as suggested by Roger. Thanks. I installed AMD's Autodetect and Install app and followed it through from there. I think I recall the update was dated 13th September 2021 so I was hopeful. But it did not make a difference. I've also rechecked the Nvidia Studio driver and that remains the latest at 471.68

One thing I've now noticed from the Vegas Properties dialogue boxes: The codec via the laptop is so4compoundplug.dll whereas the codec via the desktop is just the straight compoundplug.dll Both these folders in the laptop and the desktop have both folder available so fingers crossed it may just mean to somehow get the laptop to use the straight compoundplug.dll codec rather than the so4compoundplug.dll codec Yikes!

j-v wrote on 9/14/2021, 10:09 AM

@Peter-Riding Thanks for the sourcefile that gave you problems.
With me on laptop from signature no problem at all with my normal settings as you can see in this video.

P.S.

I made the video in Version 19 latest build but the same is hapening in VP18 latest build with the same options

Peter-Riding wrote on 9/14/2021, 10:27 AM

@Peter-Riding Thanks for the sourcefile that gave you problems.
With me on laptop from signature no problem at all with my normal settings as you can see in this video.

I've just changed my Dynamic Ram Preview to 808 as with yours, as my max is 14696 and comparable to yours at 16168. But no good.

Which codec are you getting when checked via the Properties dialogue box in Project Media > Properties > General? Is it so4compoundplug.dll or the straight compoundplug.dll? Thanks. Perhaps there is a simple method to switch the dialogue to the latter by default - but maybe that itself will have downsides.

j-v wrote on 9/14/2021, 11:17 AM

Which codec are you getting when checked via the Properties dialogue box in Project Media > Properties > General?

It is always the newer so4compoundplug no matter which option I change.

Reyfox wrote on 9/14/2021, 11:21 AM

I just tried the file out on my computer (signature below), and it played back just fine. Dynamic RAM is default 200.

john_dennis wrote on 9/14/2021, 11:26 AM

Working on my Dell Inspiron laptop.

Streams
  Video: 00:00:27.040, 25.000 fps progressive, 1920x1080x32, AVC
  Audio: 00:00:27.040, 48,000 Hz, Stereo, PCM

Summary
  [TCFM]: 9

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: so4compoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 18.0\FileIO Plug-Ins\so4compoundplug
  Format: AVC
  Version: Version 1.0 (Build 8532)
  Company: MAGIX Computer Products Intl. Co.

SYSINFO Display

Name    AMD Radeon R7 M460
PNP Device ID    PCI\VEN_1002&DEV_6900&SUBSYS_08111028&REV_C1\4&2BBAC179&0&00E0
Adapter Type    AMD Radeon Graphics Processor (0x6900), Advanced Micro Devices, Inc. compatible
Adapter Description    AMD Radeon R7 M460
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\u0366334.inf_amd64_f45fcc46e8aaf149\B365859\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0366334.inf_amd64_f45fcc46e8aaf149\B365859\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0366334.inf_amd64_f45fcc46e8aaf149\B365859\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0366334.inf_amd64_f45fcc46e8aaf149\B365859\amdxc64.dll
Driver Version    27.20.14540.4003
INF File    oem1.inf (ati2mtag_Topaz section)
Color Planes    Not Available
Color Table Entries    Not Available
Resolution    Not Available
Bits/Pixel    Not Available
Memory Address    0xC0000000-0xCFFFFFFF
Memory Address    0xD0000000-0xD01FFFFF
I/O Port    0x0000EF00-0x0000EFFF
Memory Address    0xD0200000-0xD023FFFF
IRQ Channel    IRQ 4294967271
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\U0366334.INF_AMD64_F45FCC46E8AAF149\B365859\AMDKMDAG.SYS (27.20.14540.4003, 75.45 MB (79,113,440 bytes), 4/19/2021 9:17 AM)
    
Name    Intel(R) UHD Graphics 620
PNP Device ID    PCI\VEN_8086&DEV_5917&SUBSYS_08111028&REV_07\3&11583659&0&10
Adapter Type    Intel(R) UHD Graphics Family, Intel Corporation compatible
Adapter Description    Intel(R) UHD Graphics 620
Adapter RAM    1.00 GB (1,073,741,824 bytes)
Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2fe24960ae166144\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2fe24960ae166144\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2fe24960ae166144\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2fe24960ae166144\igd12umd64.dll
Driver Version    30.0.100.9805
INF File    oem52.inf (iKBLD_w10_DS section)
Color Planes    Not Available
Color Table Entries    4294967296
Resolution    1920 x 1080 x 60 hertz
Bits/Pixel    32
Memory Address    0xD1000000-0xD1FFFFFF
Memory Address    0xB0000000-0xBFFFFFFF
I/O Port    0x0000F000-0x0000F03F
IRQ Channel    IRQ 4294967272
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_2FE24960AE166144\IGDKMD64.SYS (30.0.100.9805, 28.34 MB (29,715,104 bytes), 7/29/2021 12:59 PM)

Richvideo wrote on 9/14/2021, 12:57 PM

I am running Vegas 19 with the new update and I am seeing the same issue as Peter is seeing, the video goes black. My System is a Ryzen 3900 with 32 GB ram and an RTX 2080 Super Card. I have the most recent studio driver installed.

EDIT: I tried it using the Legacy AVC decoding and the video plays fine once I make that switch

Musicvid wrote on 9/14/2021, 2:52 PM

Working on my lowly i5 and previewing full frame rate at Best/Full.

Just for fun, I leveled it for 8 bit, then saw the opportunity to add "Post Auto-Exposure" by animating the Output Gain. See what you think (look for the gradual 1/2 stop boost midway through).

RogerS wrote on 9/14/2021, 8:19 PM

Legacy AVC decoding = compoundplug.
Not legacy = so4compound

You can change this on the file io tab if you need to for problem footage.

My guess is a bug with the NVIDIA decoder. You can also try changing the default decoder in file i/o to AMD Radeon of it's a choice and see if it works any better.

Those of us with Intel CPUs and iGPUs for decoding seem to be able to open it fine.

Former user wrote on 9/15/2021, 3:24 AM

Confirmed, The vegas hardware decoder bug. At this point, it makes you wonder why they don't just replace it. It can't be assumed people are using an intel CPU, further, it can't be assumed the intel CPU has an IGPU, but what you could assume is that a AMD or Nvidia GPU is in use, and they don't decode this file

Peter-Riding wrote on 9/15/2021, 4:22 AM

Hi, thanks very much to everyone for your efforts. I have now emailed Magix at support@magix.net I did this directly as I found the Magix site too well hidden to find an appropriate contact page :- ( Hopefully they will reply with a solution shortly - they have replied quickly and efficiently on previous occasions rather than in their "2 to 4 days" description so fingers crossed.

My CPU's have always been Intel. My old desktop has an Nvidia GPU but that is also old and not supported by Magix any more anyway. My new Alienware laptop is of course the AMD Ryzen 7 5800H with an Nvidia 3060 GPU. I see that member Richvideo is using a Ryzen 3900 with a RTX 2080. I tried both with and without the Legacy AVC Decoding options and on my laptop it did not make any difference - it used the codec so4compoundplug.dll each time. I also tried with the old desktop and without legacy decoding and on each occasion it used the straight compoundplug.dll

Musicvid: thanks for having a play with the file. It looks good but from my photographer eye the white balance and the contrast are a little off compared to what it looked like in real life on the day - which was very bright sun streaming into the large windows plus conflicting interior lighting. The photo file wasn't really doable accurately either but my client base tend to be happier with what looks good rather than what looks accurate anyway.

This new thread from this morning by Marinus-Vesseur may be referring to a similar issue:
https://www.vegascreativesoftware.info/us/forum/so4-compound-reader-causes-vegas-pro-19-to-freeze--131720/

Peter-Riding wrote on 9/15/2021, 4:40 AM

I am seriously angry now. My email has bounced back from Magix with the message "For further information on how to open a ticket with Magix support please check here www.magix.info

But there is no icon for Vegas Pro!!!

https://www.magix.info/us/support/

I just go round in circles.

Can anyone provide a link to the actual support page in which I can describe the issue.

Otherwise why don't I simply forget about paying to upgrade for a VP19 upgrade and pay a little more for Da Vinci instead :- (

Former user wrote on 9/15/2021, 4:49 AM

My new Alienware laptop is of course the AMD Ryzen 7 5800H with an Nvidia 3060 GPU. I see that member Richvideo is using a Ryzen 3900 with a RTX 2080. I tried both with and without the Legacy AVC Decoding options and on my laptop it did not make any difference - it used the codec so4compoundplug.dll each time. I also tried with the old desktop and without legacy decoding and on each occasion it used the straight compoundplug.dll

The other option is to untick legacy so that Vegas uses so4 but then tell it not to use the GPU decoder

RogerS wrote on 9/15/2021, 4:58 AM

I am seriously angry now. My email has bounced back from Magix with the message "For further information on how to open a ticket with Magix support please check here www.magix.info

But there is no icon for Vegas Pro!!!

https://www.magix.info/us/support/

I just go round in circles.

Can anyone provide a link to the actual support page in which I can describe the issue.

Otherwise why don't I simply forget about paying to upgrade for a VP19 upgrade and pay a little more for Da Vinci instead :- (

Don't get angry when you're the one in error. Support from Vegas Creative Software (the Vegas "brand" operated under Magix but semi-independently) is here, literally at the top of this forum page under "support." Magix support is not for Vegas.

https://www.vegascreativesoftware.info/us/support/

Click "ask support" , technical problem, Vegas Pro, search for something (enter anything), then scroll down and 'send a support request." That's it!

Peter-Riding wrote on 9/15/2021, 6:11 AM

Todd-B thanks very much, that did the trick :- )

I ensured that Enable Legacy AVC Decoding and Enable Legacy HEVC Decoding were not ticked and that Hardware Decoder To Use were off. The files continued to use the codec so4compoundplug.dll

I then did a render to MP4 from an 18 minute file to ensure there was nothing naughty going on with the Nvidia GPU and that was fine. Task Manager > Performance showed the CPU at close to 100% and the Nvidia GPU at 100%. The AMD GPU also showed a little usage. The render ran at just under real time compared to my older PC which needs around 4x real time.

RogerS, thanks for the link. I had already googled Vegas Pro Support and that took me to a page similar to yours but then on clicking support it took me to Magix. Hence my frustration. And now its giving me emails offering Magix Video Pro X even though I did not do anything other than be already signed into Magix. I have exchanged messages with Magix on just two occasions - 26th Oct 2018 and 24th March 2021 - and on both occasions it was not convoluted like this. Why Magix does not have an appropriate icon for Vegas Pro support on the Magix site is beyond me.

I downloaded and tested DaVinci and had no problems at all with running my files.

RogerS wrote on 9/15/2021, 7:26 AM

Similar is not the same- you're on the wrong site! Contact Vegas Creative Software using the link above.

Reyfox wrote on 9/15/2021, 7:39 AM

Yeah... while you can send support a ticket, you jump through a few hoops before you get to be able to actually write one. With this LINK I wrote in the space MP4 and was able to scroll down to the bottom of the page to actually write a support request.