That's great news for console games which (excluding VR) aren't likely to jump up from 30-60 fps range anytime soon. PC games I personally prefer to play with higher fps and fixed-interval strobed picture to keep blur minimalNrg wrote:Yep, upcoming HDMI 2.1 adds Adaptive Sync / FreeSync! So Variable Refresh Rates are possible with HDMI 2.1. It's called "Game Mode VRR features variable refresh rate".
"HDMI FORUM ANNOUNCES VERSION 2.1 OF THE HDMI SPECIFICATION":
http://www.hdmi.org/press/press_release.aspx?prid=145
You can get a good overview on what's planned for current OSSC hw by looking into roadmap section on the wiki. Profile support (which is pretty much finished) and line4/5x are the remaining major features that you can expect to be added on mainline fw. Then there are features like scaling filters (e.g. eagle) and line offset adjust (for interlaced sources) that are likely to get implemented as alternative firmwares at least initially. It doesn't make much sense to try upgrading current board by duct taping additional components on it. There might still be one new OSSC DIY board revision with audio support for all inputs (required parts and extra 3.5mm connector should be fittable within current PCB/case dimensions), but beyond that we should be looking into completely new hardware to properly implement any advanced features.Galdelico wrote:If they'll ever come, how do you guys plan do manage major hardware/software improvements to the current OSSC? Something like an HDMI 2.1 integration, new features that get past actual memory limitations, etc. Would it be possible to provide additional boards/components to attach to the unit, in order to make it more compatible and/or powerful?
I'm probably just looking too forward, but the whole project has been exciting to follow since the very beginning, for me, so it comes quite natural to wonder if the idea behind it is to reach the limits of what it can do at this stage - and then move on to the OSSC2, or whatever its successor will be named - or to expand it beyond its current capabilities, and have a device that basically grows up along with the technology it's meant to support.
I'm a bit wary of erasing/writing flash blocks when user is not explicitly saving settings, but I see your point about usability. I'd rather save last used profile number (not data) in the extra slot that currently contains remote control configuration. That way there's less data to write and smaller risk that a profile slot gets corrupted if unit is powered off at wrong moment. I'll implement that in a few days and upload code to github for evaluation.borti4938 wrote:But what I don't like is that the OSSC always loads profile 0 on each power cycle. It's a bit user-unfriendly. If I use profile 4 and switch off the OSSC, I expect that profile 4 is loaded again on the next power cycle.
So what I did is: I kept away profile 0 from the user selection and use this slot as a copy of the latest loaded/saved profile. If you like, marqs, I can send you the code changes
I doubt such HDMI connector assembly. exists.jarp wrote:Btw. does anybody know if there is PCB mounted female HDMI connectors in existence which would have DVI connector's footprint? I am of course thinking about replacing DVI connector of the OSSC with HDMI connector as adapter adds bulkiness a lot. I think there are none as Googling did not reveal anything... Yeah I should've had bought DIY kit but did not have time back then to do the assembly.