Hey,
unfortunately it was the oposit for me. On 15.0.10 a heavy project was still running stable enough and with the new version Cubase would always freeze completely after a minute or so. Tried rebooting, deactivating WiFi and so on - no luck. Had to go back to the previous version where that same project runs fine 
Software can be weird. 
Mine still isn’t perfect on heavy projects, but it is much better than 15.0.10.
I love the newly added visibility for which plugin is currently checked at the startup.
For long I thought that it’s EW Play that is (slightly) slowing the startup for me but it’s actually Waves.
Such a small thing but it makes me happy 
I wonder what they’re preparing for C16 if they decided to give such a major feature as the folder-groups in a minor update. I hope it’s gonna be what I think it’s gonna be 
@battleangel Are you referring to the VSTScannermaster file when you are talking about visibility of plugins being checked during launch? I thought that was introduced in C14 but I’m not sure. Or is it something else that I might have missed…
It didn’t show me every single plugin up until this version. Or maybe it was so fast that I couldn’t see and 15.0.20 slowed down with Waves? Hmm… It’s also possible. I’ll have to check C14 which I still keep “just in case”.
@battleangel I’ve not paid close enough attention with Cubase, but in Ableton Live when new plugins are found that tends to slow down the plugin scanning portion of the load screen. Even an update to an existing plugin will slow down and be “readable” for a moment. Then it goes back to blasting through them faster than my eyes can keep up. Any chance this could explain what you’re seeing?
Ah, I understand. In this case you might want to check the VSTScannermaster thingy. It’s a really cool feature that let’s you know in realtime which plugins are scanned and how long it takes/took.
On Windows, you’ll find the file here:
C:\Users\Username\AppData\Roaming\Steinberg
and search for “VSTScannermaster”.
@H20nly No need for Six Million Dollar Man eyes using that log file
Not really. Except if Cubase now sees Waves plugins as new every single launch. This is also possible.
But then, I didn’t saw it in 15.0.10 and before. It was just jumping to the other checkups after staying for a while on “checking plugins” or whatever was the text presented. Now I see plugin numbers going up while checking each waveshell.
Don’t tell me that I praised bug as a feature lol
Lmao 
I just take a look and Cubase 14.0.32 has only “Initializing: Scanning VST 3 Plug-ins…”, no details showing each scanned plugin (or waveshell). I can’t test 15.0.10 anymore but I’m pretty sure that I would spot the difference the same way I spotted it in 15.0.20 
So I’m going back to praise the new feature. It’s new at least for me 
Bug Report: Multitimbral MIDI Track Routing broken after 15.0.20 update
System: Cubase 15 Pro, Version 15.0.20 Build 320, Windows 11 latest release
Description:
After installing the 15.0.20 maintenance update, multitimbral setups using a combination of one Instrument Track and additional MIDI tracks (all pointing to the same HALion Sonic / HALion 7 instance) are broken in the Project window.
Symptoms:
MIDI tracks 2–4 display “Off” (“Aus”) in the track header instead of the correct output assignment
The keyboard icon in the Inspector (which normally opens the assigned VST instrument) no longer works on these MIDI tracks — only the channel editor (e) can be opened
Changing the slot assignment inside HALion Sonic has no effect on the routing shown in the track header
The MIDI monitor shows no incoming events when triggering notes via the Virtual Keyboard (Ctrl+K), yet audio is still being produced
All audio from MIDI tracks 2–4 appears to be incorrectly routed to Slot 1 regardless of the MIDI channel setting
Important: This issue is fully reproducible in previously saved and completed projects that worked correctly before the update. It is not a project corruption issue.
Steps to reproduce:
Create an Instrument Track with HALion Sonic or HALion 7
Load different sounds into Slots 1–4…or even more
Add three additional MIDI tracks, route each to the same HALion instance on channels 2, 3 and 4
Save, close and reopen the project
→ MIDI tracks 2–4 show “Off” in the track header, keyboard icon in the inspector is non-functional
Expected behavior: All four tracks should display their correct output routing and the keyboard icon should open the shared HALion instance.
This is a major misbehave and it distresses not only my new projects but also all them I have finished so far!
Since I was ever happy with Steinberg I guess they will fix it asap!
Thnx in advance
josh
I don’t seem to have that problem, everything working. did you check with other people if this is really a bug?
Does that happen with projects that I create in 15.0.20 or do I need to create the projects in an older version of Cubase?
Edit: Tested it by creating a project in Cubase 12, then loading it in Cubase 15. No issues.
___Test_MultiTimbral.cpr (284.8 KB)
No issues here in 15.0.20 either (using @Johnny_Moneto ‘s project).
Unfortunately, Folders changed to ‘Folders with Group Channel’ are still drifting to the Mixer’s Right Zone in my template. I thought that I fixed it by disabling and enabling ‘Group Folders’ again, but after a few days, it reverted again to the right zone.
What’s interesting is that only some of them do that while other don’t. Hocus pocus abra cadabra! It’s the magic! 
If you figure out a reroducable way… there seem to be quite a few lads and ladies around here who would love to get the groups into the right zone.
Dear Forum,
thanks so far for your experiences. I have tried a few things and here are my results:
downgrade from 15.0.20 to 15.0.10 → the problem still remains
reinstall version 15.0.20
deleted all my Halion Sonic Instrument and Midi tracks
purged the VSTi Inspector from Halion Sonic Instance
saved this as a new Cubase template
reloaded the new template and inserted a new Halion Sonic Instance as a Track Instrument in the VSTi Inspector
create a new instrument midi track with the b4 loaded Halion Sonic
added 3 more midi tracks (numbered 02,03,04) and routed them to HAL Slot 02, 03, 04 (01 is reserved for the instrument midi track on midi channel 01)
activate for each instrument and midi track different Halion Outs (01-04)
loaded different Instruments in Halion Slots 01-04
Conclusion after reinstalling the 15.0.20 Update:
So I guess all the trouble I discovered yesterday was some kinda installation glitch-thing. By falling back to the previous version 15.0.10 and the reinstalled the 15.0.20 fixes the faulty behave I described before. Thnx for all your replies, but I guess we should close this thread now.
thank you all
josh
That is commendably patient and detailed problem solving 
Steve
hi
Try Direct routing , then click “summing mode” that should work nice for you .
Cheers
T
Be aware, Direct Routing/Summing Mode kills direct outputs at export.