David Baay

Bounce to Clip(s) renders ARP output to a new clip, but there can be discrepancies between the realtime output and the rendered output in some cases. To record the real-time output, you would bneed to use a virtual MIDI cable or physical loopback.

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.49.html

5 ticks at 125bpm is 2.5 milliseconds. it's a rare bird who can hear, much less perform, with that level of precision.

Does the controller present separate 'control' and 'performance' ports in MIDI Devices? Sounds like your control surface setup as taken over both. I've never used a controller that was both a contorl surface and a performance controller so not sure how that's normally handled in ACT.

That doesn't seem possible. Unless you did a non-Fast, real-time bounce (?), audio preferences should have no bearing on the rendering of audio ITB.

I think you must have inadvertently grouped that fader with others. If it has a colored vertical bar along the left side (the group's color code), right-click and choose Remove from Group (or Clear Group if the whole grouping was inadvertent).

"Missing" from where? Do you have all the drivers for individual audio ports checked in Preferences > Audio > Devices?

4th approach (or maybe just expanding on the 1st approach described above): - Set up just one audio track to record and echo the stereo output of the synth connected to one pair of inuts to your interface (preferably always available) - Shift+Solo (override) that audio track so that it won't be muted by soloing MIDI tracks that drive it or other audio tracks in the project. - Create a MIDI track for each channel of the synth that you want to use with output channel assigned accordingly. - Do a rough mix of the parts using MIDI track volume, panning and controllers as needed. - When satisfied with that rough mix and the arrangement, solo each MIDI track in turn, and Bounce to Tracks with Fast Bounce disabled, and Audible Bounce and Live Input enabled in the bounce dialog, specifying a new target track for each part. - Archive bounced MIDI tracks as you go, and when you're done, disable input echo on the audio track so you're not adding to the noise floor of your mix with his from the idling synth. - When using a hardware synth for drums, you can put all the MIDI parts for each kit piece in lanes of a single track, and solo lanes when bouncing those parts to get multitrack audio. One thing to keep in mind: For any parts that are really low in the mix, you might want to make note of the audio live level of the soloed part, temporarily raise the MIDI volume up to get a better signal to noise ratio out of the synth while bouncing, and then take the level of the audio track back down after bouncing using its Input Gain or Volume controls. This will help to minimize the effect of summing of noise floors from all the separate bounces. This would also be a reason to consider doing all the drum mixing with MIDI, and recording a single drum audio track.

Rendering Audiosnap stretching (either in place or bouncing to another track) will often move transients a bit, depending on the nature of the audio, and which stretching algorithm you're using. This is a function of the algorithm, and should be the same in any DAA that uses the same algorithm. I've had at least one case where Elastique really messed with the timing of a single transient; changes of a few ticks should not be a problem in most cases.

Are you using the Volume fader in the vocal track to change the volume? And all tracks go to the Master bus, and from there to interface main outs? And the vocal track does not have input echo enabled? I can only imagine one possible routing setup within Cakewalk that could cause this to happen, and it's so unlikely, I won't even descibe it. But if your using onboard audio interface with input set to 'Stereo Mix' or 'What U Hear', (i.e. recording/monitoring from output of the interface), and the vocal track is echoing input, then the track volume could affect the whole mix. But you should also have bad feedback in that case so... I dunno.

I was addressing this: "This forces me to create a new instrument track, copy-paste the MIDI data and delete the two unwanted tracks while I could have simply used the existing instrument track and associate a different VSTi to it." Replace synth does exactly that . You didn't mention anything about changing synth channels at the same time in our orginal post, but you can do that via the Inspector after you've replaced the synth. Bottom line: it works the way it works. An instument track is by definition a combination of a MIDI track and an Audio track connected by an associated instrument plugin. Changing that to allow an empty instrument track will require re-defining what an Instrument track is as an object or maybe introducing a dummy , internal 'placeholder' instrument that Cakewalk uses to fill the void under the covers. Or you could just to that yourself by using some lightweight 'placeholder' instrument in your templates. Beyond that, any changes you want to see in the way it's implemented will need to be entered as feature requests in the Feedback forum.

See "Replace Synth": https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Browser.11.html

No, Cakewalk has no tools to track down a specific plugin's contribution to a dropout. But it's likely that no single FX is causing the problem; it's the total load exceeding the CPU's ability to keep the audio buffer filled at the current buffer size. There should be a dropout code that you can check here: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.22.html Depending on what you find, you might also want to double-check DPC latency which may have been affected by new drivers being used. https://www.resplendence.com/latencymon

No, I was wrong about that. Larry straightened me out. Buying with JamPoints does not invalidate license transfer.

Cool. Thanks, Matthew.

I'll probably download it all over a few days while working, but not try to install everything at once. I'll install one or two pieces a week, and it'll be like Christmas all year long. ;^) If I'm lucky, they'll release an installer before I'm done.

Ah, yes, I can. I had not clicked on the license button. Perfect! Muchas gracias, Larry. Made my day. ?

In a perfect world, I would not have bought Modo Bass just two weeks ago, and everything in the package would be new to me because I'd be crossgrading from AmpliTube Leslie... but this is still a slammin' I deal can't pass up. Had hoped to transfer MODO Bass to my son-in-law as a gift, but bought it with JamPoints, so no-go, I guess. Really bites to have copies of things you can't even give away. Will really have to quit watching the Deals forum after this, though. After years of spending very little on new music gear or software, I've shelled out for quite a few deals in the last month or two. And it will take many more months to get to know it all even skin deep. Everything was on the order of 60-80% off even the usual discounted 'street' prices, though, so I'm pretty psyched to have gotten so much for so little. Thanks to all for taking the time to share, and especially Larry of course. Over and out. No, really, I mean it. Seriously, I have plugins to learn, and music to make, and fellow musicians to help. And I still have a day job (thankfully). So that's it. I'm gone. For good... 'til tomorrow, at least.

I don't have that update. I take it you had similar audio performance issues...?

Open the Console View, and pull the bus pane divider to the left. Then pull the additional pane divider at the far right back to reveal the hardware output bus to confirm you have signal there also. And hover over the abbreviated name to see the full name and confirm it's going to the ouput you're monitoring.

ThreadSchedulingModel=2 is recommended for quad cores and above. You should use that even if it makes no difference in this case. What sample rate are you running? TTS-1 supports only 44.1, 48 and 96 kHz, and at 96, you have to enable Light Load Mode in System > Options. You should definitely check your DPC latency. Spikes to 50% and above in a light to moderate project (in terms of plugin load) with buffer at 128 sounds high even for that older CPU. Always good to know, what 'normal' is in your system for future reference even if this issue turns out to be TTS-1-specific.

Something made the click volume decrease as well. Possibly it was delivered to you with a fade already applied - maybe specifically intended to obscure the click. EDIT: Nulling out the click could be made a lot easier by having a copy of the raw .WAV file with the click running out further.

Yeah, it's both - natural sustain decay with a volume fade on top of that. You can see the clicks fading in this screenshot of the waveform with scale maximized:

Got De-Click working without crashing. It helps but leaves behind the room sound of the click. Also tried inverting the click from a near silent section at the end with the guitar gated out per Lars' approach. As he said, it worked well in that area, but a fade has been applied to the click along with the guitar so the level is wrong for nulling in earlier areas. And it's a challenge to get the sample-accurate alignment you need to null. Figured out the click is at 149 BPM, but still had nudge each copy by a few samples. Not happy enough with any of my results to share anything. If Lars can make it work, he's your guy. ;^)

Well we're of to an inauspicious start, but there's hope! My Izotope suite has a 'De-Click' tool that looks like it might do the job, but it just crashed Cakewalk on a test fade+click clip I created! If I can get around the crash, I'll try it on your track.