Proposal: Factory Presets for VeeOneSuite

Submitted by G3N-es on
Forums
General discussion

Now that we have bank functionality, why not factory presets?

Reasons:

  1. Educational: Nothing helps more in learning than seeing examples.
  2. Shows the true possibilities of the plugin: As I've already mentioned, the presets I found for SynthV1 and PadthV1 were very aggressive, and I thought they were only capable of making those kinds of sounds... So it took me a long time to give them a try.
  3. They are a starting point, a template for the user to build their own presets from the existing ones. If I want a piano-type sound, I start with a piano, etc.
  4. I think it's a request from all VeeOneSuite users the first time they open it: Where are the presets?

Proposal:

I'm willing to create presets that meet the following factory preset requirements:

  1. They must have acceptable quality.

  2. They must showcase the plugin's extra capabilities (especially in DrumkV1 and SampkV1, where you can get a lot out of a simple audio waveform thanks to their synthesis tools).

  3. They must not exceed 512 kilobytes per synth.

What do you think?

Submitted by rncbc on Wed, 19 Aug 2026 - 14:07

Permalink

I do also love the idea,

however, there's always the proverbial "but" (or "buts") ;)

  • synthv1 and padthv1 are straight forward, as the preset files are fully self-contained;
    but,
  • samplv1 and drumkv1are yet another story: these rely on audio sample files that are prone to licensing issues and whatever it might ensue.

on another slope of thought, preset banks are currently a user's prerogative, they are not implied nor suggested in any (factory) ontology or else, so to speak.

but factory presets are still a (very) good idea; let's push it further ahead and hope to make it for the v1.5 milestone.

wholly cheers!

Submitted by G3N-es on Wed, 19 Aug 2026 - 15:06

Permalink

Let's wait for version 1.5.

For my part, I'm still developing the script with sampling tools focused on drumkv1.

Now it's possible to get this in just a few minutes, completely automatically. A Rothes piano sampled from the EP-MK1 plugin with a bit of LSP chorus. (attach)

I'll share the script when it's more polished.

File attachments
RodesOGG.zip

Let's wait for version 1.5.

no, v1.5 is the one proposed to have such "factory presets" already, which means they will be part and integral to the upstream source distribution

that is what I mean with "factory presets" here, in this context, get it?

So I understand that the proposal has been accepted.

I'll begin creating the presets, which will of course be open for discussion so I can tweak, remove, or add others, whether mine or not, as long as they have a CC public domain license. Any other type of license is a hassle for factory presets in a libre project.

Submitted by G3N-es on Fri, 21 Aug 2026 - 20:57

Permalink

I went over the size limit, 1.5 MB.
I couldn't stick to 0.5 MB, but I think it was worth it.

The only external library used is Virtuosity SFZ, a universal CC license.
Famous and reliable. No licensing issues.
https://github.com/sfzinstruments/virtuosity_drums

The Rhodes, as I mentioned, was sampled from a well-known VST2 modeling synth.
The sounds recorded from synthesizers are not subject to licensing; it's like recording an acoustic instrument.
https://github.com/MikeMorenoDSP/EP-MK1

The SFZ and plugin names is also included in the preset as acknowledgment.

The other samples were taken from SynthV1 presets, except for some handclaps I recorded myself.

Banks:

Drum:

  • VeeOneDrum
  • Virtuosity
  • Urban (a recording of the two previous ones triggered simultaneously and with some saturation effects)

Melodic:

  • EP-MK1_Rhodes

Chords:

  • Chords_EP-MK1_Rhodes

PS:
SamplV1's turn.
I will use the samples already created for DrumKv1, I will create them from the SynthV1 presets, or from my own recordings.

PS2:
I've re-uploaded them. Since I edited them with a text editor, Urban wasn't properly recognizing the compressor activation.

Submitted by rncbc on Fri, 21 Aug 2026 - 22:36

Permalink

title says it all!

you'll certainly need this to backup/restore your whole layouts: check it out under Help > Configure... > Presets

