Followup. It will transcode the TrueHD if the player can’t accept it (most don’t). TrueHD -> AAC or AC3 can put an appreciable load on a smaller NAS (up to 30%)
apologies for not stating this earlier.
Well, all the metadata were retrieved for some time now, and the TrueHD track was only on the movie I was talking about. I just watched an 1080p episode, in direct play (video+audio), the cpu/ram load is quite low but it’s still stuttering whereas I can see that there’s buffer ahead on the progression bar.
If you have buffering in a DirectPlay situation, You have app or network issues.
DirectPlay takes about 3-4% of an i7 processor (7-10% of a typical NAS processor) in the worst of cases.
Are you using WiFi? Is it 2.4 Ghz (cluttered) or 5 Ghz through a few walls (low signal strength) ?
That’s what I thought, DirectPlay should be smooth with a DS918+.
No, my TV is connected to my modem through a RJ45 cable. I’m investigating this connection since I run a speedtest and the bandwith is ~90Mbps, which is just about what I have with Wifi 2.4GHz (from my NAS it tops at 800Mbps), so I guess there’s something wrong.
Modems are strange animals.
While they have a switch inside them (the multi-port capability), it’s not their purpose and cross-port communication (switching) isn’t the specialty. It’s a modem-router
To add, most televisions are only good for 100 Mbps. so speed tests which show 800 Mbps don’t have merit unless you are running the speedtest at the television itself (e.g. attached AppleTV 4K which is wired with Gigabit).
I concur that something is wrong. the challenge is finding where the slow spot is.
Is it the television’s ability to receive or to reply / ask for more data ?
Is it the LAN itself? The LAN seems fine so we need to dig deeper.
In my LAN, My modem/router (pfSense) feeds the main switches (HPE-1820-24G & GS110/EMX). All traffic goes through those switches.
Even though it’s a 10 GbE switch, with 5 GbE adapter on the computer,
[chuck@telfs ~.90]$ iperf3 -c 192.168.0.21
Connecting to host 192.168.0.21, port 5201
[ 5] local 192.168.0.13 port 59022 connected to 192.168.0.21 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 378 MBytes 3.17 Gbits/sec 0 4.00 MBytes
[ 5] 1.00-2.00 sec 374 MBytes 3.14 Gbits/sec 0 4.00 MBytes
[ 5] 2.00-3.00 sec 375 MBytes 3.15 Gbits/sec 0 4.00 MBytes
[ 5] 3.00-4.00 sec 376 MBytes 3.16 Gbits/sec 0 4.00 MBytes
[ 5] 4.00-5.00 sec 378 MBytes 3.17 Gbits/sec 0 4.00 MBytes
[ 5] 5.00-6.00 sec 376 MBytes 3.16 Gbits/sec 0 4.00 MBytes
[ 5] 6.00-7.00 sec 378 MBytes 3.17 Gbits/sec 0 4.00 MBytes
[ 5] 7.00-8.00 sec 378 MBytes 3.17 Gbits/sec 0 4.00 MBytes
[ 5] 8.00-9.00 sec 374 MBytes 3.14 Gbits/sec 0 4.00 MBytes
[ 5] 9.00-10.00 sec 378 MBytes 3.17 Gbits/sec 0 4.00 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 3.67 GBytes 3.16 Gbits/sec 0 sender
[ 5] 0.00-10.00 sec 3.67 GBytes 3.16 Gbits/sec receiver
iperf Done.
[chuck@telfs ~.91]$ iperf3 -c 192.168.0.21 -R
Connecting to host 192.168.0.21, port 5201
Reverse mode, remote host 192.168.0.21 is sending
[ 5] local 192.168.0.13 port 59026 connected to 192.168.0.21 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 352 MBytes 2.96 Gbits/sec
[ 5] 1.00-2.00 sec 363 MBytes 3.04 Gbits/sec
[ 5] 2.00-3.00 sec 361 MBytes 3.03 Gbits/sec
[ 5] 3.00-4.00 sec 364 MBytes 3.05 Gbits/sec
[ 5] 4.00-5.00 sec 342 MBytes 2.87 Gbits/sec
[ 5] 5.00-6.00 sec 364 MBytes 3.06 Gbits/sec
[ 5] 6.00-7.00 sec 344 MBytes 2.89 Gbits/sec
[ 5] 7.00-8.00 sec 361 MBytes 3.02 Gbits/sec
[ 5] 8.00-9.00 sec 331 MBytes 2.78 Gbits/sec
[ 5] 9.00-10.00 sec 363 MBytes 3.04 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 3.47 GBytes 2.98 Gbits/sec 10949 sender
[ 5] 0.00-10.00 sec 3.46 GBytes 2.97 Gbits/sec receiver
iperf Done.
[chuck@telfs ~.92]$ ```Well I have bad news. I tried emby and the playback is smooth, no stuttering 
I don’t have stuttering even on a single 1 Gb link.
To complicate matters, I’ve upgraded my host and now have a NUC HadesCanyon with 10 Gbps
Connecting to host 192.168.0.21, port 5201
[ 5] local 192.168.0.13 port 51750 connected to 192.168.0.21 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 1.09 GBytes 9.40 Gbits/sec 0 1.57 MBytes
[ 5] 1.00-2.00 sec 1.10 GBytes 9.42 Gbits/sec 0 1.57 MBytes
[ 5] 2.00-3.00 sec 1.10 GBytes 9.42 Gbits/sec 0 1.65 MBytes
[ 5] 3.00-4.00 sec 1.09 GBytes 9.41 Gbits/sec 0 1.65 MBytes
[ 5] 4.00-5.00 sec 1.10 GBytes 9.42 Gbits/sec 0 1.86 MBytes
[ 5] 5.00-6.00 sec 1.09 GBytes 9.38 Gbits/sec 0 1.86 MBytes
[ 5] 6.00-7.00 sec 1.09 GBytes 9.41 Gbits/sec 0 1.86 MBytes
[ 5] 7.00-8.00 sec 1.10 GBytes 9.42 Gbits/sec 0 1.86 MBytes
[ 5] 8.00-9.00 sec 1.10 GBytes 9.42 Gbits/sec 0 1.86 MBytes
[ 5] 9.00-10.00 sec 1.09 GBytes 9.41 Gbits/sec 0 1.96 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 11.0 GBytes 9.41 Gbits/sec 0 sender
[ 5] 0.00-10.00 sec 11.0 GBytes 9.41 Gbits/sec receiver
iperf Done.
[chuck@lizum plex-media-server.198]$ iperf3 -c 192.168.0.21 -R
Connecting to host 192.168.0.21, port 5201
Reverse mode, remote host 192.168.0.21 is sending
[ 5] local 192.168.0.13 port 51758 connected to 192.168.0.21 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 1.09 GBytes 9.38 Gbits/sec
[ 5] 1.00-2.00 sec 1.10 GBytes 9.41 Gbits/sec
[ 5] 2.00-3.00 sec 1.10 GBytes 9.41 Gbits/sec
[ 5] 3.00-4.00 sec 1.10 GBytes 9.42 Gbits/sec
[ 5] 4.00-5.00 sec 1.10 GBytes 9.41 Gbits/sec
[ 5] 5.00-6.00 sec 1.10 GBytes 9.41 Gbits/sec
[ 5] 6.00-7.00 sec 1.10 GBytes 9.41 Gbits/sec
[ 5] 7.00-8.00 sec 1.10 GBytes 9.41 Gbits/sec
[ 5] 8.00-9.00 sec 1.10 GBytes 9.41 Gbits/sec
[ 5] 9.00-10.00 sec 1.10 GBytes 9.42 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 11.0 GBytes 9.42 Gbits/sec 0 sender
[ 5] 0.00-10.00 sec 11.0 GBytes 9.41 Gbits/sec receiver
iperf Done.
[chuck@lizum plex-media-server.199]$ ```
I will now start profiling processor load to see what I can find. I know I'm missing something. I'm sorry for overlooking whatever I am. Health has been interfering of recent.Wow 10Gbps 
Good news, I deleted my movie and tv show librairies and created them again. Stuttering seems to have gone away since then!
Hi Chuck,
Do you know/think the hardware acceleration for burning subtitles will be included in the VA-API soon?
I’m currently also running PMS on a Celeron J3455 and while most streams work just fine with transcoding, adding subtitles to a Blu-ray rip will cause constant buffering.
Was looking at pricing for the newest NUCs earlier today, but I’d rather save the money or buy some movies instead.
I have no idea when hardware support for burning subtitles will be added.
IMHO, it’s one of the first things that should have been added but 
I’m just a lowly engineer.
The J3455 has a regular GPU in addition to the video ASIC.
To my mind, tasking the GPU to render the subtitle font is trivial. Text on a graphics display is how it’s done . Using the ASIC to merge that bitmap plane onto the video plane is another logical “OR” (merge) operation.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
