Jump to content

David Baay

Members
  • Posts

    4,391
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by David Baay

  1. I'm pretty sure this is all working as intended. When soloing a track, everything contibuting to its output needs to be soloed also, or you'll lose the sound so the Synth and any MIDI tracks feeding it will also get soloed. That's not the case with Muting. Muting anywhere in the chain silences the ouput. When you mute the synth in the rack, it mutes any tracks that depend on it so you can see that those tracks aren't going to sound even when the rack isn't visible. But a synth can be feeding more than one audio track (either via multiple outputs or multiple tracks assigned to the same output) so muting a track should not mute the synth unless it's a MIDI track, and it's the only MIDI track driving the synth. An Instrument track associates a single MIDI track and a single audio track with a synth, so muting an Insturment track will also mute the synth.
  2. Set Beats in Clip value in Groove Clip section of the Track Inspector to the full length of pattern.
  3. I didn't actually see any mention of a specific Melodyne feature that's available via Rewire but not via ARA integration. But I'm not a Melodyne power user; maybe it's obvious to those who know the standalone app well. I mostly use it for Tempo and MIDI extraction which is best done inside Cakewalk.
  4. Probably wasting my time, but that Studio One screenshot looks a lot like an Inline PRV with automation lanes under it:
  5. It does of you use Alt+left-click with snap to zero crossings enabled.
  6. I didn't get the e-mail. But after logging into Eventide, I got the $29 offer by clicking on the 'Crossgrade' button on the Octavox page.
  7. Glad to help, and totally understand where you're coming from. It can be very hard to find stuff like this, so it was a good move to ask the forum. And I agree that mute tool (and normal split tool) should have an auto-fade option.
  8. Global snap applies when drawing tempos with the 'Freehand' tool, but the line tool (and probably other pattern tools) do not appear to honor snap. If you don't want to draw freehand, you could use Project > Insert Series of Tempos, but that works by entering a step value for bpm rather than a duration between changes, so you have to calculate the step size which is awkward, and the biggest tempo step it allows is 1 bpm, so its still generally going to insert more changes than necessary (this is an ancient function that needs updating). Since I record everything in real time, I'm usually coming at it from the other direction: making the timeline conform to existing tempo changes in the recording, using Set Measure/Beat At Now, so I end up with changes right at the start of each note whatever the interval is - no more and no less. Cakewalk really needs a 'smart' tempo drawing tool that only inserts tempos at note starts, regardless of what tool you're using to draw them. In the mean time, feehand drawing with snap enabled and then tweaking out any undesired 'roughness' in your drawing by clicking above or below the 'wayward' values (still with snap enabled so you modify existing tempos rather than drawing new ones) is probably the best option.
  9. I think you were right the first time that plugin delay compensation should just take care of it all transparently. And it does for the most part. I would urge you to take some time to figure out exactly what plugin or combination of plugins and/or project routing/setup is cuasing the problem in your current case, and report it to the Bakers with a demo project. If it isn't in fact due to misreporting of delay by the plugin, they may actually be able to address the problem. And if it is a problem with the plugin, they have relationships with major plugin vendors to help push for a solution.
  10. The only real 'difficulty' with Cakewalk in achieving the same result is that MIDI automation envelopes are only available in MIDI tracks, so you'll have to split your beloved Instrument track. It seems that just addressing this one limitation would go a long way toward addressing your needs, and shouldn't take a huge development effort; all the necessary functionally is already in place. Sure the flexibility of bezier curves is cool, but it shouldn't be a showstopper not to have that. Was Studio One unusable when it didn't yet have that?
  11. Change Source in the bounce dialog from Tracks to Buses, and select only the Master bus or the first bus where they come together.
  12. I doubt the Prepare using buffer has much to do with this. The root of the issue is having too many tempo changes. Musically, there's no value in having tempo changes at a higher frequency than notes are being played, and having that many changes will play hell with the rendering of some synths and FX. When drawing tempo changes, set snap to equal the smallest interval between notes events - looks like a quarter or an eighth in this case.
  13. Just to be clear, the pop is not being 'added'. It's the natural result of truncating a waveform where the amplitude is high. Stopping a high-amplitude signal dead at a zero-crossing will still result in a pop. The issue is not so much where in the cycle you stop the signal, but how fast the signal level is changing when you stop it. So, if you can't avoid cutting off the signal in a high-amplitude area, you must add short fade in/out. The easiest way to make this happen automatically is to use the Comp tool in lanes to split out the section before muting it. Comp tool automatically creates a short crossfade at split points. It defaults to 5ms which will suffice for most cases, but can be adjusted : Preferences > Customization (Advanced view) > Editing > Auto Crossfade Comps. And if you're actually compiing, Comp tool also lets you mute one section and unmute the corresponding section in the parallel lane just by clicking on the one you want to hear. Cakewalk as a deep and capable as any DAW out there; you just need to learn it.
  14. I'm always happy to give guidance via the forum where everyone can benefit from it. A lot of the more general quesions you have are probably better addressed by Googling the web at large for articles that that explain MIDI, synth, and DAW technology more broadly. Although many forum members have enough knowledge to write a book (and some have), not many have the time or inclination to write more a than a paragraph or two at a time on the forum. Where the forum shines is in answering specific question about how to accomplish some relatively narrowly-defined task in Cakewalk. You'll get the best mileage out of the forum and your time with Cakewalk by just diving in and trying some things, and asking more specific questions as they arise. The way you use Cakewalk will depend greatly on what kind of musician you are (or aspire to be) and how you personally like to work. Everybody's different in this respect, and you'll need to find your own way to a great extent.
  15. Sort of. brundlefly is yours truly. The new forum defaulted to showing my real name, and I decided to leave it that way. David Baay, a.k.a. brundlefly, a.k.a Seth Brundle.
  16. CC messages are not typically referred to as 'automation'. So what you want is per-clip controller messages. Is it mainly that you want the messages to go with the clip when you move/copy it around?
  17. 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.
  18. Edit Filter > Automation > <synth name> > <parameter> will allow automating applicable synth parameters in a simple instrument track.
  19. 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.
  20. 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
  21. In the Controller dropdown in the PRV menu bar, disable 'Select Controllers Along with Notes'.
  22. Alt+Ctrl+C to Copy Special, make sure Tempo changes are checked, OK, and then drag to destination.
  23. 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.
  24. 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.
×
×
  • Create New...