![]() I didn't upgrade to 7 when Bias offered it a while back, then they shut down. I've yet to begin the trial, as I'm hoping to first secure a serial #. The big question: Does Peak Pro 7 work with Yosemite? Or is it broken as well on Yosemite? I have the trial install of Peak Pro 7 but I have no serial #. I'd like to update to Yosemite, but I hear Peak 6 won't work well with it, as posts in this thread will testify. It runs great on my studio MacPro, but I'm stuck in OS 10.8.5. The last version I purchased is Peak Pro 6, years ago. ![]() I'm a Bias Peak user from the early days. OK guys I've been a member for a couple years, but this is my first post. Why the **** did I upgrade to this POS again? I keep forgetting. 0 seems to be messing with my Apollo/UAD setup, whereas it has yet to successfully handoff a cell phone call to my Mac. It will suck to finally lose it.Īlso, Yosemite Sam. But the whole point of peak is instant swiss army editor. Those emails I get for SoundNope make me want to lobby a surface to air missile in their direction.Īnd yes, I do have a G4 in OS stasis for the occasional reprint of dead instruments/plug-ins, one drive boots 9 and the other boots 10.5. I can't believe no one can make that happen. Truth be told, I would pay $100 "upgrade" to just have it continue working in Yosemite. In a word, "****ing unprofessional." Oh, that's two words? So is "****ing assholes." I have to say the way BIAS folded still sticks in my craw. I have a bad feeling this is going to screw up the batch features, one of the main reasons Peak is (was?) still incredibly useful. Actually, I've just been quitting the app after I'm done editing each file. Same deal here with the move to 10.0: Unable to close the file. Heh, I just popped over to start this thread, but it appears ptfigg has beat me to it. The resulting statistics are pretty robust. So in most cases I would need to remeasure anyway using a supported off-line solution.Īudition has something called Amplitude Statistics. In fact the readout is Sample Peak and not True Peak. ![]() OTOH I found that is was only useful when I first opened a file, or after mastering/processing for Program Loudness and/or True Peak compliance. why do you need a constant readout of current max peak? Are you working in an environemnt where your headroom is always minimal? But let me ask you this - and no snark intended. and then had no idea if the plug in caused the file to hit 0.0 or not. i tried using WaveLab today, rendered a plug in. (if they do, please tell me which ones!)Ī simple, automatically updating, readout of the current max peak of your file. that i can't believe other programs don't do.
0 Comments
Leave a Reply. |