Scott James Remnant wrote:
> The midisport-firmware problem is that fxload uses the wrong environment
> variable to get the device name
If I understood the fxload docs correctly there is a command line
argument to specify the device as well. Could this be used for a
work-around in the midisport-firmware package's udev rules?
Scott James Remnant wrote:
> The midisport-firmware problem is that fxload uses the wrong environment
> variable to get the device name
If I understood the fxload docs correctly there is a command line
argument to specify the device as well. Could this be used for a
work-around in the midisport-firmware package's udev rules?