Start of audio files gets skipped

Hi, since about a month the first two or three seconds of each audio file are skipped. This happens both when I play a single song or when playing a full album. I haven’t changed anything in my setup, so I’m unsure on how to troubleshoot this.

My files are stored on a synology NAS and I use a Chord Mojo dac with a USB connection. But when playing a file on a SD card plugged into the vero over the vero analog out the problem persists.

My log file playing sample-mp3-files-Symphony No.6 (1st movement).mp3 is over here:
https://paste.kodi.tv/refezayara

Try setting keep audio alive.

Thanks, but that didn’t solve it, new log with keep audio device alive at always:

https://paste.kodi.tv/jakehozuse

We need full logs. Please use the log uploader in MyOSMC or grab-logs -A.

here you are: https://paste.osmc.tv/xewigupemu

Have you had any chance to look into the logs? Any other information I can give?

Apologies. Real life has been getting in the way. You have not been forgotten.

Few suggestions to try -

  1. Have you tried other MP3s from a different sources and different bit rates ? The logs show ffmpeg having some sort of problem with ‘float headers’ for the MP3s (I’m not sure what this really means?)

  2. Have you tried enabling/disabling ‘passthrough’ ? If passthrough is enabled then the your chorus D/A should convert the MP3 to an analog signal. If passthrough is disabled, then the kodi player should convert the MP3 to PCM and pass that to your chorus D/A which should convert the PCM data to analog.

1 Like

@grahamh Thanks for the assurance :slight_smile:

@thechrisgregory I removed the dac and directly used the 3.5mm analog output of the vero, that did not help. Thanks for your point re MP3s: the problem seems to be related to the file format, I tried a couple of FLACs, no issues found so far. I’ll try and find if can out if it’s related to particular bitrates.

… and whether this is CBR or VBR. mediainfo is a good tool to check the current details.

In your logs I see

Output configuration: Optimized ===> Default: Best match

‘Best match’ is what we suggest but ‘optimized’ should have no effect meanwhile afaIk.

If you start a song and press the Left button on the remote to go back to the start of the song, does this allow to play the start of the file or does it also get skipped that way?

I have the very same problem. :frowning:

None of the previous suggestions worked for me (keep alive, audio output configuration, fixed sampling rate, etc.). It does affect all audio formats: flac, mp3, ogg, m4a. And it doesn’t depend on sampling rate neither, cbr/vbr, and any sampling and bitrate are affected.

There’s another report of this on the forums.
We are looking in to it

Sam

Not to muddy the waters, but also on my Vero 4K recent updates (from late last year onward) brought in something I have never experienced before - and on same MP3 files from same SSD:

  • first second or so of MP3 gets skipped, this is insanely annoying and was not there before;
  • when entire folder is played (press play button on folder selection), every time it moves to next track it is “loading” forever, have to press back button on remote then can do e.g. up and down to move to next track or previous. Then it is again “loading” forever and have to press back button - all the while this happens it is actually playing the track already.

I would really really like to move back to earlier releases as this has rendered the whole thing incredibly annoying and bordering on unusable (this is Kodi v21.2).

So as per other reports, adding to the phenomenon: it is not specific to e.g. FLAC files (as some reported) and all investigations into file types, framing, etc etc are total red herrings.

On very same set of files that always played OK the recent updates (probably from v21.1 onward) have broken this fundamentally. No settings tweaking help, again the salient crucial clue: with exactly same settings from same device and same files the playback is “adding” two nasty “features” that never existed before. And sorry to say they are fundamental.

I thought I am going to live with this but seeing above report means I am not imagining it and it is not a normal “development”, something is broken.

But… I am not going to move to Vero 5 frankly no need for what it adds… and as I stay on my so far trusted Vero 4K, the above has been admittedly driving me up the wall.

1 Like

sparta300

I reinstalled the October 2024 21.1 release on my Vero 4k+ to get around some of these type problems with 21.2

You can download earlier version here https://osmc.tv/download/

You will have to run the software installer on whichever platform you choose, pick the version of osmc you want, and save it to a blank USB thumbdrive.

All instructions are here … https://osmc.tv/wiki/vero-4k/reinstalling-osmc/

I then turned off Auto Updating in the MyOSMC app

I would only turn off the Auto Update on the unsupported 4K however

1 Like

sparta300

I did purchase a new Vero V so I could continue to receive the latest Kodi releases from OSMC

YMMV

Hi

thank you was about to update on the fact that (as I was paranoid and could not remember how recently this nastiness turned up) I went back to Aug 2024 OSMC image.
And… both problems vanished and I am back to normal now.
So I shall move up to the Oct 2024 image, thanks, so that should still be OK.

I was considering Vero V but at the moment just can’t see (with what I use that fully serves my needs on Vero 4K) that I shall throw it away and move up to Vero V just for OSMC updates… Even if it never updates any more, well… still appalled it is completely dropped from supported devices but ah well…

