Import and export profiles from micro SD
- This topic has 4 replies, 5 voices, and was last updated January 12, 2018 at 5:28 PM by .
- You must be logged in to reply to this topic.
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Feature Requests › Import and export profiles from micro SD
I think it would be awesome if we could import and export our profile settings from an SD micro card. Ideally importing settings would put profiles back to how they were before a firmware update. If that’s not possible perhaps there could be an option to dump each profiles settings to a text file that could be read on a computer. That way we wouldn’t have to write down each profiles settings every time we do a firmware update. We could just look at the text file on a computer.
I also would like to see this. Below are my comments from the firmware thread. Would like to see a way to keep profiles when upgrading firmware and a way to enable binding default profiles to inputs.
Is there any way to prevent firmware updates from clearing the profiles? Or allow the user to save and store the profiles on an SD card so that updating the firmware won’t affect profiles?
Would also be interesting in binding default profiles to individual inputs until the user changes them manually. Maybe allow this with a config file?
Perhaps the best implementation would be a PC application where user could generate profiles (stored internally e.g. as XML) and export them out to a file (formatted according to target fw version) which can be written to SD card and subsequently loaded in OSSC.
Memory is really tight on the OSSC at the moment, and I am afraid only importing may be viable. I have been working on support for importing settings from the microSD card and even just that takes us within a few hundred bytes (note: not kilobytes!) of using all of the remaining usable memory. I am still trying to get the memory usage lower, but do not expect any miracles.
Writing a PC application to manage settings and write them to the SD card is probably the way to go, especially given that there simply is not enough memory left on the OSSC to maintain any kind of backward compatibility for existing settings when the firmware is upgraded.
I’d really like to see this as well. Has there been any development on importing settings from SD card ?
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Feature Requests › Import and export profiles from micro SD
I think it would be awesome if we could import and export our profile settings from an SD micro card. Ideally importing settings would put profiles back to how they were before a firmware update. If that’s not possible perhaps there could be an option to dump each profiles settings to a text file that could be read on a computer. That way we wouldn’t have to write down each profiles settings every time we do a firmware update. We could just look at the text file on a computer.
I also would like to see this. Below are my comments from the firmware thread. Would like to see a way to keep profiles when upgrading firmware and a way to enable binding default profiles to inputs.
Is there any way to prevent firmware updates from clearing the profiles? Or allow the user to save and store the profiles on an SD card so that updating the firmware won’t affect profiles?
Would also be interesting in binding default profiles to individual inputs until the user changes them manually. Maybe allow this with a config file?
Perhaps the best implementation would be a PC application where user could generate profiles (stored internally e.g. as XML) and export them out to a file (formatted according to target fw version) which can be written to SD card and subsequently loaded in OSSC.
Memory is really tight on the OSSC at the moment, and I am afraid only importing may be viable. I have been working on support for importing settings from the microSD card and even just that takes us within a few hundred bytes (note: not kilobytes!) of using all of the remaining usable memory. I am still trying to get the memory usage lower, but do not expect any miracles.
Writing a PC application to manage settings and write them to the SD card is probably the way to go, especially given that there simply is not enough memory left on the OSSC to maintain any kind of backward compatibility for existing settings when the firmware is upgraded.
I’d really like to see this as well. Has there been any development on importing settings from SD card ?
| 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 |