+- Selur's Little Message Board (https://forum.selur.net)
+-- Forum: Talk, Talk, Talk (https://forum.selur.net/forum-5.html)
+--- Forum: A/V Talk (https://forum.selur.net/forum-6.html)
+--- Thread: [INFO] Small tools I wrote,... (/thread-7.html)
Small tools I wrote,... - Selur - 06.05.2017
Mis2x265:
Wrote a small tool to convert the MediaInfo 'Encoding settings' output into an x265 command line.
Windows binaries and the source is available over at: https://github.com/Selur/Mis2x265
Misx264:
Wrote a small application which converts the 'Encoding settings' infos MediaInfo provides into normal x264 cli command line fragments.
Windows binaries and the source is available over at: https://github.com/Selur/Mis2x264
CudaEncoder:
Wrote a small command line tool which uses the old nvcuenc cuda encoder (Windows only, requires NVIDIA drivers < 340.52, since NVIDIA dropped the support in favor for nvcuenc).
Windows binaries and the source is available over at: https://github.com/Selur/CudaEncoder
IdxSubCutter:
Small command line tool to cut idx/sub subtitles based on a 'cut-list'
Windows binaries and the source is available over at: https://github.com/Selur/IdxSubCutter
Subtitle-Speed-Changer:
Small Qt project to change the speed of ttxt/ass/srt subtitles by a factor.
Windows binaries and the source is available over at: https://github.com/Selur/Subtitle-Speed-Changer
avsViewer:
A small Qt based Avisynth script viewer I use in Hybrid
the source is available over at: https://github.com/Selur/avsViewer
MediaInfoRenamer:
A small Qt tool which analyses a file through mediainfo and renames the file by adding some of the output to the file name. (Qt runtime and mediainfo are both required for this. If you use Hybrid you could simply copy the file into the Hybrid folder.)
the source is available over at: https://github.com/Selur/MediaInfoRenamer
-----
I got a few other tools, for which I released the source code, over at github for those interested.
Cu Selur
Ps.: If you have questions about one of these tools or find a bug post here in the forum or the github issue tracker.