I’m having a peculiar error with strm files.
I have several strm in a folder on my Mac. If I open these strm files on my Mac with Infuse, everything works perfectly, Infuse opens the strm file and the movie starts playing. But the same strm files shared via SMB won’t open in Infuse on the Apple TV! It gives the error “Failed to open specified in .strm file”.
How can I solve this?
And the same files play via an Emby server on Apple TV’s Infuse. In other words, they just don’t work when shared directly via SMB.
Is this affecting other strm files ?
Can you post (or send me a PM) the contents of the strm file?
I´ll send you a PM
I have a very similar problem too. When I add the local folder directly on my Mac, the STRM files work great, but through the Jellyfin server, they don’t work on either Mac or Apple TV. However, they do work on Jellyfin’s web interface. What could be the problem, and how can we debug it?
So, looking at the link in your strm file it appears to be a local link (localhost). This means the link would work when using Infuse on the device where the video is stored but would not work on other devices.
Using Emby in this case would also work since it is accessing the file locally and then serving it to Infuse on other devices.
@james That sucks. I don’t want to use servers, I’d rather share directly via SMB. There’s nothing you can do about it, isn´t it something you can change and/or fix?
Is there a chance that you could use the address you get when you do a get info (on a mac) on the file which starts out as a 192.168.x.x and gives the full path to the video?
Sorry, I´m not understanding what you want me to look at…
I’m really interested in how to use strm files but I’m not the least bit knowledgeable on how they work so I’m just trying to figure it out.
On my mac, if I click on a file that is located on my NAS I can do a get info on that file and in the information window that opens it gives the server address for that video like “smb://192.168.xxx.xxx/Videos/Movies/0 - 9/7 Days in Entebbe 2018.mkv”.
I was just wondering if you could modify that address so it’d work with strm.
I don’t think I can change anything because they are strm generated by Zurg. They point to my localhost e.g. http://localhost:9999/http/movies/xxxxxxxxxxx.mkv.
Is there a reason you are wanting to use strm files?
Typically strm files are used to point at files on a remote server or cloud service.
If these files are stored locally on your Mac you can just point Infuse at the folder where the videos are stored and stream them via SMB.
I want to use strm because they are much smaller than mkv and much lighter and quicker for Infuse to read and play.
I have Infuse pointing to the Zurg folder mounted with rclone where the strm are. And then the strm are pointing to my zurg server (localhost 9999) where the mkvs are.
For me, currently I’m duplicating TV shows that are on the family regular watch list. One copy in the library and one in a share that isn’t in the library that can be deleted after watching and the other in the library is still there for rerun rainy days.
I was hoping I could use the strm files in the non library scanned share to save disc space.
This is a stop gap till we get something like this.
I found this guide which has info specifically for Infuse. I think this would allow you to connect via WebDAV to access these files. Using the strm files would not be necessary.
Also, there are various scanning options available in Infuse for WebDAV (and other) servers and adjusting these settings can affect how fast Infuse is able to index your files.
And that’s exactly what I use, zurg, but with strm instead of mkv. I’ve used it with mkv mounted via rclone but it’s so slow that it was driving me crazy! Sometimes, after pressing play, it would take up to 30 seconds for the movie to start playing! But with strm this no longer happens, it’s much faster and light!
Had you followed those steps before? It seems as though it would allow Zurg to act as a WebDAV server, so you would be having Infuse connect that way instead of SMB. This would allow other devices to connect.
Might be worth a try.