Is there any option to re-enable this feature? All my subs are in TXT format and it's quite annoying that I need to manually select subs every time...Subtitles and renderer:
* Do not auto-detect .txt files for subtitles
Is there any option to re-enable this feature? All my subs are in TXT format and it's quite annoying that I need to manually select subs every time...Subtitles and renderer:
* Do not auto-detect .txt files for subtitles
Well, the reason is that .txt can be way more than just a subtitle.Hello,
May I ask what are those good reasons? I don't like to use outdated versions, but because of this inconvenient way of loading *.txt subtitles, I did downgrade to 1.1.5. Maybe there is (or there will be) at least possibility of re-enabling loading subtitles by drag-and-drop or from Video menu's Open Subtitle entry after selecting to display "All files"?
// I'm using Windows and Linux versions, but since I found this topic I decided to write here.
This is that __good reason__? I see you just play in Steve Jobs here. This is not a good way so for now I'll downgrade to 1.1.5. Thanks.Well, the reason is that .txt can be way more than just a subtitle.
You will be able to open manually.
Not the right way to speak to us...This is that __good reason__? I see you just play in Steve Jobs here. This is not a good way so for now I'll downgrade to 1.1.5. Thanks.Well, the reason is that .txt can be way more than just a subtitle.
You will be able to open manually.
No, 1.1.7 don't force you to select "all" at all. This is fixed.I've created account only to inform VideoLan that after 4 years of ucing VLC I've just started looking for some other player.
For me new VLC can't open subtitles.
To do that I need to goto Media->AdvancedOpen, choose video file, and change Subtitle Files to *, then choose subtitles.... that's just like middle ages.
I'll use vlc until I'll find replacement or you will fix that, but I'll try to fix that error on my own (modify scr).
PS I'm using linux, but in mac forum is topic about that, so I'm writing it here.
But still, when I open video file from browser there are no subtitles, and going through menus to get them is not user-friendly... so I'll start working on that error fix if vlc team is not going to fix that.No, 1.1.7 don't force you to select "all" at all. This is fixed.I've created account only to inform VideoLan that after 4 years of ucing VLC I've just started looking for some other player.
For me new VLC can't open subtitles.
To do that I need to goto Media->AdvancedOpen, choose video file, and change Subtitle Files to *, then choose subtitles.... that's just like middle ages.
I'll use vlc until I'll find replacement or you will fix that, but I'll try to fix that error on my own (modify scr).
PS I'm using linux, but in mac forum is topic about that, so I'm writing it here.
Not to be rude or anything but... you might want to use your brain as well. I'm a programmer myself, not the best one, but even I know that you need to capture your errors and analyse them. Also, last time I checked the golden rule of coding was to check your input as it ALWAYS CAN BE SOMETHING ELSE... I see no reason to implement check to be performed on the file before it will be loaded as a subtitle. If check fails then the file would not be loaded. No need for an error message (unless file would be loaded manually, in which case you would have a msg saying that this file is not valid subtitle file).Not the right way to speak to us...This is that __good reason__? I see you just play in Steve Jobs here. This is not a good way so for now I'll downgrade to 1.1.5. Thanks.Well, the reason is that .txt can be way more than just a subtitle.
You will be able to open manually.
Now, use your brain.
Imagine you have a .txt file that is the description of the movie, or anything related to the subtitle. Auto Opening will try to open it as a subtitle and fail. Then, it will display an error because it isn't a subtitle...
Auto-detection is restricted to the formats that are very likely to be subtitles.Also, claiming that this file can be 'way more than just a subtitle' makes me laugh. This can apply to every file I can think of and probably even more! Why oh why you have decided to apply this statement to TXT files only is completely beyond me... following this logic you should have completely remove auto-loading subtitle files with the movie as EVERY SINGLE ONE OF THEM can be 'way more than just a subtitle'... Not to mention that movie itself can be 'way more then just a movie'...
Can you explain that to 38 million population in Poland that format they all use for subtitles is not being recognized as likely to be subtitles? I'm sure they'll all love you for that, with me in first place.Auto-detection is restricted to the formats that are very likely to be subtitles.Also, claiming that this file can be 'way more than just a subtitle' makes me laugh. This can apply to every file I can think of and probably even more! Why oh why you have decided to apply this statement to TXT files only is completely beyond me... following this logic you should have completely remove auto-loading subtitle files with the movie as EVERY SINGLE ONE OF THEM can be 'way more than just a subtitle'... Not to mention that movie itself can be 'way more then just a movie'...
And .txt isn't one of those formats.
Code: Select all
static const char const sub_exts[][6] = {
"idx", "sub", "srt",
"ssa", "ass", "smi",
"utf", "utf8", "utf-8",
"rt", "aqt",
"usf", "jss", "cdg",
"psb", "mpsub","mpl2",
"pjs", "dks",
""
};
Code: Select all
static const char const sub_exts[][6] = {
"idx", "sub", "srt",
"ssa", "ass", "smi",
"utf", "utf8", "utf-8",
"txt", "rt", "aqt",
"usf", "jss", "cdg",
"psb", "mpsub","mpl2",
"pjs", "dks",
""
};
Thanks for this clever post. I'll look at another solution then.I registered myslefl only to confirm that what @yeramihi says is completly true. All people from Poland who are watching films on their computers are using gnapi (which is a Linux port forNapiProjekt) and NapiProjekt generally. And for almost all of polish people txt=subtitle...
I am maniac of movies and TV shows, and i have a lot of them on my HDD and they all have a .txt file. And I mean ALWAYS. I understand how a .txt file can be something diffrent, but i don't understand how can it be dangerous... And i REALLY don't know how adding an option "Auto detect .txt. files" can be so hard to do...
I really like VLC and i would hate to replace it with... i don't know what. For now i'm using Mplayer, but it'sjust not the same
And please - listen to people who use your program and only wants it to be better...
P.S. Sorry for my bad english
I'm afraid it isAuto-detection is restricted to the formats that are very likely to be subtitles.
And .txt isn't one of those formats.
OK, I updated to 1.1.7 and now I can select .txt file through Video -> Open Subtitles menu, but no subtitles are displayed. I still have to change extension to .srt or use Advanced Open File. Drag&drop of .txt files also doesn't work. To make sure I tried it all on few different *.avi + *.txt sets. Should I reinstall VLC with cleaning previous settings (I didn't mark it previously) or is it still not fixed?We will include a fix in VLC 1.1.7 (to be released tonight), which will allow to select *.txt files through the Video menu ("Open Subtitles...").
No, it is not.I'm afraid it isAuto-detection is restricted to the formats that are very likely to be subtitles.
And .txt isn't one of those formats.
Return to “VLC media player for macOS Troubleshooting”
Users browsing this forum: No registered users and 1 guest