NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Discussion and support › Profile settings web app
Angelgdl.Thanks to Megari the current 0.82 firmware can load settings from SD card.
I wanted to see if it was possible to make a website that produces the binary file the OSSC needs and it turns out it is!
http://pbnl.byethost7.com/ossc/profiles/
You can change settings for every profile and export them as bin file for importing with the OSSC, or as a json file for importing back into the web app.
The bin file must be written to the sdcard the same way as a firmware update.
It is setup in such a way so that it’s easy to add support for newer firmwares.
With the json file it is possible to import an old profile into the web app and export a bin file for any supported firmware.
Please try it out if you are running 0.82 firmware.
Wow, fantastic work! With this tool then it will be possible to backup/restore profiles between firmwares?
Looking forward to trying this out, thank you very much for your effort (and to Megari also)!
@Bucko Yes as long as you have the settings in the json file you can save a .bin file for any firmware version. Settings that are not found in another firmware will be skipped.
I just uploaded a change to the json output format so it is better able to apply settings between firmwares.
link for recent firmware?
0.82 doesn’t appear to have been published yet. The changes are not in the changelog on the xrgb wiki, and it’s not in the common (is it official?) firmware repository at https://www.niksula.hut.fi/~mhiienka/ossc/fw/.
Firmware v0.82 is still under development, and there’s quite many changes under the hood so it needs thorough testing before a public release.
Awesome, paulb_nl! I was writing a command-line application to do exactly this, but got a bit overwhelmed and eventually sidetracked. Glad to see that this is now implemented!
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.
Ooops I added those new modes to the timing tweaker but forgot the LineX settings. Fixed now 🙂
Anonymous
With the json file it is possible to import an old profile into the web app and export a bin file for any supported firmware.
Can you please explain this. Is it possible to export profiles from firmware .81, before updating to .82?
With the json file it is possible to import an old profile into the web app and export a bin file for any supported firmware.
Can you please explain this. Is it possible to export profiles from firmware .81, before updating to .82?
I believe he means you can import old profiles going forward. As far as I know, there is zero import/export functionality in any firmwares prior to 0.82, so this time you’ll need to manually enter your existing profiles into the web app; but, when 0.83 and beyond come out, you’ll be able to feed that JSON file into the web app to get the newer firmware loaded with your pre-existing profiles.
Anonymous
Got it. I was being a little overly wishful there, but great to see this feature, moving forward.
Nice work on this web app, it is much appreciated!
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):
I’m having a very difficult time fine-tuning the advanced feature sliders. I seem to only be able to use the mouse, which causes values such as H. sample rate to jump from 341 to 352, but I need it to only go to 342. Is there a way to get finer-grain control?
| 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 |
