scook

SEM was added at the same price as the 8 voice standalone No extra discounts from Cherry Audio AFAIK

Sure instrument tracks freeze fine. Just like an audio+MIDI pair, there must be MIDI in the track to freeze. If the MIDI clips are inside Superior Drummer 3 the track cannot be frozen because there is no data for the DAW to freeze. Drag the clips out of SD3 into the instrument track then freeze.

You may use any of the algorithms provided to render AudioSnap clips. The offline algorithms tend to be better quality but there is a setting to use the online setting. Here is the preference page covering stretch options options http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B19 There is a little information about each algorithm there.

Freeze and bounce by themselves do not use audiosnap. AudioSnap is designed to change the length of audio. This is why it must be rendered using one of the stretching algorithms. It is not possible to play AudioSnap processed clips or render the clips without using an algorithm to handle the stretch.

Why is audiosnap involved? The audio rendered from SD3 comes from MIDI and should not need to be processed through audiosnap. AudioSnap is primarily designed for recorded audio. Timing issues in SD3 may be fixed in MIDI.

Do not have the device but just read a few pages about it here https://www.alesis.com/products/view/multimix-4-usb-fx Often Alesis gear did not have factory ASIO drivers. The Alesis Multimix 4 is a mixer with a USB port. Like most mixers, the computer connection is 2 channel. From the features section: The image in the OP shows what one would expect from a stereo interface Left 1 = channel 1 from the interface Right 1 = channel 2 from the interface Stereo = both channels 1&2 from the interface

Regular freeze and bounce do not rely on stretch algorithms like AudioSnap. Freeze and bounce render audio just like the export process.

Is a per-plug-in setting. The plug-ins must be enabled in order for the 2x button in the transport module to have any effect. The upsample settings are in the upper left window decoration above the plug-in UI. FWIW, I wrote a tool to manage CbB upsample settings. Use either the built-in plug-in or CbB upsample settings. Do not use both on the same plug-in.

SF upgrades have always been expensive. I was pleasantly surprised when Humble Bundle offered SF12 Pro for $20 (with a bunch of other stuff). Eagerly awaiting their next SF Pro deal. Most of what I used SF for is now handled by iZotope RX7 but still occasionally use SF.

Yeah, I recall that from when the first version of Tools Editor was developed. IIRC, old versions of Audacity worked, newer versions (around the time of that post) did not. Since that time no one has reported success using Audacity. Just because no one has reported success is not the final word on the subject. Of course, this has nothing to do with the tool I wrote. The object of my exercise was to provide a better way to add entries to the tools section of the Utility menu. SONAR/Cakewalk are launching the program and passing the arguments. I have yet to read about an audio editor failing to run properly when setup according the information provided by Cakewalk.

Audacity is a DAW. DAWs are designed to work with projects containing multiple audio files so they are not setup to take a single wav file as an argument on their command line. Some DAWs have extensive audio editing features but they are intended to be called from inside the DAW, Audio editors are designed to work with individual files. As a result, it it common for them to support adding a wav file to their command line. There are plenty of no cost and low cost audio editors.

Are you sure about this? I don't use AUDACITY but AFAIK it does not support passing wav files on the command line. At least no one using AUDACITY has ever report successfully using a newer version of it as a WaveEditor in SONAR/CbB. Without command line support, there is no convenient way to pass data between CbB and another program using the CbB WaveEditor feature.

that thread and Noel's replies in a similar thread resulted in my developing Tools Editor. available on my Google page a new version of it and the rest of the tools should be out soon

ARA is not at play here. The plug-in is instantiated the old way before Region FX. I would have to experiment with Melodyne in the FX rack to see what is possible. The standard advice is bounce Melodyne clips ASAP. Melodyne is not intended to be left in a project like a regular effect.

More info about Snap Offset from the clip inspector help

Envelopes are the visual representation of automation used to control various aspects of the data and performance in the DAW. There is a large amount of information in the documentation about automation and how to use envelopes. There is even a glossary of terms in the documentation. For example, I am sure there are quite a few videos on the subject too. Youtube is pretty good resource for them.

It is still there and in the documentation. When documented features appear to be missing, the first thing to check is the Workspace setting. If the Workspace is OK review the click behavior settings in the Track View options menu for audio clip double-click

The 3 synths I don't have are $653 retail I already own the full version of MSoundFactory. The three synths I get with the upgrade are MDrummer, MPowerSynth and MSoundFactoryLE. Not sure what I would do with MSoundFactoryLE or why it is even mentioned in the upgrade offer. MComplete did not exist when I bought the MTotalBundle.

Is CBSProductsInfo.dll a VST plug-in? It does not sound like one. The scanner should only be used with folders containing VST plug-ins. Scanning random dlls can be a problem. May want to review the scan path in preferences.

A novel bit of reasoning

Yes, price is part of discount computation. This is why my upgrade to the MComplete bundle is $547. For $547, I get MDrummer, MPowerSynth and MSoundFactoryLE and any thing else they may add at a future date (assuming they do not add another tier above MComplete). When I purchased MTotalBundle, there was no MComplete and the only synth was MDrummer and the lite version of MDrummer. Some time after releasing MPowerSynth, Melda renamed MTotalBundle to MTotalFXBundle and added MComplete.

Could this be related to your use of Melodyne in the FX rack? Remember, once a track is transferred into Melodyne, the audio originates from the plug-in NOT the clip in the track. As I noted in your original post..

You will either need to modify the split notes to tracks CAL to group pitches rather then placing them in individual tracks or duplicate the MIDI clips and delete/filter the unwanted data from each track. There are several of ways to delete ranges of notes such as selecting the notes on the keyboard then hitting the DELETE key in the PRV. Alternately filter each voice using the MIDI Event Filter MFX. Once a key range is defined, save it as a preset for future use. The filter may be left in the MFX rack or applied to destructively remove the unwanted data in the track. If you prefer to keep all the notes on one track and distribute them to other tracks route the MIDI track through a plug-in that will echo the data such as one of the Code FN42 plug-ins MIDIChFilter, NoteMapper or VeloScaler. Then use the FN42 plug-in as the input to the "voice" tracks. Add the MIDI Event Filters for each voice on the appropriate track. or use a drum map. A drum map may route each pitch or groups of pitches to a different synth.

Assuming the clip was transferred to Melodyne, the clip shown in the DAW is no longer the source of the audio. The audio is originating in Melodyne. Any processing happening before the Melodyne plug-in is ignored as I tried to explain here

Deselect "Enable MIDI Output if Available" in the Insert Soft Synths Options dialog