VeeOneSuite presets and samples

Hi,
First of all, I wanted to say thanks for this great new feature! I’m happy to admit that I’m one of those people who really love presets and the included samples. It also makes getting started much easier for new users, since you can just jump right in. Not everyone enjoys tweaking their own sounds, and not everyone has an existing, well-organized sample library. You can always start with presets and tweak them later, or at least see how the sounds were created and learn something. Great stuff!
I’ve discovered that on Debian, you install them by adding the appropriate preset packages: sudo apt install samplv1-preset synthv1-preset drumkv1-preset padthv1-preset.
After that, the corresponding folder is automatically selected in the preset browser, giving you instant access. Awesome!

However, I do have a few questions about these great presets and samples for the VeeOne Suite.

  1. Where on the system's hard drive are these presets and samples stored?
  2. Can I change the storage location later?
  3. Can I mix and manage my own presets alongside them? Wouldn't the location used for the "official" presets be better for that purpose?
  4. As I understand it, these presets and samples are a work in progress, meaning new ones might be added with each update. How are the new presets managed alongside the existing ones and my own user presets? Are the "official" presets simply supplemented with the new ones while everything else remains unchanged?
  5. What is the best way to save the presets and samples if I want to send a song project to someone else? qtz? qtr?
  6. Wouldn't it be better—as happens with LMMS after the first launch—to automatically create a folder named "VeeOneSuit and Qtractor" in the Documents directory, containing subfolders for samples, presets, song projects, templates, etc.?
    I’m just wondering what the best approach would be if you have multiple PCs, or if you simply reinstall your operating system and want to transfer your song projects, templates, presets, samples, audio/MIDI files, and loops. Reorganizing old collections and projects is always a hassle—especially if you’ve spent years working on Windows and Mac and have installed all sorts of things—but perhaps it’s easier if you start doing it early on, simply because the DAW suggests it and provides a solid structure? :-) That last part was a bit of a joke at my own expense.

Many thanks again to everyone involved!

Best regards!

Permalink

  1. Where on the system's hard drive are these presets and samples stored?

example for samplv1: the samplv1-preset package usually installs the presets and samples to /usr/share/samplv1/preset.

  1. Can I change the storage location later?

no. once installed and imported automatically you cannot change the location.

  1. Can I mix and manage my own presets alongside them? Wouldn't the location used for the "official" presets be better for that purpose?

you can save your own presets anywhere else but the so called "factory" location (1.) which is usually read-only ie. not writable to regular users.

  1. As I understand it, these presets and samples are a work in progress, meaning new ones might be added with each update. How are the new presets managed alongside the existing ones and my own user presets? Are the "official" presets simply supplemented with the new ones while everything else remains unchanged?

once installed (2.) you'll need to re-import the collection on your own and manually (see menu Help > Configure... > Presets > Import..., then browse and choose this file /usr/share/samplv1/preset/0Factory.samplv1.conf) but only for new factory presets if any to take effect; old existing ones are automatically updated in place.

  1. What is the best way to save the presets and samples if I want to send a song project to someone else? qtz? qtr?

you're probably confusing vee-one's presets with qtractor's songs or projects; qtractor have no clue of any plugin's presets whatsoever, nor does it saves any of them at all (as much as any other DAW for that matter).

if talking about qtractor song or project portability, the zip/archive format (.qtz) is then fit to the purpose.

  1. Wouldn't it be better—as happens with LMMS after the first launch—to automatically create a folder named "VeeOneSuit and Qtractor" in the Documents directory, containing subfolders for samples, presets, song projects, templates, etc.?

nope. you're completely free to organize your stuff as you see fit to your liking; qtractor doesn't dictate any location in particular nor in general -- the same with the vee-ones -- you the user is in full charge, not the software.

hth.
cheers

Permalink

"you the user is in full charge, not the software"

Hi Hattori, that’s the approach, and although I had my doubts at first, I have to admit Rui got it spot-on again.

Deep down, it’s very simple:
In the settings, there is a preset manager.
If the user doesn't have any presets, the factory ones are loaded so they have something to work with.
If the user already has presets configured, no extra ones are loaded.

What’s the best way to organize it? That’s up to you.

However, in your case—since you prefer updating via apt—I think the most logical approach is:

1_ Personal presets
Create a local location for your personal presets.
That’s where you’ll store your personal presets and your bank configuration (the .conf file).

2_ Personal banks
So, export the current configuration (which includes the factory presets) to your local folder.
MyPresets.drumkv1.conf, for example.

3_ Save your own kits in that folder.

4_ Add your personal presets via the manager and re-export MyPresets.drumkv1.conf.

