PRESET

Forums

Hi where could I find some presets to add in synthv1? do you have a referral link? What extensions does it accept?

Permalink

I'm creating a collection of SynthV1 presets for personal use.
The first batch consists of pianos.

I'm sharing them to see if they're usable enough to share on SourceForge.

Would you remove any, all of them, or add others?
Any feedback is welcome.

File attachments

many thanks for sharing this

looking forward to the next batch(es)

cheers

ps. remind me a better kind of a preset manager is in order: a plain and flat drop-down list is rapidly becoming a nuisance , i guess :)

Permalink

"ps. remind me a better kind of a preset manager is in order: a plain and flat drop-down list is rapidly becoming a nuisance , i guess :)"

IIt's annoying, but bearable. Although, if it could be improved...
I have some pending requests for Vee One Suite, if its made sense to you, but I'll wait until the summer heat subsides a bit ;).

Here's my collection. One of the reasons I created it is that the presets available online were very focused on EMD music: harsh and aggressive. I needed something more subtle and balanced. I think I've achieved it. I'm happy... and I had a great time :).

Presets4_SynthV1.1

  • Author: G3N-es
  • License: Creative Commons Zero (CC0) 1.0 Universal
  • Date: 08/08/2026

51 presets for SynthV1: https://sourceforge.net/projects/synthv1/

Include:

  • 00_PianoGrandPiezo.synthv1
  • 01_PianoBrightGrandPiezo.synthv1
  • 02_PianoAndBass.synthv1
  • 03_PianoMellow.synthv1
  • 04_PianoHonkyTonk.synthv1
  • 05_PianoRhodeX.synthv1
  • 06_PianoWurlEZ.synthv1
  • 07_PianetE.synthv1
  • 08_PianoE-DX.synthv1
  • 09_PianoToy.synthv1
  • 10_ClavinetE.synthv1
  • 11_OrganOld.synthv1
  • 12_OrganModern.synthv1
  • 13_Acordion.synthv1
  • 14_Armonica.synthv1
  • 15_GuitarAndaluza.synthv1
  • 16_GuitarSteel.synthv1
  • 17_GuitarJazz.synthv1
  • 18_BassAndGuitar.synthv1
  • 19_GuitarAmp.synthv1
  • 20_StrWW_Litany.synthv1
  • 21_Violin.synthv1
  • 22_Cello.synthv1
  • 23_Brass.synthv1
  • 24_BrassSlow.synthv1
  • 25_WoodWind.synthv1
  • 50_SynthRemember.synthv1
  • 51_SynthStaticTheremins.synthv1
  • 52_SynthtElectricHIT.synthv1
  • 53_SynthPercuBrass.synthv1
  • 54_SynthTribal.synthv1
  • 55_SynthtPulse.synthv1
  • 56_SynthtPianoAndChorus.synthv1
  • 57_SynthBass.synthv1
  • 90_FxSiren.synthv1
  • 91_FxBirds.synthv1
  • 92_FxNoises.synthv1
  • 99_ClapD2#.synthv1
  • 99_Claps.synthv1
  • 99_CowbellG3#.synthv1
  • 99_CrashBroken.synthv1
  • 99_Crash.synthv1
  • 99_HitHatF2#.synthv1
  • 99_HitHatOpenA2#.synthv1
  • 99_HitHatPedalG2#.synthv1
  • 99_KickB1_TomG3.synthv1
  • 99_KickC1_TomG2.synthv1
  • 99_KickC2.synthv1
  • 99_SideStickC2#.synthv1
  • 99_SnareD2.synthv1
  • 99_SnareE2.synthv1
File attachments
Permalink

once again, thanks, a lot!

news are current git head main/develop already feature an improved preset manager (kinda) allowing you to organize all your presets in banks or categories and arrange them in any order you want (via drag-n-drop), whatever...

