Interesting ... could you point me to some other thread link about this. maybe its a server related issue then
It's definitely a server related issue as it happens in PHT on my PC, Plex Web and the iOS and Android apps. I'm not sure if there's a specific thread on the issue
Rasplex newbie. Love the project. Looks great and understand it's a work in progress. I've searched the forum and can't seem to find a solution to my problem. I'm running v0.1.35 on a Raspi Model B 256M. Installed fine found my Plex server which is pointing to a QNAP with all my content. I can play music and view photos fine but can't seem to get any of my videos to play. I can run them locally on my server. All of the videos are straight DVD rips to .VOB. I checked the /storage/.plexht/temp/ log file and I see the following error:
ERROR: OpenDemuxStream - Error creating demuxer
Apologize is there is another thread for this or if this was covered somewhere but again, new user, and searched the forums and Google in vain.
Thanks for any help and again great work on the project!
Rasplex newbie. Love the project. Looks great and understand it's a work in progress. I've searched the forum and can't seem to find a solution to my problem. I'm running v0.1.35 on a Raspi Model B 256M. Installed fine found my Plex server which is pointing to a QNAP with all my content. I can play music and view photos fine but can't seem to get any of my videos to play. I can run them locally on my server. All of the videos are straight DVD rips to .VOB. I checked the /storage/.plexht/temp/ log file and I see the following error:
ERROR: OpenDemuxStream - Error creating demuxer
Apologize is there is another thread for this or if this was covered somewhere but again, new user, and searched the forums and Google in vain.
Thanks for any help and again great work on the project!
Do you have the MPEG2 licence for the PI installed?
when I saw RasPlex was out, I immediatly ordered a PI (512Mb).
Two days later, I was testing RasPlex v1.32. It was quite slow and buggy but really promising.
Since I'm running v1.35 I didn't has any freeze. The PI is hidden behind my Panasonic Viera, with CEC support and powered but an USB cable and it's just great !
So thank you to the dev team and people who started this project ;)
Do you have the MPEG2 licence for the PI installed?
I have my license file and edited the config.txt file however am getting the following error when testing the codec:
VCHI initialization failed
I see a couple of other people received this same message but I didn't see any replies that potentially fix this. Has there been any developments with this error?
1080 playback is definitely choppy, 720 as well. SD seems to work fine. Video playback was better in 1.31 although I still had freezes. Still early in development so to be expected. You guys are doing great work. I wish I could do more than just post in the forum but I have no coding experience.
For non technical users
If you don't have programming experience, you can still help!
Testing bleeding edge builds, then complaining about things we broke
Purchase a case or preflashed SD card once they are available
We want to get on hacker news! Please tweet @JustShowHN Show HN: Happy Pi day! RasPlex media center for Raspberry Pi launches http://rasplex.com to celebrate Pi day!
Does RasPlex 0.1.37 auto cache if left alone or do you need to scroll through the entire movie list to get cached images and info?
Also, has anyone had any success overclocking without crashing? Specifically to Turbo settings. Other distros of XBMC do not crash on my unit but RP does however only 5 seconds after starting a movie.
since the WD Live Box I had before doesn't fully support the Plex server, I moved to a Raspberry Pi which arrived just yesterday.
At a first look everything seemed to work flawlessly but at a second look I have problems playing movies with an DTS sound track. So I searched the forum and came across various posts stating that the RasPi is trying to decode the DTS - and indead this seems to be the case. When I play such a movie, the CPU is constantly at 98 - 100% and every 4 to 5 seconds the movie stutters.
So I moved to the config and changed some values according to a topic I found dealing with the DTS problem. In detail I moved to the following values:
The topic said to use force_turbo=1 but I didn't want to change that value because of the warranty problems. With the values given I got an error message of my TV (Sony KDL55HX755) stating that an unsupported audio input was detected. So I removed the hdmi_force_edid_audio line - and I was back to stuttering.
since the WD Live Box I had before doesn't fully support the Plex server, I moved to a Raspberry Pi which arrived just yesterday.
At a first look everything seemed to work flawlessly but at a second look I have problems playing movies with an DTS sound track. So I searched the forum and came across various posts stating that the RasPi is trying to decode the DTS - and indead this seems to be the case. When I play such a movie, the CPU is constantly at 98 - 100% and every 4 to 5 seconds the movie stutters.
So I moved to the config and changed some values according to a topic I found dealing with the DTS problem. In detail I moved to the following values:
The topic said to use force_turbo=1 but I didn't want to change that value because of the warranty problems. With the values given I got an error message of my TV (Sony KDL55HX755) stating that an unsupported audio input was detected. So I removed the hdmi_force_edid_audio line - and I was back to stuttering.
As for my hardware configuration I'm using a class-4 SD card at the moment and RasPlex version 0.1.37.
Thanks in advance for any help!
You can modify this /sys/devices/system/cpu/cpufreq/ondemand/up_threshold and change the value from 95 to 60. What this does is determine the max load on the CPU before turbo kicks in. Currently it waits for the CPU to be under 95% load before overclocking, but if you lower it to around 60% then it tends to be overclocked all the time without setting the warranty bit.
I've noticed that with Version 0.1.35 everythign seems to work pretty nice except for the low res images. Once upgraded to 0.1.37 the USB has all sorts of misreads with my keyboard. Is this already a known issue with this new bleeding versions?
I've noticed that with Version 0.1.35 everythign seems to work pretty nice except for the low res images. Once upgraded to 0.1.37 the USB has all sorts of misreads with my keyboard. Is this already a known issue with this new bleeding versions?
0.1.37 seems to suffers from issues probably coming from the last OE merge. we're working on it to try to clean that up :)
@PhAzE: Will give this option a try. Do I have to set 'force_turbo' to '1' to make this work or can it stay on '0'?
@LongChair: Is your remark with the OE merge only valid for the USB issues or as well for the DTS issue? Or to put in other words: the fix mentioned in the link in my post above - is this already included in the current version of RasPlex so that there shouldn't be any DTS-issues or is this still an open point to be addressed?
@PhAzE: Will give this option a try. Do I have to set 'force_turbo' to '1' to make this work or can it stay on '0'?
@LongChair: Is your remark with the OE merge only valid for the USB issues or as well for the DTS issue? Or to put in other words: the fix mentioned in the link in my post above - is this already included in the current version of RasPlex so that there shouldn't be any DTS-issues or is this still an open point to be addressed?
The DTS issue only exists when trying to decode DTS on the rpi (meaning, not passing through DTS to a DTS-capable receiver but decoding to 2-channel audio on the pi). The CPU just isn't beefy enough to handle it without hardware decoding, which the pi can do but DTS has not licensed its ability. In my experience, the only thing that helped was a pretty significant overclock (that I unfortunately don't know what it was now), but also caused SD card corruption when I left the pi on overnight. I've since acquired some heatsinks that I hope will help, but I haven't been able to run into that overclock config again. I think the core freq was bumped up pretty high, though.