No MySQL data being written or read?

If you had a flaky network cable, I’m guess that your video problems are related to that :wink:

You’d think so, but initial test seemed to be the same. I’ve wasted enough time on this so far today, I’ll have a look later on :slight_smile:

Had already a strange feeling with the drops

        RX packets 848  bytes 257987 (251.9 KiB)
        RX errors 0  dropped 42  overruns 0  frame 0

Ahhh, where was that? In the logs? I’ve 30 years in infrastructure, if I’d seen that I’d have changed the cable immediately and not wasted everyone’s time. Think I’d convinced myself it was a problem with the image.

Yes it’s in the ifconfig section. In the first log it didn’t looked that bad as you already had transfered more.

====================== ifconfig =================== pi3lDrO1
eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC>  mtu 1500
        inet 192.168.0.158  netmask 255.255.255.0  broadcast 192.168.0.255
        ether 90:0e:b3:21:c2:71  txqueuelen 1000  (Ethernet)
        RX packets 64650  bytes 91572077 (87.3 MiB)
        RX errors 0  dropped 16  overruns 0  frame 0
        TX packets 20125  bytes 1959896 (1.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 40  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 4096
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


---------------------- ifconfig END --------------- pi3lDrO1

Agreed, it certainly didn’t look like a networking issue, what with it working and all that.

Anyway, there we are.

Assuming for stuttering video we need a mediainfo of one of the files and more logs?

Yes, and for that case always suggested to try play from USB Stick first.

Righto, I’ll sort that out for later on.

Given that I’ve been using the same sources.xml for the past 8+ years too, should I now be on NFS rather than SMB? Probably a stupid question. Think it wasn’t working very well in the olden days.

Well the bigger the movies get the more value from NFS

1 Like

Seems not to be contributing any major problem for me currently.

Perhaps I’ll phase it in at home, slowly, to avoid any moaning.

Actually moving to Kernel Mounts would be the more performant approach

1 Like

Ha, I was just reading about that actually. Either of them will stuff up my current “who’s watched what” MySQL DB, hence the slow transition.

Should I start a new thread for the stuttering video example btw? I have the media info and have tried it locally from a USB stick, via NFS and SMB same same. I just want someone to tell me it’s a bad encode - seems to always be the same ones over and over.

Not really, for the time of migration you can just use path substitution

If you would like to use a MySQL database for several Kodi clients that use different methods to access the shared media (e.g. a mix of SMB, NFS and/or system mount based access), or have need of modifying a path of an existing source (such as converting from a Kodi path to a system mount) you can use the path substitution function of Kodi to facilitate this. The following guide will provide instruction on how this works, including a section specific to MySQL usage and how your sources should be configured.

Please see [HowTo] Repairing File Paths with Path Substitution for details.

1 Like

Yes suggest that

Well that is hard to judge. So you would need to provide a sample for that to be judged.

Absolutely bang on the money. Thank you for making me aware of this.

I am more of a “if it works, levae it” kind of person with OSMC as I have a lot of other things going on.

As a long time user since the RPi early days, I decided to invest in the Vero 4K+ when I built my media room and I’m still glad I did as this forum is very helpful.

Assuming there’s no way to force older v18 clients to use the newer v19 DB as that would be a fix all solution for my particular circumstance, and I dare say a few other people too.

Not without programming and recompiling.

Okey dokey.

Thanks again.

@wuffles If you want to run both v18 and v19 you can’t use single MySQL db.

You can revert to using default local sqlite on each device and use below to keep watched status in sync

https://github.com/watchedsyncforkodi/service.watchedsync

1 Like

Cheers. I’ll maybe look into doing that once v19 is working better for me on my Vero.