Olaf

https://app.slatedigital.com/academy/courses/744623/ultimate-guide-to-synthesizers Enjoy!

Thanks, man! I have about 90 plugins inserted in the project. Could that be it?

Can you try to see if they work in a crowded project? After happily reporting it working, I still get the same problem. They open up fine in an empty project, but the problems appear when the project is already CPU heavy - around 50%, in my case. I usually manage to insert an instance of each - eq and compressor - sometimes it opens well, sometimes it doesn't - but never a second one, without having the visualization problem. Sometimes even the first ones that I've inserted won't visualize on open - and may crash CW. They work, musically, I can hear the impact on the track, but can't visualize and crash.

No, it's the 1.1.7. Normally it doesn't make any problems. I tried to open it, I think it was with the playback on, I'm not sure.

Haven't tried it, it's deactivated to avoid conflicts. Usually TH-U doesn't make any problems, this was the first time in a while. Do you have any similar problems?

Good idea, since I've noted that some settings are saved if you save them in the Track View, but not if you save in the Console view (like the collapsed states of the one knob PC modules on Instrument tracks, Show velocity on MIDI clips in Notes mode, etc.). So I've tried it. Now the Midnight compressor couldn't open either - so neither of them. It crashed Cakewalk a couple of times - the first time the blank VST was open, the Aim Assist time was frozen somewhere on the ruler, but the cursor could move, but without the Aim Assist time, and after a few seconds CW closed, before I could take a snapshot. I tried it in Reason, it worked. So I reinstalled over the old ones, opened an empty project in Cakewalk, they both worked, opened both in Console and in Track. So I reopened my project again, and now they both work. ??? It's like the Twilight Zone. Given the blank frame and the freeze, I think it's conflicting with the graphics somewhere - could be DirectX, or the VC++ redist packages, it's what I can think of, I'm no programmer. Reinstalled the packages a few times, used the latest in various configurations, no change. I had noted some things along the same lines before - screen going black, sometimes losing the settings on the control bar - position, collapsed modules, etc. In addition, resetting some plugins - just reset all my Softube Tapes again, this is maddening. Gotta reload them all. If I don't lose them at least once a night, I haven't worked long enough. Mostly when I play with the cursor position or the set loop during playback, so I always make sure to stop the playback, but often it does it anyway. I've had crashes moving the cursor line during playback, or clicking on an automation envelope. Or changing the preferences while playback was on.

TH-U opened up on no preset loaded.

Hi guys, Bug The Focusrite ISA Midnight EQ 1.7 (VST2) does not display at all. The Midnight Compressor works fine - they're a bundle, installed and activated at once.

I guess you're right, I only use two at once - measures, and time - so that would make two rows of information, which fits just fine. But I'm sure a workaround can be found. For instance, even it spills in the empty space of the context menu bar, above, that wouldn't probably hinder, since there's nothing there - and even if it were, positioning the mouse directly on that bar hides the aim assist time anyway, so you can hit anything without a problem.

Crashes for tonight: 4, so far - 3 trying to change the ASIO latency - 2 in the pics, one closed without warning - 1 trying to save while playing, again, closed without warning. On my Creative Audigy 2 ZS - 24 Bit (seen by CW as 16 Bit), 48 KHz.

