You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've checked that there is no other issue about this feature request.
This issue contains only one feature request.
The title of this issue accurately describes the feature request.
Feature description
As it is, InnerTune only exports its playlist data, user data, etc as its own .backup files. They can't be read by any program that isn't InnerTune. Having a CSV/JSON version of the database would allow other programs to read the playlist data at the very least.
Why do you want this feature?
Asking for imports/export for every file structure used by other yt clients is probably unreasonable. But it would be nice to export to CSV/JSON. I saw in #838 that as it is InnerTune can only export songs IDs (the urls? the names?) into CSV. Even if no other app accepts this format, it would be a nice way to at least have some sort of "universal" file that could be manually altered until its readable by some other program.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Checklist
Feature description
As it is, InnerTune only exports its playlist data, user data, etc as its own .backup files. They can't be read by any program that isn't InnerTune. Having a CSV/JSON version of the database would allow other programs to read the playlist data at the very least.
Why do you want this feature?
Asking for imports/export for every file structure used by other yt clients is probably unreasonable. But it would be nice to export to CSV/JSON. I saw in #838 that as it is InnerTune can only export songs IDs (the urls? the names?) into CSV. Even if no other app accepts this format, it would be a nice way to at least have some sort of "universal" file that could be manually altered until its readable by some other program.
Additional information
No response
The text was updated successfully, but these errors were encountered: