@alifftudm95, just only one DNxHR 444 10bit file crashing VP18?

and what's the duration of the clip you are dealing in your case? does the duration of the clip matters?

@alifftudm95

I had no luck with avid DNX files either. The obvious "standard" intermediate would be Prores, but DR doesn't export this on PC, and Vegas doesn't see Prores timecode anyway. Grass Valley HQX is the most solid choice; alternatively Cineform mostly works well, but occasionally has small issues. (See my other posts about cineform.)

Grass Valley HQX is the most solid choice

+1

Is this the one to download?

https://www.edius.net/hqx.html

I was able to install HQX from that link, export from Resolve (it's found under AVI, not MOV) and then import into Vegas.

Sample Media Info

General
Complete name                  : C:\Users\Roger\Desktop\crb.avi
Format                         : AVI
Format/Info                    : Audio Video Interleave
File size                      : 577 MiB
Duration                       : 1 min 11 s
Overall bit rate               : 68.2 Mb/s
TCOD                           : 36036000000

Video
ID                             : 0
Format                         : Canopus HQX
Codec ID                       : CHQX
Duration                       : 1 min 11 s
Bit rate                       : 68.1 Mb/s
Width                          : 1 920 pixels
Height                         : 1 080 pixels
Display aspect ratio           : 16:9
Frame rate                     : 23.976 (24000/1001) FPS
Bit depth                      : 8 bits
Bits/(Pixel*Frame)             : 1.371
Time code of first frame       : 01:00:00:00 / 01:00:00:00
Time code source               : Adobe tc_A / Adobe tc_O
Stream size                    : 577 MiB (100%)

I have no choice but to export in H264 codec which affect the true image quality of the colored footages.

That is not quite correct.

Grass Valley HQX works just fine in Vegas.

But my VEGAS crash when using this codec for some reason

@alifftudm95, just only one DNxHR 444 10bit file crashing VP18?

and what's the duration of the clip you are dealing in your case? does the duration of the clip matters?

in DR, you can batch render each individual clip base on the length of the cuts in the edit page, so in VEGAS, I can just simply drag & drop the graded clip on top of the original video (new track) and copy paste any effects on that I've applied on the original video (copy/paste attributes from original clip) onto graded clips.

@alifftudm95

I had no luck with avid DNX files either. The obvious "standard" intermediate would be Prores, but DR doesn't export this on PC, and Vegas doesn't see Prores timecode anyway. Grass Valley HQX is the most solid choice; alternatively Cineform mostly works well, but occasionally has small issues. (See my other posts about cineform.)

Funny enuf, GoPro cineform can import into VEGAS Effects, but not in VEGAS Pro. I tried to import the clip (gopro cineform) from Project Media, Explorer & even try to drag & drop the clip from folders but VEGAS Pro just dont see the video.

I have no choice but to export in H264 codec which affect the true image quality of the colored footages.

That is not quite correct.

Grass Valley HQX works just fine in Vegas.

But my VEGAS crash when using this codec for some reason

Do you have legacy AVC decoding checked? Maybe try to use Grassvalley with the default decoder. It seems to work here.

With Cineform and the like isn't the decoder for that 32-bit Quicktime so you have to enable that, but then have limits from the old architecture (# of clips)?

I hope Vegas provides proper decoding for DNxHR in the future.

@alifftudm95

Hi Aliff,

That is because FxHome wrote their own support for cineform in Hitfilm (Vegas fx) but Magix are still reliant upon the VFW .avi legacy codec installed by the old GoPro installers. I think you can still find this on the DrZen Vegas forum.

Recommendation: DO NOT USE THE .MOV version of anything not natively supported by Vegas - it will be either slow or crash.

@alifftudm95

Hi Aliff,

That is because FxHome wrote their own support for cineform in Hitfilm (Vegas fx) but Magix are still reliant upon the VFW .avi legacy codec installed by the old GoPro installers. I think you can still find this on the DrZen Vegas forum.

Recommendation: DO NOT USE THE .MOV version of anything not natively supported by Vegas - it will be either slow or crash.

Ah, no wonder. I really hope VEGAS update these codecs, almost all post house this type of codec/wrapper

DNxHR intermediates crash my system if I try to load too many at once so my work-around is just to work in smaller chunks if I know there is DNxHR involved... I contacted support & they said the same thing... Too many files of anything related to (obsolete) 32-bit QuickTime is going to cause issues & they have no way of updating QuickTime-related codecs (?)...

Weekly I use DNxHR to send intermediates to clients using FCP because we've had issues with FCP accepting other intermediates. Most already have AVID DNxHR codecs installed, so I'm not asking them to add another 3rd party codec they are not comfortable with. If I make things too cumbersome for them, they'll just find someone who is using FCP... I also have FCP on an older Mac Pro for the sole purpose of being able to send 100% compliant ProRes files vs. relying on Vegas' sketchy attempts to emulate ProRes... I stay in business by giving the customer what they want so I may have to do more & more in ProRes if Vegas doesn't stay current with support for ProRes RAW, etc..
 

DNxHR intermediates crash my system if I try to load too many at once so my work-around is just to work in smaller chunks if I know there is DNxHR involved... I contacted support & they said the same thing... Too many files of anything related to (obsolete) 32-bit QuickTime is going to cause issues & they have no way of updating QuickTime-related codecs (?)...

Weekly I use DNxHR to send intermediates to clients using FCP because we've had issues with FCP accepting other intermediates. Most already have AVID DNxHR codecs installed, so I'm not asking them to add another 3rd party codec they are not comfortable with. If I make things too cumbersome for them, they'll just find someone who is using FCP... I also have FCP on an older Mac Pro for the sole purpose of being able to send 100% compliant ProRes files vs. relying on Vegas' sketchy attempts to emulate ProRes... I stay in business by giving the customer what they want so I may have to do more & more in ProRes if Vegas doesn't stay current with support for ProRes RAW, etc..
 

I really hope VEGAS update their codecs, its kinda left behind from the industry standards. Almost all post house use ProRes & DNxHR in editing stage

After blotching the "X" release & then not providing quality Mac Pro updates for nearly a decade, Apple is back to throwing money at the latest FCP & Mac Pro updates to dominate the market (again)... You can count on APPLE not playing nicely with other NLEs, so Kudos to the Vegas team for announcing they will have FCP RAW support soon...

Yup. Let's hope the team add source timecode support to their Prores (raw and otherwise) as part of the implementation.

Native cineform support would be nice, but it has been yonks since I asked for this so I won't hold my breath. :)

Davinci users regularly complain about lack of Prores support on Windows - seems like the best option is to buy an Apple M1 mini for that job.

I considered Cineform is old by now... but do many users still using it?

My guess is not many. But the real point is that for intermediates you need broad support between programs. Apple Prores is proprietary - so some people object to that - but most likely is the best choice. Vegas needs to fully support it by implementing source timecode. If you have Prores, I don't think you need AVID DNX, except Davinci doesn't do Prores on Windows - but they probably should.

For Windows users, it would be most convenient if DaVinci added support for Magic YUV.

For Windows users, it would be most convenient if DaVinci added support for Magic YUV.

Totally agree with that. I saw comments from the developer about how with the SDK export-only is possible but it seems like Resolve would need to add support to read MagicYUV themselves.

But until that day, any thing Magix can do to ease Resolve-Vegas for graded files would be great.

I considered Cineform is old by now... but do many users still using it?

Still used in many post house in editing stage.

DNxHR, DNxHD, ProRes, Cineform used quite alot

DNxHR intermediates crash my system if I try to load too many at once so my work-around is just to work in smaller chunks if I know there is DNxHR involved... I contacted support & they said the same thing... Too many files of anything related to (obsolete) 32-bit QuickTime is going to cause issues & they have no way of updating QuickTime-related codecs (?)...

Weekly I use DNxHR to send intermediates to clients using FCP because we've had issues with FCP accepting other intermediates. Most already have AVID DNxHR codecs installed, so I'm not asking them to add another 3rd party codec they are not comfortable with. If I make things too cumbersome for them, they'll just find someone who is using FCP... I also have FCP on an older Mac Pro for the sole purpose of being able to send 100% compliant ProRes files vs. relying on Vegas' sketchy attempts to emulate ProRes... I stay in business by giving the customer what they want so I may have to do more & more in ProRes if Vegas doesn't stay current with support for ProRes RAW, etc..
 

I really hope VEGAS update their codecs, its kinda left behind from the industry standards. Almost all post house use ProRes & DNxHR in editing stage

The VEGAS team has made it well known that both ProRes and ProRes RAW support are coming, they've already got the license to do it and they're just getting the software stability end of it sorted now before release.

For Windows<-->Windows handoff, DNx, Cineform, ProRes, Animation, are all pretty much replaced by Magic YUV and UT, which are superior in accuracy and speed, if not always size.