NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Discussion and support › Units with different refresh rates
marqs.I have several OSSC’s, all 1.6. My first I got off eBay and the rest from here.
I’ve connected my current OSSC to an n64 with Mario kart 64 and scart with luma. I’m getting some inconsistent results with the ones purchased from VGP when connecting to my capture card. Some will match the rates of my original and I get a signal. Others have a slightly different signal and so I don’t get a picture.
I’m using default settings for all.
[IMG]http://i68.tinypic.com/wugcow.jpg[/IMG]
[IMG]http://i63.tinypic.com/2cmq52r.jpg[/IMG]
[IMG]http://i66.tinypic.com/axi9aa.jpg[/IMG]
did you try to power cycle the N64 a couple times to force OSSC to re-lock on to the signal?
Yes. On the OSD it would show the same refresh rates as the working ones, but I wouldnt get a signal to my capture card. I think cycled through the all the inputs and back to it, and it would show the odd refresh rate
Do you get an image on your monitor? Do you get a consistent reading with other sources?
It does work with the monitor. I tried it with the Super Famicom and got similar results. Maybe the capture card is just too sensitive to rate changes? I just think its odd that this single unit doesn’t share the same rates with the other 5 units i have.
Yeah it’s very odd for sure. Try something like a Genesis, that doesn’t have the weird jitter problem the SNES has?
The refresh rate shown on the screen is indicated by the digiziter chip and is not always fully accurate. Upcoming firmware has an option to display FPGA-calculated rate which is more accurate and should be uniform (within oscillator tolerance) across units. Even if the displayed rate slightly differs, the output rate should still be same regardless of unit when using one physical console. As for why one (or is there several?) does not work with the capture card, I’m guessing it might be due to variance in those digitizer chips. I’d try tweaking sync Vth and hsync tolerance options to see if they make any difference.
| 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 |
