15 Feb
2014
15 Feb
'14
3:10 a.m.
Hi Daniel,
I notice that I cannot help you without enough logs with which I can
realize what happens.
At lease, 'verbose' options for aplay/arecord, '#' nodes in
/proc/asound/cardX and dmesg.
Additionally, would you please add 'LANG=C' when you get output from
software.
I cannot read Spanish language...
hi, it does not work.
Try in following steps:
1. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16
(I expected you receive 'Available formats' output)
2. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16 -f (here the format,
maybe S32_LE)
(I expected you receive 'rate is not accurate' output)
3. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16 -f (the same above) -r
(got rate)
(I expected it will run correctly.)
I hope you to do these test when killing pulseaudio. The way is here:
https://wiki.ubuntu.com/PulseAudio/Log
Regards
Takashi Sakamoto
o-takashi(a)sakamocchi.jp
5 May
5 May
3:49 a.m.
New subject: Call for testing (final): ALSA driver for some firewire devices
Hi Takashi
I am testing your FFADO and ALSA drivers for a ProjectMix I/O. My goal is
to get the hardware running in Ardour3 with both a firewire interface and
MIDI controls working. I hope this is possible presently.
My configuration:
Ubuntu 14.04 (recently upgraded to get kernel 3.13 for your ALSA driver)
Installed the 3.11 firewire ALSA driver and the latest SVN FFADO driver
I have disabled PulseAudio as described
Firewire:
Your ffado-mixer opens and recognizes the ProjectMix, but I am not able to
see any reaction to the ffado-mixer sliders on the ProjectMix hardware.
ALSA:
I installed the modules with dkms. ALSA appears to identify the ProjectMix
but I am not able to route sound through aplay or arecord. I am not able to
verify MIDI to or from the ProjectMix.
Output: aplay -l
Output: /proc/asound/card1/firewire/clock
Output: /proc/asound/card1/firewire/firmware
Output: /proc/asound/card1/formation
Output: /proc/asound/card1/firewire/meter
Output: /proc/asound/card1/midi0
Output: /proc/asound/card1/pcm0c/info
Results of aplay -D hw:ProjectMix test.wav:
arecord -D hw:ProjectMix -c 8
arecord -D hw:ProjectMix -c 8 -f S32_LE
arecord -D hw:ProjectMix -c 8 -f S32_LE -r 8000
arecord -D hw:ProjectMix -c 8 -f S32_LE -r 48000
In addition to PCM streaming, I have tried monitoring the ProjectMix for
MIDI events using gmidimonitor:
gmidimonitor did not generate any midi events.
I would appreciate any help you can give me.
Regards,
Matt
--
View this message in context:
http://linux-audio.4202.n7.nabble.com/Call-for-testing-final-ALSA-driver-fo…
Sent from the linux-audio-dev mailing list archive at Nabble.com.
10:11 a.m.
New subject: Call for testing (final): ALSA driver for some firewire devices
Hi Matt,
(May 05 2014 12:49), M Murdock wrote:
I am testing your FFADO and ALSA drivers for a
ProjectMix I/O. My goal is
to get the hardware running in Ardour3 with both a firewire interface and
MIDI controls working. I hope this is possible presently.
My configuration:
Ubuntu 14.04 (recently upgraded to get kernel 3.13 for your ALSA driver)
Installed the 3.11 firewire ALSA driver and the latest SVN FFADO driver
I have disabled PulseAudio as described
Thanks for your trial. At first, I want to confirm which revision of
codes you use. What is the latest commit in your local repository for
ALSA drivers and which revision of FFADO you use?
Firewire:
Your ffado-mixer opens and recognizes the ProjectMix, but I am not able to
see any reaction to the ffado-mixer sliders on the ProjectMix hardware.
Please get logs and report it to me. The 'ffado-mixer' request
'ffado-dbus-server' process to execute I/O from/to devices. So what you
do is to get logs from 'ffado-dbus-server'. Follow this instruction:
1. Close ffado-mixer
2. Open your favorite terminal
3. Kill processes of 'ffado-dbus-server' because 'ffado-mixer' starts
the process with dbus help
$ killall ffado-dbus-server
4. run ffado-dbus-server with verbose option
$ ffado-dbus-server -v 6
5. run 'ffado-mixer'
It doesn't matter to run it by GUI/CUI
6. read outputs from 'ffado-dbus-server' in the terminal
ALSA:
I installed the modules with dkms. ALSA appears to identify the ProjectMix
but I am not able to route sound through aplay or arecord. I am not able to
verify MIDI to or from the ProjectMix.
In ALSA side, logs are output in /var/log/syslog. So If you have
problems, please refer to the file.
ProjectMix I/O (and Firewire 1814) can change its number of PCM channels
according to which digital interfaces are selected for input/output.
So unless you don't know the rule, 'plughw' instead of 'hw' will be
your
help. Like:
aplay -D plughw:ProjectMix /dev/urandom
arecord -D plughw:ProjectMix /dev/null
If you want to switch digital interfaces for input/output, please use
amixer/alsamixer:
$ amixer -c 1
Simple mixer control 'Clock Source',0
Capabilities: enum
Items: 'Internal with Digital Mute' 'Digital' 'Word Clock'
'Internal'
Item0: 'Internal'
Simple mixer control 'Digital Input Interface',0
Capabilities: enum
Items: 'S/PDIF Optical' 'S/PDIF Coaxial' 'ADAT Optical'
Item0: 'S/PDIF Coaxial'
Simple mixer control 'Digital Output Interface',0
Capabilities: enum
Items: 'S/PDIF Coaxial' 'ADAT Optical'
Item0: 'S/PDIF Coaxial'
Simple mixer control 'Sync Status',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
MIDI functionality may work but there is an issue for Firewire 1814. So
I guess ProjectMix I/O also has this issue because these devices are
similar. For this issue, please see '2.Data rate for MIDI substream' in
this post:
[alsa-devel] A Restriction and rest of issues for this patchsets
http://mailman.alsa-project.org/pipermail/alsa-devel/2014-April/075912.html
Finally, I reccomend you to subscribe/post ffado-devel because there are
some testers and users of this device.
https://lists.sourceforge.net/lists/listinfo/ffado-devel
Regards
Takashi Sakamoto
o-takashi(a)sakamocchi.jp
6:21 p.m.
New subject: Call for testing (final): ALSA driver for some firewire devices
ffado-dbus-server.out
<http://linux-audio.4202.n7.nabble.com/file/n90825/ffado-dbus-server.out>
Hi Takashi,
I was able to perform more tests (still with PulseAudio disabled).
Takashi Sakamoto wrote
I followed your request for logging ffado-dbus-server output. Attached is
the debug file captured with the following:
ffado-dbus-server -v 6 &> /tmp/ffado-dbus-server.out
I started ffado-mixer, played with most of the analoge input sliders,
auxiliary sliders, output sliders, and muted/unmuted channels. I also
manually adjusted some of the faders on the ProjectMix. The
ffado-dbus-server was then killed.
I was able to confirm that the headphone volume works through the ProjectMix
hardware when listening to random noise.
Takashi Sakamoto wrote
I was able to record and to play back using aplay and arecord and the
"plughw:ProjectMix" device. This is great! I didn't see any logs in
syslog
for ALSA.
I admit that I don't know the difference between "hw:ProjectMix" and
"plughw:ProjectMix". For instance, how should I start jackd (I use
qjackctl). Should I use the alsa or firewire driver in qjackctl? Which
device should I specify, hw:ProjectMix or plughw:ProjectMix?
Takashi Sakamoto wrote
Hi Matt,
(May 05 2014 12:49), M Murdock wrote:
*FFADO*: version.h shows "PACKAGE_VERSION 2.1.9999-2504"
svn log --limit 1 shows:
------------------------------------------------------------------------
r2504 | jwoithe | 2014-05-03 08:57:38 -0400 (Sat, 03 May 2014) | 1 line
README: some initial editting of device status information in preparation
for the release of FFADO 2.2
------------------------------------------------------------------------
*ALSA*: git diff HEAD^ HEAD shows the following
diff --git a/sound/firewire/amdtp.c b/sound/firewire/amdtp.c
index e573f25..29291e4 100644
--- a/sound/firewire/amdtp.c
+++ b/sound/firewire/amdtp.c
@@ -418,7 +418,7 @@ static void amdtp_write_s16(struct amdtp_stream *s,
Takashi Sakamoto wrote
I am testing your FFADO and ALSA drivers for a
ProjectMix I/O. My goal
is
to get the hardware running in Ardour3 with both a firewire interface and
MIDI controls working. I hope this is possible presently.
My configuration:
Ubuntu 14.04 (recently upgraded to get kernel 3.13 for your ALSA driver)
Installed the 3.11 firewire ALSA driver and the latest SVN FFADO driver
I have disabled PulseAudio as described
Thanks for your trial. At first, I want to confirm which revision of
codes you use. What is the latest commit in your local repository for
ALSA drivers and which revision of FFADO you use? Firewire:
Your ffado-mixer opens and recognizes the ProjectMix, but I am not able
to
see any reaction to the ffado-mixer sliders on the ProjectMix hardware.
Please get logs and report it to me. The 'ffado-mixer' request
'ffado-dbus-server' process to execute I/O from/to devices. So what you
do is to get logs from 'ffado-dbus-server'. Follow this instruction:
1. Close ffado-mixer
2. Open your favorite terminal
3. Kill processes of 'ffado-dbus-server' because 'ffado-mixer' starts
the process with dbus help
$ killall ffado-dbus-server
4. run ffado-dbus-server with verbose option
$ ffado-dbus-server -v 6
5. run 'ffado-mixer'
It doesn't matter to run it by GUI/CUI
6. read outputs from 'ffado-dbus-server' in the terminal ALSA:
I installed the modules with dkms. ALSA appears to identify the
ProjectMix
but I am not able to route sound through aplay or arecord. I am not able
to
verify MIDI to or from the ProjectMix.
In ALSA side, logs are output in /var/log/syslog. So If you have
problems, please refer to the file.
ProjectMix I/O (and Firewire 1814) can change its number of PCM channels
according to which digital interfaces are selected for input/output.
So unless you don't know the rule, 'plughw' instead of 'hw' will be
your
help. Like:
aplay -D plughw:ProjectMix /dev/urandom
arecord -D plughw:ProjectMix /dev/null If you want to switch digital interfaces for
input/output, please use
amixer/alsamixer:
$ amixer -c 1
Simple mixer control 'Clock Source',0
Capabilities: enum
Items: 'Internal with Digital Mute' 'Digital' 'Word Clock'
'Internal'
Item0: 'Internal'
Simple mixer control 'Digital Input Interface',0
Capabilities: enum
Items: 'S/PDIF Optical' 'S/PDIF Coaxial' 'ADAT Optical'
Item0: 'S/PDIF Coaxial'
Simple mixer control 'Digital Output Interface',0
Capabilities: enum
Items: 'S/PDIF Coaxial' 'ADAT Optical'
Item0: 'S/PDIF Coaxial'
Simple mixer control 'Sync Status',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
I was unable to find out where or how to change the PCM channels. alsamixer
exposes options for clock source, digital input interface (S/PDIF or ADAT)
and digital output interface (S/PDIF or ADAT). I thought the PCM interfaces
would refer to the physical input and output channels (analogue streams)
available on the ProjectMix.
Takashi Sakamoto wrote
MIDI functionality may work but there is an issue for
Firewire 1814. So
I guess ProjectMix I/O also has this issue because these devices are
similar. For this issue, please see '2.Data rate for MIDI substream' in
this post:
[alsa-devel] A Restriction and rest of issues for this patchsets
http://mailman.alsa-project.org/pipermail/alsa-devel/2014-April/075912.html
I would like to test the MIDI functionality, but I believe my jackd
configuration needs attention first. Insight into how to configure jackd
properly would be much appreciated.
Regards,
Matt
--
View this message in context:
http://linux-audio.4202.n7.nabble.com/Call-for-testing-final-ALSA-driver-fo…
Sent from the linux-audio-dev mailing list archive at Nabble.com.
8:46 p.m.
New subject: Call for testing (final): ALSA driver for some firewire devices
Hi Matt,
(May 06 2014 03:21), M Murdock wrote:
I meant the 'Digital Input Interface' and 'Digital Output Interface' as
'digital interfaces for input/output'. They're not 'PCM interface'.
When you switch these controls between 'S/PDIF' and 'ADAT', you can see
the differences of PCM channels which your jackd recognizes.
ffado-dbus-server.out
<http://linux-audio.4202.n7.nabble.com/file/n90825/ffado-dbus-server.out>
As long as I can see this log, 'ffado-mixer' correctly communicate with
'ffado-dbus-server'.
*FFADO*: version.h shows "PACKAGE_VERSION
2.1.9999-2504"
svn log --limit 1 shows:
------------------------------------------------------------------------
r2504 | jwoithe | 2014-05-03 08:57:38 -0400 (Sat, 03 May 2014) | 1 line
README: some initial editting of device status information in preparation
for the release of FFADO 2.2
------------------------------------------------------------------------
OK. It's based on r2504. Currently we, FFADO developers parepare for new
FFADO version and this revision includes related modification for README.
*ALSA*: git diff HEAD^ HEAD shows the following
diff --git a/sound/firewire/amdtp.c b/sound/firewire/amdtp.c
index e573f25..29291e4 100644
--- a/sound/firewire/amdtp.c
+++ b/sound/firewire/amdtp.c
@@ -418,7 +418,7 @@ static void amdtp_write_s16(struct amdtp_stream *s,
I expected you to run 'git show' and just show me commit hash. But
according to the 'index' field in this output, I can see HEAD in your
local repository is based on this:
firewire-lib: Fix wrong label for 16 bits Raw Audio data
https://github.com/takaswie/snd-firewire-improve/commit/72c569b8e604cfb6dda…
I can understand you work with recent sources.
I followed your request for logging ffado-dbus-server
output. Attached is
the debug file captured with the following:
ffado-dbus-server -v 6 &> /tmp/ffado-dbus-server.out
I started ffado-mixer, played with most of the analoge input sliders,
auxiliary sliders, output sliders, and muted/unmuted channels. I also
manually adjusted some of the faders on the ProjectMix. The
ffado-dbus-server was then killed.
I was able to confirm that the headphone volume works through the ProjectMix
hardware when listening to random noise.
So in this time, ffado-mixer works fine. I think you failed because
there were several processes of 'ffado-dbus-server'. Usually just one
process can execute I/Os between devices so your 'ffado-mixer'
communicated to one of these processes which cannot execute I/Os.
I was able to record and to play back using aplay and
arecord and the
"plughw:ProjectMix" device. This is great! I didn't see any logs in
syslog
for ALSA.
I admit that I don't know the difference between "hw:ProjectMix" and
"plughw:ProjectMix". For instance, how should I start jackd (I use
qjackctl). Should I use the alsa or firewire driver in qjackctl? Which
device should I specify, hw:ProjectMix or plughw:ProjectMix?
Use hw:ProjectMix for jackd. jackd can automatically adjust the number
of PCM channels, on the other hand aplay/arecord can't.
Simple mixer
control 'Clock Source',0
Simple mixer control 'Digital Input Interface',0
Simple mixer control 'Digital Output Interface',0
Simple mixer control 'Sync Status',0
I was unable to find out where or how to change the PCM channels. alsamixer
exposes options for clock source, digital input interface (S/PDIF or ADAT)
and digital output interface (S/PDIF or ADAT). I thought the PCM interfaces
would refer to the physical input and output channels (analogue streams)
available on the ProjectMix. I would like to test the MIDI functionality, but I
believe my jackd
configuration needs attention first. Insight into how to configure jackd
properly would be much appreciated.
Try to execute in terminal:
$ jackd -r -d alsa -d hw:ProjectMix -r 48000
If your system is configured to authenticate your account for 'rtprio'
priviledge, this line is also available:
$ jackd -R -P 89 -d alsa -d hw:ProjectMix -r 48000
Regards
Takashi Sakamoto
o-takashi(a)sakamocchi.jp
10:33 p.m.
New subject: Call for testing (final): ALSA driver for some firewire devices
Hi Takashi,
You have helped me to confirm that both FFADO and ALSA are working for
internal mixer level control and streaming respectively. I can also confirm
that jackd is working both with the command line configuration and when
initiated through qjackctl.
Now... what can I do to help debug MIDI communication with the ProjectMix?
This is an important feature for me as half of the hardware functionality is
as a control surface.
Regards,
Matt
--
View this message in context:
http://linux-audio.4202.n7.nabble.com/Call-for-testing-final-ALSA-driver-fo…
Sent from the linux-audio-dev mailing list archive at Nabble.com.
6 May
6 May
11:42 a.m.
New subject: Call for testing (final): ALSA driver for some firewire devices
Hi Matt,
(May 06 2014 07:33), M Murdock wrote:
Now... what can I do to help debug MIDI communication
with the ProjectMix?
This is an important feature for me as half of the hardware functionality is
as a control surface.
I'm not sure your ProjectMix I/O has this issue or not because this is
my assumption from behaviour of Firewire 1814. Firewire 1814 and
ProjectMix I/O are quite similar. So at first I ask you to confirm
ProjectMix I/O really has this issue.
If ProjectMix I/O has buffer overflow for MIDI messages, it transmits
packets with discontinuity. ALSA driver can detect it and report it to
syslog:
kernel: [19757.225489] snd-bebob fw1.0: Detect discontinuity of CIP: E8 40
So please confirm to see such logs when sending much MIDI messages to
your ProjectMix I/O.
Thanks
Takashi Sakamoto
o-takashi(a)sakamocchi.jp
22 May
22 May
6:11 p.m.
New subject: Call for testing (final): ALSA driver for some firewire devices
Hi Takishi,
I am pleased to announce that the ProjectMix I/O MIDI works flawlessly using
Makie Control Protocol right through to Ardour 3.5.357 (default package in
Ubuntu 14.04). I use the ProjectMix as a "Mackie Control Universal Pro".
The flying faders jumped as soon as I properly connected
system:midi_capture_1 to "Mackie Control In", and system:midi_playback_1 to
"Mackie Control Out" within Ardour. I have not observed any syslog errors
yet, nor have I seen any XRuns!
I'll provide any logs or output that you would find useful.
Thanks for your input so far...you have made my purchase of a ProjectMix a
successful one!
Matt
--
View this message in context:
http://linux-audio.4202.n7.nabble.com/Call-for-testing-final-ALSA-driver-fo…
Sent from the linux-audio-dev mailing list archive at Nabble.com.
3633
days inactive
3729
days old
linux-audio-dev@lists.linuxaudio.org
7 comments
2 participants
participants (2)
-
M Murdock -
Takashi Sakamoto