HT5 v5.0.68 Beta Version (UPDATED)

We're closely monitoring firmware updates. Those of us who suffer from video stuttering during long viewing periods or after frequent rewinding (10%, 20%, 30% jumps) are eagerly awaiting the new firmware.

 

Thank you. Much appreciated

 

New reception in the media library. Zidoo 8K loads Dynamic Picture into your media library for your movie collection. This brings a new home theater experience and looks stunning! Enjoy!

 

Hello, may I ask whether you are playing the video via Media Center or Poster Wall?
Additionally, could you please help confirm where the video source is stored? When performing long or frequent percentage-based fast forwarding, which video formats (e.g., MKV, ISO, Blu-ray source, etc.) mainly experience stuttering?
This information will help us pinpoint the issue more accurately.

 

I only launch movies through the Media Center.
https://forum.zidoo.tv/index.php?th...se-settings-updated.100532/page-4#post-265292
https://forum.zidoo.tv/index.php?th...-version-for-z9x-8k.101367/page-5#post-265214
In addition to what's been said in these posts, I can add another factor that, in my case, causes frequent stuttering: using fast-forwarding (jumping by 10, 20, 30%, etc.). When I launch a file and search for a specific part of the movie, frequent stuttering occurs at some point in the process, which can only be stopped by restarting the media box. If, after frequent rewinding and the stuttering, I stop watching the file and launch another file, it will also stutter.

 

I have two questions. I don' know when the following two options were exactly introduced. Never recognized it before.

1.
What exactly is the “Clear image cache” option?
Does it only delete the database of all image mappings?
I ask because if you manually add a poster from a local directory and then replace it later, but the file still has the same name, it is not displayed as updated. If “Clear image cache” only deletes the mappings in the database, then the updated image would actually be used after remapping.

2.
The same applies to “Clear matching history cache.” Does this only delete the database?
If, for example, the NFO file is not recognized correctly during matching, you would have to rescan the directory so that the corrected NFO file is recognized. This function would make it easier to fix this, right?

 

1. This clears the images that are cached on the posterwall - if you click this the posterwall has to repopulate in the same way it does after an initial scrape.

2. Not 100% sure - it should clear old matching stuff that clogs up the database but isn't part of the currently active content but I can never get it to behave as I'd expect. It certainly doesn't clear the database.

If you want to update from new NFOs not recognised during matching, this feature is part of the next update - I'm just waiting for the changelog to update this post.

@Zidoo Support-Kim can we have some clarification as to what "Clear match history cache" does please?

 

New version HT v5.0.68 posted on the first page.

I'm waiting for this to be posted on the Zidoo server so at the moment it's my own Mega link.

Also awaiting the official changelog, but this version allows NFO metadata update for files previously scraped on TMDB etc, TV Show ratings and collections/series appearing in Watching.

 

And vastly improved too! Nice touches to the in-progress banners.

Very nice.

 

Not really, it's 6-10 in my case and almost 90% of all new released movies.
Personally I've this function off.

 

Thanks for the new update! In the watching section, it's now possible to see which episode you're on, which isn't bad, but now all the titles are displayed in this section. This means that episodes I've already watched are listed with a note that I'm on episode 0. Even all the movies I've watched are now in this list.

Is there a way to disable this completely?

 

Thank you Mark. Hopefully we will get an answer from Kim.

 

Use the "Mark as watched" feature to mark the item as "Watched".

 

Hello, it is recommended that you try connecting a USB external hard drive or a SATA mechanical hard drive (non-SSD) to your Zidoo device, then play the video that previously experienced stuttering to see if the issue improves.

 

In fact, “Clear matching history cache” is only useful when a scanning error unexpectedly occurs — under normal circumstances, you won’t need this feature. Moreover, this option only clears some unnecessary cache, so its significance is quite limited.

 

Thanks for your tip, but that's exactly the problem: the series and films are marked as “watched.” I can only remove them from the list if I mark them as “not watched.” But then it doesn't make sense anymore. I don't understand why everything has to be listed anyway. The idea behind displaying the episodes is practical, but visually it looks more bad than good. I hope there will be an option to disable this feature again.

 

Isn't an internal SATA SSD the simplest, fastest, and most reliable connection? My Samsung 860 EVO 2TB SSD is a very reliable drive; it's never had any issues. As I mentioned, there aren't any specific files that cause stuttering. Stuttering does occur after extended viewing periods (over 1.5-2 hours) and after frequent use of the jump controls (10, 20, 30%) and rewinding with the large round button on the remote (long press of the left and right arrows).

 

@Markswift2003 It's funny how every show on my watch list shows the wrong labelled episode number, but when I click on it and go into it, everything is okay. I can't seem to figure out if it goes by watch history, where is it pulling these wrong episode numbers from..... lmao.


edit: Also, Trakt no longer works. No progress gets sent to Trakt anymore after continuously getting signed out every week or two. The manual sync button also no longer works.

 

Hello, when the issue occurred with your Poster Wall, did you happen to restore from an old backup or clear the data and rescan the library?

 

Just to chime in on this - I had this issue, but restored from an old back-up (z1000pro), and by looking at it, I surmised that was the issue.