apparently with massively long videos, with no timestamp corruption or seek table fuckery, like ACTUALLY massively long videos, VLC dies somewere around the "several hundred hour" mark when trying to get the next frame.

is this a bug or did my hubris exceed VLC's tolerance?

Several hundred hours.
Of video.

Did you and @Rutee07 get together?

Always split into 3gb files. For many reasons I’m not aware, but mainly file system compatibility.

@bagfox yeah but like

it's 300MB, and also btrfs/ext*/ntfs don't have that limit

@Root actually it's like 8300 some hours, almost a year of 16x16 video.

@vigidis Agreed

@Parzi 16x16? What. Why? What are you doing? And why do you think this approach is a good idea? 😟

@vigidis no

@Root because I could. I was trying to push Shotcut to its limits as well. (Shotcut uses a metric fuckton more RAM per frame at 1000 hours over 1 hour, for some reason. The more frames already allocated, the more RAM it eats per new frame added. I think at around 800 hours it began to require 1GB of swap every time I added 1 frame's worth of time to the timeline)

@vigidis it's actually 1FPS, but I see what you're saying. I'm thinking it has something to do with the timestamp in correlation to fetching the frames as they get slower and slower when trying to get frames later in the file.

(also everything i do is boredom repellant lol)

@Parzi you might want to look for work in qa,you seem to have the right mindset :P

What @Voxera said. I'd love to have someone like you on some of my projects.

That being said, I'm surprised VLC has this issue. Historically, it's been the defacto for "properly implemented" if you don't count all of the ffmpeg stuff.

@junon i mean if you wanna hire me lmao

@Voxera qualifications on jobs involving that in my state are high as hell, sadly.

@Parzi Filing bug reports on high profile open source projects can be a great portfolio for a QA position though. We recently hired someone who had no degree, but multiple legit bug reports for ways to make Firefox and AOSP crash or leak memory.

@bittersweet i'm not really that high a skill level, is the thing, and unless it's super obvious it'll be *found* well before I do, just not *fixed* yet

https://trac.videolan.org/vlc/...

Most of the log isn't relevant I think.

VLC is modular and a lot of support comes from non VLC projects depending on build time configuration.