Strato V black screen and audio cutout issues

[rafaelsmith]

As a relatively recent new user, having gotten my Strato C in April, I can definitely relate to the frustration of having my very expensive new device seem to not work. With the C having been around a while, I was able to troubleshoot my issues by just searching this forum and never having to contact support or make a post about it. My black screen issue was addressed by lowering the connection speed. Which seems sad at first, but made no difference in the PQ for me. Ultimately I think HDMI is the bad guy here in most connectivity instances, as @thrillcat pointed out. Maybe there’s something deeper in the K code that can address this or maybe there’s a firmware update for the brand new product that will help. I would also note that I had the very same black screen frustration with my JVC NZ7 with just connecting my Oppo and ATV, until I installed their firmware update. I guess my point is, yes it sucks in the moment, we need to end the tyranny of HDMI, and that usually there is a solution to the black screen, and then we can enjoy our devices as intended and forget we ever had this problem until we’re lying on the couch with our kids on Sunday morning sipping an espresso and casually browsing one’s forums and remembering, oh yes, I’ve had versions of this issue a couple of times too! My gosh that really sucked for a moment, maybe it would help to say you’re not alone, and thoughtful and talented people will pull you through.

First thing I do whenever I have these types of issues is look at HDMI cables...replace if needed... Make sure to turn off every damn version of CEC anywhere in the chain.

The fact that I have several other devices...Apple TV, Zidoo Z30, Panasonic UBD that do not have any HDMI handshake issues, audio dropouts black screens make me confident the issue is not with my cabling, projector or AVR. This problem is just with the Strato V.

I do not have any HDMI switches or anything else in the chain so my setup is as simple as it can get....Strato V->Marantz Cinema 30->Projector....all using quality cables including the one included with the Strato V. None of the HDM cables in my chain are over 15ft.

Forcing 24hz OSD on the Strato V seems to be a workaround for now.

And yes I despise HDMI.

 

[thrillcat]

My intention was not to minimize anyone's issues. I just found the tone to be a bit over the top, like "oh man I dodged a bullet I almost bought a piece of junk that doesn't work, these guys don't know what they're doing."

Of course it sucks to drop $5K on a player and have an issue like this, I'd be upset too, but I also think you need to have a little trust in the engineers at Kaleidescape to figure out why specific EDIDs are causing the problem and then address it. They now have a much larger data set to work with and can more effectively troubleshoot.

@Edgar I do think your problem is an HDMI cable, if limiting the HDMI data rate is solving the issue. A throughput limitation is easily solved by lowering the data rate. That said, the lower data rate you're using is fully capable of carrying the full signal from any and all consumer media content available today.

Kaleidescape will get this fixed, I'm confident it's a high-priority ticket in their system right now.

 

[Jin-X]

Thanks for the cable testing. But, basing it off the power consumption of the V vs the C is not a good way to look at it as the V came out 7.5 years after the C and there has been no change in movie playback requirements since then. So the V should absolutely use way less power, even with an NVME drive, considering SoC manufacturing/design advancements in that time.

For example let’s look at the Apple TV 4k boxes 4K HDR playback consumption:

1st gen (2017 A10X SoC) 5.77W
2nd gen (2021 A12 SoC) 3.41W
3rd gen (2022 A15 SoC) 2.31W (fan was also removed from this model as it was no longer needed)

Perhaps there is something going on with the power/voltage being supplied to the HDMI port, but it’s not due to the V’s power consumption being too low.

 

[Broncowrangler]

First thing I do whenever I have these types of issues is look at HDMI cables...replace if needed... Make sure to turn off every damn version of CEC anywhere in the chain.

The fact that I have several other devices...Apple TV, Zidoo Z30, Panasonic UBD that do not have any HDMI handshake issues, audio dropouts black screens make me confident the issue is not with my cabling, projector or AVR. This problem is just with the Strato V.

I do not have any HDMI switches or anything else in the chain so my setup is as simple as it can get....Strato V->Marantz Cinema 30->Projector....all using quality cables including the one included with the Strato V. None of the HDM cables in my chain are over 15ft.

Forcing 24hz OSD on the Strato V seems to be a workaround for now.

And yes I despise HDMI.

That’s exactly what I’m also trying to emphasize but maybe not doing a great job putting it across. The hdmi issues are indeed a pita and I have recently invested in all 10’ Pixelgen cables for my HT to keep things consistent across the board and eliminate a potential variable from the equation. Every other component like you also mentioned, is behaving fine except for the V. I have dealt with these issues in the past and have used that vast experience to navigate through them.

It is also imperative to note that we are early adopters for the new V; we are learning (while fighting fires) on the fly and indirectly paving the way for future owners. Also need to understand that the C is now a mature product and is in its current stable state. I’m sure that wasn’t the case upon inception.

I invariably struggle to understand when some folks downplay and tell others how to deal with their issues. Every individual deals with their set of circumstances/issues differently. We all have varying thresholds of tolerance. It’s not as if we are cyber bots programmed to operate in a similar manner. Life would be so boring in that ecosystem. Lol. You will finds these samples across various forums.

As a relatively recent new user, having gotten my Strato C in April, I can definitely relate to the frustration of having my very expensive new device seem to not work. With the C having been around a while, I was able to troubleshoot my issues by just searching this forum and never having to contact support or make a post about it. My black screen issue was addressed by lowering the connection speed. Which seems sad at first, but made no difference in the PQ for me. Ultimately I think HDMI is the bad guy here in most connectivity instances, as @thrillcat pointed out. Maybe there’s something deeper in the K code that can address this or maybe there’s a firmware update for the brand new product that will help. I would also note that I had the very same black screen frustration with my JVC NZ7 with just connecting my Oppo and ATV, until I installed their firmware update. I guess my point is, yes it sucks in the moment, we need to end the tyranny of HDMI, and that usually there is a solution to the black screen, and then we can enjoy our devices as intended and forget we ever had this problem until we’re lying on the couch with our kids on Sunday morning sipping an espresso and casually browsing one’s forums and remembering, oh yes, I’ve had versions of this issue a couple of times too! My gosh that really sucked for a moment, maybe it would help to say you’re not alone, and thoughtful and talented people will pull you through.

Couldn’t agree with you more with regards to HDMI. Thanks for relating to the issues. It does provide some level of comfort and reassurance. Much appreciated.

 

[rafaelsmith]

That’s exactly what I’m also trying to emphasize but maybe not doing a great job putting it across. The hdmi issues are indeed a pita and I have recently invested in all 10’ Pixelgen cables for my HT to keep things consistent across the board and eliminate a potential variable from the equation. Every other component like you also mentioned, is behaving fine except for the V. I have dealt with these issues in the past and have used that vast experience to navigate through them.

It is also imperative to note that we are early adopters for the new V; we are learning (while fighting fires) on the fly and indirectly paving the way for future owners. Also need to understand that the C is now a mature product and is in its current stable state. I’m sure that wasn’t the case upon inception.

I invariably struggle to understand when some folks downplay and tell others how to deal with their issues. Every individual deals with their set of circumstances/issues differently. We all have varying thresholds of tolerance. It’s not as if we are cyber bots programmed to operate in a similar manner. Life would be so boring in that ecosystem. Lol. You will finds these samples across various forums.

Couldn’t agree with you more with regards to HDMI. Thanks for relating to the issues. It does provide some level of comfort and reassurance. Much appreciated.

I will be honest and admit that I am more willing to "understand" these types of issues with a $200 device moreso than with a $4k device...but thats on me.

 

[Broncowrangler]

I’m wondering if i download furiosa again. Curious if a fresh download would mitigate the above issues. I haven’t been able to get clarity on that.

 

[Broncowrangler]

I would also like to add that Furiosa exhibited some intermittent brightness fluctuations/changes. For example a really bright scene would suddenly dim down momentarily and then get bright again. This happened during the course of the film.

 

[Packers]

I would also like to add that Furiosa exhibited some intermittent brightness fluctuations/changes. For example a really bright scene would suddenly dim down momentarily and then get bright again. This happened during the course of the film.

