Jump to content
Luke

Emby Theater on Raspberry Pi

Recommended Posts

denz

I bought it from www.dx.com and my experience with them has been positive when my friends daughter had an issue we contacted them and they provide us direct with the manufacturer who were very pleasant to deal with and responded very quickly and sorted out a issue.

 

http://www.dx.com/p/guleek-gpc-intel-z8300-win10-smart-super-pc-2gb-ram-32gb-rom-coffee-453610#.WFst0IVOKUk

 

Thanks for the links I had a look at them and they are significantly lower than I found so I will probable purchase one today.

 

I think with pi3 emby theatre will run smoothly since with pi2 overclock it is not bad but it is not something for the long run unless it can be smoother user experience.

 

I have to look through my emails and see what power supply I purchased for pi2 to see can that be used on 3.

Share this post


Link to post
Share on other sites
Luke

Pi3 can probably handle everything i would think.

Share this post


Link to post
Share on other sites
barat

I hope that ET on Pi2 won't be slower then OSMC with Emby for KODI ... then from my point of view it will be still good choice :)

Please try to aim Pi2 since those (IMO) are most popular these days ... maybe disable some effects when Pi2 detected or so - I don't mind not having some fancy animations :)

Edited by barat
  • Like 1

Share this post


Link to post
Share on other sites
denz

When playing mp3 plays for 4 seconds and it just stops.

 

I am writing this from the pi how amazing is this. 

log.txt

Share this post


Link to post
Share on other sites
denz

I have resumed a movie and it just went into a loop but the odd thing in the log file shows nothing. 

 

For testing purposes I have removed all overclock settings. 

 

After I posted the log I went to play it again and it worked. So it feels like it is not forwarding a commands when one time it works and some times it doesn't.

log.txt

Edited by denz

Share this post


Link to post
Share on other sites
denz

Regarding speed its not that bad actually the reason why kodi feels faster its the layout that is different kodi is very compact whereas emby screens are very long it is bit hard to explain however for live tv kodi blows emby away.

 

Priority should be that everything works as now i am finding a lot of bugs once the bugs get ironed then speed needs to be looked at.

 

some things that are faster than kodi like when you press back from watching a video the screen appears instant here you would want some animation to slow down the display or going to detail screen it is very fast. I think it needs more animation not less when you scroll at the menus at the top it feels very smooth and fluid.

 

Things that are slow and it jumps are detail screen scrolling when there are many actors and the in main screens when there is a lot information to scroll. I am sure luke will figure it out just first things are bugs.

 

 

Little bug when you put it in window mode you cannot maximise it any more this is not a big issue as this app will be always full screen.

Edited by denz

Share this post


Link to post
Share on other sites
Sammy

I hope that ET on Pi2 won't be slower then OSMC with Emby for KODI ... then from my point of view it will be still good choice :)

Please try to aim Pi2 since those (IMO) are most popular these days ... maybe disable some effects when Pi2 detected or so - I don't mind not having some fancy animations :)

 

 

I agree. I too have a rPi2 and don't plan to upgrade anytime soon. Thanks.

Share this post


Link to post
Share on other sites
denz

Great work Music plays fine now. Tried mp3, m4a wma all work.

Share this post


Link to post
Share on other sites
barat

Emby theater uses cec-client differently than Kodi so perhaps the problem will not occur.

Will check when we get something like beta. But 4.x has more advantages like proper handling of constant press (press&hold) - useful with "arrow" keys ... osmc was able to allow 4.x, maybe your bundle will include it as well :)

Edited by barat
  • Like 1

Share this post


Link to post
Share on other sites
barat

Ok - so for Pi You won't plan to make "customized" raspbian image?

Emby Theater for Pi is then mostly same like for linux?

Edited by barat

Share this post


Link to post
Share on other sites
Tur0k

Now this is interesting. I will have to give it a try

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
Luke

Interesting indeed !

Share this post


Link to post
Share on other sites
barat

OSMC is this kind of IMG which You write on SD so it's good idea - You have then control about system on which ET was fired ...

I'm not linux guru, so I don't know how libCEC 4.0.0 was implemented there, but I suppose that it was compiled from source.

Manual with additional step to make ET autostart would be appreciated :)

Edited by barat

Share this post


Link to post
Share on other sites
haraldov

