Asseca, I ran in to a nasty bug with the skinned version, using Reaper. I have a simple two note (interval) drone, the notes are just sustained over several bars. However, Voyager only very short sounds the two notes at the beginning and then goes silent, as if the keys where just quickly tapped instead of constantly sustained. When I replace the skinned version with the original Voyager dll then it plays without problems. With the skinnend version I'm also having notes abruptly cut off while playing from my midi-keyboard, just randomly a note gets 'swallowed'.
The problem in Reaper is happening when the notes are playing from the start. As soon as I move the clip one bar from the start it plays correctly. For a moment I thought it to be a Reaper problem but again the original Voyager dll does not show this problem, neither do other synths that I tried in place of Voyager.
Let me know if you want me to try out certain things.
Arguru Voyager - New Skin
-
- KVRAF
- 2784 posts since 18 Apr, 2001
CrimsonWarlock aka TechnoGremlin, Moved to Reason and Rack Extensions exclusively (from Reaper and VSTs) several years ago.
-
- KVRAF
- 1981 posts since 29 Feb, 2004
I have tested with v2b10 and v2b16, seems to work fine here in Reaper v3.661.
I recorded from the 1st bar, also tried playing notes from the MIDI-keyboard while playing back a song, seems to work OK so far ...
Maybe you have a small project file for me to test with only Voyager and an audio track ??
What version of windows and which ASIO driver are you using ?
Do you also have problems in Herman Seib's VstHost ?
I recorded from the 1st bar, also tried playing notes from the MIDI-keyboard while playing back a song, seems to work OK so far ...
Maybe you have a small project file for me to test with only Voyager and an audio track ??
What version of windows and which ASIO driver are you using ?
Do you also have problems in Herman Seib's VstHost ?
-
- KVRAF
- 2784 posts since 18 Apr, 2001
It seems to manifest itself after a little while in Reaper. Someone on the Reaper forum said he had no problems but later on came back to post he had similar issues after a while as well.asseca wrote:I have tested with v2b10 and v2b16, seems to work fine here in Reaper v3.661.
I recorded from the 1st bar, also tried playing notes from the MIDI-keyboard while playing back a song, seems to work OK so far ...
I'll see if I strip out everything but the Voyager track if it is still persistent. If so I'll get the project-file to you somehow. There's nothing special in there, just a chordasseca wrote:Maybe you have a small project file for me to test with only Voyager and an audio track ??
WinXP with M-audio 2496 and native m-audio drivers, running with 384 buffersize. I'll try with other hosts as well, didn't do that yet. I'll get back to you on that.asseca wrote:What version of windows and which ASIO driver are you using ?
Do you also have problems in Herman Seib's VstHost ?
CrimsonWarlock aka TechnoGremlin, Moved to Reason and Rack Extensions exclusively (from Reaper and VSTs) several years ago.
-
- KVRAF
- 2784 posts since 18 Apr, 2001
Will test that as well. But it will have to wait until tomorrow as I'm going to shutdown for the nightasseca wrote:Just another question, did you use mGUIv2b10 or mGUIv2b16 ??
Also does this bug occur with the GUI closed and opened ??
CrimsonWarlock aka TechnoGremlin, Moved to Reason and Rack Extensions exclusively (from Reaper and VSTs) several years ago.
-
- KVRAF
- 5524 posts since 5 May, 2007 from Mars Colony
Hi Limeflavour/Asseca,
I have tried many times to do the below steps and made sure I was following each instruction carefully and I get no results doing this on a Win XP 32 system with Tracktion 3. The Voyager plug-in just comes up with the old skin time and again. Any suggestions on trying to root out what I'm missing?
Thanks very much, and thanks for reviving this awesome old plug-in!
Dave
BTW, when I hit the "set" button on the set plug-ins path .exe it doesn't seem like it's doing anything (i.e. nothing happens that makes it look different, except that "set" is outlined by a dotted line after I hit it), so that may be the problem.
I have tried many times to do the below steps and made sure I was following each instruction carefully and I get no results doing this on a Win XP 32 system with Tracktion 3. The Voyager plug-in just comes up with the old skin time and again. Any suggestions on trying to root out what I'm missing?
Thanks very much, and thanks for reviving this awesome old plug-in!
Dave
BTW, when I hit the "set" button on the set plug-ins path .exe it doesn't seem like it's doing anything (i.e. nothing happens that makes it look different, except that "set" is outlined by a dotted line after I hit it), so that may be the problem.
Limeflavour wrote: Update!
Asseca has made a new installer for this skin, it's an .exe file.
How to install (With the new .exe installer):
If you DON'T have any other mGUI plugins installed:
Run the Voyager-lf.exe installer program to copy the folders+files into the VstPlugins folder.
Run asData\setVSTmGUIpaths.exe to automatically set the asData path in the registry.
Then copy/move the Arguru's Voyager.dll into the \asData\plugins 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
A.M. Gold,
What is the exact path of your asData folder ?
It is best to place the asData folder in e.g. C:\VstData\Asseca\asData.
By default the skinned plugin is called Voyager_GUI.dll. If you want, you may rename Voyager_GUI.dll to Voyager.dll
What is the exact path of your asData folder ?
It is best to place the asData folder in e.g. C:\VstData\Asseca\asData.
By default the skinned plugin is called Voyager_GUI.dll. If you want, you may rename Voyager_GUI.dll to Voyager.dll
-
- KVRAF
- 5524 posts since 5 May, 2007 from Mars Colony
Asseca, thanks for the reply. I'm a little confused as to how many Voyager plugins are supposed to be in the asseca folder. Does the original Voyager.dll go into the asData\plugins folder? If so, and if I rename Voyager_GUI.dll to Voyager.dll, then there will be two Voyager.dll files.asseca wrote:A.M. Gold,
What is the exact path of your asData folder ?
It is best to place the asData folder in e.g. C:\VstData\Asseca\asData.
By default the skinned plugin is called Voyager_GUI.dll. If you want, you may rename Voyager_GUI.dll to Voyager.dll
My asData folder is in VstPlugins\Asseca\asData, inside the same (VstPlugins) folder I use for all my other plugins for Tracktion 3. The Voyager_GUI.dll is inside the Asseca folder and the original Voyager.dll is in the plugins folder inside the asData folder.
Actually, I just went back and checked and I realized what part of the problem is: every version of Voyager_GUI.dll has failed the Tracktion 3 plug-in scan. I then tried renaming it to Voyager.dll and scanned again and that also was rejected. Do you have any sense of why that would be?
"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
Yes, a copy of the original Voyager.dll MUST be placed in the asData\plugins folder.Does the original Voyager.dll go into the asData\plugins folder?
Voyager_GUI version v2b16 seems to be correctly scanned by Tracktion 3.
PLEASE ensure that your Voyager_GUI.dll is version v2b16.
Again, I would strongly suggest to move the asData folder outside the VstPlugins folder to avoid Tracktion scanning all the files in the asData folder.
-
- KVRAF
- 5524 posts since 5 May, 2007 from Mars Colony
Edit: I finally figured it out.
Here is what I missed, and if this is something that was clearly explained somewhere then please excuse me, but if it hasn't been spelled out in the instructions somewhere then I think this point should be clarified.
What I thought I was supposed to do was to maintain the asData folder inside the Asseca folder, as it appears when the Asseca folder is unzipped. I can't remember any instructions that told me to unzip it, then separate the contents with the Voyager_GUI.dll going into your regular VST plugin folder, and the asData folder going anywhere else, (as long as it is not inside your regular VST plugins folder.
I knew the Voyager_GUI.dll had to be scanned by my host, but I never saw instructions that told me that the asData file needed to be taken out of the Asseca folder so that it is definitely not scanned by the host, so I just left it in there and put the whole Asseca folder into my VST plugins folder and scanned.
Now that I have separated out the asData folder, the scan worked and the GUI version of Voyager is loading. I'll let you know tomorrow how well it performs in Tracktion 3.
Here is what I missed, and if this is something that was clearly explained somewhere then please excuse me, but if it hasn't been spelled out in the instructions somewhere then I think this point should be clarified.
What I thought I was supposed to do was to maintain the asData folder inside the Asseca folder, as it appears when the Asseca folder is unzipped. I can't remember any instructions that told me to unzip it, then separate the contents with the Voyager_GUI.dll going into your regular VST plugin folder, and the asData folder going anywhere else, (as long as it is not inside your regular VST plugins folder.
I knew the Voyager_GUI.dll had to be scanned by my host, but I never saw instructions that told me that the asData file needed to be taken out of the Asseca folder so that it is definitely not scanned by the host, so I just left it in there and put the whole Asseca folder into my VST plugins folder and scanned.
Now that I have separated out the asData folder, the scan worked and the GUI version of Voyager is loading. I'll let you know tomorrow how well it performs in Tracktion 3.
"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
Anyway, complaints aside, I really have to thank you and Limeflavour for making this great GUI possible for this amazing synthesizer. 
"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
Unfortunately I have a major bug to report: upon loading a project today in Tracktion 3 that I saved last night with Voyager_GUI saved in it, the GUI loaded but the plugin would not make any sound when I tried triggering it with MIDI input. I then deleted and reloaded the plugin and my whole system immediately locked up and I had to hard restart my machine.
This was on a Win XP 32 bit system.
Update: I tested again several times and each time v. 2.0.16 of Voyager_GUI would not respond to MIDI after loading into a saved Tracktion 3 project. I also tried on different MIDI channels and got the same result.
This was on a Win XP 32 bit system.
Update: I tested again several times and each time v. 2.0.16 of Voyager_GUI would not respond to MIDI after loading into a saved Tracktion 3 project. I also tried on different MIDI channels and got the same result.
"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 am sorry that you are having problems. Unfortunately I only have the Traktion 3 demo.
My testing was done in Reaper, Podium Free, VstHost, energyXTv2 and re-loading projects seem to work fine.
My testing was done in Reaper, Podium Free, VstHost, energyXTv2 and re-loading projects seem to work fine.
-
- KVRAF
- 5524 posts since 5 May, 2007 from Mars Colony
I'll try it in a different project. Maybe there's a bad plug-in interaction. If and when you update the plug-in I'll try that too.
Update: I just loaded it into a blank project and saved it, then reopened it (after first switching to another project, then back) and it worked, but it was the only plug-in loaded into the project.
If this is just Tracktion somehow screwing up one project so that Voyager_GUI didn't work, I suppose that wouldn't shock me since Tracktion 3 is full of surprises. Maybe the plug-in will continue to work in future projects.
Update: I just loaded it into a blank project and saved it, then reopened it (after first switching to another project, then back) and it worked, but it was the only plug-in loaded into the project.
If this is just Tracktion somehow screwing up one project so that Voyager_GUI didn't work, I suppose that wouldn't shock me since Tracktion 3 is full of surprises. Maybe the plug-in will continue to work in future projects.
"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