scook

MCompleteBundle did not exist in 2013. The drum synth was the only instrument at the time and it was sold separately. Bought Superior Drummer instead. I tried MPowerSynth (IIRC, there was a public beta) and passed on it too. Did pick up MSoundFactory when first released. Had a little referral money so got it pretty cheap. May get MPowerSynth someday but most of it is in MSoundFactory.

Yes and this can cause problems for new users because this option along with the "Always Echo Current MIDI Track" (which is enabled by default too) can cause MIDI data from one track to unexpectedly appear on other tracks. Especially confusing when users set instrument and MIDI track inputs to None.

Synths that can send MIDI have MIDI out is enabled by default. Effects that can send MIDI have MIDI out disabled by default.

I bought a license for the free bundled and the Convolution reverb then decided to save for the bundle. The list price in 2013 was about half was it is now. I paid ~$560 for the bundle. Every effect since then has been free. The downside is the cost to upgrade to the new complete bundle. It is more than what I paid for the bundle I have

Bundles are the best way to go I bought what is now called the MTotalFXBundle years ago. My cost is down to about $5 per plug-in with all the new plug-ins added to the bundle.

Another thing to consider - All plug-ins and bundles offer free updates for life If a plug-in is added to a bundle, owners of the bundle get the plug-in for free

https://www.meldaproduction.com/about/referral?presenter=Html

Historically, they have a 50% off bundles sale near the end of the year. All through the year, individual plug-ins are selected for 50% off sales too,

Click the orange button in the bottom left of the track This is the type of stuff I recommend trying and see what happens. Bouncing clips does not change the clip type. They are still MIDI clips. Bouncing clips does not change track settings so the track output remains unchanged. Bouncing clips has nothing to do with plug-in settings.

Bouncing clips is not the same as bouncing a track. Bouncing MIDI clips does not render them to audio. The image in the OP shows a parent track with 2 clips in different take lanes. Open the take lanes to see both clips. Bouncing the clips in the parent track merges the selected clips into one clip in a single take lane.

The PRV does not recognize take lanes. To show one take lane, temporarily mute the clips in the other take lanes and enable "Hide Muted Clips" in the PRV view menu.

Are you running 1920x1080 or 3840 x 2160 w/ scaling today?

Cakewalk stores MIDI info in TTSSEQ.ini in the user directory Rename or remove the file at it is rebuilt just like Aud.ini

Controller pane draw resolution is linked to the snap setting. Either turn snap off or use a smaller snap setting.

Yes Rendering applies the Melodyne corrections and removes the plug-in from the clip(s).

Best ask the studio what they want. You will likely need to export all the tracks out of the project. You should apply Region FX before export.

I run at 1920x1080 Does ProChannelStripPresetFolder in HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Core\UserPaths point to your PC preset folder?

The buttons were removed from X-series SONAR and re-introduced in CbB.

There is no risk to the original project when starting with a MIDI file created using "Save As". It is also often less work removing data from a MIDI file especially if the original project has tempo changes and markers. A project can be thought of as a MIDI file with proprietary extensions. When a project is saved as a MIDI file all the proprietary data is ignored and stripped out of the file.

There is data loss when copying out clips instead of saving a project as a MIDI file. Tempo, position on the timeline and marker data are not embedding in clips. Historically, the only "export" option was MIDI groove clip. The "Save As" MIDI file function in the export menu is relatively new. It has always been an option from the main menu Save option. There may come a time when "Save As" does something with archive and mute when exporting MIDI. In a regular project file these track states have meaning and are preserved when saving to a new name. They have no equivalent in the MIDI standard. Saving a "partial" MIDI file might be a useful new feature. MIDI files are small. Saving the whole thing and expecting the person receiving the file can figure out what to do with it is not a big ask. Currently, if the MIDI file must be pared down to a subset of the project's MIDI data (and still contain all the MIDI "project" data) it must be done by removing the unneeded MIDI data from the project.

Maybe a display scale issue

Project > Audio Files...

Yes, it is still a trial version. I believe it is not the same as the trial available from Celemony. The trial bundled with CbB will continue to perform monophonic audio-to-midi and drag--to-timeline tempo map after the trial period for the editor ends.

BA keeps track of what it installed using registry entries in HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk\Installers I did not install the bundled Melodyne so do not have the actual key to the Melodyne record. It should be pretty clear which is the Melodyne record based on the data. Delete the appropriate key and the Add-ons option will be available again.

IIRC, it is a +3db HF shelf starting around 4k