5_ Updating factory presets:
After installing them via apt import them from /usr 0Factory and re-export MyPresets.drumkv1.conf to your local folder.

If you want to stick with the apt approach but keep all samples and presets available in the same folder, you can create symbolic links in your personal folder pointing to the original files in /usr.

Whenever you update, just drag them all over again and choose "do not overwrite"; that way, only the new ones get copied.

....

My approach is different, though. I prefer downloading things manually and managing everything locally.

I created a "presets" folder within the plugin directory (drumkv1.lv2) and store everything there—both personal and factory presets.

Why? Because I believe that if they are plugin resources, that’s where they belong. What if I want to use those samples for something else in Qtractor?
Simbolic links to those resources are copied into my "System Samples" folder.

Each element is responsible for its own resources and then shares them—globally, in this case—via direct links so they are available to other applications.

I hope that clears things up a bit.

Permalink

Thanks for the replies. I still need to play around a bit with the presets, but I think this new feature is great. I haven’t quite decided on the best way to manage my presets yet—I have the new VeeOne presets, plus my own that I’ve created for these fantastic instruments. On top of that, I have some custom presets for effects—specifically for compressors and EQs from x42 and LSP—that I use all the time. I also like to keep my collection of samples and loops handy whenever I set up a new PC.
If Qtractor were to include a few basic, built-in effects—like an EQ, a compressor, and perhaps a delay—it would become a DAW that any beginner could start using right away.
I don’t mind installing Qtractor and the VeeOne plugins separately, and I’m sure there are good reasons for keeping the projects distinct, but I would personally prefer it if everything came as a single installation package—a complete DAW including plugins, presets, samples, and other content. With the VeeOne Suite, you have to install each plugin individually, and each one can require up to four separate packages (on Debian, it’s even more now, with the addition of plugin-preset packages). This contrast becomes especially clear when you look at something like LMMS, which comes as a single package—a single program. Ardour also seems to lean toward an integrated approach, which is further highlighted by its new feature that allows users to download MIDI files, loops, and samples directly from within the application.
Just a few thoughts. In any case...
Once again, a big thank you to everyone involved in these updates to Qtractor and the VeeOne Suite (which, in my mind, are all part of the same thing) :-)
Best regards!

Permalink

I think you’ve correctly intuited that the "Factory Presets" are a small step in the direction you’re suggesting.
I don’t mean to say they were created specifically with that intent, but rather that they represent a step that makes achieving something like that easier.

Your idea (which is also mine) doesn’t depend on Rui. What you’re calling for is a form of integrated—and, I would add, portable—distribution.
This could be achieved by anyone using what already exists within Qtractor, the Vee One suite, and other complementary free/open-source software (compressors, EQs, etc.).

The approach to achieve this would involve:
An AppImage + resources (presets, samples, plugins) + a Bash launcher that automates/manages configurations and resources + a user-friendly directory structure.
To avoid duplicating resources, symbolic links could be used.

However, pulling something like this off is a titanic task. Simply creating the factory presets required an enormous effort—one that, apart from you, has received no response.
Just devising a viable technical approach to create a portable distribution for Qtractor took me weeks, and part of that process is documented here on the forum.

Issues already addressed by the factory presets:

When working on these presets, I was essentially working in the dark—no one was testing my work. For instance, I’ve realized over time that the kick drums in the "VeeOneDrum" preset turned out a bit weak, lacking punch.
The reason is that I accidentally trimmed the original attack. During the creation process, you tend to focus on very specific details, and obvious things like this can easily go unnoticed.
It’s too late to fix them now. That said, they aren’t necessarily "bad"—they just could have been better.

These, however, can still be tested:
https://www.rncbc.org/drupal/node/2964

...

When I read posts on linuxmusicians.com, I get the impression that people are keen on seeing major proprietary brands make their binaries compatible with Linux.
Whenever something like that happens, it tends to generate a lot of buzz and engagement.
Yet, when individuals share their own tools—contributing to the creation of a free ecosystem—the response is usually quite muted. Is it wrong? Perhaps not, but it is beyond my understanding.

That’s the current landscape...

Single package: A portable, self-contained distribution of Qtractor, complete with all its resources.
What’s stopping you? It’s in your hands.

