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 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.

I haven't had a mobile phone for a few years now, and it's one of the best decisions I've ever made.

I do sincerely respect your stance, don't get me wrong.

but I believe you can have GH MFA on a desktop or web TOTP app. it's not exclusive to mobile you know?
(although it's a lot easier to register there just once thanks to QRcodes or whatever...:))

hth.
cheers

ps. take your time; as said this stuff will be only effective after this coming v1.4.3 release.

I can understand you. More and more companies try to force you to use a remotely administered (by Google or Apple) mobile phone.

But GitHub doesn't, see
https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication

A minimum setup could be oathtool, see
https://askubuntu.com/questions/1460640/generating-totp-for-2fa-directly-from-the-computer-no-mobile-device

I tested it by setting 2FA as described above and used oathtool --base32 --totp "mygithubprovidedscret" -d 6 to log in. Works.

Submitted by G3N-es on Sat, 29 Aug 2026 - 22:12

Permalink

It looks like it's finally going to be possible... I was able to access GitHub without any problems with my usual account G3N-es.

They seem to have simplified it quite a bit.
(although I still find it very confusing)

Using with login tools from multinational corporations still bothers me...
But really, once everything is set up, I'd only have to log in a week before each Vee One release (if it's truly necessary) to authorize, request formatting changes, or reject (if they don't meet the requirements) the new presets submitted.

Submitted by G3N-es on Thu, 3 Sep 2026 - 09:28

Permalink

I encourage you to experiment with combining presets by loading both synths simultaneously on a track.

For example:
[SlowCristal.padthv1]+[80SlowWinds.samplv1]
[Desert.padthv1]+[Orchestra_Ensamble.samplv1]
[Cave.padthv1]+[AnaVoice.samplv1]
Etc...

Personally, the results and possibilities never cease to amaze me.

https://github.com/rncbc/samplv1-preset
https://github.com/rncbc/padthv1-preset

Submitted by rncbc on Thu, 3 Sep 2026 - 16:22

Permalink

so, preppings are underway...

now, this may function as both an internal memo and an announcement that things are starting to taking shape and align in [develop] branch for the so called "factory presets" bundle and distribution to the masses... as said, posed to a next v1.5.0 release...

things to be aware this time:

  1. factory presets are installed to reside on "<CMAKE_INSTALL_PREFIX>/share/<PROJECT_NAME>/preset/" directory, permanently;
  2. for general distribution, these presets will be packaged into separate "<PROJECT_NAME>-preset" packages, for which CMAKE_INSTALL_PREFIX is usually set to "/usr" (ie. read-only for regular users);
  3. factory presets are automatically imported once when first running either the lv2 plugin or the jack standalone;
  4. if you already have at least one preset saved on premises, no factory presets will be imported automagically anytime; you must import the new installed or updated factory presets explicitly on your own, while preserving any existing ones;

ps. as you prolly know: CMAKE_INSTALL_PREFIX is set to "/usr/local" on default (also read-only for regular users) and PROJECT_NAME is one of "synthv1", "samplv1", "drumkv1" or "padthv1", obviously(?).

was this clear enough? when in doubt please ask. :)
thanks

So far, everything fits together perfectly in my mind. It seems like an ideal workflow.

Those without a custom banks can use the default ones; those with a personalized banks will have theirs respected.

It's been a joy for me to participate in all of this firsthand :)

We haven't accounted for the possibility of factory preset updates.

If the user is coming from a previous installation, the new presets will not be updated.

I believe the mechanism should be:
When entering the Presets tab, I compare the configured preset list with the presets installed on the system.
If I have factory presets installed that don't appear in the current configured list, a window pops up:

There are factory presets not included in your list. Do you want to add them?

[X] Don't ask again | OK | Cancel

If the user is coming from a previous installation, the new presets will not be updated.

yes, that's true and applies to what is postulated on points 3. and 4. in re. Factory Presets for VeeOneSuite...

so you want the user to have the so called "factory presets" in check? what if he/she deliberately removes one or more from the factory list? does he/she have to get the nagging every time ad nauseam, until he/she gets fed up and hit the "don't ask again" box? what about plugins already in production which don't even have to get their GUIs open every time they get loaded?

I think your intentions are good but, you know from that old adage, good intentions may open the gates of hell (from the inside) or maybe just a can of worms (which I think is the case:))

thanks anyway.

So, a checkbox in the general options: "Automatically update factory presets," and set to be disabled by default.

"What about plugins already in production that don't even have to have their GUIs open every time they load?"
There shouldn't be a conflict, since one of the rules of factory presets is that a individual preset can't be updated, only added:

https://github.com/rncbc/drumkv1-preset/blob/main/README.md#4-immutability-of-presets-and-samples

P.S.: This will only affect the presets, not the programs.

