Strange behavior on timeline

[toomyem]

Hi.

I'm new to Viseron and installed it to try it out. Using docker and app version 3.5.0.
I have three cameras added via go2rtc. Mostly everything works fine. But I noticed strange behavior on timeline page.
When I try to rewind by clicking anywhere on timeline, the preview breaks. I found out that, after clicking, there is http request with year set to 1970, which results with response with no segments, obviously.

When the page is reloaded, the date is correct:

But after clicking on the timeline:

And the response contains no segments, which seems to break preview.

#EXTM3U
#EXT-X-VERSION:6
#EXT-X-MEDIA-SEQUENCE:0
#EXT-X-TARGETDURATION:5
#EXT-X-INDEPENDENT-SEGMENTS
#EXT-X-MAP:URI="/files/segments/dahua/init.mp4"
#EXT-X-ENDLIST

After that nothing works, until I reload the page. This happens for all three cameras.

Moreover, I noticed that time on the preview does not match with timeline:

As you can see, the timeline shows hours between 21 and 22. But on tooltip there is 13:58:51, which is way off.

Maybe there is some stupid mistake in my configuration. Could you direct me what can I check?

Thanks

[roflcoopter]

Thanks for trying out Viseron, and sorry you are having issues.

What does the playlist look like when you reload the page (when playback works)?

Also, what time zone are you in?
The timeline is easily the most complex part of Viseron and there might be some edge case there when calculating the times

[toomyem]

Thanks for answer.

After page reload, the timeline looks good. It properly contains events. But when I am hovering over it, there is this blue horizontal line with timestamp, which follows mouse cursor. And this timestamp seems to be off. Please notice, what timestamps are passed to request:

After reloading the timestamp is 10 digits long and represents correct time. But the request which is sent after clicking on a timeline, has timestamp with only 7 digits, and it indeed is pointing to 1970.

My timezone is set to Europe/Warsaw.

[roflcoopter]

Is the timestamp for the "hover line" wrong even on first load?
It is calculated from the start of the day, same as the time ticks on the timeline so i dont understand how they can differ

[roflcoopter]

Found the bug! To calculate where on the timeline you are clicking, we are using coordinates based on the height of the window.
En specific heights, this calculation falsely identifies the timestamp as a 13-character millisecond timestamp, when it is actually just a normal 10-digit timestamp with a decimal point and two decimals.

Will get back to you when there is a fix available to test.

[roflcoopter]

Having some issues with the build so the release is not fully completed yet

[roflcoopter]

The 3.5.2 release is now complete and includes this fix

[Ne-k]

Hey, it seems like I'm running into the same issue on version 3.5.3 on docker. The only relevent error I can see seems to be
2026-05-11 03:02:12.439 [ERROR ] [viseron.components.ffmpeg.stream.garage_driveway] - [hevc @ 0x5e8a53df8800] The cu_qp_delta 26 is outside the valid range [-26, 25].]