My new Voyager Eclectic Blue (purchased used–its around 5 years old 128 preset model) is a great great lead instrument to play but the midi timing on the Voyager is all over the place
–its not tight-its totally unusable as a bass machine sequenced from a DAW–Im really surprised how bad it is compared to the Little Phatty Stage 2 --I think the USB is the key to super tight midi on the stage 2–its incredible!
Dont get me wrong the midi works fine technically but it just feels like a sloppy implementation timing wise–I just cannot use it
Can anyone point me the right direction if there could be a software update that improves the midi timing on the Voyager–its a long shot–failing that Im going to try a Kenton USB solo as a possible solution which has quite a fast midi to CV
thanks in advance
and Merry Christmas
Dave
First question i would like to ask is…what software version are you running right now on your Voyager…?
system version 3.4
however it has not got the upgrade board (At least I think it has not ) its the original 128 program version
Hey yo how are you connecting your Voyager with midi? Is it comming from your firewire sound card? If so i had the same problem. I had a firewire sound card that had Midi in-out connection and I would control my voyager through that from ableton with really bad timing issues. Like you said USB seems to be rock solid so I connected my voyager from my MIDI keyboard that has MIDI in out and the problem was completely fixed.
Im using a MOTU microlight USB -Midi with OSX
My gut feeling is that the midi circuit in the Voyager is not as fast as the LP2’s and the Voyager will be much faster over CV/Gate in
However Im thinking of dumping the MOTU and using my kenton USB Solo midi to CV and using the Voyagers CV/gate in instead
Update–Using the Kenton USB Solo USD-CV convertor all my timing problems have disappeared
I have concluded that the midi circuit in the Voyager is sloppy and CV/Gate Ins is the best way to go
Tip Kenton user manual says this
It may be that your synth is slightly out of tune, so it will be necessary to adjust the USB SOLO to compensate for the tuning of your synth.
1, Firstly, ensure that your analogue synth is as in-tune as possible when playing from its own keyboard. Do this by adjusting the tuning or pitch knob on your analogue synth whilst playing middle C on both this and your master keyboard (or whatever you use for tuning reference). To do this, you may need to disconnect the analogue synth from the USB SOLO.
2, Connect the converter to your analogue synth and MIDI system. Check the USB SOLO is switched to the correct scaling system, Hz/V for Korg and Yamaha, or V/oct for anything else (see Editing Parameters section). Set transpose to zero. Now press bottom C (MIDI note #36) on your digital synth. Both synths should sound, don’t worry at this stage if they are not in tune.
3, Using bottom C (MIDI note #36) as a reference (you must use this note for maximum accuracy) tune in the USB SOLO with your analogue synth by adjusting the parameter FINE TUNE and TRANSPOSE if necessary (see Editing Parameters section) until it is exactly in tune.
4, When your digital & analogue synths are in tune at the bottom , play middle C, two octaves up on your digital synth. (MIDI note #60). Now adjust the SCALE parameter (see Editing Parameters section) until both synths are in tune. The analogue synth should now play correctly across it’s complete range from your master keyboard, if this is still not the case go back to step 3 and repeat the process for final tweaking.
Yeah midi timing in the voyager isn’t as tight as my lps2 and minitaur. Be nice if there was an update that could improve things in this dept. I wonder if it’s possible.
Wonder why there’s so few complaints about this issue. Is everybody else just sequencing the Voyager via CV? Or maybe just handful of people out of 1000s with a bum MIDI circuit in their Voyagers.
Not sure- I always havd to offset all the timing on the midi with voyager as it’s always late- the minitaur and lp I have are super tight over USB. I’d like to see an upgrade to the midi side of the voyager to improve timing and maybe they could make a Voyager mk2 with USB! Still- the voyager is an incredible piece of kit. couldn’t do without it!
No problem with Midi timing here (Voyager RME). Voyager is connected via MIDI In/Out 1 of my RME HDSP 9652 PCI card.
Due to the 14-bit resolution of the front-panel controls the amount of transmitted data can become very high! It is very important to avoid Midi loops.
This can be done by setting the Voyager to Local-Off or in my case, because I have a RME, by disabeling the Midi Input from the Voyager in the active DAW track (activate the MIDI input only for the recording of some knob action on the voyager).
My curiosity is piqued. I’ll set up an Octatrack MIDI sequence at 300 bpm and send it to my Voyager to see if it can keep up.
I have software OS 3.5 and all the hardware upgrades.
The voyager has a pretty bad in built latency from the point of triggering-
From the innerclock systems website litmus test:
"Trigger In to Audio Out Latency Range = 177 samples (3.69ms) "
And that says a lot. For example the akai mpc 3000 has 1 sample latency!!
No wonder the 3k feels super tight and the voyager feels baggy.
I’ll be sure to update the gang after my MIDI sequencing test.
I just saw this girl play a show with a Voyager and she was sequencing it for bass lines - she only touched it to turn some knobs (no manual playing on the keyboard) - never noticed a lag in the Voyager’s timing compared to other sequenced stuff:
Hmm, in this video, the MIDI sequenced Voyager stays in time with the drum machine that is providing the MIDI sequence. I don’t hear any lag there either.
We are talking milliseconds but theres a big difference between 1 and 177 samples delay. It’s something you sense when firing midi back from your daw, it would be hard to pick up from a video.
I don’t have any numbers or technical knowledge, but I sometimes FEEL like it’s a little slow. Especially with fast 16th note sequences with snappy bass sounds.
I have no problems at all with MIDI timing with my voyager running OS v3.5 through my MPC2000XL. The timing is tight and I’m even playing my voyager with local off, going out through MIDI to the MPC and back out to the voyager via MIDI in and there is no noticeable delay to me.
Worth mentioning is that many MIDI drivers on windows are not very good and can have quite a bit of delay involved and is somewhat a known issue and there are known issue with DirectMusic being the default MIDI device being a really poor performer. Google it and you will find tons of similar issues with MIDI lag under windows. My cheap midi sport 2x2 had unusable amounts of delay for me when I tried to software sequence any of my MIDI gear for example. I could play one thing, and it would be completely different then what was actually recorded using my underpowered netbook. I imagine this is your problem since you mention that you are running your voyager via MIDI and the LP via USB. This is comparing apples to oranges. Id imagine you’d have the same exact delay problems no matter what MIDI device you connected.
However, your problem isn’t with your voyager, the MIDI standard, or USB being superior. Its specifically with the MIDI drivers for windows being terrible and causing hiccups and lag. heres a link to get you started troubleshooting in the right place: http://www.soundonsound.com/sos/dec07/articles/cubasetech_1207.htm
In my case it might be that the filter decay is fooling me. Need to mention it to prevent a witch hunt. I sequence the Voyager with a MonoMachine, so no computer latency there. But if the decay is just a tad slow i a snappy bass sound it feels like it’s lagging. Especially with 16th note sequences.
That’s exactly what i mean- I’ve known other manufacturers to update firmware to enhance midi timing so perhaps this can be done on the Voyager. 
I see.
All the examples that I found of the Voyager being sequenced had the sequencer running on hardware rather than DAW.
maybe open door,
but does the setting: show value of every knob when moved, / or stay on patchname , also influence the fastness in reaction of the voyager ?
same like for datasenddensity, etc ?
it all has to be done by the same cpu…