From: Silvan <dmm...@us...> - 2005-11-04 05:08:33
|
On Thursday 03 November 2005 07:43 am, Ketil Thorgersen wrote: > There's no modconf on my ubuntu at least. On the ubuntu wiki pages this Can you install it? Just because it isn't there by default doesn't mean it isn't installable. Although having said that, I have no idea what K/Ubuntu has done in the way of non-Debian-style module twiddling. For that matter, it's possible that modconf is just some legacy thing from yore that is only installable to please crusty bastards like me (like LILO, for instance.) > is the tip provided: > sudo mknod -m 666 /dev/snd/seq c 116 1 > Very primitive since it must be run every time. I've seen this floating around here too, but I don't know why it's necessary. I'm guessing that it's because that new udev thing isn't configuring the MIDI devices correctly. I'm not using udev yet, and I don't even really know what udev is. It says my kernel is too old, and I say that's fine with me, I'll just keep using hotplug, thanks. Anyway, this sort of crap smacks of why I got rid of devfs back a few years ago. It had similar retarded problems not automatically creating the right things at boot, and then you'd create them, and then they'd go away, because devfs turned /dev into a virtual directory like /proc, and nothing you created there actually existed outside of RAM. Pain in the ass to figure out how to configure it correctly, and I could live without it just fine, so PLOOT, that one went into the crapper right beside aRts. I think udev is the successor to devfs, and from the look of things with this mknod advice floating around, it's probably also a pain in the ass that provides wonderful benefits to the twelve people in the world who give a flying rat's ass about the obscure kernel problem it's trying to solve, and just makes life for all the rest of us complicated for no benefit we will ever be in a position to appreciate. Probably, but maybe not. I never have bothered to figure out what udev was. I figure I'll deal with it when I have absolutely no other choice, and until then, if it ain't broke.... > I wanted to start hydrogen and rosegarden too, but my bash skills are > bad so I tried to configure QJackqtl to start rosegarden and hydrogen > instead. I first opened rosegarden and hydrogen, checking that they were > connected the way I wanted to, and then pressed "patchbay" chose new and > answered "yes". Now I had a patchbay definition that I hoped would start > hydrogen and rosegarden with the right connections, but while the > definition loads fine, the apps doesn't start. > > Does anyone know a way to do this either vie a script or via QJacktl or > another tool? I don't think the patchbay flummy is supposed to actually start applications, is it? I've never actually bothered to figure it out, but I think it's just so you can load your bits and bobs, hook them up, and then save how you had them hooked up, so that the next time you load your bits and bobs again, you can hook them back up the same way. I think you have to run all your bits and bobs by hand, or out of a script. I have no idea though, as I never have gotten around to working out some way to do this automatically. I just stupidly hook everything up by hand the same way every time, because at the moment I'm doing it, it seems faster than figuring out an easier way. (I can get away with this since I leave all of this stuff running for weeks on end, and don't set it up very often.) -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |