mpdonahue wrote:I think you are missing the big picture WRT the album publishing. You can now make a single MTFF file (and QC a single MTFF file) for all the different deliverables for a given title with correct samplerate conversion/dithering.
Thanks Mark, for your detailed overview of the Publishing, which I have been making use of in ways similar to yours for a few years now. Perhaps I should have qualified my posting to show that I was referring specifically to the new stand-alone Publishing application, as opposed to the process which has been part of Disk-Write for some years now. It would appear that the primary difference between the two methods is that the new program is a lot less "fiddly", offering a more direct and streamlined method to producing output from an existing MTFF.
BTW, has anyone else seen that Published FLAC files do not include a cover image upon completion, whereas AAC, Ogg and MP3 from the same pass will? This occurs whether you use either the new app or Disk-Write. A bug notice has been sent to Merging Support...
The other thing is that there is the ability to add or subtract gain in the sample rate conversion
I was unaware of this, but I suspect this is because I do not have the Final Check key for my system - is that right, does gain adjustment come with Final-Check?
You can also script all the information that you need for creating filenames without having to manually edit.
Yes, and I believe it was you who pointed me in the direction of using the built-in Windows capability to generate folders as part of the Saving process, through the inclusion of "\" slashes in the proposed file-name(s). With this, I've been able to output different sets of files in different formats, sample-rates and wordlengths into their own folders, while I go off and make lunch.
Finally, one of the huge advantages of VST3 over VST2 is DSP usage and speed during mixdown. VST3 will automatically disable processing is there is no input to the plugin, so it only uses DSP then the plug is active. It also allows for the correct routing of multichannel inputs and outputs of the plugin.
I was unaware of this specific benefit of VST3 - thanks for the info. I've noticed that my 11.1.4 system seems to be requiring a lower level of CPU processing, and the usage meter, which in 11.0 always seemed to display an alarming amount of activity, is now much calmer - which I attribute to both more efficient coding of plugins and program alike, along with the improvements to the CPU load meter itself as detailed in the Release Notes.
Rick - as for finding a Scully and desk - I hear ya, and I'm reminded of a friend who has a pair of 24 track decks and a 48 ch. mixer in his basement, which he picked up from various studios' close-out sales. I sold him my old Lexicon NuVerb system (computer and converters in addition to the two cards), so he's state-of-the-art 1988, in the comfort of his home. It's like walking into a time-warp...