That being said, the problem here is not only about MKVToolnix. builds (like MPC-HC & MPC-BE), things might become convenient for everyone, more flexible, and perhaps less stressful for Mosu too. The fundamental problem here may be that MKVToolnix is practically a one-person project, not developed by a team.īut it's FLOSS, so if someone starts alt. ![]() The current rounding errors of mkvmerge is less than ideal, although there are workarounds. Given that the rigorous rounding is important for Matroska (which doesn't support ntsc 24000/1001 fps explicitly), Matroska is sometimes too powerful, too complicated, thus tools tend to become complicated & confusing. While MKVToolnix is a respectable project, it's not a secret that its GUI is not known for the most intuitive UI. ![]() If you do font attachments, I'd suggest Version 57 or before to avoid the font-mime-type mess. Generally, too new versions tend to be less reliable than tried and tested older versions, especially, experimental "continuous" builds. Why are you guys avoiding Win10? Privacy concerns, or some kind of compatibility problems? If it's privacy, do you think Linux (migrating to it or using it side by side) is a realistically good option?Īlso, don't just use the "lastest" MKVToolnix blindly. Yeah, let's talk freely here without annoying Mosuįirst off, I was surprised to know there are so many die-hard Win7 users, as I was thinking I was one of only few weirdos who're still using Win7.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |