An option to expand/collapse all Pro-Channels in the console view :)
 
We already have options to widen/narrow all strips...
 
EDIT: I just learned from Craig Anderton's new book that you can hold down Ctrl when expanding a track's Pro-Channel to have all of them expand 

Also.. I'd like to be able to have a CWP open in 96KHz/24bit, and then open a MIDI file and not have it sound like absolute garbage
 
MIDI only plays correctly for me in 44KHz/16bit. Any other sample/bit rate and the sound is just distorted and unrecognisable.. Does anyone else get this?
 
I currently work around the problem by opening MIDI in a totally separate app (Sekaiju)

Hidden_Symmetry
Nested folders

+1 for this

andyjobson85
Also.. I'd like to be able to have a CWP open in 96KHz/24bit, and then open a MIDI file and not have it sound like absolute garbage
 
MIDI only plays correctly for me in 44KHz/16bit. Any other sample/bit rate and the sound is just distorted and unrecognisable.. Does anyone else get this?
 
I currently work around the problem by opening MIDI in a totally separate app (Sekaiju)

MIDI is a communication protocol, consisting of commands and is nothing to do with your sample rate or bit depth.
 
All that is stored within a MIDI track is what note you played, how loud you played it, and when you stopped playing it. It has other commands such as program change, aftertouch information, pitchbend, modulation etc.
 
However MIDI makes absolutely no sound whatsoever, all it does it tell a synth what notes to play.
 
If it's not playing correctly on a particular VSTi at 96Khz/24bit, then it's an issue with the VSTi, not with MIDI. 
 
A MIDI file will only sound as good as the synth its played through.
 

msmcleod
 
If it's not playing correctly on a particular VSTi at 96Khz/24bit, then it's an issue with the VSTi, not with MIDI. 
 
A MIDI file will only sound as good as the synth its played through.
 

 
I know what you mean about MIDI just being instructions. I've suspected for a while that it's some limitation with Cakwalk TTS-1.
 
It's a frustrating limitation as that's what's automatically loaded when you open a MIDI file, especially if you need to jump back and forth between a CWP and a reference MIDI

andyjobson85

msmcleod
 
If it's not playing correctly on a particular VSTi at 96Khz/24bit, then it's an issue with the VSTi, not with MIDI. 
 
A MIDI file will only sound as good as the synth its played through.
 

 
I know what you mean about MIDI just being instructions. I've suspected for a while that it's some limitation with Cakwalk TTS-1.
 
It's a frustrating limitation as that's what's automatically loaded when you open a MIDI file, especially if you need to jump back and forth between a CWP and a reference MIDI

One of the biggest pains with Cakewalk is that it doesn't send either bank select or sysex messages to VSTi's (such as TTS-1).
 
Program Change messages allow you to specify from a selection of 128 sounds (where 1 is Piano, 50 is strings etc)
 
Bank Select messages allow you to choose a different "bank" of 128 sounds, which for GS based MIDI files, will be variations on the 128 sounds in the default bank.
 
The TTS-1 is actually a pretty faithful reproduction of a Roland GS synth, but since it doesn't respond to Bank Select messages, some of the sounds it may be using might not be quite right.
 
The work around in TTS-1 is to manually select the required patch from the GUI, but it does require you to manually look up the equivalent sound for Bank nn / Program nn (and then remove the program/bank select messages from your MIDI track).
 
I personally use a Yamaha XG VSTi, which unfortunately has no GUI whatsoever for changing sounds and relies completely on Bank Select/Program Changes. The program changes go through fine, but the bank selects are ignored, meaning the sounds aren't the right variation in some cases.
 
Hosts such as Cantable handle the Bank Selects fine (albeit via a hardware MIDI port), but there's no way of then controlling the audio produced within Cakewalk apart from using some complicated combination of hardware midi ports, VB Cable and ASIO4ALL. It's far easier to just use an external sound module, which kinda defeats the purpose of having the VSTi in the first place.
 
Cakewalk should automatically upsample your TTS-1 to 96KHz/24 bit. It may be an up-sample configuration setting that is set wrong for this plugin, or it just doesn't support it.
 
I know that most 32bit bridged VSTi's do NOT support up sampling, but this is easily worked around by rendering (or freezing) the track and upsampling the rendered audio.
 

It would be nice if Sonar CbB could keep the configured GUI state between sessions - track height, synth view in browser, bus pane open/closed/height etc.

Peace on Earth, and Goodwill for all things under the sun, and under the rocks, and on the roll.

James Argo

Muziekschuur at home
rapid screen changes. And choice to use the numeric pad for screen changes

 
+1
For example, I hope I'll be able to change the value in transpose slider (MIDI track, inspector) with my numeric pad or + - button. It was possible in Sonar pre "skylight" versions. Now we stuck with mouse to change the value. And the tiny tiny slider interface made it difficult to slide precisely.
 
I hope there is an option to have many input interfaces (like buttons, slider or rotary knobs) to the track (in the track view) rather than in track inspector. Specially with MIDI tracks.
 
Thanks

100 %  agree that these would be major improvements. I think there is plenty of room in the track inspector if - we could minimize the appregiator and make use of the graphics space for a improved sliders