No, that makes no sense. I use JACK (not pipewire) at 44,100 and I
have no problems.
Sample rate conversion is trivial on modern hardware. I would leave
things at 48,000 and ignore the warnings.
You might want to try reconfiguring pipewire's sample rate via its
jack.conf file and maybe pipewire.conf. Setting both to 44,100 might
fix everything. I don't think pw-metadata is the best approach since
that changes things while they are running and I believe it loses your
settings when you shut down. The .conf files change things at startup
and should be more reliable.
Pipewire is too buggy for my tastes. I avoid. JACK is 100% solid.
Ted.
On 8/11/25 7:11 AM, chuck elliot wrote:
I have a piece which contains both midi and audio segments.
When I open the 'Manage Audio Files' dialog, there is a warning
about sample rate mismatches between files (44100Hz) and Jack (48000Hz).
These actually play fine but I assume that things would be better if I
adjust
Jack's settings to match the files, so I do so using "pw-metadata -n 0
clock.force-rate 41000".
(I am using Pipewire's Jack implementation).
Now RG is happy but there is horrendous latency and the audio is
sometimes seconds behind the midi output (CPU=~23%).
This doesn't make sense.
Does it?
TIA,
Chuck.
_______________________________________________
Rosegarden-user mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
_______________________________________________
Rosegarden-user mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
