In my tests I have 3 or more different synths on different tracks. So maybe there is something strange happening in Tracktion.
On the other hand I won't be surprised if there is still something wrong in the Voyager-mGUI duo. Unfortunately these combination errors, if one cannot reproduce it, is very difficult to fix ...
Anyhow, if a clear error pattern is found, then one might try to reproduce it in one of my mentioned hosts ...
Arguru Voyager - New Skin
-
- KVRAF
- 5524 posts since 5 May, 2007 from Mars Colony
Ok, I reopened a project I started new last night which had Voyager_GUI and a number of effects plug-ins, but no other VSTi's (Voyager was the only instrument, then I had some compressors, EQ's, Charseisis w/ Limeflavour GUI, and a reverb).
The exact same thing happened. Voyager wouldn't respond to any MIDI input. I then deleted it and resaved the project, then I opened a blank project to clear everything out. Then I reopened the first project and tried to reload Voyager_GUI and the system bogged down. Everything became extremely slow, but I was able to close Tracktion and avoid restarting the machine.
Interestingly, Tracktion showed the Voyager_GUI plug-in inserted on the track but the GUI itself did not appear, which leads me to believe it may be a graphics problem, but it's one I haven't seen before with any other plug-in. My graphics card is a GeForce 6800 GS and I'm on a single core Athlon 64 processor. Windows XP 32.
Update: I was able to successfully load Voyager_GUI into the same project mentioned above after closing and reopening Tracktion, so the problem appears to only be introduced when trying to load the plug-in while reopening a saved project.
Update 2: Ok, I have a more specific picture of what's going on. Basically, at least on my system, Voyager_GUI can only be loaded once after starting Tracktion 3---after that, this massive system slow-down problem occurs. I started Tracktion as stated above and was able to load Voyager_GUI into an existing project and it played fine. I then deleted it and saved the project under a new name, then tried to reload Voyager_GUI, and everything slowed to a crawl. I then got a pop-up from Tracktion saying "This plug-in is unresponsive". I was able to close the application, but, again, everything moved very slowly until Tracktion was closed, then the system went back to normal.
For some reason, reloading Voyager_GUI again after it has already been loaded one time before (not two instances, but loading it again after deleting it, even in a new project), seems to bog down the system to the point that it can't function and my guess is it's graphics related.
I'm going to try this again without the Limeflavour version of Charseisis in the project.
The exact same thing happened. Voyager wouldn't respond to any MIDI input. I then deleted it and resaved the project, then I opened a blank project to clear everything out. Then I reopened the first project and tried to reload Voyager_GUI and the system bogged down. Everything became extremely slow, but I was able to close Tracktion and avoid restarting the machine.
Interestingly, Tracktion showed the Voyager_GUI plug-in inserted on the track but the GUI itself did not appear, which leads me to believe it may be a graphics problem, but it's one I haven't seen before with any other plug-in. My graphics card is a GeForce 6800 GS and I'm on a single core Athlon 64 processor. Windows XP 32.
Update: I was able to successfully load Voyager_GUI into the same project mentioned above after closing and reopening Tracktion, so the problem appears to only be introduced when trying to load the plug-in while reopening a saved project.
Update 2: Ok, I have a more specific picture of what's going on. Basically, at least on my system, Voyager_GUI can only be loaded once after starting Tracktion 3---after that, this massive system slow-down problem occurs. I started Tracktion as stated above and was able to load Voyager_GUI into an existing project and it played fine. I then deleted it and saved the project under a new name, then tried to reload Voyager_GUI, and everything slowed to a crawl. I then got a pop-up from Tracktion saying "This plug-in is unresponsive". I was able to close the application, but, again, everything moved very slowly until Tracktion was closed, then the system went back to normal.
For some reason, reloading Voyager_GUI again after it has already been loaded one time before (not two instances, but loading it again after deleting it, even in a new project), seems to bog down the system to the point that it can't function and my guess is it's graphics related.
I'm going to try this again without the Limeflavour version of Charseisis in the project.
"You don’t expect much beyond a gaping, misspelled void when you stare into the cold dark place that is Internet comments."
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
-
- KVRAF
- 1981 posts since 29 Feb, 2004
I have noticed in the Tracktion forum that you had quite a few graphics issues with Tracktion3 and your machine.
Also, on my new machine, with Tracktion3 there is a high CPU-usage when dragging a knob on the Voyager GUI --- so far this only happens in Tracktion3, other hosts don't show any CPU-usage at all when dragging a knob. It appears there is something strange going in the graphics handling of Tracktion3.
On my old AMD Opteron 165 dual-core machine the original Voyager.dll took ages to load while on my new i530 dual-core machine the same original Voyager.dll loads much faster.
Maybe it is time to take that Phenom II and new mo/bo out of the box wou mentioned and build a new machine, some of these problems *might* be resolved with a faster machine.
Also, on my new machine, with Tracktion3 there is a high CPU-usage when dragging a knob on the Voyager GUI --- so far this only happens in Tracktion3, other hosts don't show any CPU-usage at all when dragging a knob. It appears there is something strange going in the graphics handling of Tracktion3.
On my old AMD Opteron 165 dual-core machine the original Voyager.dll took ages to load while on my new i530 dual-core machine the same original Voyager.dll loads much faster.
Maybe it is time to take that Phenom II and new mo/bo out of the box wou mentioned and build a new machine, some of these problems *might* be resolved with a faster machine.
-
- KVRAF
- 5524 posts since 5 May, 2007 from Mars Colony
True, but this plug-in in particular has unique problems that I haven't encountered in Tracktion 3 anywhere else. For instance, none of the previous graphics issues literally crashed the whole system before, and I've used dozens of different plug-ins in T3 up to now.
OTOH, if no one else is complaining about this then I can't assume it's a big priority for you, particularly since this is free and I can still use the old Voyager GUI.
It's interesting that you haven't had any issues trying the T3 demo but the other graphics issues in T3 vary from user to user as well so maybe that's the case here.
You have a point about doing the upgrade---I'm just cringing at the thought of reauthorizing a zillion C/R pieces of software and I'm not sure I'll even get Giga 3 back since Tascam no longer officially supports it. One thing I'm doing is starting to search for an alternative that will play my GS3 libraries (I mean really play them, not claim to and then fail miserably at it like Kontakt 3 does).
OTOH, if no one else is complaining about this then I can't assume it's a big priority for you, particularly since this is free and I can still use the old Voyager GUI.
It's interesting that you haven't had any issues trying the T3 demo but the other graphics issues in T3 vary from user to user as well so maybe that's the case here.
You have a point about doing the upgrade---I'm just cringing at the thought of reauthorizing a zillion C/R pieces of software and I'm not sure I'll even get Giga 3 back since Tascam no longer officially supports it. One thing I'm doing is starting to search for an alternative that will play my GS3 libraries (I mean really play them, not claim to and then fail miserably at it like Kontakt 3 does).
"You don’t expect much beyond a gaping, misspelled void when you stare into the cold dark place that is Internet comments."
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
-
- KVRAF
- 5524 posts since 5 May, 2007 from Mars Colony
One thing to note: the issue of Voyager_GUI not making any sound with MIDI input after loading a saved project couldn't be graphics related because that always happened before I tried opening the GUI.
Also, my slow GUI response problem all but disappeared in my other plug-ins after I cut down the size of my VST plug-ins folder.
Also, my slow GUI response problem all but disappeared in my other plug-ins after I cut down the size of my VST plug-ins folder.
"You don’t expect much beyond a gaping, misspelled void when you stare into the cold dark place that is Internet comments."
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
-
- KVRAF
- 1981 posts since 29 Feb, 2004
True, but as I mentioned Voyager has some strange problems of its own, expecially on slow AMD CPUs.A.M. Gold wrote:One thing to note: the issue of Voyager_GUI not making any sound with MIDI input after loading a saved project couldn't be graphics related because that always happened before I tried opening the GUI.
Also, my slow GUI response problem all but disappeared in my other plug-ins after I cut down the size of my VST plug-ins folder.
So, I have the feeling that the combination of a slow AMD CPU, a slightly wacky Tracktion3, a fussy Voyager plus mGUI trying to chain Tracktion3 to Voyager might just make for a formula of erratic behaviour which would be very difficult for me to work on...
-
- KVRAF
- 5524 posts since 5 May, 2007 from Mars Colony
I'll continue to experiment with plug-in interactions---maybe it's something I had on the track or in the project that somehow interferes.
In the mean time, I've devised a workaround, and in a sense the plot thickens here a bit.
Tracktion has chainers called racks that you can save with each project. All VST's in each rack will be saved in the project with all their settings, but the rack doesn't have to be saved on a track. I found that I could save Voayger_GUI inside a rack, but off of a track, and then move it up onto the track after opening the saved project---and it works. Voyager_GUI responds to MIDI and has no graphics issues when I do it that way.
In the mean time, I've devised a workaround, and in a sense the plot thickens here a bit.
Tracktion has chainers called racks that you can save with each project. All VST's in each rack will be saved in the project with all their settings, but the rack doesn't have to be saved on a track. I found that I could save Voayger_GUI inside a rack, but off of a track, and then move it up onto the track after opening the saved project---and it works. Voyager_GUI responds to MIDI and has no graphics issues when I do it that way.
"You don’t expect much beyond a gaping, misspelled void when you stare into the cold dark place that is Internet comments."
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
-
- KVRAF
- 5524 posts since 5 May, 2007 from Mars Colony
Well, at least I got it working. I've fallen in love with this synth after giving up on it a long time ago because of the horrific GUI. Limeflavour's is infinitely easier to work with (and nicer to look at) so I'm very glad to have found a way to continue using it.
"You don’t expect much beyond a gaping, misspelled void when you stare into the cold dark place that is Internet comments."
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
-
- KVRAF
- 1981 posts since 29 Feb, 2004
I have uploaded Voyager_GUI_v2b17.rar. Update your Voyager_GUI.dll with this one. Maybe it will be slightly better. The main change in this one is that it loads skins properly in Reaper and Tracktion3.
-
- KVRAF
- 5524 posts since 5 May, 2007 from Mars Colony
I'll try that update in the morning, thanks.
"You don’t expect much beyond a gaping, misspelled void when you stare into the cold dark place that is Internet comments."
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
---Salon on internet trolls attacking Cleveland kidnapping victim Amanda Berry
-
- KVRAF
- 2458 posts since 18 Jun, 2008 from "nunya"....
When I right click on the GUI to bring up the menu and click load/import preset nothing happens? I do have the presets in the "presets" folder in mGUI. Any ideas?
Thanks!
Thanks!
KVR >Gear Slutz! Change my mind! 
-
- KVRAF
- 1981 posts since 29 Feb, 2004
Use "ChildVST FXPB" >> "Load"/"Save" instead ...VSTJuNkiE wrote:When I right click on the GUI to bring up the menu and click load/import preset nothing happens? I do have the presets in the "presets" folder in mGUI.
-
- KVRAF
- 1924 posts since 24 Apr, 2010
VSTJuNkiE, I'm not following you around...honest.
Anyway, I'd just like to say that after a few scraps with this installation
I am up and running, I have always wanted to give Voyager a good going over but the original GUI was a bit daunting to tackle.
These skins are the boss!
Thanks for taking the time and the trouble. And a collection of presets to boot. Cheers.
p.s. The main thing to get the GUI running is to place the Voyager.dll in the asData/plugins folder.
Anyway, I'd just like to say that after a few scraps with this installation
I am up and running, I have always wanted to give Voyager a good going over but the original GUI was a bit daunting to tackle.
These skins are the boss!
Thanks for taking the time and the trouble. And a collection of presets to boot. Cheers.
p.s. The main thing to get the GUI running is to place the Voyager.dll in the asData/plugins folder.
-
- KVRAF
- 2458 posts since 18 Jun, 2008 from "nunya"....
Awww. I always wanted my own Stalker....bob bobwood wrote:VSTJuNkiE, I'm not following you around...honest.
Yep. I had it working before. A while ago. But I had to do a fresh install of Windoz due to a STD my 'puter caught(Whore!) and I've been reinstalling everything again.(yaybob bobwood wrote:Anyway, I'd just like to say that after a few scraps with this installation
I am up and running, I have always wanted to give Voyager a good going over but the original GUI was a bit daunting to tackle.
These skins are the boss!
Thanks for taking the time and the trouble. And a collection of presets to boot. Cheers.
p.s. The main thing to get the GUI running is to place the Voyager.dll in the asData/plugins folder.
)KVR >Gear Slutz! Change my mind!