I have established a small, routine structure for managing my music data—such as projects, WAV files, and samples—but the real challenge lies in remaining disciplined and keeping things organized. This also means making an effort to delete items I don’t use, such as presets, samples, loops, or even plugins. Ultimately, this is a challenge that everyone likely has to solve in their own way.
Personally, I have no trouble installing a DAW and plugins, as I’ve done it many times before. However, for a new user, it would certainly be much easier if there were a package containing a few essentials, allowing them to get started right away.
This brings us to the point you raised: the visibility of—and the response to—new features, such as the excellent new presets.
It has certainly struck me that Mr. Capela’s software doesn’t receive the attention it truly deserves. I find it quite strange how little it is discussed on social media—platforms like YouTube, Reddit, or even forums like linuxmusicians. In my view, no other Linux DAW embodies the spirit of FOSS and Linux quite like Qtractor—along with the Vee One Suite, qpwgraph, and the other "Q" tools. The software is constantly being improved, its feature set is expanding, and—as seen here in the forum—user inquiries are addressed immediately.
Perhaps a great many people use Qtractor and are so satisfied with it that they simply feel no need to talk about it? I suspect, however, that the reasons are more complex and that there is no single, simple explanation.
One factor is likely that the most popular audio/video-focused Linux distributions come with Ardour pre-installed. Fortunately, in my view, these distributions will continue to lose popularity—at least in their current form. Another reason likely lies in the prevailing zeitgeist and mindset, even among experienced Linux users—something quite evident, for instance, on the LinuxMusicians forum. It’s not so much an issue that new users there ask about proprietary solutions; rather, it strikes me as distinctly odd how frequently proprietary software is recommended in those discussions.
When discussing growth and adoption, one must also consider the ability to reach new users. Software like Ardour or LMMS doesn’t spread simply by keeping existing users happy—though that is certainly important—but rather by attracting new ones. For newcomers, especially in an era defined by a desire for "instant gratification," it is crucial—or so I believe—how quickly and effortlessly one can achieve a sense of satisfaction when using the software. In the context of DAWs, this means: how quickly can I get a sound in or out? How soon can someone move past the technical hurdles and start having fun? Let’s be honest: regardless of the operating system or the music software being used, 99% of users are not professionals—they are hobbyists looking to enjoy their free time.

Just a few thoughts I wanted to share.

Best regards!

By the way, I forgot to mention that when I spoke of simple, built-in "bread-and-butter" effects for Qtractor, I was referring to something like the effects already integrated into the Vee One plugins.
These include a chorus, flanger, phaser, delay, reverb, and even a one-knob compressor. Unfortunately, they can currently only be used with the Vee One instruments. It would be great if these effects could also be applied as standalone, simple plugins—for instance, on a vocal track. The only other things that might be missing in Qtractor would be a basic EQ plugin and a compressor that offers a bit more functionality than just an on/off switch. I imagine that with the addition of new presets, samples, the built-in instruments, and perhaps the existing effects—made available as separate, simple plugins—Qtractor would be pretty much complete.
Since each "Q" software component can already be installed individually, that doesn't need to change; rather, I’m suggesting an additional installation bundle that would allow all these "Q" packages (the essentials) to be installed as a single software suite.
As a former Reason user, I often used the simple effects found in Reason—which were originally designed and programmed only for its synthesizers—on vocal tracks and guitars as well, once Reason introduced support for audio tracks. Even later, when better built-in effects and a new mixer (with its own EQs and compressors) were added, I still frequently reached for those original, simple synth effects when working with audio tracks.

I have no way of gauging the level of effort required to turn the effects from the Vee One suite into standalone plugins, but that is precisely what I had in mind when I mentioned the idea of ​​simple, integrated effects for Qtractor.

I don't think it's worth the effort, since built-in plugins are often considered inferior. Another reason is that you can't please everyone. For example, some people want a sophisticated compressor with all the bells and whistles, while others just want a compressor with a single knob.

I was primarily referring to beginners or those switching to Linux—and the factors that influence the adoption and use of various DAWs, such as specific features, the scope of functionality, or how the software is perceived on social media platforms.

Of course, I didn’t mean to imply that one must satisfy everyone. Personally, I actually find a compressor with just a simple on/off switch quite appealing—the kind you often see on small recording mixers.
Naturally, users who eventually want more, or who are already experienced, will seek out and install software that suits their own preferences.

My broader question was: why doesn’t Qtractor see wider adoption and more attention?

Of course, broader adoption and usage can be both a blessing and a curse.
One potential downside of a larger user base is that users may place higher expectations on the developers.
On the other hand, the advantages include having more people using the software, talking about it, creating tutorials, and—almost certainly—sharing their own presets, samples, loops, and knowledge, which in turn increases the software's visibility to potential new users. A larger user base could also lead to better support for the project (attracting more interested developers and potentially securing more resources, including financial ones).