Great work. I tried Emby Theater for Pi on my Raspberry Pi 3 Model B for playing recorded mkv from Emby server Versjon 3.1.261.0 beta (Ubuntu 16.04) .

experienced problems to play two different HD channels. With livetv tvheadend streams with resolution (MBAFF) 1920x1080 (AVC, 25 fps) I got no video or sound, but with (Progressive) 1280x720 (AVC, 50 fps) I got sound and video. All this data comes from mediainfo.

I did the test with omxplayer like this:

But then I found out that I need to give the GPU (graphic processing unit) more memory when playing 1080 videos. I placed this line gpu_mem=128

in the /boot/config.txt. You can also use the utility raspi-config to do the same without text editor. After a reboot the GPU had enough memory to play 1080 videos.

More information about optimizing omxplayer you can find her: http://stevenhickson.blogspot.no/2012/08/setting-up-omxplayer-gui-on-raspberry-pi.html

Share this post


Link to post
Share on other sites
Luke

@@haraldov thanks for the info !

Share this post


Link to post
Share on other sites
haraldov

Howto build libcec 4.0.x from source (git) and make a raspberry .deb package

# Step 1 from https://help.ubuntu.com/community/CompilingEasyHowTo
sudo apt-get install build-essential checkinstall
sudo apt-get install cvs subversion git-core mercurial

# To compile libCEC 4.0.x on a new Raspbian installation.
# From https://github.com/Pulse-Eight/libcec/blob/master/docs/README.raspberrypi.md
sudo apt-get update
sudo apt-get install cmake libudev-dev libxrandr-dev python-dev swig
cd
git clone https://github.com/Pulse-Eight/platform.git
mkdir platform/build
cd platform/build
cmake ..
make
sudo make install
cd
git clone https://github.com/Pulse-Eight/libcec.git
mkdir libcec/build
cd libcec/build
cmake -DRPI_INCLUDE_DIR=/opt/vc/include -DRPI_LIB_DIR=/opt/vc/lib ..
make -j4
sudo make install
sudo ldconfig

# From Step 4 https://help.ubuntu.com/community/CompilingEasyHowTo
# If you want a .deb package replace sudo make install with:
sudo checkinstall

# Install the raspberry .deb package
sudo dpkg -i /usr/local/src/libcebuild/build_20161226-1_armhf.deb

Share this post


Link to post
Share on other sites
haraldov

Check that cec-client have found the device by running:

pi@raspberrypi:~ $ cec-client -l
libCEC version: 4.0.0, git revision: libcec-4.0.0-3+4-12fa275, compiled on Mon 26 Dec 10:42:22 UTC 2016 by pi@raspberrypi on Linux 4.4.38-v7+ (armv7l), features: P8_USB, DRM, P8_detect, randr, RPi
Found devices: 1

device:              1
com port:            RPI
vendor id:           2708
product id:          1001
firmware version:    1
type:                Raspberry Pi

Share this post


Link to post
Share on other sites
haraldov

I have no problems to use libcec 3.0.1 which comes with rasbian jessie with pixel on my Samsung LCD tv. I only wanted to give information to @@barat how to make a .deb package for upgrading to libcec 4.0.x if he wanted to try building himself. Sorry for that.

Share this post


Link to post
Share on other sites
barat
But then I found out that I need to give the GPU (graphic processing unit) more memory when playing 1080 videos. I placed this line gpu_mem=128

in the /boot/config.txt.

 

AFAIK OSMC is configured to give 256M for GPU. I dunno why they gave so much, but I suppose that it was tested in some way :) Maybe this will speedup ET GUI?

Share this post


Link to post
Share on other sites
barat

Example forum post:

https://discourse.osmc.tv/t/osmc-does-not-show-all-available-memory/7061

 

Here another one from moderator:

https://discourse.osmc.tv/t/gpu-mem-settings/18349/2

 

But if You really want I can paste here my config when I return home :)

There might be some other settings which can help to tune-up raspbian for ET purposes :)

Edited by barat

Share this post


Link to post
Share on other sites
barat

I'm not suggesting, I just wonder ... maybe they gave 256M because it best fits KODI req, but if electron uses GPU to speedup things then 256M might make ET more responsive ...

If someone is linux freak then he can install OSMC KODI17 beta, kill mediacenter (remove from "autostart") and install ET there (since OSMC is tuned-up and lightened raspbian) ...

BTW - osmc KODI allows for two video backends/players omx/mmal - but I don't know what's the difference between them.

