Start Watching Recording in Progress from Beginning(Failing)

“Watch from beginning” usually works for me but there are tons of cases where it doesn’t.

Relying on finding the program or channel in the guide just doesn’t work. Just let us select from DVR Schedule.

It becomes very hilarious and actually impossible to watch when you set it to record X minutes before/after the show. For example, I record a 12-1 show from 12-1:30. At 1:15, I try to watch but I have to select the show that started at 1, which brings me to the recording starting at 1. I actually have to wait until the recording completes to start at 12.

Server: Windows 10
Clients: Roku primarily. Also use Fire TV, Windows 10, macOS

1 Like

Coming up on 2 years and the problems still exist. Plex sends out advertising on the “joys of Plex TV” but never seem to address the issues brought forth in this thread.

Are y’all going to support ROKU devices or not? It seems like your only concern is Android. If that’s the case, at least have the courtesy to tell those of us you’ve been promising that Android is your only platform.

1 Like

We only have one major known issue left, which affects all platforms, as it’s a server side issue. If you think we’re not willing to support Roku, please have a read through the thread and you can see where our developers have directly interacted with people here to resolve issues.

1 Like

I tried to find logs from you here for your issues but cannot see any.

Don’t refer to posts by other users when saying you have a problem.

If you have a problem and something is not working for you, best to have it investigated - run with debug logging enabled on the server (should be by default) and on the roku app - see settings

Reproduce the problem, note down the time and what is wrong and capture the logs from the server and the roku app and attach with details of exactly what the issue was and at what time and when doing what

See
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/

https://support.plex.tv/articles/200250417-plex-media-server-log-files/

https://support.plex.tv/articles/201377603-roku-logs/

@DaveBinM,

I’m also facing the same issue. (See my post on May 2). Looking at LiveTV or a show when recording is in progress I can’t go RW/FF. It always returns where I started to play.

For example:
If I start a show (or LiveTV) at 8:00pm, watch it for 5 minutes and try to rewind to 8:03 (it’s an example, whatever the time I rewind, the behaviour is the same), it hangs for few seconds at 8:03pm and it brings me back at 8:05pm. The same thing happens if I try fast forward (e.g. skipping commercials to catch up on a show being recorded or LiveTV after a pause). It does not work.

I understand I should provide logs and make more tests to help (I hope) you (Plex devs) narrow down the issue, but reading this thread it seems to be a common issue.

EDIT: I’ve made some tests and retrieved the logs. Should I attached the logs to my post in this thread and shared them publicly or is there a more secure way to do it?

We’re already aware of this server side issue and are investigating it. At this time, we don’t require any more data, but thanks for the offer :slightly_smiling_face::plexheart:

Oh, ok!
Thank you. I’ll wait for announcements then.

But I have other issues (not related), so my question still remains :-). Is attaching logs to posts only way to share them?

I agree. I’m a product manager myself, and I make sure I actually eat my engineering teams cooking every day so I can relate to what our end customers experience, and provide actual user feedback based on my own usage of products. Granted, it’s not a media server product, but it does back up my Plex environment quite nicely. More engineers and product managers need to use what they produce.

We call it “dogfooding”, and I can assure we do use things in house all the time. I’ve been using Live TV & DVR since before it was released publicly, and have over 5,000 recordings. We can’t catch every possible scenario (due to the number of permutations of hardware and software), but do our best to identify as many issues as we can as early as we can

2 Likes

What device are you “dogfooding”? I believe earlier in this thread or some other thread you’ve indicated you use a Shield which apparently has been functioning for quite some time now.

However, I can confirm that the ROKU devices still have difficulties with any form of time shifting and all other issues listed for a very long time in this thread.

Tuning is still extremely slow and fails as often as it succeeds (Beefy W10 server, Hauppauge quad PCI tuners).

All this is with a direct Gb connection to a Pre or Post 2019 ROKU Ultra.

I see again where you’ve said there is only 1 bug remaining so I can only surmise you mean that the ROKU just doesn’t work as the last bug. You’ve chastised me already for saying that but I’m not trying to be anything but honest here. It’s the only logical conclusion I can draw based on my observed and reported behavior of the software.

