| Our forums are intended as a gathering place for our users to discuss our software with each other. Please note that we do not provide technical support via our forums. For support and feature requests, please contact us via email or the integrated Help Desk available in all of our applications. You can also follow us on Twitter, join us on Facebook and/or subscribe to our newsletter. Thank you! |
Exporting MP3s File Prefix
Posted by:
Evergroove
()
Date: November 15, 2011 12:05PM
Why must I have a File Prefix when exporting as an MP3? There seems to be no way around this.
Re: Exporting MP3s File Prefix
Posted by:
JackHenry
()
Date: November 16, 2011 01:32AM
Do you mean a file name? You need to call it something. You can't save (or export) anything without a name.
Re: Exporting MP3s File Prefix
Posted by:
Evergroove
()
Date: November 16, 2011 01:40AM
No... it asks for a "Fie Prefix". Why must I supply that when I've designated, and named, track markers?
Re: Exporting MP3s File Prefix
Posted by:
JackHenry
()
Date: November 16, 2011 05:59AM
File Prefix is exactly the same as File Name. If you look at the online manual, (second from the bottom) you'll see that it was originally called 'File Name'
[www.audiofile-engineering.com]
[www.audiofile-engineering.com]
Re: Exporting MP3s File Prefix
Posted by:
Evergroove
()
Date: November 16, 2011 10:20AM
I've looked at the manual. It's far from comprehensive and could use much, much, more detail all around. But we can talk about that in a different thread :-)
If I have a project with 10 tracks in it and I have set Track Labels and named them and then want to export the tracks then one would expect the file name to be what I specified in the Track Label name. Instead, I am required to supply an additional "File Prefix".
So, if my Track Label for a song in my project is titled "My Song" and I want to export the track, let's say as a WAV, whatever I put into the "File Prefix" box gets appended to the front of the track name. But you guys know this.
I see this as a problem because if I just want the file on the hard drive to be named "My Song.wav" I have *no way* of doing that, again, because I am required to specify a prefix. So, that means if I put in "My Song" for File Prefix then I really end up with a filename of "My Song My Song.wav" and then I have to go and manually edit the file name to simply be "My Song.wav".
I understand *why* WE has been programmed to do this. It's to save the users from themselves. However with proper file management on the user's end the potential for overwriting of files is lessend and really shouldn't be a problem. At the moment, WE is the only software I know of that works this way. Most software prompts you if you are about to overwrite an existing file and that's usually good enough.
Speaking of... I notice WE doesn't notify of you of potentially overwriting files either. If you try to overwrite an existing file you don't get any msg. whatsoever. Instead, it puts an underscore and number at the end. For example, My Song_000.wav That alone could cause some great confusion for users who are *expecting* the song title to be exactly what they entered but instead now have to stop and figure out which version of the song they should actually use or send to the client.
Thanks for your help and understanding on this. Like I've said, I think WE is software with a *ton* of potential. I'd just like to see some of these things addressed in the next release so that the workflow of using WE is faster and more efficient.
Of course, as a new user, I am completely willing to accept that maybe there is a better workflow and would welcome recommendations.
If I have a project with 10 tracks in it and I have set Track Labels and named them and then want to export the tracks then one would expect the file name to be what I specified in the Track Label name. Instead, I am required to supply an additional "File Prefix".
So, if my Track Label for a song in my project is titled "My Song" and I want to export the track, let's say as a WAV, whatever I put into the "File Prefix" box gets appended to the front of the track name. But you guys know this.
I see this as a problem because if I just want the file on the hard drive to be named "My Song.wav" I have *no way* of doing that, again, because I am required to specify a prefix. So, that means if I put in "My Song" for File Prefix then I really end up with a filename of "My Song My Song.wav" and then I have to go and manually edit the file name to simply be "My Song.wav".
I understand *why* WE has been programmed to do this. It's to save the users from themselves. However with proper file management on the user's end the potential for overwriting of files is lessend and really shouldn't be a problem. At the moment, WE is the only software I know of that works this way. Most software prompts you if you are about to overwrite an existing file and that's usually good enough.
Speaking of... I notice WE doesn't notify of you of potentially overwriting files either. If you try to overwrite an existing file you don't get any msg. whatsoever. Instead, it puts an underscore and number at the end. For example, My Song_000.wav That alone could cause some great confusion for users who are *expecting* the song title to be exactly what they entered but instead now have to stop and figure out which version of the song they should actually use or send to the client.
Thanks for your help and understanding on this. Like I've said, I think WE is software with a *ton* of potential. I'd just like to see some of these things addressed in the next release so that the workflow of using WE is faster and more efficient.
Of course, as a new user, I am completely willing to accept that maybe there is a better workflow and would welcome recommendations.
Sorry, only registered users may post in this forum.