Rui Nuno Capela wrote: > you'll need more than the hack headers (libjack-dev) i'm afraid: > libasound-dev, linsndfile-dev, libvorbis-dev, libmad-dev, ladspa, dssi, > liblo-dev, librubberband-dev are also recommended, at least.
Some dependencies are even in the 64 Studio beta and additional repository avail. > it would be really nice if you could always play catch up with the latest > qtractor cvs, where "things" happen. there you can actually help both of > us ;) Okay, because I guess that the 64 Studio developers are too busy to daily upgrade Qtractor ;), I'll take a look if it might be possible to compile JACK2 for my 64 Studio myself. I often read about serious trouble when doing this for Debian based distros and Suse and some time ago I had a flame war with the Packman packager who released broken packages for the repository. I fear to compile JACK myself, because the 64 Studio developers version is fine. I don't think that I will get help on the JACK list, because I often been told to use Windows, even today: I OWTTE wrote that it would be better to work on serious trouble for rt-audio and rt-MIDI, than working on making JACK being fine to work simultaneously with every consumer audio server. I can't see the need to have desktop sound while I'm producing, to the contrary, if it isn't disabled by default, I disable it, but for me there's the need e.g. to have no MIDI jitter, but most people say that I'm a blabber, there are not such troubles like jitter for Linux, I should use Windows. Maybe they are right :(, it seems to be that Linux rt-audio should fit to people who need sound effects for their desktop environment. Pulseaudio, arts etc. seems to be extreme important for Linux rt-audio, while MIDI jitter and other troubles are less important, resp. still not existing for them. ----- Babel Fish Translation ----- Subject: Re: [Jack-Devel] [LAD] jack2's dbus name Date: Fri, 19 Jun 2009 15:30:34 +0200 Oops, I can't use the Bable Fish Translation, it's funny, but no English. The short version: Because I don't help, the only thing I do is babbling, I should use Windows instead of Linux. I answered that my help on German forums was deleted, because e.g. even Paul Davis (I guess he don't like me) had the same opinion I have for some issues, e.g. because of the bad JACK packages for Suse (some time ago). The maintainer for the Suse JACK package lied, he said that he was using his own packages to make pro-audio productions, but this was impossible and when it was attested, that I wasn't babbling, but saying the truth, all threads were deleted. Your name is mentioned only because I wrote that you are helping me to figure out, if I can do something against the MIDI jitter. I only wrote (and nothing more) that it seems to be, that you believe in my so called babbling. I'm pissed! Even for Windows there are FLOSS coders, when they got bug reports, I never heard anyone of them lament, that he is doing it for free, so that his children and wife suffer for hunger, because of his free work and if somebody isn't fine with FLOSS on Windows, he should use Linux instead. They like bug reports, like some Linux coders do too. -------- Original Message -------- Subject: Re: [Jack-Devel] [LAD] jack2's dbus name Date: Fri, 19 Jun 2009 15:30:34 +0200 Rui hilft mir gerade dabei dem MIDI Jitter auf die Schliche zu kommen. Einige, nicht nur er nehmen mein Gefasel ernst. Wenn Dein Gehör nicht ausreichend musikalisch ist und Du daher kein Interesse daran hast, dass Linux besser wird, ist dies Deine Sache. Das man von meinem Engagement weniger findet liegt auch daran, dass man, sobald sich Bemühungen von mir als Wahrheit heraus gestellt haben Beiträge mit Lösungen in deutschen Foren gerne gelöscht hat, s. ehemals kaputte Packman-Version von JACK. Ich nehme gerne konstruktive Problemlösungen innerhalb und außerhalb der Listen an, nur ist es impertinent unbequeme Mitteilungen derart zu bewerten. Warum filterst Du meine Mails nicht einfach heraus und ignorierst sie? Fehler innerhalb Linux audio überhörst Du ja auch und ignorierst sie. Diskussionen sollen auch ohne persönliche Angriffe funktionieren. Florian Faber wrote: > Ralf, > > >> Maybe this is the main problem for Linux and life in any way, we did >> start with a bad move: >> > > Du redest von 'wir' - ich habe jetzt auf Anhieb nichts finden koennen, > wo Du konstruktiv zu Linux Audio beigetragen hast. > > Ich dachte, Du wolltest Dich im Dezember in Richtung Windows > zurueckziehen. Bitte mach das doch endlich mal und nerv uns hier nicht > mit Deinem wirren Gefasel. > > > Flo > > take note that using fluidsynth-dssi is not the same case to stand-alone > fluidsynth/qsynth. while the former you should expect it to be jitter-free > and minimal delay, the latter will get you into a scenario where the > kernel scheduling load along with the chosen timer resolution may > influence the jitter figures. playing with outboard equipment is in fact > adding more probable causes of jitter (the alsa/usb/uart/midi interface) > so my latter suggestion could give you numbers tat can, probably, narrow > down the jitter culprit. When I was an audio and MIDI FLOSS coder myself, for the C64 and an audio and MIDI user for the Atari ST, I never had this trouble. The UART and ACIA microchips didn't cause trouble and I guess they don't cause trouble for Linux too, problems maybe are caused by USB kernel modules. I guess the difference between those computers and actual computers is, that they didn't do real, but pseudo-multi-tasking or even no multi-tasking and they were single user systems and regularly used for MIDI or audio only, but not MIDI and audio done by the computers at the same time. But especially for the C64 there was the need to program in Assembler, while counting the cycles the Assembler commands needed, for the C64 without buffering MIDI events as sequences. Thinking about the used RAM also was very important. Maybe (I don't know, I really mean 'maybe') taking care about cycles and RAM usage and changing to single user mode will be good while programming for Linux too. Now I'm babbling ;), because I'm again shocked, because of the actual discussion on JACK dev list. I'm sorry. I wonder if there is really an interest for the kernel, ALSA and JACK guys to solve troubles they aren't able to hear, but that are serious problems for pro-audio work. > you won't get significant jitter with dssi on any buffer size. however, if > you're using a pcm slave timer, as you have been using with rosegarden, > the jitter will probably increase with buffer/period size. it should not > matter in qtractor though, as the default/system timer is independent of > the current audio period. so, unless you use a pcm timer, increasing the > buffer size will only increase the constant delay value, jitter will > almost remain the same. > > all this theoretically speaking, of course :) I'll test how it will be on my machine, but please be patient, I'll search for a repository that enables the jack-dev package(s) for jackdmp for Hardy and I will search the web how to compile JACK2 for Hardy, without running into troubles, because of bad links, because of libjack. Thank you for your effort :). The only thing I can give back to you, is to use Qtractor and to report about bugs. I try to keep my answers shorter for the next mails ... -- http://www.dailywav.com/1002/beginning.wav _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
