Jump to content

K. M. Joshi

Members
  • Posts

    84
  • Joined

  • Last visited

Posts posted by K. M. Joshi

  1. The faster the speed of your CPU, the faster it'll handle tasks like rendering (effects processing/exporting wav stems). So mostly people who want high speed rendering (online/offline) would choose the first CPU.

     

    But since you want more VSTs running at once, I think having more cores is better for you. However, it comes with a catch— you won't be able to run gigantic VSTs at once though...or even one! (I doubt there are any plugins THAT gigantic though)

    Soooo I think...go for more cores! But keep in mind that too many online (inside DAW) pitch shifting, vocoding etc won't work well (it'll take a moment to finish) due to the slower speed. 😃 Reverbs, delays, compressors etc etc should work fine, but you might have to wait a bit for pitch changes and vocoder changes to complete before you can playback the audio.

     

    Hope that helps!

  2. 6 hours ago, David Baay said:

    He's talking about the Virtual Controller that you select as an input to a MIDI or Instrument track. 

    No, I'm talking about the vertical virtual keyboard in the piano roll view. That keyboard gives almost no visual feedback (when you play back and when you play notes on a real midi keyboard or when you draw notes with a mouse) and has no position-based velocity sensitivity.

  3. I think the current PRV virtual keyboard we have in CbB needs some additional features:

    1. Animation to show the PRV virtual keyboard playing when we input notes (midi/mouse) and when the track is playing. Most other DAWs have this feature, and I think it is useful as well.

    2. The PRV virtual keyboard should change velocity according to the position of mouse clicks, instead of just sticking to the velocity value we drew the last time.

     

    Thank you!

×
×
  • Create New...