DTS, DTS-HD, DTS-X Lipsync (solved)

Ah - ok - this is the DTS sync thread - but as I said, I've seen that (recently) with a Samsung and a Finlux.

 

Having DTS sync issues with my Z3000 Pro, I tested a Dune HD Solo 8K in two configurations : first, my LG TV alone using only the TV speakers and second, with my AVR using EARC mode. In these two cases I never had any DTS or TrueHD sync issues. You can draw your own conclusions, but mine is that it's not the equipment which is faulty.

 

@Markswift2003 - all these new members....

 

Is it supposed to be funny? Tired of seeing your gifs. No one is breaking the rules, if you don't like it just ignore it. Always kissing Mark's feet. Relax, you're old enough.

 

Ok, that's an interesting workaround.
- Where do I find the global offset setting?
- Does "compatibility mode" apply to all Dolby sound formats? AC-3, EAC-3 etc.?
- What about FLAC or AAC? I also get lipsync issues with these two formats. Where would they fit in?

 

Global offset is in the context menu while playing a file.

Compatibility Mode only applies to TrueHD

FLAC and AAC will be affected by the global offset (I assume - never tried)

 

Ok, thanks. Then this unfortunately is no panacea as AC-3 and other non-TrueHD Dolby formats would be anyway out of sync I guess.

 

Logically true enough - but since this problem has no logic whatsoever, you never know, it may well work - unfortunately I can't try it because I don't have any sync problems and it's not something I can simulate.

Every other issue we've ever had I can easily see the logic and understand the cause - even the DV stutter - but this one defies any logic at all and has from the beginning. I mean hell, it might even be a faulty batch!

I have an early engineering prototype here which is stuck on prerelease firmware and for the hell of it I just tried that and that has no DTS sync problems either.

But there's a thought - I wonder if there's anyone who has the DTS sync problem, has later bought an additional player and has (or has not!) got the same problem with the same kit with the new player...

 

Well to me there is 1 major suspect in this matter and other (so called mysterious) bugs.
its stacking FW update over FW update over FW update.
If zidoo wants to get a grip on the problems they should release a full FW release.

Even 'the master in f**ked up updates' aka 'house of cards' aka Windows has the opportunity to get a updated fresh install.

 

I agree, but I don't think that'll happen - they decided to go down this road and it's a one way street.

 

Better call it a "dead end"

 

The thing is that all the previous OTA firmware for previous boxes was never the full image either - they weren't differential in the way that these are produced, but they were cumulative.

Operationally, there would be no difference between installing a full firmware image to installing a differential one - it's not at all like an operating system like Windows - the differential package is exactly that - a "difference" file and once iteratively added the final image is bit for bit the same as a full image.

The only problem, which admittedly is a big one, is the lack of ability to revert to previous firmware.

 

I don't think there's anything to stop Zidoo from providing downgrade differential packages, other than the extra effort it would take to set this up. A binary difference can work either way.

I think it is worth the effort though. The only other alternative for customers that want to go back to a version that used to work for them is to return the unit back to the retailer. The retailer then either has to wear the cost or return the rejected unit back to Zidoo.

You can bet your bottom dollar that if Zidoo boxes are being returned more often than other brands, retailers will not want to handle the brand. It will eat into their profits.

That'll lead to a shrinking market for Zidoo, which means less revenue, less profit, less money to pay their staff, less chance of bug fixes and eventually the death of that business line, if not the whole company.

The right thing to do is to fix the bugs ASAP. In the meantime, give the customers an option to choose which firmware version they want to use. That means the freedom to upgrade/downgrade as each person sees fit.

 

as for my very little experience with media players and more than modest setup :


my TV : sony LED 65X9505 ( bought when it went out september 2019, early DV)
My Amp : Denon X4300 ( with a 5.1.2 jamo+ svs setup) ( DV compatible for passthrough)
HDMI Cables : all certified high speed 2.1 48gbps


I had UB420 to read my discs ( a very minor audio offset (every audio format alike) was necessary to be perfect with my setup). ( 2 HDMIS. Audio and vidéos separately)


And then,


First i got a R_volution 4K. ( realtek)

HDMI video out to TV
HDMI audio out to AMP.