I don't have time now to play this ET build on pi2 ... so I'll stick with OSMC a while and will be just following/read this thread :)

Edited by barat

Share this post


Link to post
Share on other sites
denz

I have experimented with removing pixel desktop manager and just have xorg but it made no noticeable difference it is still jumpy and not for long term usage so it's not pixel that is cause of emby not being smooth.

 

I have watched two movies on it today one in hd and other in sd and both played without a single issue. I think for mem I put 280.

 

I have ordered pi 3 and hopefully by Friday it will be here I wanted to get it for awhile so it is good excuse.

 

As it currently stands pi 2 is just too slow great for kodi but not for emby will see how I go. I doubt it can make kodi any faster since it already can start live TV instantly it will probably just make it even more fluid.

 

I will give feedback once pi 3.

 

I will give osmc a whirl as well.

Edited by denz

Share this post


Link to post
Share on other sites
haraldov

Some notes about my experience running Emby Theater on raspberry pi 3.

 

I find Emby Theater navigation smooth and without to much lagging. I have no problems to use my tv remote for browsing the folders. For playing recordings and live tv (tvheadend live streams) from Emby server 3.1.1.0 it should be quicker.

 

1) Use gpu_mem=256 not gpu_mem=128 as noted earlier. The raspberry pi 3 have 1024 MB memory to share. Remember to update the firmware with rpi-update.

Omxplayer need a minimum of 128 MB GPU memory for rendering the subtitles.

https://github.com/huceke/omxplayer/issues/140#issuecomment-15452919

 

2) I have tried to use the experimental open gl graphics driver to optimize Emby Theater, but you only get sound and no video when you play recording. You can install the driver with raspi-config. 

 

3) I have issues with subtitles not showing when playing the file with omxplayer for some of my mkv movies. I think it has to do with gpu_mem issue mention above or because S_DVBSUB is not supported. 

 

Why do you need to use omxplayer? You can install hardware accelerated mpv for raspberry pi 1/2/3 which works better than omxplayer. For more information look here: https://nwgat.ninja/quick-easy-compiling-mpv-for-raspberry-pi/. 

Text #1
ID                                       : 2
Format                                   : S_DVBSUB
Codec ID                                 : S_DVBSUB
Language                                 : Norwegian
Default                                  : Yes
Forced                                   : No

Text #2
ID                                       : 3
Format                                   : S_DVBSUB
Codec ID                                 : S_DVBSUB
Language                                 : Norwegian
Default                                  : Yes
Forced                                   : No

pi@raspberrypi:~/emby-theater-pi $ mpv /home/pi/Desktop/Parker.mkv 
Playing: /home/pi/Desktop/Parker.mkv
 (+) Video --vid=1 (*) (h264)
 (+) Audio --aid=1 --alang=nor (*) (aac)
     Audio --aid=2 --alang=nor (*) (ac3)
 (+) Subs  --sid=1 --slang=nor (*) (dvb_subtitle)
     Subs  --sid=2 --slang=nor (*) (dvb_subtitle)
File tags:
 Title: Parker
[ffmpeg/audio] aac: element type mismatch 1 != 0
AO: [alsa] 48000Hz stereo 2ch s16
[ffmpeg/audio] aac: element type mismatch 1 != 0
[ffmpeg/audio] aac: element type mismatch 1 != 0
[ffmpeg/audio] aac: element type mismatch 1 != 0
[ffmpeg/audio] aac: element type mismatch 1 != 0
[ffmpeg/audio] aac: element type mismatch 1 != 0
Using hardware decoding (rpi).
VO: [rpi] 1280x720 mmal
[osd/libass] PlayResX undefined, setting to -1
[ffmpeg/audio] aac: element type mismatch 1 != 0 

Share this post


Link to post
Share on other sites
haraldov

Sorry, but I forget to mention about  the issues with subtitles not showing.

I can see the norwegian subtitle with Emby Theater for Windows 2.5.32 and with mpv. 

When the same file play in Emby Theater for raspberry pi I can choose which subtitle I want (ID 2 or 3), but no text displays on the movie.

 

5862e0f44448c_Skjermbilde.png

 

Any advice for this issue? 

 

Some info about the S_DVBSUB subtitle.

https://tvheadend.org/boards/5/topics/848

http://ffmpeg.org/pipermail/ffmpeg-cvslog/2013-February/060202.html

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...