big caveat: all presets are currently (de)referenced in and out as absolute paths, so it's not really ready to share the exported files (eg. *.synthv1.conf) to the world, but it's a good start (or is it not?)

hth.
cheers

UPDATE: the absolute/relative issue is now closed. enjoy.

One last request.

Configure > Programs:

At the bottom, after the "Enable" option, add an "Add from Presets" button with an import icon.

This will read the "Presets" list and add them to "Programs," numbering them starting from the last existing bank number in the Programs list.

In other words, they would be added after the existing programs.

if the programs are changed from within the track, it has no effect.

what do you mean exactly? is that about Program-Change channel messages within a loaded MIDI clip sequence?

if yes, perhaps you should know (by heart already?) that qtractor despises, ignores and even drops all of them on save.

as a pretty ancient rule, the MIDI bank/program that is set on a MIDI track/channel properties is highly honored and takes over exclusive precedence and effect to the whole MIDI track's setup; you'll need to reset both to "(None)" if you actually want to take it back.

is that it?

No, that's not it. Changing the program simply has no effect on the synthesizer.

In other words, if I choose the program I'm going to use from the track, without opening the GUI, just for convenience... the sound doesn't change.

I know that to avoid conflicts, it has to be done (from any Synth plugin that supports programs) either from the track and only from the track (some don't have a GUI), or from the GUI and only from the GUI.

Any other plugin that supports programs does the job, changing the sounds, but SynthV1 (and probably the other VeeOne plugins) doesn't.

It seems like an old bug.

PD
Confirmed, it affects all VeeOne apps and plugins, and can even block the app and/or plugin.

I've only done a very cursory test, but it seems to be fixed.

If we're going to add the factory presets, it would also be interesting if the programs for those presets were also factory-configured. Obvious?... but I thought it was worth mentioning.

Hmm... It looks like everything is ready for VeeOneSuite 1.5.

Thanks!

Submitted by G3N-es on Sun, 23 Aug 2026 - 14:13

Permalink

@bluebell and Rui:
If you have time to test them and share your impressions, that would be great. You'd be doing me a favor.

SynthV1

https://www.rncbc.org/drupal/sites/default/files/SynthV1_Presets.zip

DrumkV1

https://www.rncbc.org/drupal/sites/default/files/DrumKv1Kits_V2.26-08-2…

SamplV1

https://www.rncbc.org/drupal/sites/default/files/SamplV1Presets26-08-23…

PadthV1, UPDATE: 23-08-2026 23:20

https://www.rncbc.org/drupal/sites/default/files/PadthV1Prestes26-08-23…

File attachments
DrumkV1_pr.png

Submitted by G3N-es on Wed, 26 Aug 2026 - 17:56

Permalink

A few more instruments have been added to SamplV1 and PadthV1.
Each bank is in the same folder as its corresponding preset.
The following metadata has been added to each preset:

<preset name="Example" collection="Vee One Factory" author="G3N-es" license="Creative Commons Zero (CC0) 1.0 Universal">

I hope you enjoy them.

Regards

File attachments
VeeOnePrests26-08-26_19-48.zip

Submitted by rncbc on Fri, 28 Aug 2026 - 19:03

Permalink

let me add something to the proposal...

let the so called factory presets be open and community managed, say, reside on a github repo and a project on its own... (eg. github.com/rncbc/synthv1-presets)

two points here:

  • factory presets shall be imported as git submodules to the respective projects;
  • even so, they shall be distributed as separate packages (eg. synthv1-presets).

i'll leave the idea here for a moment, but pending further discussion ntl.

cheers

I think it's a great idea.

#Requirements
But we would need to establish some requirements for sharing.

1_ Creative Commons Zero (CC0) 1.0 Universal License:
This applies to both presets and samples. Any other type of license requires generating extra documentation that is unmanageable. Those who share are responsible for being the original author of the samples/prests or having started with samples licensed under a universal license.
If someone claims copyright, we will proceed as on other platforms: verify if it is true and remove it if so.
Since we clearly specify that the responsibility lies with the uploader, this should not cause legal problems.

Examples of compatible and incompatible libraries could be added to the text for greater clarity. This also makes it easier for creators to access compatible libraries and avoids temptation.

Example:
Compatible: Virtuosity, karoryfer, Sitala...
Incompatible: AVL Drums, Drumlabooh...
(Theoretically, Drumlabooh is compatible, but when you check the Kit documentation, you'll see that it acknowledges that there are no guarantees.)

EDITED!!!
We would significantly simplify licensing risks if only sharing samples of original works were permitted, or if they were based on the universal license library list that we provide.

I have more or less identified the most significant ones, and they cover all the needs:
Electronic and live percussion instruments.
Piano and orchestra.

2_ You cannot update/overwrite an existing preset or sample; it must be uploaded with a different name:
The reason is to ensure the consistency of projects over time. If I used preset X in my track, the project should sound the same 10 years later. If someone "improves" the preset... it could ruin previous projects.

3_ Samples must be OGG and not exceed 100 KiB per sample.

4_ Upload a new sample only if absolutely necessary:
Using existing samples and editing them in the synthesizer is preferred. This helps keep presets lightweight and avoids many potential license conflicts.

#Technical Development

1_ Metadata
It would be necessary to be able to add the following when editing the preset:

  • Collection
  • Author
  • License
  • Date
  • Comments

Alternatively, provide a reference so that authors can edit the preset header with a metadata editor. Texts.

<!DOCTYPE $NAME_SYNTH>
<preset name="$NAME_PRESET" collection="Vee One Factory" author="" license="Creative Commons Zero (CC0) 1.0 Universal" date="">
<comments></comments>

2_ Alternative Sharing Method
Creators don't necessarily know how to use Git; they're musicians or sound designers... They might not agree with GitHub's policies.
I think it would be sufficient for now if the website had a section where presets could be shared, editable only by identified users.

After that, you'd have to upload them manually... but I don't think participation would be massive.
If it were, a Drupal module would have to be developed to automate the task.

Submitted by rncbc on Sat, 29 Aug 2026 - 14:17

Permalink

well, everything you said is about totally right...

but I'm actually asking about technical implementation, not quite the ethical parts of it, which I think you've nailed it quite impressively, thanks.

so, let's (re)start with a question, to you @G3N-es in particular: as it is you that will a major collaborator to this effort, regarded as the initiator, do you have any issues with making it as github.com repos?

fyi. I've already created these:

(nb. all repos are CC0-1.0 licensed.)

Now, if you just give me your GH handle, I can grant you full privileges to manage any of those yourself, including adding the README file with all your licensing concerns, as much as you exposed above.

this way the community aspect of it will be handled through regular PRs and thus subject to yours approval, of course.

what do you say?
cheers

ps. you reckon that the repos are already populated with your latest presets bundle (VeeOnePrests26-08-26_19-48.zip)

Submitted by G3N-es on Sat, 29 Aug 2026 - 14:46

Permalink

My problem with Git in general is that I find it cumbersome, counterintuitive, and overly restrictive.
But I can make an effort.

My problem with GitHub is insurmountable since they started requiring two-factor authentication. I haven't had a mobile phone for a few years now, and it's one of the best decisions I've ever made.

My account is a ghost account. It exists, but I can't access it or delete it.

Add new comment

The content of this field is kept private and will not be shown publicly.

Markdown

  • Parses markdown and converts it to HTML.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id> <img src alt height width> <strike> <pre> <p> <br>
  • Lines and paragraphs break automatically.

Filtered HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <b> <i> <pre> <img src alt height width> <strike>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
File attachments
Unlimited number of files can be uploaded to this field.
2 MB limit.
Allowed types: jpg jpeg gif png txt doc docx xls xlsx pdf ppt pps odt ods odp zip gz bz2 xz patch diff wav ogg flac ogv mp4 qtz.