Page 1 of 1
Bugs in the Voyager Editor
Posted: Thu Mar 18, 2010 12:14 pm
by ikazlar
In the Voyager Expert Surface:
1. It's not possible to click on the 3KB switch to change its status.
2. It's not possible to click on the 3 Freq switch to change its status.
Click Options --> Show Moog
3. Clicking either on the 3KB or 3 Freq knobs changes the status and their changes are reflected in the Expert Surface. The opposite is not true.
4. In the Oscillator section click on the number that indicates the Frequency of either oscillator 2 or 3. Mine shows -32629. Type a number for instance 13047. The display shows another number (-19721).
Type 246 and it shows -32522. The slider doesn't move to 246 either.

Re: Bugs in the Voyager Editor
Posted: Thu Apr 08, 2010 5:15 pm
by barrie
I had real problems with this program and in many ways feel that I've wasted my money.
BW
Barrie
Re: Bugs in the Voyager Editor
Posted: Thu Apr 08, 2010 5:48 pm
by Just Me
I have to ask the dumb question. Why do you need an editor? I mean, there are knobs and switches for most of the functions and the menus aren't too deep to be difficult. (Try a DX7 or a Sequential VS) Can it be automated by some sequencer program to control stuff real time? I have no difficulty writting a patch and then saving or loading through SYSEX. (And since I could not get the demo version of the editor to even run on my computer, I've never had the chance to see what it would do.)
Re: Bugs in the Voyager Editor
Posted: Sat Apr 10, 2010 1:14 pm
by ikazlar
Who do we report these bugs to? I have sent an email to Soundtower and got no reply whatsoever.
Can anyone help here?
Re: Bugs in the Voyager Editor
Posted: Sat Apr 10, 2010 9:35 pm
by Kent
For backing up.
For seeing what makes a patch 'tick' at a glance.
Just Me wrote:I have to ask the dumb question. Why do you need an editor? I mean, there are knobs and switches for most of the functions and the menus aren't too deep to be difficult. (Try a DX7 or a Sequential VS) Can it be automated by some sequencer program to control stuff real time? I have no difficulty writting a patch and then saving or loading through SYSEX. (And since I could not get the demo version of the editor to even run on my computer, I've never had the chance to see what it would do.)
Re: Bugs in the Voyager Editor
Posted: Sun Apr 11, 2010 9:52 am
by polyslax
Haven't tried the editor yet myself, but I wondered what the patch mutation/breeding facilities were like to use - any thoughts?
Re: Bugs in the Voyager Editor
Posted: Thu Apr 22, 2010 9:16 am
by tedjohn09
Can anybody help???
__________________
The Losers
Paper Man
Re: Bugs in the Voyager Editor
Posted: Thu Apr 22, 2010 10:45 am
by Amos
I find the patch mutation function rather nifty.
As for bug reports, definitely contact
editors@soundtower.com .
I'll also pass along these reports myself...
Cheers,
Amos
Re: Bugs in the Voyager Editor
Posted: Thu Apr 22, 2010 10:21 pm
by MarkM
I don't have an issue with my Anniversary Edition Voyager's keyboard, but I am curious as to what kind of keyboard I have. Mine is not closed on the bottom; it has what appears to be some metal bars. Would that be Chinese or Fatar?
Re: Bugs in the Voyager Editor
Posted: Fri Apr 23, 2010 10:35 am
by Amos
Hi Mark, I think you're in the wrong thread.
Anniversary Edition - black cabinet with blue lighting, came out in 2004? If so that's the same as I have

That would have to be a Fatar keyboard.
FYI none of the Fatar keyboards used on the Voyager look like the "Fatar" photo in the other thread... Fatar makes all kinds of keyboards for different manufacturers. That photo is of some other model (looks like for a stage piano, perhaps).
Re: Bugs in the Voyager Editor
Posted: Sat Apr 24, 2010 2:38 am
by MarkM
I am indeed in the wrong thread and apologize profusely. I walked away from the computer for a short while and forgot to check what thread I was on. Sorry. And thanks to Amos for answering my question.
And now. . . . back to the "Bugs in the Voyager Editor" thread.
Re: Bugs in the Voyager Editor
Posted: Tue Jun 01, 2010 1:15 pm
by smithdwsn
Yes, you are right. I have faced this problem before one week. It is really bug. No solution for that. So i am waiting solution of this problem.