Search the Community

I thought DS918+ was the best all-round one to use. It'll mainly be used for SS and Plex, I'm not sure if DVA1622 can do the transcoding?

ok so i was referring to my baremetal system here which is based on intel i3-8100. But that is only relevant for the HW video transcoding portion. As for TCRP build, most people use the "serialgen" command of tcrp, which generates serial/MAC combo. These are not REAL serials/MAC and has no impact on network connectivity. However in my case, i was looking to install and actviate synoloyg's advance media codec pack. Which ony works if i use REAL synology serial and MAC combo. So for that i used that info in my tcrp build, no other reason.

synology usually uses its own oem area in the mac (1st half) so the mechanism might be bound to that and the tools you may find are usually working the other way around (create a SN and create a mac for it) as we are not "supporting" these things here, dsm itself runs fine without it and there are other ways to get hardware transcoding working (patching files) https://xpenology.com/forum/announcement/2-dsm-serial-number-must-read/ you can use a search engine and start with "Synology SN Tool" (keep the " ") maybe digging a little can give you information you are looking for OR if its a more business oriented use of DSM, maybe consider buying some of the products (the last one is more rhetorical as the licensing terms seem to prevent this imho, but that depends you your country and point of view too)

Thank you very much, with this patch I finally managed to enable Plex hardware transcoding

