crashes to home screen

[rastinmajera 0]

To try and make a long story short.  I keep my freenas box and the two rokus in my house on a private network that doesn't have internet access.   My son put one of the rokus online, it updated the emby app.  This stopped it from logging into the server as it needed a new version of the server.  The newer version of the Emby server needed a newer version of freenas to work.  I updated Freenas to the newest version 11.2, installed the newest emby from it's plugin menu.  Both rokus see and login fine, but when you play any video on either of them, they crash back to the home screen.  I am at a complete lose here, I've uninstalled the app on the roku, freenas and reintalled, nothing seems to fix this problem.

[Luke 37060]

Hi there, can you please attach the emby server log? thanks !

[Happy2Play 8281]

Can you post the server and ffmpeg log if any.

[rastinmajera 0]

I'll look for those and upload them when I get home.  thanks

[Happy2Play 8281]

 

I keep my freenas box and the two rokus in my house on a private network that doesn't have internet access

 

Might have to list Emby Roku channel/app version number also.

[speechles 1917]

hmmm...

 

The version of the app would help as there was an earlier bug regarding items without truly playable streams that we since corrected. Basically if permissions weren't correct or other issues caused the stream to exist but not be playable it crashes the app. We since the fixed that bug. The app now reports there are no playable streams and errors in app.

 

The Roku store holiday blackout has stopped their publishing until January 2nd (today). They might not have pushed the new store app out yet.

 

The Beta version (Emby Beta for Roku) of the app should now give an error reporting what happened rather than crash the app out. It also has several other fixes users reported during the blackout period.

 

Knowing server and app version this occurs on we might have already fixed the issue. Server logs too would help us better know how to help you. Apologies you can't enjoy things yet.

Edited January 2, 2019 by speechles

[rastinmajera 0]

Ok made it home, the emby server version is 3.5.30, emby app on roku show 3.0.128.  I think I just got it working, not sure it's the right way to fix my problem, but I can now play movies again.  I looked in the ffmpeg logs and found this listed. 

 

2019-01-02 19:07:00.598
Application version: 3.5.3.0

http://192.168.69.4:8096/emby/videos/3f841a7769c2264e0c8988abb77c65e1/live.m3u8?DeviceId=e44c40f7-dbd7-5b7f-ae12-cce3c982b634&MediaSourceId=3f841a7769c2264e0c8988abb77c65e1&VideoCodec=h264,mpeg1video,mpeg2video,hevc&AudioCodec=ac3,aac,mp2,mp3,flac,opus,vorbis,lpcm&VideoBitrate=9808000&AudioBitrate=192000&MaxFramerate=61&MaxWidth=3840&MaxHeight=2160&PlaySessionId=0357fed1e1d3456aacdcda7dd018e58a&api_key=410916461d734b27816c926f68cd409d&TranscodingMaxAudioChannels=6&RequireAvc=false&Tag=1aeaad454be4218cf4999cf25e9a02a6&SegmentContainer=ts&SegmentLength=3&MinSegments=1&BreakOnNonKeyFrames=True&h264-maxrefframes=16&h264-videobitdepth=8&h264-profile=high,main,baseline,constrainedbaseline&h264-level=51&aac-audiochannels=6&ac3-audiochannels=6&flac-audiochannels=6&lpcm-audiochannels=6&mp3-audiochannels=2&mp2-audiochannels=2&vorbis-audiochannels=6&opus-audiochannels=6&TranscodeReasons=ContainerBitrateExceedsLimit

{"Protocol":"File","Id":"3f841a7769c2264e0c8988abb77c65e1","Path":"/media/movies/Bad_Boys_1995.mp4","Type":"Default","Container":"mp4","Name":"Bad_Boys_1995","IsRemote":false,"ETag":"1aeaad454be4218cf4999cf25e9a02a6","ReadAtNativeFramerate":false,"IgnoreDts":false,"IgnoreIndex":false,"GenPtsInput":false,"SupportsTranscoding":true,"SupportsDirectStream":true,"SupportsDirectPlay":true,"IsInfiniteStream":false,"RequiresOpening":false,"RequiresClosing":false,"RequiresLooping":false,"SupportsProbing":true,"VideoType":"VideoFile","MediaStreams":[],"Formats":[],"RequiredHttpHeaders":{}}

User policy for MANCAVE: EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True

/usr/local/lib/emby-server/bin/ffmpeg -f mp4 -i file:"/media/movies/Bad_Boys_1995.mp4" -map_metadata -1 -map_chapters -1 -threads 0 -sn -codec:v:0 libx264 -pix_fmt yuv420p -preset veryfast -crf 23 -maxrate 9808000 -bufsize 19616000 -profile:v high -level 4.1 -x264opts:0 subme=0:me_range=4:rc_lookahead=10:me=dia:no_chroma_me:8x8dct=0:partitions=none -force_key_frames "expr:gte(t,n_forced*3)" -vf "scale=trunc(min(max(iw\,ih*dar)\,1920)/2)*2:trunc(ow/dar/2)*2" -flags -global_header -vsync -1 -codec:a:0 ac3 -ac 6 -ab 192000  -f segment -max_delay 5000000 -avoid_negative_ts disabled -start_at_zero -segment_time 3  -individual_header_trailer 0 -segment_format mpegts -segment_list_entry_prefix "hls/eab61560071d47975972f28ab3dbe413/" -segment_list_type m3u8 -segment_start_number 0 -segment_list "/var/db/emby-server/transcoding-temp/eab61560071d47975972f28ab3dbe413.m3u8" -y "/var/db/emby-server/transcoding-temp/eab61560071d47975972f28ab3dbe413%d.ts"

Shared object "libx264.so.152" not found, required by "libavcodec.so.58"

 

I then went into the settings for "mancave" and turned off the settings Allow audio playback that requires transcoding Allow video playback that requires transcoding Allow video playback that requires conversion without re-encoding.  It now plays fine again.  I assume this means I am missing something with the ffmpeg setup?  Anyway it's working now.  I would like to know if I need to fix this problem, so I won't run into anything in the future.

 

Thanks

[Happy2Play 8281]

Can you post the ffmpeg log.

 

Will have to search but I believe this is reported elsewhere.  OS specific.

Shared object "libx264.so.152" not found, required by "libavcodec.so.58"

[Luke 37060]

Hi, the issue is the same as here (different Emby app but same root cause):

https://emby.media/community/index.php?/topic/65333-cant-play-music-or-movies-through-web-browsers/

Thanks.

[rastinmajera 0]

Ok so if I follow that thread correctly, I have a about 3 options.  1. turn off the trans-coding, turn down my roku resolutions  2. wait for 3.6 to come out.  3.  follow the instructions for changing the ffmpeg version by manually installing and changing the startup script or uninstall emby and use your special instructions to put it back with the right libs?

 

update:

 

Well I guess I will wait for 3.6 to come out of beta.  I tried the ffmpeg manually and changing the script, didn't work got a error # 1.  Can't find a fix for that.  Is there an idea on when 3.6 will be ready?

 

OR

 

Can I just remove my current emby install and do the following to end up with a package that will work? or does this version have the same problem that I am currently stuck with?

 

cd /tmp
wget https://raw.githubusercontent.com/bott0r/iocage-plugin-emby/master/emby-server.json
iocage fetch -P dhcp=on vnet=on bpf=yes allow_raw_sockets=1 -n emby-server.json --branch 'master'

 

Thanks

Edited January 5, 2019 by rastinmajera

[Luke 37060]

Going forward with 3.6, once it goes stable, you will not need to worry about configuring the ffmpeg build anymore. Please let us know if this helps. Thanks !