You noticed very well, and I very much appreciate anybody else looking at my code and verifying what I do here. But:
As resources are sparse I currently direct them to get the successor version (which will use camilladsp as backend) and then, as a next step, solve the whole dependency/packaging mess.
Again, thanks for your input, very much appreciated!
- It was done - mostly due too lack of better knowledge - since day one in this manner. So why change a probably running system? see further points...
- I don't have time and resources to get out a working solution any faster right now. Been facing some rough times recently regarding health... I thought about this whole situation many of times sometimes late at night lying in bed when I couldn't sleep - maybe use flatpaks, or much preferrable to my taste - AppImages... simply did not come around to get to know any of these yet. Trying to set up a venv in the process of installation also seems a bit flaky to me as this would just copy current python version to the venv and then this might break when system libraries cause incompatibilities. Any suggestions to this approach?
- I very much envy your situation where you can put out a statically linked binary with everything contained. Your compiler does that. Would like to have a similar solution to my packaging as well. On top of that, I just build packages for debian/ubuntu based systems. Have received several requests to make packages for Arch or RPM-based distros. Same problem as above - lack of time and knowledge. So a solution that is independent of distor package managers would be very desireable.
As resources are sparse I currently direct them to get the successor version (which will use camilladsp as backend) and then, as a next step, solve the whole dependency/packaging mess.
Again, thanks for your input, very much appreciated!
This worked. Paxor started after pip did its thing. But now, when I try to add the output, I cannot choose the number of channels. It tells me to choose 1 or 2, but the window is empty.Oh, I see. Python version 3.11 is also affected. Next attempt of a fix 🙂
Code:pulseaudio-crossover-rack (1.89) stable; urgency=medium * feature: - fix module installation via pip3 for python versions >= 3.11 -- Jürgen Herrmann <t-5@t-5.eu> Sun, 18 Aug 2023 18:11:50 +0200
again, please provide console output. probably for that PM would be better, to avoid the noise for other people reading here? I don't know, It's a matter of taste. 🙂
As resources are sparse I currently direct them to get the successor version (which will use camilladsp as backend) and then, as a next step, solve the whole dependency/packaging mess.
Again, thanks for your input, very much appreciated!
Is the successor version available yet? I have missed lots the past few years. CamillaDSP under the hood is wise, as the community clearly has embraced DSP and this will undoubtedly help support and development.
Sorry to hear about your health. Mine isn't too good either (mental health) and it keeps surprising me how many things are affected and more difficult. I wish you all the best, with recovery and coping.
paxor console? It hasn't inserted PA modules, so there is no console output yet.again, please provide console output. probably for that PM would be better, to avoid the noise for other people reading here? I don't know, It's a matter of taste. 🙂
It's at least partly mental here as well. Not afraid to admit that.
But back to the topic, no, the successor version is not available yet. It's missing one key component, the calculation of the pipeline for camilladsp. It will be announced in a separate thread probably once it at least has a chance to work for you folks.
But back to the topic, no, the successor version is not available yet. It's missing one key component, the calculation of the pipeline for camilladsp. It will be announced in a separate thread probably once it at least has a chance to work for you folks.
No, i meant output from the linux console when running crossover rack. As you did before. And yes, you're right, lets keep this public.paxor console? It hasn't inserted PA modules, so there is no console output yet.
One more comment: I only do this for packages that are not available as upstream packages anyway. So the chance of bricking a python installation by doing that are - IMHO - very slim. In the odd case it will break anything, I will be here for help, if I am not currently knocked out by health issues 🙂I see you are working around this by using the "--break-system-packages" option. As the name suggests, using this option isn't without risks 🙂 It would be much better to do as pip suggests and create a virtual env. That way you can also specify the exact versions of dependencies, which may make things less dependant on what versions of packages the system repos provide.
Unfortunately it's not quite that simple. These packages (for example scipy) also have dependencies. If the package pip installs needs a newer version of something that was installed with apt, it will happily update it.I only do this for packages that are not available as upstream packages anyway. So the chance of bricking a python installation by doing that are - IMHO - very slim.
Have you considered using some tool for managing a virtual env? Pipenv works well and I think it should exist in the mint repos. I don't know how feasible it is to use it in a deb package though.
Unfortunately that's only for the main camilladsp binary. The gui backend is python, with similar issues as you have. I want to support Linux, mac and windows, and the only way I have found that requires a realistic effort is to use virtual environments using either venv or conda.very much envy your situation where you can put out a statically linked binary with everything contained. Your compiler does that.
I am extremely looking forward to this!As resources are sparse I currently direct them to get the successor version (which will use camilladsp as backend) and then, as a next step, solve the whole dependency/packaging mess.
I still find your approach a billion times better than the alternative(s).
Just nothing beats a simple straightforward interface like the one you're using.
Sigma studio is also a great example of this 🙂
Really sorry to hear about your health, hopefully it will get better.
I wish I could help, I can follow programming on an higher level because I used to program a lot 15-20 years ago.
Unfortunately just because lack of time and other work, that has gone a bit, so many of the important details just go over my head these days.
Alright, some time and energy. I had already messed about a bit with trying to install bits and pieces of python extensions and libraries, so I thought that might interfere with debugging a bit. I have done a clean install of paxor. Then, I added the repository and installed paxor. First startup, it mentioned some missing stuff which was all automatically fixed by pip and then paxor fired up without issue.
I could start a new new file and add an output. And now the output sink has a dropdown menu, which features "built-in audio digital stereo (HDMI)" and "Built-in audio stereo" I must add that I have already gone into raspi-config (the raspberry pi config center for detailed stuff) and have selected pulseaudio instead of pipewire. And that I have set up the config.txt with the correct dt-overlay for my hifiberry DAC8X-hat. However, in both the HDMI and stereo outputs, I get the output channels front-left and front-right.
I could start a new new file and add an output. And now the output sink has a dropdown menu, which features "built-in audio digital stereo (HDMI)" and "Built-in audio stereo" I must add that I have already gone into raspi-config (the raspberry pi config center for detailed stuff) and have selected pulseaudio instead of pipewire. And that I have set up the config.txt with the correct dt-overlay for my hifiberry DAC8X-hat. However, in both the HDMI and stereo outputs, I get the output channels front-left and front-right.
I will run paxor from terminal in a few moments, but I want to sort out what I can think of in terms of getting the right output selected in system before we look into what's going on in paxor.
Hmmm
So the DAC8X is there, but where to select it/its 8 channels.
ivo@raspberrypi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: sndrpihifiberry [snd_rpi_hifiberry_dac8x], device 0: HifiBerry DAC8x HiFi pcm5102a-hifi-0 [HifiBerry DAC8x HiFi pcm5102a-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
So the DAC8X is there, but where to select it/its 8 channels.
Hmmmm, I frustratingly don't rememember the name of the app I used before to change the soundcard in alsa. It doesn't help that my pre-teen daughter is embarassed by a love story in a cartoon she is watching and is singing very loudly to not hear the dialog 😵😉
Code:
ivo@raspberrypi:~ $ pulseaudio-crossover-rack
Starting from terminal is uneventful, as you can see. Type command, enter, boom it works.
I tried making an asound config, but that didn't change anything. Not sure I did enough in the asound config anyway.
Last time I did a fresh install of RPI OS and did the dt-overlay thing, I managed to select pro audio in pulseaudio control. That gave me 8 channels, at least there. I'm puzzled this didn't happen this time. I also didn't need it before, I think. Hmmm. Did I do something differently? I shall think about that during some coffee.
Last time I did a fresh install of RPI OS and did the dt-overlay thing, I managed to select pro audio in pulseaudio control. That gave me 8 channels, at least there. I'm puzzled this didn't happen this time. I also didn't need it before, I think. Hmmm. Did I do something differently? I shall think about that during some coffee.
what does right-clicking the sound icon in the task bar for you? for me it shows the settings, under the tab "hardware" i can set profiles for available devices. exuse the german text, if necessary i can try to get screenshots in english
bottom most - "Profil" here you can switch to multi channel if the device supports it.
another recommendation is to fire up pavucontrol, supposedly it can do similarily. have not tried myself. if you keep on struggling I will get my hands on a rpi, it is probably a must to check out new venv based strategies on non x86 systems anyways. I usually rely on virtualization to test different hardware but emulating arm on x86 is SSSLLLOOOOOOOWWW. so no use. better to spend 40€ for a RPI than to make heat with your x86 processor and indefinitely wait for results. especially as it's still 25 degrees celsius here at noon. 🙂
bottom most - "Profil" here you can switch to multi channel if the device supports it.
another recommendation is to fire up pavucontrol, supposedly it can do similarily. have not tried myself. if you keep on struggling I will get my hands on a rpi, it is probably a must to check out new venv based strategies on non x86 systems anyways. I usually rely on virtualization to test different hardware but emulating arm on x86 is SSSLLLOOOOOOOWWW. so no use. better to spend 40€ for a RPI than to make heat with your x86 processor and indefinitely wait for results. especially as it's still 25 degrees celsius here at noon. 🙂
- Home
- Source & Line
- PC Based
- Pulseaudio Crossover Rack - multi-way crossover design & implementation with linux