Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should changes to track metadata made through the web interface be saved to files? #621

Open
frecuencialibre opened this issue Nov 28, 2018 · 6 comments

Comments

@frecuencialibre
Copy link
Contributor

commented Nov 28, 2018

this conversation started in #526 (comment) 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?

  1. would make recreating databases easier as noted by @xabispacebiker,
  2. would make LT play nicer with other software, and
  3. we've already discussed and abandoned watched folders in favor of an import folder, so that argument against writing tags to files is now moot.

thoughts?

@Robbt

This comment has been minimized.

Copy link
Member

commented Nov 28, 2018

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.

@hairmare

This comment has been minimized.

Copy link
Member

commented Dec 3, 2018

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.

@Robbt

This comment has been minimized.

Copy link
Member

commented Dec 3, 2018

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

@BobWall23

This comment has been minimized.

Copy link

commented Dec 10, 2018

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.

@JohnnyC1951

This comment has been minimized.

Copy link

commented Dec 10, 2018

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).

@maydo

This comment has been minimized.

Copy link

commented Mar 6, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.