Jump to content

Search the Community

Showing results for tags 'Xpenology'.

  • 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

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 10 results

  1. solabc16

    XPEnology Users Read Me

    Hello and Welcome First, let me make the most important point, Emby Server is fully supported on XPEnology systems running DSM 5.2-5967 or later. If you're running an earlier version, check out the XPEnology forums for advice on how to update. We've had many XPEnology users update without issue and there are members of the community here who will also help, just ask. To reiterate what is detailed under Step #1 on the Synology setup page (https://emby.media/nas-server.html), please make sure you use this URL as your package source in Package Center:- https://synology.emby.media/?package_repository=360efc6e-de72-4073-b603-2bfbd7001586 Emby Server Won't Run Now, if you've installed the package successfully but it won't run, don't panic! We almost certainly know why that is, and I'll explain in detail below. If you're impatient and just want to get going, please run the two utilities listed below... Run Diagnostics : https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Run-Diagnostics Send Support Logs : https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs ...once the send logs utility has completed, post your details here along with the send logs file reference. What's the Problem? The CPU type and architecture reported by DSM when running on XPEnology is fake, which is due to it 'pretending' to be a DS3615xs. With the most recent phase of package development, we've optimised the toolchains we use to build the packages on an architecture-by-architecture basis, so as to get the best performance out of the hardware. This causes problems on the XPEnology front, as it can theoretically be running on any Intel or AMD x86-64 processor available. We have no way of knowing that it's an XPEnology system or the underlying processor type. The hardware that Synology groups under the 'bromolow' architecture, which includes the DS3615xs, contain either an Intel Xeon E3-1230 v2 or Intel Core i3-4130 processors. These are based on the 'ivybridge' and 'haswell' microarchitectures repectively. In terms of general CPU capability, this maps out as follows:- ‘ivybridge’ MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AES, PCLMUL, FSGSBASE, RDRND, F16C ‘haswell’ MOVBE, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AVX, AVX2, AES, PCLMUL, FSGSBASE, RDRND, FMA, BMI, BMI2, F16C So, for Synology hardware identifying as 'bromolow', we target the 'ivybridge' microarchitecture as the lowest common denominator. If the processor you're running XPEnology on supports these CPU features, then you're going to 'get away with it' and it will work. We may however, not be taking advantage of all the capabilities your processor has to offer. The first time we came across an issue was with the Intel Pentium G3258 processors, as these do not support the AVX feature (see above). This is the point where we decided to split the XPEnology and Synology builds and give XPEnology a dedicated repository, which you'll see in the setup guide on the main website. Our default target now for XPEnology systems is the 'nehalem' microarchitecture, which supports the following features:- ‘nehalem’ MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT Later on, we came across the Intel Core2 Duo E7200, which doesn't support SSE4.2 or POPCNT, again causing Emby Server to not start. The lowest common denominator of Core2 based processor doesn't support SSE4.1 either, so we could have dropped our baseline from 'nehalem' to 'core2', which would have given:- ‘core2’ MMX, SSE, SSE2, SSE3, SSSE3 However, our objective is to make Emby Server run as well as it possibly can, so this wasn't really a path we were willing to take; although it would have certainly been the easier one. For that reason, we enhanced our package server to allow a package architecture to be specified as part of the package source and added the ability to create additional platforms to our toolchain, in this example for Core2 processors with SSE4.1. This gives us the flexibility to support processors that are less capable than our default ('nehalem') and further optmise for processors that are better than our default in the future. Best - James
  2. FaNaTiK

    XPEnology error

    Hello. Please help. My page with Emby server does not open I have XPENOLOGY DSM 6.2-23739 on INTEL ATOM D525. It is displayed as INTEL Xeon D-1527 in DSM. I installed Emby server, using https://synology.emby.media/?package_repository=360efc6e-de72-4073-b603-2bfbd7001586 repo link. When I start the server, the page opens in the browser, but it gives an error that it is not available. And yet, after installation, the server does not start on its own, I start it, after that an icon appears in the main menu, but after a few minutes it disappears. What me to do?
  3. lesensei

    Unable to stream some movies

    Hello, I've been happily using Emby (with Premiere) on a XPenology NAS for a few years now, and recently seem to have hit a bug. When I try to play some movies of my collection, I hit the "Aucun flux compatible n'est actuellement disponible." (please pardon my french setup, this would be "No available stream" or something like that in english). I looked at the attached logs, tried to launch the "actual command" and sure enough, got the same error before ffmpeg quits: Stream specifier ':3' in filtergraph description [0:3]scale@f1=width=720:height=-2:force_original_aspect_ratio=decrease[f1_out0];[0:0][f1_out0]overlay@f2=x=(W-w)/2:y=(H-h):repeatlast=0[f2_out0] matches no streams. Just in case, here's the output of ffprobe on the file: ffprobe version 4.3.0-emby_2020_02_24-20200406T210855UTC Copyright (c) 2007-2019 the FFmpeg developers and softworkz for Emby LLC built with gcc 7.3.0 (GCC) Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/volume1/video/redactedfilename.m4v': Metadata: major_brand : mp42 minor_version : 512 compatible_brands: isomiso2avc1mp41 creation_time : 2017-10-22T20:12:17.000000Z encoder : HandBrake 1.0.7 2017040900 Duration: 02:05:05.32, start: 0.000000, bitrate: 1089 kb/s Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, smpte170m/bt470bg/bt709), 720x426 [SAR 64:45 DAR 512:213], 756 kb/s, Level 31, 25 fps, 25 tbr, 90k tbn, 180k tbc (default) Metadata: creation_time : 2017-10-22T20:12:17.000000Z handler_name : VideoHandler Stream #0:1(fra): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 160 kb/s (default) Metadata: creation_time : 2017-10-22T20:12:17.000000Z handler_name : Stereo Stream #0:2(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 160 kb/s Metadata: creation_time : 2017-10-22T20:12:17.000000Z handler_name : Stereo Stream #0:3(fra): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 720x576, 1 kb/s (default) Metadata: creation_time : 2017-10-22T20:12:17.000000Z handler_name : SubtitleHandler Stream #0:4(eng): Subtitle: dvd_subtitle (mp4s / 0x7334706D), 720x576, 2 kb/s Metadata: creation_time : 2017-10-22T20:12:17.000000Z handler_name : SubtitleHandler Stream #0:5(eng): Data: bin_data (text / 0x74786574) Metadata: creation_time : 2017-10-22T20:12:17.000000Z handler_name : SubtitleHandler Unsupported codec with id 100359 for input stream 5 Any idea what I can do to make this work again (I'm pretty sure it has worked in the past) ? Thanks for your help. ffmpeg-transcode-8b813c11-e81a-4a0b-876d-a6cf032d5a2f_1.txt
  4. Hello All If you've been following the XPEnology support threads closely, you'll know that we work hard to make sure you get a great experience with Emby Server on this platform. You're also likely aware there are a number of loaders available now, when we started there was only one and that was based on DSM 5.2. Please can you drop us a line here and let us know what loaders you are currently running with, so we can look at how best to develop and optimise the Emby Server package going forward. Best - James
  5. Folks, I wanted to verify Emby Server (Haswell build) was running properly on my XPEnology rig, so I ran the diagnostic steps posted HERE and it discovered a few issues. See here for the diagnostic logs: sendlogs_TinyPC_synology_apollolake_918+_20190325T013306UTC.tgz In an attempt to fix the issue, I installed ImageMagick courtesy of SynoCommunity, then I restarted DSM and reran the diagnostics, but unfortunately no change. So, any advice you can provide on the reported issues and how to resolve them, would be greatly appreciated. --Cheers! MardukNT
  6. I'm looking for some under the hood info - from advanced users that have built a multi-client environment. My existing system is pretty basic, as I like to keep things simple, and in the event of a problem I don't have to muck through a maze of "how did I do this again?" I have a Synology NAS - that provides all the storage for my media files. Using all the built-in 'add video' sources within Kodi - linked to my NAS. I've also enabled a MariaDB10 app, on the NAS to support the MySql feature within Kodi - so all my clients (multiple FireTV & PCs (Windows,MAC)) sync to the same dB. This all works quite well, however a bit complex configuration on each client to maintain if I make the same change or add a source, etc. So here's where my questions begin... I've installed Emby Server on one of my Synology NAS boxes, actually, this particular one is an Xpenology device. I chose that one because it has much more HP than my official Synology boxes. I've also purchased a lifetime Emby account. I've built a Kodi (18.1) client on one of my Fire TV televisions - from scratch. Installed the basic Addons that I require for my use ... OpenSubtitles, Trakt, Lyrics & Backup. I've also just installed Emby/con - addons. After running and testing - to the Kodi local dB all seems to be working well. I'm not sure how the updates to the local client dB updates, and if there is by directional flow when it comes to Trakt data, and partially watched positions, etc... Would it be better to switch to using the Mysql as a common dB source for my clients as I did before? or just stick to the Kodi local dB file dB? I'm thinking using the Mysql dB would be a bit redundant and just complicate things. That I should just let Emby do all the dB work, and keep the local client dBs updated. any HELP, feedback and or comments would be welcome. So far I'm pretty impressed with Emby server.
  7. Hello All Starting with stable release, we now default to Skia for image processing on Intel/AMD based Synology/XPEnology installations. This will see the performance of Emby Server's native image processing, along with that provided by the CoverArt plugin, significantly improved. Support for other models will be coming over the next couple of weeks, I'll post details here when the releases become available. For reference, here's a snapshot from testing on an Intel Atom based system:- Any questions, issues or comments please post them here... Best - James
  8. chattojimnow

    Next Synology Update

    Hi @solabc16 When will the next update for emby be as the Version is giving me nothing but issues Dropping out is the major issue. Becomes hidden from my network and to get it working I have to stop and start the server in synology. Anyone else having this issue?
  9. chattojimnow

    DS3615xs No icons

    Hi, has anyone else had the same issues as me with the icons on the admin menu since the 3.2 updates also the resume or start again option is gone it only resumes the media
  10. Hi, some time ago I rescheduled all my scheduled tasks to run at certain times in the night. This was with 3.0.85. After having upgraded to 3.1.2 it seems that the times which I set are now gone and are reset to the default. This seems to be me like a bug - what do you think? I am using the official xpenology build repository. Thanks in advance!
  • Create New...