Re: [Alsa-user] USB MIDI problem with receiving large sysex files
je...@web.de wrote: Recently I encountered a problem with receiving large amounts of sysex data. [...] the bank dumps never reach 830.336 bytes. The number of bytes received from a bank dump seems to be not predictable and varies strongly each time. In theory, USB MIDI reception works just fine. Looking into /var/log/messages I could find errors which would seem to be related to this issue. ...? Regards, Clemens -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] USB MIDI problem with receiving large sysex files
Thank you Clemens for your fast reply. Sorry for the weird remark regarding /var/log/messages. To clarify: I was *not* able to find related errors. One thing I have seen while watching the data received by amidi with the -d option as well as with the other tools was, that the data stream sometimes seems to stop while the Axe-Fx II is still sending data. Sometimes the stream continues after or short break, sometimes it does not. Dont know if this could be a timing issue? Regards, Joachim Gesendet:Donnerstag, 11. April 2013 um 09:01 Uhr Von:Clemens Ladisch cladi...@googlemail.com An:je...@web.de Cc:alsa-user@lists.sourceforge.net Betreff:Re: [Alsa-user] USB MIDI problem with receiving large sysex files je...@web.de wrote: Recently I encountered a problem with receiving large amounts of sysex data. [...] the bank dumps never reach 830.336 bytes. The number of bytes received from a bank dump seems to be not predictable and varies strongly each time. In theory, USB MIDI reception works just fine. Looking into /var/log/messages I could find errors which would seem to be related to this issue. ...? Regards, Clemens -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] USB MIDI problem with receiving large sysex files
Sorry for the double post, but the first try is barely readly because of html tags... :( Thank you Clemens for your fast reply. Sorry for the weird remark regarding /var/log/messages. To clarify: I was *not* able to find related errors. One thing I have seen while watching the data received by amidi with the -d option as well as with the other tools was, that the data stream sometimes seems to stop while the Axe-Fx II is still sending data. Sometimes the stream continues after or short break, sometimes it does not. Don't know if this could be a timing issue? Regards, Joachim Gesendet: Donnerstag, 11. April 2013 um 09:01 Uhr Von: Clemens Ladisch cladi...@googlemail.com An: je...@web.de Cc: alsa-user@lists.sourceforge.net Betreff: Re: [Alsa-user] USB MIDI problem with receiving large sysex files je...@web.de wrote: Recently I encountered a problem with receiving large amounts of sysex data. [...] the bank dumps never reach 830.336 bytes. The number of bytes received from a bank dump seems to be not predictable and varies strongly each time. In theory, USB MIDI reception works just fine. Looking into /var/log/messages I could find errors which would seem to be related to this issue. ...? Regards, Clemens -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] problem with new 1.0.25 build on Ubuntu Lucid
On April 9, 2013 at 11:22 PM chris hermansen clherman...@gmail.com wrote: Andrew, list: On Tue, Apr 9, 2013 at 4:31 PM, Andrew RT andrew2...@flight.us wrote: On April 8, 2013 at 10:07 PM Andrew RT andrew2...@flight.us wrote: Hi, guys I'm on Ubuntu Lucid, 2.6.32-45-generic, had audio working up until I pursued new alsa driver a couple of days ago. [...] By the way I tried to revert to official alsa packages and failed miserably; thus, there seems to be no turning back Please help! Bump. I've got a disastrous loss of audio on my main system. Anyone have a clue? You certainly have my sympathy! Lucid / 2.6.32 kernel is pretty old; can I ask some dumb questions? Do you use pulse audio or bare-bones Alsa? I think I'm using pulse. Also jack. jack suspends pulseaudio, I believe, when it runs. If Alsa: - what happens when you do a sudo aplay -l? List of PLAYBACK Hardware Devices card 0: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 My loopback device is set up when I manually insert the module ( modprobe snd-aloop). But it boots up without any snd modules initially. - what happens when you do a sudo aplay -L? null Discard all samples (playback) or generate zero samples (capture) sysdefault:CARD=Loopback Loopback, Loopback PCM Default Audio Device - what do you see in /proc/asound? The directory has: card0 cards devices Loopback modules pcm seq timers version cat /proc/asound/cards 0 [Loopback ]: Loopback - Loopback Loopback 1 There's just the loopback device. - do you see any errors in your system log file about audio? there are no recent errors, with the most recent recompiling. Like I said, the kernel module file snd-hda-intel.ko is missing from my latest /lib/modules/.I believe that's the file that would set up my audio card. But how to generate it? I'm assuming it was there before I removed my pre-compiled alsa-utils,etc, to make way for my local build (?). But then my local build failed to generate the new version of this file (?) -- Chris Hermansen · clhermansen at gmail dot com C'est ma façon de parler. Et bien — c'est ma façon de me taire. -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Status of CM6631 USB
On Wed, Apr 10, 2013 at 08:46:04 -0700, chris hermansen wrote: Torstein and list: Wait! this is still weird. Please see at bottom... On Wed, Apr 10, 2013 at 8:31 AM, chris hermansen clherman...@gmail.com wrote: Torstein, list: On Wed, Apr 10, 2013 at 2:32 AM, Torstein Hegge he...@resisty.net wrote: What does dmesg / /var/log/kern.log say when you plug in the device with the v3.9-rc6 kernel? Hmm things are getting interesting. Yesterday, when I had the problem with missing altset 2, as far as I can remember, I had plugged in the Schiit before booting and switched the Schiit to USB once booted. Today below I booted the machine, switched the Schiit to usb input, started up a terminal window, checked the kernel version, tailed the /var/log/kern.log, plugged the Schiit in, then checked the /proc/asound/Interface/stream0 file. Despite the error messages when plugging, it seems I have altset 2 back! [...] I tried to replicate the same conditions as previously, ie plug before boot, but now I seem to have the altset 2 back. I tried playing a few tracks at different speeds / bit rates and all seems fine now, ie the 24 bit files get converted to 32 bit and not 16 bit on altset 2. It would be fantastic to consider this fixed but I'm a bit lost as to how my altset disappeared for a session... After I sent this, I got to thinking, maybe I did not re-plug the Schitt while the machine was off... so: I shut down the machine, unplugged the Schiit, switched it to TOSLINK, plugged the USB back in, and rebooted. At this point I have not yet switched the Schiit back to USB, but what I have in /proc/asound/Interface/stream0 is now: clh@temuko:~$ cat /proc/asound/Interface/stream0 CMEDIA Schiit USB Interface at usb-:00:13.2-3, high speed : USB Audio Playback: Status: Stop Interface 1 Altset 1 Format: S16_LE Channels: 2 Endpoint: 5 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000, 192000 Data packet interval: 125 us Capture: Status: Stop Interface 4 Altset 1 Format: S16_LE Channels: 2 Endpoint: 8 IN (ASYNC) Rates: 44100, 48000, 88200, 96000, 192000 Data packet interval: 125 us clh@temuko:~$ ie no S32_LE altset on either playback or capture. Switching the Schiit back to USB does not change this. The USB or S/PDIF input setting on the Schiit shouldn't affect the behavior of the USB interface, it just selects the DAC source. But I don't quite follow what you did different between your tests. Plugging in after boot works fine. Keeping the USB plugged in over a reboot works fine. Plugging in the USB while the laptop is off and then booting gives a missing alternate setting? Or did I get those last two mixed up? Torstein -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] M-Audio FastTrack C400
Hi, Is the M-Audio FastTrack C400 supported on Linux? Regards, \r -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] USB MIDI problem with receiving large sysex files
je...@web.de wrote: One thing I have seen while watching the data received by amidi with the -d option as well as with the other tools was, that the data stream sometimes seems to stop while the Axe-Fx II is still sending data. Sometimes the stream continues after or short break, sometimes it does not. MIDI dumps works fine with every other device. You could try another cable and/or another USB port. Don't know if this could be a timing issue? USB MIDI uses bulk transfers, which is the same method that is used by USB hard disks. I guess your machine doesn't have problems with reading from such devices at a speed of 1.5 KB/s or more? Regards, Clemens -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] problem with new 1.0.25 build on Ubuntu Lucid [SOLVED]
IT WAS A HYPHEN VERSUS UNDERSCORE SYNTAX ISSUE! my ./configure options were: ./configure --with-cards=hda_intel,hrtimer,aloop --with-sequencer=yes BUT THEY NEEDED TO BE: ./configure --with-cards=hda-intel,hrtimer,aloop --with-sequencer=yes At a glance — the whole configure code equivocates between hyphens and underscores a lot; that should probably be addressed. Also, it would help if the configure script checked for existence of the sub-options to --with-cards=, and prevent non-existing card options, such as what I initially gave (hda_intel)... right now it just silently ignores a bad option. So, with the correction, alsa compiled and install my snd-hda-intel.ko ( /lib/modules/2.6.32-45-generic/kernel/sound/pci/hda/snd-hda-intel.ko ) I rebooted and have sound. Pulse working, and so is jack. as they did before, AFAICT. I may post back with a different topic, about the aloop device. Which is why I tried to upgrade alsa in the first place. On April 11, 2013 at 5:02 AM Andrew RT andrew2...@flight.us wrote: On April 9, 2013 at 11:22 PM chris hermansen clherman...@gmail.com wrote: Andrew, list: On Tue, Apr 9, 2013 at 4:31 PM, Andrew RT andrew2...@flight.us wrote: On April 8, 2013 at 10:07 PM Andrew RT andrew2...@flight.us wrote: Hi, guys I'm on Ubuntu Lucid, 2.6.32-45-generic, had audio working up until I pursued new alsa driver a couple of days ago. [...] By the way I tried to revert to official alsa packages and failed miserably; thus, there seems to be no turning back Please help! Bump. I've got a disastrous loss of audio on my main system. Anyone have a clue? You certainly have my sympathy! Lucid / 2.6.32 kernel is pretty old; can I ask some dumb questions? Do you use pulse audio or bare-bones Alsa? I think I'm using pulse. Also jack. jack suspends pulseaudio, I believe, when it runs. If Alsa: - what happens when you do a sudo aplay -l? List of PLAYBACK Hardware Devices card 0: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 My loopback device is set up when I manually insert the module ( modprobe snd-aloop). But it boots up without any snd modules initially. - what happens when you do a sudo aplay -L? null Discard all samples (playback) or generate zero samples (capture) sysdefault:CARD=Loopback Loopback, Loopback PCM Default Audio Device - what do you see in /proc/asound? The directory has: card0 cards devices Loopback modules pcm seq timers version cat /proc/asound/cards 0 [Loopback ]: Loopback - Loopback Loopback 1 There's just the loopback device. - do you see any errors in your system log file about audio? there are no recent errors, with the most recent recompiling. Like I said, the kernel module file snd-hda-intel.ko is missing from my latest /lib/modules/.I believe that's the file that would set up my audio card. But how to generate it? I'm assuming it was there before I removed my pre-compiled alsa-utils,etc, to make way for my local build (?). But then my local build failed to generate the new version of this file (?) -- Chris Hermansen · clhermansen at gmail dot com C'est ma façon de parler. Et bien — c'est ma façon de me taire. -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account!
Re: [Alsa-user] M-Audio FastTrack C400
rosea.grammostola wrote: Is the M-Audio FastTrack C400 supported on Linux? On Linux 3.8. Regards, Clemens -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] M-Audio FastTrack C400
On 04/11/2013 05:26 PM, Clemens Ladisch wrote: rosea.grammostola wrote: Is the M-Audio FastTrack C400 supported on Linux? On Linux 3.8. Thx, full support? Hm running debian on 3.2 atm. \r -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] M-Audio FastTrack C400
On 04/11/2013 05:28 PM, rosea.grammostola wrote: On 04/11/2013 05:26 PM, Clemens Ladisch wrote: rosea.grammostola wrote: Is the M-Audio FastTrack C400 supported on Linux? On Linux 3.8. Thx, full support? Hm running debian on 3.2 atm. ah ok 3.8 is in Debian experimental. -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Status of CM6631 USB
Torstein, list; On Thu, Apr 11, 2013 at 2:02 AM, Torstein Hegge he...@resisty.net wrote: [...] ie no S32_LE altset on either playback or capture. Switching the Schiit back to USB does not change this. The USB or S/PDIF input setting on the Schiit shouldn't affect the behavior of the USB interface, it just selects the DAC source. I am pretty sure you are correct but I wanted to make sure that there wasn't some kind of signalling that happened when I switched the active input to the USB. But I don't quite follow what you did different between your tests. Plugging in after boot works fine. Keeping the USB plugged in over a reboot works fine. Plugging in the USB while the laptop is off and then booting gives a missing alternate setting? Or did I get those last two mixed up? Sorry for the lack of clarity! First time: I plugged the Schiit USB into the laptop before booting the laptop (only one altset for output, two for input for stream0) Second time: I hot-plugged the Schiit USB into the already running laptop (two altsets for stream0, correct behaviour) Third time: I rebooted the laptop after the second time above without unplugging the Schiit (two altsets for stream0, correct behaviour) Fourth time: I halted the laptop, unplugged and replugged the Schiit, booted (only one altset, both output and capture, for stream0). I can try some repeatability testing on these if you like. -- Chris Hermansen · clhermansen at gmail dot com C'est ma façon de parler. -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] USB MIDI problem with receiving large sysex files
Your advice was perfect ... it is pretty much embarrassing, but yeah, changing to another USB port helped :-) Did try that before, but just had catched the only other USB port of the machine that obviously has problems, too. All other USB ports are working fine - as I know now ... ;-) So, thanks a bunch again! Regards, Joachim Am 11.04.2013 13:12, schrieb Clemens Ladisch: je...@web.de wrote: One thing I have seen while watching the data received by amidi with the -d option as well as with the other tools was, that the data stream sometimes seems to stop while the Axe-Fx II is still sending data. Sometimes the stream continues after or short break, sometimes it does not. MIDI dumps works fine with every other device. You could try another cable and/or another USB port. Don't know if this could be a timing issue? USB MIDI uses bulk transfers, which is the same method that is used by USB hard disks. I guess your machine doesn't have problems with reading from such devices at a speed of 1.5 KB/s or more? Regards, Clemens -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
