v1.2.22, v1.2.22_G Beta version for Z9X 8K/Z30 PRO/Z3000 PRO/UHD8000 (UPDATE)

My television, see signature, supports TVLED. With TVLED it is always RGB and 8 bit.

 

It's already on the buglist - behaviour has changed but several components of the OS nod off after 24 hours.

I've been waiting for someone else to notice this!!

 

This is standard LG TV behaviour

 

I noticed it too but it boots immediately at a button press, so didnt feel like it was much of an issue.

 

Does Zidoo follow any kind of change managment processes? Why do they keep breaking stuff that's already been addressed in past? Where is the QC

 

I've given up explaining this.....

 

Let me help out...I'll get crayons too!

 

In Dolby Vision (DV), "RGB tunnelling" refers to a method where the 12-bit DV signal (including metadata) is transported over an HDMI connection within a standard 8-bit RGB signal. This allows TVs to receive and process DV content even when the source device only outputs an 8-bit RGB signal. Essentially, the DV information is "hidden" or "tunnelled" within the 8-bit RGB stream.

 

In my experience, only the POWER button from the remote will wake up the player. The delay isn't too bad, a couple of seconds. It takes considerably longer to restore all the network connections, which means that any content, such as music on the NAS won't play. In my usage pattern, all this is done "blind" with the TV turned off.

I'd be a little bit less irritated if the Z9X 8K responded to the Android app when it is in this sleep mode. However, that is not the case. The app seems to think that the Z9X 8K is on and playing music. There is no wake up option and the power button only offers options to power off, reboot or a timed shutdown.

My usage pattern is pretty simple. Most of the time, the Z9X 8K is used as a music player, connected via HDMI to a Yamaha AVR. The TV is off most of the time, while the music plays most of the day. I use the remote or the Android app to pause/play or skip tracks. I have another remote and app to control the AVR. I only turn on the TV when I want to watch something. This may not be every day. Some days I might not play any music or watch nay TV at all.

This bug makes the whole experience very frustrating since I can no longer drive the Z9X 8K without a TV after it has gone to sleep. I'd prefer if the Zidoo never entered the sleep mode. If that can't be done, at least change the timeout to something like 7 days, not 1 day.

However, given that the Zidoo has support for digital signage mode, I would think that going to sleep would be a problem.

 

Have you ever heard the phrase live and let live?

Everyone has different needs and usage patterns.

In the words of Monthy Python: "Yes! We're all individuals!" and if you don't get that reference, I suggest watching this movie.

 

I don't need the explanation, I know it. That's why I wrote that with TVLED it's always RGB 8bit.

 

Sorry - misread your pots!

 

not to worry, someone will certainly need your information it is asked again and again

 

Ya that could be that I'm just using the power button every time out of instinct as the button to use and because of where it's programmed to on my Harmony. I had that thought after I posted that it might not be any button press and only the power button.

Mine does seem to fire up and be usable immediately, but I use PlexToZidoo, so not sure if that could be a factor in that?

For your situation, it sounds frustrating. For mine, it's been a non issue, but what has been annoying is 1 of my 8K boxes gets locked into the "HELLO" on the front display and needs to be unplugged for both power and HDMI to get it to reset and work. That happens more than I would like and is getting annoying. Hopefully they can fix both as we should ideally have the option to never have it go to sleep.

 

That does sound very annoying. Do you have any peripherals / storage devices connected? I've recently run into an unbootable situation when I had a USB stick with a Linux Live distro image connected. Perhaps the boot process is not completely reliable when there are other devices in the mix.

 

With all due respect, normally nobody connects a Linux bootable USB stick to a Zidoo. It makes no sense unless you are experimenting with the device and you must realise that it can lead to problems. Otherwise, such a stick has no place on a media player.

 

It's a Linux live image that contains video editing applications and the video files that have been edited with them. All I wanted to do is play the video files that I edited and stored on the USB stick. There's nothing weird about that.

That's preposterous! It's removable media with user generated content. ANY system should deal with that gracefully. It should not crash or otherwise misbehave. If it can't handle the content, it should simply ignore it.

 

I had mentioned it before, but I wanted to make sure it hadn't been overlooked.

I don't know if it's already on the buglist but I still have the problem since the latest firmware update that all DV files don't stutter as much as before but it still starts to stutter a little from time to time. After restarting the file it is usually gone, but as soon as you stop the file and let it continue running, the stuttering starts again.

This is quite annoying if you have to keep trying until the file runs smoothly.

 

From my point of view, the reaction of the device to a bootable USB stick is understandable, I assume the developers have also left themselves a possibility to boot the device in another way in order to investigate it in case of an error.

 

Such option should be configurable, disabled by default and probably hidden in some developers only menu, as in 99.99% cases none of the users is intended to boot player from any sources other than built-in flash.