Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
hw:rme_fireface_ucx [2020/07/14 09:45] – [General] magdesign | hw:rme_fireface_ucx [2020/07/19 16:42] (current) – [Software] magdesign | ||
---|---|---|---|
Line 5: | Line 5: | ||
The [[http:// | The [[http:// | ||
- | Its not officially supported under Linux. | + | Its not officially supported under Linux but works with Ubuntu-Studio. |
===== Software ===== | ===== Software ===== | ||
- | In CC (Class Compliant) mode the RME Fireface UCX works out of the box without having to use a patched kernel or flashing some firmware (tested | + | In CC (Class Compliant) mode the RME Fireface UCX works out of the box without having to use a patched kernel or flashing some firmware (tested |
- | ALSA will see only one channel, but after installing QJackCtl from Ubuntu-Studio installer everything works. | + | ALSA will see only one channel, but after installing QJackCtl from [[https:// |
Listed audio channels in Jack correspond to: | Listed audio channels in Jack correspond to: | ||
Line 21: | Line 21: | ||
- | CH 11 -18 => Adat/Tosink | + | CH 11 -18 => Adat (Tosink) |
You might run some pre-start and post-start scripts from QJackCtl to get rid of some pulseaudio standard routings to the first 2 channels. | You might run some pre-start and post-start scripts from QJackCtl to get rid of some pulseaudio standard routings to the first 2 channels. | ||
- | See here: https:// | + | [[ https:// |
+ | Get working scripts [[ https:// | ||
We figured out that custom routings are only loaded when QJackCtl is started from GUI rater than activated from command line only. | We figured out that custom routings are only loaded when QJackCtl is started from GUI rater than activated from command line only. |