Cubase 9...oh god please no not daylight savings time

Audio Plugin Hosts and other audio software applications discussion
Locked New Topic
RELATED
PRODUCTS
Cubase Pro 15$579.99Buy

Post

thejonsolo wrote:And here we go again.....hours of VST scanning!!!!
So Steinberg STILL gave a flying F about the DST switch scan "feature"....

Am I looking forward to that end of the month (switch in Germany)...


chk071 wrote:So Cubase rescans the plugins, when the time is set back and forth?
If you "merely" set the time back and forth, Cubase usually ignores that. Some C/R bound plugins might not however ("demo period extension prevention" comes to mind)...

But since Cubase SX (or did that first happen with C4?), every time a Daylight Saving Time switch (Summer-Time to Winter-Time and back) happens, Cubase assumes "wait... there is something wrong - better flush the blacklist and whitelist and re-scan everything again?!".

And it's sadly not only Cubase - ALL Steinberg hosts do that at this point (Wavelab not until WL6 IIRC)



If your copy of Cubase LE or Artist doesn't do that - be happy for it!

For everyone else - I feel your pain!
[ Mix Challenge ] | [ Studio Page / Twitter ] | [ KVRmarks (see: metering tools) ]

Post

[quote="Hink"]personally I dont get the uproar over daylight savings time[quote]

Hink, he's SPECIFICALLY relating this to cubase and known issues. The other should be for different thread in off-topic.

Post

Compyfox wrote:
thejonsolo wrote:And here we go again.....hours of VST scanning!!!!
So Steinberg STILL gave a flying F about the DST switch scan "feature"....

Am I looking forward to that end of the month (switch in Germany)...


chk071 wrote:So Cubase rescans the plugins, when the time is set back and forth?
If you "merely" set the time back and forth, Cubase usually ignores that. Some C/R bound plugins might not however ("demo period extension prevention" comes to mind)...

But since Cubase SX (or did that first happen with C4?), every time a Daylight Saving Time switch (Summer-Time to Winter-Time and back) happens, Cubase assumes "wait... there is something wrong - better flush the blacklist and whitelist and re-scan everything again?!".

And it's sadly not only Cubase - ALL Steinberg hosts do that at this point (Wavelab not until WL6 IIRC)



If your copy of Cubase LE or Artist doesn't do that - be happy for it!

For everyone else - I feel your pain!
Frankly, if it's all that 2 times in a year, my 50 plus plugins get re-scanned, i can well live with that...

Offtopic: Fkn hell @ over 11.000 posts here... i really didn't realize i'm such a spammer. :P

Post

thejonsolo wrote:Nice if that were true.
It is true, and if you are actually having the issues you reported, you have much deeper installation issues waaaay beyond anything cubase has done.

On the speed of scanning issue, if you are windows, put an exception in windows defender on your plugin folders.

I have 600+ plugins and my re-scan took 4 minutes.

The 5 plugins that I had restored from blacklist were still restored (AAS stuff). No re-blacklisting of anything.

The iZotope plugs have a known blacklisted VST2 set of dlls. But, your installation should have the versions that do work and that are not blacklisted. They are blacklisted on purpose for known/good reasons... If you hadn't monkyed with anything then they did not have to go through the dialog process again. I have a crapton of Izotope plugs, and I had zero messages. And, the blacklist versions of the plugs remained in the blacklist, and the "good" version of the plugs remained available in the main list and in my custom plugin menus.
If you have to ask, you can't afford the answer

Post

SJ_Digriz wrote:
This morning ..
1) start cubase
2) get coffee and donut
3) come back with coffee and start using cubase
That's a suspicious list of events... Where were you the night the donut went missing? :hihi:

Post

Codestation wrote:
SJ_Digriz wrote:
This morning ..
1) start cubase
2) get coffee and donut
3) come back with coffee and start using cubase
That's a suspicious list of events... Where were you the night the donut went missing? :hihi:
Probably standing in front of the donuts :lol:
If you have to ask, you can't afford the answer

Post

chk071 wrote:Curse words aside
I fully acknowledge that my hatred of the winter portion of US daylight savings time is completely irrational.

:D

For the reasons Hink listed... I love the summer portion. We should simply leave it that way.

Post

SJ_Digriz wrote:
Probably standing in front of the donuts :lol:[/quote]

I can't help it. This is my favorite food. I never allow myself to eat it... but...

Image



FFS I so want a donut right now. :bang:

Post

Codestation wrote: FFS I so want a donut right now. :bang:
My wife snuck out early this morning and brought back some apple fritters and various assortments. I wasn't joking when I said I got coffee and donuts in the time my scan took. :lol: I would share but post is not the best method of donut delivery.
If you have to ask, you can't afford the answer

Post

In Windows one can disable the automatic switch from DST to normal time and vice versa. I suppose that would solve the problem. Sure, your computer time would be off by one hour for half the year, but who cares.

Post

fluffy_little_something wrote:In Windows one can disable the automatic switch from DST to normal time and vice versa. I suppose that would solve the problem. Sure, your computer time would be off by one hour for half the year, but who cares.
this used to work, and still does for most people. However, a lot of the online plugin authorization systems now do a compare to the system time.
If you have to ask, you can't afford the answer

Post

chk071 wrote:Frankly, if it's all that 2 times in a year, my 50 plus plugins get re-scanned, i can well live with that...
On one hand, people have massive problems with getting "blocked" plugins back to work again.
On the other, it's a good time to check if there is a maintenance update to your tool. If there isn't - well...



At least one thing improved with Cubase 9 - the general load time until the host launches. Still not as fast as Wavelab's "plugin management" though - but then again - Apples and Oranges. What works in Cubase, doesn't necessarily in Wavelab and the other way around. Hence long beta periods of software tools.
[ Mix Challenge ] | [ Studio Page / Twitter ] | [ KVRmarks (see: metering tools) ]

Post

Compyfox wrote: At least one thing improved with Cubase 9 - the general load time until the host launches.
Yeah. Still takes at least double as long as S1 to load though, but, i can also live with that. :) As you wrote, it's better than it was before.

Post

One of the rare better improvements. Though well... the "Sentinel" is actually quite a good concept (copied from Wavelab) and was indeed long, long overdue (think Cubase 5 overdue!).



Also... hm... Donuts... (now I'm hungry as well)
[ Mix Challenge ] | [ Studio Page / Twitter ] | [ KVRmarks (see: metering tools) ]

Post

Compyfox wrote:One of the rare better improvements. Though well... the "Sentinel" is actually quite a good concept (copied from Wavelab) and was indeed long, long overdue (think Cubase 5 overdue!).



Also... hm... Donuts... (now I'm hungry as well)
I agree, however I'm not a fan of the blacklist/whitelist approach. The way wavelab does it is far superior. Plugins are still not sufficiently isolated in their own process to allow plugins to crash yet leave the host running. It's better, but not on a par with Wavelab or Reapers approach, to name a few.
If you have to ask, you can't afford the answer

Locked

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”