I just setup my new Sony A7siii and I noticed when I record in 4:2:2 10 bit, Sony Vegas 18 does not show the footage. I ONLY get a green screen. Is there a new codec I need to download? Has anyone else had this issue?
Not everyone has those files, so if you give here a link where we can download a small file you uploaded to dropbox or so, we can try or maybe find a way around?
Not everyone has those files, so if you give here a link where we can download a small file you uploaded to dropbox or so, we can try or maybe find a way around?
Here is a download link to a small file. Please feel free to download it and try it on your VEGAS 18. Thank you!
Thanks for the clip. With VP 18.334 it plays back here. Not well- <3fps in 32 bit video mode and barely better than that in 8-bit full. No GPU decoding is used. Update: if project is set to NTSC and this is added as slow motion it can play back in 8-bit mode at full 30fps @ preview/auto. Still no GPU decoding and it slams the CPU.
It says it uses Name: so4compoundplug.dll, so if you have the legacy AVC decoding box checked that's probably your problem- without so4 enabled, 10-bit footage will be a green screen.
General Complete name : Format : XAVC Codec ID : XAVC (XAVC/mp42/iso2) File size : 416 MiB Duration : 16 s 520 ms Overall bit rate mode : Variable Overall bit rate : 211 Mb/s Encoded date : UTC 2020-09-13 20:57:54 Tagged date : UTC 2020-09-13 20:57:54
Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High 4:2:2@L5.2 Format settings : CABAC / 2 Ref Frames Format settings, CABAC : Yes Format settings, Reference fra : 2 frames Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 16 s 517 ms Bit rate mode : Variable Bit rate : 200 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 59.940 (60000/1001) FPS Color space : YUV Chroma subsampling : 4:2:2 Bit depth : 10 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.402 Stream size : 395 MiB (95%) Encoded date : UTC 2020-09-13 20:57:54 Tagged date : UTC 2020-09-13 20:57:54 Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Codec configuration box : avcC
Audio ID : 2 Format : PCM Format settings : Big / Signed Codec ID : twos Duration : 16 s 520 ms Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 3.02 MiB (1%) Encoded date : UTC 2020-09-13 20:57:54 Tagged date : UTC 2020-09-13 20:57:54
Great news! First off, thank you for everyone who actually put a comment on here to try and help the situation...thank you! Secondly, Magix must have jumped on this issue quick because about 10 minutes ago I tried to run the footage again in Vegas 18 and it automatically downloaded a "codec update". The 10 bit footage plays like butter now! Thank you all for the support!
I don't think Magix did an update. It's just when you selected the right decoder and loaded the footage for the first time, it phoned home to activate the appropriate one. (I didn't see this message, presumably because I triggered it at some time in the past)
Does Magix 15 formerly known as Sony Vegas 15 support 10 bit? In particular sony and Lumix cameras. If so, can anyone tell me how to download a decoder update for 10 bit files on Sony Vegas 15?
Yes, green screen means that the so4compoundplug.dll decoder is disabled, and that is required to decode 10 bit video. VEGAS does support 10 bit (and higher) video.
Holy moly. I had disabled so4... in internal options. When switched to enabled, most files from my a7s3 works fine in VEGAS 17! I have stable 25fps with GPU at 10%.
Holy moly. I had disabled so4... in internal options. When switched to enabled, most files from my a7s3 works fine in VEGAS 17! I have stable 25fps with GPU at 10%.
Holy moly. I had disabled so4... in internal options. When switched to enabled, most files from my a7s3 works fine in VEGAS 17! I have stable 25fps with GPU at 10%.
This is why it annoys me when youtube videos suggest by default that people should disable so4 in order to increase performance... it usually doesn't, and actually removes features.
Mario, So4 is a new decoder they built into VEGAS to handle decoding HEVC and AVC files. It decodes faster, and enables 10+ bit decoding, but in the beginning when they first rolled it out, it had some bugs, so many disabled it.
This is why it annoys me when youtube videos suggest by default that people should disable so4 in order to increase performance... it usually doesn't, and actually removes features.
This is the core of my criticism of these Youtubers. They quickly put something online - but no more corrections when something changes in their statements. And forever this is on the internet and the users run into a dead end.
Holy moly. I had disabled so4... in internal options. When switched to enabled, most files from my a7s3 works fine in VEGAS 17! I have stable 25fps with GPU at 10%.
This is why it annoys me when youtube videos suggest by default that people should disable so4 in order to increase performance... it usually doesn't, and actually removes features.
Mario, So4 is a new decoder they built into VEGAS to handle decoding HEVC and AVC files. It decodes faster, and enables 10+ bit decoding, but in the beginning when they first rolled it out, it had some bugs, so many disabled it.
If I remember correctly, I had some problems with something, and this is reason why I disabled this. I'm pretty sure, that this reason could hit me again in last expected moment :)
Mario, So4 is a new decoder they built into VEGAS to handle decoding HEVC and AVC files. It decodes faster, and enables 10+ bit decoding, but in the beginning when they first rolled it out, it had some bugs, so many disabled it.
If I remember correctly, I had some problems with something, and this is reason why I disabled this. I'm pretty sure, that this reason could hit me again in last expected moment :)
You probably did, but if it was with earlier builds or versions of Vegas, the problem may have been resolved since then. I'd stay with the defaults until you have a specific reason to change them. Good luck.
I had the problem with early release of VP17. It was a crash happy piece of software for "me", where it would crash every 5 minutes. Disabling So4 stopped the crashes. After a few updates, all is well. And with VP18, it was never an issue.
Yes, agree, updates to Youtube videos might be nice, but maybe not practical? Maybe update the Description.