New problem that I've encountered in the 2020.04 - EA1 and still persists in EA2: - Project saved with the Browser and Synth Rack windows docked at bottom (since they are not accessible in the Console view). On open, the project initially displays the saved configuration, Console view, with the 2 windows docked at bottom, then a rectangle flickers in the left upper corner of the screen (over the title bar) - shortly and blank, cannot visualize it - and all the docked windows disappear, are reset to default setting (docked at right, for Track view only), then the program automatically docks to bottom a Multitrack Piano Roll window, and it opens to it. Problems existing in previous versions: - New plugin that randomly gets reset to the default settings, on various operations - mainly transport and set play loop related: Konsol (by Analog Obsession, VST3, 64 Bit). It adds to Softube Tape (again, VST3, 64 Bit). If you can find the common instruction that resets these two plugins - in all or just some of their instances, the behavior varies, don't know according to what - Cakewalk randomly sends that instruction when you play with the loop points or transport bar, and it's a bitch. Unless saved, they're lost for good, and even if saved, have to manually reload them for many instances, several times a session. Sometimes I don't even realize they're reset, and all my subsequent mix choices on the track are null and void, and have to be redone on reloading the right setting. A BITCH. - Cakewalk does not remember the following saved settings for a project, and resets them on reopen: - Show Aim Assist Time (additional question: why not place the time display rectangle ABOVE the ruler in the Navigation Bar, on the free space of the contextual menu? This new Show/Hide option is well intended, but doesn't solve the problem: either you have no time assist (defeats the purpose) or, if you use it, you have the same problem you had before the option was implemented - it covers the navigation bar ruler. Why not change the display position, and you won't need any check option at all?) - Hide velocity on MIDI clips in Note mode - Hide Navigator in Track view - One knob PC modules collapsed states on instrument tracks (not for audio tracks), IF SAVED IN CONSOLE VIEW (if saved in Track view, no problem). - The Wet Only ON state on the Nasty DLA (Variety of Sound) plugin (on Send buses) - The presets loaded on Roland Juno 106, and on Slate Digital SSD 5.5. So I have to redo all these operations on each project open before starting work - again, a bitch. - Deleting an automated PC module does not delete the automation envelope. - Reassigning an automation envelope from the drop down menu does not reassign envelope but creates a new envelope for the new selection. Windows 10 machine here. Looking for good news, guys. Take care and good luck!

@Jim Fogle Hey, Jim, I've seen that you've proposed the polls to allow comments, to discuss any suggestions in them. Why not discuss them here? That's why I posted this.

Three of the old ones, listed separately.

Hi guys, Vote if you think these options would be useful.

Guys, I've just come up with some new ideas (in addition to the 75) ?. ??? Don't kill me just yet, you can check them out here first.

Quick display buttons in the Console View. Since they will be on the already existing Console Menu Bar, they will not take any additional Console screen space. See pic below for reference. 1. Show/hide (expand/collapse) Browser Window (docked/undocked according to its default setting), for quick FX insert drag & drop onto Tracks. Saves the additional Workspace/window flipping necessary to access the Browser when you're in the Console view (pretty much most of time during mixing, for me), or the time consuming navigating through the right-click Insert FX menu - BUTTON 3. 2. Show/hide (expand/collapse) Buses. Avoids the manual dragging of the Buses pane to the right size, and then redragging it back to fit the initial size (minute, takes attention and time). This way we'll have the options of two clicks, faster, opening/closing instantly and exactly to size, instead of two precision drags across the screen - BUTTON 2. 3. Show/hide (expand/collapse) Master Bus. Does the exact same thing for the Master Bus. Again, avoids precisely and carefully dragging and aligning to the exact size - BUTTON 3. 4. Show/hide (expand/collapse) Sends/Bank/Patch modules. Shortcut to open the Sends without going though through the contextual menu - BUTTON 4. To clarify, I'm not suggesting that any existing options be removed, just the open/close to size simplification buttons added. No feature lost, just some additional options for quicker access. Looking forward to your votes.

Bugs that I've found (they also existed on the older releases): - One-knob PC modules saved as collapsed open up expanded, on project reopen (the collapsed state is not saved), if the project is saved in the Console view. This does not happen if the project is saved in the Track View. - A PC module parameter automation (for instance, Tube Saturation Output volume) envelope still subsists, unassigned, if the module is deleted - and cannot be subsequently deleted until the module is reloaded. - The automation envelope assign drop-down menu, in automation lanes, creates new envelope when a different target parameter is selected, instead of reassigning the envelope to new selection. - MIDI clips displayed in Notes mode do not remember the MIDI>Show Velocity UNCHECKED option, on project reopen. - Softube Tape VSTs reset all settings to default if the Loop On/Off button (Control Bar) is switched ON/OFF, or if the “Go To End” or “Go To Start” transport buttons are clicked during playback, in the Console View. All settings need to be reloaded from presets, to be able to continue. If the settings are not saved as presets, for each modification, they may be lost. I can’t seem to replicate the reset, no matter the “abuse”, in the Track View. - Nasty DLA VST does not remember “wet only ON” state, on project reopen. - Steven Slate Drums 5 (Free) does not remember the kit preset selection, on project reopen – always opens up to the default kit - don’t know if this is a bug, or a limitation of the free version, but normally it should remember the saved project kit, on load. - Sometimes the same happens for the Roland Juno-106 VST synth – the saved preset is not loaded on project open – unlike SSD5, it DISPLAYS the saved preset selection in the preset box, but it only plays a sine wave (does not load it). This happens occasionally. - Console Emulations sometimes stop working on tracks (mute audio, needle not moving) – they need to be replaced, or removed and readded to restart working. Maybe these could provide some insight into the bigger crash issues - the Softube Tape is sensitive to crashes on load or at various times during mixing, especially when PC module states are modified. PC modules can also cause crashes on my system (Win 10), on module state changes (remove, collapse, rearranging). They happen rarely, but sometimes do. Cheerios! Thanks for the update.

