David Baay

See the solution I gave two threads down in this forum: - Set the Now time at Measure = current tempo +1 (191). - Shift+M t to open Set Measure/Beat At Now. - Enter target tempo +1 (96) for Measure, Beat 1 and OK. - CbB will change the initial tempo around existing MIDI (and audio of present) without altering its absolute playback timing

Can't say I've ever encountered that, and can't repro now. Does it persist after restarting CbB and/or rebooting? If so, are there a lot of controllers/articulations or other special content in the track(s)?

What I'm seeing is that articulations copy/paste as expected when whole clips are selected, but not when only part of a clip is selected in either the TV or PRV. I agree it would be expected that articulations are duplicated by both Groove Clip Looping and copy-pasting partial selections.

Late to the party. I just happened to stumble on this while searching for something else. FWIW, I have written CALs where the modification of an event depends on some parameter of the one before it - or vice versa. Like billp, I have just had to save the the parameter(s) of the one event for use in processing the preceding/following event on the next iteration of the loop. I don't fully understand the issue you have with the order of notes in a chord, but it sounds like you would just need to check for simultaneity of start times (maybe within some user-specified number of ticks if chords aren't hard-quantized) and save the necessary paremeters of several events in a row to be used on the next pass. Bottom line, there is no way to store the infromation in an array. You have to create a sort of facsimile of an array using indexed variables like lastChord1, lastChord2, lastChord3 , etc.

FWIW, on my Dell laptop, the main cause of DPC latency spikes is ACPI.SYS which is involved in power management and, as such, is highly "active" in a laptop - even when it's plugged in - as compared to an AC-only desktop. I have not had any such problems with my Dell desktops. I researched and tried a lot of tweaks to address it, but only succeeded in creating other problems like the laptop failing to sleep/hibernate when it should and running its battery flat overnight. Since the laptop is not my main DAW, and doesn't need to deliver the lowest possible latency for input monitoring, it's not really a big deal for me. I do get the odd crackle once in a while, but actual engine-stopping dropouts are rare. EDIT: Looking back through my notes, I see that I have had spikes from Wdf01000.sys, and putting the laptop in Airplane Mode seemed to eliminate it at the time.

Dupe

Sure. First, understand that having 100.75 beats pass in the time of 75 is the same as having 100.75 measures pass in the time of 75, and it's just easier not to have to convert measures and beats to total beats. Then all you're doing is telling CbB "I want 100.75 measures (100 measures and 3 beats in 4/4 time) to pass in the absolute time that's currently at 75 measures from the start". But measures are counted from 1, not zero, so you need to set the Now cursor at 76:01, and tell CbB to adjust the initial tempo to make measure 101, beat 3 hit that absolute Now time (i.e. 3 minutes, 56.8 seconds).

After you Write the preset to the User bank, click the instrument name again and choose Save Bank. Save the .GMN file with an appropriate name. Note, however, that CbB does not automatically reload the saved bank file when you re-open the project. The instument assignment will have been save independently in the project, but if you want to load presets from the saved bank to another channel or change the instrument assigned to the current channel using some other preset in your custom bank, you will need to manually Load the saved file into the current session.

Go back to the original 75 BPM project with the synced audio and MIDI. - Set the Now time at 76:01. - Shift+M to bring up Set Measure/Beat At Now, enter measure 101, beat 4, and OK. - CbB will reset the initial tempo to 100.75 without affecting the playback timing of either audio or MIDI. - It will also add a mathing tempo node at 101:04 which you can delete. Alternatively, to have CbB find a possibly more precise average tempo: - Let the project play with the metronome disabled and count bars out to the last downbeat. - Stop the transport , zoom in, and place the Now time precisely on the downbeat transient. - Shift+M, enter that measure, beat 1 and OK. - CbB will calculate the tempo needed to make that measure/beat hit that Now time and change the project tempo .

I made an articulation map for the Kontakt Factory Library "Flute (all)" patch based on the following "style" info and did a quick test: case (24) message ("Staccato 1") set_text ($info,"Staccato 1") case (25) message ("Staccato 2") set_text ($info, "Staccato 2") case (26) message ("Sustain") set_text ($info, "Sustain") case (27) message ("Sforzando") set_text ($info, "Sforzando") case (28) message ("Fortepiano") set_text ($info, "Fortepiano") I found the volume variation with velocity worked pretty much as expected for all articulations. The Staccato, Sforzando and Fortepiano articulations are initially a bit louder due to their emphasized attacks, and indeed, the lowest level you can get at the default MIDI volume of 101 is around -36dB for these articulations vs, about 10 dB lower for the Sustain articulation. -36dB is pretty quiet at normal monitoring levels, but if you need to go lower, you can just lower the instrument's overall level using either MIDI Volume or Expression. For example, lowering the MIDI track Volume to 64 allowed a minimum level for a single Stacatto note of about -50dB and a maxmum of -19dB - a 30dB dynamic range which seems reasonable for a flute.

Glad to help. Incidentally, it sounds like you manually inserted and adjusted tempos to fit the timeline to the musical tempos. In future - or maybe even in this project - you might want to look into using Set Measure/Beat At Now (Shift+M) to build the tempo map. You just tell CbB where the beat transients should fall, and it calculates and inserts the tempo changes for you to make that happen. I'm a huge advocate of this technique to allow recording without a click and then matching the timeline to the performance and tightening it up as needed.

That's kind of what I was getting at: In the absence of video, you could get a very comparable aural result from far less hardware (though, admittedly I skipped ahead at some point - probably right around the 6-minute mark - to see how the video would end, so maybe I missed something important...?). The video content is the only thing that made me listen for more than a minute, and it wasn't captivating enough to make me endure the full musical composition.

