@ skull The URL for eac3to builds is now simply: https://rationalqm.us/eac3to That's consistent with how we manage the other products. You may need to tell videohelp. Thank you. As Curly said, future builds will drop the _mod, e.g., eac3to_3.42.rar Exciting to see. I also let videohelp support know...

Curly wrote: ↑

Sat Dec 02, 2023 11:38 am

Calling Ambassador skull!

Can you please inseminate released 3.41 at videohelp please. Thank you. The changelog is up-to-date.

Absolutely, fine sir. Just sent them an update, they usually respond very quickly. Cheers!

UPDATE: Videohelp page updated with v3.41!

I agree, in principle, but sometimes the old adage of "if it ain't broke, don't fix it" applies, even in situations of (old) dependencies, especially given that latest eac3to_mod version is just ~12MB in size and only contains 10 .DLLs, and runs very lean. However, it would be a nice future goal to ...

Strongly agree, whenever suggesting updated .dll, the source should be mandatory for review. For those particular (2) .dll files, I usually look to StaxRip for newer versions and still the same legacy files in their latest version.

Haha, love it Curly. Always serving the people.

I had a chance to look into the 3D stuff. ... Right call in my opinion and smart to have a " will not be added/fixed " list for reference. If a function or feature already exists in an available tool, especially if it's part of the DG-family, then it should not be duplicated/added to eac3to through...

Yes, tremendous job so far. I'll update videohelp folks about changelog.

Btw, Curly , I noticed the changelog.txt file is not updated to include all the fixes/improvements since v3.36 to v3.40? Any chance you'd be able to update/include that in future or advise what I should tell videohelp to use for changelog? Documentation is always a bug-a-bear. We're still stuck on ...

Had a user ask me in PM what is the rationale for our build numbers/slipstreaming etc. Here is how I answered: This is what Rocky told me. We have so many products with so many different version control/release/documentation setups that it is a nightmare to manage build numbers. Believe me we have ...

I don't know who to contact. Do you want to try? I think the current 3.40 is good to go. Of course lots of work still to do but it is a good working replacement for 3.36. I was sure someone on this forum reached out but they must update themselves if they can find newer versions or something. I'll ...

Nothing will be removed but MKV muxing will be deprecated and not advertised on the splash screen. The muxing support will not be touched. The MKV input stuff will be maintained and bugs fixed as needed. Sounds fair and less confusing this way. Btw, good news, videohelp does seem to have updated ea...

* Added the needed files from the 3.36 distribution. If you'd like to suggest a later version that remains compatible, feel free. Yes, the original libFLAC.dll is very old that came with eac3to, definitely recommend updating if it's going to be included moving forward, just not 64-bit .dll, as it c...

Amen, bro. I think that's a fair argument especially with makemkv being a great option, but in that case, I just think the syntax examples in internal docs and any mention of outputting to .mkv should be removed entirely, just to make it clean, as it uses the very old Haali splitter anyway for the ...

Curly wrote: ↑

Fri Nov 24, 2023 3:00 pm

Thank you for your testing and report, Trunks. Waiting for the other shoe to drop...or, do we now have a good release candidate?

Maybe give 24-48 hours for anyone else to be able to test and then consider good to go?

Curly , something I noticed, worth a quick mention, even if it only ends up being a future improvement to-do. Currently eac3to has some internal documentation and sample syntax when you just execute the program, spits this out, which is great: eac3to_mod v3.40, freeware by madshi.net, assisted by D...

new_guy wrote: ↑

Tue Nov 21, 2023 5:50 pm

The minimum time-threshold concept is dumb, right? Or is it just a UI matter?

This doesn't really seem constructive. What do you mean? It's a smart, desired feature, as several folks have agreed.

Curly wrote: ↑

Tue Nov 21, 2023 2:39 pm

I'm going to sort by duration, and not show playlists shorter than some configurable amount (2 minutes). That should help, yes?

That is a good default minimum value, agreed.

Sherman wrote: ↑

Mon Nov 20, 2023 6:05 pm

skull wrote: ↑

Mon Nov 20, 2023 5:30 pm

I added my 2 cents

Ha ha, an alias!

I made that account many years ago and really didn't even intend to post much, but yes. Now shush!

People have started attacking me over at doom9. Not sure what I did to offend. n e body? B*ndits obviously is passive aggressive due to the ban here previously. I would ignore anyone negative and just post informational-only posts over there. I added my 2 cents to try to steer things the right dire...

So far so good. More tests are needed to be sure, but you did a good job with this one! I see that you've changed the -progressnumbers command, so now the progress bar is only one line, instead of one line per new percent. That's great too, thanks! Regarding this, would it be possible to add -progr...

OK guys, here is a new build 40 test version. * Subtitles sync (may be) fixed. Please let me know if it works and/or I broke anything. Thank you. https://rationalqm.us/misc/eac3to_mod_3.40_test.rar You're amazing Curly! <3 Hope you can take a break and find some time to relax too. Hopefully someone...

We should do something, I agree. Probably issue an error message. Just crashing is low class. Making progress on sups. It is a complicated problem. I have it working perfectly with one stream, but multiple streams collide. Gonna disambiguate using the PID. Take your time. The turtle always bests th...

Try with spaces after 3: eac3to_mod.exe M:\Elemental 2) 3: English.thd 3: English.ac3 -progressnumbers Working fine here. And yes, we merge only when the filenames are the same. Yes, the syntax for eac3to always required the space . Curly , I wonder if there is some internal logic reason for this o...

Thank you, skull , you are quite correct. Not yet, beyond following the threads. When I get this subs issue solved, I'll make a formal release with a change log. Here is a sort of summary: * All bugs affecting HEVC/UHD and seamless branching have been fixed except for subs timing. * An INI file was...

is there actually a kind of changelog of all the changes made per version since overtaking the job from madshi? That is a good idea of course, but probably a lower priority while working on test/beta versions for now. Given the detailed Feature/Fix Requests list , I imagine Curly could do something...