Jump to content
XPEnology Community

Search the Community

Showing results for 'transcoding'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

  1. I installed xpenology on a HP Elitedesk G3 with i5 7500, 16GB of RAM. Everything works great but the Jellyfin app is having problems transcoding 4K videos. No matter of the settings used, it won't transcode more than 20 fps. I use the DS918+ image and HW transcoding is enabled(ls /dev/dri : card0 renderD128). Is there anything I'm missing? Thanks in advance!
  2. Before installing XPEnology using DSM 7.x, you must select a DSM platform and loader. XPEnology supports a variety of platforms that enable specific hardware and software features. All platforms support a minimum of 4 CPU cores, 64GB of RAM, 10Gbe network cards and 16 drives. Each can run "baremetal" as a stand-alone operating system OR as a virtual machine within a hypervisor. A few specific platforms are preferred for typical installs. Review the table and decision tree below to help you navigate the options. NOTE: DSM 6.x is still a viable system and is the best option for certain types of hardware. See this link for more information. DSM 7.x LOADERS ARE DIFFERENT: A loader allows DSM to install and run on non-Synology hardware. The loaders for DSM 5.x/6.x were monolithic; i.e. a single loader image was applicable to all installs. With DSM 7.x, a custom loader must be created for each DSM install. TinyCore RedPill (TCRP) is currently the most developed tool for building 7.x loaders. TCRP installs with two step-process. First, a Linux OS (TinyCore) boots and evaluates your hardware configuration. Then, an individualized loader (RedPill) is built and written to the loader device. After that, you can switch between starting DSM with RedPill, and booting back into TinyCore to adjust and rebuild as needed. TCRP's Linux boot image (indicated by the version; i.e. 0.8) changes only when a new DSM platform or version is introduced. However, you can and should update TCRP itself prior to each loader build, adding fixes, driver updates and new features contributed by many different developers. Because of this ongoing community development, TCRP capabilities change rapidly. Please post new or divergent results when encountered, so that this table may be updated. 7.x Loaders and Platforms as of 06-June-2022 Options Ranked 1a 1b 2a 2b 2c 3a 3b DSM Platform DS918+ DS3622xs+ DS920+ DS1621+ DS3617xs DVA3221 DS3615xs Architecture apollolake broadwellnk geminilake v1000 broadwell denverton bromolow DSM Versions 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 Loader TCRP 0.8 TCRP 0.8 TCRP 0.8 TCRP 0.8 TCRP 0.8 TCRP 0.8 TCRP 0.8 Drive Slot Mapping sataportmap/ diskidxmap sataportmap/ diskidxmap device tree device tree sataportmap/ diskidxmap sataportmap/ diskidxmap sataportmap/ diskidxmap QuickSync Transcoding Yes No Yes No No No No NVMe Cache Support Yes Yes Yes Yes Yes (as of 7.0) Yes No RAIDF1 Support No Yes No No Yes No Yes Oldest CPU Supported Haswell * any x86-64 Haswell ** any x86-64 any x86-64 Haswell * any x86-64 Max CPU Threads 8 24 8 16 24 (as of 7.0) 16 16 Key Note currently best for most users best for very large installs see slot mapping topic below AMD Ryzen, see slot mapping topic obsolete use DS3622xs+ AI/Deep Learning nVIDIA GPU obsolete use DS3622xs+ * FMA3 instruction support required. All Haswell Core processors or later support it. Very few Pentiums/Celerons do (J-series CPUs are a notable exception). Piledriver is believed to be the minimum AMD CPU architecture equivalent to Intel Haswell. ** Based on history, DS920+ should require Haswell. There is anecdotal evidence gradually emerging that DS920+ will run on x86-64 hardware. NOT ALL HARDWARE IS SUITABLE: DSM 7 has a new requirement for the initial installation. If drive hotplug is supported by the motherboard or controller, all AHCI SATA ports visible to DSM must either be configured for hotplug or have an attached drive during initial install. Additionally, if the motherboard or controller chipset supports more ports than are physically implemented, DSM installation will fail unless they are mapped out of visibility. On some hardware, it may be impossible to install (particularly on baremetal) while retaining access to the physical ports. The installation tutorial has more detail on the causes of this problem, and possible workarounds. DRIVE SLOT MAPPING CONSIDERATIONS: On most platforms, DSM evaluates the boot-time Linux parameters SataPortMap and DiskIdxMap to map drive slots from disk controllers to a usable range for DSM. Much has been written about how to set up these parameters. TCRP's satamap command determines appropriate values based on the system state during the loader build. It is also simple to manually edit the configuration file if your hardware is unique or misidentified by the tool. On the DS920+ and DS1621+ platforms, DSM uses a Device Tree to identify the hardware and ignores SataPortMap and DiskIdxMap. The device tree hardcodes the SATA controller PCI devices and drive slots (and also NVMe slots and USB ports) prior to DSM installation. Therefore, an explicit device tree that matches your hardware must be configured and stored within the loader image. TCRP automatic device tree configuration is limited. For example, any disk ports left unpopulated at loader build time will not be accessible later. VMware ESXi is not currently supported. Host bus adapters (SCSI, SAS, or SATA RAID in IT mode) are not currently supported. Manually determining correct values and updating the device tree is complex. Device Tree support is being worked on and will improve, but presently you will generally be better served by choosing platforms that support SataPortMap and DiskIdxMap (see Tier 1 below). CURRENT PLATFORM RECOMMENDATIONS AND DECISION TREE: VIRTUALIZATION: All the supported platforms can be run as a virtual machine within a hypervisor. Some use case examples: virtualize unsupported network card virtualize SAS/NVMe storage and present to DSM as SATA run other VMs in parallel on the same hardware (as an alternative to Synology VMM) share 10GBe network card with other non-XPEnology VMs testing and rollback of updates Prerequisites: ESXi (requires a paid or free license) or open-source hypervisor (QEMU, Proxmox, XenServer). Hyper-V is NOT supported. Preferred Configurations: passthrough SATA controller and disks, and/or configure RDM/RAW disks This post will be updated as more documentation is available for the various TCRP implementations.
  3. Check JellyFin FFmpeg logs, you should catch if HW is used or not. Edit : did you actually enabled HW transcoding in JellyFin options ?
  4. The CPU usage sits at 40% while transcoding
  5. check your CPU usage while transcoding. if it raises 100% then HW transcoding does not work.
  6. Bonsoir et merci pour ta réponse. Pour l'usage, effectivement chacun le sien, pour ma part, il serait vraiment pour du backup de données pur et dur, avec les "options" de serveurs de fichiers qui vont avec (FTP / SMB / NFS...) Pour la virtualisation, j'ai une machine dédiée et pour la domotique aussi, même si un peu overkill, elle sera a terme basculée en virtualisée. Bon après, techniquement, la quantité de ram n'est pas vraiment un problème, ça se change aisément. Pour la partie proco, comme j'étais parti dans ma tête sur de l'intel, c'était forcément (pour moi) du x86-64, j'ai pas associé intel à l'arm (après peut être que maintenant ils en font ? ils font bien des GPU) D'ailleurs ça me fait penser à une autre question, justement en parlant du GPU... En théorie, il n'y en a pas vraiment besoin mais j'ai lu quelques posts sur les iGPU et le transcoding... Actuellement, j'ai plex qui tourne sur un docker avec un vieux GPU en passthrought. Je ne sais pas encore si je le basculerais sur XPEnology ou pas, mais dans ce cas, si sur la mobo je venais à brancher un GPU en PCIe il serait pris en charge, ou il faut plutôt que je cherche un proco avec un iGPU ?
  7. I advise you to do the opposite: install ESXi to run virtual machines, one of which will be a virtual DSM Xpenology. ESXi features more than VMM To answer the rest of the questions, you need to understand what the DSM usage scenario will be: file storage only? viewing photos, home videos, movies, do you need hardware transcoding? video surveillance? Is there something else? there is hardly such a thing. You use a server CPU of 10 cores/20 threads - why do you need more powerful? Well, if increased performance is still required, then the power consumption will be higher.
  8. Hello everyone, my name is pdbear. Recently, I've been exploring the setup of media servers like Emby, Plex, Jellyfin, etc., within Synology NAS. I noticed that the lack of GPU transcoding functionality was something missing. As a vGPU user, I took some time to adapt it accordingly. Currently, the driver is based on 510.108.03, and it supports almost all x86 Synology NAS with kernel 4.4.302+. Feel free to give it a try. github link: https://github.com/pdbear/syno_nvidia_gpu_driver
  9. When setting up an XPEnology system, you must first select a DSM platform and version. XPEnology supports a few specific DSM platforms that enable certain hardware and software features. All support a minimum of 4 CPU cores, 64GB of RAM, 10Gbe network cards and 12-disk arrays. When you choose a platform and the desired DSM software version, you must download the correct corresponding loader. That may not be the "newest" loader available. The last 6.x version (6.2.4-25556) is functional only with the TCRP loader. TCRP is very different than the Jun loader. If you want to learn more, or if you are interested in deploying the latest 7.x versions, see the 7.x Loaders and Platforms thread. Be advised that installing 6.2.4 with TCRP is basically the same procedure as installing 7.x. Each of these combinations can be run "baremetal" as a stand-alone operating system OR as a virtual machine within a hypervisor (VMWare ESXi is most popular and best documented, but other hypervisors can be used if desired). Review the table and decision tree below to help you navigate the options. 6.x Loaders and Platforms as of 16-May-2022 Options Ranked DSM Platform DSM Version Loader Boot Methods*** Hardware Transcode Support NVMe Cache Support RAIDF1 Support Oldest CPU Supported Max CPU Threads Notes 1,3a DS918+ 6.2.0 to 6.2.3-25426 Jun 1.04b UEFI, BIOS/CSM Yes Yes No Haswell ** 8 6.2.0, 6.2.3 ok, 6.2.1/6.2.2 not recommended for new installs* 2,3b DS3617xs 6.2.0 to 6.2.3-25426 Jun 1.03b BIOS/CSM only No No Yes any x86-64 16 6.2.0, 6.2.3 ok, 6.2.1/6.2.2 not recommended for new installs* DS3615xs 6.2.0 to 6.2.3-25426 Jun 1.03b BIOS/CSM only No No Yes any x86-64 8 6.2.0, 6.2.3 ok, 6.2.1/6.2.2 not recommended for new installs* DS918+ 6.2.4-25556 TCRP 0.4.6 UEFI, BIOS/CSM Yes Yes No Haswell ** 8 recommend 7.x instead DS3615xs 6.2.4-25556 TCRP 0.4.6 UEFI, BIOS/CSM No No Yes any x86-64 8 recommend 7.x instead DS916+ 6.0.3 to 6.1.7 Jun 1.02b UEFI, BIOS/CSM Yes No No Haswell ** 8 obsolete, use DS918+ instead DS3617xs 6.0.3 to 6.1.6 Jun 1.02b UEFI, BIOS/CSM No No Yes any x86-64 16 6.1.7 may kernel panic on ESXi 4 DS3615xs 6.0.3 to 6.1.7 Jun 1.02b UEFI, BIOS/CSM No No Yes any x86-64 8 best compatibility on 6.1.x * 6.2.1 and 6.2.2 have a unique kernel signature causing issues with most kernel driver modules, including those included in the loader. Hardware compatibility is limited. ** FMA3 instruction support required. All Haswell Core processors or later support it. Only a select few Pentium, and no Celeron CPUs do. ** Piledriver is believed to be the minimum AMD CPU architecture to support the DS916+ and DS918+ DSM platforms. *** If you need an MBR version of the boot loader because your system does not support a modern boot methodology, follow this procedure. CURRENT LOADER/PLATFORM RECOMMENDATIONS/SAMPLE DECISION POINTS: 1. DEFAULT install DS918+ 6.2.3 - also if hardware transcoding or NVMe cache support is desired, or if your system only support UEFI boot Prerequisite: Intel Haswell (aka 4th generation) or newer CPU architecture (or AMD equivalent) Configuration: baremetal loader 1.04b, DSM platform DS918+ version 6.2.3 Compatibility troubleshooting options: extra.lzma or ESXi 2. ALTERNATE install DS3617xs 6.2.3 - if RAIDF1, 16-thread or best SAS support is desired, or your CPU is too old for DS918+ Prerequisite: USB key boot mode must be set to BIOS/CSM/Legacy Boot Configuration: baremetal loader 1.03b, DSM platform DS3617xs version 6.2.3 Compatibility troubleshooting options: extra.lzma, DS3615xs platform, or ESXi 3. ESXi (or other hypervisor) virtual machine install - generally, if hardware is unsupported by DSM but works with a hypervisor Prerequisites: ESXi hardware compatibility, free or full ESXi 6.x or 7.x license Use case examples: virtualize unsupported NIC, virtualize SAS/NVMe disks and present as SATA, run other ESXi VM's instead of Synology VMM Option 3a: 1.04b loader, DSM platform DS918+ version 6.2.3 Option 3b: 1.03b loader, DSM platform DS3617xs version 6.2.3 (VM must be set to BIOS Firmware) Preferred configurations: passthrough SATA controller and disks, and/or configure RDM/RAW disks 4. FALLBACK install DS3615xs 6.1.7 - if you can't get anything else to work Prerequisite: none Configuration: baremetal loader 1.02b, DSM platform DS3615xs version 6.1.7 SPECIAL NOTE for Intel 8th generation+ (Coffee Lake, Comet Lake, Ice Lake, etc.) motherboards with embedded Intel network controllers: Each time Intel releases a new chipset, it updates the PCI id for the embedded NIC. This means there is a driver update required to support it, which may or may not be available with an extra.lzma update. Alternatively, disable the onboard NIC and install a compatible PCIe NIC such as the Intel CT gigabit card.
  10. @littleMOLE, @gericb There is one more thing you need to know. ATOM CPUs, even though they are 1st generation Intel, are excellent models that support the movbe ("Move Data After Swapping Bytes") instruction internally. https://www.cpu-world.com/CPUs/Atom/Intel-Atom 230 AU80586RE025D.html If this command is supported, most models of REDPILL can be installed without restrictions. Even DS918+ that requires transcoding can be installed.
  11. Hello everyone, I've managed to compile the up-to-date out-of-tree i915 kernel module for sa6400, with support for up to 14th gen (Raptor Lake) Intel GPU in theory. I've verified jellyfin HW transcoding on my N100 box (12th gen, Alder Lake), in both PCIe passthrough and SR-IOV VF mode. The source code is available at https://github.com/MoetaYuko/intel-gpu-i915-backports/tree/redhat/main-epyc7002, which can be built on the cloud w/ github actions. You can find the precompiled blobs from github actions artifacts of this repo. The driver is considered alpha quality because I haven't used it long. Feel free to try it and report issues here if any. In case of missing firmware, you'll see error messages w/ the desired FW filename in dmesg. They can be downloaded at https://github.com/intel-gpu/intel-gpu-firmware and put in `/lib/firmware/i915` of your DSM. For SR-IOV with PVE hypervisor, I highly recommend using the dkms driver published at https://github.com/MoetaYuko/intel-gpu-i915-backports/releases (its source code is available at `backport/main` branch of the same repo). It has three major advantages over the popular host driver from https://github.com/strongtz/i915-sriov-dkms: Its Intel release tag is the same as my sa6400 driver, so the best compatibility is ensured. It's packaged as .deb so it can be easily installed and upgraded via apt/dpkg. The .ko binaries reside in `/lib/modules/$(uname -r)/updates/dkms` so they won't override the ones provided by the proxmox-kernel package.
  12. Hi all:) After a little bit of reverse engineering I was able to bypass the license checking mechanism introduced in DSM 6 successfully with a simple two line binary patch of synocodectool and therefore enable transcoding without a valid serial number[emoji4]. I wrote a little script to make it easier for everyone. For more information please check the github repo: https://github.com/likeadoc/synocodectool-patch HOWTO: 1. wget https://raw.githubusercontent.com/likeadoc/synocodectool-patch/master/patch.sh 2. chmod +x patch.sh 3. ./patch.sh Done:) If things go wrong simply restore the original file: ./patch.sh -r Cheers
  13. I am having problems with media playback when using Jellyfin on Synology DSM 7.2. I get a "Playback Error: This client isn't compatible with the media and the server isn't sending a compatible media format." It seems to be something with the transcoding. If I turn off transcoding then my media will play. Previously, I did not have this problem. I was able to play with transcoding turned on, so I don't know what changed. Can anyone help me with this?
  14. I'm sorry. Even though I knew that the 5900X was a model without an iGPU, I overlooked it. If you decide to migrate to a model other than DS918+, I recommend trying SA6400 instead of DS2422+. If you have an Intel iGPU in the original SA6400, H/W transcoding is easily handled. There is no need to install AME, nor does it require a genuine Serial or Mac. Codec patches are also unnecessary. However, I am also curious about how the SA6400 operates without an iGPU. If H/W transcoding is not possible, at least S/W transcoding should work. I also have Works that can be run with only a Xeon CPU without an iGPU. I will tell you the results of testing how the SA6400 works.
  15. You don't seem to have looked at my answer carefully. Transcoding from bare metal to AMD iGPU is not possible. This includes transcoding all media. It's not just that video transcoding like plex is impossible. Photo transcoding that works with i915.ko is also included here. AMD clearly has some things to give up. Think again. In the server forum in Korea where I work, for AMD transcoding, I recommend proxmox + lxc solutions. lxc says that AMD iGPU can also be used for transcoding. I also have no actual installation experience. Some users are only providing information about the possibility as shown below. If translation is possible, please refer to the search results below. https://svrforum.com/index.php?mid=nas&act=IS&search_target=title_content&is_keyword=AMD+lxc
  16. There is no model or platform you have to give up just because you use AMD Ryzen. You can think of Redpill as being developed cross-platform. However, with Ryzen, you only need to remember a few limitations. 1. Since it is not an Intel iGPU, transcoding is not possible. 2. If you need to use VMM, select one of the models that use the v1000, r1000, or epyc7002 platforms.
  17. Several choices you did could lower your chances to have the DSM booting: - DS923+ is designed for AMD Ryzen R1600 - i915 driver (is for the iGPU not related to the NIC) to my knowledge the fork from 9th gen. driver is maximum for Intel Core 10th gen., so don't expect to exploit the UHD Graphics 770 (and as Synology most probably won't release anything for Gen. 11, 12, etc... as they go now with AMD). So forget about any transcoding, except with a Plex Pass subscription - Your onboard NIC is Realtek RTL8125BG, not the best chipset in the 2,5Gb/s world, but at least it works on DS918+
  18. I have ESXi installed on this processor. And several virtual machines (Windows and DSM) at the same time. The DS920+ is slightly newer than the DS918+, but you'll only notice this in real Synology devices. When installing Xpenology, and even in the form of a virtual machine, the differences will be minimal, you can try any. You can see the model differences and recommendations here. Keep in mind that the Xeon processor does not have an iGPU, so the hardware transcoding capabilities of the DS918+/DS920+ will not be available to you anyway. of course, today it is no longer necessary to look at version 6 of the DSM Yes, this is one of the most convenient redpill-based bootloaders for today. In most cases, its installation looks like this: burn the image to a USB stick, boot, select the DSM model and answer all other questions "OK".
  19. Hello experts! I've got a many years old xpenology setup going right now in the same case running DSM6. Very happy with it, but it's time for a better CPU and some new drives. This one ideally would be using DSM7. Hopefully hardware transcoding with the integrated gpu would work in emby and plex. 1-3 streams at a time. SSD for cache if it makes sense. Maybe another SSD to host the OS, but not sure if that's possible? PSU I'll figure out later. Hoping the 2.5gbe on the motherboard will work. My network isn't 10gbe, so I don't need it, but definitely not opposed to moving to it. Intel Core i9-14900T ASRock Z790M-ITX WIFI Mini ITX LGA1700 Motherboard G.Skill Trident Z5 Neo 64 GB (2 x 32 GB) DDR5-6000 CL30 Memory Samsung 990 Pro 4 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive Western Digital Gold 22 TB 3.5" 7200 RPM Internal Hard Drive x8 Fractal Design Node 804 MicroATX Mid Tower Case LSI Broadcom SAS 9300-8i 8-port 12Gb/s SATA+SAS PCI-Express 3.0
  20. - are you sure hardware transcoding is working/enabled? It should be able to handle it! Than think about the proposed option with virtual machines running ESXi - there you can continue to use DSM and install whatever you want on the same server. And use the newest and most powerful hardware for this.
  21. A month ago, I purchased a Synology DS423+, but I returned it after two weeks for various reasons. Now, I've built an Xpenology DS920+ using an Asrock J5040 motherboard, performing a migration and using serial numbers and settings suggested by the Arc-redpill loader. Can someone explain why I can still use QuickConnect and hardware transcoding seamlessly? What can only be achieved with original serial numbers. Inviato dal mio iPhone utilizzando Tapatalk
  22. Thank you! i9-9900K is 5 years old though Right now I have an i7-7700T and it can't handle real-time transcoding of even 1 stream (depending on input and output types). i9-9900K is 2 years newer, so some chance it'd be OK, but not sure if it could handle more than 1 stream, and that's not much future proofing. Decompression performance is also too slow for my needs on my current chip. Since it's no longer produced it also costs the same as a CPU built this year. It's sounding more and more like I should give up on xpenology and maybe go to OpenMediaVault, Rockstor, EasyNAS, Unraid or similar. New UI to learn which would be a bummer, and I doubt any of them are quite as nice as DSM.
  23. Thank you so so much! Yeah I have 32gb ram in my current NAS and it is not well-utilized. You'd think at some point they'd do more caching of files in RAM I neglected to mention I will also be running sonarr, radarr, sabnzbd, etc. Decompressing large files hits the CPU super hard to the point where I spend more time decompressing than downloading now. That's where the interest in a faster CPU comes from, also proofing against unknown future needs. With such limited ability to use cores, I wonder how it decides whether to use the P or E cores. Bummer the i9 is a no-go. i5-14500t is 6 p cores and 8 e cores. i3-14100t is 4 cores, but the GPU is a 730 instead of a 770 770 would be nice to future proof transcoding to future standards or some AI thing that comes up. Probably I'll have the NAS for 6 or 7 years. Is there something you'd recommend? I guess I could always do OpenMediaVault or something but the interface does not seem remotely as nice.
  24. Yes, it's quite time to move on: DSM7 works stably, there are many useful innovations, and there are well-functioning bootloaders. But let's look at your needs and the chosen hardware: 1. "Hopefully hardware transcoding with the integrated gpu would work in emby and plex": 1.1. iGPU hardware transcoding only works for models DS918+ and DS920+ - remember it 1.2. Standard Synology drivers only support iGPUs up to the 9th generation Intel CPU 1.3. But for some new CPU models, it is possible to install the i915 patch. You can check, for example, by mentioning the Arc Loader in the Addon: 1.3.1. find your Device ID by CPU - for 14900T it's 0xA780. 1.3.2. check if this code is mentioned in the Addon 915 list? (look for "8086A780" there) - if the ID is found, the driver may be patched 2. "SSD for cache if it makes sense" - the cache is useful in cases where your DSM will use frequent access to the same small files. It is unlikely that you will need it for simple video viewing. But if you still want to, then choose NVME (not SATA SSD which are slower), and better install DS920+ 3. "Maybe another SSD to host the OS, but not sure if that's possible?" - in DSM the operating system is placed on all disks at the same time - you will not get any winnings here. But you can place the data of some packages or virtual machines on a separate SSD volume - think about it later, if necessary. 4. "Hoping the 2.5gbe on the motherboard will work. My network isn't 10gbe, so I don't need it, but definitely not opposed to moving to it" - the drivers available today support a limited list of 2.5GbE and 10GbE models (it is much smaller than for 1Gb) - you need to carefully check compatibility before choosing (search on this forum). 5. Efficiency. The hardware you choose will exceed your stated needs ("emby and plex. 1-3 streams at a time") many times: - in DS918+/DS920+ only 8 CPU threads will be used (the remaining in i9-14900T will be idle) [Updated:] not even that - most likely on i9-14900T, which has 24 cores, neither DS918+ nor DS920+ will start at all! - WiFi does not work in DSM - 64Gb RAM will never be fully used - 4Tb for the cache is too much (but you can, if it's not a pity) if you do not plan to load the server with any additional heavy tasks (for example, virtual machines), then I would recommend that you choose a less powerful configuration that will also save on electricity consumption).
  25. Hi, im just install SA6400 version on Xpenology with AuxXxilium/arc and everything works fine (even transcoding on my N100) exept usb uarts When im connect my ch340 it wont recognise like /dev/ttyUBS. Im trying install driver from r1000 and v1000 amd robertklep/dsm7-usb-serial-drivers but it starts fine, but without /dev/ttyUSB. Anybody can helps me start it? I need it to my Zigbee coordinator in Docker.
×
×
  • Create New...