OSSC Pro : UI suggestions

[Hojo_Norem]

Had my Pro for a few days now and so far I’ve been impressed.  My C64 (with self-built c0pperdragon component mod) just needed a little tweaking on the B/Pb offset  and my PS1 was near perfect out of the box.  I have plenty more machines to try out so that brings me to my first request / suggestion…  The remote has that bank of ‘P1’ to ‘P9’ buttons at the bottom.  How about letting us assign profiles + video input to them?  I’d be fine doing it via prof_n.txt.

 

Next request ties in with the first.  Could we have the profile name show on the OLED instead of the input name if it’s been defined in prof_n.txt ?

 

There are still plenty of unused buttons on the remote.  Could one be used for quickly cycling through audio inputs?

 

Concerning the current shortcut buttons on the remote, ideally repeatedly pressing the same button should cycle through the menu options.

 

And lastly (not a UI request):

50Hz ‘squash’ compensation to restore the proper AR.  Having a per-profile option to automatically apply it on detection of a 50Hz signal would be perfect.

 

Thanks.

 

• This topic was modified 8 months, 2 weeks ago by Hojo_Norem.
• This topic was modified 8 months, 2 weeks ago by Hojo_Norem.

[Zacabeb]

I second all those suggestions. 🙂

[triple_lei]

Maybe double the size of the OSD when it’s in 1080p? At the distance I sit, sometimes it’s just easier to read the display on the OSSC Pro itself.

But yeah, let’s definitely use the “unused” buttons on the remote for our 9 favorite profiles. It’s already got the letter “P” on the buttons!

[Hojo_Norem]

Just a small update – Discovered that the advanced timing menus (at least for the scaler) maintain separate states for different video formats.  This means that a single profile can store manually zoomed settings for 50Hz (interlace and prog stored separately) and unzoomed for 60Hz.  Tested this with my modded PS1.

I’ve taken a look at the source code and if I can manage to get a toolchain setup (looks like it’ll be a Linux VM) then I might have a crack at adding the profile shortcut.  These one part I need a little clarification on:

NOTE: If you want to generate distributable bitstream and do not have Intel VIP license, disable alt_vip_* modules in Qsys before platform generation and comment out `define VIP at the top of rtl/ossc_pro.v. 

I’m assuming that is relation the the de-interlacer.  Does it mean that I can compile regardless of having the licence and it’s a (not)simple case of copyright violation if I distribute the binary (not that I would in that case) or is it a case that the licence is also a physical signed file and Quartus will stonewall me with a “Give Intel some money to continue” error?

 

Oh, one last thing, what RC protocol does the OSSC use?  I want to build a device to extend the OSSC’s front panel controls (daily driver functions like profile shortcuts, input select, etc) and rather than ask for a UART I could dangle a IR diode in front of the OSSC’s sensor.

[Author]

Posts