Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HDMI blackout on 'video_render' creation #286

Closed
kirgene opened this issue Jun 7, 2014 · 4 comments
Closed

HDMI blackout on 'video_render' creation #286

kirgene opened this issue Jun 7, 2014 · 4 comments

Comments

@kirgene
Copy link

kirgene commented Jun 7, 2014

I'm trying to achieve seamless playback using OpenMAX.
I create and prepare 2 video pipelines: for current and next video that is going to be played. I destroy previous pipeline after few seconds of next video playback. So next video is played on foreground. It works fine but when I destroy previous pipeline or create next pipeline my monitor goes to sleep mode.
Running "tvservice -M" I see "HDMI in standby mode" during I create or remove "video_render" component.

I saw the same issue here:
http://www.raspberrypi.org/forums/viewtopic.php?f=67&t=50126.

Also running tvservice monitor and executing hello_video will output "HDMI in standby mode" message.

@popcornmix
Copy link
Contributor

I think the "standby" message is a red herring. It doesn't mean "switched off", it means "attached".
Note the enum for the message is both known as VC_HDMI_STANDBY and VC_HDMI_ATTACHED (with VC_HDMI_STANDBY deprecated as it is ambiguous).

With the next update tvservice will report "HDMI is attached" rather than "HDMI in standby mode".

Note: when I run "tvservice -M" and omxplayer, I get the VC_HDMI_ATTACHED callback on playback start, but it is not related to TV going off - the picture is still visible.

What does "tvservice -s" report when you are running?
That will actually show if HDMI is powered on or off.

@kirgene
Copy link
Author

kirgene commented Jun 8, 2014

I forgot to mention that screen goes black just for a couple of seconds.
When I execute "tvservice -s" during this period I get:

tvservice-client: Failed to connect to TV service: -1
state 0x0 [TV is off], 3069550592x3069549968 @ 8Hz, progressiv

@popcornmix
Copy link
Contributor

Do you see this with omxplayer, or just your own code?
Are you doing the equivalent of omxplayer's -r option?

popcornmix pushed a commit that referenced this issue Jun 9, 2014
…ls needed expansion

hdmi: Include requested mode and allow hdmi drive when edid fails
See: http://openelec.tv/forum/124-raspberry-pi/71491-4-0-4-passthru-audio-50-working-chance

tvservice: More accurate description of standby message
See: #286
popcornmix pushed a commit to Hexxeh/rpi-firmware that referenced this issue Jun 9, 2014
…ls needed expansion

hdmi: Include requested mode and allow hdmi drive when edid fails
See: http://openelec.tv/forum/124-raspberry-pi/71491-4-0-4-passthru-audio-50-working-chance

tvservice: More accurate description of standby message
See: raspberrypi/firmware#286
@Ruffio
Copy link

Ruffio commented Jun 17, 2015

@kirgene is this still an issue?

@kirgene kirgene closed this as completed Jun 19, 2015
neuschaefer pushed a commit to neuschaefer/raspi-binary-firmware that referenced this issue Feb 27, 2017
…ls needed expansion

hdmi: Include requested mode and allow hdmi drive when edid fails
See: http://openelec.tv/forum/124-raspberry-pi/71491-4-0-4-passthru-audio-50-working-chance

tvservice: More accurate description of standby message
See: raspberrypi#286
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants