Thank you for taking the time to post your concerns to us, we promise to do better next time.Originally posted on 6 February 2018. We always do our very best to try to preemptively stop these issues getting to our users, sadly on this occasion we fell short and we must learn from it. What happened with Ignite and the release of Vegas 17 was a very unique event that is very unlikely (but not impossible) to happen again when / if Vegas Pro 18 comes out. No, Ignite is not host locked, I don't believe we have ever done something like that. Got this reply (for the record Thanks for your post & let me first of all say that I completely understand where your concerns are coming from. Or is Ignite 4.1 version locked to VP17 maximum and is by default designed not to accept a future host like VP18? In all seriousness: If I now upgrade to Ignite 4.1 (because 4.0 was no longer working with VP17) -Ĭan I expect Ignite 4.1 to be working with a future release VP18, under the circumstances that I could expect any generic OFX plugin to work, Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2įor what it's worth, I've put the question to the FXHome crew:.PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition).Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB.Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB.C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen.

Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB).APPS: VIDEO: VP 365 ( 20 - build 370), VP 19 post (latest build -648), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 15 HDpro XXL, Boris Continuum 2022.5, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Audio Clean Lab 3, Sound Forge Audio Studio 16, Sound Forge Pro 16, Spectral Layers Pro 9, Audacity, FOTO: Zoner, DXO, Luminar, Topaz.

Fxhome ignite express