Which version did you download. The DV or HDR10 version?

 

[Broncowrangler]

Which version did you download. The DV or HDR10 version?

DV. While I’m at it, I have seen this behavior on a couple of other DV titles as well like Fury Road and Kingdom of the apes. The brightness fluctuations is slightly obstrusive and disconcerting. No issues like this on HDR10 titles.

 

[Packers]

DV. While I’m at it, I have seen this behavior on a couple of other DV titles as well like Fury Road and Kingdom of the apes. The brightness fluctuations is slightly obstrusive and disconcerting. No issues like this on HDR10 titles.

Is your display DV capable? If so, the fluctuations may be because with DV profile 5, the device is doing the tone mapping and not the display, which means th device is guessing what you display is capable of. DL the HDR10 version and see if it fluctuates.

 

[Broncowrangler]

Is your display DV capable? If so, the fluctuations may be because with DV profile 5, the device is doing the tone mapping and not the display, which means th device is guessing what you display is capable of. DL the HDR10 version and see if it fluctuates.

Yes it’s DV capable. I have the 83” G2. High dynamic range on the V is at auto (default) which I believe is display led.

Fwiw, LLDV mode will be device led.

 

[rafaelsmith]

DV. While I’m at it, I have seen this behavior on a couple of other DV titles as well like Fury Road and Kingdom of the apes. The brightness fluctuations is slightly obstrusive and disconcerting. No issues like this on HDR10 titles.

I also have had no issues with HDR10 titles but several DV titles have had issues. My projector is obviously not DV capable so something about V playing DV on non DV display is bugged.

 

[Broncowrangler]

I also have had no issues with HDR10 titles but several DV titles have had issues. My projector is obviously not DV capable so something about V playing DV on non DV display is bugged.

It appears V playing DV on DV capable displays is also bugged. Lol.

 

[Packers]

Yes it’s DV capable. I have the 83” G2. High dynamic range on the V is at auto (default) which I believe is display led.

Fwiw, LLDV mode will be device led.

DV 5 is an older profile which was designed for older Sony TVs that could not do TV-Led tone mapping. Designed for pre 2021 Sony TVs.

 

[Broncowrangler]

That’s a bit concerning, tbh.

 

[rafaelsmith]

DV 5 is an older profile which was designed for older Sony TVs that could not do TV-Led tone mapping. Designed for pre 2021 Sony TVs.

Unless the DV version has Atmos and the HDR10 version does not...as is the case with some movie...I am sticking with downloading the HDR10 version. Would be nice if there was a way to make HDR10 the default version....I am not sure why the V plugged into a non-DV device is downloading DV version in the first place....it should default to what the display is capable of.

 

[Packers]

That’s a bit concerning, tbh.

Unfortunately that's the only profile that will work with all DV capable displays and projectors.

 

[Packers]

Unless the DV version has Atmos and the HDR10 version does not...as is the case with some movie...I am sticking with downloading the HDR10 version. Would be nice if there was a way to make HDR10 the default version....I am not sure why the V plugged into a non-DV device is downloading DV version in the first place....it should default to what the display is capable of.

Probably because many have the HD Fury and other processors that can be set up to display LLDV on non DV displays.

 

[Broncowrangler]

Just wondering if should change to LLDV to eliminate those fluctuations. That would ensure device led arrangement and eliminate any display manipulation.

Edit: I had tried LLDV earlier but wasn’t too pleased with the PQ. Auto gives me the best results. Of course ymmv.

 

[Broncowrangler]

Update: forcing it to LLDV (low latency Dolby vision or player led DV) fixed the brightness fluctuations on Furiosa. However the PQ appears relatively drab and dull compared to auto. It’s not as punchy and vibrant as auto. This again is somewhat of a workaround and less than ideal for my specific needs.

But the audio drops on furiosa are definitely there. I played out those scenes several times. 1) 00:50:50 onwards 2)1:13:10 onwards. Both these drops are essentially very short pauses where there was no audio for a split second. More like blips for lack of better terminology. Wish we can get a larger sample size of V users.