Main menu
You are here
Thoughts on "Life, Universe and Everything"
Hello Rui!
First of all I want to say, thank you. no, Thank You! no, THANK YOU! for all your projects!
I like Qtractor very much, it's the best linux multi-track sequencer! But it still has a lot of minuses (half of them because of linux distribution packagers) using it - like riding a wild horse :) Especially lv2 and DSSI GUI support in Ubuntu :)
I tried OpenSuse (as I understand - your choise), and I was surprised I couldn't find Qtractor at all, no, actually I found it in multimedia repo(0.5.6), but without lv2 support, then I returned to KXStudio. But in Ubuntu (0.5.5-1) lv2 support is broken - application segfaults... again... KXstudio's Qtractor-svn package (0.5.6-svn-3063) is a bit better, I can open lv2 window it segfaults only when I close plugin window - some progress :) As I remember before, plugins started without native GUI, and only if I press a button, starts native GUI - it was better, now everithing crashes. I don't need round buttons and half window name of plugin for a compressor? or reverberation. Please do something! PLEEEASE!
I see you started Vee One Suite - briliant idea! make your own set of plugins and samplers (but multilayer samplers ;) like hydrodrums). You will shot two rabbits - no more gtk related problems, and no problems with external synths, samplers and hosts.
Here is another problem in linux audio "industry" - How to store everithing in one project? The crutches like ladish-lash - it's the pain in the asstral hole of the universe. Many years I tried to understand how to make it work, but maybe I'm to stupid? And still, when I save this ladish session - I stil can't share my project, because of many separate files and app configs. For example - I want to make one project with two drum sets in Hydrogen, connected to Qtractor sequencer and Rakarrack loop - I can't share it with my friend to work together.
What I dream about is:
I start Qtractor, choose buffer size, start new project - adding tracks and selecting inputs and outputs, completely control jack without qjackctl - add/remove sound inputs and outputs, adding VeeOneSuit drum sampler, fluidsynth synth (well, maybe there will be VeeOne sf2 sampler;)) for bass and keyboards, lv2 plugins (with qt GUI, no need native) for audio, record tracks, well only external apps I can imagine - rakarrack and zynadsubfx, save compressed project, send it to a friend - complete totall happiness!
Sorry, I can't help you, I'm not a programmer, I'm not even advanced tester. I could donate some money, I think many people would be happy to support development, but I don't see any donate button :)
I only have ideas about what I want to have :)
KXStudio Qtractor package
Hi konstantin, installing Qtractor from KXStudio latest should also pull in the latest releases of lilv and suil so it's kind of weird that lv2 plugins are misbehaving. I read somewhere though that renaming your Qtractor configuration file could help. Ah found it: http://code.google.com/p/amsynth/issues/detail?id=42#c31
re. Thoughts on "Life, Universe and Everything"
i hear you, Konstatin
i believe the culprit of all problems is lack on adoption to the latest lv2 >= 1.0.0.
believe it or not, most mainstream distros if not all still list the old lv2core package as their primary source. and having its version tag as something like 4.0 just doesn't help either. i know.
if you're still considering opensuse, you can try my own rpm packaging. check them all from the local archive.
alternatively you can also check out from my opensuse build service repositories. note that here you find the latest snapshots, bleeding ahead from release level stable stuff ;)
cheers
project sharing
It seems one of Konstantin's big wishes for qtr is easy sharing of sessions and if I'm not reading the Vee one new features / changelog incorrectly then I suspect this may have just improved with the latest iterations of samplv1 and drumkv1. I quote:
- Prepared for relative filesystem paths on preset file references.
Previously, I know that with samplv1 it would quietly fail if the samples weren't stored in the exact same path as when then session was created. I spotted this straight away and asked if Rui would fix it to print warnings and hopefully make it so it would scan the session folder, whereever that may be, for the samples before failing. Maybe thats happened now?
re. project sharing
if you save a qtractor session onto a so called archive/zip format (save as .qtz filename suffix or extension) all media content files, audio, midi and lv2 state files supported plugins (eg. samplv1, drumkv1) get bundled into one single file.
think of qtractor session portability and archival purposes or when you're satisfied with your arrangement at the end of the day. of course, it is the file format for project sharing, working best when peers have similar system setups ie. equivalent external connections.
cheers
Wow!
Wow!
OK I'll try latest KXstudio builds as soon as posible. About OpenSuse - maybe install side by side Kubuntu - for everyday use and OpenSuse with Rui's repository for music? I'll think about it. Only problem - where to get realtime kernel for OpenSuse.
Prepared for relative filesystem paths on preset file references
Relative, non relative, it's not a big problem - I use sound samples and soundbanks stored on separate partition mounted to /data directory, and I can simlink it to any folder i need on any computer (in theory) but I like how they do it in blender - choose relative/absolute path for external data is cool :)
.qtz
qtz is good only for Qtractor session, what happens when Qtractor connected to external host? If lv2 problem will be fixed finally - BRILIANT! I don't need external effects host. But what about samplers and synths? If you make drumv1 a multilayer sampler with drum libraries (no, I dont say you must collect library for me, just switching libraries like Hydrogen has), It will be even better - No more Hydrogen! Because it stops playing sometimes :) And if I need different drum library in Hydrogen I can't control it thru Qtractor. This is bad.
Oh, and I wanted to ask: If I connect Qtractor to Qsynth - I need only one synth instance for all MIDI tracks in Qtractor, but if I use fluidsynth dssi plugin inside qtractor, I must create instance for every track. Why is that? This is limitation of dssi? Is it posible to make one fluidsynth track and use it for all tracks?
re. multi-timbral instrument plugins (eg. fluidsynth)
Is it possible to make one fluidsynth track and use it for all tracks?
nb. multi-timbral instrument plugins may well go on a single instance inserted on a midi output bus. i must confess i haven't tested it yet with fluidsynth-dssi, but linuxsampler has been on the the kind that works that way.
btw. reading from the latest fluidsynth development (svn) there will be important soundfont sharing (as system memory resource) across several insntances, no matter if it's of the plugin genre or standlone (eg. qsynth). so the whole question might be moot on the near future anyway :)
byee
Add new comment