Why is VEGAS Pro kicked out by FilmConvert Nitrate

rock-c wrote on 11/26/2020, 7:00 AM

I have used FilmConvert Pro 2.2 inside VEGAS Pro. It is great.

But when I wanted to download FilmConvert Nitrate 3.04 in https://www.filmconvert.com/download , it returned a old FilmConvert Pro 2.2 to me.

When I selected OFX resolve, It returned me a FilmConvert Nitrate 3.04.

Does Vegas Pro is kicked out? Isn't that a OFX commonly will support VEGAS Pro?

Comments

RogerS wrote on 11/26/2020, 7:08 AM

They talked about supporting Vegas a year ago but it never happened. Too small a market? It's too bad as I wanted to test it.

rock-c wrote on 11/26/2020, 7:12 AM

They talked about supporting Vegas a year ago but it never happened. Too small a market? It's too bad as I wanted to test it.


@RogerS I think its most codes are the same as Resolve Version, because they have the same OFX api. There is no reason to kick out VEGAS Pro. 😠

RogerS wrote on 11/26/2020, 7:54 AM

@rock-c Did you contact them and ask what happened and if Vegas support is coming?

rock-c wrote on 11/26/2020, 8:02 AM

@rock-c Did you contact them and ask what happened and if Vegas support is coming?


@RogerS No, I'm not fimilar with their website and contact method.

RogerS wrote on 11/26/2020, 8:24 AM

Here's the status from last year- someone used FB Messenger to contact them:

https://www.vegascreativesoftware.info/us/forum/fyi-filmconvert-nitrate--117942/

RogerS wrote on 11/26/2020, 10:31 PM

I think if someone wants the answer, instead of speculating, ask directly.

Me, I've moved on using Leeming LUT to correct camera colors to standard Rec 709, and then Graide Color Curve for an all-in-one grading solution.

Last changed by RogerS on 11/26/2020, 10:49 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.239

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

Steve_Rhoden wrote on 11/27/2020, 12:23 AM

Another serious Color correction and Grading juggernaut, its non other than 3DLut Creator.... It's what i use quite often and simply works beautifully with Vegas Pro!.

AVsupport wrote on 11/27/2020, 6:28 AM

have the same experience. time to file a ticket with filmconvert

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Steve_Rhoden wrote on 11/27/2020, 8:47 AM

Ticket? AVsupport, many have already loooong ago requested an official Vegas Pro support from them for Nitrate, and the response is always the same, "it's coming soon"...... Until now haven't seen it.

lan-mLMC wrote on 11/27/2020, 9:01 AM

1. VEGAS Pro only supports old OFX api standard.

2. VEGAS Pro doeesn't support FilmConvert Nitrate's on-screen controls.

If you really want FilmConvert Nitrate's support for VEGAS Pro, you may wait for next brand new VEGAS Pro with latest OFX api standard and on-screen controls. It will be a long time unless you guys urge developers to upgrade OFX system as soon as possible.

lenard wrote on 11/27/2020, 5:24 PM

1. VEGAS Pro only supports old OFX api standard.

2. VEGAS Pro doeesn't support FilmConvert Nitrate's on-screen controls.

If you really want FilmConvert Nitrate's support for VEGAS Pro, you may wait for next brand new VEGAS Pro with latest OFX api standard and on-screen controls. It will be a long time unless you guys urge developers to upgrade OFX system as soon as possible.

The 'new' ofx standard came out 6 years ago, give them time guys, they're a small team

"OfxParamPropParametricRange\0" ; pub const kOfxSonyVegasHostName : & 'static [ u8 ; 31usize ] = b"com.sonycreativesoftware.vegas\0"

That means current code is from the sony vegas days. A magix staff member has commented

To be fair that was only 3 1/2 years ago, and they're a small team, and there's a pandemic

rock-c wrote on 11/27/2020, 6:23 PM

@lenard It seems latest OFX and VST3 plugin system of VEGAS Pro haven't been upgraded for a long time. 😭😰

Why doesn't Magix combine Video Pro X and VEGAS Pro product line to one so as to put all sources into one new pro software. It will speed up the revolutionary upgrade of product, rather than two turtles crawled slowly. 😭😰

AVsupport wrote on 11/28/2020, 4:24 AM

https://en.wikipedia.org/wiki/OpenFX_(API)

UPDATE: Current version is 1.4 as of June 2017

 

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Reyfox wrote on 11/28/2020, 6:14 AM

@rock-c they both edit in different ways. How on earth Magix could combine the both is beyond me, and at the same time, make it appealing to their perspective users.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.3.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

AVsupport wrote on 11/29/2020, 10:44 PM

Response from Filmconvert Support:

Yes, it's an issue with Magix/Vegas and the way they implement the OFX standard. We don't have any plans to extend support for the foreseeable future, unfortunately.

And, when asked what would be necessary:

We don't know what's stopping the OFX plugin from working on Vegas, the Vegas developers will be able to find out if they look at the logs when they load the plugin.

So I guess we'd need to find a willing, able and hard working Magix crew member to make this move to the never ending ToDo list.. ;-)

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

lan-mLMC wrote on 11/29/2020, 11:10 PM

Therefore, they indeed tried to make Nitrate compatible with VEGAS Pro but they failed.

Let's be waiting for next brand new VEGAS Pro with latest OFX standdard support, full on-screen controls and new Event FX api which is able to access to other layers.

If that day comes, it will be a great benefit for all third-party plugins. You will be able to apply Mocha Pro to Event FX directly and it will read other logo layers in VEGAS timeline to attach them to tracking, Instead of having to apply Mocha to composite FX and read very long blank black-screen frames or plenty of irrelevant event in that track to make work complex, to make too much track space wasted; You will be able to adjust S_BlurMoCurve's rotate, position, zoom directly on preview screen controls; You will be able to apply BCC Primatte Studio to Event FX directly and it will directly read other layers as background to do further Spill Suppression; You will be able to directly adjust Ignite Pro Puppet Tool in preview window normally; You will be able to read layers in VEGAS timeline as BCC Particle 3D's color layer, map layer, texture layer; You will be able to directly apply BCC Title Studio to Event FX and read that layer as texture, read other layers as background layers ......

But that may not come soon, because current VEGAS team is rather small.

rock-c wrote on 11/29/2020, 11:40 PM

Response from Filmconvert Support:

Yes, it's an issue with Magix/Vegas and the way they implement the OFX standard. We don't have any plans to extend support for the foreseeable future, unfortunately.

And, when asked what would be necessary:

We don't know what's stopping the OFX plugin from working on Vegas, the Vegas developers will be able to find out if they look at the logs when they load the plugin.

So I guess we'd need to find a willing, able and hard working Magix crew member to make this move to the never ending ToDo list.. ;-)


@AVsupport That's a big Job's news. 😖😖