Finally: Venom VB-303 v1.00

[Lesha]

yes, pattern-write mode, typo

Thank you Anton.

Still, it would be great if you could find and fix the problem. I can live with manually entering numbers for a MIDI Play mode, but the disappearing knobs problem in Ableton is too much trouble..

Anyone with enough experience in SynthEdit wanna help?

All the best
Lesha

[antto]

this is not so much SE-related, it's more within one module (the sequencer) and related to how the Host initializes/opens the plugin

i don't know what to say...
originally i spent a fairly big amount of time with this exact same issue - getting the plugin directory to the sequencer and it finally worked in the DAWs i had

use the plugin in whatever DAW it works, while it works
one day it won't work.. new OSes, new hardware, new DAWs..

this day may already be here
it still works for me on this machine (kinda crashes one of the hosts on exit, but that's just on exit.. meh)

[evosilica]

Hi,
I get the same message when selecting midiplay:

NONSEQ
Please Wait, Booting
C:\Programs\VstPlugins

The manual says, there should be a file called "N0S3q_config.cfg" in the Vb303 path, which isn't there.

Is this the problem and where can I get the missing file?

I'm not very comfortable with the 303 sequencer, but really like the sound of vb303. In a mix it sounds just as good as my x0xb0x.

Thank you

[sergiofrias]

Hello, i've done a video tutorial on VB-303

Hope you like it

[Lesha]

I tried several free plugins which can host VSTi.

discodsp Highlife and CTAF MultiFXVST displayed Venom without knobs as it is already in Ableton live.
VstBoard displayed Venom knobs correctly, but crashed Ableton Live.

Didn't try the commercial ones yet.

[antto]

sergiofrias: nice

evosilica: try this: move the MODE selector to another mode and then back to the mode you want - the Display should be refreshed
also the file N0S3q_config.cfg is going to be automatically generated if it's not found
you can run a file search in C:\ for files with name "N0S3q_config.cfg" and see where you find it
you can also check the cfg directory by going to SETTINGS mode and press FUNCTION+CLEAR

lesha: those are probably some kind of "wrappers" - they probably just "pass on" or "relay" the functions between the Host and Plugin, so that would explain why there's no change
and the one which works most likely does host the plugins in its own way and thus it works (but crashes, this could be vb303's fault too)

[Lesha]

Tried Xlutop Chainer and it displays the knobs correctly, the only problem is that I can't automate parameters in Ableton

EnergyXT behaves the same as Ableton. Firstly loads correctly, upon project restart the knobs are gone, and no chance of automating in Ableton.

EDIT: I have found a way of automating Xlutop parameters in Ableton. The downside is every time I click twice on stop button in Ableton's transport panel, MidiPlay code must be entered...

[Lesha]

Good news!
I have a confirmation that Venom displays correctly in the beta version of Bitwig Studio

[DuX]

Antto, this is the best 303 emulation I've ever heard and it's so much fun. I cannot thank you enough, maybe best done with a donation? It makes me feel like I'm playing with a real 303. I owned one, and 606, 808, 101 etc. I love this bugger! Thank you so much!

It's interesting to note that I've tested some other very commercial emulations of it in the past and I just can't help using this one because it sounds better to my ears! And since I've been using the real one and given it some time to learn how to use it, it is probably easier for me than for the rest of the people who have never owned one, especially ones who complain about the programming of sequences and playing it with your MIDI keyboard. The beauty is in the 303 as it is and especially its sequencer. Otherwise it would be just another lo-fi MIDI bassline product, kinda. It would sound awesome just playing it with a keyboard, I'm sure, but I never bothered with that because the sequencer really is the big part of the 303 sound and you nailed it quite perfectly. Those who cannot understand this, well try to reconsider your stance. Your FB comp is no slouch, either. I wish you to make living from DSP programming if that is your wish. Top notch stuff.

You should do more, more, more. Go C++ and Juce. Next step. It should worth your while...

[grooove]

Hi,

I just tried this again. First time it mystified me somewhat ;-)

This is the first 303 remake which I'd call an actual remake. Most others I've tried are almost, but not quite, entirely unlike a 303.

This VST sounds great. Can't verify if it's totally accurate, but it does sound very very much like it. And it does get my late 80s acid groove on! OMG

I'm not one to celebrate the funny midiplay lock thing. What's that about then..

But after you get the sequencer to do your bidding, it will melt your kit. All I can say is: Spend the time, it'll sing sweet acid to you!

Respect to you, Antto. It truly is a great piece of work.

goran

Note to Ableton users, if you get the rotaries disappearing bug, what seems to work is to just switch off and then on the instrument. The buttons will return. No need to make new tracks, delete and insert the plugin again or copy the plugin to another project or something.

[Lesha]

Which version of Ableton Live are you using?

[grooove]

Which version of Ableton Live are you using?

I've tried it on Live 8/32bit. The rotaries seem to come back for me if I switch the device off and on.

The plugin will forget which pattern it's on though, like when the project's loaded. But luckily the actual pattern still seems to be there. Just enable the right one again.

Note: Can't tell what's going to happen if there are more projects with the VB on disk and when you swap them. But that's for another day. I'd save any pattern worth keeping from the plugin, in case it got confused ;-)

The problem of the missing buttons is a minor one, imo, as VB publishes its parameters to Live OK. If you klick the [configure] button on the device box where you've just dropped the instrument, it will show you all of VB's parameters which are up for automation. You can use those slider controls to accomplish the same thing as on the plugin UI. The descriptions are sensible too, can't miss them.

Besides, I've mapped some rotary buttons on the old MPK49 to those six VB rotaries while I was setting up the VB sequencer programming, etc. Just save a live project with those mappings for programming the VB and proceed from there. Tweak on :)

[antto]

thanks for the kind comments
i think my ableton demo has expired by now, but basically i was thinking something like that - restart the plugin if possible
on restart, the sequencer is rebooted of course, all pattern memory is reloaded from the vst "preset"
one thing to note: whenever you edit patterns or tracks (in other words anything that has to write into the sequencer memory) - the sequencer is on the DSP thread, but the memory has to be sent to the GUI thread in order to be saved to the vst preset. this takes a short moment to happen (DSP->GUI latency)
so if you've just made some change (edited a pattern or a track or so) - wait a second before saving the DAW project or restarting the plugin

DuX: i don't use JUCE but wdl-ol (IPlug)
vb303 is calibrated to my x0xb0x, and i now have another x0xb0x (which i built myself) and i kinda like it better, but oh well
ABL3 is being brewed, it's gonna be excelent

[grooove]

Hi Antto,

I did notice something more serious though, with chained patterns. Maybe you have some insight.

If I make a single pattern and run it in host sync mode with a long midi tone from the DAW, it'll run and run and run. No problem as yet.

If, however, I chain two (I tried only two 4/4 16 steps) patterns and run that, after a while the plugin will act like it is in tap mode, with only a metronome-like repeating beep playing.

If you restart the DAWs project (stop/start), it seems to play happily again. At least for a while and then it happens again.

Tried a few times and it seems to happen repeatedly.

I was afraid my setup might be generating ghost midi messages (which VB was accepting as commands), but didn't see any with midiOX. Will keep an eye out on the issue, if I use chained patters in future.

Any idea why VB would react like that?

[antto]

is it in pattern-write mode when this happens?