Bug 495225 - playback rate not applied if defined before clicking play
Summary: playback rate not applied if defined before clicking play
Status: CONFIRMED
Alias: None
Product: kasts
Classification: Applications
Component: general (other bugs)
Version First Reported In: 24.08.2
Platform: Flatpak Linux
: NOR minor
Target Milestone: ---
Assignee: bart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-23 08:08 UTC by kde.85zhb
Modified: 2024-11-10 18:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kde.85zhb 2024-10-23 08:08:36 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
the playback rate is not applied if it is defined before launching the podcast

STEPS TO REPRODUCE
1. select a rate (x2.5 to make it clear if it works or not)
2. download a podcast
3. play it

OBSERVED RESULT
4. play rate seems to be 1

EXPECTED RESULT
5. play rate should be same as defined in step 1.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Fedora KDE 40
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
same apply when manually launching a new podcast after one completed.
need to re-select the rate to have the correct rate applied.
did not test if it happen when param "Continue playing next episode after current one finishes" is ticked.
issue happen with it unticked.
Comment 1 bart 2024-11-10 18:00:42 UTC
This is a very annoying thing with all audio backends that are currently supported: advanced audio settings will only apply on an open audio stream.  None of the backends remember settings when no stream is currently active.
I've tried adding some hacks here and there to make most settings be carried over to the next active stream, but it's definitely not exhaustive.