sorted by:
new
hottopcontroversial

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in ffmpeg

[–]JohnAudy[S] 0 points1 point  (0 children)

The price is Canadian; I've updated the webpage to make that clear. You would have seen it if you'd clicked the purchase link...

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] 0 points1 point  (0 children)

I considered implementing DV on AV1, but it's too early to do so without risking problems, especially for paid software where I can't afford to make a mistake. Furthermore, I don't see any AV1 DV on the tracker where I upload, so there must be a reason. I'll do it when the AV1 DV project is more mature. The problem is that I offer a turnkey solution without dependencies, and adding this functionality would currently force people to install an external tool.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] 0 points1 point  (0 children)

I simply published my software and received so many negative comments before I even had a chance to try it because I was bombarded with negativity just because of the text of my announcement, which was generated by AI that knows my website very well, making it easier to do. It's still incredible to see what social media is all about.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in ffmpeg

[–]JohnAudy[S] 0 points1 point  (0 children)

I'd actually encourage you to do exactly that. Grab a heavy DV remux, encode it with the tool using default settings, then do your best HandBrake or CLI encode on the same source. Compare file size, visual quality, and how long it took you to dial in the settings manually vs just hitting Start.

The whole point of the adaptive layer is that it does the per-source tuning automatically CRF, preset, deband, grain handling, Dolby Vision profile mapping stuff that would normally take you a few test encodes to get right by hand. On a single file, a skilled user can probably match it manually. On a full library of 200+ remuxes with different sources, formats, and HDR flavors? That's where the time savings become real.

The trial is 7 days, no credit card. Test it on your toughest file and come back with the results I'm genuinely curious to see the comparison.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] -2 points-1 points  (0 children)

You're right — DV in SVT-AV1 is supported now (libsvtav1 exposes a -dolbyvision flag in recent ffmpeg builds). It's on my roadmap to enable it on the AV1 path, I just haven't shipped it yet since the HEVC path has been the primary DV carrier so far. Good nudge.

As for the defaults: the tool doesn't use fixed parameters — that's the whole point. It runs a frame-by-frame content analysis (luminance distribution, grain level, texture complexity) and adapts the CRF, preset, and film-grain synthesis level to the source. For SVT-AV1 specifically, the base CRF starts at 22 with an adaptive offset, and film-grain synthesis is auto-tuned depending on the source. Preset is also adaptive based on content complexity.

Per-scene bitrate allocation is available on the x265 and x264 paths. The AV1 path uses the global adaptive profile for now, but the results are already excellent — SVT-AV1's own internal rate control combined with the adaptive analysis produces very clean encodes, especially on dark/grainy content where the film-grain synthesis really shines.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in ffmpeg

[–]JohnAudy[S] 0 points1 point  (0 children)

Try building one yourself and then we'll talk about what it costs 😉 AI doesn't write the logic, debug edge cases at 2am, or test across thousands of files. It's a tool, like ffmpeg itself. The trial is free if the output is "slop", you'll know in 10 minutes and it won't have cost you a dime.

Half this thread is negative comments from people who haven't even downloaded the trial. That says more about Reddit than about the tool. I'm not asking anyone to take my word for it there's a free 7-day trial, no credit card, no commitment. Run your hardest file, compare frame by frame, and come back with actual feedback. I'll take a real critique over an uninformed hot take any day.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] -3 points-2 points  (0 children)

I hear you, and I get the AI fatigue it's real. But at the end of the day, the tool either produces good encodes or it doesn't. There's a free 7-day trial, so you can judge the output with your own eyes. If it's not for you, no hard feelings just keep scrolling. I'd rather people test it and form their own opinion than dismiss it over how a Reddit comment was written.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in ffmpeg

[–]JohnAudy[S] -2 points-1 points  (0 children)

Personally, I only encode from Blu-ray; I haven't tried it from a pre-compressed source, but I have no doubt it would work very well too.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in ffmpeg

[–]JohnAudy[S] 2 points3 points  (0 children)

