Need advice about chaining OSSC with the Framemeister
- This topic has 0 replies, 1 voice, and was last updated March 4, 2021 at 1:12 AM by .
Viewing 1 post (of 1 total)
Viewing 1 post (of 1 total)
- You must be logged in to reply to this topic.
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Discussion and support › Need advice about chaining OSSC with the Framemeister
Hey, I have an OSSC that I am using to play various consoles including my 1CHIP SNES. The OSSC works fine with my monitor. However, I use a HDMI splitter so I can split the signal to my capture card, but my capture card (Magewell Pro Capture HDMI) does not like the signal and there is constant flickering in all modes (by the way, I also tested running the HDMI directly into the capture card without the splitter but there was still the same issue). The capture card works with all other consoles so it must be the weird sync from the SNES. I am aware that the dejitter mod is available and would most likely fix it – I’m capable of doing the mod, but without going into all the details why, I want to leave my SNES console stock and unmodded.
I have heard that the Framemeister is capable of correcting signals to make them more compatible. I have considered getting a Framemeister and running the HDMI output from the OSSC into the Framemeister HDMI input, then connecting the Framemeister’s output to my capture card. Assuming this would work, it would mean I can get the lag-free output from my OSSC to my monitor for gameplay, but also have the Framemeister fix up the signal for my capture card to work with it. Possibly a bit ridiculous but I can get a good deal on a Framemeister. The problem is that I don’t know for 100% certain that it will work, so I was wondering if anyone here happened to have any knowledge on this and could help me out before I buy it. Thanks for any help.
| Cookie | Duration | Description |
|---|---|---|
| _gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
| Cookie | Duration | Description |
|---|---|---|
| __gads | 1 year 24 days | The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites. |
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
| Cookie | Duration | Description |
|---|---|---|
| IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
| test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
| Cookie | Duration | Description |
|---|---|---|
| ct_checked_emails | session | No description |
| ct_has_scrolled | session | No description |
| ct_mouse_moved | session | No description |
| ct_screen_info | session | No description |
| wordpress_apbct_antibot | session | No description |
| wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5 | 2 days | No description |