Server Version#: 3.69.1
Player Version#: Latest iOS
Both my old DS718+ and now my DS918+ suffers from this issue. Videos that are compatible with iOS (h264) that WILL play without any transcoding, takes forever (well, a few minutes anyway) to start to play (not always but very often)! Watching the spinner for a few minutes is a bit annoying.
Forcing to transcode (I use hardware transcoding) I think seems to work better.
I’ve never experienced any issues with the webplayer (Chrome. Anyway, this problem only occurs on my iPhone8/iPad 2018 with iOS12, and I’ve had the problem for months.
I don’t have any logs at the moment but will try to get them. I can’t be the only one with this issue or can I? I think it’s strange I had it on my previous DS718+ aswell…?
I know I don’t have any logs but anyone have any hints for me?
It can actually be upgraded to 16GB no matter what Synology say. I’ve added an 8GB RAM module to the empty slot.
I’ve checked some logs now, can I pm someone complete logs?
“Despicable Me 3 (2017): no direct play video profile exists for http/mkv/h264”
Oct 14, 2018 16:11:30.213 [0x7fd80b447700] DEBUG - MDE: Despicable Me 3 (2017): no direct play video profile exists for http/mkv/h264/dca
Oct 14, 2018 16:11:30.213 [0x7fd80b447700] DEBUG - MDE: Cannot direct stream audio stream due to codec dca when profile only allows aac
Oct 14, 2018 16:11:30.214 [0x7fd80b447700] DEBUG - MDE: Despicable Me 3 (2017): selected media 0 / 11235
Oct 14, 2018 16:11:30.214 [0x7fd80b447700] DEBUG - Streaming Resource: Reached Decision id=11655 codes=(General=1001,Direct play not available; Conversion OK. Direct Play=3000,App cannot direct play this item. No direct play video profile exists for protocol http, with container mkv, and video codec h264. Transcode=1001,Direct play not available; Conversion OK.) media=(id=11235 part=(id=11296 decision=transcode container=mpegts protocol=hls streams=(Video=(id=7392 decision=copy width=1920 height=804) Audio=(id=7393 decision=transcode bitrate=258 encoder=aac channels=2 rate=48000))))
The J3455 CPU can only USE 8GB of RAM.
You can install up to 16GB, which Linux is fooled with and DSM displays (it reads the spec for each DIMM and displays the sum).
It don’t always playback, it sometimes just stops with an errormessage (sorry, don’t have it right now), sometimes it plays after a minute or two or more… I’ll see if I can get some better logs.
I’ve sent you a PM with attached logs. I’ll try get more logs from similar scenarios. I will be very interested to hear what you discover.
Thanks in advance.
No it’s not locked to directplay. I think its strange that it doesn’t work and then work a minute later and I haven’t changed a setting.
The NAS has 12GB (4+8).
What happens to Linux when it thinks it has more than the CPU can physically address is this scenario:
OS and main buffers start in low memory (0-2GB)
Temporary memory usage (stack) starts at the top).
Modular math truncates the bits above what the CPU can physically address.
Therefore, Logical address 8GB + 1 is actually physical memory address 1.
( the ‘8’ GB bit isn’t present to support the physical addressing of the location )
You actually have 4GB of overlapping or unused memory (depends on the vendor)
Doing sort of an experiment at the moment typing this… Playing back a 1080p HEVC on my iPad from Plex, running a VMM with 8GB RAM running Windows 7, playing a 1080p mediafile through Windows explorer, playing around with DSM at the same time, used memory is about 86% right now. I am no expert whatsoever concerning this, but wouldn’t something crash terribly if I only had access to 8GB?
FWIW, I have developed in the kernel itself.
I know how the SPD chip (size and speed settings) is read.
The amount of installed RAM is simply ADDED from the reported values of the SPD chips.
Perhaps going a bit offtopic now, but just wondering about people posting in that forum, here’s quote below. Have they got it wrong?
" For the 3rd time, it’s 8GB/channel so 16GB total