LittleStudios

It wouldn't surprise me the the serial number associated to the FREE version of the Black 76 has already been flagged. Waves is one company that is fully aware of how a user obtains a plugin license. I imagine IK being another major player in the plugin world also keeps track of how licenses are obtained.

Can someone explain why someone would want to redeem the code during a future group buy? Am I missing something here?

What I was pointing out is that if you have a stereo track and insert a Waves mono plugin and a Waves stereo plugin, for example, the resulting signal will be mono regardless of the order of the plugins in the FX bin or whether the mono plugin is enabled or not, even with the track interleave set to stereo. The result is the same with a Waves mono/stereo plugin and a Waves stereo plugin. This behavior is not intuitive. I ran tests in Reaper, and the way it handles mono and stereo plugins is far more intuitive. A mono plugin will output mono and a stereo will output stereo. So if you go from a mono plugin into a stereo plugin, the resulting output will be stereo. If you go from a stereo plugin into a mono plugin, the result will be mono, as expected. Now granted, under the hood it's really stereo (two buffers, left and right) and if the signal is mono it just populates both channels of the buffer with the same information. Conversely if the signal is stereo it populates the corresponding buffer with the left and right channel information. I just found it interesting and was hoping to get one of the developers to chime in, not really a big deal at the end of the day. I just use the stereo versions of the Waves plugins and ignore the other versions.

I just did some messing around in Reaper and the plugin behavior is as expected. I first inserted the Waves H-Delay (stereo) on the track and set it to a ping-pong delay and it ping-ponged as expected. The next test was inserting just the Waves H-Delay (mono/stereo) on the track and set it to ping-pong and got a ping-pong delay, too as expected, back and forth in stereo. I did another test with first inserting the Waves H-Delay (mono) followed by Waves H-Delay (stereo) set to a ping-pong delay. In Cakewalk this would produce a mono signal without the left to right ping-pong effect. I was expecting the same result in Reaper, but this was not the case. Instead I got the result that you would want, the mono version sent its result to the stereo ping-pong and output the ping-pong effect. The order in which the plugins are placed in the insert list is important and intuitive. If the stereo effect comes after the mono effect, the result is stereo. If the mono effect comes after the stereo effect, the result is mono. This makes complete sense. Cakewalks approach is not intuitive at all. If my track is a stereo track and the last effect on the track is a stereo effect, the result should be stereo, regardless if there is a mono effect prior to the stereo track. For example, a guitar track with a distortion effect (mono) followed up by a ping-pong delay plugin (stereo) would result in a mono, non-ping-pong delay. What is Reaper doing differently than Cakewalk under the hood to produce the intuitive behavior? Is Cakewalk's handling of mono/stereo plugins by design or is it legacy code that hasn't been updated? I'm not planning on switching to Reaper, no way. I just happen to prefer the way it handles mono/stereo plugins. Would be nice if Cakewalk could change its ways. What is the benefit of Cakewalk's approach to mono/stereo plugins, because I can't think of one?

This weirdness is only coming from a Cakewalk perspective, not sure how this works in other DAWs. I have a mono track, acoustic guitar. I send it out to an aux track. The aux track is stereo. To no surprise, if I place the mono version of a Waves plugin (H-Delay) on the aux track, the result is mono, yay. If I instead place the stereo version of the same plugin, in this case H-Delay and set it to "ping-pong", I get the nice left and right back and forth action in stereo, once again yay. Here's where things get weird. If I place the mono/stereo version of the same plugin on the track, H-Delay, and set it to ping-pong, the result is not stereo, it's mono. If that's not weird enough, as an experiment I first added the stereo version of H-Delay to the aux track, set it to ping-pong, it worked great. I then also inserted the mono version of H-Delay to the aux track, but I disabled it. So now I have both the mono and stereo versions of H-Delay on my aux track, but the mono version is disabled. I was expecting to get a stereo ping-pong delay effect, NOPE. It resulted in a mono signal, even though the mono version was disabled. So simply having a "Mono" plugin on the track, disabled or not, forces the track to be mono. Yes, the track interleave is set to stereo in all cases on the aux track. To simplify: mono track -> stereo aux track + stereo Waves plugin = stereo signal mono track -> stereo aux track + mono Waves plugin = mono signal or dual mono mono track -> stereo aux track + mono/stereo Waves plugin = mono signal or dual mono mono track -> stereo aux track + stereo Waves plugin + mono Waves plugin (disabled) = mono signal or dual mono mono track -> stereo aux track + stereo Waves plugin + mono/stereo Waves plugin (disabled) = mono signal or dual mono mono track -> stereo aux track + stereo Waves plugin (dry signal only or at least no ping-pong) = mono signal or dual mono I'm left to the conclusion that it's probably best to use Waves stereo version of their plugins, this way if the effect is a stereo effect, then the result will be stereo and likewise if the effect is mono the result will be mono or dual mono and closer to the user's expectations. My next question is, if this behavior is true for Waves plugins, is this true for other developers? This could be very annoying. Imagine you have a series of plugins that you want to use. If any of those plugins forces a mono result regardless of the plugins on the track being stereo or not, you would have to create a series of effects tracks (aux tracks) for each plugin as a work around to create a chain of plugins in sequence to get a result that is stereo. In my opinion, Cakewalk should use the interleave (mono or stereo) setting of the track to determine if the resulting output is mono or stereo, not let the plugins determine that outcome. This way if a plugin on a track happens to be coded as a mono plugin, the way Waves mono plugins seem to be, it won't override a following plugin that may be stereo. Noel or someone from Cakewalk, can you provide some clarification to this behavior?

