Jump to content

Search the Community

Showing results for tags 'RPI'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android
    • Android TV / Fire TV
    • Windows & Xbox
    • Apple iOS / macOS
    • Apple TV
    • Kodi
    • LG Smart TV
    • Linux & Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Testing Area
    • WMC UI (Beta)
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 6 results

  1. EliteArmedForce

    High CPU consumption

    #####Specs of Hardware used###### RPi 3 B+ OS: DietPi v6.29.2 Server installed in RPi 3 b+ Client: Mobile browser, Mobile app & PC browser Browser: Chrome latest version Emby App latest. Test done using "htop" command ################################### Attached Documents(Below) Using emby app (Mobile using emby app.jpg) Chrome mobile browser (Mobile with browser_2.jpg ....) Chrome PC (browser) Video details ################################## This rpi3 b+ is used for media server. I play various videos independent of the of its codec. Most of the time, i play H264 videos, as rpi3 b+ fails to play high bit videos of AVC/H 265 and often experience poor video playback. So, i planned to purchase new rpi 4 as it supports h265, but i stumbled upon something yesterday. I noticed that I was able to play Naruto episodes in emby mobile app smoothly without laggy playback issues that i used to get in using chrome(for video specs detail, check below)(screenshot attached below) Can anyone explain, how to fix this? and explain the problem?
  2. Hi Guys, actually I'm running my Emby on a Windows-Server 2012 R2 with a Core-i7 which is from the 3 or 4-Series. But since this costs a ton of electricity, I'd like to change this to a more energy-efficient alternative. While the new Raspberry Pi 4 seems to be very powerful, could I use this as an alternative for transcoding? (If I'm abroad, I sometimes transcode FHD-content to my mobile devices, but I often use FHD to FHD) Can anyone tell me if the RPi4 has enough power? If not, what energy-efficient alternative do you recommend? Regards, Matthias
  3. i would love to use emby server, if it working properly... I cant use Emby, because it crashing all the time. When i start a movie-after stop, then start other, the server is crashing. I tried playing this movies whit Plex and worked, but i dont like Plex. PLZ help me to use this awsome server!! My system: DietPi distribution on Raspberry pi 3, Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.4 (stretch) Release: 9.4 Codename: stretch Emby Version: Version 3.3.1.0 ffmpeg version: ffmpeg version 3.2.10-1~deb9u1+rpt1 Mono runtime version: Mono JIT compiler version 5.10.1.20 I see this on ssh session terminal, when crash is coming: Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.036759] Internal error: Oops: 17 [#10] SMP ARM Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.107391] Process Threadpool work (pid: 7323, stack limit = 0xb5f72210) Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.111531] Stack: (0xb5f73d98 to 0xb5f74000) Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.115609] 3d80: 00007f38 806d1600 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.119741] 3da0: 00082dcf b5f73ec0 b25757c0 00082dcf b5f73e54 b5f73dc0 806d1620 806ce01c Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.123787] 3dc0: 00007f38 801ed940 b3f06a6c b6fc814c 80c069c4 80d0a08c 80c049c0 b5f72000 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.127845] 3de0: 00000000 90a5e05c 00000001 00000000 00000001 00000000 00010000 00000000 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.131922] 3e00: 00000001 b2575910 0000054d 00000000 00000121 00007f38 7fffffff b5f73e28 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.135949] 3e20: 801235c4 801e0000 b25757c0 b25757c0 00202436 b5f73ec0 00000121 80108224 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.139882] 3e40: b5f72000 00000000 b5f73e74 b5f73e58 806d214c 806d1324 806d2114 b25757c0 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.143890] 3e60: 00000000 931c4fc0 b5f73e94 b5f73e78 806fe240 806d2120 802aa224 802aa178 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.147846] 3e80: 00000000 00000000 b5f73ea4 b5f73e98 80657950 806fe204 b5f73f8c b5f73ea8 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.151730] 3ea0: 80658aa0 80657938 b5f73ec8 80c82021 fffffff7 00000001 6de206f2 00202436 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.155590] 3ec0: 00000000 00000000 00000001 00082dcf 0017f667 b5f73eb8 00000001 801ee188 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.159462] 3ee0: 00000000 00000000 00000000 b5f73ef8 80101850 80123188 b5f73f00 b6802e00 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.163284] 3f00: 00000001 00400040 80c02d00 0002f04e 0000000a 80c918c0 80c823f0 80c03d68 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.167115] 3f20: 80b84378 80c02080 b5f73ef8 00000000 8017a470 80b8c92c 00000000 00000000 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.170902] 3f40: 00000001 b6804180 00202436 8012377c b5f73f6c b5f73f60 8012377c 80184560 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.174608] 3f60: b5f73f94 b5f73f70 801754d8 801236e0 b5f73fb0 76412d80 00000000 6de206f2 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.178380] 3f80: b5f73fa4 b5f73f90 80658af0 806589e4 00000000 00000000 00000000 b5f73fa8 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.182084] 3fa0: 80108080 80658ad4 76412d80 00000000 00000021 6de206f2 00202436 00000000 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.185758] 3fc0: 76412d80 00000000 6de206f2 00000121 00000000 01feac80 00380ee0 6f12a820 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.189398] 3fe0: 00000000 6f12a7a8 00000000 76e2b984 80000010 00000021 00000000 00000000 Message from syslogd@DietPi-Kodi at Apr 17 11:31:28 ... kernel:[ 2226.218091] Code: e155000c 03a05000 e2117902 1a000039 (e5d50028) AND when i check emby status, after crash: ● emby-server.service - Emby Media Server Loaded: loaded (/lib/systemd/system/emby-server.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-04-17 11:29:23 CEST; 7s ago Process: 6922 ExecStopPost=/usr/bin/emby-server clear (code=exited, status=0/SUCCESS) Process: 6673 ExecStart=/usr/bin/emby-server start (code=exited, status=134) Main PID: 6673 (code=exited, status=134) Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: Native stacktrace: Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: Debug info from gdb: Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: ================================================================= Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: Got a SIGABRT while executing native code. This usually indicates Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: a fatal error in the mono runtime or one of the native libraries Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: used by your application. Apr 17 11:29:23 DietPi-Kodi emby-server[6673]: ================================================================= Apr 17 11:29:23 DietPi-Kodi systemd[1]: emby-server.service: Unit entered failed state. Apr 17 11:29:23 DietPi-Kodi systemd[1]: emby-server.service: Failed with result 'exit-code'. THX! ServerLog.txt FFmpegLog.txt reinstalled_ffmpegLog.txt reinstalled_serverLog.txt MorningServerLog_2018_04_18.txt
  4. Hi all. I'd really appreciate a steer on where I'm going wrong with my Emby setup - it's becoming really frustrating! I have Emby Server (3.1.266.0 beta) set up in Lubuntu 16.04. My machine specs are as follows: i5 6600t HD 7950 3 GB 8GB RAM 1 TB 7200rpm HDD for media I have a powerline based home network using AV2 compliant adapters. I've tried a couple of different playback approaches - DNLA via my Bravia TV, Emby for Kodi on my RPi 2 and an old Android TV box (Minix Neo X7) but none work reliably. My media is really mixed in terms of formats and bitrates. I used to have an HTPC in the living room so had no problems with playback, but since moving to a server in another room I have had real trouble getting many things to play successfully. Higher quality files often stutter then fail and I have problems getting HEVC and other files to play at all at times. I'm happy that my network speed is decent - so I guess the issue is transcoding? I have used the Bravia 2014 profile in the past, but this didn't really help. Can someone please tell me what I need to look for in the logs? There's no info on profiles in the wiki so I'm a bit lost as to what to change to force transcoding and what settings would be best to ensure reliable playback. Attached are some recent logs - these will only show DNLA access via the TV I think Cheers ffmpeg-transcode-5b0315be-5855-4daa-8a47-e9bb820f6493.txt server-63618980178.txt
  5. hurricanehrndz

    ARM devices official instructions

    Instructions can be found on the Emby website: https://emby.media/download Our linux packages support ARM, as well as our Docker installation.
  6. Hello, I set up my Emby server on my desktop PC and it was all running perfectly, I've recently moved to using a Raspberry Pi 3 using the guide in the second post on this page: http://emby.media/community/index.php?/topic/27026-raspberry-pi/page-8 It all works fine, except no MKV file will play, I'm pretty sure this has something to do with ffmpeg, but I have checked that it is in the location that guide used. Any tips? EDIT: The error I get is a white box pops up saying Video Error: There was an error playing the video. I am accessing the server from a Windows 10 machine using Chrome, I don't think this has any effect as I have an identical server set up on this machine and the files play fine, and similar behaviour is shown when accessing the server from Android devices through Chrome. The error also occurs for .avi files I have attached the server log and a remux? log. remux_log.txt server_log.txt
×
×
  • Create New...