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

High values for --win cause black portion of screen #82

Open
traumedy opened this issue Oct 22, 2013 · 5 comments
Open

High values for --win cause black portion of screen #82

traumedy opened this issue Oct 22, 2013 · 5 comments

Comments

@traumedy
Copy link

I am using values for --win off the visible screen (negative and positive) to crop and zoom a portion of a video stream. Values above 4095 for x2 or y2 cause portions of the screen to be black, right to left for x2 and bottom to top for y2. 4095 displays properly, 4096 displays a black screen. Values below -4095 for x1 or y1 work fine.

To test, use the command line:
omxplayer --win "0 0 5760 4320" pathtomedia
.. and you will see it blacks out the right side and bottom of the screen.

@Ruffio
Copy link

Ruffio commented Jun 17, 2015

@traumedy is this still an issue?

@popcornmix
Copy link
Owner

This is a limitation of the hardware (12 bits registers for coordinates of rectangles in the HVS).
Why exactly are you doing this?

@traumedy
Copy link
Author

I was using this to create a video wall, one Pi per monitor all playing the
same video stream with --live.

On Wednesday, June 17, 2015, popcornmix [email protected] wrote:

This is a limitation of the hardware (12 bits registers for coordinates of
rectangles in the HVS).
Why exactly are you doing this?


Reply to this email directly or view it on GitHub
#82 (comment)
.

@Ruffio
Copy link

Ruffio commented Jun 17, 2015

@popcornmix if this a hw limitation the issue should be closed as there is nothing to do about it

@popcornmix
Copy link
Owner

Okay, you are relying on the clipping behaviour of the destination rectangle to get smaller source rectangle. Interestingly I did make the (software/dispmanx) clipping handle all four edges recently (it used to only protect against negative values which the hardware doesn't like).

Just tried your command with latest (rpi-update) firmware and it worked fine.
Can you run rpi-update and test again?

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