Hello.
Here i have :
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k4.9.0-3-amd64
and
uname -a
4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u1 (2017-06-18) x86_64
GNU/Linux
Le Mon, 7 Aug 2017 21:21:31 -0400,
Paul Davis <paul(a)linuxaudiosystems.com> a écrit :
oh, also: cat /proc/asound/version
On Mon, Aug 7, 2017 at 9:20 PM, Paul Davis
<paul(a)linuxaudiosystems.com> wrote:
> Anders - what does uname -a report on your system?
>
> I could get input to be received by the cpu on Linux only after
> plugging the device into a MacOS box, but even that is not proving
> reliable.
>
> On Mon, Aug 7, 2017 at 2:53 PM, Anders Hellquist <lau(a)hellquist.net>
> wrote:
>
>> I have used Ultra Ultralite AVB (not 624 AVB) to record electric
>> bass directly to Ardour and I have also recorded vocals but then I
>> routed the voice trough the internal mixer to let the vocalist
>> adjust the monitoring from Ardour and have built in DSP reverb for
>> better experience. Have not had any issues with routing or jackd
>> or the onboard stuff except the iPad application sometimes not
>> rendering the mixer/router pages correctly.
>>
>> I am running kxstudio (ubuntu 14.04 with rt-kernel and kxstudio
>> packages)
>>
>> I have a Debian 7 box that I can check with my AVB stuff but both
>> my cards are the classic MOTU Ultralite AVB.
>> If I can check anything more, I gladly will.
>>
>> Best regards, Anders
>>
>> mån 7 aug. 2017 kl. 20:04 skrev Paul Davis
>> <paul(a)linuxaudiosystems.com>om>:
>>> Could anyone working with the MOTU ultralite confirm that they
>>> have routing from analog inputs to the computer working? I can
>>> see signal showing up in the routing matrix and device page, and
>>> the device shows up as intended with 18 channels of input in
>>> JACK / ALSA, but I don't get any signal, even though I routed 6
>>> analog input channels to "To Computer 1" through "To Compute
6".
>>> Really puzzled ... everything suggests that this should just
>>> work....
>>>
>>> On Sun, Jul 23, 2017 at 6:26 AM, Anders Hellquist
>>> <lau(a)hellquist.net> wrote:
>>>
>>>> The linked product is a rj45 splitter that is very usable for
>>>> running two Ethernet connections thru a single cable but you
>>>> need one of these at both endpoints and this has nothing to do
>>>> with my use case. I know that a switch is the solution and was
>>>> only stating the limitation gnu Linux users will face because of
>>>> the missing control link.
>>>>
>>>> I am quite happy with the product and I usually only need one
>>>> card connected to my laptop and the things are just great as for
>>>> the rest of gnu AVB users. It was only a heads up for the issue.
>>>>
>>>> I hope that we in the future will have access without need for
>>>> the AVB switch, both for cost effectiveness and reduced
>>>> complexity.
>>>>
>>>> /Anders
>>>>
>>>> On Jul 23, 2017 01:49, <list(a)contacte.xyz> wrote:
>>>>
>>>>> Hello.
>>>>>
>>>>> For me there is no confusion here.
>>>>>
>>>>> Motu AVB's cards serie is not - officially - supported by MOTU
>>>>> for Gnu/Linux. Even without the «Linux» stamp on it from MOTU
>>>>> it's the more advanced card you can control without headache
>>>>> under Gnu/Linux.
>>>>>
>>>>> The feature you talk about is for proprietary Operating system
>>>>> with Motu's drivers - with some limitations.
>>>>>
>>>>> Either you bought the wrong cards, or using the wrong operating
>>>>> system for your need - it's only a guess.
>>>>>
>>>>> The AVB switch *is* your solution.
>>>>>
>>>>> Or you can try, the kernel module something like :
>>>>> CONFIG_USB_NET_* and try different devices under to see if your
>>>>> log show something when you plug any of your MOTU cards...
>>>>>
>>>>> Or you can try something like this :
>>>>>
>>>>>
http://i2.cdscdn.com/pdt2/5/2/2/1/700x700/auc3548389018522/r
>>>>> w/doubleur-de-port-rj-45-blinde.jpg
>>>>>
>>>>> sorry don't know the name in English...
>>>>>
>>>>> Let us know the result....
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> All the best.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 2017-07-23 00:20, Anders Hellquist wrote:
>>>>>
>>>>>> There is confusion for sure.
>>>>>>
>>>>>> if I link my two Motu ultralite AVB cards together by using
>>>>>> the two AVB ethernet sockets and a Cat5 or Cat6 cable. I have
>>>>>> used all ethernet connectors available and the AVB devices can
>>>>>> talk to each other but no other networking is available. If I
>>>>>> point a browser to any of the ip's of those boxes i will
not
>>>>>> get an answer since there is no possible route to those cards
>>>>>> that only have a link between them. The cards have no built in
>>>>>> wifi or extra ethernet jack.. How could I possibly connect to
>>>>>> them except by usb and Class Compliant Audio connection which
>>>>>> does not give me the extra IP over USB that the windows/osx
>>>>>> driver provides...
>>>>>>
>>>>>> I have never said anything about AVB over USB but only
>>>>>> mentioned the missing linux link which is the possibility to
>>>>>> access the http web gui trough the USB (or for cards with
>>>>>> Thunderbolt) driver provided ip-link (for control only)
>>>>>>
>>>>>> As I tried to explain. Linux users must have a AVB compliant
>>>>>> switch to get a network link to be able to manage Linked AVB
>>>>>> devices OR have windows/osx boxes connected via
>>>>>> USB/Thunderbolt to one of the AVB devices.
>>>>>>
>>>>>> Trust me, I am not confused but only stating the obvious that
>>>>>> linking to cards with just a cable will create an isolated AVB
>>>>>> cluster that will not be manageable from linux computers until
>>>>>> someone figures out how to write a driver to get the IP-over
>>>>>> USB passthru to work.
>>>>>>
>>>>>> /Anders
>>>>>>
>>>>>
>>>>>
>>>
>
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org