Want to get a second OMV box for hardware transcoding (advice needed)

  • I am using a rockpro64 but basically hardware transcoding is not possible I ran into this guide https://forums.serverbuilds.ne…icksync-and-nvenc/1408and I am really interested to go this way since Intel with its quiksync look like the way to go.

    So they are two options, just get an hp prodesk mini,micro or similar and share my hard dives between the two OMV boxes (not sure yet how to do that with mount point etc..) or get rid of the arm OMV and get a bigger intel desktop where I could attach my drives, but I am pretty sure I prefer the first option in term of purchase cost, energy,noise and redundancy since I got 2 systems instead of one so I really need advice from the experts about what to do ?

  • Why do you need to transcode? All devices I use to watch video are perfectly able to decode and scale any video I stream. Except one or two where the wifi bitrate is a problem. I fixed that by creating a lower bitrate copy of the video in advance. Emby has a function to create and manage such non-realtime "transcoded" files.


    All my clients use wifi to access the videos. And as long as the wifi bitrate is sufficient, everything works fine. I have a 3 node Asus wifi mesh in the house. Wifi bitrates are typically between 200-600 Mbps, depending on location and proximity to mesh nodes. I use wired 1Gbps ethernet between all OMV servers.


    I use NFS in OMV to serve out the shares of my servers.


    And I use autofs to mount all these shares on every Linux device.


    So any server can access any share at:


    /srv/nfs/nas#


    I have written about it in other threads here before. For example:


    remote mount plugin with offline drives


    Using autofs means that the connection is "self-healing" so it is possible to have a server turned on and then access the share at the mount point without any extra actions.

    Be smart - be lazy. Clone your rootfs.
    OMV 5: 9 x Odroid HC2 + 1 x Odroid HC1 + 1 x Raspberry Pi 4

  • I use a Beelink J45 mini PC with Ubuntu 20.04 and it's modest Pentium CPU transcodes Jellyfin steams to devices that can't natively decode the stream. My more powerful OMV system has a Pentium Gold CPU it does better at 100+ fps HEVC 10 bit -> 264. It all depends on how many devices you are sending video to. My estimate is that the OMV system will easily transcode three streams simultaneously. So you don't have to spend hugely to do the job.

    Inwin MS04 case with 315 W PSU

    ASUS Prime H310i-Plus R2.0 board

    Four port PCI-E SATA card

    8GB Kingston DDR4

    Intel Pentium Coffee Lake G5400 CPU

    Samsung Evo M.2 256GB OS drive (28 GB partitioned for OS)

    4x4TB WD Red NAS drives - UnionFS pool

    Seagate 5TB USB drive - SnapRAID parity

    1x1TB Seagate HD

    1x300GB Toshiba HD

    Seagate 2TB USB drive

  • NFS is OK for use in a LAN, but not outside. You can run NFS and SMB simultaneously. That is what I do. NFS between Linux boxes, SMB for Android clients.

    Be smart - be lazy. Clone your rootfs.
    OMV 5: 9 x Odroid HC2 + 1 x Odroid HC1 + 1 x Raspberry Pi 4

  • I just use NFS and the media server (Emby, Jellyfin) takes care of forwarding the streams to wherever you are.

    Inwin MS04 case with 315 W PSU

    ASUS Prime H310i-Plus R2.0 board

    Four port PCI-E SATA card

    8GB Kingston DDR4

    Intel Pentium Coffee Lake G5400 CPU

    Samsung Evo M.2 256GB OS drive (28 GB partitioned for OS)

    4x4TB WD Red NAS drives - UnionFS pool

    Seagate 5TB USB drive - SnapRAID parity

    1x1TB Seagate HD

    1x300GB Toshiba HD

    Seagate 2TB USB drive

  • I have got to reformat my data drive (ext4-movies) to NFS

    nfs isn't a filesystem type. It is a server protocol. You create nfs shares to serve the client just like samba.

    omv 5.5.5 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.5
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Well I am wondering about my letsencrypt Certificate cant it be use on the second OMV (NFS sharing) since I have only one domain for all my app using wildcard or should I get an extra domain from duckdns and add an other docker for letsencrypt also I read than Hardware transcoding is not really supported from container any info bout that?

  • Hardware transcoding works in the Jellyfin docker and proably others but haven't tried. Letsencrypt only works on a device that has ports 80 and 443 exposed so you can't use on two devices (unless you have two internet accounts and two routers). What you can do is have the cert on one device and use its webserver to forward certain addresses to the second device

    Inwin MS04 case with 315 W PSU

    ASUS Prime H310i-Plus R2.0 board

    Four port PCI-E SATA card

    8GB Kingston DDR4

    Intel Pentium Coffee Lake G5400 CPU

    Samsung Evo M.2 256GB OS drive (28 GB partitioned for OS)

    4x4TB WD Red NAS drives - UnionFS pool

    Seagate 5TB USB drive - SnapRAID parity

    1x1TB Seagate HD

    1x300GB Toshiba HD

    Seagate 2TB USB drive

  • What you can do is have the cert on one device and use its webserver to forward certain addresses to the second device


    let's say I have got emby.xmydomainx.duckdns.org going to192.168.2.30 how exactly I forward the certificate to 192.168.2.45, is it from the emby.subdomain.conf I assuming by changing this line proxy_pass http://192.168.2.30:8096; by proxy_pass http://192.168.2.45:8096;

    Is there a way to keep two emby.subdomain.conf with 2 addresses in case I want to go back to the other OMV?

  • I can explain how I do it but I use Apache on an Ubuntu 20.04 system as my webserver - this is 192.168.1.2. It has the LetsEncrypt certs.

    OMV is on 192.168.1.3 and doesn't face the web directly.

    I run SyncThing on OMV and on the Ubuntu/Apache device I have a virtual server as follows:


    ProxyPass /syncthing-omv/ http://192.168.1.3:8384/

    <Location /syncthing-omv/>

    ProxyPassReverse http://192.168.1.3:8384/

    Require all granted

    </Location>


    On that device I have a folder /var/www/html/syncthing-omv with a one line index.html file:


    <meta http-equiv="Refresh" content="5; url=http://192.168.1.3:8384/">


    So I'm away from home and want to look at SyncThing on OMV:


    https://my.duckdns.org/syncthing-omv


    Apache directs the request to the OMV device and the certificate is good.


    Thanslate this principle to Niginx and you'll have it going.


    But...this took a lot of working out, maybe isn't the best way, and other web apps such as Jellyfin required a different approach.

    Inwin MS04 case with 315 W PSU

    ASUS Prime H310i-Plus R2.0 board

    Four port PCI-E SATA card

    8GB Kingston DDR4

    Intel Pentium Coffee Lake G5400 CPU

    Samsung Evo M.2 256GB OS drive (28 GB partitioned for OS)

    4x4TB WD Red NAS drives - UnionFS pool

    Seagate 5TB USB drive - SnapRAID parity

    1x1TB Seagate HD

    1x300GB Toshiba HD

    Seagate 2TB USB drive

  • Regarding NFS and pardon my ignorance sine in the meantime I am testing from192.168.2.30 to on an old i386 computer I enabled NFS on both, I made a share for my media with access to the client 192.168.2.167/24 I gave RW extra option says subtree_check,insecure but so far I cannot see the share folder on the remote OMV

    can it be done from the GUI or should I use the CLI?

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!