Skip to content

Send MRA Rotation in the DV info frame #982

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

Open
TheJesusFish opened this issue Apr 20, 2025 · 7 comments
Open

Send MRA Rotation in the DV info frame #982

TheJesusFish opened this issue Apr 20, 2025 · 7 comments

Comments

@TheJesusFish
Copy link

This would be helpful for scalers to implement automatic rotation of arcade cores while using direct video.

Even sending "rotated" would be fine as there are very few cores that A) aren't CW rotated and B) don't have a flip screen dip switch. Scalers could rotate ccw by default and, in the handful of cores without a flip screen dip switch, folks could just make a custom profile (as they have to do now).

@sorgelig
Copy link
Member

Need to think about it. Currently there is no flag to identify if specific arcade game requires a rotation.

@zakk4223
Copy link
Contributor

the ini [arcade_vertical] tag uses arcade_is_vertical() which grabs the info out of the MRA. You could send 'core needs rotation' flag via the same method.

It doesn't tell you what direction the rotation is though. Most if the rotation tags in MRAs contain either 'ccw' or 'cw' I think so maybe you could use that. If just a 'rotation' bit is sufficient it's just a matter of encoding the flag into the frame in a backwards compatible way.

@sorgelig
Copy link
Member

Original idea i believe is to have correct rotation automatically. If you can't tell which direction to rotate and will need to go to settings of scaler then why not do it without that flag?
Also, most arcade fans i believe rotate their display to vertical position and this flag will only spoil their experience. So it will simply change preference to favor of specific users.

@TheJesusFish
Copy link
Author

Good questions. I was imagining it more as a toggle than a setting that was forced on folks. Like a scaler could implement a switch for "automatic rotation" just like they have for their tate modes (this is, of course, assuming that Mike, the PixelFX guys, or Markus(?) would even implement a feature that responds to the flag in the first place).

The flag would only alert the device that the core was rotated - they could do with that information whatever they'd like.

I would definitely be against having it forcefully rotate for folks who have tate'd monitors - this is more for the "big oled on the wall" crowd. We have a workaround for this (generating a profile for each arcade core and then rotating them manually) - this is would just be a "nice to have".

@sorgelig
Copy link
Member

I understand your point of view. It's good to have everything automatic, but it implies that everyone has the same setup and same usage preference. Such kind of options where it fall to 99% percents of users are already made automatic or default states.

I also look at it from hypothetical normal usage: you start some arcade for the first time, then manually rotate the screen if scaler allows then never touch rotation anymore. Isn't it simple? May be problem is in scaler which require to go deep in menu to change the setting? I don't have such scaler. May be rotation should put into easy accessible menu and automatically saved once changed then problem will be solved, i guess.

@TheJesusFish
Copy link
Author

Yup, that is fair enough. I don't want to upset the applecart for other users either. Thanks for thinking about it, duder. :)

@TheJesusFish TheJesusFish closed this as not planned Won't fix, can't repro, duplicate, stale Apr 23, 2025
@TheJesusFish
Copy link
Author

Reopening this because, on re-reading it, I think maybe I wasn't clear about what should be happening on the mister side versus what would happen on the scaler size.

For the mister side, I was only looking for the DV info frame to say "this is rotated". It shouldn't take any action - it should just have the information in there. It would be on the scalers to act on that information. I don't think this would affect existing set ups, but I also could be missing something obvious.

@TheJesusFish TheJesusFish reopened this Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants