You are here

Vee One Suite 0.5.0 - Officially beta now!


The Vee One Suite of old-school software instruments, primarily slated for Linux, featuring synthv1, a polyphonic synthesizer, samplv1, a polyphonic sampler and drumkv1, a drum-kit sampler, are officially in beta phase now.

Change-log for the new release:

  • LV2 UI Idle and Show interfaces support added.
  • First attempt to allow a headless stand-alone JACK client application run mode, without a GUI, with option given as command line argument (--no-gui).
  • A man page has been added (re. stand-alone JACK clients).
  • Reverse sample option and parameter knob added. (samplv1 and drumkv1 only).
  • Allow the build system to include an user specified LDFLAGS.

As before, all made available in dual form:

  • a pure stand-alone JACK client with JACK-session, NSM (Non Session management) and both JACK MIDI and ALSA MIDI input support;
  • a LV2 instrument plug-in.

The Vee One Suite are free and open-source Linux Audio software, distributed under the terms of the GNU General Public License (GPL) version 2 or later.

The fine print follows ;)

synthv1 - an old-school polyphonic synthesizer

synthv1 0.5.0 released!

synthv1 is an old-school all-digital 4-oscillator subtractive polyphonic synthesizer with stereo fx.


Flattr this

samplv1 - an old-school polyphonic sampler

samplv1 0.5.0 released!

samplv1 is an old-school polyphonic sampler synthesizer with stereo fx.


Flattr this

drumkv1 - an old-school drum-kit sampler

drumkv1 0.5.0 released!

drumkv1 an old-school drum-kit sampler synthesizer with stereo fx.


Flattr this

Enjoy && ever again, have fun.


Dear Rui,
Your software looks very good, but I need help. Is there a manual so that I can learn how to use your software? Until now I didn't succeed in finding out what to do to make it work.

Thank you in advance,
Kind regards,

rncbc's picture

before all else, where do you stand for a start?

a. are you familiar with linux ? linux audio/sound/music production, which generally boils down to jack ? are you familiar withe the jack-audio-connection-kit linux so called ecosystem? which distro?

if you're puzzled with all that, yet, please consider following the kxstudio route and join the forum, where a lot of parties gather with probably the very same (initial) troubles.

i've been told the kx mini manual and the forum board where it stands is a good start ;)


Hi. The SourceForge site says that is the best place to go for support, but the forums here don't have v1 topics set up yet. And I don't want to log an issue on SourceForge for what is probably a user/environment problem rather than a code-level bug. Suggestions?

rncbc's picture

you can ask it right here. what's stopping you?

however, if you do have the nerve and fresh technical evidence on hand that something is persistently wrong, please shoot to the official ticketing system, that being the*v1/tickets sites, resp.


OK, that works.

The issue I'm seeing is that I'm unable to save presets in synthv1. The save button is grayed out. And from the screenshots, it's obvious that it does work under the right conditions. I'm guessing that there's some environment thing that isn't quite right on my system.

I was seeing this in v0.3.6 (from the Ubuntu repository), so I pulled down 0.5.0 and built from source, but that didn't have any effect. The one other thing I tried was to supply a not-yet-existing patch file name on the command line, which caused everything to be set to zero values instead of the normal defaults, but still no ability to save.

I get a few warnings on stdout, but nothing that appears to be related to this. Rather, I think they have to do with the fact that the synth isn't connecting to jack's system outputs automatically. But hooking that up manually isn't a big deal.

$ /usr/local/bin/synthv1_jack -v
Qt: 4.8.6
synthv1: 0.5.0

$ /usr/local/bin/synthv1_jack
Cannot read socket fd = 11 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open synthv1-01 client

$ grep 'define CONFIG' src/config.h
#define CONFIG_JACK 1
#define CONFIG_LIBLO 1
#define CONFIG_LV2 1
#define CONFIG_LV2_UI_IDLE 1
#define CONFIG_NSM 1

Let me know if you'd prefer that I open a ticket with this info.

rncbc's picture

you have to give it a (brand new) name, before the save-preset button is enabled.

for any existing, currently loaded preset name, the save-button is only enabled after you modify some parameter or setting.


Oh geez. I didn't realize you could type in the drop-down box. Thanks!

When you'll make it for windows?

rncbc's picture

there's nothing stopping you to make it to windows.

me instead, i have no interest on wasting my precious time on doing it for platforms that i don't even run or don't stay close anymore anyhow. sorry-.



Thank you so much for all your hard work on such an awesome program!

I have a couple questions I hope you don't mind I ask them here, if this is not the appropriate location please redirect me to the best place for this.

My plan is to use drumkv1 as a sampler to play real drum samples from my electric kit, and run that in to audacity or adour. My kit is a bit of a mish mash and I can't remember what all the triggers come in on. IE element 37 - side kick...I was wondering if it is possible to rename the elements to suit my kit?

Also I am trying to build 0.5.0 but I keep gettine errors when I try to configure, I am on ubuntu 14.04. Not sure what I am missing....dependacies? ./configure out put...

checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking how to run the C++ preprocessor... /lib/cpp
configure: error: in `/home/nick/Extra Installation Files/drumkv1-0.5.0':
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details

let me know if you would like config.log, it is pretty long I didn't want to post it up here.




Add new comment