Re: [Alsa-devel] Trivial hdsp.c patch to support rev 50 cards
> hello, > > tried playback of a mono file, to the same ends. yesterday in one > instance, i got around 45min of stereo playback before a lock up. > > also experienced a lock up in ardour yesterday, monitoring a single > channel and outputing it on another channel. > > haven't tried recording anything to see if the same problem exists > there. it's tough to test these things as i'm guaranteed a lock-up, ie: > my drives have to be fsck'd each time. > > does anyone know of a way to safely debug this? can i catch the playback > thread before it pees on the floor, "NO! Geez hdsp, stream goes out the > urinal! ...hold that thing, damnit!!!" ? > > dan. > Can you please give us more informations about your system ? * hardware (x86, PowerPC, SMP, laptop, cardbus or pci version of the hdsp ?) * linux kernel version and patches applied * alsa packages versions * gcc version used to compile kernel and alsa modules Thomas --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Re: [linux-audio-user] novation remote 25 usb midi controller
Clemens Ladisch wrote: > > Eric Dantan Rzewnicki wrote: > > T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 > > D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > > P: Vendor=1235 ProdID=4661 Rev= 1.01 > > S: Manufacturer=Novation EMS > > S: Product=ReMOTE25 V1.0 > > C:* #Ifs= 1 Cfg#= 1 Atr=20 MxPwr=250mA > > I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) > > Class ff is "vendor-specific", so it's not 100% compatible with the > USB Audio Specification. > > Please post the output of "lsusb -v". > > Regards, > Clemens box1:~# lsusb -v Bus 001 Device 001: ID : Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass9 Hub bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x idProduct 0x bcdDevice0.00 iManufacturer 0 iProduct2 USB UHCI-alt Root Hub iSerial 1 6400 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type none wMaxPacketSize 8 bInterval 255 Language IDs: (length=4) (null)((null)) Bus 001 Device 004: ID 1235:4661 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 Interface bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1235 idProduct 0x4661 bcdDevice1.01 iManufacturer 1 Novation EMS iProduct2 ReMOTE25 V1.0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x20 Remote Wakeup MaxPower 250mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type none wMaxPacketSize 32 bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes3 Transfer TypeInterrupt Synch Type none wMaxPacketSize 32 bInterval 1 Language IDs: (length=4) 0409 English(US) --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] [ANN] hdspmixer-1.1
> Using a multiface with original firmware rev. > > I was using the app last night and it seemed to work well except that > today we have only a very long blank track. > What do you mean ? > Testing today with ardour reveals that the mute buttons have no effect > on the recorded signal. > That's the way it's supposed to work. The app only controls routing. As you may know there is no way to control the input level on the hdsp, no way to lower thus to mute the input signal. So even if the input is muted, there still is audio in the buffer which gets recorded, it's just not routed to the outputs. > How do the mute buttons work? I fond it difficult to distinguish between > on and off. Why is the default color red? Does that mean they are on by > default? > There are per tracks mute and solo, and global mute and solo buttons. To mute a track, you need to enable muting (global button) and then mute the particular track you want to mute. When a track gets muted (when muting is effective somewhere) all the active mute buttons (per track and global) light up. The same applies to solo. > IMO the default should be no color and when they are on they should be > red. > I copied the original app behaviour for this. If you never used Totalmix in the past I encourage you to read the Totalmix section in the Multiface documentation available in pdf format from RME's website. My plans for the future are to keep conforming to the original, and maybe add non interfering linux specific extentions (e.g. ladcca support, remote control via alsa-seq). > I also missed a control for the headphone output. > In the last row (outputs), rightmost, you have the AN.L and AN.R tracks. These are the line outs. To route signal to the line outs you have to raise the level of the line outs (AN.L and AN.R, right mouse button on one of them automatically ajusts the level of the other accordingly), and then raise the volume of the track you want, checking that the track's destination is 'Analog'. > I also found that aplay could only work at 16 bit. I will update to > current cvs soon to check that though. > This is strange. Let me know, or give me more details, please. Using the hw alsa interface the hdsp can only be opened using all available channels, in non interleaved mode, and with a depth of 24 bits (packed in 4 bytes). To play a 16 bits soundfile with aplay you should use the plughw interface that will convert the signal on the fly to meet the card's requirements. Thomas --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Re: [linux-audio-user] novation remote 25 usb midi controller
Eric Dantan Rzewnicki wrote: > Jul 31 16:35:27 box1 kernel: hub.c: USB new device connect on bus1/1, > assigned device number 3 > Jul 31 16:35:27 box1 kernel: usb.c: USB device 3 (vend/prod > 0x1235/0x4661) is not claimed by any active driver. > Jul 31 16:35:30 box1 usb.agent: ... no modules for USB product > 1235/4661/101 > > box1:~# cat /proc/bus/usb/devices > ... > T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=1235 ProdID=4661 Rev= 1.01 > S: Manufacturer=Novation EMS > S: Product=ReMOTE25 V1.0 > C:* #Ifs= 1 Cfg#= 1 Atr=20 MxPwr=250mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) Class ff is "vendor-specific", so it's not 100% compatible with the USB Audio Specification. > Steve mentioned that i might need the snd-usb-midi driver instead, but > if i remember correctly it was merged into the snd-usb-audio driver a > while back. Is that true? Yes, it's true (that the former is not true). > I've read about special case quirks being added for specific usb > devices, but haven't understood what they are... Could that be possible > with the remote 25? Those are for devices that are almost compatible with the spec. This may or may not be the case with the Remote25. Please post the output of "lsusb -v". Regards, Clemens --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
