Should work now. I just copied the email.

Fixed it.

Useful discussion of this format here: https://www.vegascreativesoftware.info/us/forum/uncompressed-vs-sony-yuv-vs-magic-yuv-the-shootout--113650/

It also appears to be on sale for $14 at the moment. I think I'll pick it up.

@Musicvid I moved our discussion over for the time being

@Musicvid wrote:

As I suspected, with version 2.3.0, I cannot encode 10 bit on my Vegas Pro 14, Are there any thoughts of extending the plugin compatibility backward to include the earlier Magix versions?

The codec installer only installs for VP17/18 currently. I don't know if the plugin binary interface changed or not between VP14 and VP17. If it didn't, it can work. If it did, it'll crash the program. For example, the plugin interface changed between VP17 and VP18, meaning the VP17 plugin doesn't work (will crash at some point) in VP18 and vice-versa.

I have a friend who still has VP14, I'll ask him to try it out for me and report back.

In the meantime, copy the following two files from the VP17 folder (by default at: "c:\Program Files\VEGAS\VEGAS Pro 17.0") to the VP14 folder (into same subfolder as it was in VP17):

magicyuvplug.x64.fio2007-config

FileIO Plug-Ins\magicyuvplug\magicyuvplug.dll

If it works, then we're happy.

@Musicvid wrote:

I believe @wwaag has made his extension available to all Magix Vegas Pro versions by way of a single common .dll. What relevance this might have to my question I of course do not know. Meanwhile, I will try your suggestion because I learn best from breaking stuff! Thanks again.

I need to create separate DLLs for VP18+ and VP17, the new 8-bit full range changes in VP18 affected the plugin interface.

@wwaag wrote:

Works in Magix versions 14-16 plus Sony 13. Didn't try V12.

Well, seems binary compatibility was retained. Needs full testing though, I doubt 10-bit+ will work, as there are stuffs that were only introduced with VP17 that I use internally.

@Musicvid wrote:

I was able to obtain those two files by creating a new folder in Program Files, Vegas Pro 17.0, and a FileIOPlugins folder inside that. I then reinstalled the Magic 2.3.0 trial, and copied the two files over to my VP14 folders.

Oh, you don't have VP17 installed, I didn't consider that. And it actually installed that way by creating the folder? Interesting. I look in the registry for vegas170.exe / vegas180.exe locations, and if it doesn't exist it shouldn't even install at all for that version....

Unfortunately, it did not work with 10 bit, but still rendered with 8 bit. Oh well, it was just wishful thinking on my part, so don't belabor yourself. Thanks again for a great product, and I'll follow the development progress.

As I suspected, VP14 doesn't have the internal pixel formats for 10-bit YUV exposed towards the plugin, that the plugin needs.

But perhaps 10-bit+ RGB might work, the internal format for that have long been existing in VP. Worth a try.

Hold the phone. It does work in V14-V16. I imported 10bit 422 footage, changed the project settings to 32bit full range and was able to render with the 10bit YUV 422 template without issue in all versions. I did not try V13.

Hold the phone. It does work in V14-V16. I imported 10bit 422 footage, changed the project settings to 32bit full range and was able to render with the 10bit YUV 422 template without issue in all versions. I did not try V13.

I tried a test rendering MagicYUV 10bit 4.2.2 and it failed to render. However, I can render 10 4.2.0 just fine.

In case any one thinking about using the 10 bit 4.2.0 as their intermediate for long form project. You better think again before you want to do this. I was testing a 3.5 minutes long footage 4K 30P, render out to 10 bit 4.2.0. The end result is massive 28gb.

@wwaag @MagicYUV

My goodness Wayne, it works! Rendering 10 bit 4:2:2 as we speak.

Setting the project to 32-bit float did the trick. Thanks to you both!

This makes me a convert. I can hold off on the 12-pack on my shopping list.

It looks like a slight change to the installer will make 2.3.0 compatible with all Magix Vegas Pro versions 14-18?

But I may keep the trial around a few more days. That psychedelic watermark is a hoot!

@Musicvid @wwaag

IMO 10-bit codecs are only meaningful above 8-bit project settings.

I just had a chance to try myself, and it fails for all 10-bit YUV variants in VP14. In every project setting (8/32v/32f).

Is there any reason to stick to older VP versions (like 14)? Why not upgrade to VP18?

@BruceUSA What VP version did you try in?

@BruceUSA What VP version did you try in?

VP18 B344

@BruceUSA And so 10-bit YUV 4:2:2 failed to render there? What was the error message (if any?) What source and what project settings were used (8bit legacy, full, 32bit video, full)?

@Musicvid @wwaag

1. IMO 10-bit codecs are only meaningful above 8-bit project settings.

2. I just had a chance to try myself, and it fails for all 10-bit YUV variants in VP14. In every project setting (8/32v/32f).

3. Is there any reason to stick to older VP versions (like 14)? Why not upgrade to VP18?

@MagicYUV

1. I agree absolutely. A number of controlled tests listed in my signature have debunked popular "alchemy through upsampling" theories that have unfortunately swamped the internet.

2. @wwaag's Happy Otter Scripts has a function called Import Assist that externally imports 10 bit YUV and other hostile source (GH5), and transcodes it to a number of Vegas-friendly formats -- among them Magic YUV! (A bit of circular thinking never hurt any low-budget editor in this business!)

3. One word -- Unemployment. Independent postproduction services are a guaranteed nonseller this year. So is teaching music. Fortunately, I have enough archival scanning projects lined up to keep the lights on this winter.

Anyway, thank you both! What a wonderful collaborative community we have, and despite the economy, has made me an anticipant buyer with both of you entrepreneurs, if at the expense of my beer budget. Having V14-18 now compatible with high-bit Magic kind of completes the picture for me, as I suspect it will for several other production types here.

@BruceUSA And so 10-bit YUV 4:2:2 failed to render there? What was the error message (if any?) What source and what project settings were used (8bit legacy, full, 32bit video, full)?

Project settings 32bit video full. See attach pic .

@MagicYUV

Here are a few screen grabs showing successful render in V14. First, media info of raw footage from Sony FS7.

Now project settings.

Now render settings.

And finally the rendered file. Note that it took roughly 2 minutes to render a 14 sec. file.

Why use V14? Some users don't want to pay for a new version since V14 meets their needs. Some prefer using V14 due to better stability. even though they have purchased later versions. As the developer of HOS, I have mostly used V14 in the past just to ensure compatibility will all versions.

I had so many stability issues with V14 I almost swore off VEGAS entirely. It wasn't until near the end of 15's life that I started to be able to enjoy using it in real production environments.