FallingSnow / h265ize

A node utility utilizing ffmpeg to encode videos with the hevc codec.
MIT License
527 stars 81 forks source link

How i disable the audiostream renaming? #123

Open MeisterKnobi opened 6 years ago

MeisterKnobi commented 6 years ago

Because i have trouble with this function i search for a solution to Disable it. Some files its simple DTS and AC3, like the source, but at most times the 1. audio stream is unnamed (like the source) and the 2. "German DTS DTS blabla (stereo)" but is actually jap and also tagged as it. I'm fine with it that the audiosteams just be unnamend, only to be tagged as eng, jap or ger. is there any option for h265ize thats not listed in the README.md that would help?

FallingSnow commented 6 years ago

That option used to exist but got removed for some reason. Can I suggest trying nmmes-cli. It's the successor to h265ize and offers close to all the features h265ize does but is still in alpha. You should be able to disable the audio title normalization in nmmes-module-normalize with --no-audio-titles.

MeisterKnobi commented 6 years ago

thx i will try it. did you discontinued h265ize? and when yes, why? for me its a verry nice little program, except the little audio title bug.

marshalleq commented 5 years ago

I have to say, I prefer the h265ize to nmmes-cli. It's just that it's simpler and does one thing and the one thing is what I want. I don't need any of that other stuff. And Nmmes seemed a bit confusing to me. h265ize really took off out there, because it's obvious what it does. I wish I was a developer so I could maintain it, hopefully someone will climb on board and help you.

FallingSnow commented 5 years ago

100% agree. nmmes has potential, it was built to be very modular. People would be able to share a single URL to share all encoding settings (even modules :D). It just never matured. It is a half built mess sadly.

I want to eventually replace h265ize with nmmes and have it be even simpler than h265ize is but it's hard to maintain motivation.

@MeisterKnobi I think I responded to this originally, with a big long paragraph of explanation, then my browser crashed and I said f**k that :P

I basically stopped developing h265ize because it was to be replaced nmmes. Unfortunately development just fizzled out.

marshalleq commented 5 years ago

Well I'm glad you did - because lot's of people are looking for this tool and you're the only one that realised that and stepped up and made it. You should see how many people have made docker containers for it, done things like put it in their automated video workflow and such. Actually I've seen guides for doing it in Handbrake that just don't come close to the simplicity and perfection this tool already gets to, even if you do want to replace it! I run mine in a docker. It's not perfect, but it's the best thing out there by far. You really made a name for yourself with this I think! Thanks for what you did already. :D