Jump to content

Search the Community

Showing results for tags 'odroid'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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 Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • 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
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support


  • Emby Blog


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 5 results

  1. nwcatalyst

    Add HW Encoding for ODROID C2

    As discussed in this thread, would like to add HW encoding support for the ODROID C2. Another developer from the Hardkernel community has created a program that does the video encoding. We would just need team emby to create the code to re-pipe this into ffmpeg... The C2 would be an awesome and fully capable $40 emby box with this ability (for me, anyway... only looking to do a single 1080/720 stream). Thanks,
  2. I'm using an ODROID C1+ with OpenELEC as a client device. This device is listed as 'Device X' and connected with the user 'A' with Emby. I'm also using different computers as clients. Everything is fine. I recently added a new client device, an ODROID C2 with LibreELEC. Let's say I call it 'Device Y' and I connect it with the emby user 'B'. The problem is that 'Device Y' doesn't list in emby devices and is not active. Even worst, when I reboot the server, it says that 'Device X' is connected with user 'B'. I can use both devices just fine but it's a mess since it changes the viewed contents of both users randomly. 'Device X' is local and 'Device Y' is outside homenetwork though. How to restart all the device ID's or what's the problem? I tried to change the MAC addresses but it doesn't work. Deleting the visible device in the list doesn't seem to work also. server-63619576295.txt
  3. hardkernel and their suppliers are selling very cheap pcb running Ubuntu 14.04 with a Samsung Exnyos 8 core processor 2gb of ram and many other features for under $100. These are very fast I have an eval with my work for some projects. Is there any chance that the nas versions can be compiled with the switch to support the big.LITTLE endian architecture so it can be tested? These are way cheaper and many times more powerful than all the rather pricey NAS units out there. I'd love to test it if you can throw one out there. The Ubuntu image that comes with the odroids are fully dev capable so dependencies shouldn't be any issue at all. Steve
  4. I was having issues getting emby installed on my odroid. No matter what I tried the actual emby plugin would not even show up in repo lists. I tried the official odroid lubuntu images as well as several openelec versions. My solution was to check for updates before and after installing the repository. If I did not do it first I think it cached a dependency error and ignored emby. Then since nothing actually changed it would never fully check the emby plugin for compatability again. It looks like kodi checks md5 sums to see if there are any changes. I think it has something to do with the fact these images we write to the device were pulled from a working device. Kodi is not treating it like a first run and therefor is not trying to cache or update anything. If you have already installed the repo, uninstall the REPO and delete your addons DB file. (.kodi/userdata/Database/addons*.db.), restart the device and from the settings>addons menu press the left arrow and select Check For Updates, Now install the repo and check for updates again. You should now be able to go to settings>addons>Install From Repo>Emby for Kodi Repo>Video Addons>Emby>INSTALL! You might be able to skip deleting the database file, I have not tried yet. There may be delays too. I had to update after installing the repo twice before anything showed. On my second Odroid I updated before installing the repo and after and emby was right there and installed with no issues. This only seems to happen if you try to install before doing anything else with kodi. If I had browsed or added an addon before it would have likely worked fine. Maybe even just having the device running long enough to get an updated time and date.
  5. I didn't find any correct Dockerfile or instructions on how to install Emby on top of armhf architecture so I had to combine some of them and as a result here is working Emby Docker image - https://hub.docker.com/r/kayrus/emby/ I've tested it on my Cubietruck with Debian Wheezy and Linux kernel which supports Docker (>=3.6). For example Armbian for Cubietruck has Linux kernel v4.2.3. In any case even if you don't have Docker you can try to install Emby just following Dockerfile manually. What doesn't work: direct play for all my h.264 MKV videos using web browser (for example direct play of the same videos works perfectly on Plex - https://hub.docker.com/r/kayrus/plex/). I don't know how can I force Emby to disable transcoding for MKV, but it works and it is really slow. Direct play of the h.264 inside the MP4 container works fine. Details on this image: I had to cross-compile ffmpeg, libvidstab1.0 and libx265-59 packages from this PPA repo: https://launchpad.net/~mc3man/+archive/ubuntu/trusty-media/+packages. These packages are available inside the image in /tmp/deb directory. You can compile them yourself using armv7/armhf-ubuntu:14.04.3 Docker image if you wish. Here are basic instructions: Enable multiverse repo: deb http://ports.ubuntu.com/ubuntu-ports/ trusty main restricted universe multiverse deb http://ports.ubuntu.com/ubuntu-ports/ trusty-updates main restricted universe multiverse deb http://ports.ubuntu.com/ubuntu-ports/ trusty-backports main restricted universe multiverse deb http://ports.ubuntu.com/ubuntu-ports/ trusty-security main restricted universe multiverse apt-get install build-essential autoconf libasound2-dev libass-dev libbz2-dev libfdk-aac-dev libfreetype6-dev libmp3lame-dev libopencore-amrnb-dev libopencore-amrwb-dev libopus-dev libpulse-dev libsdl1.2-dev libsoxr-dev libspeex-dev libtheora-dev libva-dev libvdpau-dev libvo-aacenc-dev libvorbis-dev libx11-dev libx264-dev libxext-dev libxfixes-dev libxcb-shm0-dev libxcb-xfixes0-dev libxvidcore-dev libxvmc-dev texi2html zlib1g-dev cmake python-sphinx debhelper libgsm1-dev libiec61883-dev libavc1394-dev libjack-jackd2-dev liblzma-dev libmodplug-dev libopenal-dev libopenjpeg-dev librtmp-dev libschroedinger-dev libsctp-dev libshine-dev libsnappy-dev libtwolame-dev libvo-amrwbenc-dev libvpx-dev libwavpack-dev libwebp-dev libzmq3-dev libzvbi-dev texinfo yasm cleancss doxygen node-less Build instructions: * dpkg-sorce -x package_name.dsc * cd package_name && dpkg-buildpackage -b * install missed dependencies if necessary build x265 package from wily sources: http://packages.ubuntu.com/wily/x265 build libstab from https://launchpad.net/~mc3man/+archive/ubuntu/trusty-media/+packages sources: https://launchpad.net/~mc3man/+archive/ubuntu/trusty-media/+sourcepub/5273238/+listing-archive-extra dpkg -i libx265-dev_1.7-4_armhf.deb libx265-59_1.7-4_armhf.deb libvidstab1.0_1.0~trusty1.3_armhf.deb libvidstab-dev_1.0~trusty1.3_armhf.deb Then download ffmpeg and compile: https://launchpad.net/~mc3man/+archive/ubuntu/trusty-media/+sourcepub/5734739/+listing-archive-extra Install packages: dpkg -i libx265-59_1.7-4_armhf.deb libvidstab1.0_1.0~trusty1.3_armhf.deb ffmpeg_2.8.3+git1~trusty1_armhf.deb || apt-get install -fy Image size is approximately 315Mb. Mono takes lot of space. You can also find example Systemd unit file on image description page.
  • Create New...