Jump to content

msmcleod

Staff
  • Posts

    6,835
  • Joined

  • Last visited

  • Days Won

    35

Everything posted by msmcleod

  1. One solution could be to do everything in 440Hz, then slow down the 2 track master in an audio editor (e.g. Audacity) so that it's effectively playing at 432Hz.
  2. No, CbB will always use the default system browser, but FWIW I've got Firefox set as my default browser and BandLab login in CbB via Firefox is working fine for me on several machines. Check Firefox is up-to-date, and also check your security settings within Firefox. I'm using the Firefox default settings for security.
  3. Omnisphere is memory intensive, so it's possible it could be a bad memory. This has happened to me in the past and is very difficult to identify. If you're lucky, you might see some discrepancies in the BIOS when it's reporting the speed of your memory modules - i.e. if one looks different from the other, that's a good indication that one has gone bad. Alternatively, Windows 10 has a built in memory checker: https://www.windowscentral.com/how-check-your-pc-memory-problems-windows-10
  4. Although it's best to install them in order, I don't think it's absolutely necessary as long as you install (or re-install) CbB last.
  5. Within Preferences->Keyboard Shortcuts, it's possible to bind the commands to MIDI notes - including start/stop. However this will start/stop the whole project, not just a specific track. To trigger a specific track, you could use the Matrix view - however, the Matrix view is clip based, so you'd need to make sure that everything on that track is a single clip (i.e. bounce to clip(s) ).
  6. I've still got MasterWriter 2 running on a VM running Windows XP... it does the job well.
  7. Drag the meter bar (where it says +6 0 -6) up and down and it'll zoom the meter scale. Double clicking it will reset it to the default.
  8. Linked clips allow you to change one clip, and the change will happen in all of the others. It's useful when you want the same thing repeated many times, and you don't want to have to edit the same thing in all of the copies. The whole point of linked clips is that the contents of them remain exactly the same - so you can't select lots of clips and link them. Linking can only be done at paste time using the "Paste Special" command. To unlink them, select the clips you want to unlink, right click and select "unlink". Linked clips is a pretty old feature, which in many ways has been superseded by groove clips / step sequencer clips. However whereas groove/step sequencer clips can be "rolled out" to many repetitions, a linked clip has the advantage in that it can be placed anywhere and changes will still be kept in sync. The main use case for linked audio clips is repeated copies of a drum loop.
  9. Double check your anti-virus, OneDrive and any cloud sync settings, and make sure your Cakewalk projects directory, and global audio directory are excluded. If any of these are trying to access the audio files while Cakewalk is using them it could cause a freeze or a crash.
  10. I've personally gone through a range of USB MIDI interfaces that have failed to perform to expectations. By far the worst performers were USB MIDI cables. There are two issues with these cables: 1. USB runs at 480Mbps , where as MIDI runs at 31.250Kbs. This means data being sent out needs to be stored in a buffer, so that it can be sent out at a slower speed. The issue is that the buffer in these cables is tiny (in the order of a few 100 bytes), so it doesn't take long for that buffer to be full, and data to be lost. This leads to stuck / lost notes, pitch bend / modulation being jumpy, and sysex basically not working at all. A good analogy is a bucket with small tap in it - you're drinking from the small tap, but at the same time it's being filled from a waterfall. The bigger the bucket, the less water overflows.... these MIDI cables have a very small bucket. 2. You can't really use more than one of them. Each of the cables is seen as a generic "USB Compliant MIDI Device" making it impossible to tell each one apart - and because of the primitive way Windows deals with both MIDI and USB, depending on which port fires up first, they can swap port numbers without reason. Friendly names in Cakewalk won't help you here, because Windows swaps the devices around. The MIDISport 8x8 and 2x2 used to be my interfaces of choice, but their drivers have not been updated for years and now prove unreliable in Windows 10. The only interface I can rely on nowadays is my Miditech MidiFace 8x8 (they also do a 4x4). This is a USB 3 class compliant device. I have 3 control surfaces and several controller keyboards running off one without any issues whatsoever.
  11. As others have mentioned... don't use MIDI notes for key switches or commands - use articulations instead. Articulations won't appear as notes in the staff view. There's an outstanding task to associate articulations with staff view articulations, although I can't say how soon it'll get scheduled. This won't allow you to edit articulations in the staff view, but will at least show you them.
  12. It's not Cakewalk doing this, it's Windows. Windows blocks drag and drop between programs running as different users as a security measure. There are a handful of old DX plugins that need admin permissions on their very first use, but aside from that there's no reason to run Cakewalk as admin. Also, consider that if Cakewalk is running as admin, so will every plugin - are you 100% happy with giving every plugin you've downloaded unrestricted access to your PC?
  13. Just had a look at the code which greys out that command. The conditions are: 1. The selection contains something other than step sequencer clips 2. The first stream in the selection is a MIDI stream. I suspect you've got an envelope stream (either automation or tempo) in your selection. Try switching off "Select Track Envelopes with Clips" in the TV Options.
  14. Ouch - sorry to hear that. Yes, that would explain it. If the CPU is damaged or starved of power, it can cause crashes. I actually had a similar issue, where my CPU would freeze after an hour or so of heavy network traffic (e.g. getting the latest NI Komplete, or copying files). Very frustrating. It turned out that the default CPU voltage setting in the BIOS was just slightly too low. It took me about 4 years to work this out.
  15. IIRC Articulations don't work for live MIDI input. Short of a hardware solution to re-map channels, the only other way I can think of is to use the down arrow key to switch track focus while you're playing. This won't work for recording though. Other solutions spring to mind: 1. Record arm all and echo enable all 3 tracks, but use mute automation to mute the tracks you don't want to hear when recording. Then just trim the clips afterwards to remove the parts you don't want. 2. Use something like TTS-1 with program changes for piano at bar 1, guitar at bar 3, and harmonica at bar 5. Record your performance on that track, then split/copy the clips on to your Kontakt tracks. It's less than ideal, as the sounds you're playing won't be the same as what Kontakt is. However, I have used this technique in the past, except using hardware instruments rather than TTS-1, to avoid latency when recording additional parts in an already busy project, and it's not quite as bad as it sounds.
  16. This error message is Window's cryptic way of telling you the device is open by another application. Check Task Manager to see if any other programs are still running that may be stealing your MIDI device.
  17. First rule out a config issue: 1. Check your Keyboard Shortcuts aren't configured to use the sustain pedal as a SHIFT key: 2. Make sure Controller events are enabled: 3. Make sure you have no control surfaces using the MIDI port your pedal is coming in on: Once you've ruled those out, check the hardware configuration of your pedal. Quite a few pedals have a polarity switch. Some keyboards automatically detect the polarity on start up, whereas others require it to be set a particular way. If your pedal has such a switch, try flipping it and trying again.
  18. When you make edits or copies of clips (also splitting a clip will make a copy), copies are made of the waveform files to support the undo process. Once you undo, most of the files should be deleted. Some commands however, such as freeze will keep the files to support the "quick freeze" process. You can delete any unused files by choosing "Clean Audio Folder". Be really careful with this command though, as once those files are gone, they're gone. Avoid searching any directory other than the current project directory. Also, do not use this method if you use Cakewalk project versioning / auto save, or you save copies of your project in the same folder, as it can only find files that it knows aren't part of the current project - it has no idea what files the other projects might be referencing. So check the files before you delete them. In the example below, I know the project is MIDI only for the time being, so any audio was either a bounce/freeze or possibly some temporary guitar recordings.
  19. If you want to make a mono clip into a stereo one, just right click on the clip and pick "Convert to Stereo". I'd have recommended this in your other thread, however the question in the other thread was how to combine two mono clips into a stereo one (and I assumed the two mono clips were actually different).
  20. Use per-output instrument tracks with Kontakt. It won't matter what MIDI channel your keyboard is set to, it'll just use the correct MIDI channel for whatever the focused track is using: Note there is only ONE instance of Kontakt in use here - all the instrument tracks are sharing the same single instance of Kontakt.
  21. The lyrics view is primarily used for adding lyrics to Karaoke MIDI files. IMO it's not really suitable as a prompter. This is how I do lyrics prompting using Melda's free MNotepad and automation:
×
×
  • Create New...