Jump to content

Mike Z

  • Content Count

  • Joined

  • Last visited

Everything posted by Mike Z

  1. Thanks for that note. I'm aware that my plugins are a little scattered and could use some cleanup. I have plugins that came with my M Audio keyboard and more with my Steinberg interface, plus anything I've downloaded to try out; I let them install in their default locations. I figure there's no real harm in scanning several folders (even scanning folders multiple times) other than speed; CbB boots up so quickly that it doesn't bother me.
  2. I'll see if I can walk you through this... Under Preferences, look on the left sidebar for File -> VST Settings You should see at the top "VST Scan Paths"; click "Add" Navigate to the spitfire audio folder, click OK. You probably have to manually scan again (click the "Scan" button) Hope that works for you!
  3. Don't be too modest, you already impressed me with the chicken sandwich trick. : )
  4. Hi Marcello, I've been following this thread, maybe I can offer some help too. YouLean loudness meter has a way to show you the true peaks in real time (not just the average or integrated levels). If you disable the Short-term loudness graph you'll see a different picture. If you have any large peaks (for example a kick that is putting out a high level in the sub-50 Hz range) you'll see it quickly. Also, you mentioned the red lines/dots at the top of the meter; I believe those are spots where the peaks exceed the True Peak Max level setting. I'm using the free version and I think the preset for that is -1 dB. Any peaks higher than that will show up with a red dot. If you have the Pro version I believe you can set your True Peaks manually. For me, looking at the True Peak loudness gave me a lot of information about why my songs were showing up as "too loud" even though they didn't sound loud.
  5. I used SAW32 for awhile back in the early 2000s, I agree it was a great DAW for the time. I recently found a list of "DAWs through the ages" or something like that, and SAW wasn't mentioned so I had to search for it. Apparently there is still a cult-like following for SAW, mainly because of how streamlined and stable it is.
  6. I bet you could shake that abacus and make a nice percussive sound.
  7. Try downloading Youlean Loudness Meter... there's a free version as well as the pro. Set the display to show True Peak values and you will watch the wave in real time. If you change the compressor settings (ratio, threshold, etc.) you can see how that affects the peaks and overall volume levels.
  8. I started using the free version of Youlean loudness meter a few weeks ago, would never go without it again. One side benefit for me of Youlean is it really helped me get a better grasp on how to set my compressors. I set up Youlean to display True Peak values then began adjusting the compressor settings. Changing the threshold, ratio, and output settings shows how that affects the track volume in real time. It really makes a difference for me in managing peaks and loudness levels without compromising the dynamic range of the recordings.
  9. This is from Cubase 10.5 LE: This option is offered on a project-by-project basis. The default setting is 0, when I changed it to 1 as shown, the timer ruler ended up like this:
  10. Thanks, I didn't realize Cubase has that option. I just tried it and it works exactly like I expected: the time ruler now starts at 0 and proceeds from there. When I tried it on an existing project, it even asked if I wanted to shift the clips to the new start position, or leave them as they are.
  11. Thanks, but I'm not looking for a count-in before the recording starts, I'm looking for a count-in before the playing starts, while recording, so that early notes get recorded. Exactly. A musical score starts at measure 1, not measure 2. Yet every DAW forces songs to start at measure 2 or later to allow early notes to be recorded.
  12. I don't want a count-in before recording, I want recording to start before playing so I get the dead air space before measure 1. This is what I've already been doing, beginning at measure 2. What I'm suggesting is that the song should start at measure 1, with a bit of room for grace note/pickup notes before that.
  13. I've been thinking about this for awhile now, haven't seen it on any DAW yet. I would like my projects to start at measure 0 instead of the usual measure 1. The reason is that I always like to have a bit of silence between hitting the Record button and starting to play. Sometimes there's a grace note or pickup note before the bar, other times it's just an eager note that hits a little early. I don't like cleaning those up because it can add to the organic feel of songs. If all notes hit at exactly the same time it can sound too mechanical imho. Normally, I wait until measure 2 to start recording. That means all the measures in the song are advanced by 1 (eg. a 16 bar phrase starts at measure 2 and ends at bar 17). I can't imagine this would be difficult to implement; it probably should be an "opt-in" feature since many people will want to stick with the way it's always been. Just a check box in Preferences to start the Time Ruler at Measure 0 instead of 1. I realize this is a minor issue, I could live without it (have for a long time now) but it would help me stay organized a bit.
  14. I can't help with the Novation keyboard, but i spent some time learning how to configure an Oxygen Pro 49 to use with CbB. here's what I learned, maybe you can modify the approach to use on the Novation. The rest of the thread has some good info on ACT and control surface mapping, which is relevent for you as well.
  15. Here are some screen shots. Note that I picked a synth patch where velocity is very noticeable, notes played softly sound very soft and notes where I hit the keys hard sound very different. When I play it back with the effect bypassed I can hear the difference in note velocity (both loudness and timbre) but when the effect is activated the notes all sound the same.
  16. I just tried this, I don't know all the ways to use the Velocity plugin but if you click on the top left of the plugin (Presets) you should find a preset named "All 127". Select that and it will set all velocity of all notes to 127, the highest setting. The nice part of this is that it doesn't actually change the velocity of the notes, for example if you look in the piano roll view and expand the bottom section, you'll see that the notes all stay at the same velocity from when you recorded them. But with the plugin activated they play back at the same maximum velocity. You can see in the volume meter for the track that the notes are playing back at maximum velocity.
  17. I have a Dell laptop with touch screen, and CbB works perfectly by touch.
  18. @Astraios @msmcleod I tried duplicating this issue, here's what I found: -with no drum map everything worked as I expected; Deleting a track, then Undeleting returned the synth track properly, all settings back , etc. -when I added a MIDI track and drum map (Steven Slate Drums), deleted a synth track and Undeleted it, the track returned but the same instrument as the track immediately after it (Piano 1 in this case). -If I right click --> Replace synth and select the original synth (Saxophia), now the track has Steven Slate as the instrument even though is still is labelled as the original instrument -right click again, select Replace synth again...this time it actually replaces the synth with Saxophia, but it also replaces Steven Slate with Saxophia. Both tracks seem linked together now.
  19. In the plugin manager dialog, click a little lower on MIDI Effects (MFX). That should display your GR6 MFX on the middle field (Registered Plugins). If it doesn't show up on the far right field (Plugin Menu Layout) then you'll need to click on "Add Plugin" to add it to the menu tree. Also, I believe on the Effects rack in the browser, Guitar Rig 6 will show up under audio effects, while the MFX version will show up under MIDI effects. (I don't have the MFX version so I'm guessing here, but I think that's how it works)
  20. If you mean setting the DAW type on the keyboard to Bitwig, I believe the only fix is to change it to MPC or Reason or Ableton. Any other DAW types I tried had various odd issues (especially when panning).
  21. Bumping and adding my support for this request. Collapsing the track should also collapse the automation/take lanes associated with it.
  22. I'm definitely a supporter of this idea.
  23. I'm not 100% certain (going by memory here, don't actually have my e-kit connected right now) but I think if you use a MIDI cable to connect your Alesis kit to your audio interface you should be able to set your track input as "All Inputs --> MIDI omni" and that'll accept MIDI notes/commands from just about any MIDI device. I think that's what I did last time I tried this.
  24. There's definitely an issue getting meters to toggle properly with a key binding. I assigned a shortcut to "Show/Hide All Meters" and it worked... but only to turn on meters. It never turns them off again. And if I assign the shortcut to "Options | Meter Options | Track Playback" or "Options | Meter Options | Track Record" it doesn't do anything. Strangely enough, if you assign a key to "Reset All Meters" that seems to work.
  • Create New...