Surprised not to find more information on this, but maybe I missed something. I found this AIR thread basically saying that Tracktion isn't supported and this KVR thread.
I tried both 32-bit and 64-bit versions of Tracktion and Xpand! 2.
By the way, thank you to the Tracktion team for making T5 free.
Any way to get Xpand! 2 working in Tracktion 5 without a wrapper? [SOLVED]
-
- KVRAF
- 1787 posts since 22 Feb, 2014
Last edited by telecharge on Tue Aug 02, 2016 3:58 pm, edited 1 time in total.
-
- KVRAF
- 1790 posts since 30 Dec, 2012
We believe this is a problem with Xpand! 2 not being able to be scanned from a separate process. We do this in Tracktion to avoid crashing the host if the plugin being scanned crashes.
We've added an option to scan in the main process in T7 which may enable you to scan Xpand! 2. You could try downloading the demo of this, scanning the plugins and then going back to T5.
Make sure you don't open any Projects or Edits in T7 though or you won't be able to open them in T5 again.
We've added an option to scan in the main process in T7 which may enable you to scan Xpand! 2. You could try downloading the demo of this, scanning the plugins and then going back to T5.
Make sure you don't open any Projects or Edits in T7 though or you won't be able to open them in T5 again.
-
- KVRAF
- 1690 posts since 13 Jan, 2014
Had the same problem with most of the AIR Instruments/effects. Strange thing is that it works in T 4, dont know if thats of any help for you, dont know if there is so much difference and you need the new T 5 functions. And I can confirm what dRowAudio said, it works (for me, win 7, 64 bit) in T 7.
-
- KVRAF
- 37533 posts since 14 Sep, 2002 from In teh net
I have all the Air plugins I have working in T7 on Mac, and they worked in T6 too. Maybe this is a Win issue though?
-
- KVRer
- 12 posts since 15 Feb, 2015
As previously mentioned, T6 also exhibits this problem on my Windows 10 (64-bit) system, however...
I discovered that I could get around this issue in T6 by merely launching T7 demo, scanning for plug-ins and quitting T7, then relaunching T6. T6 then shows the Xpand!2 plug-in as active and it appears to work properly. Perhaps this workaround might work for T5?
I discovered that I could get around this issue in T6 by merely launching T7 demo, scanning for plug-ins and quitting T7, then relaunching T6. T6 then shows the Xpand!2 plug-in as active and it appears to work properly. Perhaps this workaround might work for T5?
-
- KVRAF
- 2417 posts since 17 Jun, 2003
Should do, that's the exact same workaround drowaudio suggestedchandig wrote:As previously mentioned, T6 also exhibits this problem on my Windows 10 (64-bit) system, however...
I discovered that I could get around this issue in T6 by merely launching T7 demo, scanning for plug-ins and quitting T7, then relaunching T6. T6 then shows the Xpand!2 plug-in as active and it appears to work properly. Perhaps this workaround might work for T5?
"my gosh it's a friggin hardware"
-
- KVRAF
- Topic Starter
- 1787 posts since 22 Feb, 2014
Scanning with the T7 demo worked. Thanks all. 
For the record, T7 crashed when I unchecked "Use a separate process for plugin scanning," but scanned successfully once I rechecked it. It now lists and loads in T5.
A few other notes on my experience with T5 on Windows 10 64-bit...
I had to scan several times to get all the AIR plugins added. If T5 hangs on a plug-in while scanning it, click Cancel, go the bottom of the list, select the "failed" plug-in in red, click Scanning and Sorting >>> Remove selected plug-in from list, then scan again. This worked for all my "failed" plug-ins except Arturia's Analog Lab 2 64-bit VST2 version; however, the VST3 version scanned successfully.
For the record, T7 crashed when I unchecked "Use a separate process for plugin scanning," but scanned successfully once I rechecked it. It now lists and loads in T5.
A few other notes on my experience with T5 on Windows 10 64-bit...
I had to scan several times to get all the AIR plugins added. If T5 hangs on a plug-in while scanning it, click Cancel, go the bottom of the list, select the "failed" plug-in in red, click Scanning and Sorting >>> Remove selected plug-in from list, then scan again. This worked for all my "failed" plug-ins except Arturia's Analog Lab 2 64-bit VST2 version; however, the VST3 version scanned successfully.