Awesome -mkdr wrote:http://youtu.be/XGN-JXVELd8
Download the Beta/Demo installer from here:
https://dl.dropbox.com/u/880206/MKDR_Ve ... b_demo.exe
As this is Beta/Demo, what are the restrictions in functionality, or is it just a timeout?
Awesome -mkdr wrote:http://youtu.be/XGN-JXVELd8
Download the Beta/Demo installer from here:
https://dl.dropbox.com/u/880206/MKDR_Ve ... b_demo.exe
10€Kriminal wrote:How much will the editor cost?
Thats cool, i'll def grab that once u have the synth.mkdr wrote:10€Kriminal wrote:How much will the editor cost?
The demo is limited to 9 minutes.. i think. Other than that it's fully functional.
I'm working on the patch management. I still couldn't decode some received patches correctly. It seems the hw is sending bytes in a wrong order. It's clearly somekind of hw problem as receiving single patches from the "edit buffer" of the synth works like it's supposed to. I'm sure i can fix the problem in some way. When your ports are configured correctly you can turn the patch selection knob and the editor fetches that patch from the synth.breakmixer wrote:Just to confirm in 32 bit install cubase 5/w7, this works 100%, tried the demo 5 times...
If on a similar set-up, choose venom synth in/out on the VST.
In cubase settings I had to a little messing about, but this configuration worked.
Direct Music Venom Synth In Visible X Active X
Windows Midi Venom Synth In Visible X Inactive
The only thing I wondered about was how to load free/commercial banks, without having to rely on the Vyzex editor?
Also how can you save Free/Commercial Banks to the hardware itself?
Apart from that - I was altering patches, renaming and as soon as clicked return that patch was named on the hardware, then just saved it to the venom itself.
So all in all good work, just a bit concerned about patch management, saving and loading, 3rd party whole banks and single presets etc...
Many thanks!
No lol, I'm not too worried about the multi's myself! It's also above me.mkdr wrote:Btw. Any ideas on Multi's and how to save and handle those?
Ah ok, that would explain why I didn't got the GUI reflecting the changes done in the Venom with the Remote 25. I'll try to refresh.breakmixer wrote:
If you change any 'performance controls' on the hardware the VST does not do any parameter changes unless you hit 'request' to update(* Except Resonance, that worked weirdly).
mkdr wrote:Btw. Any ideas on Multi's and how to save and handle those?
Heh Ok. No problembreakmixer wrote:No lol, I'm not too worried about the multi's myself! It's also above me.mkdr wrote:Btw. Any ideas on Multi's and how to save and handle those?
Have a look out for that "rapid changing of the 3rd osc" (sounds like a sci-fi movie) and if it does the disconnecting thing again come here yellin'!breakmixer wrote: So I have another play(over ten times now) and it holds the 'venom synth in/out' settings rock solidly, the Vyzex editor used to fail nearly every or every other time, so this is really good.
So far I've had stuck notes once and a non responsive vst at the same time, this was when changing the '3rd osc' rapidly, this then disconnected the vst from the hardware totally - but I'm not sure if the demo had just timed out, could of been that, anyway I must of fired it up ten times and cannot find any definite fault - If you change any 'performance controls' on the hardware the VST does not do any parameter changes unless you hit 'request' to update(* Except Resonance, that worked weirdly).
Glad to hear you like it. And yes a dedicated thread might be a good idea. I totally forgot to do thatbreakmixer wrote: So all in all, very very happy and will purchase the full version as soon as it's ready.
Maybe you need to start a dedicated thread on this?
As to be expected from quality productsbreakmixer wrote: PS I'm using the venom midi in/outs for my MophoEd and that is rock solid too.
I use Remote Zero Mk II(i.e. Automap) with his other editor for Mopho(Mopho'ed) and that works fine, have you wrapped the plugin with automap?Bifop wrote:Ah ok, that would explain why I didn't got the GUI reflecting the changes done in the Venom with the Remote 25. I'll try to refresh.
Maybe an "auto refresh" feature would help.
? I'm using Venom as my main controller already, i.e. to play all my VSTs/Hardware within my daw(Cubase 5)mkdr wrote:Oh and I'm planning to use VenomEd myself without a dedicated midi-input from the synth because i wan't to use the keys as my master keys in Cubase. Just to let people know that it's possible. Only an uplink is needed for proper operation. Haven't tested it with those Multi's yet though.. fingers crossed.
I've tried to stay clear of Vyzex after i initially looked up what it was doing with Midiox.. I've done everything by the documentation since. And that's actually not what i ment.Bifop wrote: What part of the procedure are you missing ? Looking in the docs, it requires a handshake procedure. Did you spied Vyzex's messages regarding multis (with a virtual midi driver and an hex editor for instance) ?
Sorry if I state the obvious or If I misunderstood your question.
I use the first remote incarnation (so no automap).breakmixer wrote:
I use Remote Zero Mk II(i.e. Automap) with his other editor for Mopho(Mopho'ed) and that works fine, have you wrapped the plugin with automap?
Using Remote 25 the parameters should update in realtime, not by 'request'ing, I think that is only for the onboard 'performance controls' of the Venom.
I will try this tomorrow and report back, you should be able to assign(learn) the Remote 25 to the Venom'ed no problem.
Do you mean that Vyzex sends some "garbage" in the sysex strings ?mkdr wrote:
I've tried to stay clear of Vyzex after i initially looked up what it was doing with Midiox.. I've done everything by the documentation since. And that's actually not what i ment.
Yeah things can really get messy with the patches organisation since they are not stored in the multi ! YOur method would mean we'd have a succesion of let's say, drum, bass, arpeggio and pad in the memomy banks, right ?mkdr wrote: The thing is.. as the synth saves all it's Multis as "references" to patches in the synths memory, there's no sensible way to send Multis to be used standalone. I'm thinking of doing it in series of fours on the patch banks. So for example Multi 1 has patches 1,2,3 and 4. Multi 2 = 5,6,7,8. Multi 3 = 9,10,11,12. And so on. This way the patch handling wouldn't be an issue for the user. Better to have 64 Multis that work flawlessly than 100 that you can easily mess up. Right?
Well that's my view on it. Any comments?
+ 1000mkdr wrote: Why oh why don't any synth manufacturer do it like Clavia did?! Nord Leads have Multis that include all the patch data inside them. No stupid referencing and things to mess up.
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement