Hosting AIR Transfuser 2: getting false "missing file" errors
Posted: Thu Apr 11, 2019 10:20 pm
I just bumped into a can of worms called AIR Transfuser 2.
Looks like Reason and Voltage Modular belong to the group of DAWs causing it to not work properly, at least in Windows 10.
I ended up commenting about it here:
https://twitter.com/Koshdukai/status/11 ... 6991926272
Works fine under Ableton Live 10, Cakewalk and savihost
but looks like something is off when hosted by R10 or VM which causes it to "not see" its library *.big files when its own factory presets (also inside those *.big zip'ish files) reference them (using a relative path through an internal $Transfuser Content variable).
So it can access its library for some files and not for others (mostly audio ones)
Not sure if Cherry Audio can understand what's happening... could it be something as simple as a \ vs / issue in the path ? I've noticed how AIR internally uses / for folder separator instead of \ on Windows.
Not sure if the VST access the file system through the DAW or directly. If it's through the DAW, then it might be something related with the file path parsing ?!
Looks like Reason and Voltage Modular belong to the group of DAWs causing it to not work properly, at least in Windows 10.
I ended up commenting about it here:
https://twitter.com/Koshdukai/status/11 ... 6991926272
Works fine under Ableton Live 10, Cakewalk and savihost
but looks like something is off when hosted by R10 or VM which causes it to "not see" its library *.big files when its own factory presets (also inside those *.big zip'ish files) reference them (using a relative path through an internal $Transfuser Content variable).
So it can access its library for some files and not for others (mostly audio ones)
Not sure if Cherry Audio can understand what's happening... could it be something as simple as a \ vs / issue in the path ? I've noticed how AIR internally uses / for folder separator instead of \ on Windows.
Not sure if the VST access the file system through the DAW or directly. If it's through the DAW, then it might be something related with the file path parsing ?!