Moderator: Martin Hairer
A few of the problems I'm running into include:
Getting an alert that I can't add the plugin because another instantiation of the same plugin is already in, even though this is not the case; After attempting a batch bounce I often get the alert "The effect XYZ could not be applied because it is already in use" which is not the case. I was disappointed that I could not use a plugin more than once, as I can on other hosts, but in these cases it's telling me that a plugin can't be used because I have used up the single usage when I have only put it in once in a batch, or sometimes not at all.
Several AU plugins that behave fine in other apps behave erratically, especially in the way of retaining settings and visual feedback of their metering;
Every time I tweak a setting in a plugin and wish to save this new setting it insists on creating a new setting, instead of simply saving the parameter change to the setting I am on, which is how the plugin behaves in other hosts;
When attempting to create a new AU rack continually getting the alert "Could Not Create new User File", with the options buttons of "yes" "no" and "cancel". Clicking yes or no repeats the alert several times until I get a rack which contains old plugins from a previous session, which I then have to delete and start over;
When I go to create a batch the plugins are often not listed in the menu. Several quits usually brings this back;
One of the biggest issues that I did not foresee when purchasing is that there is no way to adequately preview what the result of the stack of plugin settings will do. I have to create an AU rack, get the results, save settings, and then re-create this list of plugins in a batch document and re-add the settings. Then I have to just have faith that it is doing what I hope it is, because there is not visual indication of the audio or the plugins' metering. Unfortunately, when I reload the batch document Amadeus is not confidently recreating the settings so this is not working out.
Any thoughts on any of these issues would be very helpful.
Blane & DeRosa Prods
Is this correct or am I missing something? How can one add a string of processing to a batch and preview the results with each process, including change of a plugin's parameters, and hear the results without bouncing, reimporting, etc?
To add to this, I just did a batch test and the resulting file began being processed 3 seconds into the audio.
B & D
Regarding the visual feedback when batch processing, I do not quite understand what kind of behaviour you're after. The whole point of the batch processor is to let the computer do its thing without human intervention. It seems to me that allowing for manual intervention at each step would basically defeat the point? Regards,
An error occured while processing ‘1sp19.mov’: The file is not a movie file.
An error occured while processing ‘1sp16.mov’: A necessary data reference could not be resolved.
There doesn't some to be any consistency in the errors, as I'm converting mp3 to Quicktime files (AAC audio), so I don't understand why I receive different errors for similar file types. In the same batch, some files manage to encode without issue.
I don't think it is an issue with the file or the batch settings as the same files will convert perfectly when I drag them individually onto the processor. While this is a temporary solution, it is most inconvenient.
I'm using the latest version of Amadeus Pro downloaded from the web site on an iMac i7.
Thanks for any help you can provide.
Thanks Martin, I'll try that.Martin Hairer wrote:Hi, regarding the "The effect XYZ could not be applied because it is already in use" alert, this is probably because, by default, the batch processor tries to make use of multiple cores if available. If your plug-in does not support being instantiated multiple times (most do), this might cause such a message. You can set the number of cores used for batch processing to 1 in the preferences.
Martin Hairer wrote: Regarding the visual feedback when batch processing, I do not quite understand what kind of behaviour you're after. The whole point of the batch processor is to let the computer do its thing without human intervention. It seems to me that allowing for manual intervention at each step would basically defeat the point? Regards,
Not looking for manual intervention, just to be able to verify the audible result of what the batch I'm creating will sound like. During creation of the batch it is difficult (unless I'm missing something) to create a batch with several plugins with finely tuned parameters that are reflecting the material. For example, if I've made a batch of 6 plugins, batched a folder of voiceovers and then decided I need to notch out more low end at the first plugin, it would be good to be able to check, either aurally or via their meters, how the dynamic plugins which follow need to be adjusted, so that they are responding the same and my level is the same. If I just substituted the revised eq I'd likely not be hitting the plugins that followed as they should be. But to make them correct seems unwieldy.
Again, if I'm missing a proper way to use the batching please let me know : )