Sorry, I was a bit impatient to start the reproduction. But not all attempts are obscured by the update process, as far as I can tell.
Can I ask you to check again the timeframes starting from 21:04:58.328 (this episode plays fine) and 21:05:22.090 (this episode aborts)?
If you need to see the Kodi startup itself, where the scanner and library updates usually run, I can repro with the offending options disabled tonight.
I observe the issue also after all library updates are completed, with OSMC/Kodi running in idle for hours.
DS1515+ running on latest DSM 6.1.4-15217 Update 5
Will check tonight, but I do not expect to find anything
Works like a charm on other devices (MPC HC on Windows)
Well, one idea I have is that related smb version (and a possible bug) has to do with it.
My Vero 4k tells me that it uses max. SMBv3, my Syno has max SMBv1 but I’m not sure whether this is the default.
@neoacix: So, what are the settings on your Vero 4k and your Syno?
DSM is configured for min. version SMB1 and max. version SMB2.
I enabled debug logging and watched log.smbd while attempting to start mentioned Stargate episode. I can’t really make a lot of sense of the o/p, therefore attaching it here in case anyone wants to take a stab at it.
Interestingly, when I set the max. version to SMB3 rather than v2, the issue appears to be no more. Video files previously failing to play after the December update now run fine. Or at least the two that I tried do.
When setting max. version back to SMB2, the same files immediately refuse to play again.
So I assume that some Samba update has been included for the OSMC December update, that is affecting SMB2 behavior; Can somebody confirm?
At least you have a solution setting max. SMB to v3 on the Syno, now. I tried your problem smb constellation also with a Syno DS214se but this got also DSM 6.1.4-15217 Update 5 till now … but I cannot reproduce this.
Did the December Update on my Vero4K and got Problems with streaming Files from my Synology SMB Shares.
Some files did not start at all.
Some files we’re starting and when i skipped 30 Seconds or more, i we’re sent back to menue.
Some files looked like they we’re starting. You could see the Playbacktime in the upper right Corner, but nothing happens.
Before the December Update Stream Files from my Synology SMB Shares we’re no Problem at all.
My Vero ist hooked Up with an Ethernet cable.
Updated my Synology to the latest Firmware.
It’s actually thanks to @JimKnopf, he sort of pointed the direction and led me exploring the depths of Synology Samba configuration
This seems to work for now, so I want to thank all who helped get there!
If you need any information or log that may help you fix the SMB2 issue, just give a holler…
I’m glad you’ve resolved this. There haven’t been changes to Kodi’s SMB implementation, but Debian Stretch does feature newer versions of Samba packages. It looks like this may be one to keep an eye out on.
I’ve written to the Debian mailing list some time ago about some problems with the current Debian Samba implementation but we didn’t get far with this.
We will monitor the state of Samba in Debian. If there are long term problems and it doesn’t meet the requirements of OSMC, we’ll package this and include it downstream with some improvements.
Ok, just did some new tests and finally was able to reproduce this also on the Synology DS214SE (which is one of the smallest Synology’s ARM platforms) after using very small video trailers. All AC3 trailers let abort the stream for the videoplayer at once, some of the TrueHD and DTS trailer as well but I don’t think it’s that related but more the size of the clips.
The required condition for this issue is
Vero 4k: Settings -> Services -> SMB client -> maximum protocol version = SMBv2 or SMBv3
Synology: Control Panel -> File Services -> SMB -> Advanced Settings -> Maximum SMB Protocol = SMB2
What me very wonders is that the combination
Vero 4k: max. protocol ver. SMB2
Syno: max, protocol ver. SMB3
works … ??? I expect the negotiated protocol version is then SMB2 but this constellation does not show the error.
So, setting both sides to SMBv3 or forcing the Vero 4k to SMBv1 solves this issue.
I found it on my OSMC devices set to SMBv3, isn’t it the default already?
On the Synology NAS there seems to be a lot of users with a setting of max. SMBv2 … which is causing the issue. Without deeper knowledge it seems to be an issue with SMBv2 … but I do not get a clue out of it why Vero 4k with max. SMBv2 and Syno with max. SMBv3 works here.
