edited 12:51 AM EST February 12, 2009
edited 3:27 AM EST February 16, 2009
Thanks snakemeat for adding the 1 loop functionality! I did the timing manually before I knew about 2sf timer, but now I'll be able to use it for all future conversions. I'll still have to add a fade delay to the lengths to do the S-curve style fadeouts (setting the fade used by vio2sf to 0 and using Sox for the fade instead), but I can get around that if you don't feel like adding a Fade Delay feature to 2sf timer. I'm looking forward to the day when somebody makes a timing tool for other non-stream Nintendo platforms!
edited 3:29 AM EST February 16, 2009
http://www.sendspace.com/file/2zkda5
Especially loving the batch file you included. Will be up when the next update rolls.
//Edit
Though you could have added the actual tagging commands to the batch as well. :)
edited 11:17 AM EST February 16, 2009
I'll still have to add a fade delay to the lengths to do the S-curve style fadeouts (setting the fade used by vio2sf to 0 and using Sox for the fade instead), but I can get around that if you don't feel like adding a Fade Delay feature to 2sf timer.
I'm not exactly sure what you are requesting here or if I could add it. Any more info you could provide me would increase the chances of seeing it added.
So that he can wavewrite the files and add better fadeouts manually.
Knurek, I agreed at first that I could have had the tags in the script, then I thought about it. What if somebody edits some of the tags to something they like better, and just want to adjust the timing every once in awhile? I can't think a good reason why somebody would need to transfer the tags to another version of the same rip. If they liked the tags, they could just use the included 2sfs. Otherwise they could use their own 2sfs and just use the timing functionality of the script.
I'll keep your suggestion in mind anyway for future albums (but out of curiosity, could you please explain why you want it?). I've been planning on having tags in CSV format, that way they can be used by a wide variety of programs for importing. Future versions of that script would offer an option to import from the file.
Though I'm torn between 1 of 2 options for the CSV:
1. Omit commas from titles (though keep including them in the actual tags) and use "Artist1 / Artist2 / etc." instead of the comma as the separator for multiple artists. This would be standard CSV. Of course there's the option of escape syntax, but that would break quite a few pre-existing programs and would make parsing more complicated for programmers. Even apps with regex such as mp3Tag don't support escape functionality when importing from text files.
2. Use the less standard CSV format with semi-colon as the delimiter. This goes against the name of the format, but would be compatible with programs such as Mp3tag. Though it wouldn't be imported correctly into a spreadsheet when a casual user with Office installed opens it.
Any opinions?
I was thinking more of an update process. If you have the pack that's on manly, just download a batch file, run it and you have a fully tagged set without the need for redownloading the 2sflib once again. I know that it's 2009 and most people won't care about 10 MB download, but there's still some poor guys on dialup, and every MB counts there. :)
And as for CSV, I'm not sure how widely it's supported but "variable","variable, that has comman","other variable" seems to work fine with OpenOffice at least.