Audio : No A/V delay. everything in sync.
Video : STD DV -> pink image. LLDV -> great image ( a bit dark) -> i guess my 2019 tv cant handle TV LED DV. boohoo for that.

BD Menus work great. no pb.
No major issue. ( apart from maybe a bit of judder)


Then i switched to R_volution 8K. ( amlogic)

HDMI AUDIO+VIDEO to the AMP. and the AMP to the TV.

Audio : DTS out of sync. had to adjust offset.
Video : TVLED DV - > works ok ! why it is working? does my amp tamper with EDID? Very good picture. a lot smoother than realtek soc ( i think?)

VC1 Macroblocking. ( R_volution just caught up with this issue..)

Some BD menus dont work well. The overlay often fails to display chapters images, or some part of menus ( also the case on some menus with Zidoo. i guess the SOC is young =).


So i switched to Zidoo Z3000.

HDMI VIDEO - TV
HDMI audio - AMP.

-> TVLED DV -> pink image. as it was with realtek R_volution. ( if i dont use custom EDID, TV LED option is not showed. Only LLDV. Which i'm using)
-> STD DV - great picture ( a bit grainy/ oversharpened maybe?)

Audio -> DTS Delay. had to adjust offset.

VC1 works fine. no macroclock on my few tests.
BD menus work fine . on par with R_volution. maybe even better in some case.

i have not had the time to play with HT apk, or even watch several movies but for the few 10 min tests i had, playback was smooth. Audio quality was great.

i only play ISOS ( UHD/BD) . No tv shows or movies from the streaming plateforms.

i'm curious. Do people who watch only UHD or BD rips have as much problems with stutter etc than people who watch mostly downloaded streamed contents?

thats all folks ! ( i know you can hear the jingle)

 

sorry for the offtopic chatter but

In theory there is a difference between the previous version and the update. But! Is this true? Has everybody updated to the same FW? Is somewhere an update package refused?
And what about all those settings that became (ir)relevant are they updated too?
Clearly there is a big difference in behavior between the boxes. Do they really have the same software?
An installer with a system check would be nice. something similar to "sfc /scannow"

 

One of the problems with differential packages is the sheer number required to allow fully agile updating and downgrading - you need a dff specific to every available firmware and to every proposed target firmware for each box - or at least a pathway, and the number increases (probably exponentially, but I can't be bothered doing the maths) as more firmware revisions are added.

The previous argument over the inability to downgrade firmware was that different hardware revisions could lead to issues when downgrading and there was always the possibility of bricking the device. But Dune always managed it and in fact on earlier Zidoo boxes there was a sneaky way of doing it that wasn't made public. As far as the AML boxes go - different SOC, so I don't know if that argument holds water or is even used anymore, but again, Dune AML boxes do it and Zidoo don't.

On one hand I disagree with the use of differential firmware and on the other I understand and somewhat agree - There are a lot of features that Zidoo get right and Dune & R_Zappitilution get wrong - there are several areas, particularly with regard to Dolby Vision and HDR agility that Zidoo have correct but Dune/R-Zap have incorrect and I understand Zidoo wanting to protect their IP, particularly when it has been stolen before and apparently the AML SOC isn't as secure as Realtek in this regard.

 

Not really sure what you're asking - but yes, if you update your Z9X 8K to v1.2.05 and I do the same, regardless of the path we took, we both have exactly the same firmware - because everything is validated with checksums along the way, it can't be any other way.

 

The reason you get a pink image with TV Led is because that TV doesn't support TV Led, so all you'll see is the raw 8-bit video which is presented in very attractive shades of bright pink and red!

I think Sonys finally started supporting TV Led around 2021... not 100% sure though.

Don't know why the R_Zappitilution 8K gave you a correct image - possibly you had VS10 switched on, or the logic in the HDR options in the firmware was incorrect - a strong possibility because although I don't have an R_Zappitilution box, I do have some Dunes and they're both made by the same OEM and I know the Dunes have a couple of logic flaws in their HDR settings.

 

In each cases, ( zidoo/Rvolution4k or Rvolution 8k) i have VS10 enabled for DV and HDR contents. ( and HDR to DV processing).