Magic YUV 10 Bit not supported

Musicvid wrote on 1/30/2023, 1:45 PM

Vegas 20 Build 326

10 bit project and source

Error:

Same project in 8 bit works.

@MagicYUV

Comments

wwaag wrote on 2/5/2023, 11:37 PM

Seems to work OK here. Rendered 10bit, 420, 422, and 444 including HDR and they all rendered without issue. What were your render settings?

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia 1050ti graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Wolfgang S. wrote on 2/5/2023, 11:41 PM

It is unlikely, that this codec is decoded in Vegas as 10bit anyway.

wwaag wrote on 2/5/2023, 11:49 PM

Imported back into Vegas, it shows 10 bit 444.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia 1050ti graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

RogerS wrote on 2/6/2023, 12:16 AM

It looks like the MagicYUV plug does handle high-bit. Here's 10-bit 4:2:2 (tested with VP 19). 

Folder: D:\My Documents\Dropbox\Videos
  Type: MagicYUV AVI
  Size: 4.83 GB (4,947,486,496 bytes)
  Created: Monday, February 6, 2023, 3:07:29 PM
  Modified: Monday, February 6, 2023, 3:08:05 PM
  Accessed: Monday, February 6, 2023, 3:10:14 PM
  Attributes: Archive

Streams
  Video: 00:00:05.739, 29.970 fps progressive, 7680x4320x20, MagicYUV 10-bit YUV 4:2:2
  Audio: 00:00:05.739, 48000 Hz, 16 Bit, Stereo, Uncompressed

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: magicyuvplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 19.0\FileIO Plug-Ins\magicyuvplug
  Format: MagicYUV
  Version: 1.0.0.0
  Company: INNOMAGIC Bt.

 

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.270

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

Grazie wrote on 2/6/2023, 2:00 AM

It is unlikely, that this codec is decoded in Vegas as 10bit anyway.

@Wolfgang S. - Why do you say this?

 

Imported back into Vegas, it shows 10 bit 444.


@wwaag - Thanks for clarifying.

 

RogerS wrote on 2/6/2023, 2:15 AM

I was able to import and render out a 10-bit MagicYUV video in 32-bit full mode here in VP 20.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.270

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

Wolfgang S. wrote on 2/6/2023, 2:49 AM

It is unlikely, that this codec is decoded in Vegas as 10bit anyway.

@Wolfgang S. - Why do you say this?

 

Imported back into Vegas, it shows 10 bit 444.


Unfortunately I know, that the implementation of the 10bit decoding required an native implementation in the past. That was true for the cineform code, but also ProRes. But if the OFX interface is still used for the decoding, you end up with 8bit onlyl.

So the information, that is shown in the media properties, is not a guarantee that this codec is decoded as 10 bit really.

Also, that you can import the codec and exprt it again does not proofe anything, Roger.

The best way to explore that is to take such an imported file in the histogram - and enlarge it. So we have identified that in the past, if it is decoded in 8bit or 10 bit really.

What I have not done is to expore that for this codec really. Simply, because I do not use this codec.

 

Grazie wrote on 2/6/2023, 2:57 AM

@Wolfgang S. - O…K….? Would you kindly take me through, step-by-step, the separation of the understanding of the two sets of processes?

Wolfgang S. wrote on 2/6/2023, 3:37 AM

@Grazie

the test approach was a simple one,

- use a 32bit floating point project

- bring in the test file

- apply the filter levels to the test file

- choose for the test dramatic settings. For example Input start 0,550 and output end 0,552

If you do that for a 10bit and a 8bit file, you will see a dramatic difference!

 

8bit file (from the GH4, recorded internaly)

 

10 bit file (from the EVA1, recorded also internaly but to 10bit)

 

Wolfgang S. wrote on 2/6/2023, 3:46 AM

An old thread, where we have explored such points in 2015, can be found here (but it is in German):

https://www.videotreffpunkt.com/videotreffpunkt/index.php?thread/17874-10-bit-uhd-prores-verarbeitung-in-vegas-wissenstand-1-2015/&pageNo=1

RogerS wrote on 2/6/2023, 3:55 AM

I see no reason to doubt that MagicYUV doesn't work as advertised, which is up to 14 bit depth in Vegas: https://www.magicyuv.com/

Original file is high-bit and then converted to MagicYUV 10 bit 422 in Vegas.

32-bit video levels (full seemed to have issues with the levels Fx)


8-bit video levels

Happy to be corrected if I'm missing something.

Last changed by RogerS on 2/6/2023, 3:56 AM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.270

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

