| OvenWerks | s/in/unin/ | 00:41 |
|---|---|---|
| BrianHechinger[m | Heh, i wish. Sadly I'll never get the native instruments stuff to work on Linux. Got close, but they use bome midi wish installs a driver so no wine. | 12:28 |
| BrianHechinger[m | Also, until proton fully supports DXR 1.1 i still need Windows for Cyberpunk. | 12:29 |
| BrianHechinger[m | s/wish/which/ | 12:35 |
| BrianHechinger[m | If you ever do have audio software that does run under wine WineASIO is awesome. | 12:36 |
| BrianHechinger[m | Oh, damn, this FW card is even better than expected. | 12:44 |
| BrianHechinger[m | looking for it after popping it in I it shows up as two devices. | 12:44 |
| BrianHechinger[m | 08:00.0 FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller (rev 08) | 12:44 |
| BrianHechinger[m | 09:00.0 FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller (rev 08) | 12:44 |
| BrianHechinger[m | So, I wondered and.... | 12:45 |
| BrianHechinger[m | IOMMU Group 27:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/119d23a3f94dbc9cabf29c2d44c1bf02969e11b3) | 12:45 |
| BrianHechinger[m | each fw chip (there are two on the card) is in its own IOMMU group. Which means one can be passed through to windows. :-D | 12:45 |
| Eickmeyer | BrianHechinger[m: the distribution of WineASIO as a binary is illegal, but is fine if compiled as a source. See https://wiki.ubuntu.com/wineasio | 13:53 |
| Eickmeyer | Hence, we can never carry it. | 13:54 |
| BrianHechinger[m | winetricks installs it so that's good enough I guess? | 13:54 |
| Eickmeyer | I mean, sure. | 13:55 |
| Eickmeyer | The source itself is fine to distribute since the sources are redistributable. The binary is made from incompatible licenses and is not redistributable, so it's a mess. | 13:56 |
| BrianHechinger[m | That does sound like a mess. And kinda pointless if your ask me. | 13:58 |
| Eickmeyer | It is, but a lot of it is because Steinberg doesn't understand the meaning of open source. | 14:03 |
| BrianHechinger[m | Ugh. What a hassle. Time for some self building binary technology. 😜 | 14:08 |
| Eickmeyer | They also licensed the VST3 SDK as non-redistributable without express permission from them OR if licensed as GPL3, developer discretion. Debian took the stance of "You can't do that", so we can't have VST3 plugins in the repos. | 14:10 |
| Eickmeyer | In all honesty, Steinberg can't do that, they needed to pick one route or the other, they can't have their cake and eat it too. | 14:11 |
| BrianHechinger[m | Right? | 14:13 |
| Eickmeyer | Tons of discussion on this has happened at #lad:libera.chat, so falktx in all his wisdom reverse-engineered the vst3 SDK (clever, eh?) | 14:15 |
| BrianHechinger[m | Yeah, that was a good way to handle it | 15:12 |
| BrianHechinger[m | Ok, so now I have two firewire devices on my computer up to the point where the VM starts. Is there a way to get jack (via studio controls) to use only one of them or am I best off setting the VM to start and boot so the second device is captured by the VM before jack starts so it's not visible to jack? | 15:13 |
| BrianHechinger[m | Oh, I can blacklist it in studio-controls. Is that good enough? | 15:14 |
| Eickmeyer | Should be, but I'm no expert on FW. OvenWerks, if you're around ^ ? | 15:15 |
| BrianHechinger[m | nope, doesn't look like that does the right thing. | 15:15 |
| BrianHechinger[m | jack came up with the audiofire4 instead of the saffire pro | 15:16 |
| BrianHechinger[m | I wonder if it just picks the first one from the list | 15:16 |
| BrianHechinger[m | because the AF4 is on port 0 and the saffire on port 1 | 15:17 |
| BrianHechinger[m | Ah ha! | 15:18 |
| BrianHechinger[m | that does indeed appear to be the case | 15:18 |
| OvenWerks | BrianHechinger[m: Huh, well that explains things maybe. | 16:24 |
| OvenWerks | BrianHechinger[m: I note that I have /dev/fw0 and /dev/fw1 | 16:25 |
| OvenWerks | You may recall, I had no luck getting one of my cables to work and got another. The difference being That the first was 6pin and the second 8pin. | 16:26 |
| OvenWerks | Right now with the way jackdbus is called, it just uses the default fw device (/dev/fw0) | 16:28 |
| BrianHechinger[m | Explains what things? | 16:28 |
| OvenWerks | It could well be that the 6pin jack is connected to /dev/fw1 | 16:28 |
| BrianHechinger[m | This new card only has 8 pin connectors | 16:29 |
| OvenWerks | So maybe if I had set jackdbus to to use fw1 my 6pin cable would have worked | 16:29 |
| BrianHechinger[m | Oh | 16:29 |
| BrianHechinger[m | I don't think so | 16:29 |
| OvenWerks | Mine has two 8pin and one 6 pin | 16:29 |
| BrianHechinger[m | There are 4 ports | 16:29 |
| BrianHechinger[m | And I'm plugged into the middle two | 16:30 |
| BrianHechinger[m | So it's signing fw0 to the first device it finds and few to the second | 16:30 |
| BrianHechinger[m | s/signing/assigning/ | 16:31 |
| BrianHechinger[m | s/signing/assigning/, s/few/fw1/ | 16:31 |
| BrianHechinger[m | Which is typical Linux behavior | 16:31 |
| OvenWerks | Studio-controls is not set up to handle any fw device exceopt fw0 (or rather it doesn't pick any device) | 16:32 |
| BrianHechinger[m | Ok, that tracks with what i saw then. Whichever device is fw0 is what controls attaches jack to | 16:32 |
| BrianHechinger[m | Which is perfectly acceptable behavior for my needs | 16:33 |
| OvenWerks | I did think at the time I would like to be able to pick which device to use but, not having two devices to play with, wasn't sure how to go about that or how to test it. | 16:34 |
| OvenWerks | However, if my card actually puts the 6pin plug on fw1, I may be able to test that. | 16:35 |
| BrianHechinger[m | It's only going to do that if there is another device getting assigned to fw0 | 16:35 |
| OvenWerks | At least now that the alsa fw module seems to work(ish), it should show up there. | 16:36 |
| OvenWerks | huh | 16:36 |
| OvenWerks | not helpful then | 16:36 |
| BrianHechinger[m | ffado-test ListDevices (or whatever it's called I'm in my phone) should list the devices it sees without the need for Jack or ALSA talking to the device. | 16:37 |
| BrianHechinger[m | s/in/on/ | 16:37 |
| BrianHechinger[m | https://paste.ubuntu.com/p/CWBdHqPgxh/ | 16:45 |
| BrianHechinger[m | it doesn't matter which ports they're plugged into, at the firewire layer it instantiates them in the order it finds them. | 16:45 |
| BrianHechinger[m | so it's always Port 0 and Port 1 | 16:45 |
| OvenWerks | when I use ffado-test ListDevices I only see one device but I still see fw0 and fw1. That is whay I am wondering if the fw0 and 1 are a part of the PCIe card rather than the devices. | 17:12 |
| OvenWerks | Or it may be that fw0 is the card and fw1 is the device... | 17:13 |
| OvenWerks | what do you see for ls /dev/fw* | 17:13 |
| BrianHechinger[m | Hmm, it appears I've forgotten to enable the ssh server on my desktop so I'll have to check later. | 17:14 |
| OvenWerks | No worries. | 17:14 |
| BrianHechinger[m | I could have sworn i enabled that. Weird. | 17:14 |
| BrianHechinger[m | Haha, nevermind. I just haven't connected from my phone since before we moved so it still had the old IP. 🤣 | 17:15 |
| BrianHechinger[m | ➜ ls /dev/fw* /dev/fw2 /dev/fw3 | 17:16 |
| BrianHechinger[m | That makes sense because they other two ports are currently passed through to the VM so they "don't exist" from Linux's point of view currently | 17:17 |
| OvenWerks | Ah, ok so one for the card and one for the device | 17:18 |
| BrianHechinger[m | But, that tells me that all physical ports on the card get a fw device no matter if something is connected | 17:18 |
| BrianHechinger[m | Which makes sense for a bus device | 17:18 |
| BrianHechinger[m | No, those are for the card | 17:18 |
| BrianHechinger[m | Not the device | 17:18 |
| OvenWerks | I wonder what happens when they are chained. | 17:18 |
| BrianHechinger[m | I don't have any 6 to 6 cables handy so unfortunately i can't check | 17:19 |
| sunjam[m] | Anyone else kept their 20.04 install and tried updating themselves to 22.04 and kde? I'd like to adjust my sources and keep my install if I can pull it off. Switching away from Ubuntu studio specific repos is fine if that helps. Thoughts appreciated. | 17:21 |
| OvenWerks | the ffado backend is supposed to be able to handle chains of up to three devices I think. | 17:21 |
| OvenWerks | sunjam[m]: | 17:22 |
| BrianHechinger[m | sunjam: upgrading felt like a bad idea so i did a fresh install | 17:22 |
| BrianHechinger[m | But I'm setup to do that easily | 17:22 |
| OvenWerks | sorry I think going from 20.04 to 22.04 is not recomended because of the DE change | 17:23 |
| BrianHechinger[m | Oh, yeah, i was on 21.10 (which had the new DE) and still felt like upgrading was a bad idea. 😜 | 17:23 |
| BrianHechinger[m | OvenWerks: I just powered down the VM so the other two ports came back: | 17:26 |
| BrianHechinger[m | ls /dev/fw* | 17:27 |
| BrianHechinger[m | /dev/fw0 /dev/fw1 /dev/fw2 /dev/fw3 | 17:27 |
| sunjam[m] | <OvenWerks> "sorry I think going from 20.04..." <- I understand. That is why I'm asking | 17:28 |
| BrianHechinger[m | OvenWerks: is enabling backports a reasonably idea? | 17:29 |
| OvenWerks | BrianHechinger[m: Thanks. Not sure what I can do with that | 17:29 |
| OvenWerks | BrianHechinger[m: in what context? | 17:29 |
| BrianHechinger[m | OvenWerks: Basically, I think what I'm getting at is using /dev/fw* as the options in studio-controls isn't going to work. those aren't the actual devices. | 17:30 |
| BrianHechinger[m | OvenWerks: in the context of am I going to suffer for it or will it just be good getting newer stuff if possible? | 17:30 |
| OvenWerks | sunjam[m]: If I was going to try it, I would tend to copy my working partition to a second partition and try with that | 17:30 |
| OvenWerks | BrianHechinger[m: backports is recomended. There are many times where bugs are fixed in new versions but because there are more than bug fixes they can't be SRUed | 17:32 |
| BrianHechinger[m | ok | 17:32 |
| OvenWerks | (studio-controls is one of them) | 17:32 |
| OvenWerks | It is always possible to go back to the release version with muon if you have trouble | 17:33 |
| BrianHechinger[m | weird, I enabled backports but I don't have the new version of controls available | 17:35 |
| OvenWerks | sunjam[m]: I think the best way is to have more than one partition, One for your home directory, one for the the current system and one for the new system. | 17:36 |
| OvenWerks | sunjam[m]: I use 40G partitions for the system and everything else for home. (actually it is more complex than that in my case) | 17:38 |
| OvenWerks | In my case, I keep my home directory quite small and have links to working directories (software, audio projects, documents, etc.) Then after a new install, I copy the home directory (cp -a) into the new partiton and do a double move: mv user user.inst then mv user.old user (I do the move with the DE logged out from a terminal ctr/alt/F2) | 17:44 |
| OvenWerks | Like I said, more complex and maybe not needed. | 17:45 |
| BrianHechinger[m | OvenWerks: 40G is enough? I've been meaning to do that | 18:14 |
| OvenWerks | cfdisk says 39.1g ;) | 19:31 |
| OvenWerks | but I am pretty sure when I made them with the partition manager I used 40000 Mb | 19:32 |
| OvenWerks | BrianHechinger[m: also note that I have added the whole ubuntu build stack and all the extra libs and dev files to build ardour and other stuff but the build directories themselves are on a different partition | 19:34 |
| OvenWerks | not many years ago I used 20g | 19:41 |
| OvenWerks | The extra 20g is mostly to deal with the extra stuff I install. | 19:41 |
| BrianHechinger[m | I'll have to check and see what my issue is | 20:03 |
| BrianHechinger[m | I really miss ZFS | 20:03 |
| BrianHechinger[m | But I'm not thrilled with ZFS on Linux | 20:03 |
| OvenWerks | You could use it for the system and use something else for home | 20:04 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!