Kontakt should be able to scale volume/loudness more or less continuously across the velocity range regardless of the number of velocity layers. What you typically hear with a limited number of velocity layers is sudden transitions in timbre, not volume. I haven't played around with articulation maps much at all but if the OP shares the .artmap file, I can give it a shot with the Kontakt Factory Library and see if I can reproduce and/or diganose the problem.

What keyboard and are you monitoring the keyboard's onboard sound or using a soft synth? And if it's onboard sound, is it triggered by Local Control or by MIDI echoed through a track in CbB and back to the keyboard synth? I've seen the opposite problem with some soft synths that sustained notes are stopped by All Notes Off (CC123) sent from the keyboard when the last key is released (not all keyboards do this, but my Roland RD-300s did). This is a MIDI programming error specific to some synths (e.g. TruePianos). But I've never heard of this happening the other way around as you describe it. Incidentally, just to be clear, releasing the sustain pedal should cause the keyboard to send CC64=0 (or a series of events down to 0 if the pedal/keyboard implements continuous sustain), not Note Off(s). EDIT: I see from your other post about the MIDI problem that it's a controller-only M-Audio Hammer 88 . Strangely, the manual does not have a MIDI Implementation chart, so I can't tell if it ever sends CC123, but it does indicate that the sustain is On/Off only. So the big question is what piano synth are you using?

Maybe using onboard sound? Most internal sound chips/cards have an option in the mixer to use the output as an input for recording - commonly called "What U Hear" or "Stereo Mix". Otherwise you would need to physically patch outputs to inputs on your Focusrite.

Yeah, I'm pretty sure you could get that out of a laptop running just CbB with a copy of NI Komplete Standard and a 49-key MIDI controller. ;^) Just don't ask me to troubleshoot "No sound" from that setup ? More than 'shades' of Vangelis.

I agree the amount of change he's dealing with is pretty small, especially considering it's over 16 bars. But if he cuts it up and moves parts around without allowing them to follow tempo, or flattening the tempo overall, he's going to have gaps/overlaps at clip boundaries and sync problem if he moves pieces if individual tracks. In this context, it could be audble if he doesn't do one or the other.

- Save As a copy of the project with "Flattened Tempos" appended to the name. because you're going to be deleting your painstakingly matched tempo changes. - Select all audio clips. - Open Audiosnap section of Clip Properties in the Inspector and check the 'Enable' box. - In 'Follow Options', choose 'Autostretch'' (this mode stretches audio uniformly between tempo changes without regard to beats). - Check the 'Follow Proj Tempo' box above Follow Options to enable audio stretching to follow changes to project tempo(s). - Switch to the Tempo List in the Inspector and delete all the variable tempos, leaving just the initial one to be the fixed tempo (you can then adjust that one tempo as needed). - Experiment with different stretching algorithms on different tracks (see Audiosnap documentation). - When you're satisfied with the result, you'll probably want to render the stretching permanent by Bounce to Clips(s)) to get the best possible audio quality. - As before I recommend doing detructive things like Bounce to Clip(s) in a new copy of the project so you can revert to the non-destructively stretched version if you determine something needs to be fixed later.

When using a keyboard synth, it's usually best to set it up as if it were separate keyboard controller and sound module. Disable Local Control of the internal sounds from the keyboard and echo the MIDI through a MIDI track in CbB and back to the keyboard synth. For drums, the keyboard synth will probably want to see MIDI on channel 10, but you don't have to change the transmit channel on the keyboard; you can just set the forced ouput Channel in the MIDI track to channel 10, and leave the Input set to channel 1 of the keyboard's MIDI port. The same goes for any other instrument sound you might want to use from the keyboard, assuming it's multi-timbral - just set the the output channel of a dedicated MIDI track to the relevant channel in the multi-timbral patch setup. You'll probably also want to find and load an Instrument Definition for the keyboard synth so you can set patches from the MIDI track so you always have the right sounds on the right channels for a particular project. You can continue to use 'live', real-time audio output of the synth from the recorded MIDI while devleoping a project, and only commit to recorded audio when the arrangement and MIDI editing are complete. Just don't make the mistake I've made in the past of only recording the final Master and never recording the individual synth tracks such that I couldn't revisti a project later because the synth had died.

When you have Always Echo Current MIDI Track enabled in Preferences > MIDI > Playback and Recording (on by default), the currently focused track will show an 'A' for 'automatic' in the enabled Input Echo button. If you click that button, the 'A' will go away, indicating that Input Echo is forced On and will continue echoing even when focus moves away. This allows having more than one track echoing input (for purposes of layering, etc). So check that other tracks don't have the Input Echo button lit. Otherwise, you should not be encountering this problem, and it should not be necessary to to assign specific input channels. But I usually do recommend choosing channel 1 for everything to avoid doubling in the case that some MIDI source is sending on more than one channel (as my old RD-300s did by default).

I can confirm that inconsistency with Send Level and Pan controls. Double-clicking anywhere in any other control resets it and never opens text entry. With track/bus Volume controls you can double-click the numeric value to enter text, but I usually use Enter on the keyboard to access text entry for any control, regardless.

Yes, that's my understanding as well. And the change is pretty subtle and would probably only be really noticible if it's out of sync with some other timing reference. So.. what's the goal?

Didn't know there was such a thing. ;^)

I've sometimes had only the 'touched' track change, but always attributed it to workiing too fast and releasing Ctrl a moment before making the selection. I don't recall ever seeing some-but-not-all of them change; are you sure about that?

More like an 'oversight' than a 'decision' probably. If they had taken the time signature into account, it would have been easy to specify "Beats in Clip" based on that, and probably not that difficult to implement after the fact.