checkbox in the general options: "Automatically update factory presets," and set to be disabled by default.

that would be the way, indeed, but I still think, for the time being, that it would be better still to have the user decide whether he/she actually needs or wishes to update at all...

a simple note in the docs to import the updated preset/*.conf file(s) from time to time would be enough, again for the time being.

note: checking for preset updates would probably need an increasingly expensive runtime check routine, on every runtime instance startup, plugin and/or standalone, to make it supposedly work... sorry to tell, that's not going to fly... ;)

so, let's not overengineer this, shall we?
thanks

"factory presets are automatically imported once when first running either the lv2 plugin or the jack standalone;"

I'm not getting it to work on my computer... everything appears empty.
Maybe I'm doing something wrong.

Generated config file:

[ColorThemes]
KXStudio=/usr/local/share/drumkv1/palette/KXStudio.conf
Wonton%20Soup=/usr/local/share/drumkv1/palette/Wonton Soup.conf

[Custom]
ColorTheme=
StyleTheme=

[Default]
ControlsEnabled=false
FrameTimeFormat=0
KnobDialMode=0
KnobEditMode=0
Preset=
PresetDir=
ProgramsEnabled=false
RandomizePercent=20
SampleDir=
UseGMDrumNames=true

[Dialogs]
PresetsPreview=false
ProgramsPreview=false
UseNativeDialogs=false

[Program]
Version=1.4.3

[Tuning]
Enabled=false
KeyMapDir=
KeyMapFile=
RefNote=69
RefPitch=440
ScaleDir=
ScaleFile=

But they are not installed. Latest development version

-- Install configuration: "Release"
-- Installing: /usr/local/lib/lv2/drumkv1.lv2/drumkv1.so
-- Installing: /usr/local/lib/lv2/drumkv1.lv2/manifest.ttl
-- Installing: /usr/local/lib/lv2/drumkv1.lv2/drumkv1.ttl
-- Installing: /usr/local/lib/lv2/drumkv1.lv2/drumkv1_ui.ttl
-- Installing: /usr/local/bin/drumkv1_jack
-- Installing: /usr/local/share/icons/hicolor/32x32/apps/org.rncbc.drumkv1.png
-- Installing: /usr/local/share/icons/hicolor/scalable/apps/org.rncbc.drumkv1.svg
-- Installing: /usr/local/share/applications/org.rncbc.drumkv1.desktop
-- Installing: /usr/local/share/metainfo/org.rncbc.drumkv1.metainfo.xml
-- Installing: /usr/local/share/mime/packages/org.rncbc.drumkv1.xml
-- Installing: /usr/local/share/icons/hicolor/32x32/mimetypes/org.rncbc.drumkv1.application-x-drumkv1-preset.png
-- Installing: /usr/local/share/icons/hicolor/scalable/mimetypes/org.rncbc.drumkv1.application-x-drumkv1-preset.svg
-- Installing: /usr/local/share/man/man1/drumkv1.1
-- Installing: /usr/local/share/man/fr/man1/drumkv1.1
-- Up-to-date: /usr/local/share/drumkv1/palette
-- Installing: /usr/local/share/drumkv1/palette/Wonton Soup.conf
-- Installing: /usr/local/share/drumkv1/palette/KXStudio.conf
-- Up-to-date: /usr/local/share/drumkv1/preset

Submitted by G3N-es on Mon, 7 Sep 2026 - 10:39

Permalink

I've thoroughly reviewed all the presets. Something might have slipped through the net, but nothing dysfunctional.

I think they're ready. I've attached a mini-demo of the new DrumkV1 presets.

File attachments
demo_DrumkV1_Presets.qtz

Submitted by rncbc on Mon, 7 Sep 2026 - 10:59

Permalink

good!

fyi. they are also packaged to the repos as:

  • synthv1(-preset) >= 1.4.3.6git.3e2042
  • samplv1(-preset) >= 1.4.3.8git.ab5e29
  • drumkv1(-preset) >= 1.4.3.8git.de17d0
  • padthv1(-preset) >= 1.4.3.6git.da60d2

thank you
cheers

UPDATE: and rather IMPORTANT for samplv1 and drumkv1 presets only:

@G3N-es: you'll need to add this line right after <samples> (samplv1) and <elements> (drumkv1):

<sample-rate>SAMPLE_RATE</sample-rate>

to all your samplv1 and drumkv1 presets, being SAMPLE_RATE the reference sample rate (in frames per second) of your jack/pipewire engine at the time you save sample offset and loop ranges; otherwise users will get a severely bad experience if he/she has any other sample-rate than yours when loading those presets any other time.

sorry for this one-time inconvenience; the latest samplv1 and drumkv1 above already saves this to preset files alright, but current factory presets, at the time of this writing, don't have it.

again, this applies to samplv1 and drumkv1 presets only, all others are fine.

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.