2 Bugs: 1.Updating-issue & 2. A/B-loop freezes

[Marcador]

Dear all,

1st off, I'd like to thank all you folks who are making VLC possible.
I am as grateful for you guys here on the forum who are trying their best to help, although some posts here make think some users seem to take all this for granted!

Today, I’m turning to you, as I find two erratic behaviors in VLC for MAC:


BUG 1: When setting an A/B-loop -> decreasing playback-speed causes the loop to become choppy, resp. the loop freezes at playback speed below appr. 80%.

FYI:In “normal” playback-mode (NO loop enabled), this problem does NOT occur. Freezing/chopping only happens in A/B-loop.


BUG 2: VLC doesn’t update. Not a problem per se, however trying to update manually (via the dropdown-menu “VLC media player”), VLC says: “You are using the most current version.”

FYI: This has happened to me before in version 3.0.18. Then, re-installing VLC solved the issue.


ENVIRONMENT
PC: Macbook Pro, 14” - Nov. 2023 (MRX33D/A)
OS: Sonoma 14.5 (most recent OS)
CPU: Apple Silicon M3pro (11 cores/14 core-GPU)
RAM: 18 GB
SSD: 512 GB (of which appr. 195 GB free)

FYI: Laptop is quite new (bought May '24), I set up the machine from scratch (NO MIGRATION from TimeMachine-backup).

VLC:
Version: 3.0.20 (current version on your site should be 3.0.21…?)

FYI:
- Re-starting & deleting preferences = Done, no effect.
- Nightly Build = Not yet tried.
- Auto-update = Tried disabling in settings, no effect.

I studied the FAQ, and the "HowTos"; read the foum-posts as well. Unfortunately, to no avail... Only thing I found was someone having the opposite of my "Update-bug" (albeit, they downgraded to an older version etc.).

Therefore, I am thankful for any help! If you need any further info, just let me know.
However, a disclaimer is in order: I'm "just a user", and not a programmer, thus pls don't get mad at me if I act noob-ly... ;o)

Wishing all of you a relaxing weekend,

Marcador

[fkuehne]

There is no update bug. The .21 update is not enabled on purpose due to regressions we saw, which are not bad enough to pull the update from the website, but significant enough to not give the update to everyone. We are working on a .22 that will be available everywhere.

For the A-B problem, does this happen with all your files or just some? What is the file format so I can try to reproduce?