Infuse can use local subs.
I do not see how it would be possible currently to use local subtitles on Apple TV? I can only look for subtitles on Open Subtitles. I believe other apps support navigating the folder structure for subtitle selection -or at least, Infuse could provide a list of subtitles found in the same folder / sub-folder of the media file.
As long as you follow the naming instructions in the users guide for your local subtitles those subtitles will be selectable in the subtitle menu when playing the video on the Apple TV.
The user guide states …in the same folder. Is the same folder where my mkv rips are?
This is the directory structure:
Where episode.srt is not the same as media.mp4
So even if extract all the .srts from the sub-folder structure I still have to manually rename them. So really -there are other players out there that support this, it’s useful, it’s flexible and I don’t understand what would be so hard to implement about it.
Please have a look at my previous post to understand better what my situation is and why it would be useful to have this functionality in Infuse.
One reason I can see for not adding this is it would slow down Infuse when it has to scan for every video looking for a subs folder and when it’s already available to add your own local subs, renaming them seems to be a pretty quick solution since you know what subs you’ll need and not have to rename 30 different subtitle files.
You can add your support to a currently running thread that is requesting the browse “subs” folder here if you like.
Don’t forget that you need to click the like button on the first post in that thread to show your support for that suggestion!
Looks something like this, right?
You’ll first need to create a suggestion thread explaining why Infuse should support parsing subtitles stored in such an odd manner, and then convince a large enough number of other Infuse users to publicly voice support for your suggestion that Firecore is suitably motivated to dedicate the time and resources required both to write the code required to successfully parse subtitle files stored and named in this non-standard way, and to (hopefully) ensure the newly written code doesn’t introduce weird issues elsewhere in Infuse.
I’m afraid it’s far easier to simply resign yourself to renaming the files and moving them to the correct location as needed. Software exists that can help you automate the process, if you find yourself doing it often.
There’s no need for infuse to do anything different than to enable the user to manually specify a subtitle file that is stored in a sub-folder inside the folder storing the media the user is trying to play. And I can’t imagine this being harder than implemented something like looking up subs online on Open Subtitles or similar.
Also it is not that trivial to rename tens of subtitles… imagine a season of 28 episodes. And now imagine each subtitle is stored in a sub-folder, and each subtitle is named english.srt. Now imagine you want to have subtitles in 2 languages. So, can you think of an easy way to extract each english.srt from its episode subfolder, move it next to the media, rename it identically to the media and do that for multiple languages?
I will of course in that thread and voice my support.
You’re very close in your depiction of the folder structure.
However I don’t want Infuse to do anything to the subtitles in sub-folders… right now I have an Emby server and I am only using Infuse as a player, nothing more. And all that I want is to have a button to ‘browse’ manually for a subtitle file. And I suggested, if there are security or performance concerns, that Infuse only allows you to browse for subtitles inside the main folder where the media is located.
And yet you are arguing that it ought to be trivial for Firecore to parse these poorly named and grouped files automagically for you.
Like I said, you can utilize other software to assist you in the process if necessary.
Like I already said, I don’t want Firecore to parse anything, only to let me specify manually the subtitle for the file playing.
And if that is something less trivial to implement than interfacing with an online host to find subtitles over the internet rather than on my local network next to the media, then I will seriously consider deleting this thread.
But won’t you then need to do this repeatedly for every single episode you watch of this series (and all other series similarly sourced)?
That seems (to me) to be far more painful (or tedious) than remaining all the subtitles up front.
I suppose the user suggestion thread in that case would be something to the effect of “allow a user to (on demand) point Infuse to a specific subtitle file in a specific share directory (other than the one the currently playing video file resides in)” — essentially, opening up a file browser instead of a pre-configured open subtitles search when local subtitles are not present or satisfactory?
This is a very good synthesis.
So yes: in case there is no subtitle embedded or a matching subtitle next to the media, allow then the user to browse and specify one himself.
I do not believe this to be more tedious than the example I described above -one can browse for the subtitle while the opening credits are running or they could not browse at all for one unless there’s dialogue difficult to understand. This is much more convenient than preemptively shuffling and renaming hundreds of subtitles.
it would slow down Infuse when it has to scan for every video looking for a subs folder
Not necessarily. Instead of finding all subtitle files during the long-taking scan, it should delay the reading of the Subs folder(s) up to when you actually want to play the video, or even only when you want to choose subtitles, and only then it has to actively look for all the subtitles to choose from, scanning the subdirs. That slight delay we can surely with.
BTW, as a programmer, I believe they’re not doing an ideal job when they scan a remote (networked) video directory tree. I’m writing software that regularly scans NAS volumes, and I’m certainly faster detecting changes on the same volume than Infuse does on my AppleTV.
The original question was asked and answered. The OP want’s something different and was directed to the currently running suggestion thread with that request where they can show their support.
That makes sense. Having carelessly blown out my ear drums earlier in life than most, I now require subtitles for almost all content I sit down to watch. If one only uses subtitles occasionally, I can see why the math may add up differently.
This may be true, but I’m curious: Is your more-efficient scanning software customized to your specific NAS environment, or does it also (as Infuse must) run — with limited permissions and APIs — on iOS, tvOS, and MacOS; while supporting at least a couple handfuls of different network transfer protocols (both local and remote), a dozen different online file-hosting services, scores of different networking and storage device operating systems (when including support for variant release editions and multitudes of version revisions) running on hundreds of different hardware configurations; with all of the above user-regionalized to a myriad of different world language options?
Might it also be possible that the frequency of collection update detection you prefer is neither required nor desired by all other users of Infuse (who might prefer less frequent updating in exchange for less heavy utilization of various system or network resources)?
I suspect it’s a lot harder for the writers of any given piece of software to provide an “ideal” experience for all users than many give credit; especially when all those users interact with the software in their own unique ways and likely each have a different definition in their minds of what “ideal” means.
I try to keep that in mind when I find myself tending toward apoplectic when bemoaning how Firecore has gone so long failing to fix “obvious” flaws in their software which I (very helpfully) keep periodically bringing to their attention.
I have optimized for different network protocols (SMB, AFP, NFS), though Apple has done a great job in their higher-level file APIs, where you can specify which metadata you’re interested in, and they optimize the calls. For instance, often it’s faster to fetch only the file names, not other attributes (mod date, size etc.) at first, and only if you notice differences, you fetch the extra data.
For Infuse, which can mostly assume that files don’t change their contents (there’s always the forced scan for that), it could only fetch the names in each dir, and see which files changed.
Another method is to rely on the fact that a dir’s mod date won’t change as long as the files inside haven’t been exchanged. That doesn’t count for deeper dir levels, though.
I’d offer my expertise to Infuse, if they’d want it, too
Oh, on AppleTV, Infuse scans my NAS nearly every time I open it, and then it takes minutes each time. That’s not ideal, and quite annoying. I’d not bring that up otherwise.
Only “workaround” for me, to get it offer newly added items faster, is to go into the specific folder where the new items are in. That helps a little, but it also tedious.