Thanks so much for these excellent instructions. My goal was to normalize a number of files.
I do like your ring tone example though and may just have to try that. Jenine Stanley dragonwalke...@gmail.com On Jul 29, 2014, at 5:16 AM, Paul Erkens <paul.erk...@gmail.com> wrote: > Hi Jenine, > > I've had difficulties myself as well, and I found out how to get things going. > To batch process files in amadeus pro, do the following. > > First, fire up amadeus and to begin with, hit command shift n to open the > batch processor. The layout of the window is actually simple, once you > understand the basics. There are 4 tabs: format, actions, meta data and > artwork. For now, forget about the last 2. If you just want to batch convert, > then only the format tab is important. By default, after you open the batch > processor, you will already be inside the format tab, so skip all tab stuff > for now. > > Next, you will want to select the files to work on. However, even though this > is the logical way of doing it, you first need to set a number of options. > This is because once you have selected your source files, amadeus will > immediately begin cranking away, without you having the chance to set > conversion options first. So, first set options, and then hit select files. > Let's go through the options. > > Resulting format is the first option you need to set. Just select your > desired destination format from this popup menu, like mp3, m4a etc. To be > clear: this is what you want your source files to become, once amadeus > converted them. > Once the destination file format is chosen, use the button next to the format > chooser, to specify your settings. For example, say you want your source > files, in whatever format they are now, to be converted into mp3 files, with > a bitrate of 256. Then first select mp3 from the resulting format menu, and > then hit the settings button next to it, so you can select 256 kilobits for > your resulting mp3 files. There's a whole lot more to know, but this will get > you started. After you choose your desired bitrate, or other destination file > options from the settings dialog, be sure to hit okay there, and you will > return to the amadeus batch processor. > > The next option in the batch processor is called destination location. In > short, this is straight forward. The popup has a few preset folders for you > to choose from, but of course you can also point to a folder of your own > choice. Again: this is the folder where you want your converted files to go. > > Next option is delete original. This is a checkbox. If you are totally sure > that your batch processor conversion options are correct, which take some > experience, only then would I advise you to turn this thing on. If you find > that you are satisfied with your converted files, you can always delete your > source files manually, so that you are in control. > > Next is: change name to. I never use this, and now that I'm looking at it > again, I wouldn't bother. Same goes for filter files, which is the next > option, and I'd also not worry about entering regular expressions. > > Next is: open subfolders recursively. This affects your selection of source > files. With this checkbox off, only files, single files from 1 folder that > you select, will be converted. With this checkbox on, all subfolders of the > source will be traversed and converted. To clarify: let's say you have a > folder called big store, full of audio. It doesn't matter where this > imaginary folder is on your mac. Just imagine that big store, contains audio > files, and also imagine that big store has subfolders, also containing audio. > So we were looking at this checkbox labeled: open subfolders recursively. > Now. If you have this checkbox off, then amadeus will look in this big store > source folder, and if it finds any audio files at its top level, only those > will be converted. If you turn this checkbox on, then amadeus will also go > through each and every subfolder inside big store, and all audio it > encounters there, will also be converted. Keep in mind that it is up to you, > to determine what happens to the original audio. If you have set a > destination folder for conversion, different from the source folder, then the > original audio will still be safe and unaffected, and it won't be > overwritten by the converted files. > > Next option: retain folder hierarchy. The folder hierarchy is simply the > layout of a particular folder, with all subfolders beneath it. Of course, > only if you chose to recursively go through lots of audio folders, there's > the question how to store all those files on your destination. You could > either choose to throw all resulting files into one single folder, it being a > collection of all the files gathered from all source folders recursed, or, > you can choose to have amadeus recreate the entire folder hierarchy at your > destination. If you do that, then you will see the entire folder tree on your > destination as well, just like you have it on your source location, and then > each converted file will be in a location you recognize. Again, only turn > this box on, if you are recursing your source folder tree. > > Finally, there's the option: drag files on this area to process them. This > used to be slightly cumbersome, but it is not anymore. We used to have to > click this area on the screen using the voiceover mouse simulation, but now, > the amadeus author has given us a simple button to click, that voiceover > recognizes, which opens the source file browser. This button is unlabeled > though, so voiceover will just call it: button. Now that you have set all > your options for conversion, you begin conversion itself by selecting the > source files or folder, and then if you hit open, to return to amadeus pro, > conversion will be on its way. > > Now without all extra info, here's how to quickly convert audio to mp3 256, > just as an example. > 1. Open amadeus, and start the batch processor, command shift n. > 2. In the format tab, select the destination file format, in this case mp3, > and set the mp3 details using the settings button. There, you choose 256 as > the mp3 bitrate to convert into. > 3. Choose your destination folder, where all your converted files will go. > 4. Go through the other options as described, for recursion etc. Usually, you > can leave all of those at their defaults, as long as you are not going to > recursively convert. > 5. Finally, hit the unlabeled button. This will open the source file > selection dialog. Select what you want converted, and once hit open from this > dialog, you will return to amadeus and conversion will be going on. > 6. Once conversion is complete, which has a nice progress window, you will > get a message box telling you how things went, that you can close with an > okay button. > 7. Finally, if you now close amadeus pro using command q, amadeus will ask > you to save or discard, well, something. Here, amadeus is asking you if you > want to keep the batch conversion settings as you just set them, for future > use or not. It is perfecly safe to not save here, because it will not affect > your converted files, and it is easy to recreate the settings once you know > what they do. It's a matter of less than a minute for all of them. > > As a side note, a remark on the actions tab. Amadeus pro is not just a simple > converter. You can do all sorts of cool things to your files. Say you have > 200 songs in your source folder, and you want all of them to become ring > tones. To do that in an automated way, here's what you could do. Often, the > first 30 seconds of a song is intro. A soft beginning, which won't be useful > as a ring tone, because that only lasts 30 seconds at best. So, you might > want to begin each ring tone, 30 seconds or so into the song. To do this, you > can tell amadeus to cut off the first 30 seconds of your song, as the first > step to make it into a ring tone. Next, you want 30 seconds of the song for > your ring tone, but no more. So, in the actions tab of the batch file > converter, tell amadeus to then cut off everything after the first 30 > seconds. To summarize up to this point, you now have an audio snippet from > your song, starting 30 seconds into the song, and lasting 30 seconds from > there. Then, you could choose to nicely fade in the beginning of the snippet, > because that will sound smoother as the start of your ring tone. A fade in of > a few tenths of a second is enough to make your ring tone sound nicely at its > start. Likewise, fade it out at the end if you want. Once you have your ring > tone snippet, it might be that its volume is not as loud as it could be, > without clipping. So, you could then have amadeus pro normalize the segment > for you, so that its volume is maxed out in the resulting file. > > All these things can be added in sequence, one after the other, using the add > button on the actions tab of the batch processor. Each newly added action > will be carried out after the other ones, in the order you added them to the > list box of actions to take. > Finally, choose ring tone, as your amadeus pro destination file format. You > choose this from the same menu where you chose mp3. The choice is called: > iphone ring tone. To be clear, an iphone ring tone is not an mp3. Rather, > it's an m4r. So, do choose iphone ring tone in the above case, not mp3, or > itunes won't be willing to import your 200 segments as new ring tones, and > itunes will instead import them as little 30 second songs, which is not what > you intend. > > Hth, > Paul. > On Jul 20, 2014, at 2:25 AM, Jenine Stanley <dragonwalke...@gmail.com> wrote: > >> Can anyone who has successfully used the batch processor in Amadeus Pro give >> me some step by step directions. I'm obviously not doing something right. >> >> I can't even explain what I think I'm doing wrong because I've tried several >> methods of selecting files and applying effects to them and nothing has >> quite worked. >> >> Thanks. >> Jenine Stanley >> dragonwalke...@gmail.com >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MacVisionaries" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to macvisionaries+unsubscr...@googlegroups.com. >> To post to this group, send email to macvisionaries@googlegroups.com. >> Visit this group at http://groups.google.com/group/macvisionaries. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to macvisionaries+unsubscr...@googlegroups.com. > To post to this group, send email to macvisionaries@googlegroups.com. > Visit this group at http://groups.google.com/group/macvisionaries. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To unsubscribe from this group and stop receiving emails from it, send an email to macvisionaries+unsubscr...@googlegroups.com. To post to this group, send email to macvisionaries@googlegroups.com. Visit this group at http://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout.