Wolfgang S. wrote on 2/6/2023, 4:24 AM

If this codec has been implemented in the meantime as 10bit codec in Vegas too - great.

In your measuring approach I would tend to compare 8bit files with 10bit files - but since you manage the decoding here about the project settings, that should work too.

But that are the reasons why I use the measuring approach always, if possible. Simply, beause such measurements show us the technical truth.

Grazie wrote on 2/6/2023, 4:42 AM

@Wolfgang S. - So, to achieve closure, will you do the Math?

Wolfgang S. wrote on 2/6/2023, 4:46 AM

@Wolfgang S. - So, to achieve closure, will you do the Math?

Was the original question solved? Not sure about that.

Grazie wrote on 2/6/2023, 5:05 AM

I’m gone.

RogerS wrote on 2/6/2023, 7:49 AM

Did anyone manage to replicate the original render error? The file name says HDR, wonder if that's a clue as to settings.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.270

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

Wolfgang S. wrote on 2/6/2023, 8:08 AM

Since neither project settings, nor media settings, nor rendern settings were published, I think it is hard to repro those findings.

GJeffrey wrote on 5/7/2023, 6:57 PM

I am having the exact same issue as the OP both on VP18 and VP20.

Anyone knows how to solve it?

RogerS wrote on 5/7/2023, 8:24 PM

Can you provide the exact conditions that trigger an error? We need to be able to replicate it.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.270

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

GJeffrey wrote on 5/9/2023, 7:25 AM

@RogerS

To recreate my issue

1/ Render a prores422 file using vegas 20-403. Rendered file should be YUV422-10bits

2/ Import this file to a new project. Project settings 32 bits video level or full, same result

3/ Render using MagicYUV 422-10bits. Same error windows as the OP

It's a fresh MagicYUV install.

Rendering 8bits no issue

RogerS wrote on 5/9/2023, 8:03 AM

Interesting, thanks for the steps. I tried that on a ~30s file first creating a ProRes file and then rendering to MagicYUV in a 32-bit full (view transform off) project.

My render dialog box looks quite different:

I am using MagicYUV Ultimate 2.3.2

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.270

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

GJeffrey wrote on 5/9/2023, 8:34 AM

Thanks @RogerS

Your screenshot actually solve the problem.

I also have VP18 installed in my computer and notice that magicyuv option is available in the render window, option that i didn't have in VP20.

I then copy paste magicyuv folder from VP18/FILE IO PLUGINS to the same folder im VP20 and magicyuv.config from VP18 folder to VP20 folder.

Now magicyuv render option is available and works.

I was using Video for windows render option before.

RogerS wrote on 5/9/2023, 8:41 AM

Oh... I would never have figured that out. Glad it helped you!

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.270

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

john_dennis wrote on 5/9/2023, 9:06 AM

I just did a MagicYUV Ultimate installation on an image with only Vegas Pro 20 installed and I had no File I/O plugin in the Vegas 20 folder. I also had no message from the MagicYUV installer about the target installation folder.

My main system:
Motherboard: ASUS ProArt Z790-CREATOR WIFI
CPU: Intel Core i9-13900K - Core i9 13th Gen Raptor Lake 24-Core (8P+16E) P-core Base Frequency: 3.0 GHz E-core Base Frequency: 2.2 GHz LGA 1700 125W Intel UHD Graphics 770 Desktop Processor - BX8071513900K
GPU: Currently intel on-die video adapter
RAM: CORSAIR Vengeance 64GB (2 x 32GB) 288-Pin PC RAM DDR5 5600 (PC5 44800) Desktop Memory Model CMK64GX5M2B5600C40
Disk O/S & Programs: WD Black SN850 NVMe SSD WDS100T1X0E - SSD - 1 TB - PCIe 4.0 x4 (NVMe)
Disk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drives
Disk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642
Case: LIAN LI PC-90 Black Aluminum ATX Full Tower Case
CPU cooling: CORSAIR - iCUE H115i RGB PRO XT 280mm Radiator CPU Liquid Cooling System
Power supply: SeaSonic SS-750KM3 750W 80 PLUS GOLD Certified Full Modular Active PFC Power Supply
Drive Bay: Kingwin KF-256-BK 2.5" and 3.5" Trayless Hot Swap Rack with USB 3
Sound card: Realtek S1220A on motherboard. Recording done on another system.
Primary Monitor: ASUS ProArt 31.5" 1440p HDR10 Monitor PA328QV
O/S: Windows 10 Pro 10.0.19045 Build 19045
Camera: Sony RX10 Model IV

https://www.youtube.com/user/thedennischannel