all of that on the whole vee-one range:

  • synthv1 >= v1.4.2.8git.6e4524
  • samplv1 >= v1.4.2.7git.68fd5e
  • drumkv1 >= v1.4.2.8git.4a028f
  • padthv1 >= v1.4.2.8git.30bd14

double thanks if you're willing to step up for the beta-testing ;)...
enjoy!

EDIT: here's for the (new) looks:

EDIT2: updated refactored versions and 2nd screenshot.

I think Drupal or server has banned me. I haven't been able to visit the website for two days.
I set up a VPN just in case, and sure enough...
(I suppose it's my fault; when I close the browser, the website tab often remains open. When I reopen it, the website loads... which generates a lot of traffic, and I suppose Drupal or the server configuration finds that suspicious).

....

Now, let's get to the testing. I've only done it on SynthV1:

Buts

It's certainly much nicer and more organized now. However, I've found "buts":

1_
Grouped presets can't be scrolled through with the mouse wheel, and I consider this unacceptable to the point (in my case) that I won't use this new preset bank functionality.

I've come up with a possible solution:
Two lists, one combo box:

  • The collapsed list: List of all presets without groups. The group is displayed in a tooltip (similar to how it was done in the values ​​section for plugin shortcuts in Qtractor, which can be scrolled with the mouse wheel).

  • Expanded list: The current list.

I believe that by doing it this way, it might also be possible to collapse the groups in the expanded list.
This would allow for the following workflow, which I consider optimal:

  1. Expand.

  2. Collapse groups that are not of interest.

  3. Select the first preset of the group that interests me, and from there scroll through using the mouse wheel.

2_
This is useful for users to organize their presets, but the banks themselves cannot be exported or imported, which is not helpful for sharing presets, creating stable collections, etc.
In other words, the presets still have to be numbered, since I can't export the bank in a specific order.

Other considerations:

  1. With the LV2 GUI, text editing in the Combobox fails, and it doesn't allow text editing in the Spinbox. I assume this is due to my LV2 compilation libraries.

  2. Everything works fine with an external GUI.

I will open a new topic to discuss GUI selection in Qtractor, as I have questions about how it works.

Pending request

I mentioned in a previous post that I was going to request new features for Vee One Suite; however, I've come to the conclusion that they weren't worthwhile.

Anyway, I'll bring them up again so as not to leave you wondering.

  1. Metadata Management for Presets: (author, license, date...): This doesn't make sense, since very few people actually share presets, and those few do so only sporadically. The metadata can be included with a text editor or with accompanying documentation. It's not worth adding a specific internal feature.

  2. MIDI Note Filters: The goal is to be able to use multiple synthesizer instances to create drum kits. But... it's not efficient. It's better to render each trigger and assemble them in DrumkV1.
    "it would be best to split the sample into separate files, one for each key/element, don't you agree?"
    However, it remains a very laborious task for which I haven't yet found an efficient workflow.

The most I've managed is this:

  1. Recording: The most efficient way is to record all the instruments in a single recording.

  2. Editing the beginnings and ends of each instrument (we're talking about at least 16 instruments).

  3. Exporting: Again, exporting a single file is much more efficient.

  4. Importing into Tenacity: This allows you to assign tags and export the sampled data in chunks, following the name of each tag. Create each tag and name it 16 times... and export.

Ideally, I'd have a percussion sampler that allows you to directly record the triggers and save them in its own internal state format, or in external files with a predefined format, e.g., KitName_NoteNumber.

A task that currently takes me hours would be reduced to seconds.

But it doesn't exist. Fabla 2 was heading in that direction but remained in alpha.

EDITED:
Now it already exists. https://www.rncbc.org/drupal/node/2946

Grouped presets can't be scrolled through with the mouse wheel, and I consider this unacceptable to the point (in my case) that I won't use this new preset bank functionality.

refactored the bank/preset drop-down list to fit the bill, please confirm

cheers

Now it works!!! Thanks :)
I've added a folder emoji. It's definitely clearer with the icon. I don't know if there's a way to include the folder image by default.

If not, and perhaps a better visual solution, highlight the color of the groups somehow to differentiate them from the presets.

I still think the tooltip should display the bank/group name.

Another observation, as already happens in Qtractor with buses and plugins:
Before when creating/adding a new preset, it used to be sorted alphabetically. Now, it would make sense for it to be created right after the original (edited) preset, not at the end of the list. When we create a preset based on another, it's usually a version of or related to the other, so the logical place to create it is after the previous one.

## Bugs detected

1. If no preset exists, the preset manager appears disabled.

2. Falsely modified when scrolling through presets with the mouse wheel. This only happens the first time you import presets and create groups from the preset manager. Once you close the instance and reopen it, everything works correctly.

It's definitely clearer with the icon. I don't know if there's a way to include the folder image by default.

added, but note that the bank items are grayed-out so the folder icon will too.

  1. If no preset exists, the preset manager appears disabled.

fixed. it was a left-over from the Programs tab which is should be fully disabled when there are no saved presets to select.

  1. Falsely modified when scrolling through presets with the mouse wheel. This only happens the first time you import presets and create groups from the preset manager.

k. will need to repro this somehow.

seeya

I understand you're referring to reproducing it. I've tested it from SynthV1 LV2; it might not happen in the desktop application.

Delete all presets from the manager. Delete the instance.
Load a new instance.
Create two or more groups with content from scratch.
Then, in the Combobox, scroll through all the presets with the mouse wheel.

When you jump to the second group, the preset appears as modified, as shown in the GIF. This has been happening since at least the previous implementation (bis).

Interestingly, if you delete the instance and load a new one, the problem disappears. The presets behave correctly. It only occurs the first time they are created, from the instance they are created from.

Before when creating/adding a new preset, it used to be sorted alphabetically. Now, it would make sense for it to be created right after the original (edited) preset, not at the end of the list. When we create a preset based on another, it's usually a version of or related to the other, so the logical place to create it is after the previous one.

this is also now hopefully in place, since the latest revisions:

  • synthv1 >= 1.4.2.13git.77b31d
  • samplv1 >= 1.4.2.12git.e15685
  • drumkv1 >= 1.4.2.13git.997b50
  • padthv1 >= 1.4.2.13git.5efb97

keep on
thanks

EDIT2: updated series (see below)

Bugs:

1_Combobox

* If presets are added from the combobox, they load in reverse order.
* Even if all presets are deleted from the manager, the last one deleted still appears in the combobox.
...

2_Preset Manager

* The Bank button doesn't create banks and may crash.

___

Other considerations:

In the Preset Manager, change the "x" icon to an "eraser" to make it clear that presets are erased but not deleted, unlike in the combobox.

Regarding the folder icon, perhaps it should be changed to a neutral color to maintain consistency.


Edit: I suppose it's due to a disabled state, so changing the icon doesn't solve anything; there will always be a difference.

1_Combobox

If presets are added from the combobox, they load in reverse order.

fixed.

Even if all presets are deleted from the manager, the last one deleted still appears in the combobox.

maybe fixed

2_Preset Manager

The Bank button doesn't create banks and may crash.

fixed.

(new versions updated above)

many thanks for your findings (continued)
cheers

We're almost there.... :)

It seems it won't save new presets... I lost two cool new ones because of this :( , flutes and bassoon... but I understand the logic, so I can easily recreate them.

I thought there wouldn't be, but yes, there will probably be a second, expanded version of presets.

Permalink

The percussion was created by rendering the percussion presets and assembling/editing them in DrumkV1.

ok, this is just about a PoC, isn't it? the problem here is about efficiency, mostly in ram but cpu takes its toll every one-time the preset is loaded: you see, each element or key loads the whole sample file only to use an small excerpt of it

it would be best to split the sample into separate files, one for each key/element, don't you agree?

seeya

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.