2021-06-03, 03:30 AM
Great, that works! I'll do some further testing now.
2021-06-03, 03:30 AM
Great, that works! I'll do some further testing now.
2021-06-03, 05:42 PM
Try this channel https://my.roku.com/account/add/LRZKZL with 1.11.11 I disabled subtitles completely so they shouldn't show. Let me know if the * comes up.
Martin
2021-06-03, 07:06 PM
Thanks, that definitely got rid of the CCs, but short pressing the * button still does nothing.
Regarding the original topic, I've been doing some further testing using the transcoding settings you provided on the current release (and now this version without CCs), and it works, but I'm still getting "-2 The connection timed out" regularly, just not every time. It can happen when I'm loading Live TV for the first time, or when changing the channel. Re-loading Live TV immediately after the error seems to get around it. I wonder if the error is caused by variable latency on starting up a channel on the server side, because the server is a low end machine? Given that once a stream starts, I get no hiccups -- the video is smooth -- it makes me wonder if it's just possible to lengthen the time out duration slightly, to account for this slightly slow initialization? Some further specs: The Live TV stream gets stored on the main SSD, so it's more likely down to slow CPU speed or some sort of network latency. The server is connected directly to the router over Fast Ethernet (but I doubt it would need Gigabit). My router is 802.11ac, in very close range to the Streaming Stick, and the Streaming Stick is connected using the 5GHz channel, with Excellent signal strength. So I figure it could be the slow CPU on the server, or it could be the performance of the 3600X itself.
2021-06-03, 07:20 PM
I figured your * isn't going to work on your firmware, so I will tweak things a bit for the next release.
I thought you only used 2.4 so your Roku stick is actually better then mine. Fast Ethernet should be fine without wifi dropouts. Changing aac to mp3 in the config.xml settings might be slightly more efficient. Remember, we need zipped logs to analyze problems, it's not a Roku problem, 15 seconds is already long enough. Martin Quote:Changing aac to mp3 in the config.xml settings might be slightly more efficient. I've been testing it with mp3 transcoding, and also updated to server version 5.1.2.210603 last week, and wanted to follow up with you with some additional thoughts, because I've continued to see it happening. I noticed that it seemed as if most of the latency was occurring *before* ffmpeg.exe started transcoding. Then I noticed the other involved process running, DeviceHostWindows.exe? I looked up DeviceHostWindows.exe and found this thread: https://forums.nextpvr.com/showthread.ph...276&page=2 For whatever reason, I had 'Keep digital tuners primed' unchecked. I'll test it now with it checked and get back to you. My latest theory was that it was due to some sort of inconsistent latency originating from the HDHomeRun tuner. Maybe keeping the tuners primed avoids this?
2021-06-15, 05:08 PM
(2021-06-15, 04:20 AM)mmortal03 Wrote: For whatever reason, I had 'Keep digital tuners primed' unchecked. I'll test it now with it checked and get back to you. My latest theory was that it was due to some sort of inconsistent latency originating from the HDHomeRun tuner. Maybe keeping the tuners primed avoids this? For HDHR tuners, I'm pretty sure that you don't want that option checked. As I understand it, with HDHRs it will cause the HDHR tuners to constantly stream across the network to you server--even if you aren't using them. That will put extra load on both you network and your server (because it has to receive all of the extra network traffic and discard it).
2021-06-15, 05:32 PM
(2021-06-15, 05:08 PM)BrettB Wrote: For HDHR tuners, I'm pretty sure that you don't want that option checked. As I understand it, with HDHRs it will cause the HDHR tuners to constantly stream across the network to you server--even if you aren't using them. That will put extra load on both you network and your server (because it has to receive all of the extra network traffic and discard it).This is only if you're using BDA drivers with your HDHR. ie 'ATSC' or 'QAM' device types on the Settings->Devices page. The 'HDHR' device type uses a different mechanism, and that checkbox makes no difference.
2021-06-16, 01:01 PM
2021-06-16, 01:17 PM
Still waiting to see those logs.
Martin.
2021-06-21, 12:21 PM
(2021-06-16, 01:17 PM)mvallevand Wrote: Still waiting to see those logs. I don't think I've seen this issue in the last week, so I've been focused on that other thread. I haven't nailed down what the difference might be. Did you happen to make any relevant changes to that build that has the subtitles turned off? As that's the one I'm testing with. It could obviously just be something different on my end. I'll let you know if I start seeing it consistently again. |
|