this conversation started in https://github.com/LibreTime/libretime/issues/526#issuecomment-427693597 but merits it's own thread. see that thread for more opinions.
my vote is that yes, changes to metadata should be saved to files. why?
thoughts?
I think it sounds like a good idea. It would also be useful to investigate the potential to use custom ID3 tags store useful metadata.
I think we should keep both possibilities here (and maybe guard this by a setting). Once we get watched folders back up and running it will make sense to be able to use a readonly file system with audio on it while still being able to have a record of things like silan and/or replaygain info.
Well "watched folders" is still at #111 as my import script didn't provide that functionality. It's kind of a long way off with no plan for how to best execute it without completely rewriting the current import process used by analyzer and deal with the issues caused by using remote files. See discussion on #577
I think this would be nice, but I can't say I have thought about repercussions much.
We sometimes upload files to Libretime, then download them to play out when someone is live DJing. It would be somewhat convenient if any metadata changes made through the UI tracked along with the file.
This could be done in a few lines of code using id3 or eyed3 and a trivial database loop, as a utility. I already do the reverse: loading up all the current & future SHOW titles & descriptions from imported podcast files' title & composer mp3 tags, if changed (It's witchcraft-driven and off-topic for here).
i think also it would be nice writing into files and also the opposite way from files rereadng into DB
also we need the possiblity to edit tags on multiple selected files.
currently there is no way to edit multiple files and reread into db
This issue has been automatically marked as stale because it has not had activity in the last 5 months. It will be closed if no activity occurs in the next month.
Please chat to us on discourse or ask for help on our chat if you have any questions or need further support with getting this issue resolved.
You may also label an issue as pinned if you would like to make sure that it does not get closed by this bot.
Metadata is crucial for us especially in building complex shows with smart blocks and playlists. Being able to take that metadata where ever we go is also important. Whether LibreTime should modify the original files ... I'm not sure what the best answer is. If LibreTime had an export feature that gave you the option to take the metadata with you, then we wouldn't have to modify the metadata.
I second supporting the import of custom metadata fields because that would allow us to build more complex shows. Currently we use the label field (which fails to import in Airtime 2.5.1) to "label" our songs accordingly, then realising label is actually music label but that's metadata we could care less about so we modify it to our hearts content =).
So in my opinion. LibreTime should probably write to the files for shows that it has fully imported and is control over, but if we manage to get a "watched folder" type of scenario it probably would be safer to avoid doing this because I suspect it would be smart to treat this files as read-only to avoid messing up someone elses external filesystem.
Most helpful comment
So in my opinion. LibreTime should probably write to the files for shows that it has fully imported and is control over, but if we manage to get a "watched folder" type of scenario it probably would be safer to avoid doing this because I suspect it would be smart to treat this files as read-only to avoid messing up someone elses external filesystem.