Then we agree @uglymagoo
@blindpet @uglymagoo thanks for helping 
Sadly i noticed that i had to change plex.js to main*.js and inserted the command one more time 10 seconds later (you can see it in the above picture (starting at around the lower third). Did this change anything? Thank you so much
Sorry, that I am pedantic.
@VirtualPlex said:
I have read that Plex for ARM will not do any transcoding as itâs disabled.
But this statement is simply wrong. PMS for ARM transcodes just fine. The culprit is, that when the webbrowser client and the PMS negotiate in the initial stage of a media request, they come to the conclusion that PMS on ARM is not powerfull enough to do any video transcoding on the fly, and decide to terminate the request.
Hence, the problem only exist in th econtext of the webbrowser client - AFAIK - and only for files where the video stream needs to be transcoded. Transcoding of the audio stream and/or remuxing into a different container formats proceeds without problem.
Does that include audio transcoding(which takes almost no CPU) as well? I have quite a bit of my library with DTS or AC3 only audio, formats which are not generally natively supported on smartphones and the like. So if thereâs no audio transcoding on Plex for ARM, then Iâm kinda screwedâŠ
I can tell that with my iPad as client the PMS running on my bananapi transcodes when needed just fine, but the processor is not powerful enough to do it for video as fast as necessary. Hence, the movie plays for a minute or so and then pauses for another minute. Media which only needs transcoding of DTS or AC3 audio, plays flawlessly.
Hence, VirtualPlex should be a happy kid.
PS: Your screen shot show that the streameditor (sed) threw an error. Hence the js file has not been modified. I think you must have made a typing mistake. Does the â;â not have to be escaped?
May i ask someone to please go through my terminal picture again. I am still a little worried that i made something wrong because i tried to issue the command again (you can see it on the picture posted before) right after it did not work but changed it to main* before. Still got an error message. Thank you so much
@noreason because you did not put main*.js in the first line, no changes whatsoever were made to the javascript file at all and explains why you got all those errors (despite my poor German).
The first line creates a variable for the main*.js file that is found so the variable was empty because you used plex.js instead, that resulted in all of the following errors.
@blindpet mh⊠but as you can see in the lower third part of the picture i reissued the command with main*.js inserted (and still got errors). Or am i understanding something totally wrong now? On this picture you can see me issuing the command with plex*.js -> error messages -> me trying to get back the old version (as instructed in the tutorial) via the mv command -> error again -> me running everything with main*.js -> error again.
@noreason further down on the tutorial page there is a manual method, I suggest you try that instead.
@blindpet i guess i will keep it the way it is 
no transcoding needed so far 
But you still think that everything should be fine despite those error messages right? Sorry to be so annoying!
@noreason yes it should be fine, if it is working you have nothing to worry about
@blindpet Thx a lot
re: Audio transcoding on ARM
Thanks all for the clarification that it will work!
I am guessing this has been addressed before but forgive me for not looking through all 51 pages of posts :). I put video files on a 8gb thumb drive and mounted it but when I mapped my movies library to the directory nothing was found after scanning. I know the files are still on the drive also. Any ideas? Does file format matter? I used the MiniBianPlexARMv7 image to install.
@davehess0 this has come up enough times and for some reason I hadnât added it to the guide page, it is there now at the bottom. It assumes you use the mounting drives guide, if you have some sort of automounting software it may conflict.
Thanks for the clarification regarding the transcoding! Looks like no PMS on RPi for me then
So I just moved my installation from my Pi2 to my new and shiny Pi3 (by copying /var/lib/plexmediaserver to the new Pi).
Unfortunately transcoding does not work. As I basically changed everything (System, Distribution (freshly installed Raspbian Jessy, and did this whole copy old data thing and apparently there is a new version of plexmediaserver as well (0.9.15.6.1714-7be11e1-1)) Iâm not sure what the issue actually is.
I see those âTranscode runner appears to have diedâ messages in my logfile, when I run the commands manually the Plex New Transcoder actually dies with a SIGBUS.
Does anyone run it on a Pi3?
@mthiesen just got the Pi 3 today and upgraded Minibian so it works on the Pi 3 (no wifi though despite latest stable kernel). Installed Plex using the instructions and modified the main*.js file and transcoding is indeed working with my test XviD files.
A ready-made Plex image that I have working on the Pi 3 is on the bottom of the guide page, the javascript file is already modified. Please let me know if it works for you.
You will need the /usr/lib/plexmediaserver folder too but I would just install fresh if you want a guaranteed working system
@blindpet So you can confirm that the existing ARMv7 builds just work on the Pi 3 as they did on the Pi 2? Nice
Yes @uglymagoo that is what Iâm confirming
I read that the new chip is only being used as a faster 32 bit version of an armv7 so whatever advantages of the 64-bit architecture may not be used at all.
I did some quick tests with Elephantâs Dream in 1080p (XviD) and the Pi 3 doesnât transcode it any better than the Pi 2, the recommendation should still be to use Plex clients with the appropriate codecs to decode locally rather than relying on PMS to transcode on the fly.
Have you tried overclocking?
It should make a significant boost. Well it was with RP1âŠ
With the release of Pi3, this thread can finally die!
Well done everyone.
