Re: M-audio Audiophile Firewire

Re: M-audio Audiophile Firewire

[Takashi Sakamoto]

Hi,
(CCed to alsa-devel, ffado-devel)

On Oct 22 2016 07:37, Peti Pap wrote:
> Do you have any advice about this soundcard?

I own the unit and work with it on Linux system.

> .... I tried use on Linux Mint (Sarah) 64 bit, and I installed ffado packs,
> and jack too... but still only the blue led lighting, and no any sound. (On
> the Jack "panel" I tried all of the possibble settings)

Please show your environment; at least, kernel version and libffado2.


Regards

Takashi Sakamoto

Re: M-audio Audiophile Firewire

[Takashi Sakamoto]

On Oct 22 2016 08:28, Peti Pap wrote:
> Hi,
>
> Thank you the fast answers. Tomorrow I do - again (umpteen) - clean
install
> and if you can/want help - I try to set up the things with your help.
> Anyway, the "lates time" was last week, and I updated fully my System, and
> I tried to compile the latest ffado2 too. (Unfortunately... I am just a
> "next...next finish-man" on Linux... so not so much analytical thinking I
> have). But here the time 1:24am, so I try to sleep, and after when I
> installed the Mint (or if you have recomendation wich distro is better for
> making music (I wanna use the Tracktion Linux ver.)... but I dont want a
> lot of unnecessary software packs (like in the Ubuntu Studio or KX).... so
> after the installation I'll write again (already... today :) )

Please don't omit address list for CC...

Although your unit (M-Audio AudioPhile FW) is one of units based on
DM1000 and BeBoB firmware, it has a unique quirk related firmware loading.

ALSA bebob driver can handle the quirk partly with an condition;
firmware version 5058 or later is required. So what you should do is to
check the version. If your unit has younger version of firmware, you
need to update it with drivers for old Windows operating system.

In detail, see comment of this patch:
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/firewire/bebob/bebob.c?id=a2b2a7798fb6a5c639189e5c8f608a56fdc7a222


Regards

Takashi Sakamoto

Re: M-audio Audiophile Firewire

[Takashi Sakamoto]

On Oct 22 2016 18:35, Peti Pap wrote:
> My current Windows driver details;
> (M-audio Firewire control panel)
>
> Panel: 5.10.0.5058
> Driver: 5.10.0.5058
> Bootloader: 2003/10/06 10:00:41
> Firmware: 2007/05/04 10:22:12
> Hardware: model: D version: 1
> GUID: 000D-6C03-00D9-5B38

You can use firmware version 5061, too. Anyway, ALSA bebob driver can
drive your unit.

On Oct 23 2016 01:33, Peti Pap wrote:
> I installed:
> Linux Mint 18 64 bit
> Low Latency Kernel 4.8
> Tracktion T5

Aha. You use Tracktion for Linux. I like it.

> In Tracktion -> Settings -> Audio Decives menü I can select between ALSA
> and JACK audio device types
> When I select ALSA I can choose 2 FW audiophile stuff;
> 1. "FW Audiophile, FW Audiophile PCM; direct sample mixing device"
> 2. ""FW Audiophile, FW Audiophile PCM; direct hardware device without any
> conversions"

Good. You can see ALSA PCM nodes for your unit.

> I can enable/disable the channels too (I enabled 1+2 channel) and I
set the
> Default wave output
> The sample rate 48kHz
>
> But still no green light (only the blue LED lighting by the power button),
> and no any sound... :\

When the power LED turns at green color instead blinking, ALSA bebob
driver successfully makes the unit to load firmware.

The rest is to configure routing of internal DSP. Just after loading
firmware, no DSP sources are connected to outputs. For this purpose, you
can use ffado-dbus-server/ffado-mixer (GUI), or
hinawa-maudio-bebob-normal-cui in hinawa-utils (CUI).

https://github.com/takaswie/hinawa-utils

The hinawa-utils is an application of libhinawa.
https://launchpad.net/ubuntu/+source/libhinawa

For example:
$ ./hinawa-maudio-bebob-normal-cui 1 mixer-routing
Arguments for mixer-routing command:
  mixer-routing sink source [value]
    mixer-1/2 [analog-1/2, digital-1/2, stream-1/2, stream-3/4,
stream-5/6] [0, 1]
    mixer-3/4 [analog-1/2, digital-1/2, stream-1/2, stream-3/4,
stream-5/6] [0, 1]
    mixer-5/6 [analog-1/2, digital-1/2, stream-1/2, stream-3/4,
stream-5/6] [0, 1]

$ ./hinawa-maudio-bebob-normal-cui 1 mixer-routing mixer-1/2 stream-1/2 1


Regards

Takashi Sakamoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: M-audio Audiophile Firewire

[Peti Pap]

Excuse me;

"When the power LED turns at green color instead blinking, ALSA bebob
driver successfully makes the unit to load firmware"

The unit already stopped blinking after a basic linux installation (from
the first boot). But no any "green" LED, only(!) the power LED lighting,
but the power LED color is blue.
So, I reinstalled - again - my system, and now I dont know what can I do
:|

Re: M-audio Audiophile Firewire

[Takashi Sakamoto]

On Oct 23 2016 18:03, Peti Pap wrote:
> Excuse me;
> 
> "When the power LED turns at green color instead blinking, ALSA bebob
> driver successfully makes the unit to load firmware"
> 
> The unit already stopped blinking after a basic linux installation (from
> the first boot). But no any "green" LED, only(!) the power LED lighting,
> but the power LED color is blue.
> So, I reinstalled - again - my system, and now I dont know what can I do
> :|

Ah, sorry. It shoud be turns at blue color... When you can see any ALSA
PCM nodes for your unit, the unit loads firmware correctly.


Regards

Takashi Sakamoto

Re: M-audio Audiophile Firewire

[Peti Pap]

Now I restart the system, and the FFADO-Mixer working, there have a lot of
settings, I tried some, but I noticed when I try to play a youtube video or
mp3 the sound is "creak". And when I try to set 48khz, after an m3 playing
always 'recoil' to 44.1
I want use this unit as a simple stereo 48khz sound device, to playing mp3
wav and videos, and recording/make music in Tracktion.


2016-10-23 11:23 GMT+02:00 Takashi Sakamoto <o-takashi@sakamocchi.jp>:

> On Oct 23 2016 18:03, Peti Pap wrote:
> > Excuse me;
> >
> > "When the power LED turns at green color instead blinking, ALSA bebob
> > driver successfully makes the unit to load firmware"
> >
> > The unit already stopped blinking after a basic linux installation (from
> > the first boot). But no any "green" LED, only(!) the power LED lighting,
> > but the power LED color is blue.
> > So, I reinstalled - again - my system, and now I dont know what can I do
> > :|
>
> Ah, sorry. It shoud be turns at blue color... When you can see any ALSA
> PCM nodes for your unit, the unit loads firmware correctly.
>
>
> Regards
>
> Takashi Sakamoto
>

Re: M-audio Audiophile Firewire

[Peti Pap]

Hi again,


I installed now an Ubuntu 16.10 (because this distro can handle ffado 2.3
well), and now almost work the playback (but sometimes a bit noisy, and I
dont know the reason).
When I start the FFADO Mixer from terminal, I get the following messages:

Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
-----------------------------------------------
FFADO Control DBUS service
Part of the FFADO project -- www.ffado.org
Version: 2.3.0-
(C) 2008, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------

1477244892717343:  (ffado-dbus-server.cpp)[ 270] main:  Discovering
devices...
03966254548:  (ffado-dbus-server.cpp)[ 329] main: DBUS service running
03966254588:  (ffado-dbus-server.cpp)[ 330] main: press ctrl-c to stop it &
exit
03966254597: Debug (ffado-dbus-server.cpp)[ 333] main: dispatching...
03970152237: Error (avc_avdevice.cpp)[ 300] supportsSamplingFrequency:
sample rate not supported by input plug
03970268300: Error (avc_avdevice.cpp)[ 300] supportsSamplingFrequency:
sample rate not supported by input plug
03970396280: Error (avc_avdevice.cpp)[ 300] supportsSamplingFrequency:
sample rate not supported by input plug
03971004282: Error (avc_avdevice.cpp)[ 300] supportsSamplingFrequency:
sample rate not supported by input plug
03971128298: Error (avc_avdevice.cpp)[ 300] supportsSamplingFrequency:
sample rate not supported by input plug

(And if I close the mixer GUI, I cant re-open again without killing the
ffado-dbus-server)

Maybe should I - somehow - force the ALSA driver to keep always the 24bit
48000Hz?
Anyway on the mixer I use under the "Mix" tab; Stream 1/2 In.

Regards,

Peter


2016-10-23 12:48 GMT+02:00 Peti Pap <roachkiller44@gmail.com>:

> Now I restart the system, and the FFADO-Mixer working, there have a lot of
> settings, I tried some, but I noticed when I try to play a youtube video or
> mp3 the sound is "creak". And when I try to set 48khz, after an m3 playing
> always 'recoil' to 44.1
> I want use this unit as a simple stereo 48khz sound device, to playing mp3
> wav and videos, and recording/make music in Tracktion.
>
>
> 2016-10-23 11:23 GMT+02:00 Takashi Sakamoto <o-takashi@sakamocchi.jp>:
>
>> On Oct 23 2016 18:03, Peti Pap wrote:
>> > Excuse me;
>> >
>> > "When the power LED turns at green color instead blinking, ALSA bebob
>> > driver successfully makes the unit to load firmware"
>> >
>> > The unit already stopped blinking after a basic linux installation (from
>> > the first boot). But no any "green" LED, only(!) the power LED lighting,
>> > but the power LED color is blue.
>> > So, I reinstalled - again - my system, and now I dont know what can I do
>> > :|
>>
>> Ah, sorry. It shoud be turns at blue color... When you can see any ALSA
>> PCM nodes for your unit, the unit loads firmware correctly.
>>
>>
>> Regards
>>
>> Takashi Sakamoto
>>
>
>

Re: [FFADO-devel] M-audio Audiophile Firewire

[Jonathan Woithe]

On Sun, Oct 23, 2016 at 08:22:32PM +0200, Peti Pap wrote:
> I installed now an Ubuntu 16.10 (because this distro can handle ffado 2.3
> well), and now almost work the playback (but sometimes a bit noisy, and I
> dont know the reason).
> When I start the FFADO Mixer from terminal, I get the following messages:
> 
> Cannot create RT messagebuffer thread: Operation not permitted (1)
> Retrying messagebuffer thread without RT scheduling
> Messagebuffer not realtime; consider enabling RT scheduling for user

This indicates that your user does not have access to the realtime
scheduling features on the system.  While this should not affect the
operation of ffado-mixer (and its related ffado-dbus-server), it will cause
problems if you choose to use the FFADO audio streaming system via jackd's
"firewire" backend.  From the above message I'm not sure if you're doing
this though: the "noisy" playback might still be relating to your use of the
ALSA streaming driver.

On most distributions it is sufficient to add your user to the "audio".

Not having access to the realtime scheduling shouldn't cause ffado-mixer any
problem.  However, just to be sure it's probably worth adding your user to
the audio group to see if that improves the ffado-mixer behaviour.

> -----------------------------------------------
> FFADO Control DBUS service
> Part of the FFADO project -- www.ffado.org
> Version: 2.3.0-
> (C) 2008, Pieter Palmers
> This program comes with ABSOLUTELY NO WARRANTY.
> -----------------------------------------------
> 
> 1477244892717343:  (ffado-dbus-server.cpp)[ 270] main:  Discovering
> devices...
> 03966254548:  (ffado-dbus-server.cpp)[ 329] main: DBUS service running
> 03966254588:  (ffado-dbus-server.cpp)[ 330] main: press ctrl-c to stop it &
> exit
> 03966254597: Debug (ffado-dbus-server.cpp)[ 333] main: dispatching...
> 03970152237: Error (avc_avdevice.cpp)[ 300] supportsSamplingFrequency:
> sample rate not supported by input plug

I'm not sure what would cause this.  Was the device actively streaming audio
at the time you started ffado-dbus-server?  That still shouldn't cause any
issues, but obviously something is amiss.

> (And if I close the mixer GUI, I cant re-open again without killing the
> ffado-dbus-server)

That's strange.  Something seems to be getting hung up somewhere.

Peti: to keep the original thread in alsa-devel on topic, you may like to
subscribe to ffado-devel and start a fresh thread there about the
above ffado-mixer / ffado-dbus-server issues you are seeing.

Regards
  jonathan

Re: [FFADO-devel] M-audio Audiophile Firewire

[Pap Peti]

On 2016-10-24 00:43, Jonathan Woithe wrote:
> On Sun, Oct 23, 2016 at 08:22:32PM +0200, Peti Pap wrote:
>> I installed now an Ubuntu 16.10 (because this distro can handle ffado 2.3
>> well), and now almost work the playback (but sometimes a bit noisy, and I
>> dont know the reason).
>> When I start the FFADO Mixer from terminal, I get the following messages:
>>
>> Cannot create RT messagebuffer thread: Operation not permitted (1)
>> Retrying messagebuffer thread without RT scheduling
>> Messagebuffer not realtime; consider enabling RT scheduling for user
> This indicates that your user does not have access to the realtime
> scheduling features on the system.  While this should not affect the
> operation of ffado-mixer (and its related ffado-dbus-server), it will cause
> problems if you choose to use the FFADO audio streaming system via jackd's
> "firewire" backend.  From the above message I'm not sure if you're doing
> this though: the "noisy" playback might still be relating to your use of the
> ALSA streaming driver.
>
> On most distributions it is sufficient to add your user to the "audio".
>
> Not having access to the realtime scheduling shouldn't cause ffado-mixer any
> problem.  However, just to be sure it's probably worth adding your user to
> the audio group to see if that improves the ffado-mixer behaviour.
>
>> -----------------------------------------------
>> FFADO Control DBUS service
>> Part of the FFADO project -- www.ffado.org
>> Version: 2.3.0-
>> (C) 2008, Pieter Palmers
>> This program comes with ABSOLUTELY NO WARRANTY.
>> -----------------------------------------------
>>
>> 1477244892717343:  (ffado-dbus-server.cpp)[ 270] main:  Discovering
>> devices...
>> 03966254548:  (ffado-dbus-server.cpp)[ 329] main: DBUS service running
>> 03966254588:  (ffado-dbus-server.cpp)[ 330] main: press ctrl-c to stop it &
>> exit
>> 03966254597: Debug (ffado-dbus-server.cpp)[ 333] main: dispatching...
>> 03970152237: Error (avc_avdevice.cpp)[ 300] supportsSamplingFrequency:
>> sample rate not supported by input plug
> I'm not sure what would cause this.  Was the device actively streaming audio
> at the time you started ffado-dbus-server?  That still shouldn't cause any
> issues, but obviously something is amiss.
>
>> (And if I close the mixer GUI, I cant re-open again without killing the
>> ffado-dbus-server)
> That's strange.  Something seems to be getting hung up somewhere.
>
> Peti: to keep the original thread in alsa-devel on topic, you may like to
> subscribe to ffado-devel and start a fresh thread there about the
> above ffado-mixer / ffado-dbus-server issues you are seeing.
>
> Regards
>    jonathan

Re: [FFADO-devel] M-audio Audiophile Firewire

[Pap Peti]

Hi again (and again many thanks),

I think my things still belongs to the 'alsa-devel' topic, because I use 
the 'ffado-mixer' only to 'turn on' my audio input(s)/output(s)

I added my username to the "audio" anyway, and already I wont noticed 
noise (but sometimes the audio 'stream(?)' stuck a ~half second when I 
listen music and e.g.: meanwhile run a long file copy, or come some 
sound from the browser. I think its a 'multi-threaded' problem, and/or 
different audio sampling rate in same time.

So I use to make live records, and do some electric tracks too, but I 
dont feel I need Jack, because ALSA also can work with low latency (at 
least in the Tracktion). And - strange - but I feel on this platform the 
sound quality better than on Windows (with Win10 and the latest Win7 
64bit drivers).

My main problem already only;

After when I turn off the soundcard and/or the laptop, I need to start 
again the ffado-mixer to turning on the channels (default: every channel 
muted, or inactive). I'd appreciate some stuff that resolves the basic 
settings, I only need the 1/2 sreaming out and 1/2 analog input. Thats all.

(sometimes when I restart the system and the soundcard still on power 
(external ps) the settings are retained)

Regards,

Peti


On 2016-10-24 00:43, Jonathan Woithe wrote:
> On Sun, Oct 23, 2016 at 08:22:32PM +0200, Peti Pap wrote:
>> I installed now an Ubuntu 16.10 (because this distro can handle ffado 2.3
>> well), and now almost work the playback (but sometimes a bit noisy, and I
>> dont know the reason).
>> When I start the FFADO Mixer from terminal, I get the following messages:
>>
>> Cannot create RT messagebuffer thread: Operation not permitted (1)
>> Retrying messagebuffer thread without RT scheduling
>> Messagebuffer not realtime; consider enabling RT scheduling for user
> This indicates that your user does not have access to the realtime
> scheduling features on the system.  While this should not affect the
> operation of ffado-mixer (and its related ffado-dbus-server), it will cause
> problems if you choose to use the FFADO audio streaming system via jackd's
> "firewire" backend.  From the above message I'm not sure if you're doing
> this though: the "noisy" playback might still be relating to your use of the
> ALSA streaming driver.
>
> On most distributions it is sufficient to add your user to the "audio".
>
> Not having access to the realtime scheduling shouldn't cause ffado-mixer any
> problem.  However, just to be sure it's probably worth adding your user to
> the audio group to see if that improves the ffado-mixer behaviour.
>
>> -----------------------------------------------
>> FFADO Control DBUS service
>> Part of the FFADO project -- www.ffado.org
>> Version: 2.3.0-
>> (C) 2008, Pieter Palmers
>> This program comes with ABSOLUTELY NO WARRANTY.
>> -----------------------------------------------
>>
>> 1477244892717343:  (ffado-dbus-server.cpp)[ 270] main:  Discovering
>> devices...
>> 03966254548:  (ffado-dbus-server.cpp)[ 329] main: DBUS service running
>> 03966254588:  (ffado-dbus-server.cpp)[ 330] main: press ctrl-c to stop it &
>> exit
>> 03966254597: Debug (ffado-dbus-server.cpp)[ 333] main: dispatching...
>> 03970152237: Error (avc_avdevice.cpp)[ 300] supportsSamplingFrequency:
>> sample rate not supported by input plug
> I'm not sure what would cause this.  Was the device actively streaming audio
> at the time you started ffado-dbus-server?  That still shouldn't cause any
> issues, but obviously something is amiss.
>
>> (And if I close the mixer GUI, I cant re-open again without killing the
>> ffado-dbus-server)
> That's strange.  Something seems to be getting hung up somewhere.
>
> Peti: to keep the original thread in alsa-devel on topic, you may like to
> subscribe to ffado-devel and start a fresh thread there about the
> above ffado-mixer / ffado-dbus-server issues you are seeing.
>
> Regards
>    jonathan

Re: M-audio Audiophile Firewire

[Takashi Sakamoto]

On Oct 27 2016 04:25, Pap Peti wrote:
> I think my things still belongs to the 'alsa-devel' topic, because I use 
> the 'ffado-mixer' only to 'turn on' my audio input(s)/output(s)
> 
> I added my username to the "audio" anyway, and already I wont noticed 
> noise (but sometimes the audio 'stream(?)' stuck a ~half second when I 
> listen music and e.g.: meanwhile run a long file copy, or come some 
> sound from the browser. I think its a 'multi-threaded' problem, and/or 
> different audio sampling rate in same time.
> 
> So I use to make live records, and do some electric tracks too, but I 
> dont feel I need Jack, because ALSA also can work with low latency (at 
> least in the Tracktion). And - strange - but I feel on this platform the 
> sound quality better than on Windows (with Win10 and the latest Win7 
> 64bit drivers).

If you need "sham" latency value, using libffado stuff is suitable to
your aim.

In a point of packet streaming protocol for IEC 61883-1/6 and interrupt
interval of OHCI 1394 context, ALSA bebob driver has minimum value for
PCM frames in one buffer period. Currently tt's 5msec. In detail, see
comment of corresponding code:
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/firewire/amdtp-stream.c#n140

Jackd with firewire backend just displays value convenient to users,
although it's not reasonable in a technical point.


Well, about the noise you heard, I can't re-generate the issue. So we
could judge it depending on environment. Do you explain more details?
Which application you use? What OHCI 1394 controller you use? And so on.

> My main problem already only;
> 
> After when I turn off the soundcard and/or the laptop, I need to start 
> again the ffado-mixer to turning on the channels (default: every channel 
> muted, or inactive). I'd appreciate some stuff that resolves the basic 
> settings, I only need the 1/2 sreaming out and 1/2 analog input. Thats all.
> 
> (sometimes when I restart the system and the soundcard still on power 
> (external ps) the settings are retained)

This is not supported in ALSA bebob driver because it can be implemented
in user land. Please use ffado-dbus-server/ffado-mixer or
libhinawa/hinawa-utils.


Regards

Takashi Sakamoto

Re: M-audio Audiophile Firewire

[Pap Peti]

My controller:


*-firewire
                    description: FireWire (IEEE 1394)
                    product: XIO2200A IEEE-1394a-2000 Controller (PHY/Link)
                    vendor: Texas Instruments
                    physical id: 0
                    bus info: pci@0000:06:00.0
                    version: 01
                    width: 32 bits
                    clock: 66MHz
                    capabilities: ohci bus_master cap_list
                    configuration: driver=firewire_ohci latency=32 
maxlatency=4 mingnt=2
                    resources: irq:19 memory:f1c04000-f1c047ff 
memory:f1c00000-f1c03fff


...summerize:

- If the system work with ALSA driver, the latency minimum 5ms. (and 
where/how can I check the current/real value?)

Anyway I cant use the Sakamoto's utils, I downloaded and installed from 
a package, but not any manual with that. I dont know how can I start 
that stuff and configure in terminal. So only the Jack controller 
remember my settings (and save)?


Regards



On 2016-10-27 01:47, Takashi Sakamoto wrote:
> On Oct 27 2016 04:25, Pap Peti wrote:
>> I think my things still belongs to the 'alsa-devel' topic, because I use
>> the 'ffado-mixer' only to 'turn on' my audio input(s)/output(s)
>>
>> I added my username to the "audio" anyway, and already I wont noticed
>> noise (but sometimes the audio 'stream(?)' stuck a ~half second when I
>> listen music and e.g.: meanwhile run a long file copy, or come some
>> sound from the browser. I think its a 'multi-threaded' problem, and/or
>> different audio sampling rate in same time.
>>
>> So I use to make live records, and do some electric tracks too, but I
>> dont feel I need Jack, because ALSA also can work with low latency (at
>> least in the Tracktion). And - strange - but I feel on this platform the
>> sound quality better than on Windows (with Win10 and the latest Win7
>> 64bit drivers).
> If you need "sham" latency value, using libffado stuff is suitable to
> your aim.
>
> In a point of packet streaming protocol for IEC 61883-1/6 and interrupt
> interval of OHCI 1394 context, ALSA bebob driver has minimum value for
> PCM frames in one buffer period. Currently tt's 5msec. In detail, see
> comment of corresponding code:
> http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/firewire/amdtp-stream.c#n140
>
> Jackd with firewire backend just displays value convenient to users,
> although it's not reasonable in a technical point.
>
>
> Well, about the noise you heard, I can't re-generate the issue. So we
> could judge it depending on environment. Do you explain more details?
> Which application you use? What OHCI 1394 controller you use? And so on.
>
>> My main problem already only;
>>
>> After when I turn off the soundcard and/or the laptop, I need to start
>> again the ffado-mixer to turning on the channels (default: every channel
>> muted, or inactive). I'd appreciate some stuff that resolves the basic
>> settings, I only need the 1/2 sreaming out and 1/2 analog input. Thats all.
>>
>> (sometimes when I restart the system and the soundcard still on power
>> (external ps) the settings are retained)
> This is not supported in ALSA bebob driver because it can be implemented
> in user land. Please use ffado-dbus-server/ffado-mixer or
> libhinawa/hinawa-utils.
>
>
> Regards
>
> Takashi Sakamoto

Re: M-audio Audiophile Firewire

[Takashi Sakamoto]

On Oct 27 2016 23:10, Pap Peti wrote:
> My controller:
>
>
> *-firewire
>                    description: FireWire (IEEE 1394)
>                    product: XIO2200A IEEE-1394a-2000 Controller (PHY/Link)
>                    vendor: Texas Instruments
>                    physical id: 0
>                    bus info: pci@0000:06:00.0
>                    version: 01
>                    width: 32 bits
>                    clock: 66MHz
>                    capabilities: ohci bus_master cap_list
>                    configuration: driver=firewire_ohci latency=32
> maxlatency=4 mingnt=2
>                    resources: irq:19 memory:f1c04000-f1c047ff
> memory:f1c00000-f1c03fff

Not enough to re-generate your issue in my hand. Please inform below 
information to me:
  - applications in your test
  - operations in your test
  - the environment of your test; distribution, kernel version, and so on


Regards

Takashi Sakamoto

Re: M-audio Audiophile Firewire

[Pap Peti]

Okay,

Now I went back to Linux Mint Sarah (18) with Cinnamon window manager (x64)

MY HW:

H/W path         Device      Class          Description 
======================================================= 
                              system         Computer 
/0                           bus            Motherboard 
/0/0                         memory         3834MiB System memory 
/0/1                         processor      Intel(R) Core(TM) i5-2520M 
CPU @ 2.5 /0/100                       bridge         2nd Generation 
Core Processor Family /0/100/2                     display        2nd 
Generation Core Processor Family /0/100/16                    
communication  6 Series/C200 Series Chipset Family 
/0/100/16.3                  communication  6 Series/C200 Series Chipset 
Family /0/100/19        enp0s25     network        82579LM Gigabit 
Network Connection /0/100/1a                    bus            6 
Series/C200 Series Chipset Family /0/100/1b                    
multimedia     6 Series/C200 Series Chipset Family 
/0/100/1c                    bridge         6 Series/C200 Series Chipset 
Family /0/100/1c.1                  bridge         6 Series/C200 Series 
Chipset Family /0/100/1c.1/0    wlp3s0      network        Centrino 
Advanced-N 6205 [Taylor Pea /0/100/1c.3                  bridge         
6 Series/C200 Series Chipset Family /0/100/1c.3/0                
bridge         XIO2000(A)/XIO2200A PCI Express-to-P 
/0/100/1c.3/0/0              bus            XIO2200A IEEE-1394a-2000 
Controller /0/100/1c.4                  bridge         6 Series/C200 
Series Chipset Family /0/100/1c.4/0                generic        MMC/SD 
Host Controller /0/100/1d                    bus            6 
Series/C200 Series Chipset Family /0/100/1f                    
bridge         QM67 Express Chipset Family LPC Cont 
/0/100/1f.2                  storage        6 Series/C200 Series Chipset 
Family /0/100/1f.3                  bus            6 Series/C200 Series 
Chipset Family /0/2             scsi1       storage /0/2/0.0.0       
/dev/cdrom  disk           DVDRAM GT50N

and:

Linux 4.4.0-45-generic x86_64

ffado-dbus-ser 2:2.2.1+svn2

ffado-mixer

DAW: Tracktion 5 (x64) /if I use with ALSA driver, I cant play sounds 
paralell with another applications e.g.: browser - youtube, or any player)

And I cant connect JACK firewire backend with realtime priority.

"

14:51:17.044 D-BUS: JACK server could not be started. Sorry

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
skipping unlock

Tue Nov 1 14:51:16 2016: Starting jack server...

Tue Nov 1 14:51:16 2016: JACK server starting in realtime mode with 
priority 10

Tue Nov 1 14:51:16 2016: self-connect-mode is "Don't restrict self 
connect requests"

Tue Nov 1 14:51:16 2016: ERROR: Cannot lock down 107341338 byte memory 
area (Cannot allocate memory)

Tue Nov 1 14:51:17 2016: ERROR: firewire ERR: FFADO: Error creating 
virtual device

Tue Nov 1 14:51:17 2016: ERROR: Cannot attach audio driver

Tue Nov 1 14:51:17 2016: ERROR: JackServer::Open failed with -1

Tue Nov 1 14:51:17 2016: ERROR: Failed to open server

Tue Nov 1 14:51:19 2016: Saving settings to 
"/home/delest/.config/jack/conf.xml" ...

14:51:25.334 Could not connect to JACK server as client. - Overall 
operation failed. - Unable to connect to server. Please check the 
messages window for more info.

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
skipping unlock*"*

So, I think maybe the JACK make me less CPU usage in the DAW , and/or I 
can play sound from another source too, in each time. But if I can solve 
theese problems with ALSA, thats also okay for me :) Regards Peti
On 10/28/2016 03:30 AM, Takashi Sakamoto wrote:
> On Oct 27 2016 23:10, Pap Peti wrote:
>> My controller: *-firewire                    description: FireWire 
>> (IEEE 1394)                    product: XIO2200A IEEE-1394a-2000 
>> Controller (PHY/Link)                    vendor: Texas Instruments 
>>                    physical id: 0                    bus info: 
>> pci@0000:06:00.0                    version: 01                    
>> width: 32 bits                    clock: 66MHz                    
>> capabilities: ohci bus_master cap_list                    
>> configuration: driver=firewire_ohci latency=32 maxlatency=4 mingnt=2 
>>                    resources: irq:19 memory:f1c04000-f1c047ff 
>> memory:f1c00000-f1c03fff 
> Not enough to re-generate your issue in my hand. Please inform below 
> information to me:  - applications in your test  - operations in your 
> test  - the environment of your test; distribution, kernel version, 
> and so on Regards Takashi Sakamoto 

Re: M-audio Audiophile Firewire

[Pap Peti]

UPDATE:

jackd2         2:1.9.11~201 amd64

and my audio.conf:

# Provided by the jackd package.
#
# Changes to this file will be preserved.
#

@audio   -  rtprio     99
@audio   -  memlock    unlimited
@audio   -  nice      -10

(I added my username to the audio group)

Now the Qjack can start with firewire driver and realtime

An example:


1. Start Qjack (Driver: firewire, Sampe Rate: 48kHz, Realtime, Server 
Prefix: jackd)
2. Start Tracktion T5

Now the Messages / Status "output" is:

16:34:42.619 Statistics reset.

16:34:42.636 ALSA connection change.

16:34:42.645 D-BUS: Service is available (org.jackaudio.service aka 
jackdbus).

16:34:45.949 D-BUS: JACK server is starting...

Tue Nov 1 16:34:42 2016: Starting jack server...

Tue Nov 1 16:34:42 2016: JACK server starting in realtime mode with 
priority 10

Tue Nov 1 16:34:42 2016: self-connect-mode is "Don't restrict self 
connect requests"

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
skipping unlock

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
skipping unlock

16:34:45.994 ALSA connection graph change.

16:34:46.036 D-BUS: JACK server was started (org.jackaudio.service aka 
jackdbus).

Tue Nov 1 16:34:45 2016: Saving settings to 
"/home/delest/.config/jack/conf.xml" ...

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_SPDIFIn L_in'

Tue Nov 1 16:34:45 2016: New client 'firewire_pcm' with PID 0

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_SPDIFIn R_in'

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_LineIn L_in'

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_LineIn R_in'

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_MidiIn 1_in'

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_SPDIFOut L_out'

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_SPDIFOut R_out'

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_LineOut1 L_out'

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_LineOut1 R_out'

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_LineOut2 L_out'

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_LineOut2 R_out'

Tue Nov 1 16:34:45 2016: graph reorder: new port 
'firewire_pcm:000d6c0300d95b38_MidiOut 1_out'

16:34:48.188 JACK connection change.

16:34:48.191 Server configuration saved to "/home/delest/.jackdrc".

16:34:48.192 Statistics reset.

16:34:48.201 Client activated.

16:34:48.202 Patchbay deactivated.

16:34:48.207 JACK connection graph change.

Tue Nov 1 16:34:48 2016: New client 'qjackctl' with PID 5079

16:35:09.709 ALSA connection graph change.

16:35:09.721 ALSA connection change.

16:35:09.734 JACK connection graph change.

Tue Nov 1 16:35:09 2016: New client 'JuceJackDummy' with PID 5104

Tue Nov 1 16:35:09 2016: Client 'JuceJackDummy' with PID 5104 is out

16:35:11.627 JACK connection graph change.

Tue Nov 1 16:35:11 2016: New client 'JuceJackDummy' with PID 5104

16:35:11.687 ALSA connection graph change.

16:35:11.729 ALSA connection change.

16:35:11.992 ALSA connection graph change.

16:35:12.133 ALSA connection change.

Tue Nov 1 16:35:11 2016: Client 'JuceJackDummy' with PID 5104 is out

16:35:16.858 JACK connection graph change.

16:35:16.947 JACK connection change.

16:35:16.960 JACK connection graph change.

16:35:16.975 ALSA connection graph change.

16:35:17.157 ALSA connection change.

16:35:17.288 ALSA connection graph change.

16:35:17.359 ALSA connection change.

16:35:17.393 ALSA connection graph change.

16:35:17.562 ALSA connection change.

Tue Nov 1 16:35:16 2016: New client 'JUCEJack' with PID 5104

Tue Nov 1 16:35:16 2016: port 'JUCEJack:in_1' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:in_2' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:in_3' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:in_4' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:in_5' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:out_1' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:out_2' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:out_3' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:out_4' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:out_5' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:out_6' created

Tue Nov 1 16:35:16 2016: port 'JUCEJack:out_7' created

Tue Nov 1 16:35:16 2016: Connecting 'JUCEJack:out_1' to 
'firewire_pcm:000d6c0300d95b38_SPDIFOut L_out'

Tue Nov 1 16:35:16 2016: Connecting 'JUCEJack:out_2' to 
'firewire_pcm:000d6c0300d95b38_SPDIFOut R_out'

Tue Nov 1 16:35:16 2016: Connecting 'JUCEJack:out_3' to 
'firewire_pcm:000d6c0300d95b38_LineOut1 L_out'

Tue Nov 1 16:35:16 2016: Connecting 'JUCEJack:out_4' to 
'firewire_pcm:000d6c0300d95b38_LineOut1 R_out'

Tue Nov 1 16:35:16 2016: Connecting 'JUCEJack:out_5' to 
'firewire_pcm:000d6c0300d95b38_LineOut2 L_out'

Tue Nov 1 16:35:16 2016: Connecting 'JUCEJack:out_6' to 
'firewire_pcm:000d6c0300d95b38_LineOut2 R_out'

Tue Nov 1 16:35:16 2016: ERROR: JackGraphManager::Connect different port 
types port_src = 24 port_dst = 12

16:35:19.777 JACK connection graph change.

16:35:19.968 JACK connection graph change.

Tue Nov 1 16:35:19 2016: Disconnecting 'JUCEJack:out_1' from 
'firewire_pcm:000d6c0300d95b38_SPDIFOut L_out'

Tue Nov 1 16:35:19 2016: Disconnecting 'JUCEJack:out_2' from 
'firewire_pcm:000d6c0300d95b38_SPDIFOut R_out'

Tue Nov 1 16:35:19 2016: Disconnecting 'JUCEJack:out_3' from 
'firewire_pcm:000d6c0300d95b38_LineOut1 L_out'

Tue Nov 1 16:35:19 2016: Disconnecting 'JUCEJack:out_4' from 
'firewire_pcm:000d6c0300d95b38_LineOut1 R_out'

Tue Nov 1 16:35:19 2016: Disconnecting 'JUCEJack:out_5' from 
'firewire_pcm:000d6c0300d95b38_LineOut2 L_out'

Tue Nov 1 16:35:19 2016: Disconnecting 'JUCEJack:out_6' from 
'firewire_pcm:000d6c0300d95b38_LineOut2 R_out'

Tue Nov 1 16:35:19 2016: Client 'JUCEJack' with PID 5104 is out

Tue Nov 1 16:35:19 2016: New client 'JUCEJack' with PID 5104

Tue Nov 1 16:35:19 2016: port 'JUCEJack:in_1' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:in_2' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:in_3' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:in_4' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:in_5' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:out_1' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:out_2' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:out_3' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:out_4' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:out_5' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:out_6' created

Tue Nov 1 16:35:19 2016: port 'JUCEJack:out_7' created

Tue Nov 1 16:35:19 2016: Connecting 
'firewire_pcm:000d6c0300d95b38_SPDIFIn L_in' to 'JUCEJack:in_1'

Tue Nov 1 16:35:19 2016: Connecting 
'firewire_pcm:000d6c0300d95b38_SPDIFIn R_in' to 'JUCEJack:in_2'

Tue Nov 1 16:35:19 2016: Connecting 
'firewire_pcm:000d6c0300d95b38_LineIn L_in' to 'JUCEJack:in_3'

Tue Nov 1 16:35:19 2016: Connecting 
'firewire_pcm:000d6c0300d95b38_LineIn R_in' to 'JUCEJack:in_4'

Tue Nov 1 16:35:19 2016: ERROR: JackGraphManager::Connect different port 
types port_src = 5 port_dst = 17

Tue Nov 1 16:35:19 2016: Connecting 'JUCEJack:out_1' to 
'firewire_pcm:000d6c0300d95b38_SPDIFOut L_out'

Tue Nov 1 16:35:19 2016: Connecting 'JUCEJack:out_2' to 
'firewire_pcm:000d6c0300d95b38_SPDIFOut R_out'

Tue Nov 1 16:35:19 2016: Connecting 'JUCEJack:out_3' to 
'firewire_pcm:000d6c0300d95b38_LineOut1 L_out'

Tue Nov 1 16:35:19 2016: Connecting 'JUCEJack:out_4' to 
'firewire_pcm:000d6c0300d95b38_LineOut1 R_out'

Tue Nov 1 16:35:19 2016: Connecting 'JUCEJack:out_5' to 
'firewire_pcm:000d6c0300d95b38_LineOut2 L_out'

Tue Nov 1 16:35:19 2016: Connecting 'JUCEJack:out_6' to 
'firewire_pcm:000d6c0300d95b38_LineOut2 R_out'

Tue Nov 1 16:35:19 2016: ERROR: JackGraphManager::Connect different port 
types port_src = 24 port_dst = 12


Maybe the solution: somehow routing ALSA via JACK, and after I can use 
the DAW with firewire driver, and the others with ALSA in each time?

Regards

Peti


On 11/01/2016 02:54 PM, Pap Peti wrote:
>
> Okay,
>
> Now I went back to Linux Mint Sarah (18) with Cinnamon window manager 
> (x64)
>
> MY HW:
>
> H/W path         Device      Class          Description 
> ======================================================= 
>                              system         Computer 
> /0                           bus            Motherboard 
> /0/0                         memory         3834MiB System memory 
> /0/1                         processor      Intel(R) Core(TM) i5-2520M 
> CPU @ 2.5 /0/100                       bridge         2nd Generation 
> Core Processor Family /0/100/2                     display        2nd 
> Generation Core Processor Family /0/100/16                    
> communication  6 Series/C200 Series Chipset Family 
> /0/100/16.3                  communication  6 Series/C200 Series 
> Chipset Family /0/100/19        enp0s25     network        82579LM 
> Gigabit Network Connection /0/100/1a                    bus            
> 6 Series/C200 Series Chipset Family /0/100/1b                    
> multimedia     6 Series/C200 Series Chipset Family 
> /0/100/1c                    bridge         6 Series/C200 Series 
> Chipset Family /0/100/1c.1                  bridge         6 
> Series/C200 Series Chipset Family /0/100/1c.1/0    wlp3s0      
> network        Centrino Advanced-N 6205 [Taylor Pea 
> /0/100/1c.3                  bridge         6 Series/C200 Series 
> Chipset Family /0/100/1c.3/0                bridge         
> XIO2000(A)/XIO2200A PCI Express-to-P /0/100/1c.3/0/0              
> bus            XIO2200A IEEE-1394a-2000 Controller 
> /0/100/1c.4                  bridge         6 Series/C200 Series 
> Chipset Family /0/100/1c.4/0                generic        MMC/SD Host 
> Controller /0/100/1d                    bus            6 Series/C200 
> Series Chipset Family /0/100/1f                    bridge         QM67 
> Express Chipset Family LPC Cont /0/100/1f.2                  
> storage        6 Series/C200 Series Chipset Family 
> /0/100/1f.3                  bus            6 Series/C200 Series 
> Chipset Family /0/2             scsi1       storage /0/2/0.0.0       
> /dev/cdrom  disk           DVDRAM GT50N
>
> and:
>
> Linux 4.4.0-45-generic x86_64
>
> ffado-dbus-ser 2:2.2.1+svn2
>
> ffado-mixer
>
> DAW: Tracktion 5 (x64) /if I use with ALSA driver, I cant play sounds 
> paralell with another applications e.g.: browser - youtube, or any player)
>
> And I cant connect JACK firewire backend with realtime priority.
>
> "
>
> 14:51:17.044 D-BUS: JACK server could not be started. Sorry
>
> Cannot connect to server socket err = No such file or directory
>
> Cannot connect to server request channel
>
> jack server is not running or cannot be started
>
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
> skipping unlock
>
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
> skipping unlock
>
> Tue Nov 1 14:51:16 2016: Starting jack server...
>
> Tue Nov 1 14:51:16 2016: JACK server starting in realtime mode with 
> priority 10
>
> Tue Nov 1 14:51:16 2016: self-connect-mode is "Don't restrict self 
> connect requests"
>
> Tue Nov 1 14:51:16 2016: ERROR: Cannot lock down 107341338 byte memory 
> area (Cannot allocate memory)
>
> Tue Nov 1 14:51:17 2016: ERROR: firewire ERR: FFADO: Error creating 
> virtual device
>
> Tue Nov 1 14:51:17 2016: ERROR: Cannot attach audio driver
>
> Tue Nov 1 14:51:17 2016: ERROR: JackServer::Open failed with -1
>
> Tue Nov 1 14:51:17 2016: ERROR: Failed to open server
>
> Tue Nov 1 14:51:19 2016: Saving settings to 
> "/home/delest/.config/jack/conf.xml" ...
>
> 14:51:25.334 Could not connect to JACK server as client. - Overall 
> operation failed. - Unable to connect to server. Please check the 
> messages window for more info.
>
> Cannot connect to server socket err = No such file or directory
>
> Cannot connect to server request channel
>
> jack server is not running or cannot be started
>
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
> skipping unlock
>
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, 
> skipping unlock*"*
>
> So, I think maybe the JACK make me less CPU usage in the DAW , and/or 
> I can play sound from another source too, in each time. But if I can 
> solve theese problems with ALSA, thats also okay for me :) Regards Peti
> On 10/28/2016 03:30 AM, Takashi Sakamoto wrote:
>> On Oct 27 2016 23:10, Pap Peti wrote:
>>> My controller: *-firewire                    description: FireWire 
>>> (IEEE 1394)                    product: XIO2200A IEEE-1394a-2000 
>>> Controller (PHY/Link)                    vendor: Texas Instruments 
>>>                    physical id: 0                    bus info: 
>>> pci@0000:06:00.0                    version: 01                    
>>> width: 32 bits                    clock: 66MHz                    
>>> capabilities: ohci bus_master cap_list                    
>>> configuration: driver=firewire_ohci latency=32 maxlatency=4 mingnt=2 
>>>                    resources: irq:19 memory:f1c04000-f1c047ff 
>>> memory:f1c00000-f1c03fff 
>> Not enough to re-generate your issue in my hand. Please inform below 
>> information to me:  - applications in your test  - operations in your 
>> test  - the environment of your test; distribution, kernel version, 
>> and so on Regards Takashi Sakamoto