Jerky playback and no sound on some videos

This is a bit of a long shot but we have a newer kernel that changes the way frame rate syncing is done, it is possible that this might help. You can install it as a test by doing the following:

sudo apt-get update
sudo apt-get install vero2-image-3.10.94-28-osmc --reinstall

After a reboot you can check you’re on the right version with:

cat /proc/version

(It should be -28-osmc. The current released kernel is -27-osmc)

Please let us know if this helps with stutter and no audio. You can revert to the previous version with:

sudo apt-get install vero2-image-3.10.94-27-osmc --reinstall

If this doesn’t help please provide a mediainfo of a file that exhibits the problem.

1 Like

Please see the mediainfo section in How to submit a useful support request - General - OSMC

Thanks for the suggestion. No change though.

Here are a couple of files that have the problem

And here are some that don’t

One of the files that won’t play sound is actually a cartoon/animation. So I don’t know.
Could be like you said, a lot more to the story though.

1 Like

Me neither - it obviously is a little more complicated than that …
Oh well, it was just a theory …

I know that was directed at @TL81, and I don’t want to hijack this thread. However I thought you might find it useful to know that I just tried that test kernel and played part of “Frozen” (3D) - before (GA kernel), basically no sound (and jerky video); after (test kernel), jerky video but with much more sound. I.e., plays for about a second; pauses for about 1/4 second; rinse and repeat but most times when it’s playing we do get sound.
So in our case, it made a … well, let’s just say “difference” :slightly_smiling:

So after today’s update (2016.02-4) things pretty much look the same. I even think buffering has gotten a little worse. Meanwhile things are smooth on the Pi, so I’ll keep on using that for my daily media consumption.

Are you using Kodi’s built in NFS client ? EG in the Video source you have nfs://something ? If so, there has been quite a lot of discussion about this in another thread. There seems to be an issue with libNFS in Kodi, although quite why it seems to be more noticable on the Vero 2 at the moment we’re not sure.

It’s very likely that if you switch to a Kernel NFS mount your buffering problem will be solved. There are various tutorials out there so it’s not too difficult, so here’s a brief explanation of what to do.

First create a directory under /mnt to mount your remote nfs file system. I call mine Mac-Mini:

sudo mkdir /mnt/Mac-Mini

Now add a new entry for it in /etc/fstab. Here is an example to get you started: (leave the existing line in place and add this as a new line, all as one line) /mnt/Mac-Mini nfs noatime,noauto,x-systemd.automount,nfsvers=3,nolock,nofail,local_lock=all,soft,retrans=2,tcp 0 0

Replace the IP address with the IP address of your NFS server (if it has a static IP) or it’s hostname, and the path immediately after that with your NFS export path. The second path is to the mount point you just created.

Once you have saved that try mounting it, replace the path with the correct one for your system:

sudo mount /mnt/Mac-Mini

(The mount options I gave will also cause it to auto mount on boot)

If you look in that folder you should now see files on your NFS server. You now need to change your video sources. Unless you use path substitution in advancedsettings.xml you will need to remove your existing TV Shows and Movies sources and re-add them. This time instead of choosing NFS browse to “Root Filesystem” then mnt then whatever you called yours instead of Mac-Mini, then to your Movie or TV Shows folder and add the source as before.

Give that a try and see if it helps. While performance of the built in NFS client in Kodi doesn’t seem to be nearly as good as it should be for reasons we haven’t worked out yet, a Kernel NFS mount will always be faster than Kodi’s built in NFS client even if this issue wasn’t there, so if you are trying to squeeze every last drop of streaming performance out you are best to stay with the Kernel mount if it helps for you.

1 Like

Forgive me. But I am not experienced with the commandline at all. How do I add a new entry into the fstab file?

Edit: I tried to do it with Filezilla. But it seems I don’t have the necessary permissions. I can read all files fine, but I don’t have write permission.

The easiest is to login with ssh and then edit the file with sudo nano /etc/fstab, but be careful only to add your entry and not change any other entry.

Details regarding how to access the command line interface can be found here on our Wiki:

Thank you for your advice. It really helps a lot.
As far as I can see, having tested for a couple of minutes, it does indeed seem like the buffering has gone. Will watch a full length movie later, to confirm.
Will this issue be addressed in future updates, so one doesn’t have to make these changes manually?

For me, there are only two problems left, keeping the Vero 2 from being the perfect media center. The failure to play some videos with AC-3 sound, and the (approx. 200 ms) audio/video sync issue.
Still I’m happy it looks like we’re getting there.

It would be good if we could find out more about the file you are having issues playing. Please see the mediainfo section in How to submit a useful support request - General - OSMC

Those are already displayed further back in this topic. Along with ones that have no problems.

The audio/video sync issue is consistent throughout all of my files

After testing the April update, I have found that the problem with playing many videos with AC-3 sound, remains. Is this a problem for any one else? And is it something you guys are looking into?
I must say I’m really sad still not being able to use the Vero as my primary media player

I believe we have addressed most playback issues in the last update.

If you’re still having problems some fresh logs will help



First two files are not playing any sound. The third is playing fine.


Is this one of the affected files?

I’d like to see MediaInfo output on it. Kodi believes it to be 50fps, which seems odd for this kind of ‘rip’.

We’re treading a fine line on legality of your rip, but I’d like to know if it’s a poor encode or an issue with Vero.


That’s strange. The file seems to be 25 fps.

The Pi1 with the same version OSMC handles everything just fine.

Kodi will by default output 25fps content at 50hz even if the TV supports a 25fps HDMI mode. (Which most do)

This can be overridden in advancedsettings.xml however to force 25fps content to output at 25hz - usually there is no visual difference doing so though as 50hz is exactly 2x 25.

But that doesn’t explain why there’s no sound, right?

We would need to know more about your setup and your configured audio settings

Audio settings are default as far as I’m aware.
My setup is audio through HDMI to a Samsung TV, and from there, analog audio to a stereo amp.
Is that what you meant, or do you need specifics?