scook

Better than deleting the thread as it may help some one else later on.

The only CbB specific add-on is the Theme Editor. It is necessary if you plan on modifying themes. Otherwise, everything else is included with Platinum.

V-Vocal is one of the plug-ins made in Japan by Roland. The plug-in was not part of the sale to Gibson so, Cakewalk could not include the plug-in with newer versions of their DAW. It was replaced by Melodyne in X3 when Cakewalk added VST3 and ARA support. V-Vocal is still supported, however; to maintain backward compatibility.

V-Vocal is a special DX plug-in. To install from X2 requires at least a minimal installation using the advanced install option like this

AFAIK, automation works the same for instrument and audio+MIDI tracks driving soft synths. When using audio+MIDI tracks it is possible to control where the automation for the plug-in appears using the drop down under "Display Automation On:" near the bottom of the Insert Soft Synth Options dialog.

Does adjusting Time+ slider on the inspector for the instrument MIDI tab or MIDI track help (lower slider pointed to by Q)? Image source: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Inspectors.3.html#1220713

It is a collection of Reaktor Blocks. Blocks were introduced in Reaktor 6. They work like modules in other software modular synths. A block usually performs a single function such as an oscillator, filter or sequencer.

The Music Creator series was based on SONAR code. The project files made in MC5 are similar to SONAR 8. The issues moving from MC5 to CbB are CbB requires 64bit Win7 or newer. It works best on Win10. CbB does run on 32bit Windows. CbB requires an internet connection to activate the software. MC5 is a 32bit DAW. Any projects containing 32bit DX plug-ins may load without those plug-ins unless there are 64bit DX versions installed. The minimum requirements for CbB are listed on this page

Assuming the track/bus headers are expanded enough to see all the controls, I suppose one could create a custom track control setting suppressing the MSR buttons. All the factory track control settings show the waveform preview on the buses and synth audio tracks. In the image below, the track control is the drop down in the red box

Each dimension must be greater than or equal to its minimum. The minimum required height is 800.

Waveform preview is available on buses and synth audio tracks only. These tracks have waveform preview instead of input echo.

To route audio to another track takes a patch point (or aux track) but then the track must be recorded to see the effected waveform. A bus with waveform preview enabled will show the effected waveform without actually recording the track. Both of these solutions work in real time. The fastest way is bounce the track with fast bounce enabled.

Is ripple edit enabled?

To be clear 1040-A and 1040-EZ are not used this year according to https://www.irs.gov/forms-pubs/about-form-1040 The Form 1040 link on the same page is for a two page pdf. The first page is in the OP.

Sorry I cannot reproduce the problem using CbB 2019-03 build 20. When I create a project template the active tab in the inspector is stored in the template. If no tab is specified the inspector opens which the channel strips displayed. IOW, a project created from the template shows the inspector as it was saved in the template. Are the templates stored in the default template folder? Do they overwrite existing factory templates?

This does not meet the minimum recommended for CbB of 1280x800

IDK, if it is simpler. I had to provide the same info as last year just on different schedules. I have not been able to use the short form in years though.

AFAIK, that is the full first page of form 1040. I just grabbed a copy of f1040.pdf from irs.gov and it agrees with what I filed earlier this month. Page one looks just like the image posted. The forms changed quite a bit this year. For example, line 6 references a new Schedule 1. There are now 6 numbered schedules that hold details that used to be on form 1040.

An account was required to get the registration code for SONAR 8. The requirement started in 2005.

This only exercises the plug-in and its audio output. A better test is the virtual MIDI keyboard in the DAW. At least it sends MIDI data from a "device" to the synth. Still the virtual MIDI keyboard does not rely on TTSSEQ.ini so probably would have worked just like the plug-in keyboard. The actual cause is not known. At least, I do not recall anyone being able to reproduce the problem. There may be multiple conditions that cause the problem. The symptom, while rare, has been described well before Win10 and resetting the ini is a frequent suggestion.

Both DAWs use similar methods to discover and communicate with MIDI devices. It is not just your computer. The symptom has been described before on different HW/SW combinations. But the failure does not appear to be easily reproduced. The suggestion to reset the ini file comes from a review of similar threads.

I am guessing the MIDI I/O activity is showing up in the icon in the Windows taskbar. Do synth play with using the virtual controller? Is the keyboard also used as a control surface?

Try renaming TTSSEQ.ini in the CbB and SONAR user folders in appdata.

The colors and icons used in the plug-in browser depend on the theme. Pretty sure the significance of the colors used in the browser are not documented for this reason. There was a similar thread a couple of months ago The colors in that thread were for a different theme.

It is difficult from the OP to know if the user is reporting actual audio drop outs (usually accompanied with a message from the DAW or the audio engine is shutting down) or some MIDI data not being played. Providing a little more info may help such as, the name of the failing plug-in, project sample rate and ASIO buffer settings, OS and details about the PC hardware.