Auto sync mode selection


Viewing 3 posts - 16 through 18 (of 18 total)
  • Author
  • #18701

    So, when you’re on a given input and the OSSC loses sync (such as during a mode change), and you’ve got ‘Autodetect input’ set to ‘All inputs’, the auto input switching starts scanning all inputs for a signal? So if I have two consoles connected, and one of them does a mode change, it will switch to the other console?

    I have thought about that but then I thought who has 2 consoles turned on at the same time? 😛 If it is a mode change on the same sync input so for example AV1 RGBS 240i->480i or AV2 YPbPr 480i->480p then the change is instant so auto input scanning does not have time to kick in. Only on something like AV1 RGBS -> RGsB.

    If so, how much more complicated would it be to start with the ‘Current input’ behavior and fall back to the ‘All inputs’ after 1 or 2 seconds?

    That’s a good idea. I have added that so now after it loses sync it will stay on the Current input behavior for a short time before changing to other inputs.

    Also, how complicated would it be possible to hijack Button 0 functionality when Autodetect Input is enabled, so that pressing it triggers a kind of seek-next functionality? (Not unlike how modern radios can automatically seek to the next station with a decent signal.)

    Its probably a better idea to use an unused button like the Right arrow. What is your use-case for seek-next functionality? Currently if you use the 1,2,3 buttons it will work like seek-next depending on which input is active.

    I encountered a bug where a lot of times the OSSC will not report the correct info on the display after auto switching input. On my NTSC SNES it sometimes even chose the 288p PAL mode. This might be related to the speed of switching but it also happens sometimes when I change the input manually. I’ll have to spend time debugging it.

    Ok so my SNES is actually outputting 288p at 60.55Hz. Apparently it chose to break down when I was testing the auto switching. The pin for 50/60Hz was broken long time ago so I just need to fix that again. It wasn’t caused by the auto switching.


    What is your use-case for seek-next functionality?

    Precisely the use-case of having active video on two or all three OSSC inputs and switching between them. That said, it does seem like a rare/edge case.


    With removing the defective SNES out of the equation, the auto switching is working fine. I also had the incorrect display happen on unmodified 0.79 firmware. I found that when lowering the Sync lpf the chance of varying display info is greatly reduced.

    I realize now that you were talking about Button 0 on the OSSC itself and I have re-used the same functionality and set it to the Right arrow button on the remote. That means it will search for the next input with sync but will not respect the YPbPr/RGsB selections. I will look into fixing that but I think its quite a complex change and free space for firmware code is getting very tight so I have to try to shave as much bytes as possible.

    I added a limit to how many times it cycles through all inputs so its not infinitely switching inputs when it doesn’t find sync because I have seen people say they keep their OSSC on 24/7 and I don’t know if its safe for the hardware to keep switching for so long. Currently its set to 10 times. Just press a button and it will continue switching.

    Here is a test firmware. It is a newer version so your profiles will not load. If you do not save a profile on the test firmware then you can load your profiles again when you flash back to your previous firmware. Also the settings for auto switching do not save yet.

    Do keep in mind that this is a test firmware and in the unlikely event that you cannot flash another firmware you will need to buy a USB blaster ($ 3).

Viewing 3 posts - 16 through 18 (of 18 total)
  • You must be logged in to reply to this topic.