[FBX]

New firmware is released (0.88) that fixes the profile importing bug.

[FBX]

Thanks for the update on that!

[FBX]

Web editor needs to be updated to 0.87. I’m getting complaints my profiles cannot be imported, and editing the version number manually doesn’t work either.

[FBX]

Apparently it’s not just me either. Had someone else message me they can’t get the SNES stable on 0.84 when it worked perfectly fine before they updated. Now I can’t claim to know if 0.83 had the same problem as I never got around to checking that one, but the updates before then my SNES was working rock-steady. Now I have to shift a bit out of phase to get a picture to hold on 0.84. Something had to have been changed during the past few firmwares for my SNES to suddenly become so unstable on the OSSC.

I’ll try the alt build, but the point is something got “fixed” when it wasn’t broken to begin with, so people shouldn’t have to use alternate builds.

[FBX]

I don’t know when this started as I hadn’t done much testing with 0.83, but I noticed on 0.84, my SNES 1CHIP console is now very unstable on the sync (picture blacks out for several seconds at a time). It was never this way before, so clearly something was changed on how sync is handled. Anyone have some insight on this?

[FBX]

I’m having trouble understanding the math here. I know that if I choose line4x for Genesis 320 mode, the horizontal multiplication factor is 4. So what do I put in for H. samplerate and H. s.rate adj to get 427.5? I had artemio make me a spreadsheet to calculate the formula, but when I put in 427 for H. samplerate, I get an effective samplerate output of around 107 depending on the value in H. s.rate adj. I’m just totally confused.

Edit: spreadsheet was missing a parenthesis, which threw the whole formula off. It all makes sense now, and I was right in working it out in my head that a value of “2” was needed for 427.5 for 320 at line4x.

[FBX]

Thanks for fixing that bug in the app! I was able to make a working set of profiles for RGB SCART (except 32X is using HD Retrovision cables in the YPbPr jacks):

http://www.firebrandx.com/downloads/ossc_profiles_fbx.zip

[FBX]

I don’t recall exactly what I did as it’s been a while since I even used the Framemeister, but feel free to check out the Dreamcast + Toro Box + OSSC Framemeister profile I made:

http://www.firebrandx.com/downloads/OSSCTORO.zip

I believe it used HDMI1 input and I was able to dial in a perfect integer scale on it from the 960P source. I even made a comparison picture showing the difference between straight into the Framemeister and then using the OSSC to line double to 960P into the FM’s HDMI port:

[FBX]

The app is missing the 512×240 optimal timing option in the drop-down box on each LineX mode. Can you update the app to include this new feature of firmware 0.82? Much appreciated!

Edit: This is also causing a bug: When you assign 320×240 mode in the app for each LineX box, the OSSC reads it as 512. When you assign 256×240 in the app, the OSSC sees that as 320. So it seems the missing 512 mode is causing a ‘shift’ in the OSSC’s recognition of optimal timing modes from the bin file.

[FBX]

I’ve since started a repository of all new optimal timing research based on the 0.81 firmware. I even found some slight tweaks to improve the Genesis/MA profiles too. All are now text files on my web page here:

OSSC Optimal Timing Repository

Still a work in progress as I’ve got a lot more consoles to go through, but it’s a page that will continue to expand for quite some time!

-FBX

[FBX]

Card is a sandisk and works great whenever I test it for any other applications. I’m thinking the Disk image software is flaky when it comes to these tiny bin files.

[FBX]

Found a stupid solution that works: Make the win32 disk imager write the bin file to the card TWICE in a row. Then it worked fine after that.

[FBX]

Well I’ve not messed with anything lower than line4x to be honest, and in that case (and for line5x as well) I recommend using the “4:3” 256 aspect ratio mode the OSSC offers. There are some alignment issues with 8:7 mode I’m not happy with (one side gets pinched while the other side gets a hair of overscan).

That said, you could see what the 4:3 option does for 256 mode optimal, and see if you can adjust your monitor based on that mode instead.

[FBX]

I do know that there is dithering on Code Veronica for example, and it’s definitely the game itself doing it. Here’s a screenshot I took of a perfectly dialed-in optimal timing image of the title screen:

Code Veronica Title Screen

[FBX]

@Galdelico

Yeah, my capture card detects the various OSSC 480i modes at some very oddball resolutions that didn’t even make sense to me. Interlaced content is just not the OSSC’s cup of tea so to speak.

[Author]

Posts