[00:00] <len-dt> USB 1 and 2 are problems for audio/midi anyway.
[00:00] <len-dt> Wow!
[00:00] <ailo> Nah, normal boot. Damn!
[00:00] <len-dt> :)
[00:01] <ailo> Those docs are never complete. They always figure you know what you need to do before you do it, to a degree
[00:02] <len-dt> I was playing around with my USB ports... plugging in a memstick in different ones to see what irqs it uses.
[00:02] <len-dt> All 6 use the saem one.
[00:03] <len-dt> They all seem to be 23:          0          0   IO-APIC-fasteoi   ehci_hcd:usb1
[00:05] <len-dt> Yet it lists usb 1 to usb 5
[00:07] <len-dt> ailo, I checked my MB doc and it says I only have the 6 ports...
[00:08] <len-dt> I think ehci is USB2 and uhci is usb1.1, driver wise.
[00:11] <len-dt> Anyway, I said all that to say it appears that for this MB at least, USB2 inputs get routed from which ever hardware port they use to the same driver. I wonder what happens when I plug in two USB2 devices.
[00:18] <len-dt> ailo, Paul at ardour in answering a user question says "@Edward: you are correct: a2jmidid -e is the best option, for all cases actually. It has better timing (jitter & latency) characteristics than the code which implements the "seq" and "raw" options of the ALSA backend. Eventually, the functionality of a2jmidi will be more easily available. It also provides "better" port names (well, more human readable ones anyway)."
[00:23] <ailo> There's some controversy around jackd2 also, I believe
[00:23] <ailo> But, hopefully they will get all that stuff mended in the future
[00:24] <ailo> If there is one setup that is optimal for everyone, and includes all available functionality, then that is the way to go
[00:27] <len-dt> ailo, right now I don't seem to be getting any midi out from hydrogen...
[01:23] <ailo> I really want to have the thcp server running, but alas, I need to learn all about networking to do it it seems.
[01:23] <len-dt> ailo, Ran hydrogen with both it's own drums as well as an external synth (yamaha TG100) with no noticeable timing issues. Both drums sounded at the same time.
[01:24] <len-dt> I did two ways, alsa only and a2j only.
[01:24] <ailo> len-dt: Try recording the external sounds. Timing is very noticable for me
[01:25] <ailo> I was unable to sample 1-2 sec of a beat
[01:25] <ailo> It never timed right, no matter how I tried recording it
[01:25] <ailo> Like a drunken drummer
[01:25] <len-dt> Right now, I can't get either midi seq or raw to work right now, so I will reboot.
[01:28] <len-dt> Ah! can't make changes to the settings while hydrogen is running.
[02:01] <ailo> Finally :P, some progress..
[02:02] <len-dt> ailo, using midi seq. setting hydrogen to play it's own sound as well as output to midi port. recording hydrogen on left and TG100 on right using audacity. On playback sounds fine.
[02:03] <len-dt> I will now reset up everything for just alsa midi.
[02:04] <len-dt> Unless you can see some error in my test method ailo.
[02:06] <len-dt> Does system load make a difference? I am using -p 128 and pulse bridging is enabled too. My midi card is an ensoniq pci card.
[02:09] <acmeinc1> i'm coming in late, but is there somethign I need to be aware of midi-wise?   i plan to lay some stuff down this weekend for testing.  it looks like u guys were testing lag times w/ midi, and I was wondering if the default settings were causing a problem.
[02:11] <ailo> len-dt: It may depend a lot on the device. Could be that pci is much more reliable than usb
[02:11] <len-dt> So far I have not had a problem, ailo seems to have timing problems on midi outputs to real devices.
[02:12] <ailo> acmeinc1: For me, I get really audible timing errors when sending alsa midi to an external usb synth
[02:12] <len-dt> ailo, I agree. My earlier comment about USB ports was something to the effect that many MB seem to have an internal USB hub for all their ports
[02:13] <len-dt> Or at least mine.
[02:13] <acmeinc1> ok, thx for the clarification.
[02:14] <ailo> I finally got network boot going. I had a dhcp server running already, which I had no idea about. After I fixed that, it was terribly easy. Now, I can install all my machines through the network :D
[02:15] <len-dt> ailo, All? you make it sound like you have a flock
[02:15] <ailo> I have a bunch of older machines, but a couple of newer ones too
[02:15] <len-dt> ailo, my installs are all different.
[02:16] <ailo> I will install Debian and Ubuntu on all of them. Control using vnc or ssh
[02:17] <len-dt> I have four, one is real old. So it gets a real light one. The server has server and my Yf's has desktop.
[02:17] <len-dt> Both mine have US.
[02:18] <len-dt> Hmm, five.
[02:32] <len-dt> ailo, is your usb midi port midi only or part of an audio i/f
[02:34] <len-dt> And I guess I should also ask USB1.1 or 2.0? And do you have any other USB devices plugged in?
[02:38] <len-dt> ailo, I think I will run the recommended a2jmidid -e option.
[02:48] <ailo> It's midi only. A synth module called Roland xv-5050
[02:48] <ailo> I have a usb midi i/o device as well. M-audio, that requires firmware
[02:49] <ailo> Last time I had to use my firewire midi to the synth module, so I could use jack midi
[02:50] <len-dt> ailo, I was just wondering if there was more than one USB device being used at the same time and if that may be an issue.
[02:51] <ailo> No, this was entirely just the fault of alsa + this usb device
[13:00] <ailo> len-dt: rtirq script was just updated after recent discoveries http://www.rncbc.org/jack/#rtirq
[13:12] <len-dt> ailo, when will it make it into the repos?
[13:13] <len-dt> ailo, I guess I should be asking what package it is a part of right now.
[13:26] <len-dt> ailo, it looks like it only ran in runlevel 34 the new one sets RL2-5
[13:31] <len-dt> It uses a different method of finding tasklets.
[14:03] <len-dt> I'll have to try it with my netbook which still has some xruns at -p 128
[14:05] <len-dt> Hi Ho, off to work.... later.
[14:09] <len-dt> scott-work, just before I'm gone. The comment on #ubuntustudio about starting  Yoshimi. a2j fixes that and the -a may break something else. I assume it makes an alsa midi port instead of a jack midi port.
[14:10] <len-dt> In any case, that would be the .desktop file for  Yoshimi.
[18:58] <scott-work> len-dt: i noted that in my evernote file :)
[20:08] <len-dt> Mr. holstein is a good teacher.
[20:09] <holstein> len-dt: i hope so
[20:09] <holstein> i try and be realistic in the support channel
[20:10] <len-dt> It is hard to figure where to start with a machine I have never seen and a set of software I'm not sure of.
[20:10] <holstein> yup
[20:10] <holstein> and the hardware config can be so different
[20:11] <len-dt> speaking of which, is it true with fire wire that the only way to feed pulse is with jack bridging?
[20:12] <holstein> len-dt: i can try some tests
[20:12] <holstein> i remember having issues way back
[20:12] <holstein> i was assured at the time that i wasnt though ;)
[20:12] <len-dt> One of the users seemed to think that firewire doesn't provide any alsa ports.
[20:13] <holstein> len-dt: remind me and i'll try
[20:13] <holstein> when im near "the rig"
[20:13] <holstein> that'll be a while though
[20:13] <len-dt> if I remember ;-)
[20:13] <holstein> im not sure when ill take the time to switch from 10.04 on there
[20:15] <len-dt> It does take some time. Don't use the upgrade option in ubiquity... it failed for me when trying to upgrade from 11.10 xubuntu to 12.04.
[20:16] <holstein> nah.. i'll do a fresh install
[20:17] <len-dt> That was what I intended. The upgrade option in ubiquity was where the fresh install option normally was.
[20:17] <len-dt> I hadn't seen it before
[20:17] <holstein> im the kind of guy who will go buy a hard drive and save the old one for a few months or so
[20:18] <len-dt> This machine still has the old stuff on it. my netbook I backed up my home dir and reinstalled.
[20:19] <holstein> i think i still have an old pata drive somewhere with "64studio" written on it
[20:19] <len-dt> I therefore still have gcdmaster on a second boot if I want to use it.
[20:20] <len-dt> I had the live cd for that but never installed it. It seemed to be flaky at the time... might have been my hardware too. Then I found audio slack and used that.
[20:21] <holstein> that was the first distro i was able to get firewire working in
[20:22] <len-dt> I think I started pre-USB... that was what I had the ensoniq card for. The MB was sub GHz. too.
[20:23] <len-dt> 8 tracks and 600MB was a lot :-)
[20:25] <len-dt> (hard drive that is)