26 May
2017
26 May
'17
11:35 p.m.
Hello.
You know the AVB serie from MOTU.
We've talked about the 1248 & the UTRALITE AVB previously on the
Linux Audio Users list :
http://lists.linuxaudio.org/pipermail/linux-audio-user/2017-May/108050.html
http://lists.linuxaudio.org/pipermail/linux-audio-user/2017-March/107629.ht…
Now the MOTU 624 AVB.
Working with Gnu/Linux Debian 8.7.
The same as 1248 & ULTRALITE AVB, «real» class compliant, and web app
to control all the settings of the card from your browser.
Update firmware with 0 trouble through the web app interface :
http://achromatopsie.fr/list/00_installfirm.jpg
http://achromatopsie.fr/list/01_verifyingfirm.jpg
http://achromatopsie.fr/list/02_rebootfirm.jpg
http://achromatopsie.fr/list/03_successfirm.jpg
Some screen shot from the Routing menu (sorry need to zoom out, too
much inputs ! AVB disabled so no stream appears on the screen)
http://achromatopsie.fr/list/04_routing.jpg
Screen shot from the Mixing menu :
http://achromatopsie.fr/list/05_mixing.jpg
http://achromatopsie.fr/list/06_mixingzoom.jpg
http://achromatopsie.fr/list/07_mixingzoom1.jpg
And from the Device menu :
http://achromatopsie.fr/list/08_device.jpg
http://achromatopsie.fr/list/09_device2.jpg
Pluged with USB3, Gnu/Linux Debian 8.7 - Custom Kernel :
Linux 4.9.3-amd-64-20170113 #1 SMP PREEMPT Sat Apr 8
17:30:25 CEST 2017 x86_64 GNU/Linux
lsusb
Bus 003 Device 002: ID 07fd:0005 Mark of the Unicorn
lsusb -t
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
|__ Port 1: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 3, Class=Vendor Specific Class, Driver=, 5000M
|__ Port 1: Dev 2, If 4, Class=Vendor Specific Class, Driver=, 5000M
|__ Port 1: Dev 2, If 5, Class=Vendor Specific Class, Driver=, 5000M
aplay -l
**** Liste des Périphériques Matériels PLAYBACK ****
carte 0: D624 [624], périphérique 0: USB Audio [USB Audio]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
Made some quick record (guitar from emulated output of an amp,
microphone vocal) nothing to say, work perfectly. Nice preamp - for me
- clean, no hiss, no background noise, nice dynamic, can hear all my
bad notes and bad fingers on the guitar :)
The line input - jack - work also perfectly, respect the color of my
preamp (Warm Audio)
Did not try the optical I/O as i do not have any devices for it.
Thanks UC2, thanks MOTU.
Anyone have access to the Alsa project card's list and update ?
https://www.alsa-project.org/main/index.php/Matrix:Vendor-Mark_Of_The_Unico…
All the best !
20 Jul
20 Jul
4:57 p.m.
Fully confirmed. Here using Debian Jessie. Complete plug-n-play operation.
Incredible.
I predict that within 4-5 years, every external audio interface will use
MOTU's web configuration model. It is *so* great, not necessarily in the
sense of being the best possible UI for this, but because IT JUST WORKS
EVERYWHERE.
On Fri, May 26, 2017 at 5:35 PM, list <list(a)contacte.xyz> wrote:
Hello.
You know the AVB serie from MOTU.
We've talked about the 1248 & the UTRALITE AVB previously on the
Linux Audio Users list :
http://lists.linuxaudio.org/pipermail/linux-audio-user/
2017-May/108050.html
http://lists.linuxaudio.org/pipermail/linux-audio-user/
2017-March/107629.html
Now the MOTU 624 AVB.
Working with Gnu/Linux Debian 8.7.
The same as 1248 & ULTRALITE AVB, «real» class compliant, and web app
to control all the settings of the card from your browser.
Update firmware with 0 trouble through the web app interface :
http://achromatopsie.fr/list/00_installfirm.jpg
http://achromatopsie.fr/list/01_verifyingfirm.jpg
http://achromatopsie.fr/list/02_rebootfirm.jpg
http://achromatopsie.fr/list/03_successfirm.jpg
Some screen shot from the Routing menu (sorry need to zoom out, too
much inputs ! AVB disabled so no stream appears on the screen)
http://achromatopsie.fr/list/04_routing.jpg
Screen shot from the Mixing menu :
http://achromatopsie.fr/list/05_mixing.jpg
http://achromatopsie.fr/list/06_mixingzoom.jpg
http://achromatopsie.fr/list/07_mixingzoom1.jpg
And from the Device menu :
http://achromatopsie.fr/list/08_device.jpg
http://achromatopsie.fr/list/09_device2.jpg
Pluged with USB3, Gnu/Linux Debian 8.7 - Custom Kernel :
Linux 4.9.3-amd-64-20170113 #1 SMP PREEMPT Sat Apr 8
17:30:25 CEST 2017 x86_64 GNU/Linux
lsusb
Bus 003 Device 002: ID 07fd:0005 Mark of the Unicorn
lsusb -t
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
|__ Port 1: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 3, Class=Vendor Specific Class, Driver=, 5000M
|__ Port 1: Dev 2, If 4, Class=Vendor Specific Class, Driver=, 5000M
|__ Port 1: Dev 2, If 5, Class=Vendor Specific Class, Driver=, 5000M
aplay -l
**** Liste des Périphériques Matériels PLAYBACK ****
carte 0: D624 [624], périphérique 0: USB Audio [USB Audio]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
Made some quick record (guitar from emulated output of an amp,
microphone vocal) nothing to say, work perfectly. Nice preamp - for me
- clean, no hiss, no background noise, nice dynamic, can hear all my
bad notes and bad fingers on the guitar :)
The line input - jack - work also perfectly, respect the color of my
preamp (Warm Audio)
Did not try the optical I/O as i do not have any devices for it.
Thanks UC2, thanks MOTU.
Anyone have access to the Alsa project card's list and update ?
https://www.alsa-project.org/main/index.php/Matrix:Vendor-
Mark_Of_The_Unicorn
All the best !
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
21 Jul
21 Jul
1:56 a.m.
On Thu, 20 Jul 2017 10:56:59 -0400
Paul Davis <paul(a)linuxaudiosystems.com> wrote:
I predict that within 4-5 years, every external audio
interface will
use MOTU's web configuration model. It is *so* great, not necessarily
in the sense of being the best possible UI for this, but because IT
JUST WORKS EVERYWHERE.
Hallelujah !
-- David
11:25 p.m.
Do you get the local web GUI to work?
If using Windows or Mac, you get local access to the web GUI trough USB or
thunderbolt.
I have two devices and no switch and have no way to use the web GUI if I
connect both of them via Ethernet since my Linux laptop don't get the
"local host" type of link through USB.
I think the MOTU line is really nice but this is a sort of a problem in
Linux for now.. or do I miss something?
fre 21 juli 2017 kl. 01:57 skrev David <dplist(a)free.fr>fr>:
On Thu, 20 Jul 2017 10:56:59 -0400
Paul Davis <paul(a)linuxaudiosystems.com> wrote:
I predict that within 4-5 years, every external
audio interface will
use MOTU's web configuration model. It is *so* great, not necessarily
in the sense of being the best possible UI for this, but because IT
JUST WORKS EVERYWHERE.
Hallelujah !
-- David
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
22 Jul
22 Jul
7:02 p.m.
The web GUI works without issues.
I specifically bought the AVB because I trusted IP-over-RJ45 (the Ultralite
AVB has its own RJ45) more than IP-iver-USB, which would be true of (say)
the Ultralite MK4.
My impression was that either way, each device must end up with its own IP
address, and you just point the browser at the one you want to talk to. I
don't know much about how IP-over-USB works.
Note that if you have two devices, you're probably better off linking them
over AVB. I have the vague impression that they will show up as a single
device in the web GUI (but I'm not really clear on that).
On Fri, Jul 21, 2017 at 5:25 PM, Anders Hellquist <lau(a)hellquist.net> wrote:
Do you get the local web GUI to work?
If using Windows or Mac, you get local access to the web GUI trough USB or
thunderbolt.
I have two devices and no switch and have no way to use the web GUI if I
connect both of them via Ethernet since my Linux laptop don't get the
"local host" type of link through USB.
I think the MOTU line is really nice but this is a sort of a problem in
Linux for now.. or do I miss something?
fre 21 juli 2017 kl. 01:57 skrev David <dplist(a)free.fr>fr>:
On Thu, 20 Jul 2017 10:56:59 -0400
Paul Davis <paul(a)linuxaudiosystems.com> wrote:
I predict that within 4-5 years, every external
audio interface will
use MOTU's web configuration model. It is *so* great, not necessarily
in the sense of being the best possible UI for this, but because IT
JUST WORKS EVERYWHERE.
Hallelujah !
-- David
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
9:42 p.m.
And that is where the problem starts.. I have two Ultralite AVBs and if I
link them together. I have no longer access to the web GUI unless I get
myself an AVB compliant switch for an extra 300usd. If I were running
Windows or OSX. I could just connect to my linked AVB devices thru the IP
over USB link the driver provides and set up streams between them and do
whatever I wanted but that is not possible when using Linux which I am. I
could keep a dedicated windows or OSX box connected to the other AVB device
just to be able to set things up but how convenient is that?
Until I can set up AVB routes and configure stuff on my cards without the
extra cost of an AVB switch, this is for from perfect IMHO.
/Anders
On Jul 22, 2017 19:02, "Paul Davis" <paul(a)linuxaudiosystems.com> wrote:
The web GUI works without issues.
I specifically bought the AVB because I trusted IP-over-RJ45 (the
Ultralite AVB has its own RJ45) more than IP-iver-USB, which would be true
of (say) the Ultralite MK4.
My impression was that either way, each device must end up with its own IP
address, and you just point the browser at the one you want to talk to. I
don't know much about how IP-over-USB works.
Note that if you have two devices, you're probably better off linking them
over AVB. I have the vague impression that they will show up as a single
device in the web GUI (but I'm not really clear on that).
On Fri, Jul 21, 2017 at 5:25 PM, Anders Hellquist <lau(a)hellquist.net>
wrote:
Do you get the local web GUI to work?
If using Windows or Mac, you get local access to the web GUI trough USB
or thunderbolt.
I have two devices and no switch and have no way to use the web GUI if I
connect both of them via Ethernet since my Linux laptop don't get the
"local host" type of link through USB.
I think the MOTU line is really nice but this is a sort of a problem in
Linux for now.. or do I miss something?
fre 21 juli 2017 kl. 01:57 skrev David <dplist(a)free.fr>fr>:
On Thu, 20 Jul 2017 10:56:59 -0400
Paul Davis <paul(a)linuxaudiosystems.com> wrote:
I predict that within 4-5 years, every external
audio interface will
use MOTU's web configuration model. It is *so* great, not necessarily
in the sense of being the best possible UI for this, but because IT
JUST WORKS EVERYWHERE.
Hallelujah !
-- David
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
10:18 p.m.
What IP address do both units show from the main menu when you connect them
together? What happens when you point a browser at either of those
addresses?
On Sat, Jul 22, 2017 at 3:42 PM, Anders Hellquist <lau(a)hellquist.net> wrote:
And that is where the problem starts.. I have two
Ultralite AVBs and if I
link them together. I have no longer access to the web GUI unless I get
myself an AVB compliant switch for an extra 300usd. If I were running
Windows or OSX. I could just connect to my linked AVB devices thru the IP
over USB link the driver provides and set up streams between them and do
whatever I wanted but that is not possible when using Linux which I am. I
could keep a dedicated windows or OSX box connected to the other AVB device
just to be able to set things up but how convenient is that?
Until I can set up AVB routes and configure stuff on my cards without the
extra cost of an AVB switch, this is for from perfect IMHO.
/Anders
On Jul 22, 2017 19:02, "Paul Davis" <paul(a)linuxaudiosystems.com> wrote:
> The web GUI works without issues.
>
> I specifically bought the AVB because I trusted IP-over-RJ45 (the
> Ultralite AVB has its own RJ45) more than IP-iver-USB, which would be true
> of (say) the Ultralite MK4.
>
> My impression was that either way, each device must end up with its own
> IP address, and you just point the browser at the one you want to talk to.
> I don't know much about how IP-over-USB works.
>
> Note that if you have two devices, you're probably better off linking
> them over AVB. I have the vague impression that they will show up as a
> single device in the web GUI (but I'm not really clear on that).
>
>
> On Fri, Jul 21, 2017 at 5:25 PM, Anders Hellquist <lau(a)hellquist.net>
> wrote:
>
>> Do you get the local web GUI to work?
>>
>> If using Windows or Mac, you get local access to the web GUI trough USB
>> or thunderbolt.
>>
>> I have two devices and no switch and have no way to use the web GUI if I
>> connect both of them via Ethernet since my Linux laptop don't get the
>> "local host" type of link through USB.
>>
>> I think the MOTU line is really nice but this is a sort of a problem in
>> Linux for now.. or do I miss something?
>>
>> fre 21 juli 2017 kl. 01:57 skrev David <dplist(a)free.fr>fr>:
>>
>>> On Thu, 20 Jul 2017 10:56:59 -0400
>>> Paul Davis <paul(a)linuxaudiosystems.com> wrote:
>>>
>>> > I predict that within 4-5 years, every external audio interface will
>>> > use MOTU's web configuration model. It is *so* great, not
necessarily
>>> > in the sense of being the best possible UI for this, but because IT
>>> > JUST WORKS EVERYWHERE.
>>>
>>> Hallelujah !
>>>
>>> -- David
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>> Linux-audio-user(a)lists.linuxaudio.org
>>> http://lists.linuxaudio.org/listinfo/linux-audio-user
>>>
>>
>>
>
10:19 p.m.
there also seems to be some confusion ... there is no possibility to route
AVB via IP-over-USB on any platform, AFAIK.
On Sat, Jul 22, 2017 at 4:18 PM, Paul Davis <paul(a)linuxaudiosystems.com>
wrote:
What IP address do both units show from the main menu
when you connect
them together? What happens when you point a browser at either of those
addresses?
On Sat, Jul 22, 2017 at 3:42 PM, Anders Hellquist <lau(a)hellquist.net>
wrote:
And that is where the problem starts.. I have two
Ultralite AVBs and if I
link them together. I have no longer access to the web GUI unless I get
myself an AVB compliant switch for an extra 300usd. If I were running
Windows or OSX. I could just connect to my linked AVB devices thru the IP
over USB link the driver provides and set up streams between them and do
whatever I wanted but that is not possible when using Linux which I am. I
could keep a dedicated windows or OSX box connected to the other AVB device
just to be able to set things up but how convenient is that?
Until I can set up AVB routes and configure stuff on my cards without the
extra cost of an AVB switch, this is for from perfect IMHO.
/Anders
On Jul 22, 2017 19:02, "Paul Davis" <paul(a)linuxaudiosystems.com> wrote:
> The web GUI works without issues.
>
> I specifically bought the AVB because I trusted IP-over-RJ45 (the
> Ultralite AVB has its own RJ45) more than IP-iver-USB, which would be true
> of (say) the Ultralite MK4.
>
> My impression was that either way, each device must end up with its own
> IP address, and you just point the browser at the one you want to talk to.
> I don't know much about how IP-over-USB works.
>
> Note that if you have two devices, you're probably better off linking
> them over AVB. I have the vague impression that they will show up as a
> single device in the web GUI (but I'm not really clear on that).
>
>
> On Fri, Jul 21, 2017 at 5:25 PM, Anders Hellquist <lau(a)hellquist.net>
> wrote:
>
>> Do you get the local web GUI to work?
>>
>> If using Windows or Mac, you get local access to the web GUI trough USB
>> or thunderbolt.
>>
>> I have two devices and no switch and have no way to use the web GUI if
>> I connect both of them via Ethernet since my Linux laptop don't get the
>> "local host" type of link through USB.
>>
>> I think the MOTU line is really nice but this is a sort of a problem in
>> Linux for now.. or do I miss something?
>>
>> fre 21 juli 2017 kl. 01:57 skrev David <dplist(a)free.fr>fr>:
>>
>>> On Thu, 20 Jul 2017 10:56:59 -0400
>>> Paul Davis <paul(a)linuxaudiosystems.com> wrote:
>>>
>>> > I predict that within 4-5 years, every external audio interface will
>>> > use MOTU's web configuration model. It is *so* great, not
necessarily
>>> > in the sense of being the best possible UI for this, but because IT
>>> > JUST WORKS EVERYWHERE.
>>>
>>> Hallelujah !
>>>
>>> -- David
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>> Linux-audio-user(a)lists.linuxaudio.org
>>> http://lists.linuxaudio.org/listinfo/linux-audio-user
>>>
>>
>>
>
23 Jul
23 Jul
12:20 a.m.
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
2017-07-22 22:19 GMT+02:00 Paul Davis <paul(a)linuxaudiosystems.com>om>:
there also seems to be some confusion ... there is no
possibility to route
AVB via IP-over-USB on any platform, AFAIK.
On Sat, Jul 22, 2017 at 4:18 PM, Paul Davis <paul(a)linuxaudiosystems.com>
wrote:
What IP address do both units show from the main
menu when you connect
them together? What happens when you point a browser at either of those
addresses?
On Sat, Jul 22, 2017 at 3:42 PM, Anders Hellquist <lau(a)hellquist.net>
wrote:
And that is where the problem starts.. I have two
Ultralite AVBs and if
I link them together. I have no longer access to the web GUI unless I get
myself an AVB compliant switch for an extra 300usd. If I were running
Windows or OSX. I could just connect to my linked AVB devices thru the IP
over USB link the driver provides and set up streams between them and do
whatever I wanted but that is not possible when using Linux which I am. I
could keep a dedicated windows or OSX box connected to the other AVB device
just to be able to set things up but how convenient is that?
Until I can set up AVB routes and configure stuff on my cards without
the extra cost of an AVB switch, this is for from perfect IMHO.
/Anders
On Jul 22, 2017 19:02, "Paul Davis" <paul(a)linuxaudiosystems.com> wrote:
> The web GUI works without issues.
>
> I specifically bought the AVB because I trusted IP-over-RJ45 (the
> Ultralite AVB has its own RJ45) more than IP-iver-USB, which would be true
> of (say) the Ultralite MK4.
>
> My impression was that either way, each device must end up with its own
> IP address, and you just point the browser at the one you want to talk to.
> I don't know much about how IP-over-USB works.
>
> Note that if you have two devices, you're probably better off linking
> them over AVB. I have the vague impression that they will show up as a
> single device in the web GUI (but I'm not really clear on that).
>
>
> On Fri, Jul 21, 2017 at 5:25 PM, Anders Hellquist <lau(a)hellquist.net>
> wrote:
>
>> Do you get the local web GUI to work?
>>
>> If using Windows or Mac, you get local access to the web GUI trough
>> USB or thunderbolt.
>>
>> I have two devices and no switch and have no way to use the web GUI if
>> I connect both of them via Ethernet since my Linux laptop don't get the
>> "local host" type of link through USB.
>>
>> I think the MOTU line is really nice but this is a sort of a problem
>> in Linux for now.. or do I miss something?
>>
>> fre 21 juli 2017 kl. 01:57 skrev David <dplist(a)free.fr>fr>:
>>
>>> On Thu, 20 Jul 2017 10:56:59 -0400
>>> Paul Davis <paul(a)linuxaudiosystems.com> wrote:
>>>
>>> > I predict that within 4-5 years, every external audio interface will
>>> > use MOTU's web configuration model. It is *so* great, not
>>> necessarily
>>> > in the sense of being the best possible UI for this, but because IT
>>> > JUST WORKS EVERYWHERE.
>>>
>>> Hallelujah !
>>>
>>> -- David
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>> Linux-audio-user(a)lists.linuxaudio.org
>>> http://lists.linuxaudio.org/listinfo/linux-audio-user
>>>
>>
>>
>
1:49 a.m.
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/rw/doubleur-de-p…
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
12:26 p.m.
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
7 Aug
7 Aug
8:04 p.m.
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
>>
>
>
8:53 p.m.
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/rw/doubleur-de-p…
>
> 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
>>
>
>
8 Aug
8 Aug
3:20 a.m.
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/
>>> rw/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
>>>>
>>>
>>>
>
3:21 a.m.
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
>>>>
>>>
>>>
>
3:34 a.m.
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
>>>>>>
>>>>>
>>>>>
>>>
>
9:44 a.m.
Hello !
I am at work so I don't have access to the AVB card or the computer at the
moment but will report back in maybe 9 hours
The kernel I believe is 3.13-126 Low-latency 64-bit from the ubuntu repo
I'll get the true information when at the computer
/Anders
2017-08-08 3:34 GMT+02:00 list <list(a)contacte.xyz>yz>:
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
https://lists.linuxaudio.org/listinfo/linux-audio-user
7:27 p.m.
Hi again and sorry for the delay
uname -a
Linux 3.13.0-126-lowlatency #175-Ubuntu SMP PREEMPT Thu Jul 20 19:13:12 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k3.13.0-126-lowlatency.
/Anders
8:18 p.m.
I got mine to work (kernel 4.9) but it seems a little unreliable and may
have needed to be used on a MacOS box first. Still trying to figure out
what causes the lack of signal at the CPU. Certainly not caused by config
changes on the MOTU itself.
On Tue, Aug 8, 2017 at 1:27 PM, Anders Hellquist <lau(a)hellquist.net> wrote:
Hi again and sorry for the delay
uname -a
Linux 3.13.0-126-lowlatency #175-Ubuntu SMP PREEMPT Thu Jul 20 19:13:12
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k3.13.0-126-lowlatency.
/Anders
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
8:57 p.m.
Ok, the only quirk with my setup that others have experienced too according
to Ardour forum threads is that I often need two to four attempts to start
jackd (actually using cadence in kxstudio to starti jackd) but when
successfully started, it has never failed.
Sometimes it starts on first attempt and sometimes I need more than 5 but
usually on second or third.
I hope you can figure out whats causing the unreliable behaviour on your
end.
/Anders
2017-08-08 20:18 GMT+02:00 Paul Davis <paul(a)linuxaudiosystems.com>om>:
I got mine to work (kernel 4.9) but it seems a little
unreliable and may
have needed to be used on a MacOS box first. Still trying to figure out
what causes the lack of signal at the CPU. Certainly not caused by config
changes on the MOTU itself.
On Tue, Aug 8, 2017 at 1:27 PM, Anders Hellquist <lau(a)hellquist.net>
wrote:
Hi again and sorry for the delay
uname -a
Linux 3.13.0-126-lowlatency #175-Ubuntu SMP PREEMPT Thu Jul 20 19:13:12
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k3.13.0-126-lowlatency.
/Anders
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
9:33 p.m.
That seems to be a function of the device taking a noticeably long time to
switch sample rates and be "ready for action". If JACK changes the device
state as a part of the startup, it takes a while before it is actually
ready.
On Tue, Aug 8, 2017 at 2:57 PM, Anders Hellquist <lau(a)hellquist.net> wrote:
Ok, the only quirk with my setup that others have
experienced too
according to Ardour forum threads is that I often need two to four attempts
to start jackd (actually using cadence in kxstudio to starti jackd) but
when successfully started, it has never failed.
Sometimes it starts on first attempt and sometimes I need more than 5 but
usually on second or third.
I hope you can figure out whats causing the unreliable behaviour on your
end.
/Anders
2017-08-08 20:18 GMT+02:00 Paul Davis <paul(a)linuxaudiosystems.com>om>:
I got mine to work (kernel 4.9) but it seems a
little unreliable and may
have needed to be used on a MacOS box first. Still trying to figure out
what causes the lack of signal at the CPU. Certainly not caused by config
changes on the MOTU itself.
On Tue, Aug 8, 2017 at 1:27 PM, Anders Hellquist <lau(a)hellquist.net>
wrote:
Hi again and sorry for the delay
uname -a
Linux 3.13.0-126-lowlatency #175-Ubuntu SMP PREEMPT Thu Jul 20 19:13:12
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k3.13.0-126-lowlatency.
/Anders
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
9:40 p.m.
Could be but the device remembers the sample rate and everything else
between bootups and the display is showing 48k before I hit start in
cadence (or qjackctl) so from my point of view, sample rate change does not
occur..
I don't think waiting before launching jack helps but I can try that and
see if it helps.
/Anders
On Aug 8, 2017 9:33 PM, "Paul Davis" <paul(a)linuxaudiosystems.com> wrote:
That seems to be a function of the device taking a
noticeably long time to
switch sample rates and be "ready for action". If JACK changes the device
state as a part of the startup, it takes a while before it is actually
ready.
On Tue, Aug 8, 2017 at 2:57 PM, Anders Hellquist <lau(a)hellquist.net>
wrote:
Ok, the only quirk with my setup that others have
experienced too
according to Ardour forum threads is that I often need two to four attempts
to start jackd (actually using cadence in kxstudio to starti jackd) but
when successfully started, it has never failed.
Sometimes it starts on first attempt and sometimes I need more than 5 but
usually on second or third.
I hope you can figure out whats causing the unreliable behaviour on your
end.
/Anders
2017-08-08 20:18 GMT+02:00 Paul Davis <paul(a)linuxaudiosystems.com>om>:
I got mine to work (kernel 4.9) but it seems a
little unreliable and may
have needed to be used on a MacOS box first. Still trying to figure out
what causes the lack of signal at the CPU. Certainly not caused by config
changes on the MOTU itself.
On Tue, Aug 8, 2017 at 1:27 PM, Anders Hellquist <lau(a)hellquist.net>
wrote:
Hi again and sorry for the delay
uname -a
Linux 3.13.0-126-lowlatency #175-Ubuntu SMP PREEMPT Thu Jul 20 19:13:12
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k3.13.0-126-lowlatency.
/Anders
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
9 Aug
9 Aug
12:15 a.m.
So the story seems to be this: ALSA stream reconfiguration (the sort of
thing done by JACK or by an application running on top of ALSA) *while the
device is running* will result in random re-arrangement of the input
channel mapping. In particular, JACK does this when an xrun happens (also
when dynamically changing the buffer size).
What the MOTU web app shows as a routing to "To Computer N" can end up sort
of anywhere in the full range of possibilities. Result: it looks as if no
signal is flowing through to the CPU, but it is ... just on the wrong
channel(s).
Restarting the device at the ALSA level will change it again, and again ...
until it is finally fixed.
Tentative diagnostic: ALSA driver bug.
On Tue, Aug 8, 2017 at 3:40 PM, Anders Hellquist <lau(a)hellquist.net> wrote:
Could be but the device remembers the sample rate and
everything else
between bootups and the display is showing 48k before I hit start in
cadence (or qjackctl) so from my point of view, sample rate change does not
occur..
I don't think waiting before launching jack helps but I can try that and
see if it helps.
/Anders
On Aug 8, 2017 9:33 PM, "Paul Davis" <paul(a)linuxaudiosystems.com> wrote:
> That seems to be a function of the device taking a noticeably long time
> to switch sample rates and be "ready for action". If JACK changes the
> device state as a part of the startup, it takes a while before it is
> actually ready.
>
> On Tue, Aug 8, 2017 at 2:57 PM, Anders Hellquist <lau(a)hellquist.net>
> wrote:
>
>> Ok, the only quirk with my setup that others have experienced too
>> according to Ardour forum threads is that I often need two to four attempts
>> to start jackd (actually using cadence in kxstudio to starti jackd) but
>> when successfully started, it has never failed.
>> Sometimes it starts on first attempt and sometimes I need more than 5
>> but usually on second or third.
>>
>> I hope you can figure out whats causing the unreliable behaviour on your
>> end.
>>
>> /Anders
>>
>> 2017-08-08 20:18 GMT+02:00 Paul Davis <paul(a)linuxaudiosystems.com>om>:
>>
>>> I got mine to work (kernel 4.9) but it seems a little unreliable and
>>> may have needed to be used on a MacOS box first. Still trying to figure out
>>> what causes the lack of signal at the CPU. Certainly not caused by config
>>> changes on the MOTU itself.
>>>
>>> On Tue, Aug 8, 2017 at 1:27 PM, Anders Hellquist <lau(a)hellquist.net>
>>> wrote:
>>>
>>>> Hi again and sorry for the delay
>>>>
>>>> uname -a
>>>>
>>>> Linux 3.13.0-126-lowlatency #175-Ubuntu SMP PREEMPT Thu Jul 20
>>>> 19:13:12 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>>>>
>>>>
>>>>
>>>> cat /proc/asound/version
>>>>
>>>> Advanced Linux Sound Architecture Driver Version
>>>> k3.13.0-126-lowlatency.
>>>>
>>>>
>>>> /Anders
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Linux-audio-user mailing list
>>>> Linux-audio-user(a)lists.linuxaudio.org
>>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>>
>>>>
>>>
>>
>
12:41 a.m.
On Tue, August 8, 2017 5:15 pm, Paul Davis wrote:
Tentative diagnostic: ALSA driver bug.
Isn't this a class compliant USB device? Does the bug seem likely to
affect only this one device, or is this something that for some reason
other people have just not reported with other devices yet, but should be
expected to affect all multi-channel USB devices?
--
Chris Caudle
1:09 a.m.
There are some reports of similar issues even with non-USB devices, so I
suspect it is an ALSA bug. Probably not that hard to debug and fix, but I'm
not clear that I have the time or energy for it.
On Tue, Aug 8, 2017 at 6:41 PM, Chris Caudle <chris(a)chriscaudle.org> wrote:
On Tue, August 8, 2017 5:15 pm, Paul Davis wrote:
Tentative diagnostic: ALSA driver bug.
Isn't this a class compliant USB device? Does the bug seem likely to
affect only this one device, or is this something that for some reason
other people have just not reported with other devices yet, but should be
expected to affect all multi-channel USB devices?
--
Chris Caudle
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
1:53 p.m.
Just for information
Reading up on Motu 624 AVB a bit and my guess is that there are a lot of
difference under the hood compared to my Utralite AVB cards, I have no idea
if that is a cause of i/o channel mapping issues though
Quick compare
624 has Gigabit Eth, USB3, Thunderbolt, ESS Sabre 32 Ultra DACs, Color
display and capable of handling 8 blocks of AVB streams in all Sample rates
and is cheaper
vs
Ultralite has 100Mbit, USB2, no Thuderbolt, cheaper converters but close
spec wise, blue low res display, can handle 3 blocks of streams in 44k1/48k
and two blocks in 88 and only one block in 192k
The only pro with Ultralite AVB is Midi in/Midi Out, 2 more inputs and 2
more outputs
/Anders
2017-08-09 1:09 GMT+02:00 Paul Davis <paul(a)linuxaudiosystems.com>om>:
There are some reports of similar issues even with
non-USB devices, so I
suspect it is an ALSA bug. Probably not that hard to debug and fix, but I'm
not clear that I have the time or energy for it.
On Tue, Aug 8, 2017 at 6:41 PM, Chris Caudle <chris(a)chriscaudle.org>
wrote:
On Tue, August 8, 2017 5:15 pm, Paul Davis
wrote:
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
Tentative diagnostic: ALSA driver bug.
Isn't this a class compliant USB device? Does the bug seem likely to
affect only this one device, or is this something that for some reason
other people have just not reported with other devices yet, but should be
expected to affect all multi-channel USB devices?
--
Chris Caudle
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
10 Aug
10 Aug
5:19 a.m.
To add informations :
The 624 is a stripped down - in size/inputs - version of the 1248, using
the same DAC.
Easier to put in a bag to go on set, than the 19" rack size of the
1248.
So, it's the same for the 624, it take 2 or more time to be started by
jackd, either on command line, or with qjackctl.
All the best.
Le Wed, 9 Aug 2017 13:53:28 +0200,
Anders Hellquist <lau(a)hellquist.net> a écrit :
Just for information
Reading up on Motu 624 AVB a bit and my guess is that there are a lot
of difference under the hood compared to my Utralite AVB cards, I
have no idea if that is a cause of i/o channel mapping issues though
Quick compare
624 has Gigabit Eth, USB3, Thunderbolt, ESS Sabre 32 Ultra DACs, Color
display and capable of handling 8 blocks of AVB streams in all Sample
rates and is cheaper
vs
Ultralite has 100Mbit, USB2, no Thuderbolt, cheaper converters but
close spec wise, blue low res display, can handle 3 blocks of streams
in 44k1/48k and two blocks in 88 and only one block in 192k
The only pro with Ultralite AVB is Midi in/Midi Out, 2 more inputs
and 2 more outputs
/Anders
10:33 p.m.
On Aug 10, 2017 06:19, "list" <list(a)contacte.xyz> wrote:
To add informations :
The 624 is a stripped down - in size/inputs - version of the 1248, using
the same DAC.
I don't know if that's correct, the 1248 doesn't have usb3, so I guess
driver wise there are differences too.
Cheers
Moshe
11 Aug
11 Aug
12:27 p.m.
Hello.
And sometimes, with Ultralite AVB and 624, when fresh booting/start the
computer/cards. Launch qjackctl to start Jack and then Jack:
Card unusable, jack fail completly to stop - have to kill.
To recover from this i have to power off the card, and start again
jack/qjackctl.
I was suspected and usb problem - got an old motherboard, with no more
bios update for the USB 3.
Hope this maybe help.
All the best.
JackEngine::ClientNotify: no callback for notification = 3 Jack:
**** alsa_pcm: xrun of at least -309192.928 msecs Jack: ALSA XRun
wait_status = 0 Jack: JackSocketServerChannel::Execute : fPollTable i =
1 fd = 11 Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -309328.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -309464.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -309601.024 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -309736.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -309873.024 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -310008.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -310144.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -310280.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -310416.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -310552.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -310688.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -310824.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -310960.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -311096.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -311232.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -311368.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -311505.024 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -311641.024 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -311777.024 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -311913.024 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -312048.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -312184.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -312320.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -312457.248 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -312593.120 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -312728.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -312864.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -313000.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -313136.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -313272.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -313408.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -313544.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -313680.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -313816.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -313952.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -314088.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -314225.216 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -314360.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -314497.088 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -314632.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -314769.216 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -314905.088 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -315040.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -315176.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -315312.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -315449.088 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -315584.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -315720.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -315856.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -315992.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -316129.088 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -316264.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -316400.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -316537.056 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -316673.056 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -316808.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -316945.056 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -317081.056 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -317216.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -317352.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -317488.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -317625.056 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -317760.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -317896.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -318032.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -318168.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -318304.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -318440.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -318576.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -318712.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -318848.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -318985.184 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -319120.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -319256.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -319392.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -319528.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -319664.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -319800.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -319936.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -320072.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -320209.024 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -320344.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -320481.152 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -320616.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -320752.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -320888.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -321025.024 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -321160.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -321296.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -321432.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -321568.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -321705.024 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -321840.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -321976.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -322112.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -322248.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -322384.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -322520.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -322656.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -322792.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -322928.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -323064.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -323200.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -323336.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -323472.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -323608.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -323748.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -323884.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -324020.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -324156.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -324293.120 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -324429.120 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -324564.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -324700.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -324836.896 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -324972.864 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -325108.864 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -325244.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -325380.864 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -325516.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -325652.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -325788.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -325924.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -326060.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -326196.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -326332.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -326469.216 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -326604.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -326740.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -326877.216 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -327012.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -327148.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -327284.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -327420.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -327556.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -327692.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -327828.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -327964.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
12:13:43.703 JACK s'arrête...
Jack main caught signal 15
Jack: JackServer::Stop
Jack: JackThreadedDriver::Stop
Jack: JackPosixThread::Stop
Jack: **** alsa_pcm: xrun of at least -328100.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -328236.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -328372.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -328508.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -328644.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -328780.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -328916.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -329052.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -329188.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -329324.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -329460.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -329596.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -329733.184 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -329868.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
12:13:45.557 JACK s'arrête...
Jack: **** alsa_pcm: xrun of at least -330005.184 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -330140.832 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -330277.088 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -330412.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -330548.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -330685.056 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -330820.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -330956.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -331092.992 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -331228.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -331364.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -331500.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -331636.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -331773.088 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -331908.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -332044.992 msecs
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: ALSA XRun wait_status = 0
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -332180.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -332316.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -332452.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -332588.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -332724.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -332861.088 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -332996.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -333132.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -333268.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -333404.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -333540.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -333676.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -333812.960 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -333948.928 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -334085.184 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: **** alsa_pcm: xrun of at least -334221.056 msecs
Jack: ALSA XRun wait_status = 0
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 11
Jack: JackRequest::Notification
Jack: JackEngine::ClientNotify: no callback for notification = 3
Jack: JackEngine::ClientNotify: no callback for notification = 3
12:13:49.901 JACK s'arrête...
12:13:49.912 JACK a été arrêté
12:13:49.913 JACK a planté.
Le Tue, 8 Aug 2017 18:15:24 -0400,
Paul Davis <paul(a)linuxaudiosystems.com> a écrit :
So the story seems to be this: ALSA stream
reconfiguration (the sort
of thing done by JACK or by an application running on top of ALSA)
*while the device is running* will result in random re-arrangement of
the input channel mapping. In particular, JACK does this when an xrun
happens (also when dynamically changing the buffer size).
What the MOTU web app shows as a routing to "To Computer N" can end
up sort of anywhere in the full range of possibilities. Result: it
looks as if no signal is flowing through to the CPU, but it is ...
just on the wrong channel(s).
Restarting the device at the ALSA level will change it again, and
again ... until it is finally fixed.
Tentative diagnostic: ALSA driver bug.
7 Aug
7 Aug
8:57 p.m.
Maybe downgrading the firmware will change things?
/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/rw/doubleur-de-p…
>
> 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
>>
>
>
23 Jul
23 Jul
1:12 a.m.
Hello.
Updated my Jessie for a «Stretch» Debian 9.
The cards work the same, perfect.
Little glitch at first when i start Jackd - with Qjackctl or command
line - the card never starts the fist time, have to do it again...not a
big deal.
4-5 years ago i was grumbling about Audio brands not supporting
Gnu/Linux out of the box and make my - our - life miserable, and
wondered why i can access all my router/modem/switch through a web app
and not audio cards the same way....
I guess even people with proprietary operating system get bored with
update troubles, compatibility with Os version/driver and trash a
perfectly working card after upgrading they computer/Os and discovered
that the driver no more exist for the new version of Os...maybe MOTU
heard that...let's hope for the best...
On 2017-07-20 16:56, Paul Davis wrote:
Fully confirmed. Here using Debian Jessie. Complete
plug-n-play
operation. Incredible.
I predict that within 4-5 years, every external audio interface will
use MOTU's web configuration model. It is *so* great, not necessarily
in the sense of being the best possible UI for this, but because IT
JUST WORKS EVERYWHERE.
10 Oct
10 Oct
4:35 p.m.
On 7/20/17 10:56, Paul Davis wrote:
Fully confirmed. Here using Debian Jessie. Complete
plug-n-play
operation. Incredible.
I predict that within 4-5 years, every external audio interface will use
MOTU's web configuration model. It is *so* great, not necessarily in the
sense of being the best possible UI for this, but because IT JUST WORKS
EVERYWHERE.
Is MOTU 8A a similar model? Would work just the same as the 624?
17 Oct
17 Oct
3:29 p.m.
I would expect Motu 8A to work out of the box
*Just somthing important for Class compliant usage. (IMHO)*
A heads up related to Class Compliant mode and Motu AVB devices
The latest firmware for Motu Ultralite AVB removed a setting where the user
could set the USB Mode and enable more than 24channel over USB
The total number of channels was restricted by Samplerate but if the mode
was set to 44k/48k1 it was possible to run up to 64channels over USB
This is no longer possible from latest firmware where 24channel is a hard
limit due to stability. If using windowsor OSX driver, extended channel
count is still available but not in CC mode.
I do not know if this is true for other Motu AVB devices but I would guess
it also aplies to them.
It is safe to downgrade the firmware and use the extended channel count but
new features and fixes to DSP-stuff and AVB stack (if there will be) will
probably only be implemented in the newer channel count restricted firmwares
Let hope they reimplement the setting later so the user can use more than
24 channel if neede.
Motu rep:
"That's correct. The latest firmware limited the channel count when using
the class compliant drivers. You can only access 64 channels when using the
Mac or Windows drivers that we provide on motu.com/download. If you're not
looking to use the driver, or are on an OS other than Mac or Windows, feel
free to downgrade to the previous firmware."
.
/Anders
2017-10-10 16:35 GMT+02:00 Bernardo Barros <bernardo.barros(a)nyu.edu>du>:
On 7/20/17 10:56, Paul Davis wrote:
Fully confirmed. Here using Debian Jessie.
Complete plug-n-play
operation. Incredible.
I predict that within 4-5 years, every external audio interface will use
MOTU's web configuration model. It is *so* great, not necessarily in the
sense of being the best possible UI for this, but because IT JUST WORKS
EVERYWHERE.
Is MOTU 8A a similar model? Would work just the same as the 624?
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
18 Dec
18 Dec
10:39 a.m.
Hello, that's very interesting.
I just gave a try a motu 624 with ubuntu lowlatency kernel, but also with a
generic kernel too.
I have the following problem:
Once I test tone with a pure sinewave (easy and reliable way to test a
sound),after a few
seconds periodic clicks are quite audible. Actually these clicks are present
with any kind of sound,
just more difficult to track if the sound is not a pure sinewave.
Did you test your sound using a pure tone in debian?
Do you have the same issue? I tried different workarounds but the clicks are
still there. For sure isnot a jack issue,because using alsa directly I had
the same problem.
Any feedback appreciated from anyone who tried the new Motu products with
linux.
Thanks a lot!
list wrote
Hello.
You know the AVB serie from MOTU.
We've talked about the 1248 & the UTRALITE AVB previously on the
Linux Audio Users list :
http://lists.linuxaudio.org/pipermail/linux-audio-user/2017-May/108050.html
http://lists.linuxaudio.org/pipermail/linux-audio-user/2017-March/107629.ht…
Now the MOTU 624 AVB.
Working with Gnu/Linux Debian 8.7.
The same as 1248 & ULTRALITE AVB, «real» class compliant, and web app
to control all the settings of the card from your browser.
Update firmware with 0 trouble through the web app interface :
http://achromatopsie.fr/list/00_installfirm.jpg
http://achromatopsie.fr/list/01_verifyingfirm.jpg
http://achromatopsie.fr/list/02_rebootfirm.jpg
http://achromatopsie.fr/list/03_successfirm.jpg
Some screen shot from the Routing menu (sorry need to zoom out, too
much inputs ! AVB disabled so no stream appears on the screen)
http://achromatopsie.fr/list/04_routing.jpg
Screen shot from the Mixing menu :
http://achromatopsie.fr/list/05_mixing.jpg
http://achromatopsie.fr/list/06_mixingzoom.jpg
http://achromatopsie.fr/list/07_mixingzoom1.jpg
And from the Device menu :
http://achromatopsie.fr/list/08_device.jpg
http://achromatopsie.fr/list/09_device2.jpg
Pluged with USB3, Gnu/Linux Debian 8.7 - Custom Kernel :
Linux 4.9.3-amd-64-20170113 #1 SMP PREEMPT Sat Apr 8
17:30:25 CEST 2017 x86_64 GNU/Linux
lsusb
Bus 003 Device 002: ID 07fd:0005 Mark of the Unicorn
lsusb -t
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
|__ Port 1: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 3, Class=Vendor Specific Class, Driver=, 5000M
|__ Port 1: Dev 2, If 4, Class=Vendor Specific Class, Driver=, 5000M
|__ Port 1: Dev 2, If 5, Class=Vendor Specific Class, Driver=, 5000M
aplay -l
**** Liste des Périphériques Matériels PLAYBACK ****
carte 0: D624 [624], périphérique 0: USB Audio [USB Audio]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
Made some quick record (guitar from emulated output of an amp,
microphone vocal) nothing to say, work perfectly. Nice preamp - for me
- clean, no hiss, no background noise, nice dynamic, can hear all my
bad notes and bad fingers on the guitar :)
The line input - jack - work also perfectly, respect the color of my
preamp (Warm Audio)
Did not try the optical I/O as i do not have any devices for it.
Thanks UC2, thanks MOTU.
Anyone have access to the Alsa project card's list and update ?
https://www.alsa-project.org/main/index.php/Matrix:Vendor-Mark_Of_The_Unico…
All the best !
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
19 Dec
19 Dec
12:07 a.m.
Hello.
Can you give the precise way you did this - i prefer command line tools
if possible.
As i got one, i can try to reproduce the behaviour maybe.
Please add : How do you connect the 624 on your computer ? USB2 or USB3
port on your motherboard ?
Firmware used by the Motu 624 ?
Cheers.
On 2017-12-18 10:39, georgnk wrote:
Hello, that's very interesting.
I just gave a try a motu 624 with ubuntu lowlatency kernel, but also
with a
generic kernel too.
I have the following problem:
Once I test tone with a pure sinewave (easy and reliable way to test a
sound),after a few
seconds periodic clicks are quite audible. Actually these clicks are
present
with any kind of sound,
just more difficult to track if the sound is not a pure sinewave.
Did you test your sound using a pure tone in debian?
Do you have the same issue? I tried different workarounds but the
clicks are
still there. For sure isnot a jack issue,because using alsa directly I
had
the same problem.
Any feedback appreciated from anyone who tried the new Motu products
with
linux.
Thanks a lot!
list wrote
Hello.
You know the AVB serie from MOTU.
We've talked about the 1248 & the UTRALITE AVB previously on the
Linux Audio Users list :
http://lists.linuxaudio.org/pipermail/linux-audio-user/2017-May/108050.html
http://lists.linuxaudio.org/pipermail/linux-audio-user/2017-March/107629.ht…
Now the MOTU 624 AVB.
Working with Gnu/Linux Debian 8.7.
The same as 1248 & ULTRALITE AVB, «real» class compliant, and web app
to control all the settings of the card from your browser.
Update firmware with 0 trouble through the web app interface :
http://achromatopsie.fr/list/00_installfirm.jpg
http://achromatopsie.fr/list/01_verifyingfirm.jpg
http://achromatopsie.fr/list/02_rebootfirm.jpg
http://achromatopsie.fr/list/03_successfirm.jpg
Some screen shot from the Routing menu (sorry need to zoom out, too
much inputs ! AVB disabled so no stream appears on the screen)
http://achromatopsie.fr/list/04_routing.jpg
Screen shot from the Mixing menu :
http://achromatopsie.fr/list/05_mixing.jpg
http://achromatopsie.fr/list/06_mixingzoom.jpg
http://achromatopsie.fr/list/07_mixingzoom1.jpg
And from the Device menu :
http://achromatopsie.fr/list/08_device.jpg
http://achromatopsie.fr/list/09_device2.jpg
Pluged with USB3, Gnu/Linux Debian 8.7 - Custom Kernel :
Linux 4.9.3-amd-64-20170113 #1 SMP PREEMPT Sat Apr 8
17:30:25 CEST 2017 x86_64 GNU/Linux
lsusb
Bus 003 Device 002: ID 07fd:0005 Mark of the Unicorn
lsusb -t
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
|__ Port 1: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 3, Class=Vendor Specific Class, Driver=,
5000M
|__ Port 1: Dev 2, If 4, Class=Vendor Specific Class, Driver=,
5000M
|__ Port 1: Dev 2, If 5, Class=Vendor Specific Class, Driver=,
5000M
aplay -l
**** Liste des Périphériques Matériels PLAYBACK ****
carte 0: D624 [624], périphérique 0: USB Audio [USB Audio]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
Made some quick record (guitar from emulated output of an amp,
microphone vocal) nothing to say, work perfectly. Nice preamp - for me
- clean, no hiss, no background noise, nice dynamic, can hear all my
bad notes and bad fingers on the guitar :)
The line input - jack - work also perfectly, respect the color of my
preamp (Warm Audio)
Did not try the optical I/O as i do not have any devices for it.
Thanks UC2, thanks MOTU.
Anyone have access to the Alsa project card's list and update ?
https://www.alsa-project.org/main/index.php/Matrix:Vendor-Mark_Of_The_Unico…
All the best !
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from:
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
7:26 a.m.
Thank you for the response. I connect my motu using usb 3 ports,but I have
also tried to disable usb 3 functionality from bios.
I mainly connect it via qjackctl. Then I test tone using pure data,440 hz
sinewave. You can also test it using audacity generating a sine wave tone.
If you prefer command tools,maybe you can use libraries like stk toolkit or
Maximilian ,in c++.
I can also select my sound card without qjackctl and Jackd.
Pure data can see my input s and outputs directly. Then I go audio test play
the sine wave , wait a while, I move frequency up and down,clicks start and
never stop.
I use the latest firmware,but I couldn't find a way to downgrade,it says the
old firmware can't be used,its out of date.
Thank you
list-2 wrote
Hello.
Can you give the precise way you did this - i prefer command line tools
if possible.
As i got one, i can try to reproduce the behaviour maybe.
Please add : How do you connect the 624 on your computer ? USB2 or USB3
port on your motherboard ?
Firmware used by the Motu 624 ?
Cheers.
On 2017-12-18 10:39, georgnk wrote:
> Hello, that's very interesting.
>
> I just gave a try a motu 624 with ubuntu lowlatency kernel, but also
> with a
> generic kernel too.
>
> I have the following problem:
> Once I test tone with a pure sinewave (easy and reliable way to test a
> sound),after a few
> seconds periodic clicks are quite audible. Actually these clicks are
> present
> with any kind of sound,
> just more difficult to track if the sound is not a pure sinewave.
> Did you test your sound using a pure tone in debian?
> Do you have the same issue? I tried different workarounds but the
> clicks are
> still there. For sure isnot a jack issue,because using alsa directly I
> had
> the same problem.
> Any feedback appreciated from anyone who tried the new Motu products
> with
> linux.
> Thanks a lot!
>
>
> list wrote
>> Hello.
>>
>> You know the AVB serie from MOTU.
>> We've talked about the 1248 & the UTRALITE AVB previously on the
>> Linux Audio Users list :
>>
>> http://lists.linuxaudio.org/pipermail/linux-audio-user/2017-May/108050.html
>> http://lists.linuxaudio.org/pipermail/linux-audio-user/2017-March/107629.ht…
>>
>> Now the MOTU 624 AVB.
>> Working with Gnu/Linux Debian 8.7.
>> The same as 1248 & ULTRALITE AVB, «real» class compliant, and web app
>> to control all the settings of the card from your browser.
>>
>> Update firmware with 0 trouble through the web app interface :
>>
>> http://achromatopsie.fr/list/00_installfirm.jpg
>>
>> http://achromatopsie.fr/list/01_verifyingfirm.jpg
>>
>> http://achromatopsie.fr/list/02_rebootfirm.jpg
>>
>> http://achromatopsie.fr/list/03_successfirm.jpg
>>
>> Some screen shot from the Routing menu (sorry need to zoom out, too
>> much inputs ! AVB disabled so no stream appears on the screen)
>>
>> http://achromatopsie.fr/list/04_routing.jpg
>>
>> Screen shot from the Mixing menu :
>>
>> http://achromatopsie.fr/list/05_mixing.jpg
>>
>> http://achromatopsie.fr/list/06_mixingzoom.jpg
>>
>> http://achromatopsie.fr/list/07_mixingzoom1.jpg
>>
>> And from the Device menu :
>>
>> http://achromatopsie.fr/list/08_device.jpg
>>
>> http://achromatopsie.fr/list/09_device2.jpg
>>
>> Pluged with USB3, Gnu/Linux Debian 8.7 - Custom Kernel :
>> Linux 4.9.3-amd-64-20170113 #1 SMP PREEMPT Sat Apr 8
>> 17:30:25 CEST 2017 x86_64 GNU/Linux
>>
>> lsusb
>>
>> Bus 003 Device 002: ID 07fd:0005 Mark of the Unicorn
>>
>> lsusb -t
>>
>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
>> |__ Port 1: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 5000M
>> |__ Port 1: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 5000M
>> |__ Port 1: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
>> |__ Port 1: Dev 2, If 3, Class=Vendor Specific Class, Driver=,
>> 5000M
>> |__ Port 1: Dev 2, If 4, Class=Vendor Specific Class, Driver=,
>> 5000M
>> |__ Port 1: Dev 2, If 5, Class=Vendor Specific Class, Driver=,
>> 5000M
>>
>> aplay -l
>> **** Liste des Périphériques Matériels PLAYBACK ****
>> carte 0: D624 [624], périphérique 0: USB Audio [USB Audio]
>> Sous-périphériques: 0/1
>> Sous-périphérique #0: subdevice #0
>>
>> Made some quick record (guitar from emulated output of an amp,
>> microphone vocal) nothing to say, work perfectly. Nice preamp - for me
>> - clean, no hiss, no background noise, nice dynamic, can hear all my
>> bad notes and bad fingers on the guitar :)
>> The line input - jack - work also perfectly, respect the color of my
>> preamp (Warm Audio)
>>
>> Did not try the optical I/O as i do not have any devices for it.
>>
>> Thanks UC2, thanks MOTU.
>>
>> Anyone have access to the Alsa project card's list and update ?
>> https://www.alsa-project.org/main/index.php/Matrix:Vendor-Mark_Of_The_Unico…
>>
>> All the best !
>>
>>
>>
>>
>> _______________________________________________
>> Linux-audio-user mailing list
>
>
Linux-audio-user@.linuxaudio
>
>> http://lists.linuxaudio.org/listinfo/linux-audio-user
>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
5:51 p.m.
On Mon, 18 Dec 2017, georgnk wrote:
I can also select my sound card without qjackctl and
Jackd.
Pure data can see my input s and outputs directly. Then I go audio test play
the sine wave , wait a while, I move frequency up and down,clicks start and
never stop.
If these are random clicks, that sounds like sync issues. Some things to
try:
- set pulse default and alternate sample rate to 48000
- turn off HDA audio either in bios or in pulse:
pactl unload-module module-udev-detect
pactl unload-module module-alsa-card
(note that if pulse can see any audio card directly,
it may choose to sync from that one even if you are
not using it)
- try different sample rates, in particular both 44100 and
48000. It may be that alsa is under the impression
it can set sample rate when that is not the case.
I have not seen in this thread any meantion of the web interface that the
motu AVB series interfaces normally have, so I am guessing this is not one
of these boxes. Motu's support in the past with Linux has be notoriously
bad until the AVB series, so you may have something that will not work
with Linux properly... as in, it is USB2.0 compliant so far as sound
transfer is concerned, but expects a provided blob to do device setup. The
AVB series uses a web based setup tool that is OS agnostic.
--
Len Ovens
www.ovenwerks.net
5:58 p.m.
On Tue, 19 Dec 2017, Len Ovens wrote:
I have not seen in this thread any meantion of the web
interface that the
motu AVB series interfaces normally have, so I am guessing this is not one of
these boxes. Motu's support in the past with Linux has be notoriously bad
until the AVB series, so you may have something that will not work with Linux
properly... as in, it is USB2.0 compliant so far as sound transfer is
concerned, but expects a provided blob to do device setup. The AVB series
uses a web based setup tool that is OS agnostic.
Sorry it says AVB right in the subject. I missed. Do not trust alsa to set
the sample rate, use the web based setup tool for that. Make sure that
alsa and the web setup are the same. make sure the web setup shows a
reasonable sync source.
--
Len Ovens
www.ovenwerks.net
6:32 p.m.
On Tue, Dec 19, 2017 at 11:58 AM, Len Ovens <len(a)ovenwerks.net> wrote:
On Tue, 19 Dec 2017, Len Ovens wrote:
I have not seen in this thread any meantion of the web interface that the
ALSA can set it. But it is *slow* to be set. JACK (1) will typically fail
the first time you start it with a different SR than the current AVB
setting because the device appears to fail to respond. Second time it will
be fine (because the SR change has finally happened).
The bigger problem with the Ultralite AVB (for me) has been that the
capture channels get remapped semi-randomly in blocks of 8 (e.g. input
channel 1-8 can be remapped to be input channel 8-16 etc.) It doesn't
happen except at device open. It is likely an ALSA driver problem and can
probably be solved relatively easily with a USB quirk, but I have not found
the time or inclincation to fix it because I'm not doing any recording with
it.
motu AVB series interfaces normally have, so I am
guessing this is not one
of these boxes. Motu's support in the past with Linux has be notoriously
bad until the AVB series, so you may have something that will not work with
Linux properly... as in, it is USB2.0 compliant so far as sound transfer is
concerned, but expects a provided blob to do device setup. The AVB series
uses a web based setup tool that is OS agnostic.
Sorry it says AVB right in the subject. I missed. Do not trust alsa to set
the sample rate, use the web based setup tool for that. Make sure that alsa
and the web setup are the same. make sure the web setup shows a reasonable
sync source.
20 Dec
20 Dec
2:41 a.m.
Hello thank you for the reply.
The clicks are periodic.well,not strictly periodic but almost every two
seconds. I have tried your suggestions but didn't change something.
What I have also discovered is that the clicks are not passing through my
software. Testing a sine wave and using a spectrum analysis in real time,
sndpeek, clicks don't show up there. It seems they are coming directly to my
monitors (headphones)
Thanks a lot
Len Ovens wrote
On Mon, 18 Dec 2017, georgnk wrote:
I can also select my sound card without qjackctl
and Jackd.
Pure data can see my input s and outputs directly. Then I go audio test
play
the sine wave , wait a while, I move frequency up and down,clicks start
and
never stop.
If these are random clicks, that sounds like sync issues. Some things to
try:
- set pulse default and alternate sample rate to 48000
- turn off HDA audio either in bios or in pulse:
pactl unload-module module-udev-detect
pactl unload-module module-alsa-card
(note that if pulse can see any audio card directly,
it may choose to sync from that one even if you are
not using it)
- try different sample rates, in particular both 44100 and
48000. It may be that alsa is under the impression
it can set sample rate when that is not the case.
I have not seen in this thread any meantion of the web interface that the
motu AVB series interfaces normally have, so I am guessing this is not one
of these boxes. Motu's support in the past with Linux has be notoriously
bad until the AVB series, so you may have something that will not work
with Linux properly... as in, it is USB2.0 compliant so far as sound
transfer is concerned, but expects a provided blob to do device setup. The
AVB series uses a web based setup tool that is OS agnostic.
--
Len Ovens
www.ovenwerks.net
_______________________________________________
Linux-audio-user mailing list Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
3:59 p.m.
Hello.
I am away from my computer with the MOTU 624 AVB for the holidays. I'll
make a try when i'll be back.
But i've just checked the firmware pages of MOTU's web site and :
v1.3.2+520 (Release Date 2017-12-13)
A new one as been added few days ago. I've never tried this one.
Is the the firmware you running your card with ?
The change log says :
Added Bios menu
Hmm i'm really wonder what it does, and if it break anything with
Gnu/Linux Os.
Cheers !
On 2017-12-20 02:41, georgnk wrote:
Hello thank you for the reply.
The clicks are periodic.well,not strictly periodic but almost every two
seconds. I have tried your suggestions but didn't change something.
What I have also discovered is that the clicks are not passing through
my
software. Testing a sine wave and using a spectrum analysis in real
time,
sndpeek, clicks don't show up there. It seems they are coming directly
to my
monitors (headphones)
Thanks a lot
Len Ovens wrote
On Mon, 18 Dec 2017, georgnk wrote:
I can also select my sound card without qjackctl
and Jackd.
Pure data can see my input s and outputs directly. Then I go audio
test
play
the sine wave , wait a while, I move frequency up and down,clicks
start
and
never stop.
If these are random clicks, that sounds like sync issues. Some things
to
try:
- set pulse default and alternate sample rate to 48000
- turn off HDA audio either in bios or in pulse:
pactl unload-module module-udev-detect
pactl unload-module module-alsa-card
(note that if pulse can see any audio card directly,
it may choose to sync from that one even if you are
not using it)
- try different sample rates, in particular both 44100 and
48000. It may be that alsa is under the impression
it can set sample rate when that is not the case.
I have not seen in this thread any meantion of the web interface that
the
motu AVB series interfaces normally have, so I am guessing this is not
one
of these boxes. Motu's support in the past with Linux has be
notoriously
bad until the AVB series, so you may have something that will not work
with Linux properly... as in, it is USB2.0 compliant so far as sound
transfer is concerned, but expects a provided blob to do device setup.
The
AVB series uses a web based setup tool that is OS agnostic.
--
Len Ovens
www.ovenwerks.net
_______________________________________________
Linux-audio-user mailing list Linux-audio-user@.linuxaudio
--
Sent from:
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
21 Dec
21 Dec
2:35 a.m.
Hi.
Yes the firmware is v1.3.2+102 (520 is for the avb)
I don't know either what the bios menu is doing. I can only find bios if I
press the select button from my interface and shows some info,nothing more.
If you test it one day please let me know if you also have this (minor)
issue.
Have nice holidays. Cheers!
list-2 wrote
Hello.
I am away from my computer with the MOTU 624 AVB for the holidays. I'll
make a try when i'll be back.
But i've just checked the firmware pages of MOTU's web site and :
v1.3.2+520 (Release Date 2017-12-13)
A new one as been added few days ago. I've never tried this one.
Is the the firmware you running your card with ?
The change log says :
Added Bios menu
Hmm i'm really wonder what it does, and if it break anything with
Gnu/Linux Os.
Cheers !
On 2017-12-20 02:41, georgnk wrote:
> Hello thank you for the reply.
> The clicks are periodic.well,not strictly periodic but almost every two
> seconds. I have tried your suggestions but didn't change something.
>
> What I have also discovered is that the clicks are not passing through
> my
> software. Testing a sine wave and using a spectrum analysis in real
> time,
> sndpeek, clicks don't show up there. It seems they are coming directly
> to my
> monitors (headphones)
>
> Thanks a lot
>
>
> Len Ovens wrote
>> On Mon, 18 Dec 2017, georgnk wrote:
>>
>>> I can also select my sound card without qjackctl and Jackd.
>>> Pure data can see my input s and outputs directly. Then I go audio
>>> test
>>> play
>>> the sine wave , wait a while, I move frequency up and down,clicks
>>> start
>>> and
>>> never stop.
>>
>> If these are random clicks, that sounds like sync issues. Some things
>> to
>> try:
>> - set pulse default and alternate sample rate to 48000
>> - turn off HDA audio either in bios or in pulse:
>> pactl unload-module module-udev-detect
>> pactl unload-module module-alsa-card
>> (note that if pulse can see any audio card directly,
>> it may choose to sync from that one even if you are
>> not using it)
>> - try different sample rates, in particular both 44100 and
>> 48000. It may be that alsa is under the impression
>> it can set sample rate when that is not the case.
>>
>> I have not seen in this thread any meantion of the web interface that
>> the
>> motu AVB series interfaces normally have, so I am guessing this is not
>> one
>> of these boxes. Motu's support in the past with Linux has be
>> notoriously
>> bad until the AVB series, so you may have something that will not work
>> with Linux properly... as in, it is USB2.0 compliant so far as sound
>> transfer is concerned, but expects a provided blob to do device setup.
>> The
>> AVB series uses a web based setup tool that is OS agnostic.
>>
>> --
>> Len Ovens
>> www.ovenwerks.net
>>
>> _______________________________________________
>> Linux-audio-user mailing list
>
>
Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
5:01 a.m.
Hi guys, I think I found the cause of these tiny clicks.
Messing around with clock mode I discovered that changing the clock mode
affects the rate of these clicks. Choosing ltc or optical mode then back to
internal..They stop for a while and then start again.
If you have any ideas I 'd appreciate a lot.
Cheers
georgnk wrote
Hi.
Yes the firmware is v1.3.2+102 (520 is for the avb)
I don't know either what the bios menu is doing. I can only find bios if I
press the select button from my interface and shows some info,nothing
more.
If you test it one day please let me know if you also have this (minor)
issue.
Have nice holidays. Cheers!
list-2 wrote
Hello.
I am away from my computer with the MOTU 624 AVB for the holidays. I'll
make a try when i'll be back.
But i've just checked the firmware pages of MOTU's web site and :
v1.3.2+520 (Release Date 2017-12-13)
A new one as been added few days ago. I've never tried this one.
Is the the firmware you running your card with ?
The change log says :
Added Bios menu
Hmm i'm really wonder what it does, and if it break anything with
Gnu/Linux Os.
Cheers !
On 2017-12-20 02:41, georgnk wrote:
> Hello thank you for the reply.
> The clicks are periodic.well,not strictly periodic but almost every two
> seconds. I have tried your suggestions but didn't change something.
>
> What I have also discovered is that the clicks are not passing through
> my
> software. Testing a sine wave and using a spectrum analysis in real
> time,
> sndpeek, clicks don't show up there. It seems they are coming directly
> to my
> monitors (headphones)
>
> Thanks a lot
>
>
> Len Ovens wrote
>> On Mon, 18 Dec 2017, georgnk wrote:
>>
>>> I can also select my sound card without qjackctl and Jackd.
>>> Pure data can see my input s and outputs directly. Then I go audio
>>> test
>>> play
>>> the sine wave , wait a while, I move frequency up and down,clicks
>>> start
>>> and
>>> never stop.
>>
>> If these are random clicks, that sounds like sync issues. Some things
>> to
>> try:
>> - set pulse default and alternate sample rate to 48000
>> - turn off HDA audio either in bios or in pulse:
>> pactl unload-module module-udev-detect
>> pactl unload-module module-alsa-card
>> (note that if pulse can see any audio card directly,
>> it may choose to sync from that one even if you are
>> not using it)
>> - try different sample rates, in particular both 44100 and
>> 48000. It may be that alsa is under the impression
>> it can set sample rate when that is not the case.
>>
>> I have not seen in this thread any meantion of the web interface that
>> the
>> motu AVB series interfaces normally have, so I am guessing this is not
>> one
>> of these boxes. Motu's support in the past with Linux has be
>> notoriously
>> bad until the AVB series, so you may have something that will not work
>> with Linux properly... as in, it is USB2.0 compliant so far as sound
>> transfer is concerned, but expects a provided blob to do device setup.
>> The
>> AVB series uses a web based setup tool that is OS agnostic.
>>
>> --
>> Len Ovens
>> www.ovenwerks.net
>>
>> _______________________________________________
>> Linux-audio-user mailing list
>
>
Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
1:54 p.m.
Hello.
According to the manual :
https://s3.amazonaws.com/motu-www-data/manuals/avb/624_User_Guide.pdf
Page 45.
Do you run any optical device ? Or a outside clock device to sync with ?
The only «problems» i have with the MOTU 624 AVB with Gnu/Linux (Debian
8.7 and 9) are :
Got 1 Xrun per Hour, not matter what i do, even if i do nothing with the
computer.
If i change the Buffer size, sometimes called frames/period, the lower i
set it the more i get Xrun without doing nothing with the computer.
I guess it's a USB3 (never tested USB2) problem with either my
motherboard - not a new one - or Alsa....
Latency is not a problem for what i'm doing, as i also have with the
MOTU 624 AVB the routing grid that allow to have direct monitoring.
Other thing :
If i set the Sampling Rate in the MOTU 624 AVB's web interface, to
192000, all the «From Computer» (1 2 3 ...) disappear, thus no sound
from anything played from computer.
Never investigate further this point as i do not know why i would use
192000 sampling rate...
Cheers !
On 2017-12-21 05:01, georgnk wrote:
Hi guys, I think I found the cause of these tiny
clicks.
Messing around with clock mode I discovered that changing the clock
mode
affects the rate of these clicks. Choosing ltc or optical mode then
back to
internal..They stop for a while and then start again.
If you have any ideas I 'd appreciate a lot.
Cheers
georgnk wrote
Hi.
Yes the firmware is v1.3.2+102 (520 is for the avb)
I don't know either what the bios menu is doing. I can only find bios
if I
press the select button from my interface and shows some info,nothing
more.
If you test it one day please let me know if you also have this
(minor)
issue.
Have nice holidays. Cheers!
list-2 wrote
Hello.
I am away from my computer with the MOTU 624 AVB for the holidays.
I'll
make a try when i'll be back.
But i've just checked the firmware pages of MOTU's web site and :
v1.3.2+520 (Release Date 2017-12-13)
A new one as been added few days ago. I've never tried this one.
Is the the firmware you running your card with ?
The change log says :
Added Bios menu
Hmm i'm really wonder what it does, and if it break anything with
Gnu/Linux Os.
Cheers !
On 2017-12-20 02:41, georgnk wrote:
> Hello thank you for the reply.
> The clicks are periodic.well,not strictly periodic but almost every
> two
> seconds. I have tried your suggestions but didn't change something.
>
> What I have also discovered is that the clicks are not passing
> through
> my
> software. Testing a sine wave and using a spectrum analysis in real
> time,
> sndpeek, clicks don't show up there. It seems they are coming
> directly
> to my
> monitors (headphones)
>
> Thanks a lot
>
>
> Len Ovens wrote
>> On Mon, 18 Dec 2017, georgnk wrote:
>>
>>> I can also select my sound card without qjackctl and Jackd.
>>> Pure data can see my input s and outputs directly. Then I go audio
>>> test
>>> play
>>> the sine wave , wait a while, I move frequency up and down,clicks
>>> start
>>> and
>>> never stop.
>>
>> If these are random clicks, that sounds like sync issues. Some
>> things
>> to
>> try:
>> - set pulse default and alternate sample rate to 48000
>> - turn off HDA audio either in bios or in pulse:
>> pactl unload-module module-udev-detect
>> pactl unload-module module-alsa-card
>> (note that if pulse can see any audio card directly,
>> it may choose to sync from that one even if you are
>> not using it)
>> - try different sample rates, in particular both 44100 and
>> 48000. It may be that alsa is under the impression
>> it can set sample rate when that is not the case.
>>
>> I have not seen in this thread any meantion of the web interface
>> that
>> the
>> motu AVB series interfaces normally have, so I am guessing this is
>> not
>> one
>> of these boxes. Motu's support in the past with Linux has be
>> notoriously
>> bad until the AVB series, so you may have something that will not
>> work
>> with Linux properly... as in, it is USB2.0 compliant so far as
>> sound
>> transfer is concerned, but expects a provided blob to do device
>> setup.
>> The
>> AVB series uses a web based setup tool that is OS agnostic.
>>
>> --
>> Len Ovens
>> www.ovenwerks.net
>>
>> _______________________________________________
>> Linux-audio-user mailing list
>
>
Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from:
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list Linux-audio-user@.linuxaudio
--
Sent from:
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
2:55 p.m.
Hi.
No,I don't run any optical device. My clock mode is always internal.
I have tweaked my ubuntu dist adapting some of my configurations from here:
https://wiki.linuxaudio.org/wiki/system_configuration
And switching to lowlatency kernels every time I am doing audio stuff.
But the matter is all these tweaks have nothing to do with these periodic
clicks
list-2 wrote
Hello.
According to the manual :
https://s3.amazonaws.com/motu-www-data/manuals/avb/624_User_Guide.pdf
Page 45.
Do you run any optical device ? Or a outside clock device to sync with ?
The only «problems» i have with the MOTU 624 AVB with Gnu/Linux (Debian
8.7 and 9) are :
Got 1 Xrun per Hour, not matter what i do, even if i do nothing with the
computer.
If i change the Buffer size, sometimes called frames/period, the lower i
set it the more i get Xrun without doing nothing with the computer.
I guess it's a USB3 (never tested USB2) problem with either my
motherboard - not a new one - or Alsa....
Latency is not a problem for what i'm doing, as i also have with the
MOTU 624 AVB the routing grid that allow to have direct monitoring.
Other thing :
If i set the Sampling Rate in the MOTU 624 AVB's web interface, to
192000, all the «From Computer» (1 2 3 ...) disappear, thus no sound
from anything played from computer.
Never investigate further this point as i do not know why i would use
192000 sampling rate...
Cheers !
On 2017-12-21 05:01, georgnk wrote:
> Hi guys, I think I found the cause of these tiny clicks.
> Messing around with clock mode I discovered that changing the clock
> mode
> affects the rate of these clicks. Choosing ltc or optical mode then
> back to
> internal..They stop for a while and then start again.
> If you have any ideas I 'd appreciate a lot.
> Cheers
>
>
> georgnk wrote
>> Hi.
>> Yes the firmware is v1.3.2+102 (520 is for the avb)
>> I don't know either what the bios menu is doing. I can only find bios
>> if I
>> press the select button from my interface and shows some info,nothing
>> more.
>>
>> If you test it one day please let me know if you also have this
>> (minor)
>> issue.
>>
>> Have nice holidays. Cheers!
>>
>>
>>
>>
>> list-2 wrote
>>> Hello.
>>>
>>> I am away from my computer with the MOTU 624 AVB for the holidays.
>>> I'll
>>> make a try when i'll be back.
>>>
>>> But i've just checked the firmware pages of MOTU's web site and :
>>>
>>> v1.3.2+520 (Release Date 2017-12-13)
>>>
>>> A new one as been added few days ago. I've never tried this one.
>>> Is the the firmware you running your card with ?
>>>
>>> The change log says :
>>>
>>> Added Bios menu
>>>
>>> Hmm i'm really wonder what it does, and if it break anything with
>>> Gnu/Linux Os.
>>>
>>> Cheers !
>>>
>>>
>>>
>>> On 2017-12-20 02:41, georgnk wrote:
>>>> Hello thank you for the reply.
>>>> The clicks are periodic.well,not strictly periodic but almost every
>>>> two
>>>> seconds. I have tried your suggestions but didn't change something.
>>>>
>>>> What I have also discovered is that the clicks are not passing
>>>> through
>>>> my
>>>> software. Testing a sine wave and using a spectrum analysis in real
>>>> time,
>>>> sndpeek, clicks don't show up there. It seems they are coming
>>>> directly
>>>> to my
>>>> monitors (headphones)
>>>>
>>>> Thanks a lot
>>>>
>>>>
>>>> Len Ovens wrote
>>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>>>>
>>>>>> I can also select my sound card without qjackctl and Jackd.
>>>>>> Pure data can see my input s and outputs directly. Then I go
audio
>>>>>> test
>>>>>> play
>>>>>> the sine wave , wait a while, I move frequency up and
down,clicks
>>>>>> start
>>>>>> and
>>>>>> never stop.
>>>>>
>>>>> If these are random clicks, that sounds like sync issues. Some
>>>>> things
>>>>> to
>>>>> try:
>>>>> - set pulse default and alternate sample rate to 48000
>>>>> - turn off HDA audio either in bios or in pulse:
>>>>> pactl unload-module module-udev-detect
>>>>> pactl unload-module module-alsa-card
>>>>> (note that if pulse can see any audio card directly,
>>>>> it may choose to sync from that one even if you are
>>>>> not using it)
>>>>> - try different sample rates, in particular both 44100 and
>>>>> 48000. It may be that alsa is under the impression
>>>>> it can set sample rate when that is not the case.
>>>>>
>>>>> I have not seen in this thread any meantion of the web interface
>>>>> that
>>>>> the
>>>>> motu AVB series interfaces normally have, so I am guessing this is
>>>>> not
>>>>> one
>>>>> of these boxes. Motu's support in the past with Linux has be
>>>>> notoriously
>>>>> bad until the AVB series, so you may have something that will not
>>>>> work
>>>>> with Linux properly... as in, it is USB2.0 compliant so far as
>>>>> sound
>>>>> transfer is concerned, but expects a provided blob to do device
>>>>> setup.
>>>>> The
>>>>> AVB series uses a web based setup tool that is OS agnostic.
>>>>>
>>>>> --
>>>>> Len Ovens
>>>>> www.ovenwerks.net
>>>>>
>>>>> _______________________________________________
>>>>> Linux-audio-user mailing list
>>>>
>>>>
Linux-audio-user@.linuxaudio
>>>>
>>>>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sent from:
>>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>>> _______________________________________________
>>>> Linux-audio-user mailing list
>>>>
>>
>>
Linux-audio-user@.linuxaudio
>>
>>>>>>
_______________________________________________
>>> Linux-audio-user mailing list
>>
>>
Linux-audio-user@.linuxaudio
>>
>>>>
>>
>>
>>
>>
>> --
>> Sent from:
>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>> _______________________________________________
>> Linux-audio-user mailing list
>
> Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
1:32 p.m.
Hello.
i still use an old firmware. As i do not really trust - yet - MOTU with
Gnu/Linux.
Keep in mind that if this AVB series products work under Gnu/Linux, i
think it's more a side effect from USB audio Class compliant than a real
desire from MOTU (it has to work for Apple/Ipad).
As this new v1.3.2+102 firmware shows that you have nothing new in the
web interface ( no bios menu added with other options ? ) it may do
something for Windows/Apple Os's users ?!
On 2017-12-21 02:35, georgnk wrote:
Hi.
Yes the firmware is v1.3.2+102 (520 is for the avb)
I don't know either what the bios menu is doing. I can only find bios
if I
press the select button from my interface and shows some info,nothing
more.
If you test it one day please let me know if you also have this (minor)
issue.
Have nice holidays. Cheers!
list-2 wrote
Hello.
I am away from my computer with the MOTU 624 AVB for the holidays.
I'll
make a try when i'll be back.
But i've just checked the firmware pages of MOTU's web site and :
v1.3.2+520 (Release Date 2017-12-13)
A new one as been added few days ago. I've never tried this one.
Is the the firmware you running your card with ?
The change log says :
Added Bios menu
Hmm i'm really wonder what it does, and if it break anything with
Gnu/Linux Os.
Cheers !
On 2017-12-20 02:41, georgnk wrote:
> Hello thank you for the reply.
> The clicks are periodic.well,not strictly periodic but almost every
> two
> seconds. I have tried your suggestions but didn't change something.
>
> What I have also discovered is that the clicks are not passing
> through
> my
> software. Testing a sine wave and using a spectrum analysis in real
> time,
> sndpeek, clicks don't show up there. It seems they are coming
> directly
> to my
> monitors (headphones)
>
> Thanks a lot
>
>
> Len Ovens wrote
>> On Mon, 18 Dec 2017, georgnk wrote:
>>
>>> I can also select my sound card without qjackctl and Jackd.
>>> Pure data can see my input s and outputs directly. Then I go audio
>>> test
>>> play
>>> the sine wave , wait a while, I move frequency up and down,clicks
>>> start
>>> and
>>> never stop.
>>
>> If these are random clicks, that sounds like sync issues. Some
>> things
>> to
>> try:
>> - set pulse default and alternate sample rate to 48000
>> - turn off HDA audio either in bios or in pulse:
>> pactl unload-module module-udev-detect
>> pactl unload-module module-alsa-card
>> (note that if pulse can see any audio card directly,
>> it may choose to sync from that one even if you are
>> not using it)
>> - try different sample rates, in particular both 44100 and
>> 48000. It may be that alsa is under the impression
>> it can set sample rate when that is not the case.
>>
>> I have not seen in this thread any meantion of the web interface
>> that
>> the
>> motu AVB series interfaces normally have, so I am guessing this is
>> not
>> one
>> of these boxes. Motu's support in the past with Linux has be
>> notoriously
>> bad until the AVB series, so you may have something that will not
>> work
>> with Linux properly... as in, it is USB2.0 compliant so far as sound
>> transfer is concerned, but expects a provided blob to do device
>> setup.
>> The
>> AVB series uses a web based setup tool that is OS agnostic.
>>
>> --
>> Len Ovens
>> www.ovenwerks.net
>>
>> _______________________________________________
>> Linux-audio-user mailing list
>
>
Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from:
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
2:36 p.m.
Hello,
When I tried to upload the file with older firmwares I couldn't. The warning
was that I was trying to upload an out of dated firmware. Is there any way
to downgrade?
For sure the web interface using windows Os doesn't show something new such
as bios menu...Except I am blind
Cheers
list-2 wrote
Hello.
i still use an old firmware. As i do not really trust - yet - MOTU with
Gnu/Linux.
Keep in mind that if this AVB series products work under Gnu/Linux, i
think it's more a side effect from USB audio Class compliant than a real
desire from MOTU (it has to work for Apple/Ipad).
As this new v1.3.2+102 firmware shows that you have nothing new in the
web interface ( no bios menu added with other options ? ) it may do
something for Windows/Apple Os's users ?!
On 2017-12-21 02:35, georgnk wrote:
> Hi.
> Yes the firmware is v1.3.2+102 (520 is for the avb)
> I don't know either what the bios menu is doing. I can only find bios
> if I
> press the select button from my interface and shows some info,nothing
> more.
>
> If you test it one day please let me know if you also have this (minor)
> issue.
>
> Have nice holidays. Cheers!
>
>
>
>
> list-2 wrote
>> Hello.
>>
>> I am away from my computer with the MOTU 624 AVB for the holidays.
>> I'll
>> make a try when i'll be back.
>>
>> But i've just checked the firmware pages of MOTU's web site and :
>>
>> v1.3.2+520 (Release Date 2017-12-13)
>>
>> A new one as been added few days ago. I've never tried this one.
>> Is the the firmware you running your card with ?
>>
>> The change log says :
>>
>> Added Bios menu
>>
>> Hmm i'm really wonder what it does, and if it break anything with
>> Gnu/Linux Os.
>>
>> Cheers !
>>
>>
>>
>> On 2017-12-20 02:41, georgnk wrote:
>>> Hello thank you for the reply.
>>> The clicks are periodic.well,not strictly periodic but almost every
>>> two
>>> seconds. I have tried your suggestions but didn't change something.
>>>
>>> What I have also discovered is that the clicks are not passing
>>> through
>>> my
>>> software. Testing a sine wave and using a spectrum analysis in real
>>> time,
>>> sndpeek, clicks don't show up there. It seems they are coming
>>> directly
>>> to my
>>> monitors (headphones)
>>>
>>> Thanks a lot
>>>
>>>
>>> Len Ovens wrote
>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>>>
>>>>> I can also select my sound card without qjackctl and Jackd.
>>>>> Pure data can see my input s and outputs directly. Then I go audio
>>>>> test
>>>>> play
>>>>> the sine wave , wait a while, I move frequency up and down,clicks
>>>>> start
>>>>> and
>>>>> never stop.
>>>>
>>>> If these are random clicks, that sounds like sync issues. Some
>>>> things
>>>> to
>>>> try:
>>>> - set pulse default and alternate sample rate to 48000
>>>> - turn off HDA audio either in bios or in pulse:
>>>> pactl unload-module module-udev-detect
>>>> pactl unload-module module-alsa-card
>>>> (note that if pulse can see any audio card directly,
>>>> it may choose to sync from that one even if you are
>>>> not using it)
>>>> - try different sample rates, in particular both 44100 and
>>>> 48000. It may be that alsa is under the impression
>>>> it can set sample rate when that is not the case.
>>>>
>>>> I have not seen in this thread any meantion of the web interface
>>>> that
>>>> the
>>>> motu AVB series interfaces normally have, so I am guessing this is
>>>> not
>>>> one
>>>> of these boxes. Motu's support in the past with Linux has be
>>>> notoriously
>>>> bad until the AVB series, so you may have something that will not
>>>> work
>>>> with Linux properly... as in, it is USB2.0 compliant so far as sound
>>>> transfer is concerned, but expects a provided blob to do device
>>>> setup.
>>>> The
>>>> AVB series uses a web based setup tool that is OS agnostic.
>>>>
>>>> --
>>>> Len Ovens
>>>> www.ovenwerks.net
>>>>
>>>> _______________________________________________
>>>> Linux-audio-user mailing list
>>>
>>>
Linux-audio-user@.linuxaudio
>>>
>>>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from:
>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>>
>
> Linux-audio-user@.linuxaudio
>
>>>>
_______________________________________________
>> Linux-audio-user mailing list
>
> Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
6:11 p.m.
hi.
Hmm, last resort to try an older firmware, i'm not sure about this, but
i would try to «factory reset» the card, either with the web interface,
or the front LCD panel. Maybe (MAYBE) it fallback on the Initial
shipping version.
Keep in mind that the problem you have may not coming from the card
itself, but, pulseaudio, jack etc.
Aaah computers....
On 2017-12-21 14:36, georgnk wrote:
Hello,
When I tried to upload the file with older firmwares I couldn't. The
warning
was that I was trying to upload an out of dated firmware. Is there any
way
to downgrade?
For sure the web interface using windows Os doesn't show something new
such
as bios menu...Except I am blind
Cheers
list-2 wrote
Hello.
i still use an old firmware. As i do not really trust - yet - MOTU
with
Gnu/Linux.
Keep in mind that if this AVB series products work under Gnu/Linux, i
think it's more a side effect from USB audio Class compliant than a
real
desire from MOTU (it has to work for Apple/Ipad).
As this new v1.3.2+102 firmware shows that you have nothing new in the
web interface ( no bios menu added with other options ? ) it may do
something for Windows/Apple Os's users ?!
On 2017-12-21 02:35, georgnk wrote:
> Hi.
> Yes the firmware is v1.3.2+102 (520 is for the avb)
> I don't know either what the bios menu is doing. I can only find bios
> if I
> press the select button from my interface and shows some info,nothing
> more.
>
> If you test it one day please let me know if you also have this
> (minor)
> issue.
>
> Have nice holidays. Cheers!
>
>
>
>
> list-2 wrote
>> Hello.
>>
>> I am away from my computer with the MOTU 624 AVB for the holidays.
>> I'll
>> make a try when i'll be back.
>>
>> But i've just checked the firmware pages of MOTU's web site and :
>>
>> v1.3.2+520 (Release Date 2017-12-13)
>>
>> A new one as been added few days ago. I've never tried this one.
>> Is the the firmware you running your card with ?
>>
>> The change log says :
>>
>> Added Bios menu
>>
>> Hmm i'm really wonder what it does, and if it break anything with
>> Gnu/Linux Os.
>>
>> Cheers !
>>
>>
>>
>> On 2017-12-20 02:41, georgnk wrote:
>>> Hello thank you for the reply.
>>> The clicks are periodic.well,not strictly periodic but almost every
>>> two
>>> seconds. I have tried your suggestions but didn't change something.
>>>
>>> What I have also discovered is that the clicks are not passing
>>> through
>>> my
>>> software. Testing a sine wave and using a spectrum analysis in real
>>> time,
>>> sndpeek, clicks don't show up there. It seems they are coming
>>> directly
>>> to my
>>> monitors (headphones)
>>>
>>> Thanks a lot
>>>
>>>
>>> Len Ovens wrote
>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>>>
>>>>> I can also select my sound card without qjackctl and Jackd.
>>>>> Pure data can see my input s and outputs directly. Then I go
>>>>> audio
>>>>> test
>>>>> play
>>>>> the sine wave , wait a while, I move frequency up and down,clicks
>>>>> start
>>>>> and
>>>>> never stop.
>>>>
>>>> If these are random clicks, that sounds like sync issues. Some
>>>> things
>>>> to
>>>> try:
>>>> - set pulse default and alternate sample rate to 48000
>>>> - turn off HDA audio either in bios or in pulse:
>>>> pactl unload-module module-udev-detect
>>>> pactl unload-module module-alsa-card
>>>> (note that if pulse can see any audio card directly,
>>>> it may choose to sync from that one even if you are
>>>> not using it)
>>>> - try different sample rates, in particular both 44100 and
>>>> 48000. It may be that alsa is under the impression
>>>> it can set sample rate when that is not the case.
>>>>
>>>> I have not seen in this thread any meantion of the web interface
>>>> that
>>>> the
>>>> motu AVB series interfaces normally have, so I am guessing this is
>>>> not
>>>> one
>>>> of these boxes. Motu's support in the past with Linux has be
>>>> notoriously
>>>> bad until the AVB series, so you may have something that will not
>>>> work
>>>> with Linux properly... as in, it is USB2.0 compliant so far as
>>>> sound
>>>> transfer is concerned, but expects a provided blob to do device
>>>> setup.
>>>> The
>>>> AVB series uses a web based setup tool that is OS agnostic.
>>>>
>>>> --
>>>> Len Ovens
>>>> www.ovenwerks.net
>>>>
>>>> _______________________________________________
>>>> Linux-audio-user mailing list
>>>
>>>
Linux-audio-user@.linuxaudio
>>>
>>>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from:
>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>>
>
> Linux-audio-user@.linuxaudio
>
>>>>
_______________________________________________
>> Linux-audio-user mailing list
>
> Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from:
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
22 Dec
22 Dec
5:33 a.m.
Hi guys,
I tried debian live dvd 9.3
And I did a fast test after selecting my sound card's outputs with:
Speaker-test -t sine -f 880
The same periodic clicks appear after a few seconds. I also played with
sample rates, buffer and period sizes without success.
I didn't use jack,I don't think this is a jack issue. I don't think is a
linux distribution issue.
I am curious if others have the same problem,I don't have another computer
to test. Whenever you have the time to test please let me know the results.
Thanks
list-2 wrote
hi.
Hmm, last resort to try an older firmware, i'm not sure about this, but
i would try to «factory reset» the card, either with the web interface,
or the front LCD panel. Maybe (MAYBE) it fallback on the Initial
shipping version.
Keep in mind that the problem you have may not coming from the card
itself, but, pulseaudio, jack etc.
Aaah computers....
On 2017-12-21 14:36, georgnk wrote:
> Hello,
> When I tried to upload the file with older firmwares I couldn't. The
> warning
> was that I was trying to upload an out of dated firmware. Is there any
> way
> to downgrade?
>
> For sure the web interface using windows Os doesn't show something new
> such
> as bios menu...Except I am blind
>
> Cheers
>
> list-2 wrote
>> Hello.
>>
>> i still use an old firmware. As i do not really trust - yet - MOTU
>> with
>> Gnu/Linux.
>>
>> Keep in mind that if this AVB series products work under Gnu/Linux, i
>> think it's more a side effect from USB audio Class compliant than a
>> real
>> desire from MOTU (it has to work for Apple/Ipad).
>>
>> As this new v1.3.2+102 firmware shows that you have nothing new in the
>> web interface ( no bios menu added with other options ? ) it may do
>> something for Windows/Apple Os's users ?!
>>
>>
>>
>> On 2017-12-21 02:35, georgnk wrote:
>>> Hi.
>>> Yes the firmware is v1.3.2+102 (520 is for the avb)
>>> I don't know either what the bios menu is doing. I can only find bios
>>> if I
>>> press the select button from my interface and shows some info,nothing
>>> more.
>>>
>>> If you test it one day please let me know if you also have this
>>> (minor)
>>> issue.
>>>
>>> Have nice holidays. Cheers!
>>>
>>>
>>>
>>>
>>> list-2 wrote
>>>> Hello.
>>>>
>>>> I am away from my computer with the MOTU 624 AVB for the holidays.
>>>> I'll
>>>> make a try when i'll be back.
>>>>
>>>> But i've just checked the firmware pages of MOTU's web site and
:
>>>>
>>>> v1.3.2+520 (Release Date 2017-12-13)
>>>>
>>>> A new one as been added few days ago. I've never tried this one.
>>>> Is the the firmware you running your card with ?
>>>>
>>>> The change log says :
>>>>
>>>> Added Bios menu
>>>>
>>>> Hmm i'm really wonder what it does, and if it break anything with
>>>> Gnu/Linux Os.
>>>>
>>>> Cheers !
>>>>
>>>>
>>>>
>>>> On 2017-12-20 02:41, georgnk wrote:
>>>>> Hello thank you for the reply.
>>>>> The clicks are periodic.well,not strictly periodic but almost every
>>>>> two
>>>>> seconds. I have tried your suggestions but didn't change
something.
>>>>>
>>>>> What I have also discovered is that the clicks are not passing
>>>>> through
>>>>> my
>>>>> software. Testing a sine wave and using a spectrum analysis in real
>>>>> time,
>>>>> sndpeek, clicks don't show up there. It seems they are coming
>>>>> directly
>>>>> to my
>>>>> monitors (headphones)
>>>>>
>>>>> Thanks a lot
>>>>>
>>>>>
>>>>> Len Ovens wrote
>>>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>>>>>
>>>>>>> I can also select my sound card without qjackctl and Jackd.
>>>>>>> Pure data can see my input s and outputs directly. Then I go
>>>>>>> audio
>>>>>>> test
>>>>>>> play
>>>>>>> the sine wave , wait a while, I move frequency up and
down,clicks
>>>>>>> start
>>>>>>> and
>>>>>>> never stop.
>>>>>>
>>>>>> If these are random clicks, that sounds like sync issues. Some
>>>>>> things
>>>>>> to
>>>>>> try:
>>>>>> - set pulse default and alternate sample rate to 48000
>>>>>> - turn off HDA audio either in bios or in pulse:
>>>>>> pactl unload-module module-udev-detect
>>>>>> pactl unload-module module-alsa-card
>>>>>> (note that if pulse can see any audio card directly,
>>>>>> it may choose to sync from that one even if you are
>>>>>> not using it)
>>>>>> - try different sample rates, in particular both 44100 and
>>>>>> 48000. It may be that alsa is under the impression
>>>>>> it can set sample rate when that is not the case.
>>>>>>
>>>>>> I have not seen in this thread any meantion of the web interface
>>>>>> that
>>>>>> the
>>>>>> motu AVB series interfaces normally have, so I am guessing this
is
>>>>>> not
>>>>>> one
>>>>>> of these boxes. Motu's support in the past with Linux has be
>>>>>> notoriously
>>>>>> bad until the AVB series, so you may have something that will
not
>>>>>> work
>>>>>> with Linux properly... as in, it is USB2.0 compliant so far as
>>>>>> sound
>>>>>> transfer is concerned, but expects a provided blob to do device
>>>>>> setup.
>>>>>> The
>>>>>> AVB series uses a web based setup tool that is OS agnostic.
>>>>>>
>>>>>> --
>>>>>> Len Ovens
>>>>>> www.ovenwerks.net
>>>>>>
>>>>>> _______________________________________________
>>>>>> Linux-audio-user mailing list
>>>>>
>>>>>
Linux-audio-user@.linuxaudio
>>>>>
>>>>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sent from:
>>>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>>>> _______________________________________________
>>>>> Linux-audio-user mailing list
>>>>>
>>>
>>>
Linux-audio-user@.linuxaudio
>>>
>>>>>>>>
_______________________________________________
>>>> Linux-audio-user mailing list
>>>
>>>
Linux-audio-user@.linuxaudio
>>>
>>>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from:
>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>>
>
> Linux-audio-user@.linuxaudio
>
>>>>
_______________________________________________
>> Linux-audio-user mailing list
>
> Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
24 Dec
24 Dec
12:57 a.m.
Hello.
Hope you can play this, let me know.
http://achromatopsie.fr/LAU/Lau-Test.mkv
So i got it too.
I've tried on an older computer, with some Intel HDA on motherboard
sound chipset, the same.
So the card is not guilty.
As i said previously, i got some Xrun - 1 per hour, depending on how i
set the Buffer size, sometimes called frames/period - even when the
computer is idling doing nothing.
I've tried several Kernel, build my own, try to change settings for the
USB kernel options and other things, always the same. So i gave up.
Not clicks on my voice over recording so...i can live with that.
I suspect some USB kernel's driver problem, or Alsa trouble with USB. Or
motherboard USB. But all of this is beyond my knowledge or skills.
For the record here :
Linux 4.13.4-2017-10-18-amd-64 #1 SMP PREEMPT
MOTU 624 with 1.3.1+81 connected with USB 3 port.
lau@reader:~$ lsusb
Bus 002 Device 002: ID 07fd:0005 Mark of the Unicorn
lau@reader:~$ lsusb -t
Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
|__ Port 1: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
Aaah computers !
Merry Christmas !
Le 2017-12-22 05:33, georgnk a écrit :
Hi guys,
I tried debian live dvd 9.3
And I did a fast test after selecting my sound card's outputs with:
Speaker-test -t sine -f 880
The same periodic clicks appear after a few seconds. I also played with
sample rates, buffer and period sizes without success.
I didn't use jack,I don't think this is a jack issue. I don't think is
a
linux distribution issue.
I am curious if others have the same problem,I don't have another
computer
to test. Whenever you have the time to test please let me know the
results.
Thanks
list-2 wrote
hi.
Hmm, last resort to try an older firmware, i'm not sure about this,
but
i would try to «factory reset» the card, either with the web
interface,
or the front LCD panel. Maybe (MAYBE) it fallback on the Initial
shipping version.
Keep in mind that the problem you have may not coming from the card
itself, but, pulseaudio, jack etc.
Aaah computers....
On 2017-12-21 14:36, georgnk wrote:
> Hello,
> When I tried to upload the file with older firmwares I couldn't. The
> warning
> was that I was trying to upload an out of dated firmware. Is there
> any
> way
> to downgrade?
>
> For sure the web interface using windows Os doesn't show something
> new
> such
> as bios menu...Except I am blind
>
> Cheers
>
> list-2 wrote
>> Hello.
>>
>> i still use an old firmware. As i do not really trust - yet - MOTU
>> with
>> Gnu/Linux.
>>
>> Keep in mind that if this AVB series products work under Gnu/Linux,
>> i
>> think it's more a side effect from USB audio Class compliant than a
>> real
>> desire from MOTU (it has to work for Apple/Ipad).
>>
>> As this new v1.3.2+102 firmware shows that you have nothing new in
>> the
>> web interface ( no bios menu added with other options ? ) it may do
>> something for Windows/Apple Os's users ?!
>>
>>
>>
>> On 2017-12-21 02:35, georgnk wrote:
>>> Hi.
>>> Yes the firmware is v1.3.2+102 (520 is for the avb)
>>> I don't know either what the bios menu is doing. I can only find
>>> bios
>>> if I
>>> press the select button from my interface and shows some
>>> info,nothing
>>> more.
>>>
>>> If you test it one day please let me know if you also have this
>>> (minor)
>>> issue.
>>>
>>> Have nice holidays. Cheers!
>>>
>>>
>>>
>>>
>>> list-2 wrote
>>>> Hello.
>>>>
>>>> I am away from my computer with the MOTU 624 AVB for the holidays.
>>>> I'll
>>>> make a try when i'll be back.
>>>>
>>>> But i've just checked the firmware pages of MOTU's web site and
:
>>>>
>>>> v1.3.2+520 (Release Date 2017-12-13)
>>>>
>>>> A new one as been added few days ago. I've never tried this one.
>>>> Is the the firmware you running your card with ?
>>>>
>>>> The change log says :
>>>>
>>>> Added Bios menu
>>>>
>>>> Hmm i'm really wonder what it does, and if it break anything with
>>>> Gnu/Linux Os.
>>>>
>>>> Cheers !
>>>>
>>>>
>>>>
>>>> On 2017-12-20 02:41, georgnk wrote:
>>>>> Hello thank you for the reply.
>>>>> The clicks are periodic.well,not strictly periodic but almost
>>>>> every
>>>>> two
>>>>> seconds. I have tried your suggestions but didn't change
>>>>> something.
>>>>>
>>>>> What I have also discovered is that the clicks are not passing
>>>>> through
>>>>> my
>>>>> software. Testing a sine wave and using a spectrum analysis in
>>>>> real
>>>>> time,
>>>>> sndpeek, clicks don't show up there. It seems they are coming
>>>>> directly
>>>>> to my
>>>>> monitors (headphones)
>>>>>
>>>>> Thanks a lot
>>>>>
>>>>>
>>>>> Len Ovens wrote
>>>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>>>>>
>>>>>>> I can also select my sound card without qjackctl and Jackd.
>>>>>>> Pure data can see my input s and outputs directly. Then I go
>>>>>>> audio
>>>>>>> test
>>>>>>> play
>>>>>>> the sine wave , wait a while, I move frequency up and
>>>>>>> down,clicks
>>>>>>> start
>>>>>>> and
>>>>>>> never stop.
>>>>>>
>>>>>> If these are random clicks, that sounds like sync issues. Some
>>>>>> things
>>>>>> to
>>>>>> try:
>>>>>> - set pulse default and alternate sample rate to 48000
>>>>>> - turn off HDA audio either in bios or in pulse:
>>>>>> pactl unload-module module-udev-detect
>>>>>> pactl unload-module module-alsa-card
>>>>>> (note that if pulse can see any audio card directly,
>>>>>> it may choose to sync from that one even if you are
>>>>>> not using it)
>>>>>> - try different sample rates, in particular both 44100 and
>>>>>> 48000. It may be that alsa is under the impression
>>>>>> it can set sample rate when that is not the case.
>>>>>>
>>>>>> I have not seen in this thread any meantion of the web interface
>>>>>> that
>>>>>> the
>>>>>> motu AVB series interfaces normally have, so I am guessing this
>>>>>> is
>>>>>> not
>>>>>> one
>>>>>> of these boxes. Motu's support in the past with Linux has be
>>>>>> notoriously
>>>>>> bad until the AVB series, so you may have something that will
>>>>>> not
>>>>>> work
>>>>>> with Linux properly... as in, it is USB2.0 compliant so far as
>>>>>> sound
>>>>>> transfer is concerned, but expects a provided blob to do device
>>>>>> setup.
>>>>>> The
>>>>>> AVB series uses a web based setup tool that is OS agnostic.
>>>>>>
>>>>>> --
>>>>>> Len Ovens
>>>>>> www.ovenwerks.net
>>>>>>
>>>>>> _______________________________________________
>>>>>> Linux-audio-user mailing list
>>>>>
>>>>>
Linux-audio-user@.linuxaudio
>>>>>
>>>>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sent from:
>>>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>>>> _______________________________________________
>>>>> Linux-audio-user mailing list
>>>>>
>>>
>>> Linux-audio-user@.linuxaudio
>>>
>>>>>>>>
_______________________________________________
>>>> Linux-audio-user mailing list
>>>
>>> Linux-audio-user@.linuxaudio
>>>
>>>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from:
>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>>
>
> Linux-audio-user@.linuxaudio
>
>>>>
_______________________________________________
>> Linux-audio-user mailing list
>
> Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from:
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
1:24 a.m.
Hi. Thank you for the feedback.
Yes,right,it doesn't affect recording or exporting etc.
I have tested with a blue yeti,soso, interface it doesn't give any of these
periodic clicks,neither my internal had intel.
I think/hope it's a matter of time small issues like this to be resolved.
I don't have time to search more about that though...
The fact is that motu avb series not only work with linux but we can also
use the web app to make configurations. Well not everything is perfect,but
let's be optimistic
Merry Christmas!
list-2 wrote
Hello.
Hope you can play this, let me know.
http://achromatopsie.fr/LAU/Lau-Test.mkv
So i got it too.
I've tried on an older computer, with some Intel HDA on motherboard
sound chipset, the same.
So the card is not guilty.
As i said previously, i got some Xrun - 1 per hour, depending on how i
set the Buffer size, sometimes called frames/period - even when the
computer is idling doing nothing.
I've tried several Kernel, build my own, try to change settings for the
USB kernel options and other things, always the same. So i gave up.
Not clicks on my voice over recording so...i can live with that.
I suspect some USB kernel's driver problem, or Alsa trouble with USB. Or
motherboard USB. But all of this is beyond my knowledge or skills.
For the record here :
Linux 4.13.4-2017-10-18-amd-64 #1 SMP PREEMPT
MOTU 624 with 1.3.1+81 connected with USB 3 port.
lau@reader:~$ lsusb
Bus 002 Device 002: ID 07fd:0005 Mark of the Unicorn
lau@reader:~$ lsusb -t
Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
|__ Port 1: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 5000M
|__ Port 1: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
Aaah computers !
Merry Christmas !
Le 2017-12-22 05:33, georgnk a écrit :
> Hi guys,
> I tried debian live dvd 9.3
> And I did a fast test after selecting my sound card's outputs with:
> Speaker-test -t sine -f 880
>
> The same periodic clicks appear after a few seconds. I also played with
> sample rates, buffer and period sizes without success.
>
> I didn't use jack,I don't think this is a jack issue. I don't think is
> a
> linux distribution issue.
>
> I am curious if others have the same problem,I don't have another
> computer
> to test. Whenever you have the time to test please let me know the
> results.
> Thanks
>
>
> list-2 wrote
>> hi.
>>
>> Hmm, last resort to try an older firmware, i'm not sure about this,
>> but
>> i would try to «factory reset» the card, either with the web
>> interface,
>> or the front LCD panel. Maybe (MAYBE) it fallback on the Initial
>> shipping version.
>>
>> Keep in mind that the problem you have may not coming from the card
>> itself, but, pulseaudio, jack etc.
>>
>> Aaah computers....
>>
>>
>>
>> On 2017-12-21 14:36, georgnk wrote:
>>> Hello,
>>> When I tried to upload the file with older firmwares I couldn't. The
>>> warning
>>> was that I was trying to upload an out of dated firmware. Is there
>>> any
>>> way
>>> to downgrade?
>>>
>>> For sure the web interface using windows Os doesn't show something
>>> new
>>> such
>>> as bios menu...Except I am blind
>>>
>>> Cheers
>>>
>>> list-2 wrote
>>>> Hello.
>>>>
>>>> i still use an old firmware. As i do not really trust - yet - MOTU
>>>> with
>>>> Gnu/Linux.
>>>>
>>>> Keep in mind that if this AVB series products work under Gnu/Linux,
>>>> i
>>>> think it's more a side effect from USB audio Class compliant than a
>>>> real
>>>> desire from MOTU (it has to work for Apple/Ipad).
>>>>
>>>> As this new v1.3.2+102 firmware shows that you have nothing new in
>>>> the
>>>> web interface ( no bios menu added with other options ? ) it may do
>>>> something for Windows/Apple Os's users ?!
>>>>
>>>>
>>>>
>>>> On 2017-12-21 02:35, georgnk wrote:
>>>>> Hi.
>>>>> Yes the firmware is v1.3.2+102 (520 is for the avb)
>>>>> I don't know either what the bios menu is doing. I can only find
>>>>> bios
>>>>> if I
>>>>> press the select button from my interface and shows some
>>>>> info,nothing
>>>>> more.
>>>>>
>>>>> If you test it one day please let me know if you also have this
>>>>> (minor)
>>>>> issue.
>>>>>
>>>>> Have nice holidays. Cheers!
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> list-2 wrote
>>>>>> Hello.
>>>>>>
>>>>>> I am away from my computer with the MOTU 624 AVB for the
holidays.
>>>>>> I'll
>>>>>> make a try when i'll be back.
>>>>>>
>>>>>> But i've just checked the firmware pages of MOTU's web
site and :
>>>>>>
>>>>>> v1.3.2+520 (Release Date 2017-12-13)
>>>>>>
>>>>>> A new one as been added few days ago. I've never tried this
one.
>>>>>> Is the the firmware you running your card with ?
>>>>>>
>>>>>> The change log says :
>>>>>>
>>>>>> Added Bios menu
>>>>>>
>>>>>> Hmm i'm really wonder what it does, and if it break anything
with
>>>>>> Gnu/Linux Os.
>>>>>>
>>>>>> Cheers !
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 2017-12-20 02:41, georgnk wrote:
>>>>>>> Hello thank you for the reply.
>>>>>>> The clicks are periodic.well,not strictly periodic but almost
>>>>>>> every
>>>>>>> two
>>>>>>> seconds. I have tried your suggestions but didn't change
>>>>>>> something.
>>>>>>>
>>>>>>> What I have also discovered is that the clicks are not
passing
>>>>>>> through
>>>>>>> my
>>>>>>> software. Testing a sine wave and using a spectrum analysis
in
>>>>>>> real
>>>>>>> time,
>>>>>>> sndpeek, clicks don't show up there. It seems they are
coming
>>>>>>> directly
>>>>>>> to my
>>>>>>> monitors (headphones)
>>>>>>>
>>>>>>> Thanks a lot
>>>>>>>
>>>>>>>
>>>>>>> Len Ovens wrote
>>>>>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>>>>>>>
>>>>>>>>> I can also select my sound card without qjackctl and
Jackd.
>>>>>>>>> Pure data can see my input s and outputs directly.
Then I go
>>>>>>>>> audio
>>>>>>>>> test
>>>>>>>>> play
>>>>>>>>> the sine wave , wait a while, I move frequency up and
>>>>>>>>> down,clicks
>>>>>>>>> start
>>>>>>>>> and
>>>>>>>>> never stop.
>>>>>>>>
>>>>>>>> If these are random clicks, that sounds like sync issues.
Some
>>>>>>>> things
>>>>>>>> to
>>>>>>>> try:
>>>>>>>> - set pulse default and alternate sample rate to 48000
>>>>>>>> - turn off HDA audio either in bios or in pulse:
>>>>>>>> pactl unload-module module-udev-detect
>>>>>>>> pactl unload-module module-alsa-card
>>>>>>>> (note that if pulse can see any audio card directly,
>>>>>>>> it may choose to sync from that one even if you are
>>>>>>>> not using it)
>>>>>>>> - try different sample rates, in particular both 44100
and
>>>>>>>> 48000. It may be that alsa is under the impression
>>>>>>>> it can set sample rate when that is not the case.
>>>>>>>>
>>>>>>>> I have not seen in this thread any meantion of the web
interface
>>>>>>>> that
>>>>>>>> the
>>>>>>>> motu AVB series interfaces normally have, so I am
guessing this
>>>>>>>> is
>>>>>>>> not
>>>>>>>> one
>>>>>>>> of these boxes. Motu's support in the past with Linux
has be
>>>>>>>> notoriously
>>>>>>>> bad until the AVB series, so you may have something that
will
>>>>>>>> not
>>>>>>>> work
>>>>>>>> with Linux properly... as in, it is USB2.0 compliant so
far as
>>>>>>>> sound
>>>>>>>> transfer is concerned, but expects a provided blob to do
device
>>>>>>>> setup.
>>>>>>>> The
>>>>>>>> AVB series uses a web based setup tool that is OS
agnostic.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Len Ovens
>>>>>>>> www.ovenwerks.net
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Linux-audio-user mailing list
>>>>>>>
>>>>>>>
Linux-audio-user@.linuxaudio
>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sent from:
>>>>>>>
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>>>>>> _______________________________________________
>>>>>>> Linux-audio-user mailing list
>>>>>>>
>>>>>
>>>>>
Linux-audio-user@.linuxaudio
>>>>>
>>>>>>>>>>>>
_______________________________________________
>>>>>> Linux-audio-user mailing list
>>>>>
>>>>>
Linux-audio-user@.linuxaudio
>>>>>
>>>>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sent from:
>>>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>>>> _______________________________________________
>>>>> Linux-audio-user mailing list
>>>>>
>>>
>>>
Linux-audio-user@.linuxaudio
>>>
>>>>>>>>
_______________________________________________
>>>> Linux-audio-user mailing list
>>>
>>>
Linux-audio-user@.linuxaudio
>>>
>>>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from:
>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>>
>
> Linux-audio-user@.linuxaudio
>
>>>>
_______________________________________________
>> Linux-audio-user mailing list
>
> Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
25 Dec
25 Dec
1:12 p.m.
Hi!
I have the Ultralite AVB and have downgraded my card as per recommendations
from Motu tech support. The reason for me was to be able to use more than
24ch stream in CC more from my computer. That option is removed on later
firmware. The latest public beta firmware which probably is available for
624 has a very nice touch console. (Mixer made for touch based surfaces
that will be a nice addition)
My understanding is that you should be able to downgrade as you please but
I can not guarantee anything. Tech support is great and will probably
respond quickly even if "Operating system = Other"
/Anders
On Dec 21, 2017 2:36 PM, "georgnk" <georg_nik(a)yahoo.gr> wrote:
Hello,
When I tried to upload the file with older firmwares I couldn't. The
warning
was that I was trying to upload an out of dated firmware. Is there any way
to downgrade?
For sure the web interface using windows Os doesn't show something new such
as bios menu...Except I am blind
Cheers
list-2 wrote
Hello.
i still use an old firmware. As i do not really trust - yet - MOTU with
Gnu/Linux.
Keep in mind that if this AVB series products work under Gnu/Linux, i
think it's more a side effect from USB audio Class compliant than a real
desire from MOTU (it has to work for Apple/Ipad).
As this new v1.3.2+102 firmware shows that you have nothing new in the
web interface ( no bios menu added with other options ? ) it may do
something for Windows/Apple Os's users ?!
On 2017-12-21 02:35, georgnk wrote:
> Hi.
> Yes the firmware is v1.3.2+102 (520 is for the avb)
> I don't know either what the bios menu is doing. I can only find bios
> if I
> press the select button from my interface and shows some info,nothing
> more.
>
> If you test it one day please let me know if you also have this (minor)
> issue.
>
> Have nice holidays. Cheers!
>
>
>
>
> list-2 wrote
>> Hello.
>>
>> I am away from my computer with the MOTU 624 AVB for the holidays.
>> I'll
>> make a try when i'll be back.
>>
>> But i've just checked the firmware pages of MOTU's web site and :
>>
>> v1.3.2+520 (Release Date 2017-12-13)
>>
>> A new one as been added few days ago. I've never tried this one.
>> Is the the firmware you running your card with ?
>>
>> The change log says :
>>
>> Added Bios menu
>>
>> Hmm i'm really wonder what it does, and if it break anything with
>> Gnu/Linux Os.
>>
>> Cheers !
>>
>>
>>
>> On 2017-12-20 02:41, georgnk wrote:
>>> Hello thank you for the reply.
>>> The clicks are periodic.well,not strictly periodic but almost every
>>> two
>>> seconds. I have tried your suggestions but didn't change something.
>>>
>>> What I have also discovered is that the clicks are not passing
>>> through
>>> my
>>> software. Testing a sine wave and using a spectrum analysis in real
>>> time,
>>> sndpeek, clicks don't show up there. It seems they are coming
>>> directly
>>> to my
>>> monitors (headphones)
>>>
>>> Thanks a lot
>>>
>>>
>>> Len Ovens wrote
>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>>>
>>>>> I can also select my sound card without qjackctl and Jackd.
>>>>> Pure data can see my input s and outputs directly. Then I go audio
>>>>> test
>>>>> play
>>>>> the sine wave , wait a while, I move frequency up and down,clicks
>>>>> start
>>>>> and
>>>>> never stop.
>>>>
>>>> If these are random clicks, that sounds like sync issues. Some
>>>> things
>>>> to
>>>> try:
>>>> - set pulse default and alternate sample rate to 48000
>>>> - turn off HDA audio either in bios or in pulse:
>>>> pactl unload-module module-udev-detect
>>>> pactl unload-module module-alsa-card
>>>> (note that if pulse can see any audio card directly,
>>>> it may choose to sync from that one even if you are
>>>> not using it)
>>>> - try different sample rates, in particular both 44100 and
>>>> 48000. It may be that alsa is under the impression
>>>> it can set sample rate when that is not the case.
>>>>
>>>> I have not seen in this thread any meantion of the web interface
>>>> that
>>>> the
>>>> motu AVB series interfaces normally have, so I am guessing this is
>>>> not
>>>> one
>>>> of these boxes. Motu's support in the past with Linux has be
>>>> notoriously
>>>> bad until the AVB series, so you may have something that will not
>>>> work
>>>> with Linux properly... as in, it is USB2.0 compliant so far as sound
>>>> transfer is concerned, but expects a provided blob to do device
>>>> setup.
>>>> The
>>>> AVB series uses a web based setup tool that is OS agnostic.
>>>>
>>>> --
>>>> Len Ovens
>>>> www.ovenwerks.net
>>>>
>>>> _______________________________________________
>>>> Linux-audio-user mailing list
>>>
>>>> Linux-audio-user@.linuxaudio
>>>
>>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from:
>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>>
>
>> Linux-audio-user@.linuxaudio
>
>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>> _______________________________________________
>> Linux-audio-user mailing list
>
>> Linux-audio-user@.linuxaudio
>
>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
>
Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
1:32 p.m.
Hey Anders,
Thanks for that information!
I wondered why I'm not able anymore to stream 64 channels.
I have the Motu 1248, which firmware are you on?
Do you know which it is for the 1248?
Cheers
Moshe
On Dec 25, 2017 14:12, "Anders Hellquist" <lau(a)hellquist.net> wrote:
Hi!
I have the Ultralite AVB and have downgraded my card as per recommendations
from Motu tech support. The reason for me was to be able to use more than
24ch stream in CC more from my computer. That option is removed on later
firmware. The latest public beta firmware which probably is available for
624 has a very nice touch console. (Mixer made for touch based surfaces
that will be a nice addition)
My understanding is that you should be able to downgrade as you please but
I can not guarantee anything. Tech support is great and will probably
respond quickly even if "Operating system = Other"
/Anders
On Dec 21, 2017 2:36 PM, "georgnk" <georg_nik(a)yahoo.gr> wrote:
Hello,
When I tried to upload the file with older firmwares I couldn't. The
warning
was that I was trying to upload an out of dated firmware. Is there any way
to downgrade?
For sure the web interface using windows Os doesn't show something new such
as bios menu...Except I am blind
Cheers
list-2 wrote
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
Hello.
i still use an old firmware. As i do not really trust - yet - MOTU with
Gnu/Linux.
Keep in mind that if this AVB series products work under Gnu/Linux, i
think it's more a side effect from USB audio Class compliant than a real
desire from MOTU (it has to work for Apple/Ipad).
As this new v1.3.2+102 firmware shows that you have nothing new in the
web interface ( no bios menu added with other options ? ) it may do
something for Windows/Apple Os's users ?!
On 2017-12-21 02:35, georgnk wrote:
> Hi.
> Yes the firmware is v1.3.2+102 (520 is for the avb)
> I don't know either what the bios menu is doing. I can only find bios
> if I
> press the select button from my interface and shows some info,nothing
> more.
>
> If you test it one day please let me know if you also have this (minor)
> issue.
>
> Have nice holidays. Cheers!
>
>
>
>
> list-2 wrote
>> Hello.
>>
>> I am away from my computer with the MOTU 624 AVB for the holidays.
>> I'll
>> make a try when i'll be back.
>>
>> But i've just checked the firmware pages of MOTU's web site and :
>>
>> v1.3.2+520 (Release Date 2017-12-13)
>>
>> A new one as been added few days ago. I've never tried this one.
>> Is the the firmware you running your card with ?
>>
>> The change log says :
>>
>> Added Bios menu
>>
>> Hmm i'm really wonder what it does, and if it break anything with
>> Gnu/Linux Os.
>>
>> Cheers !
>>
>>
>>
>> On 2017-12-20 02:41, georgnk wrote:
>>> Hello thank you for the reply.
>>> The clicks are periodic.well,not strictly periodic but almost every
>>> two
>>> seconds. I have tried your suggestions but didn't change something.
>>>
>>> What I have also discovered is that the clicks are not passing
>>> through
>>> my
>>> software. Testing a sine wave and using a spectrum analysis in real
>>> time,
>>> sndpeek, clicks don't show up there. It seems they are coming
>>> directly
>>> to my
>>> monitors (headphones)
>>>
>>> Thanks a lot
>>>
>>>
>>> Len Ovens wrote
>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>>>
>>>>> I can also select my sound card without qjackctl and Jackd.
>>>>> Pure data can see my input s and outputs directly. Then I go audio
>>>>> test
>>>>> play
>>>>> the sine wave , wait a while, I move frequency up and down,clicks
>>>>> start
>>>>> and
>>>>> never stop.
>>>>
>>>> If these are random clicks, that sounds like sync issues. Some
>>>> things
>>>> to
>>>> try:
>>>> - set pulse default and alternate sample rate to 48000
>>>> - turn off HDA audio either in bios or in pulse:
>>>> pactl unload-module module-udev-detect
>>>> pactl unload-module module-alsa-card
>>>> (note that if pulse can see any audio card directly,
>>>> it may choose to sync from that one even if you are
>>>> not using it)
>>>> - try different sample rates, in particular both 44100 and
>>>> 48000. It may be that alsa is under the impression
>>>> it can set sample rate when that is not the case.
>>>>
>>>> I have not seen in this thread any meantion of the web interface
>>>> that
>>>> the
>>>> motu AVB series interfaces normally have, so I am guessing this is
>>>> not
>>>> one
>>>> of these boxes. Motu's support in the past with Linux has be
>>>> notoriously
>>>> bad until the AVB series, so you may have something that will not
>>>> work
>>>> with Linux properly... as in, it is USB2.0 compliant so far as sound
>>>> transfer is concerned, but expects a provided blob to do device
>>>> setup.
>>>> The
>>>> AVB series uses a web based setup tool that is OS agnostic.
>>>>
>>>> --
>>>> Len Ovens
>>>> www.ovenwerks.net
>>>>
>>>> _______________________________________________
>>>> Linux-audio-user mailing list
>>>
>>>> Linux-audio-user@.linuxaudio
>>>
>>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from:
>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>>
>
>> Linux-audio-user@.linuxaudio
>
>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>> _______________________________________________
>> Linux-audio-user mailing list
>
>> Linux-audio-user@.linuxaudio
>
>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
>
Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
2:02 p.m.
Hi !
I am currently running the public beta for my card which is 1.3.4+539 and
that is limiting the USB streams.
The last one with configurable USB streaming for my card was. 1.2.8+378
I hope the first one for your card 1.2.9+28 still has the option and maybe
1.3.0+59 do as well.
The changlog suggests to me that 1.3.1 is the first crippled one for your
card but since I don't have a 624, I can't check.
Best regards, Anders
On Dec 25, 2017 1:32 PM, "Moshe Werner" <moshwe(a)gmail.com> wrote:
Hey Anders,
Thanks for that information!
I wondered why I'm not able anymore to stream 64 channels.
I have the Motu 1248, which firmware are you on?
Do you know which it is for the 1248?
Cheers
Moshe
On Dec 25, 2017 14:12, "Anders Hellquist" <lau(a)hellquist.net> wrote:
Hi!
I have the Ultralite AVB and have downgraded my card as per
recommendations from Motu tech support. The reason for me was to be able to
use more than 24ch stream in CC more from my computer. That option is
removed on later firmware. The latest public beta firmware which probably
is available for 624 has a very nice touch console. (Mixer made for touch
based surfaces that will be a nice addition)
My understanding is that you should be able to downgrade as you please but
I can not guarantee anything. Tech support is great and will probably
respond quickly even if "Operating system = Other"
/Anders
On Dec 21, 2017 2:36 PM, "georgnk" <georg_nik(a)yahoo.gr> wrote:
Hello,
When I tried to upload the file with older firmwares I couldn't. The
warning
was that I was trying to upload an out of dated firmware. Is there any way
to downgrade?
For sure the web interface using windows Os doesn't show something new
such
as bios menu...Except I am blind
Cheers
list-2 wrote
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
Hello.
i still use an old firmware. As i do not really trust - yet - MOTU with
Gnu/Linux.
Keep in mind that if this AVB series products work under Gnu/Linux, i
think it's more a side effect from USB audio Class compliant than a real
desire from MOTU (it has to work for Apple/Ipad).
As this new v1.3.2+102 firmware shows that you have nothing new in the
web interface ( no bios menu added with other options ? ) it may do
something for Windows/Apple Os's users ?!
On 2017-12-21 02:35, georgnk wrote:
> Hi.
> Yes the firmware is v1.3.2+102 (520 is for the avb)
> I don't know either what the bios menu is doing. I can only find bios
> if I
> press the select button from my interface and shows some info,nothing
> more.
>
> If you test it one day please let me know if you also have this (minor)
> issue.
>
> Have nice holidays. Cheers!
>
>
>
>
> list-2 wrote
>> Hello.
>>
>> I am away from my computer with the MOTU 624 AVB for the holidays.
>> I'll
>> make a try when i'll be back.
>>
>> But i've just checked the firmware pages of MOTU's web site and :
>>
>> v1.3.2+520 (Release Date 2017-12-13)
>>
>> A new one as been added few days ago. I've never tried this one.
>> Is the the firmware you running your card with ?
>>
>> The change log says :
>>
>> Added Bios menu
>>
>> Hmm i'm really wonder what it does, and if it break anything with
>> Gnu/Linux Os.
>>
>> Cheers !
>>
>>
>>
>> On 2017-12-20 02:41, georgnk wrote:
>>> Hello thank you for the reply.
>>> The clicks are periodic.well,not strictly periodic but almost every
>>> two
>>> seconds. I have tried your suggestions but didn't change something.
>>>
>>> What I have also discovered is that the clicks are not passing
>>> through
>>> my
>>> software. Testing a sine wave and using a spectrum analysis in real
>>> time,
>>> sndpeek, clicks don't show up there. It seems they are coming
>>> directly
>>> to my
>>> monitors (headphones)
>>>
>>> Thanks a lot
>>>
>>>
>>> Len Ovens wrote
>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>>>
>>>>> I can also select my sound card without qjackctl and Jackd.
>>>>> Pure data can see my input s and outputs directly. Then I go audio
>>>>> test
>>>>> play
>>>>> the sine wave , wait a while, I move frequency up and down,clicks
>>>>> start
>>>>> and
>>>>> never stop.
>>>>
>>>> If these are random clicks, that sounds like sync issues. Some
>>>> things
>>>> to
>>>> try:
>>>> - set pulse default and alternate sample rate to 48000
>>>> - turn off HDA audio either in bios or in pulse:
>>>> pactl unload-module module-udev-detect
>>>> pactl unload-module module-alsa-card
>>>> (note that if pulse can see any audio card directly,
>>>> it may choose to sync from that one even if you are
>>>> not using it)
>>>> - try different sample rates, in particular both 44100 and
>>>> 48000. It may be that alsa is under the impression
>>>> it can set sample rate when that is not the case.
>>>>
>>>> I have not seen in this thread any meantion of the web interface
>>>> that
>>>> the
>>>> motu AVB series interfaces normally have, so I am guessing this is
>>>> not
>>>> one
>>>> of these boxes. Motu's support in the past with Linux has be
>>>> notoriously
>>>> bad until the AVB series, so you may have something that will not
>>>> work
>>>> with Linux properly... as in, it is USB2.0 compliant so far as sound
>>>> transfer is concerned, but expects a provided blob to do device
>>>> setup.
>>>> The
>>>> AVB series uses a web based setup tool that is OS agnostic.
>>>>
>>>> --
>>>> Len Ovens
>>>> www.ovenwerks.net
>>>>
>>>> _______________________________________________
>>>> Linux-audio-user mailing list
>>>
>>>> Linux-audio-user@.linuxaudio
>>>
>>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from:
>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>>
>
>> Linux-audio-user@.linuxaudio
>
>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>> _______________________________________________
>> Linux-audio-user mailing list
>
>> Linux-audio-user@.linuxaudio
>
>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>
>
>
>
>
> --
> Sent from:
> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
>
Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
2:54 p.m.
Hi,
I'm currently on 1.2.9+28.
For me it's only possible to start jack when I configure it for 24 channels
I/O
Maybe I should downgrade?
On Dec 25, 2017 15:02, "Anders Hellquist" <lau(a)hellquist.net> wrote:
Hi !
I am currently running the public beta for my card which is 1.3.4+539 and
that is limiting the USB streams.
The last one with configurable USB streaming for my card was. 1.2.8+378
I hope the first one for your card 1.2.9+28 still has the option and maybe
1.3.0+59 do as well.
The changlog suggests to me that 1.3.1 is the first crippled one for your
card but since I don't have a 624, I can't check.
Best regards, Anders
On Dec 25, 2017 1:32 PM, "Moshe Werner" <moshwe(a)gmail.com> wrote:
> Hey Anders,
>
> Thanks for that information!
> I wondered why I'm not able anymore to stream 64 channels.
> I have the Motu 1248, which firmware are you on?
> Do you know which it is for the 1248?
>
> Cheers
>
> Moshe
>
>
> On Dec 25, 2017 14:12, "Anders Hellquist" <lau(a)hellquist.net> wrote:
>
> Hi!
>
> I have the Ultralite AVB and have downgraded my card as per
> recommendations from Motu tech support. The reason for me was to be able to
> use more than 24ch stream in CC more from my computer. That option is
> removed on later firmware. The latest public beta firmware which probably
> is available for 624 has a very nice touch console. (Mixer made for touch
> based surfaces that will be a nice addition)
>
> My understanding is that you should be able to downgrade as you please
> but I can not guarantee anything. Tech support is great and will probably
> respond quickly even if "Operating system = Other"
>
> /Anders
>
>
>
> On Dec 21, 2017 2:36 PM, "georgnk" <georg_nik(a)yahoo.gr> wrote:
>
>> Hello,
>> When I tried to upload the file with older firmwares I couldn't. The
>> warning
>> was that I was trying to upload an out of dated firmware. Is there any
>> way
>> to downgrade?
>>
>> For sure the web interface using windows Os doesn't show something new
>> such
>> as bios menu...Except I am blind
>>
>> Cheers
>>
>> list-2 wrote
>> > Hello.
>> >
>> > i still use an old firmware. As i do not really trust - yet - MOTU
>> with
>> > Gnu/Linux.
>> >
>> > Keep in mind that if this AVB series products work under Gnu/Linux, i
>> > think it's more a side effect from USB audio Class compliant than a
>> real
>> > desire from MOTU (it has to work for Apple/Ipad).
>> >
>> > As this new v1.3.2+102 firmware shows that you have nothing new in the
>> > web interface ( no bios menu added with other options ? ) it may do
>> > something for Windows/Apple Os's users ?!
>> >
>> >
>> >
>> > On 2017-12-21 02:35, georgnk wrote:
>> >> Hi.
>> >> Yes the firmware is v1.3.2+102 (520 is for the avb)
>> >> I don't know either what the bios menu is doing. I can only find
bios
>> >> if I
>> >> press the select button from my interface and shows some info,nothing
>> >> more.
>> >>
>> >> If you test it one day please let me know if you also have this
>> (minor)
>> >> issue.
>> >>
>> >> Have nice holidays. Cheers!
>> >>
>> >>
>> >>
>> >>
>> >> list-2 wrote
>> >>> Hello.
>> >>>
>> >>> I am away from my computer with the MOTU 624 AVB for the holidays.
>> >>> I'll
>> >>> make a try when i'll be back.
>> >>>
>> >>> But i've just checked the firmware pages of MOTU's web site
and :
>> >>>
>> >>> v1.3.2+520 (Release Date 2017-12-13)
>> >>>
>> >>> A new one as been added few days ago. I've never tried this
one.
>> >>> Is the the firmware you running your card with ?
>> >>>
>> >>> The change log says :
>> >>>
>> >>> Added Bios menu
>> >>>
>> >>> Hmm i'm really wonder what it does, and if it break anything
with
>> >>> Gnu/Linux Os.
>> >>>
>> >>> Cheers !
>> >>>
>> >>>
>> >>>
>> >>> On 2017-12-20 02:41, georgnk wrote:
>> >>>> Hello thank you for the reply.
>> >>>> The clicks are periodic.well,not strictly periodic but almost
every
>> >>>> two
>> >>>> seconds. I have tried your suggestions but didn't change
something.
>> >>>>
>> >>>> What I have also discovered is that the clicks are not passing
>> >>>> through
>> >>>> my
>> >>>> software. Testing a sine wave and using a spectrum analysis in
real
>> >>>> time,
>> >>>> sndpeek, clicks don't show up there. It seems they are
coming
>> >>>> directly
>> >>>> to my
>> >>>> monitors (headphones)
>> >>>>
>> >>>> Thanks a lot
>> >>>>
>> >>>>
>> >>>> Len Ovens wrote
>> >>>>> On Mon, 18 Dec 2017, georgnk wrote:
>> >>>>>
>> >>>>>> I can also select my sound card without qjackctl and
Jackd.
>> >>>>>> Pure data can see my input s and outputs directly. Then
I go audio
>> >>>>>> test
>> >>>>>> play
>> >>>>>> the sine wave , wait a while, I move frequency up and
down,clicks
>> >>>>>> start
>> >>>>>> and
>> >>>>>> never stop.
>> >>>>>
>> >>>>> If these are random clicks, that sounds like sync issues.
Some
>> >>>>> things
>> >>>>> to
>> >>>>> try:
>> >>>>> - set pulse default and alternate sample rate to 48000
>> >>>>> - turn off HDA audio either in bios or in pulse:
>> >>>>> pactl unload-module module-udev-detect
>> >>>>> pactl unload-module module-alsa-card
>> >>>>> (note that if pulse can see any audio card
directly,
>> >>>>> it may choose to sync from that one even if you
are
>> >>>>> not using it)
>> >>>>> - try different sample rates, in particular both 44100
and
>> >>>>> 48000. It may be that alsa is under the
impression
>> >>>>> it can set sample rate when that is not the case.
>> >>>>>
>> >>>>> I have not seen in this thread any meantion of the web
interface
>> >>>>> that
>> >>>>> the
>> >>>>> motu AVB series interfaces normally have, so I am guessing
this is
>> >>>>> not
>> >>>>> one
>> >>>>> of these boxes. Motu's support in the past with Linux
has be
>> >>>>> notoriously
>> >>>>> bad until the AVB series, so you may have something that
will not
>> >>>>> work
>> >>>>> with Linux properly... as in, it is USB2.0 compliant so far
as
>> sound
>> >>>>> transfer is concerned, but expects a provided blob to do
device
>> >>>>> setup.
>> >>>>> The
>> >>>>> AVB series uses a web based setup tool that is OS agnostic.
>> >>>>>
>> >>>>> --
>> >>>>> Len Ovens
>> >>>>> www.ovenwerks.net
>> >>>>>
>> >>>>> _______________________________________________
>> >>>>> Linux-audio-user mailing list
>> >>>>
>> >>>>> Linux-audio-user@.linuxaudio
>> >>>>
>> >>>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Sent from:
>> >>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>> >>>> _______________________________________________
>> >>>> Linux-audio-user mailing list
>> >>>>
>> >>
>> >>> Linux-audio-user@.linuxaudio
>> >>
>> >>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>> >>> _______________________________________________
>> >>> Linux-audio-user mailing list
>> >>
>> >>> Linux-audio-user@.linuxaudio
>> >>
>> >>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Sent from:
>> >> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>> >> _______________________________________________
>> >> Linux-audio-user mailing list
>> >>
>>
>> > Linux-audio-user@.linuxaudio
>>
>> >> https://lists.linuxaudio.org/listinfo/linux-audio-user
>> > _______________________________________________
>> > Linux-audio-user mailing list
>>
>> > Linux-audio-user@.linuxaudio
>>
>> > https://lists.linuxaudio.org/listinfo/linux-audio-user
>>
>>
>>
>>
>>
>> --
>> Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.ht
>> ml
>> _______________________________________________
>> Linux-audio-user mailing list
>> Linux-audio-user(a)lists.linuxaudio.org
>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> https://lists.linuxaudio.org/listinfo/linux-audio-user
>
>
>
5:57 p.m.
I don't think there is any older firmware for 624
According to MOTU firmware change log 1.2.9 is the first initial firmware
devices are shipped with.
http://motu.com/techsupport/technotes/firmwarechangelog/
/Anders
mån 25 dec. 2017 kl. 14:54 skrev Moshe Werner <moshwe(a)gmail.com>om>:
Hi,
I'm currently on 1.2.9+28.
For me it's only possible to start jack when I configure it for 24
channels I/O
Maybe I should downgrade?
On Dec 25, 2017 15:02, "Anders Hellquist" <lau(a)hellquist.net> wrote:
> Hi !
>
> I am currently running the public beta for my card which is 1.3.4+539 and
> that is limiting the USB streams.
>
> The last one with configurable USB streaming for my card was. 1.2.8+378
>
>
> I hope the first one for your card 1.2.9+28 still has the option and
> maybe 1.3.0+59 do as well.
>
> The changlog suggests to me that 1.3.1 is the first crippled one for your
> card but since I don't have a 624, I can't check.
>
> Best regards, Anders
>
> On Dec 25, 2017 1:32 PM, "Moshe Werner" <moshwe(a)gmail.com> wrote:
>
>> Hey Anders,
>>
>> Thanks for that information!
>> I wondered why I'm not able anymore to stream 64 channels.
>> I have the Motu 1248, which firmware are you on?
>> Do you know which it is for the 1248?
>>
>> Cheers
>>
>> Moshe
>>
>>
>> On Dec 25, 2017 14:12, "Anders Hellquist" <lau(a)hellquist.net>
wrote:
>>
>> Hi!
>>
>> I have the Ultralite AVB and have downgraded my card as per
>> recommendations from Motu tech support. The reason for me was to be able to
>> use more than 24ch stream in CC more from my computer. That option is
>> removed on later firmware. The latest public beta firmware which probably
>> is available for 624 has a very nice touch console. (Mixer made for touch
>> based surfaces that will be a nice addition)
>>
>> My understanding is that you should be able to downgrade as you please
>> but I can not guarantee anything. Tech support is great and will probably
>> respond quickly even if "Operating system = Other"
>>
>> /Anders
>>
>>
>>
>> On Dec 21, 2017 2:36 PM, "georgnk" <georg_nik(a)yahoo.gr> wrote:
>>
>>> Hello,
>>> When I tried to upload the file with older firmwares I couldn't. The
>>> warning
>>> was that I was trying to upload an out of dated firmware. Is there any
>>> way
>>> to downgrade?
>>>
>>> For sure the web interface using windows Os doesn't show something new
>>> such
>>> as bios menu...Except I am blind
>>>
>>> Cheers
>>>
>>> list-2 wrote
>>> > Hello.
>>> >
>>> > i still use an old firmware. As i do not really trust - yet - MOTU
>>> with
>>> > Gnu/Linux.
>>> >
>>> > Keep in mind that if this AVB series products work under Gnu/Linux, i
>>> > think it's more a side effect from USB audio Class compliant than a
>>> real
>>> > desire from MOTU (it has to work for Apple/Ipad).
>>> >
>>> > As this new v1.3.2+102 firmware shows that you have nothing new in the
>>> > web interface ( no bios menu added with other options ? ) it may do
>>> > something for Windows/Apple Os's users ?!
>>> >
>>> >
>>> >
>>> > On 2017-12-21 02:35, georgnk wrote:
>>> >> Hi.
>>> >> Yes the firmware is v1.3.2+102 (520 is for the avb)
>>> >> I don't know either what the bios menu is doing. I can only find
bios
>>> >> if I
>>> >> press the select button from my interface and shows some
info,nothing
>>> >> more.
>>> >>
>>> >> If you test it one day please let me know if you also have this
>>> (minor)
>>> >> issue.
>>> >>
>>> >> Have nice holidays. Cheers!
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> list-2 wrote
>>> >>> Hello.
>>> >>>
>>> >>> I am away from my computer with the MOTU 624 AVB for the
holidays.
>>> >>> I'll
>>> >>> make a try when i'll be back.
>>> >>>
>>> >>> But i've just checked the firmware pages of MOTU's web
site and :
>>> >>>
>>> >>> v1.3.2+520 (Release Date 2017-12-13)
>>> >>>
>>> >>> A new one as been added few days ago. I've never tried this
one.
>>> >>> Is the the firmware you running your card with ?
>>> >>>
>>> >>> The change log says :
>>> >>>
>>> >>> Added Bios menu
>>> >>>
>>> >>> Hmm i'm really wonder what it does, and if it break anything
with
>>> >>> Gnu/Linux Os.
>>> >>>
>>> >>> Cheers !
>>> >>>
>>> >>>
>>> >>>
>>> >>> On 2017-12-20 02:41, georgnk wrote:
>>> >>>> Hello thank you for the reply.
>>> >>>> The clicks are periodic.well,not strictly periodic but
almost every
>>> >>>> two
>>> >>>> seconds. I have tried your suggestions but didn't change
something.
>>> >>>>
>>> >>>> What I have also discovered is that the clicks are not
passing
>>> >>>> through
>>> >>>> my
>>> >>>> software. Testing a sine wave and using a spectrum analysis
in real
>>> >>>> time,
>>> >>>> sndpeek, clicks don't show up there. It seems they are
coming
>>> >>>> directly
>>> >>>> to my
>>> >>>> monitors (headphones)
>>> >>>>
>>> >>>> Thanks a lot
>>> >>>>
>>> >>>>
>>> >>>> Len Ovens wrote
>>> >>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>> >>>>>
>>> >>>>>> I can also select my sound card without qjackctl and
Jackd.
>>> >>>>>> Pure data can see my input s and outputs directly.
Then I go
>>> audio
>>> >>>>>> test
>>> >>>>>> play
>>> >>>>>> the sine wave , wait a while, I move frequency up
and down,clicks
>>> >>>>>> start
>>> >>>>>> and
>>> >>>>>> never stop.
>>> >>>>>
>>> >>>>> If these are random clicks, that sounds like sync
issues. Some
>>> >>>>> things
>>> >>>>> to
>>> >>>>> try:
>>> >>>>> - set pulse default and alternate sample rate to
48000
>>> >>>>> - turn off HDA audio either in bios or in pulse:
>>> >>>>> pactl unload-module module-udev-detect
>>> >>>>> pactl unload-module module-alsa-card
>>> >>>>> (note that if pulse can see any audio card
directly,
>>> >>>>> it may choose to sync from that one even if
you are
>>> >>>>> not using it)
>>> >>>>> - try different sample rates, in particular both 44100
and
>>> >>>>> 48000. It may be that alsa is under the
impression
>>> >>>>> it can set sample rate when that is not the
case.
>>> >>>>>
>>> >>>>> I have not seen in this thread any meantion of the web
interface
>>> >>>>> that
>>> >>>>> the
>>> >>>>> motu AVB series interfaces normally have, so I am
guessing this is
>>> >>>>> not
>>> >>>>> one
>>> >>>>> of these boxes. Motu's support in the past with
Linux has be
>>> >>>>> notoriously
>>> >>>>> bad until the AVB series, so you may have something that
will not
>>> >>>>> work
>>> >>>>> with Linux properly... as in, it is USB2.0 compliant so
far as
>>> sound
>>> >>>>> transfer is concerned, but expects a provided blob to do
device
>>> >>>>> setup.
>>> >>>>> The
>>> >>>>> AVB series uses a web based setup tool that is OS
agnostic.
>>> >>>>>
>>> >>>>> --
>>> >>>>> Len Ovens
>>> >>>>> www.ovenwerks.net
>>> >>>>>
>>> >>>>> _______________________________________________
>>> >>>>> Linux-audio-user mailing list
>>> >>>>
>>> >>>>> Linux-audio-user@.linuxaudio
>>> >>>>
>>> >>>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>> Sent from:
>>> >>>>
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>> >>>> _______________________________________________
>>> >>>> Linux-audio-user mailing list
>>> >>>>
>>> >>
>>> >>> Linux-audio-user@.linuxaudio
>>> >>
>>> >>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>> >>> _______________________________________________
>>> >>> Linux-audio-user mailing list
>>> >>
>>> >>> Linux-audio-user@.linuxaudio
>>> >>
>>> >>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Sent from:
>>> >> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>> >> _______________________________________________
>>> >> Linux-audio-user mailing list
>>> >>
>>>
>>> > Linux-audio-user@.linuxaudio
>>>
>>> >> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>> > _______________________________________________
>>> > Linux-audio-user mailing list
>>>
>>> > Linux-audio-user@.linuxaudio
>>>
>>> > https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.ht
>>> ml
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>> Linux-audio-user(a)lists.linuxaudio.org
>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>
>>
>> _______________________________________________
>> Linux-audio-user mailing list
>> Linux-audio-user(a)lists.linuxaudio.org
>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>
>>
>>
30 Dec
30 Dec
6:26 p.m.
So I'm having an interesting issue.
In the Motu menu (web-app) of my 1248 I can sometimes configure the card
for 64 channels in the "Computer Setup" menu and sometimes the maximum
channel count is 24.
Very strange as all that I did was a reboot of the laptop.
Did anyone elso of the Motu owners encounter something like that?
I'm on firmware 1.2.9+1280.
Cheers
Moshe
On Mon, Dec 25, 2017 at 5:57 PM, Anders Hellquist <lau(a)hellquist.net> wrote:
I don't think there is any older firmware for 624
According to MOTU firmware change log 1.2.9 is the first initial firmware
devices are shipped with.
http://motu.com/techsupport/technotes/firmwarechangelog/
/Anders
mån 25 dec. 2017 kl. 14:54 skrev Moshe Werner <moshwe(a)gmail.com>om>:
> Hi,
>
> I'm currently on 1.2.9+28.
> For me it's only possible to start jack when I configure it for 24
> channels I/O
>
> Maybe I should downgrade?
>
> On Dec 25, 2017 15:02, "Anders Hellquist" <lau(a)hellquist.net> wrote:
>
>> Hi !
>>
>> I am currently running the public beta for my card which is 1.3.4+539
>> and that is limiting the USB streams.
>>
>> The last one with configurable USB streaming for my card was. 1.2.8+378
>>
>>
>> I hope the first one for your card 1.2.9+28 still has the option and
>> maybe 1.3.0+59 do as well.
>>
>> The changlog suggests to me that 1.3.1 is the first crippled one for
>> your card but since I don't have a 624, I can't check.
>>
>> Best regards, Anders
>>
>> On Dec 25, 2017 1:32 PM, "Moshe Werner" <moshwe(a)gmail.com>
wrote:
>>
>>> Hey Anders,
>>>
>>> Thanks for that information!
>>> I wondered why I'm not able anymore to stream 64 channels.
>>> I have the Motu 1248, which firmware are you on?
>>> Do you know which it is for the 1248?
>>>
>>> Cheers
>>>
>>> Moshe
>>>
>>>
>>> On Dec 25, 2017 14:12, "Anders Hellquist" <lau(a)hellquist.net>
wrote:
>>>
>>> Hi!
>>>
>>> I have the Ultralite AVB and have downgraded my card as per
>>> recommendations from Motu tech support. The reason for me was to be able to
>>> use more than 24ch stream in CC more from my computer. That option is
>>> removed on later firmware. The latest public beta firmware which probably
>>> is available for 624 has a very nice touch console. (Mixer made for touch
>>> based surfaces that will be a nice addition)
>>>
>>> My understanding is that you should be able to downgrade as you please
>>> but I can not guarantee anything. Tech support is great and will probably
>>> respond quickly even if "Operating system = Other"
>>>
>>> /Anders
>>>
>>>
>>>
>>> On Dec 21, 2017 2:36 PM, "georgnk" <georg_nik(a)yahoo.gr>
wrote:
>>>
>>>> Hello,
>>>> When I tried to upload the file with older firmwares I couldn't. The
>>>> warning
>>>> was that I was trying to upload an out of dated firmware. Is there any
>>>> way
>>>> to downgrade?
>>>>
>>>> For sure the web interface using windows Os doesn't show something
new
>>>> such
>>>> as bios menu...Except I am blind
>>>>
>>>> Cheers
>>>>
>>>> list-2 wrote
>>>> > Hello.
>>>> >
>>>> > i still use an old firmware. As i do not really trust - yet - MOTU
>>>> with
>>>> > Gnu/Linux.
>>>> >
>>>> > Keep in mind that if this AVB series products work under Gnu/Linux,
i
>>>> > think it's more a side effect from USB audio Class compliant
than a
>>>> real
>>>> > desire from MOTU (it has to work for Apple/Ipad).
>>>> >
>>>> > As this new v1.3.2+102 firmware shows that you have nothing new in
>>>> the
>>>> > web interface ( no bios menu added with other options ? ) it may do
>>>> > something for Windows/Apple Os's users ?!
>>>> >
>>>> >
>>>> >
>>>> > On 2017-12-21 02:35, georgnk wrote:
>>>> >> Hi.
>>>> >> Yes the firmware is v1.3.2+102 (520 is for the avb)
>>>> >> I don't know either what the bios menu is doing. I can only
find
>>>> bios
>>>> >> if I
>>>> >> press the select button from my interface and shows some
>>>> info,nothing
>>>> >> more.
>>>> >>
>>>> >> If you test it one day please let me know if you also have this
>>>> (minor)
>>>> >> issue.
>>>> >>
>>>> >> Have nice holidays. Cheers!
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> list-2 wrote
>>>> >>> Hello.
>>>> >>>
>>>> >>> I am away from my computer with the MOTU 624 AVB for the
holidays.
>>>> >>> I'll
>>>> >>> make a try when i'll be back.
>>>> >>>
>>>> >>> But i've just checked the firmware pages of MOTU's
web site and :
>>>> >>>
>>>> >>> v1.3.2+520 (Release Date 2017-12-13)
>>>> >>>
>>>> >>> A new one as been added few days ago. I've never tried
this one.
>>>> >>> Is the the firmware you running your card with ?
>>>> >>>
>>>> >>> The change log says :
>>>> >>>
>>>> >>> Added Bios menu
>>>> >>>
>>>> >>> Hmm i'm really wonder what it does, and if it break
anything with
>>>> >>> Gnu/Linux Os.
>>>> >>>
>>>> >>> Cheers !
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> On 2017-12-20 02:41, georgnk wrote:
>>>> >>>> Hello thank you for the reply.
>>>> >>>> The clicks are periodic.well,not strictly periodic but
almost
>>>> every
>>>> >>>> two
>>>> >>>> seconds. I have tried your suggestions but didn't
change
>>>> something.
>>>> >>>>
>>>> >>>> What I have also discovered is that the clicks are not
passing
>>>> >>>> through
>>>> >>>> my
>>>> >>>> software. Testing a sine wave and using a spectrum
analysis in
>>>> real
>>>> >>>> time,
>>>> >>>> sndpeek, clicks don't show up there. It seems they
are coming
>>>> >>>> directly
>>>> >>>> to my
>>>> >>>> monitors (headphones)
>>>> >>>>
>>>> >>>> Thanks a lot
>>>> >>>>
>>>> >>>>
>>>> >>>> Len Ovens wrote
>>>> >>>>> On Mon, 18 Dec 2017, georgnk wrote:
>>>> >>>>>
>>>> >>>>>> I can also select my sound card without qjackctl
and Jackd.
>>>> >>>>>> Pure data can see my input s and outputs
directly. Then I go
>>>> audio
>>>> >>>>>> test
>>>> >>>>>> play
>>>> >>>>>> the sine wave , wait a while, I move frequency
up and
>>>> down,clicks
>>>> >>>>>> start
>>>> >>>>>> and
>>>> >>>>>> never stop.
>>>> >>>>>
>>>> >>>>> If these are random clicks, that sounds like sync
issues. Some
>>>> >>>>> things
>>>> >>>>> to
>>>> >>>>> try:
>>>> >>>>> - set pulse default and alternate sample rate to
48000
>>>> >>>>> - turn off HDA audio either in bios or in pulse:
>>>> >>>>> pactl unload-module module-udev-detect
>>>> >>>>> pactl unload-module module-alsa-card
>>>> >>>>> (note that if pulse can see any audio card
directly,
>>>> >>>>> it may choose to sync from that one even
if you are
>>>> >>>>> not using it)
>>>> >>>>> - try different sample rates, in particular both
44100 and
>>>> >>>>> 48000. It may be that alsa is under the
impression
>>>> >>>>> it can set sample rate when that is not
the case.
>>>> >>>>>
>>>> >>>>> I have not seen in this thread any meantion of the
web interface
>>>> >>>>> that
>>>> >>>>> the
>>>> >>>>> motu AVB series interfaces normally have, so I am
guessing this
>>>> is
>>>> >>>>> not
>>>> >>>>> one
>>>> >>>>> of these boxes. Motu's support in the past with
Linux has be
>>>> >>>>> notoriously
>>>> >>>>> bad until the AVB series, so you may have something
that will not
>>>> >>>>> work
>>>> >>>>> with Linux properly... as in, it is USB2.0 compliant
so far as
>>>> sound
>>>> >>>>> transfer is concerned, but expects a provided blob
to do device
>>>> >>>>> setup.
>>>> >>>>> The
>>>> >>>>> AVB series uses a web based setup tool that is OS
agnostic.
>>>> >>>>>
>>>> >>>>> --
>>>> >>>>> Len Ovens
>>>> >>>>> www.ovenwerks.net
>>>> >>>>>
>>>> >>>>> _______________________________________________
>>>> >>>>> Linux-audio-user mailing list
>>>> >>>>
>>>> >>>>> Linux-audio-user@.linuxaudio
>>>> >>>>
>>>> >>>>>
https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> --
>>>> >>>> Sent from:
>>>> >>>>
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>>> >>>> _______________________________________________
>>>> >>>> Linux-audio-user mailing list
>>>> >>>>
>>>> >>
>>>> >>> Linux-audio-user@.linuxaudio
>>>> >>
>>>> >>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>> >>> _______________________________________________
>>>> >>> Linux-audio-user mailing list
>>>> >>
>>>> >>> Linux-audio-user@.linuxaudio
>>>> >>
>>>> >>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Sent from:
>>>> >> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>>>> >> _______________________________________________
>>>> >> Linux-audio-user mailing list
>>>> >>
>>>>
>>>> > Linux-audio-user@.linuxaudio
>>>>
>>>> >> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>> > _______________________________________________
>>>> > Linux-audio-user mailing list
>>>>
>>>> > Linux-audio-user@.linuxaudio
>>>>
>>>> > https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-
>>>> f5.html
>>>> _______________________________________________
>>>> Linux-audio-user mailing list
>>>> Linux-audio-user(a)lists.linuxaudio.org
>>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>>
>>>
>>> _______________________________________________
>>> Linux-audio-user mailing list
>>> Linux-audio-user(a)lists.linuxaudio.org
>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
>>>
>>>
>>>
7:29 p.m.
* Moshe Werner <moshwe(a)gmail.com> [2017-12-30 18:26]:
So I'm having an interesting issue.
In the Motu menu (web-app) of my 1248 I can sometimes configure the card
for 64 channels in the "Computer Setup" menu and sometimes the maximum
channel count is 24.
Very strange as all that I did was a reboot of the laptop.
Did anyone elso of the Motu owners encounter something like that?
I'm on firmware 1.2.9+1280.
See this thread perhaps
https://lists.linuxaudio.org/pipermail/linux-audio-user/2017-September/1086…
25 Dec
25 Dec
2:45 p.m.
Hi that's interesting.
I couldn't downgrade so I haven't tried older firmware.
Maybe I need to contact tech support.
By the way, I am curious if the ultralite avb has also these periodic clicks
I described before. Thanks.
Anders Hellquist wrote
Hi!
I have the Ultralite AVB and have downgraded my card as per
recommendations
from Motu tech support. The reason for me was to be able to use more than
24ch stream in CC more from my computer. That option is removed on later
firmware. The latest public beta firmware which probably is available for
624 has a very nice touch console. (Mixer made for touch based surfaces
that will be a nice addition)
My understanding is that you should be able to downgrade as you please but
I can not guarantee anything. Tech support is great and will probably
respond quickly even if "Operating system = Other"
/Anders
On Dec 21, 2017 2:36 PM, "georgnk" <
georg_nik@
> wrote:
> Hello,
> When I tried to upload the file with older firmwares I couldn't. The
> warning
> was that I was trying to upload an out of dated firmware. Is there any
> way
> to downgrade?
>
> For sure the web interface using windows Os doesn't show something new
> such
> as bios menu...Except I am blind
>
> Cheers
>
> list-2 wrote
> > Hello.
> >
> > i still use an old firmware. As i do not really trust - yet - MOTU
> with
> > Gnu/Linux.
> >
> > Keep in mind that if this AVB series products work under Gnu/Linux, i
> > think it's more a side effect from USB audio Class compliant than a
> real
> > desire from MOTU (it has to work for Apple/Ipad).
> >
> > As this new v1.3.2+102 firmware shows that you have nothing new in the
> > web interface ( no bios menu added with other options ? ) it may do
> > something for Windows/Apple Os's users ?!
> >
> >
> >
> > On 2017-12-21 02:35, georgnk wrote:
> >> Hi.
> >> Yes the firmware is v1.3.2+102 (520 is for the avb)
> >> I don't know either what the bios menu is doing. I can only find bios
> >> if I
> >> press the select button from my interface and shows some info,nothing
> >> more.
> >>
> >> If you test it one day please let me know if you also have this
> (minor)
> >> issue.
> >>
> >> Have nice holidays. Cheers!
> >>
> >>
> >>
> >>
> >> list-2 wrote
> >>> Hello.
> >>>
> >>> I am away from my computer with the MOTU 624 AVB for the holidays.
> >>> I'll
> >>> make a try when i'll be back.
> >>>
> >>> But i've just checked the firmware pages of MOTU's web site and
:
> >>>
> >>> v1.3.2+520 (Release Date 2017-12-13)
> >>>
> >>> A new one as been added few days ago. I've never tried this one.
> >>> Is the the firmware you running your card with ?
> >>>
> >>> The change log says :
> >>>
> >>> Added Bios menu
> >>>
> >>> Hmm i'm really wonder what it does, and if it break anything with
> >>> Gnu/Linux Os.
> >>>
> >>> Cheers !
> >>>
> >>>
> >>>
> >>> On 2017-12-20 02:41, georgnk wrote:
> >>>> Hello thank you for the reply.
> >>>> The clicks are periodic.well,not strictly periodic but almost every
> >>>> two
> >>>> seconds. I have tried your suggestions but didn't change
something.
> >>>>
> >>>> What I have also discovered is that the clicks are not passing
> >>>> through
> >>>> my
> >>>> software. Testing a sine wave and using a spectrum analysis in real
> >>>> time,
> >>>> sndpeek, clicks don't show up there. It seems they are coming
> >>>> directly
> >>>> to my
> >>>> monitors (headphones)
> >>>>
> >>>> Thanks a lot
> >>>>
> >>>>
> >>>> Len Ovens wrote
> >>>>> On Mon, 18 Dec 2017, georgnk wrote:
> >>>>>
> >>>>>> I can also select my sound card without qjackctl and Jackd.
> >>>>>> Pure data can see my input s and outputs directly. Then I go
audio
> >>>>>> test
> >>>>>> play
> >>>>>> the sine wave , wait a while, I move frequency up and
down,clicks
> >>>>>> start
> >>>>>> and
> >>>>>> never stop.
> >>>>>
> >>>>> If these are random clicks, that sounds like sync issues. Some
> >>>>> things
> >>>>> to
> >>>>> try:
> >>>>> - set pulse default and alternate sample rate to 48000
> >>>>> - turn off HDA audio either in bios or in pulse:
> >>>>> pactl unload-module module-udev-detect
> >>>>> pactl unload-module module-alsa-card
> >>>>> (note that if pulse can see any audio card directly,
> >>>>> it may choose to sync from that one even if you are
> >>>>> not using it)
> >>>>> - try different sample rates, in particular both 44100 and
> >>>>> 48000. It may be that alsa is under the impression
> >>>>> it can set sample rate when that is not the case.
> >>>>>
> >>>>> I have not seen in this thread any meantion of the web
interface
> >>>>> that
> >>>>> the
> >>>>> motu AVB series interfaces normally have, so I am guessing this
is
> >>>>> not
> >>>>> one
> >>>>> of these boxes. Motu's support in the past with Linux has
be
> >>>>> notoriously
> >>>>> bad until the AVB series, so you may have something that will
not
> >>>>> work
> >>>>> with Linux properly... as in, it is USB2.0 compliant so far as
> sound
> >>>>> transfer is concerned, but expects a provided blob to do device
> >>>>> setup.
> >>>>> The
> >>>>> AVB series uses a web based setup tool that is OS agnostic.
> >>>>>
> >>>>> --
> >>>>> Len Ovens
> >>>>> www.ovenwerks.net
> >>>>>
> >>>>> _______________________________________________
> >>>>> Linux-audio-user mailing list
> >>>>
> >>>>
Linux-audio-user@.linuxaudio
> >>>>
> >>>>> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Sent from:
> >>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> >>>> _______________________________________________
> >>>> Linux-audio-user mailing list
> >>>>
> >>
> >>
Linux-audio-user@.linuxaudio
> >>
> >>>> >>>
_______________________________________________
> >>> Linux-audio-user mailing list
> >>
> >>
Linux-audio-user@.linuxaudio
> >>
> >>> >>
> >>
> >>
> >>
> >>
> >> --
> >> Sent from:
> >> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> >> _______________________________________________
> >> Linux-audio-user mailing list
> >>
>
> Linux-audio-user@.linuxaudio
>
> >> >
_______________________________________________
> > Linux-audio-user mailing list
>
> Linux-audio-user@.linuxaudio
>
> >
>
>
>
>
> --
> Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
5:06 p.m.
Hi
No periodic clicks so far. Have been using the Ultralite almost every day
for a few months (I have two of them but rarely use the other one). The
only glitch so far are a few times where the sound has been a bit strange
like distorted in the top of the frequencies. Kind of bit crushed low
resolution effecting the top end only. That has gone away by just stop jack
(using cadence) and starting it again. I use my card set to internal clock
source and no connected AVB or adat devices by the way.
Regards, Anders
On Dec 25, 2017 2:45 PM, "georgnk" <georg_nik(a)yahoo.gr> wrote:
Hi that's interesting.
I couldn't downgrade so I haven't tried older firmware.
Maybe I need to contact tech support.
By the way, I am curious if the ultralite avb has also these periodic
clicks
I described before. Thanks.
Anders Hellquist wrote
Hi!
I have the Ultralite AVB and have downgraded my card as per
recommendations
from Motu tech support. The reason for me was to be able to use more than
24ch stream in CC more from my computer. That option is removed on later
firmware. The latest public beta firmware which probably is available for
624 has a very nice touch console. (Mixer made for touch based surfaces
that will be a nice addition)
My understanding is that you should be able to downgrade as you please
but
I can not guarantee anything. Tech support is
great and will probably
respond quickly even if "Operating system = Other"
/Anders
On Dec 21, 2017 2:36 PM, "georgnk" <
georg_nik@
> wrote:
> Hello,
> When I tried to upload the file with older firmwares I couldn't. The
> warning
> was that I was trying to upload an out of dated firmware. Is there any
> way
> to downgrade?
>
> For sure the web interface using windows Os doesn't show something new
> such
> as bios menu...Except I am blind
>
> Cheers
>
> list-2 wrote
> > Hello.
> >
> > i still use an old firmware. As i do not really trust - yet - MOTU
> with
> > Gnu/Linux.
> >
> > Keep in mind that if this AVB series products work under Gnu/Linux, i
> > think it's more a side effect from USB audio Class compliant than a
> real
> > desire from MOTU (it has to work for Apple/Ipad).
> >
> > As this new v1.3.2+102 firmware shows that you have nothing new in the
> > web interface ( no bios menu added with other options ? ) it may do
> > something for Windows/Apple Os's users ?!
> >
> >
> >
> > On 2017-12-21 02:35, georgnk wrote:
> >> Hi.
> >> Yes the firmware is v1.3.2+102 (520 is for the avb)
> >> I don't know either what the bios menu is doing. I can only find bios
> >> if I
> >> press the select button from my interface and shows some info,nothing
> >> more.
> >>
> >> If you test it one day please let me know if you also have this
> (minor)
> >> issue.
> >>
> >> Have nice holidays. Cheers!
> >>
> >>
> >>
> >>
> >> list-2 wrote
> >>> Hello.
> >>>
> >>> I am away from my computer with the MOTU 624 AVB for the holidays.
> >>> I'll
> >>> make a try when i'll be back.
> >>>
> >>> But i've just checked the firmware pages of MOTU's web site and
:
> >>>
> >>> v1.3.2+520 (Release Date 2017-12-13)
> >>>
> >>> A new one as been added few days ago. I've never tried this one.
> >>> Is the the firmware you running your card with ?
> >>>
> >>> The change log says :
> >>>
> >>> Added Bios menu
> >>>
> >>> Hmm i'm really wonder what it does, and if it break anything with
> >>> Gnu/Linux Os.
> >>>
> >>> Cheers !
> >>>
> >>>
> >>>
> >>> On 2017-12-20 02:41, georgnk wrote:
> >>>> Hello thank you for the reply.
> >>>> The clicks are periodic.well,not strictly periodic but almost every
> >>>> two
> >>>> seconds. I have tried your suggestions but didn't change
something.
> >>>>
> >>>> What I have also discovered is that the clicks are not passing
> >>>> through
> >>>> my
> >>>> software. Testing a sine wave and using a spectrum analysis in real
> >>>> time,
> >>>> sndpeek, clicks don't show up there. It seems they are coming
> >>>> directly
> >>>> to my
> >>>> monitors (headphones)
> >>>>
> >>>> Thanks a lot
> >>>>
> >>>>
> >>>> Len Ovens wrote
> >>>>> On Mon, 18 Dec 2017, georgnk wrote:
> >>>>>
> >>>>>> I can also select my sound card without qjackctl and Jackd.
> >>>>>> Pure data can see my input s and outputs directly. Then I go
audio
> >>>>>> test
> >>>>>> play
> >>>>>> the sine wave , wait a while, I move frequency up and
down,clicks
> >>>>>> start
> >>>>>> and
> >>>>>> never stop.
> >>>>>
> >>>>> If these are random clicks, that sounds like sync issues. Some
> >>>>> things
> >>>>> to
> >>>>> try:
> >>>>> - set pulse default and alternate sample rate to 48000
> >>>>> - turn off HDA audio either in bios or in pulse:
> >>>>> pactl unload-module module-udev-detect
> >>>>> pactl unload-module module-alsa-card
> >>>>> (note that if pulse can see any audio card directly,
> >>>>> it may choose to sync from that one even if you are
> >>>>> not using it)
> >>>>> - try different sample rates, in particular both 44100 and
> >>>>> 48000. It may be that alsa is under the impression
> >>>>> it can set sample rate when that is not the case.
> >>>>>
> >>>>> I have not seen in this thread any meantion of the web
interface
> >>>>> that
> >>>>> the
> >>>>> motu AVB series interfaces normally have, so I am guessing this
is
> >>>>> not
> >>>>> one
> >>>>> of these boxes. Motu's support in the past with Linux has
be
> >>>>> notoriously
> >>>>> bad until the AVB series, so you may have something that will
not
> >>>>> work
> >>>>> with Linux properly... as in, it is USB2.0 compliant so far as
> sound
> >>>>> transfer is concerned, but expects a provided blob to do device
> >>>>> setup.
> >>>>> The
> >>>>> AVB series uses a web based setup tool that is OS agnostic.
> >>>>>
> >>>>> --
> >>>>> Len Ovens
> >>>>> www.ovenwerks.net
> >>>>>
> >>>>> _______________________________________________
> >>>>> Linux-audio-user mailing list
> >>>>
> >>>>> Linux-audio-user@.linuxaudio
> >>>>
> >>>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Sent from:
> >>>> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> >>>> _______________________________________________
> >>>> Linux-audio-user mailing list
> >>>>
> >>
> >>> Linux-audio-user@.linuxaudio
> >>
> >>>> https://lists.linuxaudio.org/listinfo/linux-audio-user
> >>> _______________________________________________
> >>> Linux-audio-user mailing list
> >>
> >>> Linux-audio-user@.linuxaudio
> >>
> >>> https://lists.linuxaudio.org/listinfo/linux-audio-user
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Sent from:
> >> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
> >> _______________________________________________
> >> Linux-audio-user mailing list
> >>
>
>
f5.html
Linux-audio-user@.linuxaudio
>
> >> https://lists.linuxaudio.org/listinfo/linux-audio-user
> > _______________________________________________
> > Linux-audio-user mailing list
>
> Linux-audio-user@.linuxaudio
>
>>
>
>
>
>
> --
> Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user- >
_______________________________________________
> Linux-audio-user mailing list
>
Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
6:02 p.m.
Hi. Thanks for the info.
It seems other avb products have different result?
Hmmm maybe usb 3 super speed?..Who knows.
Anyway thanks
Anders Hellquist wrote
Hi
No periodic clicks so far. Have been using the Ultralite almost every day
for a few months (I have two of them but rarely use the other one). The
only glitch so far are a few times where the sound has been a bit strange
like distorted in the top of the frequencies. Kind of bit crushed low
resolution effecting the top end only. That has gone away by just stop
jack
(using cadence) and starting it again. I use my card set to internal clock
source and no connected AVB or adat devices by the way.
Regards, Anders
On Dec 25, 2017 2:45 PM, "georgnk" <
georg_nik@
> > wrote:
>
>> Hi that's interesting.
>> I couldn't downgrade so I haven't tried older firmware.
>> Maybe I need to contact tech support.
>>
>> By the way, I am curious if the ultralite avb has also these periodic
>> clicks
>> I described before. Thanks.
>>
>>
>> Anders Hellquist wrote
>> > Hi!
>> >
>> > I have the Ultralite AVB and have downgraded my card as per
>> > recommendations
>> > from Motu tech support. The reason for me was to be able to use more
>> than
>> > 24ch stream in CC more from my computer. That option is removed on
>> later
>> > firmware. The latest public beta firmware which probably is available
>> for
>> > 624 has a very nice touch console. (Mixer made for touch based surfaces
>> > that will be a nice addition)
>> >
>> > My understanding is that you should be able to downgrade as you please
>> but
>> > I can not guarantee anything. Tech support is great and will probably
>> > respond quickly even if "Operating system = Other"
>> >
>> > /Anders
>> >
>> >
>> >
>> > On Dec 21, 2017 2:36 PM, "georgnk" <
>>
>> georg_nik@
>>
>> > > wrote:
>> >
>> >> Hello,
>> >> When I tried to upload the file with older firmwares I couldn't.
The
>> >> warning
>> >> was that I was trying to upload an out of dated firmware. Is there any
>> >> way
>> >> to downgrade?
>> >>
>> >> For sure the web interface using windows Os doesn't show something
new
>> >> such
>> >> as bios menu...Except I am blind
>> >>
>> >> Cheers
>> >>
>> >> list-2 wrote
>> >> > Hello.
>> >> >
>> >> > i still use an old firmware. As i do not really trust - yet -
MOTU
>> >> with
>> >> > Gnu/Linux.
>> >> >
>> >> > Keep in mind that if this AVB series products work under
Gnu/Linux,
>> i
>> >> > think it's more a side effect from USB audio Class compliant
than a
>> >> real
>> >> > desire from MOTU (it has to work for Apple/Ipad).
>> >> >
>> >> > As this new v1.3.2+102 firmware shows that you have nothing new in
>> the
>> >> > web interface ( no bios menu added with other options ? ) it may
do
>> >> > something for Windows/Apple Os's users ?!
>> >> >
>> >> >
>> >> >
>> >> > On 2017-12-21 02:35, georgnk wrote:
>> >> >> Hi.
>> >> >> Yes the firmware is v1.3.2+102 (520 is for the avb)
>> >> >> I don't know either what the bios menu is doing. I can only
find
>> bios
>> >> >> if I
>> >> >> press the select button from my interface and shows some
>> info,nothing
>> >> >> more.
>> >> >>
>> >> >> If you test it one day please let me know if you also have
this
>> >> (minor)
>> >> >> issue.
>> >> >>
>> >> >> Have nice holidays. Cheers!
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> list-2 wrote
>> >> >>> Hello.
>> >> >>>
>> >> >>> I am away from my computer with the MOTU 624 AVB for the
holidays.
>> >> >>> I'll
>> >> >>> make a try when i'll be back.
>> >> >>>
>> >> >>> But i've just checked the firmware pages of MOTU's
web site and :
>> >> >>>
>> >> >>> v1.3.2+520 (Release Date 2017-12-13)
>> >> >>>
>> >> >>> A new one as been added few days ago. I've never tried
this one.
>> >> >>> Is the the firmware you running your card with ?
>> >> >>>
>> >> >>> The change log says :
>> >> >>>
>> >> >>> Added Bios menu
>> >> >>>
>> >> >>> Hmm i'm really wonder what it does, and if it break
anything with
>> >> >>> Gnu/Linux Os.
>> >> >>>
>> >> >>> Cheers !
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> On 2017-12-20 02:41, georgnk wrote:
>> >> >>>> Hello thank you for the reply.
>> >> >>>> The clicks are periodic.well,not strictly periodic but
almost
>> every
>> >> >>>> two
>> >> >>>> seconds. I have tried your suggestions but didn't
change
>> something.
>> >> >>>>
>> >> >>>> What I have also discovered is that the clicks are not
passing
>> >> >>>> through
>> >> >>>> my
>> >> >>>> software. Testing a sine wave and using a spectrum
analysis in
>> real
>> >> >>>> time,
>> >> >>>> sndpeek, clicks don't show up there. It seems they
are coming
>> >> >>>> directly
>> >> >>>> to my
>> >> >>>> monitors (headphones)
>> >> >>>>
>> >> >>>> Thanks a lot
>> >> >>>>
>> >> >>>>
>> >> >>>> Len Ovens wrote
>> >> >>>>> On Mon, 18 Dec 2017, georgnk wrote:
>> >> >>>>>
>> >> >>>>>> I can also select my sound card without
qjackctl and Jackd.
>> >> >>>>>> Pure data can see my input s and outputs
directly. Then I go
>> audio
>> >> >>>>>> test
>> >> >>>>>> play
>> >> >>>>>> the sine wave , wait a while, I move frequency
up and
>> down,clicks
>> >> >>>>>> start
>> >> >>>>>> and
>> >> >>>>>> never stop.
>> >> >>>>>
>> >> >>>>> If these are random clicks, that sounds like sync
issues. Some
>> >> >>>>> things
>> >> >>>>> to
>> >> >>>>> try:
>> >> >>>>> - set pulse default and alternate sample rate to
48000
>> >> >>>>> - turn off HDA audio either in bios or in pulse:
>> >> >>>>> pactl unload-module module-udev-detect
>> >> >>>>> pactl unload-module module-alsa-card
>> >> >>>>> (note that if pulse can see any audio
card directly,
>> >> >>>>> it may choose to sync from that one even
if you are
>> >> >>>>> not using it)
>> >> >>>>> - try different sample rates, in particular both
44100 and
>> >> >>>>> 48000. It may be that alsa is under the
impression
>> >> >>>>> it can set sample rate when that is not
the case.
>> >> >>>>>
>> >> >>>>> I have not seen in this thread any meantion of the
web interface
>> >> >>>>> that
>> >> >>>>> the
>> >> >>>>> motu AVB series interfaces normally have, so I am
guessing this
>> is
>> >> >>>>> not
>> >> >>>>> one
>> >> >>>>> of these boxes. Motu's support in the past with
Linux has be
>> >> >>>>> notoriously
>> >> >>>>> bad until the AVB series, so you may have something
that will
>> not
>> >> >>>>> work
>> >> >>>>> with Linux properly... as in, it is USB2.0
compliant so far as
>> >> sound
>> >> >>>>> transfer is concerned, but expects a provided blob
to do device
>> >> >>>>> setup.
>> >> >>>>> The
>> >> >>>>> AVB series uses a web based setup tool that is OS
agnostic.
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>> Len Ovens
>> >> >>>>> www.ovenwerks.net
>> >> >>>>>
>> >> >>>>> _______________________________________________
>> >> >>>>> Linux-audio-user mailing list
>> >> >>>>
>> >> >>>>
Linux-audio-user@.linuxaudio
>> >> >>>>
>> >> >>>>>> >>
>>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> --
>> >> >>>> Sent from:
>> >> >>>>
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>> >> >>>> _______________________________________________
>> >> >>>> Linux-audio-user mailing list
>> >> >>>>
>> >> >>
>> >> >>
Linux-audio-user@.linuxaudio
>> >> >>
>> >> >>>>> >>
>>> _______________________________________________
>> >> >>> Linux-audio-user mailing list
>> >> >>
>> >> >>
Linux-audio-user@.linuxaudio
>> >> >>
>> >> >>>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Sent from:
>> >> >> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>> >> >> _______________________________________________
>> >> >> Linux-audio-user mailing list
>> >> >>
>> >>
>> >>
Linux-audio-user@.linuxaudio
>> >>
>> >> >>> >> >
_______________________________________________
>> >> > Linux-audio-user mailing list
>> >>
>> >>
Linux-audio-user@.linuxaudio
>> >>
>> >> >> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-
>> f5.html
>> >> _______________________________________________
>> >> Linux-audio-user mailing list
>> >>
>>
>>
Linux-audio-user@.linuxaudio
>>
>> >>> >>
>> >
>> > _______________________________________________
>> > Linux-audio-user mailing list
>>
>>
Linux-audio-user@.linuxaudio
>>
>> >>
>>
>>
>>
>>
>> --
>> Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>> _______________________________________________
>> Linux-audio-user mailing list
>>
Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
27 Mar
27 Mar
9:55 a.m.
Anders Hellquist wrote
Hi
No periodic clicks so far. Have been using the Ultralite almost every day
for a few months (I have two of them but rarely use the other one). The
only glitch so far are a few times where the sound has been a bit strange
like distorted in the top of the frequencies. Kind of bit crushed low
resolution effecting the top end only. That has gone away by just stop
jack
(using cadence) and starting it again. I use my card set to internal clock
source and no connected AVB or adat devices by the way.
Regards, Anders
On Dec 25, 2017 2:45 PM, "georgnk" <
georg_nik@
> > wrote:
>
>> Hi that's interesting.
>> I couldn't downgrade so I haven't tried older firmware.
>> Maybe I need to contact tech support.
>>
>> By the way, I am curious if the ultralite avb has also these periodic
>> clicks
>> I described before. Thanks.
>>
>>
>> Anders Hellquist wrote
>> > Hi!
>> >
>> > I have the Ultralite AVB and have downgraded my card as per
>> > recommendations
>> > from Motu tech support. The reason for me was to be able to use more
>> than
>> > 24ch stream in CC more from my computer. That option is removed on
>> later
>> > firmware. The latest public beta firmware which probably is available
>> for
>> > 624 has a very nice touch console. (Mixer made for touch based surfaces
>> > that will be a nice addition)
>> >
>> > My understanding is that you should be able to downgrade as you please
>> but
>> > I can not guarantee anything. Tech support is great and will probably
>> > respond quickly even if "Operating system = Other"
>> >
>> > /Anders
>> >
>> >
>> >
>> > On Dec 21, 2017 2:36 PM, "georgnk" <
>>
>> georg_nik@
>>
>> > > wrote:
>> >
>> >> Hello,
>> >> When I tried to upload the file with older firmwares I couldn't.
The
>> >> warning
>> >> was that I was trying to upload an out of dated firmware. Is there any
>> >> way
>> >> to downgrade?
>> >>
>> >> For sure the web interface using windows Os doesn't show something
new
>> >> such
>> >> as bios menu...Except I am blind
>> >>
>> >> Cheers
>> >>
>> >> list-2 wrote
>> >> > Hello.
>> >> >
>> >> > i still use an old firmware. As i do not really trust - yet -
MOTU
>> >> with
>> >> > Gnu/Linux.
>> >> >
>> >> > Keep in mind that if this AVB series products work under
Gnu/Linux,
>> i
>> >> > think it's more a side effect from USB audio Class compliant
than a
>> >> real
>> >> > desire from MOTU (it has to work for Apple/Ipad).
>> >> >
>> >> > As this new v1.3.2+102 firmware shows that you have nothing new in
>> the
>> >> > web interface ( no bios menu added with other options ? ) it may
do
>> >> > something for Windows/Apple Os's users ?!
>> >> >
>> >> >
>> >> >
>> >> > On 2017-12-21 02:35, georgnk wrote:
>> >> >> Hi.
>> >> >> Yes the firmware is v1.3.2+102 (520 is for the avb)
>> >> >> I don't know either what the bios menu is doing. I can only
find
>> bios
>> >> >> if I
>> >> >> press the select button from my interface and shows some
>> info,nothing
>> >> >> more.
>> >> >>
>> >> >> If you test it one day please let me know if you also have
this
>> >> (minor)
>> >> >> issue.
>> >> >>
>> >> >> Have nice holidays. Cheers!
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> list-2 wrote
>> >> >>> Hello.
>> >> >>>
>> >> >>> I am away from my computer with the MOTU 624 AVB for the
holidays.
>> >> >>> I'll
>> >> >>> make a try when i'll be back.
>> >> >>>
>> >> >>> But i've just checked the firmware pages of MOTU's
web site and :
>> >> >>>
>> >> >>> v1.3.2+520 (Release Date 2017-12-13)
>> >> >>>
>> >> >>> A new one as been added few days ago. I've never tried
this one.
>> >> >>> Is the the firmware you running your card with ?
>> >> >>>
>> >> >>> The change log says :
>> >> >>>
>> >> >>> Added Bios menu
>> >> >>>
>> >> >>> Hmm i'm really wonder what it does, and if it break
anything with
>> >> >>> Gnu/Linux Os.
>> >> >>>
>> >> >>> Cheers !
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> On 2017-12-20 02:41, georgnk wrote:
>> >> >>>> Hello thank you for the reply.
>> >> >>>> The clicks are periodic.well,not strictly periodic but
almost
>> every
>> >> >>>> two
>> >> >>>> seconds. I have tried your suggestions but didn't
change
>> something.
>> >> >>>>
>> >> >>>> What I have also discovered is that the clicks are not
passing
>> >> >>>> through
>> >> >>>> my
>> >> >>>> software. Testing a sine wave and using a spectrum
analysis in
>> real
>> >> >>>> time,
>> >> >>>> sndpeek, clicks don't show up there. It seems they
are coming
>> >> >>>> directly
>> >> >>>> to my
>> >> >>>> monitors (headphones)
>> >> >>>>
>> >> >>>> Thanks a lot
>> >> >>>>
>> >> >>>>
>> >> >>>> Len Ovens wrote
>> >> >>>>> On Mon, 18 Dec 2017, georgnk wrote:
>> >> >>>>>
>> >> >>>>>> I can also select my sound card without
qjackctl and Jackd.
>> >> >>>>>> Pure data can see my input s and outputs
directly. Then I go
>> audio
>> >> >>>>>> test
>> >> >>>>>> play
>> >> >>>>>> the sine wave , wait a while, I move frequency
up and
>> down,clicks
>> >> >>>>>> start
>> >> >>>>>> and
>> >> >>>>>> never stop.
>> >> >>>>>
>> >> >>>>> If these are random clicks, that sounds like sync
issues. Some
>> >> >>>>> things
>> >> >>>>> to
>> >> >>>>> try:
>> >> >>>>> - set pulse default and alternate sample rate to
48000
>> >> >>>>> - turn off HDA audio either in bios or in pulse:
>> >> >>>>> pactl unload-module module-udev-detect
>> >> >>>>> pactl unload-module module-alsa-card
>> >> >>>>> (note that if pulse can see any audio
card directly,
>> >> >>>>> it may choose to sync from that one even
if you are
>> >> >>>>> not using it)
>> >> >>>>> - try different sample rates, in particular both
44100 and
>> >> >>>>> 48000. It may be that alsa is under the
impression
>> >> >>>>> it can set sample rate when that is not
the case.
>> >> >>>>>
>> >> >>>>> I have not seen in this thread any meantion of the
web interface
>> >> >>>>> that
>> >> >>>>> the
>> >> >>>>> motu AVB series interfaces normally have, so I am
guessing this
>> is
>> >> >>>>> not
>> >> >>>>> one
>> >> >>>>> of these boxes. Motu's support in the past with
Linux has be
>> >> >>>>> notoriously
>> >> >>>>> bad until the AVB series, so you may have something
that will
>> not
>> >> >>>>> work
>> >> >>>>> with Linux properly... as in, it is USB2.0
compliant so far as
>> >> sound
>> >> >>>>> transfer is concerned, but expects a provided blob
to do device
>> >> >>>>> setup.
>> >> >>>>> The
>> >> >>>>> AVB series uses a web based setup tool that is OS
agnostic.
>> >> >>>>>
>> >> >>>>> --
>> >> >>>>> Len Ovens
>> >> >>>>> www.ovenwerks.net
>> >> >>>>>
>> >> >>>>> _______________________________________________
>> >> >>>>> Linux-audio-user mailing list
>> >> >>>>
>> >> >>>>
Linux-audio-user@.linuxaudio
>> >> >>>>
>> >> >>>>>> >>
>>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> --
>> >> >>>> Sent from:
>> >> >>>>
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>> >> >>>> _______________________________________________
>> >> >>>> Linux-audio-user mailing list
>> >> >>>>
>> >> >>
>> >> >>
Linux-audio-user@.linuxaudio
>> >> >>
>> >> >>>>> >>
>>> _______________________________________________
>> >> >>> Linux-audio-user mailing list
>> >> >>
>> >> >>
Linux-audio-user@.linuxaudio
>> >> >>
>> >> >>>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Sent from:
>> >> >> http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>> >> >> _______________________________________________
>> >> >> Linux-audio-user mailing list
>> >> >>
>> >>
>> >>
Linux-audio-user@.linuxaudio
>> >>
>> >> >>> >> >
_______________________________________________
>> >> > Linux-audio-user mailing list
>> >>
>> >>
Linux-audio-user@.linuxaudio
>> >>
>> >> >> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-
>> f5.html
>> >> _______________________________________________
>> >> Linux-audio-user mailing list
>> >>
>>
>>
Linux-audio-user@.linuxaudio
>>
>> >>> >>
>> >
>> > _______________________________________________
>> > Linux-audio-user mailing list
>>
>>
Linux-audio-user@.linuxaudio
>>
>> >>
>>
>>
>>
>>
>> --
>> Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
>> _______________________________________________
>> Linux-audio-user mailing list
>>
Linux-audio-user@.linuxaudio
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@.linuxaudio
Hi guys problem with periodic clicks solved with my new
laptop, could be because old usb 3 generation,or don't know
exactly what but with my new laptop everything fixed!
So happy,cheers!
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
15 Jan
15 Jan
5:53 p.m.
Hi everyone,
I know this is an old thread, but apparently this is the most recent
discussion about the MOTU 624 audio interface.
I have found it used for a good price and I would like to ask the people
that own it if it is still a good choice or if they can recommend a better
USB interface with similar features.
As far as I can understand form the above discussion the MOTU 624 works
pretty much out of the box under Linux, but there are some issues with
recent firmware. Also if you connect the ethernet cable you can access the
web app to control all the settings of the card from your browser. Is that
correct?
Thank you,
Marco
Il giorno mer 20 dic 2017 alle ore 15:59 <list(a)achromatopsie.com> ha
scritto:
Hello.
I am away from my computer with the MOTU 624 AVB for the holidays. I'll
make a try when i'll be back.
But i've just checked the firmware pages of MOTU's web site and :
v1.3.2+520 (Release Date 2017-12-13)
A new one as been added few days ago. I've never tried this one.
Is the the firmware you running your card with ?
The change log says :
Added Bios menu
Hmm i'm really wonder what it does, and if it break anything with
Gnu/Linux Os.
Cheers !
On 2017-12-20 02:41, georgnk wrote:
--
|_|0|_|
|_|_|0|
|0|0|0|
Hello thank you for the reply.
The clicks are periodic.well,not strictly periodic but almost every two
seconds. I have tried your suggestions but didn't change something.
What I have also discovered is that the clicks are not passing through
my
software. Testing a sine wave and using a spectrum analysis in real
time,
sndpeek, clicks don't show up there. It seems they are coming directly
to my
monitors (headphones)
Thanks a lot
Len Ovens wrote
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
On Mon, 18 Dec 2017, georgnk wrote:
I can also select my sound card without qjackctl
and Jackd.
Pure data can see my input s and outputs directly. Then I go audio
test
play
the sine wave , wait a while, I move frequency up and down,clicks
start
and
never stop.
If these are random clicks, that sounds like sync issues. Some things
to
try:
- set pulse default and alternate sample rate to 48000
- turn off HDA audio either in bios or in pulse:
pactl unload-module module-udev-detect
pactl unload-module module-alsa-card
(note that if pulse can see any audio card directly,
it may choose to sync from that one even if you are
not using it)
- try different sample rates, in particular both 44100 and
48000. It may be that alsa is under the impression
it can set sample rate when that is not the case.
I have not seen in this thread any meantion of the web interface that
the
motu AVB series interfaces normally have, so I am guessing this is not
one
of these boxes. Motu's support in the past with Linux has be
notoriously
bad until the AVB series, so you may have something that will not work
with Linux properly... as in, it is USB2.0 compliant so far as sound
transfer is concerned, but expects a provided blob to do device setup.
The
AVB series uses a web based setup tool that is OS agnostic.
--
Len Ovens
www.ovenwerks.net
_______________________________________________
Linux-audio-user mailing list Linux-audio-user@.linuxaudio
--
Sent from:
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
1190
days inactive
2520
days old
linux-audio-user@lists.linuxaudio.org
62 comments
15 participants
participants (15)
-
Anders Hellquist -
Bernardo Barros -
Chris Caudle -
David -
georgnk -
LAU Reader -
lau-reader
-
Len Ovens -
list -
list＠achromatopsie.com
-
list＠contacte.xyz
-
Marco Santamaria -
Moshe Werner -
Paul Davis -
Peter P.