Ok, now I know what I have to do (“send the “OMNI ON” to V256 through channel 16). But how do I do this??? How can I send the command OMNI ON (CC 125 – “0”)??? Can I send this command from Studio Logic Pro??? Thank you.

hi, new user (actually paid for but haven’t received it yet
is it possible to change the MIDI channel, as that would be a dealbreaker of not, as using hardware sequencer changing the midi channel may require a playback stop (it does on the electribes i use) and i have pre set midi channel for different hardware synth and one of those, the lead one, can only receive on 1, 2 and 3 so the lead part is always assigned to channel 3(jx3p) and so should be the v256, and also, i use another device that forces MIDI channel 16 as a mixer so that channel is all control changes

but thinking out loud, i might be able to re route channels in my MIDI time piece, but still a big bumer to have only 16 and omni (which is really not practical in a hardware live situation with all channels being pretty much loaded with data flowing through them, maybe since it has a midi in the firmware can get some upgrades?

you can’t access that through the function menu? I’ve got a DGX200 and i’m fairly certain I can change the midi channel on mine. You can snag the manual for the DGX300 here: http://usa.yamaha.com/products/musical-instruments/keyboards/digitalkeyboards/dgx_series/dgx-300/?mode=model

Same here. I am trying to send data both from my DAW (Studio One V2) and directly from my M-Audio Keystation 88es. Both can send on MIDI channel 16, and to the degree that I can test the signal being sent, that’s what appears to be coming out of the midi cable.

However I have tried sending both note information as well as a CC 125 (all different vaues, ending with 0), and am getting no response from the v256 internal synth.

I am starting to wonder if there’s been some change to the v256 recently, since both mpb212 and I appear to be doing the right thing and there’s no response.

Are we missing out on some particular knob setting or something?

The solution to my problem turned out to be that the unit was defective, probably a bad solder joint.
EHX offered to fix it for the cost of shipping but since it was within 30 days of purchase from Amazon i was able to just exchange straight for a new unit at no cost.

I bought a second unit to get stereo carrier+mod vocoding on my DAW, had no problems with second unit.
Actually I found that there’s a lot of external synths that work better than the internal ones so in the long run I turned out not to even use this feature.

As for this being a recurring problem, that’s the nature of manufacturing in medium sized lots: the facility is set up custom to do do a few hundred units that get built all on the same day, and that batch is warehoused and sold off for 6 months or a year. If soldering machine #23 was having problems that day, then a whole bunch of units in that batch will have issues with whatever part soldering machine #23 was processing.

I use all soft synths (VST), and I’ve tried them all.
Of course it’s more a matter of the timbre than the synth itself, but I have found that Cyclop by SugarBytes has a ton of presets that sound particularly good with the vocoder.
Cyclop is nominally a specialist Bass synth marketed toward DnB-Dubstep-Elektro enthusiasts, so it’s geared toward adding the kind of modulation, distortion, and harmonic noise that go well with a vocoder. Because it’s a bass synth it’s primarily set up for multi-timbral monophonic (in the sense of one-key-at-a-time as opposed to “not stereo”) play.