Fuck yeah. Who doesn’t like good news? 🎉 Also, really surprised they got it working well enough on RDNA 2 to plan to release it, that’s just gravy on the cake.

I am not patronising and that was not my intent. Read whatever you want into it of course, I can’t stop you.

Well, sure, and I appreciate your sanguinity haha! I just main support, and felt your question deserves a proper answer.

I am planning on answering when I’m at a computer, as well, because I actually do have a matrix server set up with Synapse and MAS. Quick question though, when you ask how it works, do you mean the actual backend, or are you asking if the performance/user experience is good?

Don’t get me wrong, suggestions are appreciated, but you’re answer is absolutely typical of a Stack overflow “huhuh well don’t do it wrong then” comment. You could have, for example, said you don’t use Synapse but this is why you like Continuwuity. (edit: not prescribing speech, giving an example of how your comment could have read better)

As well, I take issue with the idea that people can only ask for help in sanctioned forums. This is a self-hosting community, after all; I am here not only to learn but to share what I learn, which I thought was the whole point.

What is this, StackOverflow? You didn’t answer their question and instead just told them to use a different solution.

I thought we’ve (indirectly?) observed dark matter with Webb? https://www.youtube.com/watch?v=HLedYv1lzQ0

Did I totally misunderstand what Anton was saying?

Ick. I’ve only had a few cups of pre-ground coffee in my life, because they were uniformly awful. I’d believe dead cockroaches are why, for sure.

Ah, I’ll put in a zoom feature, that’s a good idea!

Remind me of the hardware you’re running on? 22 hours for a 4k HDR movie sounds about in the ballpark for converting on CPU. I’ve just switched to Linux (Mint, not Cachy) and I think there’s an issue with detecting GPU on Linux, so this’d track (or you have Precision Mode enabled) - if you see “libx265” or “libx264” in the top right, you’re on CPU. I’m looking into this one.

Can I ask which version you downloaded? I’ll look into the DVTools/MP4box issue.

Also, yes, I removed the codec and container selection boxes - it’s HEVC/MKV by default unless you go for “Compatibility Mode” in which case you get H.264/MP4. “Preserve AV1” of course preserves AV1 which is incompatible with MP4 so they’re mutually exclusive.

So… How’s it working? 😅 (Just realised it’s been a while since I’ve touched HISTV and this came to mind, I’ve been working on my business and day job)

I watched Quantum Leap with my dad when I was a kid. You’re gonna try and tell me I’m not writing this reply on Ziggy?

Ah, what version did you try? This is due to issues with the renderer, but I just got this fixed by disabling GPU drawing for the form last night. Give 2.5.9 a go 😊

Hey, I haven’t made a full post about this yet, but I thought you’d like to know: v2.5.0 is out, and it implements quietvoid’s tools for DoVi support! https://github.com/obelisk-complex/histv-universal/releases

It’ll even handle DV 5 and 7 😊

You totally can though. It’s a common phrase.

Sweet as, lmk if you have any questions or run into any issues! 😊

Whether it’s an alternative depends on what you use Handbrake for. HISTV can’t convert ISO or rip discs, it only converts video files. If you just use Handbrake to get smaller videos, HISTV will work for you without having to use more controls than it would take to launch the space shuttle 😅

Thanks for your patience, took me a minute to get my VM up and running so I could test the Flatpak, but it’s working and with no permissions: https://github.com/obelisk-complex/histv-universal/releases/tag/v2.3.6

By which I mean “Replace source” works out of the box with no permissions; in order for “Place next to source” output to work, you’ll have to give permission to the folder via flatseal (as you noted).

I’ve got a few more updates to make - I’m simplifying the UI a little, and I’m adding the ability to transcode AV1 - and then I’ll work on getting it building entirely offline in order to submit it to the Flathub store for review. Great suggestion, I appreciate it! (👉ﾟヮﾟ)👉

Ah-ha, thanks for the update on Docker! Saves me going down that rabbit hole 😅

On the files on the NAS: yep, that’s by design. My files are across the WAN, not LAN, so I built it to stage remote files locally before transcoding. It currently pulls a file, transcodes it, and moves it wherever you chose for output. This does mean that going over a network is slow, because you have to wait for the staging and cleanup before doing another file. That’s deliberately conservative though; I wanted to avoid saturating networks in case the network operator takes exception to that sort of thing. A secondary benefit is that the disk space required for operations is just twice the size of the source file - very low chance of having to pause a job because the disk monitoring detected there’s no room.

I’ll look at putting in an override that disregards the network and treats remote files as local for you!

Haha thanks! You mean, support them for output, as well as being able to convert from? Last night I outlined adding an “Auto” option for container, which would keep the source container if possible, but the controls I’ve exposed vs the ones I haven’t are a conscious choice, to maximise player compatibility for the outputs without the user having to know anything about codecs, containers, encoders, their hardware, or quality settings. I’m deliberately keeping the options to a minimum because I didn’t want to make Handbrake 😅

As to why I chose these codecs: h264 works on devices from 15+ years ago, and HEVC is compatible back to 2015-16. AV1 is 2020 onwards and requires GPU decoding; that’s too new and resource-intensive for my goals with HISTV.

I’ll think about how I could pull this off though. Perhaps a “lite” mode that keeps the original codec and container, or an “auto” mode for codec dropdown too. I think I like the second one better: lets you mix and match keeping container or codec or both, without adding any real complexity to the options.

Hahaha baby steps! But I’ll look at it; if nothing else I think it would be very funny to have the dev equivalent of Jar Jar Binks end the format war by accident (which I say as just a joke; I of course have no idea how complex the issue actually is).

Edit: Damn dude, you weren’t kidding about the challenge. You’re right that HISTV won’t work for DoVi 5 in its current state - “Fundamental to FFMPEG” does kinda mean “fundamental to HISTV”, being that it’s basically just a clever wrapper around FFMPEG. That said, if your tooling is ready, I’ve got a plan to integrate it. The philosophy with HISTV is to preserve whatever we can and fall back gracefully as far as we have to if we can’t preserve the current profile, which your tools slot into like they were made for it (Rust Gang represent (👉ﾟヮﾟ)👉).

Ah, then the real slowness is going to come from having them on a spinning disk HDD. For friends, 3Mbps or 4Mbps target bitrate should be plenty, with the 2x multiplier should be enough to preserve detail. No need to touch anything else, you don’t need precision mode for it. Maybe start with 3 and that on just one episode, and see how you go - if you find yourself noticing it looks blocky, bump up to 4Mbps and you’ll be golden.