[01:11] <Souler> Hi. I need your help. I have the Focusrite Saffire Pro 14 firewire audio interface. It is connected via an adapter to the Thunderbolt port. I don't know how to make it be seen in the system as a sound card and work with the jack server. I am giving you what the system says now:
[01:11] <Souler> www.paste.debian.net/1181175
[01:16] <Eickmeyer[m]> Souler: You're not likely to get much help here. Try #opensourcemusicians or #lau (Linux Audio Users).
[01:17] <oerheks> hmm It's not just you! paste.debian.net is down.
[01:17] <OvenWerks> if you take the www off the front it works for me
[01:18] <OvenWerks> Souler: that paste shows the snd_dice module loaded... so your device should show up as an alsa device
[01:19] <OvenWerks> try: cd /tmp && wget https://community.ardour.org/files/adevices.sh && bash ./adevices.sh |pastebinit
[01:20] <OvenWerks> that is all one line
[01:23] <OvenWerks> matrix has vanished :P
[01:23] <wonko> I should setup jack
[01:23] <wonko> I'm trying to avoid doing anything on this PC though
[01:24] <Souler> paste.debian.net/1181180
[01:26] <OvenWerks> Souler: interesting... opps hes gone
[01:27] <OvenWerks> Souler: that paste does not show safire
[01:27] <OvenWerks> I am not sure why
[01:28] <OvenWerks> does it show up if you run ffado-mixer?
[01:29] <Souler> 02:29:43 logginghandler: Could not communicate with the FFADO DBus service...
[01:30] <OvenWerks> Ouch. Ok, I think you have run past my personal experience with firewire devices
[01:32] <OvenWerks> I do have an audiofire 12 which works fine, but it uses a different kernel module and a PCIe FW card.
[01:32] <OvenWerks> I have heard that dice based devices may not work as well with the alsa drivers.
[01:33] <OvenWerks> If you are using studio-controls you can try turning the alsa drivers off and use the original ffado drivers. Do note that after turning them off you need to reboot for the actual change to work.
[01:35] <Souler> How to do it?
[01:35]  * OvenWerks is assuming you are running on ubutnustudio
[01:36] <wonko> OvenWerks: what are your buffer sizes and number of periods for that FW device?
[01:39] <Souler> At the moment the system does not see my device properly. Qjackctl doesn't see him either. I don't know what the buffers will be yet.
[01:39] <OvenWerks> wonko I have tried various. For watching utube I normally run 1024/3
[01:39] <wonko> Oh, so not impressively better than a USB device?
[01:39] <OvenWerks> wonko I have had it to 32.
[01:40] <wonko> 3?
[01:40] <wonko> because that's a damn sight better than I can do with this Komplete Audio
[01:40] <wonko> I can do 128/3 but xruns happen
[01:40] <wonko> 256/3 was way more stable
[01:40] <wonko> of course that was on the old system
[01:41] <wonko> I haven't tried on this one, maybe I will
[01:41] <wonko> because I see you can pick up something like the M-Audio Firewire 410 for like $40 and if that's supported that might be a good option.
[01:51] <wonko> On the other hand, this is a little alarming: https://linuxmusicians.com/viewtopic.php?t=21332
[01:51] <wonko> FireWire is slowly getting dropped out of linux?
[01:52] <wonko> or is that not really happening?
[01:53] <wonko> oh, ok, so not actually anything to worry about.
[01:53] <wonko> after reading to the end. :)
[02:00] <wonko> The AudioFire4 looks really, really nice.
[02:19] <Eickmeyer[m]> wonko: FireWire isn't being dropped from the kernel (yet), but manufacturing of FireWire devices has ceased.
[03:06] <OvenWerks> wonko: Just for your information. I was playing around with my AF12 and when using the alsa drivers my minimum frame size was 256/2 anything lower (128/3) and jack would not start.
[03:08] <OvenWerks> wonko: then I switched to using the ffado drivers and now I can run the af12 at 32/2 and so far (10min) no xruns
[03:11] <OvenWerks> wonko: the ffado devs are still active. The ALSA devs however, seem to have stopped short on their quest to include FW devices.
[03:15] <OvenWerks> wonko: fw devices are easier to use as alsa devices for sure, the port names are what we are used to (system:capture_1, etc). FFADO drivers give me: irewire_pcm:0014860268b568f1_Unknown_in
[03:15] <OvenWerks> opps missed the f  :P
[03:17] <OvenWerks> what is worse is that is input1 but input 2 is Unknown0_in and Unknown11_in is a midi port :)
[03:18] <OvenWerks> wonko: however, If I use jack_connect to connect to system:playback_1, it does connect to the right place
[03:22] <OvenWerks> wonko: so those are the pluses and misuses of FW with alsa or ffado
[03:47] <OvenWerks> I would have to say that it is too bad firewire audio is no longer made, certainly with the ffado drivers I get fewer xruns (1 in 50 minutes) at 32/2 than I have with any alsa device on this system (and this OS) with my ice1712 based PCI card at 64/2
[06:25] <Eickmeyer[m]> I finally backported studio-controls 2.1.0 to the PPA. Can't believe I hadn't done it yet.
[06:28] <OvenWerks> Eickmeyer[m]: I wondering why I only had 2.0.26
[06:31] <OvenWerks> Hmm, maybe because back ports was turned off?
[06:32] <Eickmeyer[m]> ooops, wrong channel.
[06:34] <OvenWerks> Souler: You missed some of what I said above
[06:35] <OvenWerks> Souler: I played around a bit with my FW device and Jack and found that when using the ALSA modules for it The lowest latency I could do was 256/2
[06:36] <OvenWerks> However when I switched to the FFADO modules I have been running for 4 and a half hours at 32/2 with only one xrun.
[13:43] <wonko> Now that I know more than I did when I started this journey I'm extra bummed that FW has taken a back seat to USB which is significantly inferior for low latency audio purposes.
[13:45] <wonko> I fouond an AudioFire4 for $100 and a TI based FW card will run me about $40-50. That's not bad at all.
[14:00] <Souler> Hi. Hope you can help me solve my problem. I have a firewire audio interface. It is connected via an apple firewire / thunderbolt adapter to a ThinkPad W541 computer with Debian Buster. I cannot run it myself. The system says such errors: http://paste.debian.net/1181175
[14:00] <Souler> One interesting thing is happening. I still have Windows on my computer. All the drivers are well installed and the interface starts and works, gets up. If I switch back to Debian later it still works and it starts working on Linux too, it connects normally to Jack Server and works fine. When I shut down my computer and then choose Debian again, it doesn't work again. It seems Windows is bringing the interface to a certain
[14:00] <Souler> functional state and linux is catching it, but linux alone is not able to bring it to that state. Can you help me to configure my computer so that the interface works on linux from start to finish?
[14:47] <wonko> It sounds like the driver under linux isn't initializing the device properly. You may have to chase the driver author(s) down about that one there is likely nothing we can do.
[15:30] <Souler_Lab> Ok. Thank you for your interesing.
[17:38] <OvenWerks> souler doesn't stay around long enough for me to answer
[18:36] <wonko> There, just bought an AudioFire4
[18:37] <wonko> Won't get to use it until after we move, but that's fine. :)
[21:21] <wash70> Hey so I used ubuntu studio installer but want to uninstall, is there an easy way to do this or am I better off just reinstalling my os?