I’m sorry to hear this.
We promised 5 years of support from 2017 which then became eight years.

At some point we have to move forward. We are still providing security updates.

Out of curiosity: what kind of timeframe would stop you from being appalled?

2 Likes

No probs, realistically (as a SW guy myself) I appreciate support can’t live on forever - it’s just that looking at feature additions I had no plans to acquite Vero V whilst this one serves all my needs… hence it just feels like I’d be forced to get a Vero V purely for the continued support, especially as I was “late arrival” and got Vero 4K+ only 2 years ago - so such if life, I’ll take a hit on that for now.

I cannot help sensing a tad of sarcasm in the question, so to elaborate: it is a bit of a fallacy to count from the start of a time period whilst the product is still sold up to very recent times, but the SW support falls of a cliff relatively shortly after one still buys into the physical platform. It had generous support for generous time, BUT it was still sold as brand new device to many including myself - and under 2 years later it is not faded out, support ends in entirety - for a type of device that might not be bought for 5 minutes before entire new generation is considered to be purchased and so on. The overlap between an actively sold / ‘live’ HW device and the end of SW support for it (with cliff edge complete discontinuation) is, you may appreciate, quite less than ideal :)… Either one had to end earlier (but then of course new generation had to be ready and sold) or the other i.e. support timeline to overlap more with lifecycle of the device still in stock in myriad placed and actively purchased - so the one painful thing here is the timing of the two lifecycles and how they (don’t) overlap sufficiently. But such if life. It feels as if the synchronisation of the two lifecycles was quite unusual… with a cliff edge that came very soon after a given generation of physical device/platform (finally) ended. It is hard to find an analogy in other platforms where HW and SW timelines expose a new buyer to such cliff edge so soon, without proper bridging between the two or gradual rampdown and so on.

Counting from the beginnings of that generation it is and was a very generous time period, absolutely. But the devil is in the little fact that some may have bought it toward the end of a period and as a type of device was not purchased for some months or 1-2 years at most. Silly me, it was anachronistic of me to expect that while it was still a “live” and very much sold device its SW support would then ‘shortly’ after that fall of the cliff. Silly again, but assumed a longer overlap between generations therefore longer (even partial) support to exist while older generation faded out. End was coming, and was extended, much appreciated, but it is still an interesting story - someone could have bought this a year after me and find that a year later all support ended.

Sure, in the world where people upgrade and buy another generation just for the heck of it months after they bought previous version it starts to feel “normal” but call me old-fashioned… 1 or 2 years after buying something one would use long term as a device it is not (my) normal expectation to blink and find it has ended all support already… without an ample overlap, but I appreciate for very heterogenous i.e. multi-HW platform cases it’s always a pain.

So to quantify it, well how long is an ideal piece of string :slight_smile: but I admit it was quite a shock that a device still being actively sold (and only bought 2 years ago by myself) reaches such a point in life cycle that all support is gone.

Re: the reported issue, indeed if it’s helpful then certainly something between these two releases has gone astray (might be inter-related, the endless “loading” whilst track already plays should not in theory have something to do with actual skipping of initial audio frames but… purely speculating).

Hi,

I don’t want to force a Vero V on anyone and I’ve made it clear that if it works well for you now, it probably will for a long time yet. Where some users have got concerned is that they’ve thought end of support means it’s dead. It isn’t. It still gets security updates and after they are gone if you have it in a good network environment you won’t have any issue whatsoever. Main pointer: don’t port forward SSH

Playback is the main feature, and we’ve left that in good standing. There is a seeking issue, but that fix is backported.

No sarcasm, I genuinely don’t know what people’s expected lifespan in a device is. There are still people using 2009 era WD TV Lives and only upgrading when they find new codecs don’t work. They are not connected to the internet though so they had a good lifespan.

I do think we made deadlines for SW support quite clear on our website.

Vero 4K/4K+ still has a future for the willing. The device was officially upstreamed in to the Linux kernel. It means you could run the latest kernel to date using something like Armbian or LibreELEC, but you won’t unfortunately have feature parity with what we offered. Maybe it will work for you if you need the latest and greatest, maybe it won’t. You’d probably be better off just ensuring your device is isolated on your network.

The last Vero 4K+ sales were around January/February 2023 and supported ended in January 2025 officially but we extended this until March 2025. There will be a May 2025 update for Vero 4K/4K+ but this really is the last update.

I do get your point and your complaint is more valid than those that have bought devices in 2017 and are disappointed about the discontinuation of updates in 2025.

Going forward, I will think about how to learn from this and manage customer expectations. Hopefully you can appreciate that it is not easy. COVID-19 delayed the transition from Vero 4K+ to Vero V and it all got a bit muddled from there.

Cheers

Sam