It is difficult to find precise figures or studies regarding the reasons behind the adoption and usage of music software; however, recent studies—for instance, in Germany—indicate that one in five people makes music. There is also data available on the types of musical instruments used and how many people, for example, engage in singing.
AI-based research even suggests that a great many people—ranging from those just starting out to professional producers—work with loops and samples. This is because they facilitate and accelerate the creative process, enabling the creation of complex sonic landscapes without requiring extensive prior musical knowledge. Aside from that, I personally quite like loop-based music—even in clubs or at concerts—and it’s hard to deny that this is an area where a large, if not the largest, portion of hobbyist musicians—those using a DAW with software synths, samplers, and drum machines—operate.
There must be a reason why proprietary software like Live, Bitwig, FL Studio, and Reason—as well as free software like LMMS and now even Ardour—all strive to cater to this space.

What they all have in common is:

  1. Loop-based or pattern-based workflows (yes, even Ardour now has its own "Session View"). Different DAWs approach this in various ways using distinct tools—for instance, through a "Session View" (Ableton Live, Bitwig, Ardour), integrated loop players like Dr. Rex or the Matrix step sequencer in Reason, the arrangers found in LMMS and FL Studio, or loop functions built directly into individual tracks (as seen in Apple’s Logic Audio—and, I believe, GarageBand).
  2. "Bread-and-butter" effects and instruments that cover the essentials.
  3. At least a basic set of "bread-and-butter" sounds (samples, audio/MIDI loops—even Ardour, in its current version, offers downloads for free samples and loops).
  4. A selection of presets that make getting started easier, while also demonstrating how things are constructed and what a given plugin is capable of.

Perhaps it’s not a bad idea to discuss this; I’ve noticed—both here and on forums like LinuxMusicians or Reddit—that whenever the topic of Qtractor comes up, it’s almost always the same two or three users chiming in. While their help and advice are consistently excellent—and it’s clear they are true enthusiasts of the software—it also strongly suggests that the overall user base is likely quite small. As I said, I’m just sharing a few of my thoughts here.

Best regards ;-)

Permalink

I agree with what you’re saying.

Ultimately, the exact number of users doesn’t really matter though, judging by SourceForge downloads alone, there are thousands.
It’s true, however, that many are only sporadic users, people who open it up every once in a long while just to play around for fun, as you mentioned.

Many others don’t use it as their primary DAW, but rather just as a MIDI sequencer.

If there were a distribution of Qtractor that came with everything needed to get started right away, the user base would undoubtedly be larger.

But does it really matter?
Let whoever wants to use it, use it! :)

As I mentioned, doing everything required would be a task of such magnitude that it’s simply unmanageable for one or two people.

Just creating samples (MIDI/audio loops) and presets of an acceptable quality would take months or even years.

And then there’s the matter of providing support...

Commercial companies outsource all those tasks to specialized firms, so, in reality, thousands of people are working on them.

LMMS, which is the closest equivalent, doesn’t include loops either, and its collection of presets is quite limited.

And yet, we’re talking about software that is hundreds of times more popular—and therefore has many more contributors—than Qtractor.

Why is that? First, because it’s available for Windows; second, because it mirrors the approach of FL Studio; and, of course, because of its built-in tools.

Even with those millions of users, LMMS progresses very, very slowly. It’s just not enough—it’s an enormous undertaking.

Furthermore, while an "all-in-one" integrated system has many advantages, it also comes with a significant trade-off.

When you provide everything pre-configured, you end up limiting the user’s creativity—their core, fundamental creativity. By offering a predefined framework, you’re effectively shaping—and potentially restricting—the results they can achieve.

Does having a large library of high-quality loops actually foster creativity? Or does it just make everything sound more or less the same, regardless of who is using it?

So, that is the reason why what you’re looking for doesn’t exist.
If I were capable of taking on a task of that scale, I would have done it. In terms of knowledge alone, I fall short—though it is true that I am good at learning any discipline on the fly without making a fool of myself.
But it’s just not feasible. You need a coordinated, multidisciplinary team.

I’ll stick to this idea:
What does it matter? Let anyone use it, however they like.
And that is actually viable.

P.S.
That’s not to say that steps couldn’t be taken in that direction, or that it might not be achieved someday.

P.S.2
In recent months, DAWs with integrated plug-ins have begun to emerge, thanks to the rapid development pace enabled by AI.

However, they do not come with samples. Furthermore, I can guarantee that any available presets are either extremely limited, or more likely non-existent. Especially when it comes to channel-strip presets that combine multiple plug-ins to achieve specific effects (such as "jazz club vocals" or "rock mastering").

The fact is, creating these presets can be just as complex as the programming itself—and the workload required to build a decent starting library may be even greater. In this area, the assistance provided by AI is far more limited.

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.