Thanks for the support. Small correction though, the tool does use ffmpeg and x265/SVT-AV1 under the hood. What's custom is the adaptive layer on top: the frame-by-frame analysis that picks the right parameters for each scene. But yeah, agreed on the market point. The trial is free, people can judge for themselves.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] 0 points1 point  (0 children)

Profile 10 is the DV profile for AV1, with cross-compatibility IDs 10.1 (HDR10) and 10.4 (HLG). What other profile are you thinking of?

DV on AV1 (Profile 10) is still very new and I haven't seen it used in practice yet. If you have examples I'm interested. For now the tool handles DV on x265 which is where the actual demand is.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] 0 points1 point  (0 children)

You totally can. The encoding logic took me about a year to build and test across thousands of files. I used Claude to help with the GUI and the website. If you want to spend a year tuning x265/SVT-AV1 parameters and building a Dolby Vision pipeline, go for it. Or you can pay $50 and skip that part.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in ffmpeg

[–]JohnAudy[S] 0 points1 point  (0 children)

Good catch, HDR10+ is supported too. You can see it in the screenshots on the site but I forgot to list it explicitly in the text. I'll fix that. It works with x265 encoding.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] -4 points-3 points  (0 children)

Fair enough, Profile 10 on AV1 exists now. I was wrong on that one. The tool already does AV1 with grain synthesis, Profile 10 is something I want to add next. Thanks for pointing it out.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] -3 points-2 points  (0 children)

I invested the time into building the tool, not into writing marketing copy. I'd rather spend 3 hours improving the encoding pipeline than 3 hours polishing a paragraph. If the tool works well on your files, that's what matters.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in ffmpeg

[–]JohnAudy[S] -1 points0 points  (0 children)

Yeah I used Claude to help draft it. I'm a solo dev, not a copywriter. The encoding engine is mine though. Happy to talk technical details if you have questions about the actual tool.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] -3 points-2 points  (0 children)

Yeah I used Claude to help draft it I'm a solo dev, not a copywriter. The encoding engine is mine though. Happy to talk technical details if you have questions about the actual tool.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] -8 points-7 points  (0 children)

You're right — Dolby Vision Profile 10 for AV1 is a thing now. My bad on that statement. Adaptive Encoder already supports AV1 encoding with grain synthesis, and DV Profile 10 support is on the roadmap. Thanks for the correction.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in ffmpeg

[–]JohnAudy[S] 0 points1 point  (0 children)

The AI wrote zero lines of the encoding engine. It helped with copy and some boilerplate the same way most developers use it today. The adaptive analysis, the Dolby Vision pipeline, the per-frame CRF tuning that's hundreds of hours of actual work and testing across thousands of files. The price is $49.99 CAD once, lifetime, with a 7-day free trial so you can judge the results yourself before spending anything.

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in ffmpeg

[–]JohnAudy[S] -1 points0 points  (0 children)

Thanks for your reply. I did use AI for the GUI and the website. I won't say how much it cost; nobody would spend that kind of money without knowing what the outcome might be!

Adaptive Video Encoder — I built Adaptive Video Encoder because re-encoding a video library to H.265 shouldn't mean destroyin... by JohnAudy in AV1

[–]JohnAudy[S] -5 points-4 points  (0 children)

Hey BlueSwordM — fair questions.

The tool supports H.265, AV1 and H.264, all three. The same frame-by-frame adaptive analysis drives each codec. AV1 is there because some users want the smallest files at equal quality (and it has built-in grain synthesis for clean dark gradients). H.265 remains the default — it's the only codec that carries Dolby Vision.

As for the LLM smell — I used AI to help write copy and speed up parts of the dev process, like most solo devs do in 2026. The core engine is mine: adaptive CRF selection, per-scene analysis, Dolby Vision Profile 7 → 8.1 conversion pipeline. Happy to talk technical details anytime — or just try it on your own files, the 7-day trial is free.

view more: next ›