Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Bugged playback time reported by foobar (Read 318 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Bugged playback time reported by foobar

This is an error I have had sometimes but had not been able to reproduce it until now (and make captures)

Noticed it because some components or scripts were crashing when the float value was expected to be lower than a safe integer.

The console (%playback_time_seconds%):
- For JSP3: [11:27:24] JSP3 3,1638862116397E+134
- For SMP: [11:20:17] 3.1638862116397002e+134

The status bar (%playback_time%):
- CUI: 3150551671 Wk ...

Playlist: (%playback_time_seconds%):
- CUI: -9223372036854775808

Since the bugged value is provided to CUI and all components and display elements, it is not only a SMP error. I have experienced this at v1.6.17 (win 11)

The file is paused (?) but fb is playing. I am not sure how I reach this point, has happened to me sometimes when playing a file but pausing it too fast (I think).

I don't use any kind of components for loops or things like that.
 

Re: Bugged playback time reported by foobar

Reply #1 –
Why are you using old 1.6.x version? I know Peter found null output related bugs in 2023 and 2024, which I assume are fixed in 1.6.18. Definitely fixed in 2.x series. I think it's highly likely your problem is related to null output.

Re: Bugged playback time reported by foobar

Reply #2 –
That's a good question  ::) , somehow I missed the update on this system. Didn't bother to check, since I'm using 1.6.18 in the other systems, and thought it was already the last one. Thanks for mentioning it.

I don't really know how to trigger the problem, so meanwhile we can suppose that's the bug you mentioned. If I find it at 1.6.18 I will report it.