I personally like the idea of bare metal builds, but virtualization has it benefits. 1- Yes you can install the latest DSM on most hardware 2- You have to use a USB to build the loader and to boot into the DMS. I have has issues bending or breaking a USB that sticks out, so you either need to purchase a low profile USB or get a dongle and keep it inside the case. 3- The installation of DSM has been stable for me since I upgraded from 6.2 to 7.x.x 4- All of the features are available for use with your original serial number 5- Yes you can use the Synology mobile apps (see # 4) 6- With the new loaders updates are not an issue like in the past. With your plans to expand in the future and if you are not looking for hardware transcoding, try the DS3622xs+ or the DS1621+(which is built on a Ryzen CPU) Have a look at this for hardware and platforms you can use: Then choose your loader creation method. TCRP is the best way to learn the process, but a lot has changed... so please read as much as you can:

What the hell. That worked. I didn't even have to enable transcoding, as it was already on. It took me longer to install because I lost my flash drive for 3 hours, than it did to just install Plex and... Wow. I think what happened was, my first install was on a spare AMD that I put 3615 on, then migrated to a DS920 install, but it must've not installed the drivers because it didn't work, and neither did a clean 918 install, but this one sure did. Thank you so much. I've been pulling my hair for 2 weeks on this. Deep down, I knew the solution was going to be super simple, as it so often is. I'm just glad it's over.

DS920 is the way to go. I was using arpl the last beta and that's it. Nothing to do except enabling hw transcoding in plex settings.

Is there a process you followed to enable hw transcoding on your j5040 with Xpenology? I get like 99% CPU, which means QuickSync isn’t working. PlexPass and everything. 90% of the time I’ll be direct playing, but I just want to transcode remotely to my partner’s laptop on occasion. I switched from DS920+ to DS918+ thinking that could be the issue, but no dice.

also die 3622 läuft auch mit ryzen,, das einzige das mit einfällt was dann nicht geht wäre VMM (aber den verwenden nicht viele da die performance eher schlecht ist) das wichtigere ist nach den unterstützten cpu kernen zu schauen https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ die 923+ wir imho derzeit von keinem loader unterstützt (und wird es evtl. auch nicht da es keine vorteile gegenüber den anderen hat, die 918+/920+ waren wegen hardware transcoding mit intel quck sync video inetressant, das hat/kann die 923+ nicht, im moment wird die arbeit eher in die amd epyc bsasierte sa6400 fließen, die kommt als erst 7.1 mit kernel 5.x und das wird dann auch die notwendige vorarbeit zu 7.2 sein die dann für viele alten units auch kernel 5.x bringen soll - aber hier sind wir dann auch schon im märchenland da der loader die sa6400 noch nicht kann und 7.2 erst in q2/2023 zu erwarten ist) eine einfache methode zu schauen was an system und dsm version vom tcrp loader unterstützt wird ist mal bei einer extension (aka treiber) rein zuschauen https://github.com/pocopico/rp-ext/tree/main/e1000e/releases und synology hast eine schöne übersicht parat welche unit mit welcher cpu kommt https://kb.synology.com/en-global/DSM/tutorial/What_kind_of_CPU_does_my_NAS_have aber wie gesagt, eine amd unit als basis ist nur zwingend wenn man vmm nutzen will

what show your NAS with this command? cat /usr/syno/etc/codec/activation.conf You can force install codecs if you use Videstation and play with hw transcoding.

Hi, What version should I be installing on a Terramaster f4-423? I tried a while back, but was never able to find it on the network or synology finder. Processor Model Intel® Celeron® N5105/5095 Processor Architecture X.86 64-bit Processor Frequency Quad Core 2.0 GHz (Max burst up to 2.9) Hardware Transcoding Engine H.264, H.265, MPEG-4, VC-1;maximum resolution: 4K (4096 x 2160); maximum frame rate per second (FPS): 60 Memory System Memory 4GB Pre-installed Memory module 4GB (1 x 4GB) Total Memory Slot Number 2 (DDR4 SODIMM) Maximum Supported Memory 32 GB (16GB+16GB) Disk Slot Number4

@blackmangaHi I had been banging my head for weeks to try to get HW transcoding to work in plex on my ds918 xpenelogy , DSM 7.1.0 42661 with TCRP loader, setup. i think your thread here is prbably the closes im getting to making it work. I have a mini pc with lntel N5095A processor. I have copied over the .ko fies from your first post here. What i dont understand, do i need to copy over some firmware bin files also? So far i did run your scripts, but dont think they worked on my setup because the /dev/dri is still missing. Therefore i wondering if need to copy over some bin files before running your scrut. Would really appreciate your help here. THanks

Just to +1 the above reply. The key to transcoding is not to transcode! (especially with 4k content) I put all my 4k TV and movies in a separate library so my users who don't have 4k capable hardware know not to play them. Transcoding 1080p and 720p material is a lot less CPU intensive. But as my server is hosted somewhere with plenty of upstream bandwidth I encourage my users to set their clients to *not* transcode remote material if their home internet connections can handle it.

Well I was able to sort my own issue. By using sataport map of 22 and disk Id of 00. ps. Would some have any pointers for me to get hw transcoding to work under ds918,dsm 7.1 setup. Using real Mac and serial. Even have synologys advanced media codec pack installed and activated. I seem to be missing the /dev/dri directory.

HW transcoding is overrated if you have good CPU (which you have). Picture quality is much better if you use cpu only. I know that hw transcoding is a kind of holly grail of every media server, but, nowadays we have so many devices which support direct play, so, overrated. But in case if you want save power (electricity bills) that's another story. I'm using j5040 Asrock (10 wats only) for hw transcoding to spare some energy. A matter of choice.

DS3622xs seems to be the most common platform, unless you want hardware video transcoding then ds918 seems to be the way to go.

Hi all Currently using ARPL as the loader with DS918+ as the model and using the latest pat file. Everything is working fine so this question to the masses is me just being curious. I see a lot of comments around the use of one of the later models for the pat files with a number of them referring to DS3622xs+. Can anyone advise why people would change their installation to use 3622 over DS918+? I am running my server on a repurposed Dell Optiplex 9020 SFF with a core i5 CPU. Software wise, the only thing I think of significance would be that I run Plex Media Server and believe the CPU has enough grunt to do hardware transcoding. Any views or thoughts on this one? Cheers

Thanks. I'll at least view the grub config to check. Any chance you think this could affect boot? I know that's a dumb question to ask. I'm essentially looking to convert my ds3622xs+ to a ds920+ to enable HEVC support and also HW transcoding in Plex. I have a feeling the model convert part can't be done remotely as that probably requires a loader rebuild?

its not normal to to things like that, so there are things in place to prevent that "just load" was not meant to be loading any extension, it was more low level like extracting the kernel module (*.ko) file, copy it to a place in the system partition and load it manually with "insmod", just to test if its working or not, apollolake and geminilake use the same kernel and are more or less the same when it comes to the cpu, so kernel settings used to compile the kernel and its modules will be the same, usually its very strict handled and you would only use modules compiled with the same kernel version and even the same settings but depending on the case the settings thing can be less of a problem (you might run into more problems if you use kernel modules made for a different system like a ryzen based unit in theory there is not much difference between 918+ and 920+, so you could migrate (for now) to 918+, use the drivers you need and if 920+ gets the driver you need or any other unit is more interesting you can migrate to that going to 918+ can be done more "by the book" with a normal howto and would only have steps you have already done before (if you hat 3622 before 920+) if you go 918+ you might need to redo steps about codes and hardware transcoding as it would be a new install (files in the system partition are overwritten) and if you generated/used a 920+ special serial number then you need a new one for 918+

the list of units supported is not static, so there is not ultimate answer (especially if there would be a dsm *.pat for a unit with kernel 5.x like maybe use syno own website, in the compare you can check anything above 8 (like 12 and above, https://www.synology.com/en-global/products?bays=12%2Cmore12) and see all units potentially needing syno's own drives, just check that against the list of the loader you intent to user, there is more then one loader, tcrp and arpl come to mind first but you might find other git's and sources to derived versions the often used 918+ and 920+ (hardware transcoding with some intel cpu's) are 4 bay units and will not have that but from my point of view i might not bother about that as long as i can add my own drives into the list like the yet unreleased unit with epyc7002 (maybe the SA6400?), i guess that might be adapted fast as it would offer some interesting features when it comes to hardware support one problem with changing the database of drives might be that after a update the drive database will jump back to syno's standard, your volume will be seen as "warning" and you need to add your drives again to get it back to normal as long as it not breaks anything with the update i don't see much of a problem and might be more looking to whats the best unit for my purpose and hardware

No worries, thanks for responding. And Surveillance Station uses your AMD CPU for transcoding as well?

Does baremetal based on ds3622xs+ not support intel quicksync for HW video transcoding(for plex)? EDIT: ignore. guess i found the answer on the DSM 7 loaders page, theres a table there that shows this model not support intel quicksync. A follow up question. Can quicksync support be enabled in the ds3622 model somehow?

@fbelavenuto I saw on your github that You added i915 addons two days ago. Does that mean that are drivers for enabling hw transcoding on newer gen of cpu's? I have 10th gen i3.

- Результат: Успешно - Версия и модель загрузчика: JUN'S LOADER v1.04b - DS918+ - Версия DSM: DSM 6.2.2-24922 - Дополнительные модули extra.lzma: YES (extra918plus_v0.8_syno.zip: extra/extra2 + Zimage + rd.gz из этой темы). - Аппаратное решение: H410M S2H V2, Core i5-10400 (встроенное видеоядро есть), чипсет Intel H470, сетевая Realtek RTL8118AS (AIDA выдала Realtek RTL8168/8111). - Короткий коментарий: завелось без проблем при четком соблюдении инструкции этой темы (версия 6.2.2 и т.д., выше написал). Hardware Transcoding не проверял. Завести на нем не удалось JUN'S LOADER v1.03b - DS3615xs. Не видит сеть даже с extra.lzma.

Спешу поделиться результатами. Итак, резюмирую. Может быть, кто-то сэкономит массу ценнейшего ресурса под названием "время", прочитав мой поток сознания На запасной платформе ITX J1800 относительно просто удалось запустить DS3615xs DSM 6.2.3-25426 с сохранением всех данных. На существующей платформе Core i5-3570 Asus Z8P77 после многих-многих часов мучений удалось полноценно запустить DS3615xs DSM 6.2.3-25426 с сохранением всех данных (собственно, эта версия и была до аварии). Однако, на этой платформе как-то странно работает БИОС. Я его даже обновил - ничего не изменилось. То есть я просто не вижу, пошла загрузка с флешки или нет. При этом зайти по DEL в настройки могу, и картинка есть. Настройки графики 100 раз менял: iGPU, PCI, PCIe, Auto - бесполезно. Также у меня закралось подозрение на работу SATA на этой MB. То ли проблема с контроллером, то ли с драйверами, то ли с самими разъемами. Там два серых порта, 4 синих. Изначально я использовал синие (это сейчас я вычитал, что серые 6Гбит, синие 3Гбит). Больше года назад поставил корзину - была идея делать вторичный бэкап на съемный HDD. Сначала вроде успешно прошло. А спустя месяцы втыкаю HDD - а у меня повреждение раздела (делал с выключением питания, не на горячую). Разумеется, первое под подозрением - корзина. Я купил другую, чуть покруче. Но и с ней рандомно происходили чудеса - всё та же ошибка "Повреждение раздела". Причем, не только на диске в корзине, но и на рандомном стационарном диске (их три). При этом в большинстве случаев удавалось просто нажать "Восстановить" - и моментально система становилась "ОК". Но вот в последние пару случаев мне выдало ошибку: на WD Black обнаружены поврежденные секторы, а на WD Red - просто отказ системного раздела. WD Black я отдельно прогнал Victoria полностью, несколько часов. Вообще ничего. Время доступа отличное. Ни одного блока с повышенным временем. SMART отличный. Ладно, отложил до лучших времен. WD Red до сих пор - отказ раздела, этот винт я использовал для своих экспериментов с DSM - много раз форматировал ему 1 раздел. Сейчас данные с него доступны, но отказ раздела вылечить не знаю как. В общем, слишком много подозрений: внезапная авария, странности с БИОС, подозрения на SATA - по совокупности факторов я принял решение перейти на новую платформу. Эксперименты со старой платформой отнимают колоссальное количество времени. Приобрел связку на i5-10400. Чего я только ни пытался: DS918+, DS3615xs - либо постоянно крашится при установке (ошибка 13), либо вообще не виден в сети. Я уж драйвера extra и extra2 разные ему подсовывал на флешку - бесполезно. Потом еще раз внимательно почитал вот эту тему https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ Чуть отдохнул, собрал мозги в кучу, еще раз внимательно прочитал - и увидел две главные штуки: что нужна версия 6.2.2; и что нужны zImage и rd.gz от 918+. После этого создал флешку. Выбрал DS918+ DSM 6.2.2 И без проблем сначала на тестовом WD Red удалось завести систему, а потом и с остальными дисками. При этом у меня WD Red был в корзине, остальные стационарно - никаких сбоев пока нет. Конечно, пакеты пришлось ставить руками - бэкап не помог. Но это мелочи. Главное - все данные сохранны. Plex (не из центра пакетов!) подхватил всю библиотеку со всеми постерами и настройками. hardware transcoding не проверял, мне вообще не до него после таких плясок с оркестром. Ну и еще раз: обращайте внимание на форму разъемов питания HDD, я про те, что на кабелях. Они от температуры деформируются. Прямоугольная щель принимает форму более овальную. Это может быть причиной сбоев, т.к. контакт нарушается. Я такие сразу поменял. Всем Бобра!