Thanks. It’s not the Lumagen. It still bleeds like a mofo. I blame the RGB cable. I’ve asked a friend to try to make one that conforms to the information on JunkerHQ.
The same. I can try, but I’d like to note that it’s not reds that are bleeding 😉
It’s the only retro console I have here right now.
jonlad>
By god, there better be some new OSSC videos on youtube soon!
You asked for it :p
By god, there better be some new OSSC videos on youtube soon!
I’d shoot some video, but my image seems to bleed a lot (easiest point of reference is to look at the “0 CREDIT” at the bottom left and see the trails coming off the T). It wasn’t like this with the XRGB mini, where I used a different RGB-Scart cable (it was actually a custom cable that went directly from the AES to the little round RGB input on the front of the unit). The one I used back in the day with my AES, when TVs still had Scart inputs, doesn’t seem to work, and the one that does is from Retro Gaming Cables UK and seems to be of rather low quality. I need something better.
Nevermind what this post said earlier. It works. Just need to try to make it look a little better 😉
Shipping notice received 😀
I ordered on June 24th. Will mine ship one of these days? 🙂
The Lumagen is integral to the professional calibration on my setup. Removing it is not an option.
Thank you. I’d prefer to avoid lag but there is no way around the Lumagen as it is an absolutely essential part of my setup.
Don’t feel too bad; I’m 3778 and just sold my XRGB-mini 😉
I know this is mostly OOP, but has anyone tried the OSSC with a Lumagen scaler? I have a Lumagen RadianceXD, a scaler that is superior to anything ABT has made ;), and I hope this would be a good combo that’s simpler to use than the XRGB-mini I’ve just sold.
| 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 |
