scook

From the main CbB menu Help > Keyboard Shortcuts

Good It is a decent guitar to MIDI solution.

IIRC, the demo is standalone only. (I guess this has changed over the years) The full version also has a VST plug-in. The standalone will give you an idea of how responsive the software is to guitar and it will load synths so you can hear how it plays. To use the VST - Add MIDI Guitar 2 VST to the guitar track's FX rack, set "Enable MIDI output" on (see image below) and input echo on add a synth to the project using either an instrument or audio+MIDI pair and choose a preset set the instrument or MIDI track input to MIDI Guitar 2 and enable input echo play guitar

^^^This Make sure no MIDI output devices are selected in preferences. Open the MIDI file instead of importing. With no MIDI output device available, Cakewalk will automatically add TTS-1 to the project and configure it to play the MIDI file. Then one can add other plug-ins and audio tracks to the project and change the MIDI tracks outputs to the new plug-ins.

Try MIDI Guitar 2 by Jam Origin

I see T1 is muted. When comping the lanes should not be muted, the clip(s) need to be muted.

It just means the take lane is physically larger on the screen not that the clip is louder. It is possible to drag the lane to make it even larger but this does not increase the clip volume.

The take lane track is the original track. I made the take lane taller than the parent track. There is no volume difference between the parent track and take 1. The levels do not change between a parent track and a take lane.

Clicks can happen when an audio clip is spit any where but a zero crossing. This is discussed in the last paragraph here. Slightly fading the clip should eliminate the click.

After a quiet spell, recently I have received a few emails from support on the PC module issue. Earlier today they asked about the new release and I suggested they follow this thread. Support is going back to the devs. Maybe this will get fixed some time in the future. Until then, the pre-2.4.96 installers are the only recourse for PC modules.

All tracks have one or more takes. What I proposed is adding a second take of room sound and comping between the performance and the room sound track. Comping occurs in the take lanes. The results are displayed in the track. Always work with a copies until the method is clear. Even then, I would work with a copy and saving the original tracks just in case. Try the steps described in the experiment using the smart tool or the comping tool Comping is non-destructive. Flattening merges the comped tracks into a new take lane muting the other take lanes. Note: this does not affect the comped clips because comping mutes clips not lanes. So the original comped takes are still there and intact. It is very much like pasting but takes less clicks as the "pasting" happens when the selection is made.

These are not instruments. They are instrument definition files use for communicating between the actual hardware synths the DAW.

You actually have two takes, the narration and the room sound Here is a small video showing how to replace parts of one clip with another. It consist of the parent track, a take lane with the "room clip" (which is muted) and another with the actual performance. The lanes are zoomed in quite a bit but could be zoomed more. Then I replace part of the performance with silence from the muted clip using comping. Then notice how one can progressively replace one clip with another to fine tune between the two. The result of comping the two is shown in the parent track.

Yes, I understand. Comping will do this by allowing you to replace one part of a clip with another As an experiment create a track open the take lanes copy a narration clip into the lane add another lane and copy the room sound into another muting the clip try comping between the two

Could add the room sound as muted clip(s) into a second take lane and use comping to replace the unwanted sounds in the narration lane with the room sound or use volume automation between two tracks

Users cannot delete posts. If whatever is posted is a real problem, let a mod know and they will help.

It is still in the thread The default sort order of the Q&A section is by likes NOT by date. The sort option is on the right just below the question post. At least that is where the option is located in the default PC browser theme.

Yeah I misread your post.

Really? I just updated to v2.1.3 from https://tal-software.com/products/tal-vocoder The website shows v2.1.2 but the plug-ins reports v2.1.3 and it has "Enable MIDI Out" disabled MIDI Out is not needed for the vocoder. It uses MIDI data to control the plug-in but does not have to generate or pass through MIDI data.

Yeah, now that you mention it, the vocoder only has a "MIDI in" option but it is off by default too. The link discusses MIDI output but the idea is similar. The MIDI I/O options on the standard header VST drop down control whether a plug-in shows up in MIDI input and output drop downs. Effects and synths have different defaults for these options.

IIRC, TAL Vocoder scans as an effect so use option 2

The delay is the result of buffering audio playback. There are two ways to reduce this buffering: Lower the audio interface buffer size - this is set using the buffer size slider in preferences or the ASIO client software supplied by the interface manufacturer. Reduce plug-in delay compensation - some plug-in need time to process. To see if PDC is affecting the project click the FX button in the Mix module to turn off all plug-ins. If there is a noticeable difference - one or more plug-ins in the project are the cause. Either replace, bypass or remove the offending plug-ins. While reading about the Mix module and FX button read the PDC button section too.

If clicking on the drums in the SI-Drums UI and playing MIDI through the plug-in do not make any sound, the plug-in may not have an audio track associated with it. IOW, the plug-in was added with only a MIDI track. Synths need either a simple instrument track or an audio+MIDI track pair for a complete routing. Try adding an audio track to the project and set the input drop down of the audio track to the SI-Drums stereo output.

There are several differences between the image in the OP and the second image including, snap settings, the sample rate and record bit depth. There is no way to tell if the image showing the project sample rate at 96k is because there is an audio clip in the project at 96k or the preference setting was just changed and not applied If a new project does not use the new project sample rate from preferences, the template used to create the project contains one or more references to 96k audio clips. Changing the record bit depth does not affect a project's sample rate.

The transport shows the sample rate and record bit depth that will be used when recording the project that is loaded. The sample rate is read from a clip header in the project. The record bit depth is read from preferences. The yellow arrow points to the default sample rate that will be used in a new project and existing projects that do not have any audio clips. Red Book CDs use 44.1 kHz 16bit. But the format of the final product has little bearing on how the DAW should be set up.