Aggregated list of bugs in HT5 v4.3.52 (All SOCs)

I haven’t had a crash under any circumstance so far. Today I was reviewing a 3 season TV series jumping all over the place and exiting etc.

 

Unless your development team has a strict change control process in place and is prepared for branched builds and software distribution, you'll end up with hotfixes being done from the most recent development branch. That means picking up many of the changes that are work in progress. I'm not intimately familiar with how Zidoo have set up their dev, staging, beta and release environments, but on my past projects, each one of these only supported one current version and each update had to be incremental. It was not possible to do a roll back in an environment (you could revert changes, but the build number would always increment), but it was possible to switch between them (for example move from a beta stream to a release stream).

My guess is that Zidoo don't have anything that complex. They probably have just local dev environments and a release build environment that is manually updated from the dev.

If all that sounds a bit too complicated, just think of it as the updates being based on whatever the developers are currently working on, instead of just patching a single thing on the old versions. (BTW: That's not the best strategy)

P.S. : This is all speculation on my part. I don't actually know the Zidoo specifics, I've just seen the details of software maintenance and hot fixes in many organisations.

 

Thanks Netmask. I'll finish updating my collection (doing a bulk rename now) and try the new version.

 

Haven't nailed it down yet - on one box (Z9X 8K) it crashes on every collection when you exit the collection screen.

On the 8000 it doesn't do it at all.

(You can update and then uninstall and it'll revert to the firmware version of HT if you want to try it. So for example if you're on v4.3.40 now, you can install v4.3.52 to test, uninstall, and then install v4.3.40 again.)

 

I'm on a Z9X 8K, installed 4.3.52, cleared database and scanning now. Fingers crossed, it'll be all-right. If not, I backed up the database just before the update.

 

Quick update - I think you'll be ok - I just did a factory reset on the Z9X 8K and that fixed this crash issue - so no idea where it came from... My boxes do tend to get buggered around with more than most though...

Have updated the first post to reflect.

 

Thanks for keeping the list up to date.

I'm now running into the new #1 bug on the list - NFOs are ignored when scrape fails. So far 12 unmatched items, where I was expecting at most 4.
A very minor issue, if that is the worst bug.

 

Z9s with 4.3.52 patch.

TVDB and TV Maze not adding Director's info on poster wall for tv shows and media info and cast info is initially very slow to load.
However it works fine on TMDB.

Unrelated little bug: Weather app location search not working 'failure to obtain weather data' after searching for a location.

 

I am scanning my hard drive and it's not downloading anything at all. I own the Z9S and I tested the HT versions RTD1296 v4342 (which worked until yesterday) and v4352 (which doesn't work).

 

I just fully reset HT5 v4.3.52 on a Z9S then added two sources - one with 100 movies and one with 2 TV series (both no local NFOs).

 

Since my post today I have been scanning the films and so far almost 60 films out of 621. Very slow!!!!

 

Something's very badly wrong somewhere then.

On a Z9S, scanning rate is about 1s per film if media info scanning is on and approx 0.5s per film if it isn't.

 

If a scan also involves an Internet scrape, these time estimates can blow out significantly due to external factors.

I'm seeing times of about 3 seconds per file with a 1,000 Mbit/s down & 50 Mbit/s up Internet connection, here in Australia.

Australian ping times vary a lot from about 2ms to local CDN servers (such as Cloudflare), 20ms to most major cities in Australia, 200ms for North American servers and around 300ms for European sites. It gets worse for countries with poor connectivity, such as South Africa or Chile.

Then you need to also add into account the server speed, which will vary with demand and also any rate throttling. Still, I would say that if you are averaging more than 5 seconds per file then things are slow.

Large scans are slow, my last scan was ~5,800 files and it was not done after 4 hours. It did finish overnight.

 

TMDB api calls are pretty rapid, even if ping is slow - the main driver for speed is MediaInfo parsing of the file - but I agree, if >5s average then something is wrong.

 

I have a Z1000 Pro, which update will work to fix HT movie poster issues?

 

https://forum.zidoo.tv/index.php?th...mdb-fix-v4-3-52-realtek-1619dr-models.100383/

 

Thanks, Deano86 Are you sure it won't create more issues?

 

I'm not sure if this should be considered a bug, but for older users who don't have great vision, it would be great to integrate the modification described below.
Eki Shaw said he would pass on the information, but since you kindly offered to aggregate all the bugs, it would be great if you could pass this on as well.

 

No, not a bug - a suggestion for improvement, so not applicable here.

This thread is for bugs that have occured since the update to fix the TMDB issue - there were and are still a few regressions.

 

Such as what? Yes, there have been a couple of little niggles that have entered into the HT5 operation, but the main thing is fixed.. the TMDB access and thus the ability to update your movie info..and the latest 4.3.52 version also fixes some of those unintential issues that were introduced in the earlier quick fix releases...