This is some serious stuff!! Great update. The best one since I've been on board. I don't think I've waited for one more eagerly than these days. I love the arranger. And am stoked about seeing my idea implemented, for the PC module settings copy/paste - and also the drag & drop. I would implement it with clicking anywhere on the module except the active knobs/buttons, but still a great addition. Why not carry the idea through all the way, though? Drag & drop in empty area of a PC creates new instance of the module, with the current setting. And also replicating the behavior for FX modules - drag & drop on same type plugin rectangle pastes the settings. Also, copy and paste option available on right click on the FX module rectangle. Another idea from my long list that I would like to see available more quickly - the possibility to open instruments from the console, by left-click on the instrument track icon - leave the icon change for right click - because we need to open the instruments a lot more often, in the mix, than we need to change icons - and having to flip through different windows for that is time consuming, and a little off putting. Also, make the plugin browser bar (or just the double arrow button, to save console work space) available & expandable in the console view, for instant FX inserts drag & drop, in addition to the lengthy right-click menu selection. I'll stop here, cause I'll go into all of them. Great work, guys. Glad to see someone's listening. I know you're working on the crashes and bugs, too, which is very much needed. Take care.

@Jim Fogle@chuckebaby Hey guys! I've put up the first questions for the polls, if you want to vote on them. You can find them here: and Everyone else is obviously also welcome to vote.

Hi, guys! I'd like to propose a list of additional options and simplifications to the Cakewalk workflow, and would like to see how many people would welcome the simplifications. Vote below if you want them. You can also check the first part(s) for more options and context. This one is about: - new options to also work with/open Instruments in the Console View. - undo options.

Hi, guys! I'd like to propose a list of additional options and simplifications to the Cakewalk workflow, and would like to see how many people would welcome the simplifications. Vote below if you want them. This first part is about: - the possibility to also create/adjust soft synths from the Console View.

@Jim Fogle No problem. I'll give you a sign when I've posted the first one.

@Jim Fogle I think I'll break it down in smaller chunks, of 10 or so, so people don't get discouraged by it being too long. Need to find the time to choose/start with the things that will be the biggest gain in the short run. Any preferences?

You're right about that, and every time there's a disagreement - or even misunderstanding - the first reflex is to put somebody down or insult, which effectively makes any longer term relationship impossible, since disagreement between any two people is, at some point, inevitable. I think it's a good idea, and I'll try it. Thanks for the suggestion ??.

Hi, Jim! I understand what you're saying, but think about posting - at this point - 76 different posts, and then talking separately on all 76 of them. It would mean flooding the forum, which I wanted to avoid, one, and then, generate endless discussions about all of them - cause you know how those can get. Plus, I thought about having a centralized document for changes. My initial idea was not to go into debate for each, but put them out there, on a list, so that people can vote in the way of "hm, I would to see this, that, and that, this and the other may be helpful, and don't want this, that, and that", so that we can get a notion of those that will be the most requested, to bring them forward to the attention of Bandlab. A sort of simple voting. That doesn't mean we can't talk about them or have alternative suggestions - if there's better ideas on how to simplify some operations, why not - I mean, that's the idea. So feel free to ask. It'd be nice to talk about the actual suggestions, instead of judgments over intentions, for a change. You've actually given me an idea. I'm noing to number them, instead of the bullets, so that you, or anyone, can easily address 1, 5, 25, etc. Would that help?