Closed spectromas closed 3 months ago
I'll take a deeper look later. Same thing is happening to me but a couple of weeks ago this was working well.
However, there is something bad when setting that property. hardware_node_group
is not a value. It is meant to be replaced by users with the actual value in their systems. I use pro-audio-0
. This value is the node.group
PipeWire property of the main audio interface you're using.
I'll check the documentation because this is probably not clear enough. Even I made the same mistake once. :disappointed:
Where the value is set depends on your system but his command could help you. Search for you main audio interface.
$ pw-cli info all | grep -i node.group
BTW, I don't seem to find the pro-audio-0
group any more. Perhaps this has changed in the last PipeWire releases or my config files are obsolete now.
Have you found the value of this property? Have you managed to make it work?
Ah that makes sense about hardware_node_group
! I did find pro-audio-2
with that command but doesn't appear to make any difference unfortunately and the log looks to be the same as far as I can tell. I think pipewire recently updated to 1.2 so might be something to do with that?
I think pipewire recently updated to 1.2 so might be something to do with that?
In Debian testing, PipeWire was updated to version 1.2 very recently so it's probably this.
I'm checking all this right now.
To me, there is something going on with PipeWire 1.2.0.
Function jack_get_cycle_times
returns wrong values occasionally.
I haven't reported anything as I'm still investigating this.
Thanks for the update @dagargo. I've seen a few different issues popping about this version of pipewire in various places so it does seem that something odd might be happening.
I believe there's a bug in PipeWire since 1.1.83 which makes Overwitch to not work at all due to internal timing issues. I'm still investigating this but I'm pretty sure 1.1.82 woks nicely. I haven't reported anything yet.
I pushed a few commits to address this kind of errors in a better way but I've just realized it crashes when devices are unplugged. I'll take a look at this later.
I pushed a few commits to address this kind of errors in a better way but I've just realized it crashes when devices are unplugged. I'll take a look at this later.
Fixed and pushed.
I found the bug and reported it to the PipeWire team here. It has already been solved. :rocket:
We can leave this open until next version goes out but I've already tested it and works pretty well.
Amazing, thank you! I'll keep an eye out for a pipewire update coming through.
Hi There,
I'm having the same issue; my version of overwitch is through the AUR that was last updated in January. Do I have to build this package from the git repository to get these fixes, or do I have to wait for an update to Pipewire? Thanks.
@Zolani13, you'll definitely need a new PipeWire version. From version 1.1.83 to 1.2.1, all suffer from a bug that produced bat time measurements, which is absolutely needed by Overwitch. The bug is already fixed in its master branch.
Overwitch 1.1 should work. Version 1.2 will only be a refined version with better MIDI timing and support for SysEx.
Just got the pipewire update and I can confirm that overwitch is working again! Thanks again for the help/fixes/investigation.
Thanks for trying this out and reporting.
I'm leaving this open for a few days until PipeWire 1.2.2 reaches Debian testing.
I'll report back against the official release and close this if nothing goes wrong.
Just here to confirm that overwitch is now working with my Digitone, also in EndeavourOS (Arch). Thanks again for the updates
PipeWire 1.2.2 is in Debian testing and is Overwitch is working pretty well.
Thanks for testing this.
This can be closed.
I have previous used overwitch with my digitakt (mk1) on this system so I'm not sure what's changed but I cannot get any sound from it now. Running from the GUI, the status says 'Tuning' and the Overbridge to Jack Ratio grows and grows.
When I run from a terminal I get this, with the last message repeating constantly with the number getting larger each time:
I am on Arch Linux with pipewire. I have tried using "PIPEWIRE_PROPS='{ node.group = hardware_node_group }'" but this didn't make any difference. I am currently using the AUR package for overwitch but I have also tried building from the master branch and the same thing happens in both cases.
Do you have any idea why this might be happening?