Ticket #262 (new bug)

Opened 9 years ago

Last modified 6 years ago

[Focusrite Saffire Pro 10 I/O] jackd does not start with the sample rate different from the last used

Reported by: fice Assigned to:
Priority: waiting for device info Milestone: Indeterminant (need device info)
Component: devices/bebob Version: FFADO 2.0.0
Keywords: Cc:
The device the bug applies to: Focusrite Saffire Pro 10 I/O

Description

Focusrite Saffire Pro 10 I/O: jackd does not start with the sample rate different from the last used, have to restart twice. Have this problem with both ffado 2.0.0 and current svn trunk.

How to reproduce:
1. Start jackd

$ jackd -R -dfirewire -p256 -r48000
jackdmp 1.9.4
...
JACK server starting in realtime mode with priority 60
libffado 2.999.0-1790 built Jan 18 2010 00:41:49

2. Stop jackd with Ctrl+C, wait for the device to reboot.

3. Start jackd with different sample rate

$ jackd -R -dfirewire -p256 -r44100
...
libffado 2.999.0-1790 built Jan 18 2010 00:41:49
<waits 1 min>
firewire ERR: FFADO: Error creating virtual device
Cannot attach audio driver
JackServer::Open() failed with -1
no message buffer overruns
Failed to start server

4. Start jackd again with sample rate of 44100 kHz

$ jackd -R -dfirewire -p256 -r44100
<starts successfully>

Change History

01/18/10 14:28:02 changed by fice

  • device_name set to Focusrite Saffire Pro 10 I/O.

03/27/12 07:14:27 changed by adi

Is that still true? Otherwise, we'd like to close the bug.

03/27/12 16:10:56 changed by jwoithe

From Philippe Carriere on the ffado-devel mailing list:

It looks like what happened with Pro24 and 40 (now solved). But Pro 10 is not a Dice device, is it ?

The component in the ticket is set to "devices/bebob" so I suspect you're probably right. That means that the fix for the DICE devices you mention may not automatically apply here (unless of course the fix was in a layer below the driver and thus is common to multiple devices). Therefore I think we need the original reporter (or someone else who owns a PRO 10) to retest with the current codebase and report back.

04/27/12 07:00:30 changed by jwoithe

  • priority changed from minor to waiting for device info.
  • milestone set to Indeterminant (need device info).

Without further help from a person with access to a Pro10 we can't pursue this ticket further. Changing priority and milestone to indicate that device information is required.