-
Notifications
You must be signed in to change notification settings - Fork 33
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
[Feature req.]Write tonie name and track names into filenames #29
Comments
I've been thinking about this... is this the right place for discussions? If this gets implemented (perhaps controlled by an option switch), please keep track order by prefixing the new information by (at least) the track number (with two digits, see #51). Checking the available information inside the ogg stream after decoding, I found that there are ARTIST and ALBUM entries in the (so called by I was missing track name or sequence number. Neither Teddy nor TeddyBench appear to provide them yet (there are only a few tags.Add() statements). |
Since a second "mention" does not show up here: In #30 there are scraper scripts which return track lists. Let's have ARTIST, ALBUM and TRACK fields in the "User comments", and in a next step use them for friendlier filenames! |
Using a two-step approach this is already possible: Due to #51, I'd recommend to run An all-in-one solution is clearly preferred, thus I'm holding back my (immature but working...) script now. |
Currently, the .ogg files of backed-up tracks are named consecutively, e.g.,
ID-ID - Track #1.ogg
.Even if tonie name and track names are present in the JSON one can provide to teddy, the info is only included into the file metadata.
It would make handling the backup files much easier if these infos could be directly included into the filenames!
As a workaround, I am currently looking into extracting the .ogg metadata to automatically rename the .ogg files.
If I get to a result I'll post it here.
If anyone already has an automatic solution I'll gladly save time and use it :-)
Thanks!
The text was updated successfully, but these errors were encountered: