The url needs to be able to be resolved by the client. The media isn’t local to the client. You need to use a url that the client can access the video file from.
Thanks for the reply but i have no idea what you said or mean or even know what too do (i a short term how will this url work with content stored on my server's hard drives?
The paths in your STRM files are paths to the videos files locally on the computer. Channels loads those directly on the client. It can’t reach them since they’re on another computer.
Why don’t you just import the actual files into Channels with the local content feature?
just wanted to give the new thing ago, see if its the same as emby but in this case it's not
reason im not import local is im going to move over to the shield as ive setup a nas if it import the content it bogs down the shield hence emby strm make the shield more smoother with less i/o strain belive it or not so wanted to shift from emby too channels now you have the same feature but sadly its not mature like embys one with local content
anyhow many thanks for reply
I wouldn't link to Kodi resources as a reference for Channels STRM imports. It talks about different protocols and playlist types that aren't supported by Channels. The best way to explain this feature, as I understand it, is it simply allows for files that are otherwise already compatible with Channels to be remotely hosted.
Will strm links using .mov link (that plays in channels, not external app) work with virtual channels ?
@Maddox I've been playing around more with this recently. Noticed that even though the link plays just fine in channels it does not pull over the length of the video so the video cannot be scrubbed to different times. In channels it just shows the video being a "0" length.
Another thing, which is probably a byproduct of the my first point, is that the watch state is not saved so I can't restart where I left off. Might want to check into this cause the online documentation you have about this feature seems to indicate the watch state should be saved so maybe there was a regression at some point??
STRM playback now works in Android with the next beta build.
Fixed in DVR prerelease.
Fixed in next tvOS beta
I'm on August 31st versions of both the server and the Android app; none of my test videos play in the web or on Android. The web player just spins and Android gives a "Recording Not Found (-13)" error. All play fine directly and even launching VLC from the web client.
Hmm. Is this remotely? Can you submit diagnostics
Okay, after the last fixes in the latest version, some of them play, but not all of them. I have confirmed all of the links are real and working, but I get various errors:
It does not appear to be a "file type" issue because I can get the Apple MOV file to play with no issue, but a different MOV file throws one of these errors.
Also, there appears to be some weird overlapping going on with the text on the playback bar in the left corner:
Submitted diagnostics from the TS4K+: aa89f5b4-45a8-4ff4-90a8-dbbc3e2467a4
One of those was using WMA audio. I added support for that in the latest build.
The others I'm not sure. May be related to the web server hosting the files.
Didn't seem to resolve the issue on any of them (all latest versions). The host files play fine on the web at the exact same time. Wondering if it has something to do with the files being so small / low bit-rate that they just look like failures? They are very tiny and low quality.
afe9bef4-092d-4228-b25d-f029daa62eae
Do the same videos play if you download and import?
So I downloaded this file:
https://www.learningcontainer.com/wp-content/uploads/2020/05/sample-avi-file.avi
It plays perfectly fine on my computer. I added it to my imports, however, it will not play in the Web Player or on Android. Submitted diagnostics from the TS4K+: 661f9adf-3f87-43d3-a27f-2f1afb5d7b3e
I did notice in the logs that it is basically failing at each segment because of a missing codex:
2022/09/06 08:20:48.242649 [ENC] Next segment to pre-encode of 52 is 52s from the last request of 0
2022/09/06 08:20:48.248009 [ENC] Starting encoder for sample-avi-file_dowload.avi in C:\Files\Media\Channels DVR\Streaming\file80368-ip10.255.1.144-3774689051\encoder-52-2201167099 at 52 (51.000000) (encoder=h264_amf, resolution=240, deinterlacer=blend, bitrate=436, segment_size=0.01)
2022/09/06 08:20:48.317864 [HLS] ffmpeg: file80368-ip10.255.1.144: Guessed Channel Layout for Input Stream #0.1 : stereo
2022/09/06 08:20:48.317864 [HLS] ffmpeg: file80368-ip10.255.1.144: Decoder (codec msmpeg4v2) not found for input stream #0:0
2022/09/06 08:20:48.322607 [HTTP] | 200 | 6.2599ms | 127.0.0.1 | POST "/dvr/files/80368/hls/progress?key=file80368-ip10.255.1.144"
2022/09/06 08:20:48.441218 [ENC] Encoder stopped for sample-avi-file_dowload.avi in C:\Files\Media\Channels DVR\Streaming\file80368-ip10.255.1.144-3774689051\encoder-52-2201167099 after starting from 52 without encoding any segments. Marked segment as failed.
Okay I'll add that codec. If there are others they will also need to be added individually.
Okay, this is weird. I installed the latest pre-release and tested with the same file, and now it is looking for a different Codec (adpcm_ms).
2022/09/07 08:11:09.150294 [ENC] Next segment to pre-encode of 125 is 2m5s from the last request of 0
2022/09/07 08:11:09.154510 [ENC] Starting encoder for sample-avi-file_dowload.avi in C:\Files\Media\Channels DVR\Streaming\file80368-ip10.255.1.144-4007405193\encoder-125-4136029055 at 125 (124.000000) (encoder=h264_amf, resolution=, deinterlacer=blend, bitrate=10000, segment_size=0.01)
2022/09/07 08:11:09.216958 [HLS] ffmpeg: file80368-ip10.255.1.144: Guessed Channel Layout for Input Stream #0.1 : stereo
2022/09/07 08:11:09.217403 [HLS] ffmpeg: file80368-ip10.255.1.144: Decoder (codec adpcm_ms) not found for input stream #0:1
2022/09/07 08:11:09.219475 [HTTP] | 200 | 5.0234ms | 127.0.0.1 | POST "/dvr/files/80368/hls/progress?key=file80368-ip10.255.1.144"
2022/09/07 08:11:09.348956 [ENC] Encoder stopped for sample-avi-file_dowload.avi in C:\Files\Media\Channels DVR\Streaming\file80368-ip10.255.1.144-4007405193\encoder-125-4136029055 after starting from 125 without encoding any segments. Marked segment as failed.