

Hey,
thanks for the good work.
Would it be possible to add language code in the filename of downloaded subtitles in front of extension.
For example:
instead of getting
"The.Walking.Dead.S05E02.720p.WEB-DL.2CH.x265.HEVC-PSA.srt"
I would get
"The.Walking.Dead.S05E02.720p.WEB-DL.2CH.x265.HEVC-PSA.en.srt" for English subtitles.
VLC is still able to correctly associate subtitles with played file and I get different subtitles files for different languages (not overwriting each other).
Thanks - Oct 22 2014
thanks for the good work.
Would it be possible to add language code in the filename of downloaded subtitles in front of extension.
For example:
instead of getting
"The.Walking.Dead.S05E02.720p.WEB-DL.2CH.x265.HEVC-PSA.srt"
I would get
"The.Walking.Dead.S05E02.720p.WEB-DL.2CH.x265.HEVC-PSA.en.srt" for English subtitles.
VLC is still able to correctly associate subtitles with played file and I get different subtitles files for different languages (not overwriting each other).
Thanks - Oct 22 2014

Remember position
VLC Extensions by augustbering 25 comments
Greetings, thanks for a great extension (:
Just a question. Would it be possible to make it enabled by default?
So when you play a file, it remembers the position and perhaps when you play the same file again, it could as whether you want to play from beginning or from the last position?
Thanks (: - Jul 24 2014
Just a question. Would it be possible to make it enabled by default?
So when you play a file, it remembers the position and perhaps when you play the same file again, it could as whether you want to play from beginning or from the last position?
Thanks (: - Jul 24 2014
Greetings,
I'm experiencing troubles using "Search by hash" functionality.
I've captured communication using Wireshark and compared it to communication of official openSubtitles searcher (which also uses hash searching function) and found some inconsistencies.
While the official searcher sends movie size of value "2 331 600 371" (which is correct), VLSub
sends <double>65535</double> (possible overflow?). Also the calculated hash is slightly different.
"354a0e589e5aae50" with openSubtitles searcher and
<string>354a0e581362485c</string> with VLSub.
Thanks for the otherwise great extension though :) - May 13 2014
I'm experiencing troubles using "Search by hash" functionality.
I've captured communication using Wireshark and compared it to communication of official openSubtitles searcher (which also uses hash searching function) and found some inconsistencies.
While the official searcher sends movie size of value "2 331 600 371" (which is correct), VLSub
sends <double>65535</double> (possible overflow?). Also the calculated hash is slightly different.
"354a0e589e5aae50" with openSubtitles searcher and
<string>354a0e581362485c</string> with VLSub.
Thanks for the otherwise great extension though :) - May 13 2014