-
Notifications
You must be signed in to change notification settings - Fork 14
Change add-on to use inputstream.ffmpegdirect which also enables timeshifting #67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
b0812a0 to
3b61f11
Compare
|
Note this PR requires testing before any merge is possible. |
ksooo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs a bit more love, imo.
Q: could we get rid of the internal rtsp stuff completely and require inputstream.adaptive?
Q2: why so many different stream handlers? Wouldn't be one (ISA?) enough?
pvr.octonet/resources/language/resource.language.en_gb/strings.po
Outdated
Show resolved
Hide resolved
pvr.octonet/resources/language/resource.language.en_gb/strings.po
Outdated
Show resolved
Hide resolved
pvr.octonet/resources/language/resource.language.en_gb/strings.po
Outdated
Show resolved
Hide resolved
8c9d970 to
0cfb8c5
Compare
|
I've cleaned up the PR now. Extra log statements were simply for testing. |
Yes, getting rid of the internal rtsp stuff is the plan. But i can't test here, need @da-anda to test and see what works. ISA can't be used as it does not support rtsp. |
|
@da-anda I also added a commit to request kodi update the EPG if it has not been requested. Should mean you always get EPG now. |
0cfb8c5 to
eab5fdf
Compare
not sure this is a good idea as fetching the epg takes a very long time on the server side and what happens if you have multiple pvr.octonet connected to the same device all doing this (regularly)? I think this problem needs to be solved in the firmware of the octonet. There a feature is missing that you can set a fetch interval for the epg data so that the octo takes care. EDIT: oh i misread your comment, ignore what i wrote |
|
I tested all 3 alternatives, and only |
pvr.octonet/resources/language/resource.language.en_gb/strings.po
Outdated
Show resolved
Hide resolved
|
Please fix the commit message "changelog and version v21.1.0" - version is 21.0.0 |
c5db93e to
0aad52d
Compare
Done |
0aad52d to
1e42fe2
Compare
|
Ok, I removed the original setting, and opening the stream using the Live API. Now we just use ffmpegdirect, which supports timeshifting. Note, a fix is required for timeshifting for rtsp, but that is a separate PR for ffmpegdirect. |
Cool, could we add a dependency to ffmpegdirect to addon.xml? |
|
I'm not conviced that the EPG load 10 secs after start is something that actually fixes the root cause of the "@da-anda not having EPG data" problem. If there are no data at the octonet, you can try to fetch them as many times as you want without success. Kodi remembering last EPG fetch timestamp and da-anda meanwhile fixing EPG data on the octopus and Kodi not fetching these new data on next start is something that the commit in this PR fixes by "accident" I'd say. |
it already is added, isn't it? |
according to your other comment, the correct fix would be to not return the NO_ERROR state in case no channel could be mapped, correct? (aka some data got back from octonet, but not the correct channels) |
Not sure. It should return NO_ERROR only if data for the requested channel was returned by octopus, but for channels not having EPG data also NO_ERROR must be returned (afair, it's been a while since I looked at this stuff). Not sure whether the octopus API allows to detect the latter. |
1e42fe2 to
9888398
Compare
So this behaviour was observed when @da-anda did not have a valid EPG. Now that he does I reckon we drop this commit for now and see if it's needed later at a later point. In recent tests Kodi remembers the EPG data, and should just request it according to it's own schedule. |
9888398 to
9af448b
Compare
9af448b to
60c8704
Compare
|
Ok, commit dropped, it's in draft PR #68 in case we need it. This PR should be ready to go now. |
ksooo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!
|
@phunkyfish did a runtime-test of this PR. Timeshift seems not to work properly. Sometimes Kodi completely freezes when trying ff/rew, sometimes Kodi crashes. There seem to be several scenarios to cause misbehaviour. |
Correct, as stated above, this needs to be fixed in a separate PR for ffmpegdirect. But nothing it change in this PR to help that. |
If you could do a backtrace and pinpoint the crash and logs too that would be great. When you have time. |
Okay, then let’s hold off the merge of this PR until the ffmpegdirect fix is available. |
This would depend on me having access to a stream. Which I don't currently. I could just comment out the setting for now and then we can revert that commit once it's working? |
|
well, technically you do have access to a stream since VLC can play the streams off of my octonet just fine, it's just KODI/ffmpeg that won't play it via remote connection for whatever reason 😉 |
|
Well it turns out that timeshift is broken on omega. So hopefully I can fix this without a stream in rtsp stream kodi. Time to start bisecting… |
Okay, then let's merge this PR as is. |
v21.0.0