Jump to content

msmcleod

Staff
  • Content Count

    4,572
  • Joined

  • Last visited

  • Days Won

    22

msmcleod last won the day on January 16 2021

msmcleod had the most liked content!

Community Reputation

3,290 Excellent

About msmcleod

Recent Profile Visitors

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

  1. Finally got around to finishing off watching season 2 of Star Trek Picard, and in the last episode noticed Rafi was using a KORG nanoKONTROL 2 to hack into the drones... ... with a strategically placed bit of aluminium covering the KORG logo & name.
  2. Unless you're up to date with all of the latest the Windows 7 updates, you may have issues using the in-app refresh activation. Downloading BandLab Assistant and using that to update activation is still an option on Windows 7.
  3. Arranger sections are definitely not tied to any of the material - they're either tied to a specific MBT time by default, or specific sample time if the arranger track is set to absolute time. There's really no such thing as single track ripple editing... there's either Ripple Edit All or Ripple Edit Selection, so I'm assuming you're using Ripple Edit Selection for tracks. Ripple Edit Selection should have no effect on arranger sections - only Ripple Edit All all does. Moving an arranger section will move the events under it, but not the other way around... unless you've got Ripple Edit all on. From what you're saying though, maybe this isn't always the case. If you do see a case of arranger sections moving unexpectedly, please let me know the steps to reproduce, or alternatively post a video of it happening.
  4. This message is in response to Windows telling Cakewalk this MIDI device has been removed. If it's coming up repeatedly, then it could indicate one of the following: A dirty USB connection ( clean your USB connections - I normally use contact cleaner, or WD40 ) A faulty USB cable ( try another cable ) An out of date driver for your device ( update the drivers if it has any ) A fault in the device itself... in which case it might need replacing
  5. I don't think you'd want to add the MPKMini as a control surface. Control surfaces are primarily designed for controlling transport. Just enable its MIDI input within Preferences->MIDI->Devices.
  6. We're not aware of any outstanding Arranger bugs - can you elaborate?
  7. Sad news... https://www.theguardian.com/music/2022/may/19/vangelis-greek-composer-chariots-of-fire-blade-runner-dies
  8. You could try checking "Always open all devices" within Preferences->Audio->Playback and Recording. On adding a track, Cakewalk enumerates all the devices for populating the input/output dropdowns in the track header. This is much quicker if the devices are already open and ready to go.
  9. Sounds like you're running CbB as Administrator. Windows automatically disables drag/drop between applications running as non-admin and admin.
  10. I got this, but the CPU usage is crazy high... (both in CbB and Studio One 5) anyone else seeing this?
  11. From what I can tell, the clips or the content aren't actually moving, but what you're actually seeing is the clip being drawn slightly differently due to where the split points are. When you're zoomed out, the drawing of a clip is average of the waveform as it's trying to draw several sample values in a single pixel. The number of samples that are being averaged are changing as you are effectively changing the length of the clip by moving the split point. As you zoom in to the point where samples are more obvious, this effect is lessened to the point where it doesn't happen at all. But audibly, the clip is fine.
  12. Yes, you can do that. Just insert a new synth, and change the output of the MIDI track to that synth.
  13. Yes, you can do that however: 1. It requires knowledge of how MIDI tracks / soft synths are routed, and 2. Most new users just want the track to be an single instrument track, rather than separate MIDI / synth tracks. Having separate MIDI / synth tracks makes for a more complex project ( up to double the track count ), and can cause confusion for new users. For example, the gut instinct for adjusting the volume of, say a piano track, is to go to the track with all the piano MIDI data on it and changing the volume slider... except by doing this you're not changing the piano's synth's output volume, you're changing the MIDI volume ( CC #7) of that channel. Instead you have to go to the synth audio track to change the volume. And then there's which track to use for FX, or MIDI vs VST automation. So you have to be constantly aware of what you're adjusting and how things are routed. Simple Instrument / Per Output Instrument tracks take the complexity out of that. You've still got complete control via the Track Inspector Midi/Audio tabs, but by default it's easy to work with. The only limitation with using instrument tracks is the case where you've got several per-output instrument tracks fed to a single synth instance, and you need automation on the VST parameters. In this case, you're limited to putting the VST parameter automation on the first track. However, this can be usually worked around by mapping CC's to the parameters within the VST itself, then adding MIDI automation in each individual track. Alternatively, you can create an additional MIDI track solely for adding VST automation.
  14. msmcleod

    Automation trick?

    Yes - the shelf tool alters existing envelopes. If there's no node to the right of it, there's no envelope to modify at that point.
  15. @Torbjörn Lundberg - there are a lot of different ways to do this, as detailed in this thread - but I admit the explanations are a bit daunting for new users. For new users, I'd recommend doing the following: 1. Create a new Kontakt instrument track for the track you want to change, then move that track so it's underneath the old MIDI track. 2. Select everything in the old MIDI track by clicking on the track number, then hold down SHIFT and drag the MIDI clip selection to your new Kontakt track (holding down SHIFT stops the MIDI clips moving left/right in time when you're dragging). 3. Delete the old MIDI track. I appreciate there'll be a bunch of users who think "Why, when you could just do X,Y, Z.....", but this method is simple and easy to understand for new users. There are definitely more efficient ways of doing this, especially if you're going to be changing all of your tracks to share a single Kontakt instance, but this should at least get you up and running.
×
×
  • Create New...