Re: [alsa-devel] ALSA Fireworks driver
Doug McLain wrote:
[nostar@iggy firewire]$ cat /proc/asound/cards 3 [AudioFire12 ]: Fireworks - AudioFire12 Echo Digital Audio AudioFire12 v5.0, GUID 0014860fc44a84a6 at fw1.0, S400
[nostar@iggy export]$ aplay -D plughw:AudioFire12 wg.wav aplay: main:660: audio open error: No such file or directory
[nostar@iggy export]$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA NVidia], device 0: ALC1200 Analog [ALC1200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 1: ALC1200 Digital [ALC1200 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0
There is not PCM device for the AF12.
In theory, it shouldn't be possible for the driver to attach to the device without having created the PCM device. Are you sure that you have the latest version of the driver? Where exactly did you get it from? Please check that the fireworks.c file has 2275 lines, like this one: http://git.alsa-project.org/?p=alsa-kprivate.git;a=blob;hb=fireworks;f=sound...
Regards, Clemens
Aha! I had an older version that someone from the ffado list pointed me to. I grabbed the .c and .h file from your link and built them (after defining CSR_IPCR and CSR_OPCR locally, my kernel-dev pkg doesnt have them) and now jack starts and I can record and play from ardour, but only at 44.1Khz, even though I start jackd with -r48000. It looks like 44.1Khz is the default setting the AF12 powers up at, and the alsa driver doesn't know how to change SR yet, is this the case?
I start the device up using ffado to force it into 48K, but then jack will no longer start using the alsa driver until I cycle power on the device.
The driver appears to work good in 44.1K though. Aplay plays wav files using plughw, but not hw.
I also wonder if you can explain to me how to clone just that driver so I can keep up with it correctly using git pull. I'm a little weak on git. I just grabbed the .c and .h files manually and made my own Makefile for standalone module building.
Doug
On 06/17/2011 07:17 AM, Clemens Ladisch wrote:
Doug McLain wrote:
[nostar@iggy firewire]$ cat /proc/asound/cards 3 [AudioFire12 ]: Fireworks - AudioFire12 Echo Digital Audio AudioFire12 v5.0, GUID 0014860fc44a84a6 at fw1.0, S400
[nostar@iggy export]$ aplay -D plughw:AudioFire12 wg.wav aplay: main:660: audio open error: No such file or directory
[nostar@iggy export]$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA NVidia], device 0: ALC1200 Analog [ALC1200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 1: ALC1200 Digital [ALC1200 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0
There is not PCM device for the AF12.
In theory, it shouldn't be possible for the driver to attach to the device without having created the PCM device. Are you sure that you have the latest version of the driver? Where exactly did you get it from? Please check that the fireworks.c file has 2275 lines, like this one: http://git.alsa-project.org/?p=alsa-kprivate.git;a=blob;hb=fireworks;f=sound...
Regards, Clemens
Doug McLain wrote:
It looks like 44.1Khz is the default setting the AF12 powers up at, and the alsa driver doesn't know how to change SR yet, is this the case?
Actually, the driver knows quite well how to change SR, and does this to initialize the device to 44.1 kHz. However, this driver was intended as a prototype, so I didn't bother to implement making the other SRs available to ALSA applications.
FYI I tried #define FIXED_RATE 48000 just to see if I could use the driver at 48K for soem recording sessions today.
This should work if you also change FIXED_RATE_SFC (0...6 = 32/44.1/48/ 88.2/96/176.4/192 kHz).
Aplay plays wav files using plughw, but not hw.
This is to be expected if your .wav doesn't have twelve channels of 32-bit samples.
I also wonder if you can explain to me how to clone just that driver so I can keep up with it correctly using git pull. I'm a little weak on git. I just grabbed the .c and .h files manually and made my own Makefile for standalone module building.
The driver is in a kernel repository because it is part of the kernel; using it with other kernel versions would require back-porting any changes in the kernel API (as you did this with the CSR_ symbols).
Current development is in the firewire-kernel-streaming branch, where the drivers are composed of more files and depend on some changes in the core kernel. There is no easy way of using these with another kernel.
Regards, Clemens
Nice, now I have it up and running with my preferred SR of 48Khz, and it seems to be stable. I figured out the git stuff since the last email I sent. I didn't know how to browse and switch to various branches, so I kept getting the wrong files in sound/firewire.
Thanks for the help, Doug
On 06/21/2011 07:38 AM, Clemens Ladisch wrote:
Doug McLain wrote:
It looks like 44.1Khz is the default setting the AF12 powers up at, and the alsa driver doesn't know how to change SR yet, is this the case?
Actually, the driver knows quite well how to change SR, and does this to initialize the device to 44.1 kHz. However, this driver was intended as a prototype, so I didn't bother to implement making the other SRs available to ALSA applications.
FYI I tried #define FIXED_RATE 48000 just to see if I could use the driver at 48K for soem recording sessions today.
This should work if you also change FIXED_RATE_SFC (0...6 = 32/44.1/48/ 88.2/96/176.4/192 kHz).
Aplay plays wav files using plughw, but not hw.
This is to be expected if your .wav doesn't have twelve channels of 32-bit samples.
I also wonder if you can explain to me how to clone just that driver so I can keep up with it correctly using git pull. I'm a little weak on git. I just grabbed the .c and .h files manually and made my own Makefile for standalone module building.
The driver is in a kernel repository because it is part of the kernel; using it with other kernel versions would require back-porting any changes in the kernel API (as you did this with the CSR_ symbols).
Current development is in the firewire-kernel-streaming branch, where the drivers are composed of more files and depend on some changes in the core kernel. There is no easy way of using these with another kernel.
Regards, Clemens
FYI I tried #define FIXED_RATE 48000 just to see if I could use the driver at 48K for soem recording sessions today. It built, loaded, and successfully changed the device to 48K, and jack starts fine, but no audio makes it from ardour to the device. Also, aplay fails:
aplay -D plughw:AudioFire12 wg.wav aplay: main:660: audio open error: Input/output error
Everything goes back to normal when I change the source back to 44100.
On 06/17/2011 07:17 AM, Clemens Ladisch wrote:
Doug McLain wrote:
[nostar@iggy firewire]$ cat /proc/asound/cards 3 [AudioFire12 ]: Fireworks - AudioFire12 Echo Digital Audio AudioFire12 v5.0, GUID 0014860fc44a84a6 at fw1.0, S400
[nostar@iggy export]$ aplay -D plughw:AudioFire12 wg.wav aplay: main:660: audio open error: No such file or directory
[nostar@iggy export]$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA NVidia], device 0: ALC1200 Analog [ALC1200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 1: ALC1200 Digital [ALC1200 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0
There is not PCM device for the AF12.
In theory, it shouldn't be possible for the driver to attach to the device without having created the PCM device. Are you sure that you have the latest version of the driver? Where exactly did you get it from? Please check that the fireworks.c file has 2275 lines, like this one: http://git.alsa-project.org/?p=alsa-kprivate.git;a=blob;hb=fireworks;f=sound...
Regards, Clemens
participants (2)
-
Clemens Ladisch -
Doug McLain