I was hoping their announcement was going to be RX 8.

Understood, my current situation dealt with a project that was setup by another party and I was taking over. They didn't use take lanes. I wanted to use take lanes and thought there has to be a more efficient way to move items into take lanes once the Cakewalk project had already been set up.

I've really received a project started by another party. They have a bunch of takes, all on separate tracks. It would be nice to have a feature that would help with getting these tracks on another track as take lanes. Here's a list of some behavior that would be very handy: Add selected tracks as take lanes Add selected clips as take lanes, maybe an option to maintain time stamp position or to place at now marker on new take lane Add take lanes to existing track or create a new track I imagine this type of tool would most likely function through a dialog box. Just a thought.

I ended up just dragging them one at a time into take lanes. Soooooo much easier to edit that way. Would be nice if there were a way to take existing tracks and have a command like, "Create new track and add selection as take lanes".

I've inherited a project with multiple takes that were originally done without using take lanes. In order to simplify the task of comping, I'd like to pull the separate takes together into take lanes.

Is there an easy way or am I going to have to drag and drop? Not a huge deal.

Also I think some of the confusion stems from the fact that there are currently two standards being used to map 0dBu on DBFS, EBU R68 and SMPTE RP155. I've attached an image that better describes this.

I believe I found the answer at the IK forum: https://cgi.ikmultimedia.com/ikforum/viewtopic.php?f=13&t=14486

Not sure if Peter can answer or find the answer to this. So I'm fully on board with IK and T-Racks, love it. One issue that I've found is the VU meters in T-Racks Metering plugin, they are off by -4dB. I've generated a 1k sine wave at -18dBFS. I calibrate the VU meter in T-Racks Metering plugin to be -18dBFS and the read out should be 0dB on the VU. Instead I get -4dB on the VU. I verified this with the TB ProAudio MVM2 and PSP TripleMeter, both show the correct readout of 0dB VU. I also tested this in the plugin version and stand alone T-Racks application. Thanks.

Took the plunge and I'm happy.

I've been demoing the plugins and I think they are all great. The only thing that bugs me, just a little, the VU meters, especially on the Black 76 seem to move a little slow. Just to make sure I wasn't crazy I compared the movement to other VU meters, making sure to use meters based on 300ms average and it still seems a bit slow. It's more noticeable in GR mode than the output settings.

Peter, Does this qualify https://www.ikmultimedia.com/products/tr5/?pkey=tr5 for Pick & Mix Group Buy?

In my case, that's not too bad. If I had multiple systems, 10 authorizations could be an issue, so I see how that could be frustrating for some people.

Question regarding authorizations. From a post in the Coffee House: https://discuss.cakewalk.com/index.php?/topic/6676-lovehate-relationship-with-ik/ How many authorizations do you get? Are there no measures in place to handle system rebuilds?

If you buy the plugins separately without buying T-RackS 5, are they resizeable?

I downloaded the freebie from Acustica, BASSTard. I started noticing a strange behavior with the VST3 version of the plugin in Cakewalk by BandLab. I insert the plugin on a track, apply the settings that I want. Hit the play button (or space bar) and it sounds great, awesome. Time to stop the track, so I hit the stop button (or space bar, doesn't matter) and the "Boost" knob resets back to the default position. In the process of trouble shooting, I installed the VST2 version and the problem doesn't exist with this version. I then uninstall the VST3 version and reinstall it. No good, same result as before. So I see if the problem happens in a different DAW. I try Reaper, and both the VST3 & 2 versions work great. So I go to Sonar Platinum by Cakewalk and I get the same problem as I do in Cakewalk by BandLab. I'm curious as to what it is about Cakewalk/Sonar that causes the Play/Stop functions to communicate to the VST3 version of the plugin to reset the "Boost" knob back to the default position. I've been communicating with Acustica about this issue and all I've received for a solution is to uninstall and reinstall. Which I have and nothing changes. I'm not sure how much of an effort they're going to put into a free plugin. Any thoughts? Noel, any thoughts?

To have the ability to have a user defined project length. This way when exporting, the user defined project length could be used as an option for exporting project audio. I find having to select the tracks that I want included in my project audio export an unnecessary evil. If I don't want certain tracks included in my exported audio I would simply mute, archive or delete the tracks. This one may most likely be only me, but it appears that the export volume is linked to the "Hardware Volume" fader. I'm curious as to why anyone would want the exported audio linked to this fader. Shouldn't the volume of the mix be controlled by the Master Bus? Especially during the mastering process where a lot of analysis plugins are inserted on the Master Bus to determine the overall volume output. It defeats the purpose if the Hardware Volume fader has been altered. I sometimes use the Hardware Volume fader as a quick way to lower the listening volume during mastering, instead of messing with my I/O knobs. Yes I have forgotten to return the Hardware Volume fader to zero and had to re-export. I understand that many may like the current workflow and it could very well stay as is. I'm suggesting adding to the current workflow, maybe in the form of radio buttons to toggle the options to export all tracks in the project and in the user defined project length. These settings could then be saved as an export preset.

Thanks. I have yet to pull the trigger on any device.

Cool.

Only in Cakewalk have I run into this issue. Once you insert LSGate on a track go to the plugin properties as shown in the picture below: Once the plugin properties dialog box opens, make sure the following check boxes are checked: Once the prior steps have taken place, remove the plugin from the track and re-insert it. This only needs to be done once and only once. The plugin will function as expected from now on.