im very happy for all the support this request has gotten, but a little dissapointed no dev have chimed in. seems to me, this wont get any priority at all. considering some even report trouble playing 720p over local wifi, it really should.
I’m hoping this might help my issue streaming to a aTV. I have buffering issues streaming HD video to that device as well.
just adding that I would appreciate this feature too.
+1. Effectively the client is treating the server like an internet source- netflix or itunes. So it should behave like progressive download. Start transferring, figure out the transfer speed over the first few seconds, then start playing as soon as its confident it can continue to play without buffering. But then continue to download until the whole thing is done.
A bit like realtime transcoding on something like airvideo - if it can transcode faster than realtime, it chews through the entire movie and then you’re just streaming the transcoded file.
I have a large storage array with a dual quad core in it. Its more than capable of transcoding the stream much faster than the client reads it. I’d say its about 30% cpu to have 2x the transcoded file done. About halfway though a movie its transcoded the entire thing.
I understand that on My Xoom for example downloads it piece by piece but they are played on a per file basis, as someone mentioned above, storing it local is the way to go. Even at max bit rate that your device can handle by the time you trim the front of the file, and add to the back, you have a rolling file size for the most part.
I don’t have a buffering problem at home, but I’m running a cisco access point all gig to the array. However when I’m mobile, or on another persons wifi, I get buffering. I know its not my internet connection because I have 50/50 fios, and its clean.
So yes, giant buffer +1
I would just like to chime in that while my 5Mb upload speed is nice, it can almost handle 720p streaming from my mini to my iPad. If the buffer was increased to a minute or two I wouldn’t have any stuttering. Has anyone looked into the preferences to allow a larger buffer? I mean if you can set it to a number between 1-20 I’m sure I could just edit the preference file and tell it to buffer up to 120, or 240.
I am trying to stream HD content on my LG5600, can someone please tell me that if there is anyway to change the cache?
Thanks
The current maximum is still 20 seconds of buffer. What machine are you using as your plex server? Is the LG5600 connected via a wired connection or wireless?
+1 I’d also like to see additional caching settings greater than 20seconds. Ethernet over power is the best I can do and it stutters on busy scenes. Local media plays fine however.
Is there any update on this? I still see the AQ drop to zero on a couple of movies.
I’m a +1 on this as well. I stream from a dedicated server out on the internet and during peak internet hours the transfer speeds can suffer drastically. It would be nice to be able to pause, go take a piss, have a cigarette or go screw my girlfriend then get back to it preloaded and ready to go.
It would be nice to see some more involvement from the developers to say “This is on the way in the next release” or “This is not going to make the next release but we’ll consider it in the future.”
+1
720p from remote PMS sometimes works and sometimes it lags a lot on my 10 Mbit/s connection (I know I can select a lower quality profile, but I would like to avoid transcoding and use Direct Streaming).
I would like to have more than 20 sec cache as an option.
Devs, are you hearing us? 
+1
This would be a very nice feature for remote users. Source content is often in variable bitrate, and internet connections are often volatile. Caching could really help!
Has this been looked at by any devs yet? Wireless N eliminated the need for this but it would save our hard drives to spin for 10 minutes caching a 2 hour movie vs streaming.
+1 on this from me. In my home theater, I run the Plex client on a machine with 32GB of RAM. I’d love to be able to cache the entire film/episode into RAM for a more stable forward/reverse seeking experience.
Let it start playing right away. In the background, pull the file across the network as fast as possible until the cache is full or the whole file is stored locally. This kind of feeds into having the PMS use an object store instead of a filesystem as well. Someday…
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