I’ll not post any logs as there is too much information I choose not to share. I understand it would be your preference but I"m not a paying customer to debug your software beyond reporting how you can repeat the problems.

This is a very simple problem to replicate if you would only purchase a ROKU Ultra and use it. I get that there are many combinations of hardware but the ROKU Ultra is one of the most used devices based on sales figures so that should be in your testing. You don’t support many different PCI tuners so you should also have a W10 setup with the Hauppauge quad PCI tuners. Again, no disrespect intended, just statements of obvious fact.

This has been suggested before by others. Put together a W10 server with a quad PCI tuner and a ROKU Ultra and you can replicate all these issues without problem.

Hope this helps and I look forward to your report back on your product.

Thanks again and good luck!

Personally, iPhone, iPad, Apple TV, Web, and Nvidia Shield. Others internally use Roku, Amazon Fire TV, Android Mobile, and our web based TV apps.

I said there is one server bug which we’re aware of that’s outstanding, in relation to timeshiftimg.

It’s also incredibly hard to solve issues we can’t replicate, without logs, so we know what’s happening there. We don’t ask anyone else to debug, but merely to spend the five minutes required to pass logs along, so we can debug.

Personally, I can’t just purchase a Roku, as they don’t sell them in the country I live in, so obviously not one of the most used devices in my country :sweat_smile:

We have a full testing lab with different OSes, tuners, and devices, but that still doesn’t mean we can reproduce your exact issue. We’ll never be able to completely replicate someone’s setup, with their tuner, network, server, reception, and all that.

It’s not ONE issue, it just doesn’t work and it’s been reported here for a VERY long time. It’s REAL easy to reproduce if you just use a ROKU. I know of no one using a ROKU who will tell you that time shifting has ever reliably worked (except maybe Noah).

Try it, I have confidence you’ll be able to reproduce the problems (multiple). All you have to do is try!

Good luck!

And with no disrespect, and only because you’ve mentioned you’re very careful with the words you use in other posts, we can diagram your sentence if you like because what you said was

and then you went on to modify that object by saying

You didn’t say you only had one server bug remaining. You said you only had one bug remaining and it was on the server. Two very different things.

Anyway, spend 10 minute with the ROKU and all the problems reported will be easily replicated.

Good luck.

How’s your testing going with the ROKU.

I’ll bet you found all the problems in 10 minutes, or at least observed them. It’s not complicated. Just use ANY up to date W10 server with Hauppauge quad PCI tuners configured to your recommended specs or better, ANY OTA signal acceptable to your software for playback/viewing, a wired Gb connection and your choice of a ROKU Stick+ or either Ultra.

I know you said you had all this in your lab so I’m eager to hear your report out. Heck, would love to see the log files too if you don’t mind sharing.

Good luck, I have confidence you’ll find these problems if you try.

While I’m not questioning this statement as factual, IMO Plex has no credibility in this area…hence users posing this question. There’s too many easily reproducible bugs that exist for long time frames where Plex employees request logs…instead of saying “this is a known bug”. The later rarely happens on this forum compared to the former.

That’s okay, you’re allowed to have your opinion. However, as I’ve stated before, there are so many variables that we can’t catch every possible scenario. For things we have identified, there is also a matter of priority. So we might catch and fix a really serious issue or two, and know there are a few little things that will get fixed later, and you’d never know the bigger issues ever existed. Being easy to reproduce also doesn’t necessarily mean easy to fix either. So sure, maybe you can reproduce it easily, but we can’t. That’s why we ask for logs. Personally, I make a point of acknowledging known bugs when I come across people mentioning them, but I tend to focus my time on finding things we don’t know about :man_shrugging: :plexheart:

Running server v1.19.4.2935 on a Synology NAS. Plex for Windows client gives me the option to start recording in progress from beginning and when tested yesterday it worked. Android client (Pixel device) and Roku client (Streaming Stick+) do not even give the option, it just starts playing the channel live. Tried both the regular Roku channel and the Preview (Beta) channel.

Yep - Start Watching Recording in Progress has stopped working in the last few days on my Shield…

How close were you to the start of the recording? I personally can’t reproduce :thinking:
What’s the app version?

Android app version is 8.2.1.18636 (1cc6ce64). Pretty sure I was >10 minutes from start of recording, having seen earlier references to this.