Jump to content

David Baay

Members
  • Posts

    4,917
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by David Baay

  1. A MIDI track just contains performance instruction for a synth; mono/stereo and interleave are not relevant to a MIDI track. 'Monophonic' in this context is referring to the limitation that Melodyne Essentials can only detect pitches in recordings where only one pitch at a time is sounding. Bass lines typically are mostly - but not strictly - monophonic. Assuming you're not talking about'loops' (typically short 2-4-measure recordings of instrument 'riffs') an 'instrument sample' is typically played by a 'synth' (software or hardware) responding to MIDI. For example a MIDI track sends (or echoes from your keyboard) a Note On event with note number 60 with a velocity of 100, and the synth responds by playing a recorded sample with the corresponding pitch (middle C) with proportional loudness and timbre according to it's programming. Some time later, the MIDI track sends a Note Off, and the synth responds by releasing the note (typically with some sort of gradual decay determined by it's programming or the recording of the sample). A 'keyboard workstation' is a type of hardware synth, so you're still talking about a 'synth bass' when the sounds are coming from a keyboard.
  2. Edit Filter > Automation > <synth name> > <parameter> will allow automating applicable synth parameters in a simple instrument track.
  3. It's not a dodge; it's simply a best practice. Apply Trimming just renders the non-destructive splits permanent so you're not tracking a million hidden transient markers unnecessarily. I wouldn't have suggested it if I hadn't tried it. I've never personally experienced the kind of drastic performance degradation you reported but I know that splitting at transient markers and leaving AS active on all those thousands of slip-edited clips has the potential to cause that.
  4. You should really follow up on some of the suggestions made in your old thread about your issues with editing multitrack drums before repeating this. Specifically, either apply markers from a guide track and quantize by stretching rather then by splitting as Lord Tim suggested, or Apply Trimming after splitting at transients as I suggested if that's still your preferred method: http://forum.cakewalk.com/Editing-multitrack-drums-is-completely-impossible-This-needs-to-be-addressed-m3362190.aspx
  5. In the Controller dropdown in the PRV menu bar, disable 'Select Controllers Along with Notes'.
  6. Alt+Ctrl+C to Copy Special, make sure Tempo changes are checked, OK, and then drag to destination.
  7. I misread this this first time to mean that pitch info was dropped from the conversion after expiration. I realize now you're saying the audio pitch correction/editing functions expire, but monophonic MIDI conversion (which is all Essential does in the first place) continues to work.
  8. First things first: make sure you have Follow Snap Settings checked under View > Grid Resolution in the PRV menu. This is a per-project setting, so if you have a template that doesn't have it enabled, that might explain why it isn't consistently working as expected. EDIT: Also make sure you have Show Vertical Gridlines enabled. Assuming that's set correctly, there's a limit to how close together Cakewalk will draw gridlines. If you set a fine resolution, and aren't zoomed in far enough for the the lines to be a reasonable distance apart, it will default to a coarser reolution. Other than that, I haven't seen anything like this recently, but I *do* generally have PRV snap enabled at a fine resolution while Global remains at a Measure or Quarter.
  9. Both Drum Replacer and Audiosnap allow extracting transient locations as MIDI, but the resulting note events will all have the same pitch (MIDI note number) and duration. So right away you've lost two of the most essential and difficult-to-reproduce elements of a bass part. So I really don't think either of those tools will be very useful for the purpose. If you have some flavor of Melodyne installed, dragging an audio clip directly to a MIDI track will automatically use Melodyne to extract the notes as MIDI data (including pitch and duration information if the trial hasn't expired as Steve mentioned). One issue to beware of with reinforcing a bass part using a MIDI-driven synth is that you will tend to get undesirable phasing effects from the interaction of the harmonics unless you only reinforce the fundamental with a simple sine wave, as is more commonly done.
  10. David Baay

    Flatten comp

    No, it's not possible to limit the scope of Flatten Comp to certain lanes or time ranges. Functionally, there's really no need to flatten a comp at all, unless you plan to move the resulting clip - or parts of it - to another track or section of the comped track or you just want to have it 'set in stone' to protect it against possible editing mishaps later. The alternative is to do it manually: - Select the comped section and bounce it to a new track. If desired, you can then drag that clip into a new lane of the original track and manually mute and lock the clips that contributed as Flatten Comp would. - Split the clips as needed before comping, select and drag the relevant sections (e.g. Choruses) as a group to lanes of a new track, holding Shift to preserve the start times, and comp them there. When using Bounce to Tracks, you'll need to beware of track Gain, Volume and FX getting baked into the bounces.
  11. The limitation of both those options is that they won't extract the pitch information. Ideally you would want to use at least Melodyne Essential for this purpose. I believe it's still available as a free add-on to CbB via the Bandlab Assistant. Beyond that, if you are okay with finding the pitches yourself, and just want the rhythm extracted, I would suggest you just try the other options and see which works best. Audiosnap is more flexible in terms of controlling the transient detection, and i would be inclined to go that way. Drum Replacer is optimized for detecting drum transients so I suspect it might not do as well with bass, especially if the part has a lot of sustained notes. And it won't be able to do direct replacement due to the lack of pitch detection.
  12. Fiddle-farting? I wager I'll have my MIDI track recorded before you can find your car keys. ;^) But, seriously, I can see where the advice to 'just record a real one' is sort of an extension of my 'just play it in real time' advice often given to those asking how to humanize their MIDI sequences, and I'm inclined to second it. The one caveat I would add in this case is that, in my experience, 'playing' a shaker well and consistently can be a more challenging musical endeavor than one might imagine.
  13. GM synths like the TTS-1 have a Cabasa on note #69 (A above middle C), and Maraca on note #70. I've been using these sounds from a Roland D-110 for decades (!) to do 'shaker' patterns. Some years ago I created an SFZ instrument of the D-110's drum kit that I can share on request. PM me an e-mail address if you want to give it a whirl.
  14. David Baay

    Icon Question

    I don't think so. Could be a handy feature.
  15. I assume you mean the position indicator for Aim Assist. Others have complained about that. Not currently possible to get rid of them other than toggling off Aim Assist (X). Personally I almost never use Aim Assist; having the line following my mouse pointer everywhere in the clips pane makes me nervous.
  16. After adding the track at the bottom, you can drag it to the desired position. There are several hotspots on the track where you get the 'move' tool; I usually hover just to the right of the track name field. Routing to a drum map is determined by the Output assignment of the MIDI track. Copying a MIDI clip to a new track can't bring a drum map assignment with it. It sounds like maybe focus is still on the original track in the PRV...?
  17. Just to minimize the number of possible variables, I would start by disabling 'Always Echo Current MIDI Track in Preferences', and set all the MIDI track inputs to None. Then make sure you have a forced output Channel assigned on each MIDI Track, and that the MIDI clips themselves contain no Pan or Volume controllers (CC10 and CC7, respectively). Incidentally, why not update to the latest 19.10 release?
  18. Your wish is the Bakers' command. That was just 'fixed' in 19.10. It's now an option in Preferences > Editing to have Paste Special settings persist, and they don't by default.
  19. View > Show Multiple Lanes
  20. The one mistake I still find myself making in the PRV is expecting right-click to bring up note properties. But when I need to delete many individual notes, I find right-click to be very handy. On the other hand, I adapted to lasso by dragging the right-click so easily that I soon found myself trying to do it in other applications or Windows Explorer, and getting unexpected results.
  21. At this point, there are so many useful new features and improvements (dozens of major ones, and hundreds of little ones) that it's hard to say what, if anything, is indispensible. But, off the top of my head, some of the biggies are : - Overall Stability and Performance - Plugin Support and Management - Navigation and View Management (Control Bar, Multidock, Inspector, Browser, Screensets, Lenses, Auto-zoom, Plugin Window Recycling, etc.) - ProChannel - Mix Recall - Patch Points/Aux Tracks - Take Lanes/Comping - PRV Track/Controller Pane Improvements - Ripple Editing - ARA and Region FX
  22. Three tips to help avoid problems with dropped/stuck MIDI notes: - Insert soft synths in the Synth Rack rather than in audio track FX bins - Increase the 'Prepare Using' buffer value to the old default of 500ms under Preferences > MIDI > Playback and Recording; the newer default of 250ms is too low in a lot of cases, especially if the project includes PDC-inducing plugins. - Make sure MIDI track inputs are assigned to a specific port and channel, and not All Inputs - Omni. Some MIDI FX plugins can also cause problems like this.
  23. Dragging and hearing the note replay sounds like you're getting the Velocity adjustment tool which activates when hovering at the upper edge of a note., and replays the note as you raise or lower the velocity so you can hear the result. Sizing and zooming the PRV view to make the notes a little taller will help distinguish the hotspots. The second part about superimposed notes isn't clear to me. Normally it's not necessary to have a new event start at the same pitch before the previous one ends. That musical effect is usually accomplished by using Sustain or Sostenuto on plucked/hammered string instruments or using legato samples/modes on bowed sting instruments. But maybe I misunderstood...?
  24. I generally resist the urge to comment on posts here, but sometimes the rest of the forum is so quiet, it's hard to resist. ;^) Ultimately these suggestions are intended primarily for the Bakers' eyes, but that doesn't mean other users aren't welcome to weigh in with their opinions about the value, necessity or implementation details of a suggested feature/change. It can happen (and has happened) that a suggestion gets accepted and implemented in a way that really screws up the workflow of long-time users, so they have right to register their concerns in advance. And, as you say, there appear to be many cases where a user isn't aware of an existing feature that offers most or all of what they want.
  25. Right-click deletes. Also not previously mentioned, I believe, is that left-click and drag draws a note of any desired length, and a very short drag before release draws another note of the last-used duration - effectively giving you a note with a single-click, no modifier, and no tool-swapping. Since it's difficult to make music of any interest using only a single duration (one-shot drum sample triggering excepted, of course), I would think a lot of note entry would involve this click-and-drag gesture.
×
×
  • Create New...