Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

10 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. On an audio track, while record-enabled, it shows the level of the input signal.
  2. Yeah... This problem is typically caused by screen scaling in Display Options. Set it to 100%. Not 125% or anything higher.
  3. Just curious... in a digital environment, why would you prefer a VU meter over the meter next to the fader for monitoring input gain? During recording, I'd think you'd only be concerned about avoiding clipping. As for gainstaging, with the 32/64bit float audio engine, you pretty much can't clip a bus input, even if you are hitting it at +20 or more (although some plugins might not like this).
  4. I perform live with Cakewalk. A project file will typically host several audio stems and software instruments. In some situations, I want to simply control two different plugins using faders/knobs on one of my MIDI controller keyboards. One project has a sweepable filter on each of two audio tracks. With ACT, there is no way I know of to allow for control of each of these at one time. I know about the option of using "configure as synth," but this plugin (Waves OneKnob Filter) does not take that setting for some reason. I set it for both the VST and VST3 entries for the plugin in CW Plugin Manager and restart... and after all plugins are rescanned, it does not show up as a synth with MIDI connections. Going back into CW Plugin Manager, the "configure as synth" button is found to be unchecked. Even if it worked, this wouldn't be an ideal situation... with it requiring an additional MIDI track and extra effort to configure. It would be nice to have a control surface mode where, instead of allowing a "lock" to a particular instance of a plugin, all sliders/knobs could simply be locked individually to whatever they are set to control from whatever plugin each was assigned to. This would be *much* more useful for live situations than the current ACT behavior, which is better suited for recording/mixing.
  5. Maybe don't write out the entire name of the product (for now)? Instead of "NI Symphony Series Brass Ensemble Trumpets", why not "NISS Trumpets" (since trumpets are obviously part of a brass ensemble)?
  6. I have some recent projects that have 10-12 tracks of drums with 5-6 takes (clips are linked). Navigation was always quite slow, especially after comping/editing. I checked one of these projects just before installing the update and then again after install. Significant improvement. I also have a client who sometimes brings me 60-80 takes of his lead vocal. This can really bog things down. This should help with that quite a bit, I'd assume.
  7. Clips pane performance improvements are very welcome (and very noticeable). Thanks guys!
  8. Not a bug. This image is created in order to show a project preview in the Start Screen.
  9. In a pinch, you could duplicate the track/events and then link the clips to allow for easy editing.
  10. So, you bounced your tracks to a whole new set of tracks? Did you delete or archive your old tracks? If not, could simply be you are pulling too much data from your hard drive.
  11. Makes sense. I wonder if the B2C algorithm could then analyze how the clips relate to each other in time before starting the process. Many times, the clips I'm bouncing all have the exact same start and end times, so being aware of that and then processing them together would make sense. For clips that don't start/end together (let's say you have one that spans 3:01:000-10:01:000 and another than spans 5:01:000-12:01:000), then you could still run the bounces in parallel by drawing a virtual "box" around them and running the bounce from the earliest start time to the latest end time and including each new clip as its start time is reached during the pass. Of course... I know very little about the complexity of coding such a thing.
  12. These are all valid points, but kind of off-topic. I'm referring to a very specific bug that occurs with Elastique algorithms only. The usefulness of AudioSnap is a separate conversation that deserves its own thread.
  13. Too big to attach here... so here you go: http://www.mistercatstudios.com/mtest.zip 1) Open the project. It contains one audio track of an overhead mic from the drum kit. The tempo map has already been adjusted to match the human performance. No timing changes have been made to the audio at all. 2) Check playback from various points along the timeline. The metronome should match the drums perfectly. 3) Select the clip and open the AudioSnap Palette. Change the Online Stretch Method to "Elastique Efficient" or "Elastique Pro". 4) Check playback again. The further along the timeline you go, the further away the drums get from the metronome.
  14. Radius Mix works and sounds great, but is not available for realtime processing. The issue I'm describing affects realtime playback. It means "Groove" and "Percussion" algorithms are usable, but both Elastique algorithms are not.
  15. Yeah... this is a different issue. "Bounce to Clips" is always done one track at a time with the current Cakewalk engine. BTW... looking at your video, you can see much more clearly what is going on with CPU usage in Task Manager by right-clicking on the CPU graph and choosing "Change graph to -> Logical Processors". It will then show all 8 threads and their usage on your Core i7.
  • Create New...