Taperssection.com
Gear / Technical Help => Post-Processing, Computer / Streaming / Internet Devices & Related Activity => Topic started by: panther65 on November 07, 2006, 04:55:50 PM
-
I'm a llittle confused about flac metadata in frontend. I understand to put all of the pertinent info regarding venue, city, recording gear in the fields, but wiki.etree.org suggusts renaming the file with just the track number and title. I'm assuming this is so you can see the song and track on a computer-based player. Is this necessary and possible. I tried it, but would the resulting file be acceptable to upload to archive/etree?
-
common practice is to skip the metadata and include the venue, source info, song names, etc. in a text file that accompanies the flac fileset. There is a great foobar component that actually scans the text file and then automatically populates the metadata fields. Further, the metadata can be added to flac files by other tagging programs, it's not necessary to use the flac frontend to add the metadata.
-
Thank you.
-
Some of us don't know crap about meta-data or tagging or whatever. I rely on the file name and text file for that info.
Terry
-
Some of us don't know crap about meta-data or tagging or whatever. I rely on the file name and text file for that info.
Terry
right but it's nice to tag in foobar or another program so that when I'm listening to a show on the computer in foobar I can see
the band name, song title, venue etc instead of just jgb1981-03-20 (for example)
-
Some of us don't know crap about meta-data or tagging or whatever. I rely on the file name and text file for that info.
Terry
right but it's nice to tag in foobar or another program so that when I'm listening to a show on the computer in foobar I can see
the band name, song title, venue etc instead of just jgb1981-03-20 (for example)
Agreed, metadata also is key when using ipods, etc. Def. nice to have and easy to add using foobar. Back to the original issue, no HARM adding metadata and doing so won't cause etree/archive compliance issues, but not required . . .