mjhjmtu

To use an audio application requiring jackd-firewire, I have to start up things in the following order:

1. Power up the hardware interface (a Phonic mixing console in my case)


2. Start jackd


3. Start the audio application

Any other order will make the audio application complain about "no jack" so I have to close it and then run the above sequence.

When the hw interface is off, the /dev/fw1 device simply does not exist. Creating /dev/fw1 with mknod does not help - jackd will not start with such a "dead" device.

vs. built-in soundcard

This is in contrast to a built-in soundcard, where the /dev-device is always there when the computer is running.

vs. Pulseaudio

Even pulseaudio configured to use firewire output allows me to turn the hw interface off and back on. Sound will just stop and resume, and the application does not complain (I only tested this with google-chrome playing a movie).

udev

I know how to use udev to start jackd when /dev/fw1 comes to existence. But I still have to exit the audio application in case I forgot to power up the hw ifc prior to starting the application.

My question

Is there a way to let the application believe it can connect to jackd even when jackd does not see a firewire device? Ideally I would like to be able to disconnect the hardware while the application is running without any ill effects, except hearing no sound.