Re: re Zoom R16

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



El 10/18/2013 10:04 PM, Natanael Olaiz escribió:
> El 10/18/2013 08:27 AM, Clemens Ladisch escribió:
>> Natanael Olaiz wrote:
>>
>>> [...]
>>> On the other hand, audio doesn't seem to works straightforward. The
>>> device is seen, but I was not able to make it work with jack nor aplay.
>>
>> What happens?
>>
> I think it had some trouble with the sample rate or some of the other
> defined arguments, but I still didn't had many time to try different
> combinations...
>
> Plus, I don't know how to change the sample rate on the device. There is
> no control exposed for alsamixer, and I cannot change it from the device
> itself. When I tested it, as soon I started jackd the device changed the
> sample rate to 96kHz (when I was trying 48kHz from the jackd command,
> and the device was at 44.1kHz before), and (q)jack(ctl)d stopped like
> waiting for the device.
>
> ...
>
> But after my previous mail I tried again with alsa_in on a running 48kHz
> jackd server (Focusrite Saffire), and it worked!!!! I was able to use
> all the 8 input channels!!! (my impression was an incredibly -for the
> price...- clean sound!)
>
> I tried then adding an alsa_out (at the same time than alsa_in), but it
> said the device was already in use (I have a H2n and as far I can
> remember I can execute both together...)
I'm using the R16 as MIDI controller [R16 -> a2jmidid (alsa midi)->
(jack midi) ardour3] and audio capture [R16 -> alsa_in (alsa device with
8 input channels) -> ffado jack host].

It seems to work quite well when is running, but there is something not
fine:

 - it takes a long time to the device to appears as an alsa device since
it is detected from the kernel module

 - at least when it is not used (but I think it can occurs even when
streaming) it seems to block ALSA for moments. Meanwhile alsa seems is
unresponsive. Trying to start qjackctl (just open the frontend, not even
starting jack) opened an unresponsive widget. As soon I disconnected the
USB from the R16, the buttons and the control of the widget appeared.

- I was with the above described chain (jack + R16 alsa_in) , and all
the audio devices suddenly hanged. I saw in the R16 the sample rate at
96kHz (when it was -as JACK- at 48kHz)

A dmesg shows this :

> [  268.877864] 3:1:1: cannot get freq at ep 0x3
> [  272.489903] firewire_core 0000:07:00.0: created device fw1: GUID
> 00130e0100060dce, S400
> [  273.879240] 3:1:1: cannot set freq 44100 to ep 0x3
> [  278.903419] 3:1:1: cannot get freq at ep 0x3
> [  283.904662] 3:1:1: cannot set freq 44100 to ep 0x3
> [  286.633916] 3:1:1: cannot get freq at ep 0x3
> [  286.638154] 3:1:1: cannot set freq 44100 to ep 0x3
> [  286.671291] 3:1:1: usb_set_interface failed (-71)
> [  286.675542] 3:1:1: usb_set_interface failed (-71)
> [  286.679792] 3:1:1: usb_set_interface failed (-71)
>  "" * 20
> [  286.799821] 3:1:1: usb_set_interface failed (-71)
> [  286.830497] usb 1-1.4: USB disconnect, device number 3
> [  304.980599] hda-intel: IRQ timing workaround is activated for card
> #0. Suggest a bigger bdl_pos_adj.
> [  305.930727] usb 1-1.4: new high-speed USB device number 4 using
> ehci-pci
> [  306.022714] usb 1-1.4: config 1 interface 3 altsetting 0 bulk
> endpoint 0x1 has invalid maxpacket 64
> [  306.022717] usb 1-1.4: config 1 interface 3 altsetting 0 bulk
> endpoint 0x82 has invalid maxpacket 64
> [  306.023508] usb 1-1.4: New USB device found, idVendor=1686,
> idProduct=00dd
> [  306.023513] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [  306.023515] usb 1-1.4: Product: R16
> [  306.023517] usb 1-1.4: Manufacturer: ZOOM Corporation
> [  306.023519] usb 1-1.4: SerialNumber: 0
> [  311.025093] 4:1:1: cannot get freq at ep 0x3
> [  321.027467] 4:2:1: cannot get freq at ep 0x84
> [  331.090900] 4:1:1: cannot get freq at ep 0x3
> [  336.092152] 4:1:1: cannot set freq 44100 to ep 0x3
> [  341.115367] 4:1:1: cannot get freq at ep 0x3
> [  346.116557] 4:1:1: cannot get freq at ep 0x3
> [  356.273029] 4:1:1: cannot get freq at ep 0x3
> [  358.352531] 4:2:1: usb_set_interface failed (-110)
> [  820.268089] 4:1:1: cannot get freq at ep 0x3
> [  825.269267] 4:1:1: cannot set freq 44100 to ep 0x3

Any hint?


Thanks in advance,
Natanael.


>
> Soon I'll do more controlled tests and I'll update you. But it look so
> good!! :-)
>
> Thanks a lot!!!
>
> Natanael.
>> Regards,
>> Clemens
>>

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user





[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux