LittleStudios

Is Waves starting to migrate from $29.99 to $24.95?? $24.95 the new meta!!

Just learned that the hard way. I foolishly downloaded the installer and let'er rip. I go through the install and iLock is like "Hell no." Back to V6 for me.

I ended up replying back that I was just curious if it was ok to have two accounts and I got this reply: So it looks like multiple accounts are allowed, but not recommended. I would say if you are thinking about having two accounts, double check for yourself that it's allowed.

I emailed PA about having multiple accounts and got this as the reply: I removed the support team members name from the quote

Having multiple accounts may not be a problem with PA. This is copied from their FAQ page:

Making new accounts may be a loophole, but it seems shady. I'd be afraid they'd catch on and ban the people taking advantage of the loophole.

Norton did NOT like these files. Most likely because they are new.

Not sure I like the reverb swap. It sounds really unnatural. If you're using it as a creative effect, sure. To place a sound in a space, I'm not so sure.

How does acquiring the freebie work? I have an account at ADSR. When I make a purchase, does it show up in the cart, or does it show up in my account? Not sure if I'm asking this right. NEVERMIND.... I need to read the post completely... my bad

What is the competition? The link just says competition... food eating competition?

I run VUMT after it to gain match.... annoying, ah well. I understand the idea of doing hardware emulations, but automatic gain control would be nice. PA should add that feature into there added functionality section of their plugins. I'm referring to the section of their plugins that has TMT, headroom, monomaker, etc. Why not put it there?

I have a Ryzen 9 5900x... It's pretty sweet! Not sure what they're going for now, but I was able to get mine below MSRP from B&H Photo.

This looks super interesting.

@Noel Borthwick I've switched to the default scheduling model, no crashing. @bitflipper I agree with you. I've only had my MOTU interface for maybe 5 months. Typically I use larger buffer sizes, but I've just left the default buffer sizes. Most of my mixing projects have been smaller, except for this latest project I'm working on, which is substantially larger. I have a decent machine, which can usually handle anything I throw at it. I guess there's always an exception. I've gone into my settings and bumped up the buffers, giving the CPU a chance to breathe. Thanks guys!

Thanks, Noel! Another question, as a test, last night I increased my buffer size to see if that would help. Could this issue also be caused by using a buffer size that was too small for my system and my current project?

Ever since the latest update to version: 2022.02 (Build 039, 64 bit) I've been experiencing Audio Engine Dropouts. I get the error Audio Engine Dropout (19). Code (19) is not found in the online documentation. Any help would be appreciated.

Larry, same here I'm not getting a pop up. I already have it, I'm just greedy. Because I already have it is probably why it's not popping.

I find the stereo behavior of tracks in Cakewalk to be odd or even misbehaving. When you insert a mono plugin on a stereo track it converts the track to behaving as if it's mono regardless of its track setting. I've thrown together a short video demonstrating this as well as how the same situation behaves in Reaper. Check it out: https://youtu.be/89XEGXEvjKs

kvraudio.com

I don't like it, but do you think they are coming from the "gift card" type approach. Where for the holidays you could buy someone Gear Credits to use. If this is the direction they are going, I get it. When you buy a gift card you pay the face value. Like I said I don't like it, dumb idea, just playing devil's advocate.

All Waves deals ultimately end up at the same place... $29.

Could the Tascam Tape Collection be purchased in order to qualify for the group buy?

I just had an interesting thought. Using the AUD.ini you can set specific sample rates to oversample at for each plugin. Knowing that not every plugin has the same maximum operating sample rate, can we define a maximum sample rate for each plugin in the AUD.ini. For example, let's say I set my project sample rate to 192 KHz. Well, the Waves J37 tape plugin tops out at 96 KHz. If I set the plugin upsample rate in the AUD.ini file for the Waves J37 to 96 KHz and enable plugin upsampling, will it, for lack of better words, downsample the Waves J37? Basically project running at 192 KHz and the Waves J37 running at 96 KHz. Would this work? Is this even necessary? Does Cakewalk recognize the maximum sample rate of a plugin and not exceed it? Companies like Waves are inconsistent with the maximum sample rates their plugins run at: Codex Wavetable Synth 96 kHz dbx® 160 Compressor / Limiter 192 kHz DeBreath 96 kHz DeEsser 192 kHz Doppler 96 kHz Dorrough Stereo 192 kHz Dorrough Surround 192 kHz Doubler 192 kHz DTS Neural™ Mono2Stereo 48 kHz DTS Neural™ Surround DownMix 48 kHz DTS Neural™ Surround UpMix 48 kHz Dugan Automixer 96 kHz Dugan Speech 96 kHz Eddie Kramer Bass Channel 96 kHz Eddie Kramer Drum Channel 96 kHz Eddie Kramer Effects Channel 96 kHz Eddie Kramer Guitar Channel 96 kHz Eddie Kramer Vocal Channel 96 kHz Electric 200 Piano 96 kHz Electric 88 Piano 96 kHz Electric Grand 80 Piano 96 kHz Element 2.0 Virtual Analog Synth 96 kHz EMI TG12345 Channel Strip 192 kHz eMo D5 Dynamics 96 kHz eMo F2 Filter 192 kHz eMo Generator 96 kHz eMo Q4 Equalizer 192 kHz Enigma 192 kHz F6 Floating-Band Dynamic EQ 192 kHz Flow Motion FM Synth 48 kHz

This is what I did. I don't want to quote my prior post, but there I describe that I did use independent but identical tracks, one track had an upsampled plugin, basically doing nothing except giving the signal something to pass through. Bounced the result of the oversampled track to a new track and counted samples (really fun btw). The oversampled track was arriving at the speakers 140 samples late.

I think the Cakewalk documentation may need a refresh. Could also be that the authors of the documentation were making the assumption that the user would only enable plugin upsampling on a handful of plugins. Which I think makes sense. You would think that if they intended on the user enabling upsampling on a bunch of plugins they would have come up with a more useful user interface for such a task.