RasPlex 9.9.16 is here
This build is getting to be pretty stable, and unless there are any major problems with it, this will be the basis for 0.4.0
At which point, we will finally recommend users switch to it.
Until then, remember this is still considered "experimental"
The big changes in this release are:
- Added support for tcpdump, to help debug network problems
- The storage partition will now automatically be resized from around 1GB to whatever the side of the card is on the first boot.
- RapidXML replaces tinyXML, which offers some performance improvements
- Transcoding is "fixed" by default, though there will still be issues with surround sound
- Playback for all or most media formats and resolutions (at least on the local network, given a good network infrastructure) should be stutterless with few or no audio artifacts.
- We have added support for an up-front auto-caching system, which will automatically download all metadata for locally found servers the first time you boot. This results in an initial performance hit, but overall much faster performance after the cache has been (automatically) warmed up. In the future, this will be optional and part of the startup wizard, as well as the rasplex-settings dialog. For now, it's force "on", since we need it to be tested.
Some important things to keep in mind:
- Certain actions still cause crashes or infinite hangs (the known ones are trying to go "left" or "right" to switch between descriptions of TV shows in a series will cause an infinite hang, usually)
- Adjusting overscan tends to require a reboot, as it takes a long time or forever to redraw the gui to new overscanned size
- DTS / AC3 cannot be used with transcoding - you get whatever audio plex gives you for now
- Playback and control from iOS and Android, as well as official plex web client is REALLY sketchy, and should not be relied on until these changes are fixed by plex (we are working with them to help, but it's a tricky bug)
- Scrolling too fast in movies or tv show lists will cause "dead nodes" with no description to show up, which remain for about 1 minute. This is issue will be fixed in a future release.
- The autocaching feature is very new, and probably has some bugs. We don't think it works with remote or shared libraries (yet)
http://sourceforge.net/projects/rasplex/files/experimental/rasplex-RP-9.9.16.img.gz/download
Please report all bugs according to our submission guide, so we can figure them out and fix them more effectively:
https://github.com/RasPlex/RasPlex/wiki/How-to-report-a-bug
Dale, I think the auto caching is a great idea. Will this be extended to fanart if necessary? With changes at the library end will the cache update? I mean will tha ability be added or it exists now?
Caching fails at some point in that of the 2 sections I review one section is partially cached. The blank thumbs give you an error message if you try to play. The other section is totally blank. This is after caching completed. 100%.
So far so good. Possibly one small bug; both Plex for android app v3.2.3.67 and Plex Remote v2.10 were showing a client name of "plexhometheather on rasplex". When I changed the following line in guisettings.xml
plexhometheater on rasplex
to
Master.Bedroom
even though the name was changed in oe_settings.xml
Master.Bedroom
it now shows the correct client name in both Plex for android app v3.2.3.67 and Plex Remote v2.10.
@Dale:
On the 24’th I visited my brother (who’s using my RPi) and updated the RPi from 0.2.2 to 9.9.16, and the result was a tremendous increase of the unit’s responsiveness and overall speed. I know you said that the new caching methods probably wouldn’t affect shared server access, but that is the only type of access this RPi does (my brother has no PMS server of his own), and its speed improvement is significant.
Eg:
Opening the “All shows” listing of my shared “TV Shows” section took appx 24 seconds with v0.2.2, but with v9.9.16 this was reduced to just 6 seconds. So that speed was quadrupled…!!! And this is even more noteworthy when we consider that the listing of v0.2.2 was a text listing, while the listing opened by v9.9.16 is an ‘icon wall’. Previously my brother never used the icon wall modes, because it made the client too slow and unresponsive, but with the new version he uses nothing else.
All in all, I’m really impressed by the results of this version. 
Best regards: dlanor
Dale, I’m simply at awe about how much the improvement is significant over 0.3.1. I was totally OK with the overall performance, taking into account the fact that RPI is a low cost machine.
But this version not only looks amazing, the performance increase is astounding. As a plex devotee who has access to almost all of the other clients, rasplex has taken first place as far as I’m concerned.
I immediately hit the donation Burton, and while I haven’t donated much (I did just have my twin sons born) but I donate it with all my heart.
Keep up the unbelievable work!
Sent from my Nexus 4 using Tapatalk
I'm experiencing strong network problems. The raspberry is flooding the network with udp broadcast packages on port 32414.
The whole network goes down.
Anybody else with a similar problem?
logfile keeps repeating the following two lines:
17:49:45 T:2986341472 WARNING: FillBuffer: curl [?G??Re:32400/:/timeline] failed with code 6
17:49:45 T:2986341472 ERROR: CCurlFile::CReadState::Open, didn't get any data from stream.
PI: Model B with 512 MB
SD-Card: Samsung 16GB Class 10
Ethernetconnection: Copper
Installed with the GUI-Installer under OSX
Plex Media Server is running on a Synology NAS on Version 0.9.8.18
edit: CPU usage is always much higher (above 90%) than it was in 0.3.1. Both in gui/menu and during playback.
Tried to install rasplex on a 2nd SD-Card. Same issue.
one additional thing:
if you try to enter a mediaserver manually. It is not possible to chose the ok button.
I'm experiencing strong network problems. The raspberry is flooding the network with udp broadcast packages on port 32414.
The whole network goes down.
Anybody else with a similar problem?
logfile keeps repeating the following two lines:
17:49:45 T:2986341472 WARNING: FillBuffer: curl [?G??Re:32400/:/timeline] failed with code 6
17:49:45 T:2986341472 ERROR: CCurlFile::CReadState::Open, didn't get any data from stream.
Plex Media Server is running on a Synology NAS on Version 0.9.8.18
Same here,
Latest version is crashing my wifi to.
Now going back to stable version.
for the moment I solved the problem by blocking the port via iptables
it seems that rasplex is still working normally
but this is only a work around.
but 1080p content does not play fluid.
i think i'll change back to stable version too
for the moment I solved the problem by blocking the port via iptables
it seems that rasplex is still working normally
but this is only a work around.
but 1080p content does not play fluid.
i think i'll change back to stable version too
could you link the necessary iptables lines please?.
sudo iptables -A OUTPUT -p udp --dport 32414 -j DROP
should do.
This solved my general network-problem, but not the cpu usage issue.
videocontent does not play fluid. So I went back to 0.3.1.
I guess i'm not experiencing nay of these issues since i'm using a wired connection with 9.9.61
Ethernetconnection: Copper
.
I use a wired connection, too.
Only ipad and macbook are using wireless lan.
Maybe your router has more power and can handle the packets? Already made a tcpdump?
Actually recently I switched to a lighter setup for my router. Since my pc is always trretning like crazy, I connected my computer with a switch to the modem and set the wireless router behind it, so it doesn't need to handle all of that traffic. After that, my network is rock solid without any need to restart the router.
As long as your wifi works in the same subnet of the raspberry it shuld be affected, too. But the question is: does your rasplex behave the same way? Can you run tcpdump on your raspberry?
How is your CPU load during idle?
I’m sorry but I have a pretty basic familiarity with Linux. Can you instruct me exactly how to retrieve that data?
Sent from my Nexus 4 using Tapatalk
well... do you know how to ssh into your raspberry?
if not, which OS do you use on your PC? Windows, linux, OS X?
sudo iptables -A OUTPUT -p udp --dport 32414 -j DROPshould do.
This solved my general network-problem, but not the cpu usage issue.
videocontent does not play fluid. So I went back to 0.3.1.
Cool, trying to find somewhere to put it. /etc is read only . where did u put it so it gets into init?.
