IGNITE PRO 4.1 for VP17 released

AVsupport wrote on 8/24/2019, 5:48 PM

FXHome seemingly have released an update to fix the compatibility 'issues' with VP17.

This can be had as an upgrade if you have -like me- a previous version for $ 129.40.

Impatient but still undecided I shall observe if Magix can come up with a meaningful update strategy for Hitfilm Pro an Ignite owners that are already on VP17.

Last changed by AVsupport

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.

Comments

Dexcon wrote on 8/24/2019, 6:53 PM

This can be had as an upgrade if you have -like me- a previous version for $ 129.40.

I have a previous version of Ignite and currently have Ignite as part of my current active HitFilm Pro subscription (even though FXHome stress that it is not a subscription), yet my upgrade offer to Ignite 4.1 is $159,20. That works out to be nearly $250 AUD (including the 3% credit card int'l xfer fee). FXHome say they only use USD, GBP and Euro, but it doesn't look like there is any way to select GBP instead of USD, important to me because the exchange rate to AUD from GBP is much better than the USD/AUD exchange rate.

I think that if I need to use an Ignite FX - which admittedly isn't all that often - I'll round trip through HitFilm, VP16 or Resolve.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16 Edit, Vegas Pro 17 Edit, Vegas Pro 18, Vegas Pro 19 Edit, Vegas Pro 20 Edit, HitFilm Pro 2021.3, BCC 2023, Mocha Pro 2022.5.1, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 9, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 1TB M.2 PCIe NVMe SSD

D drive: 6TB WD 7200 rpm Black HDD 3.5"

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

AVsupport wrote on 8/24/2019, 7:01 PM

In the same boat @Dexcon ; wonder if it's possible to nest VP16 into VP17 projects and do the 'old' Ignite stuff there..? (yes I don't like the FXHome money-grab either...strictly speaking this is still a major OFX- Version 4 ..)

Last changed by AVsupport on 8/24/2019, 7:03 PM, changed a total of 1 times.

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.

Dexcon wrote on 8/24/2019, 7:22 PM

@AVsupport

nest VP16 into VP17 projects and do the 'old' Ignite stuff there..?

A great suggestion. I just tried it - a few video events in VP16 with a random different Ignite FX on each event and then created a veg project. On importing the veg project into VP17, the dreaded plug-in warning window popped up saying that none of the Ignite FX were installed. Drat!

It looks like having to render in VP16 or other NLE is going to be necessary after all.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16 Edit, Vegas Pro 17 Edit, Vegas Pro 18, Vegas Pro 19 Edit, Vegas Pro 20 Edit, HitFilm Pro 2021.3, BCC 2023, Mocha Pro 2022.5.1, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 9, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 1TB M.2 PCIe NVMe SSD

D drive: 6TB WD 7200 rpm Black HDD 3.5"

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

AVsupport wrote on 8/24/2019, 8:12 PM

looks like having to render in VP16 or other NLE is going to be necessary after all.

perhaps some clever Magix coders could create a 'version hook' on the Nest to open with the appropriate Version in the first instance to provide additional backwards compatibility? @GaryRebholz might know?

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.