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

[Compyfox]

At least "something" good came out of it, chk071... I had a good laugh. So feel honored.

[el-bo (formerly ebow)]

Moaning about a plug rescan twice a year is like first world problems with their own first world problems

Get Tae f**k!

[incubus]

BTW, who ever decides what topic are relevant and which ones are not? If it doesn't apply to you, stay away. If it does you can bitch all you want. The trolling over people with issues in extremely hypocritical because when YOU (whomever) have an issue, it's gonna get brought up.

It's a stupid thing for a daw to do, stop trying to make it out like it's whining.

[thecontrolcentre]

Soooo ... why does Cubase even do this? Its not something I ever came across with any DAW I ever used (Acid & Live mainly).

[Compyfox]

Soooo ... why does Cubase even do this? Its not something I ever came across with any DAW I ever used (Acid & Live mainly).

I'd like to know this as well, actually since it started to happen with SX/C4 (or was it really C5 - I really, really don't remember anymore) days - and it happens in ALL Steinberg hosts.


It's obviously not a "bug" - so this "feature" must have a deeper reason...

[el-bo (formerly ebow)]

Moaning about a plug rescan twice a year is like first world problems with their own first world problems

Get Tae f**k!

Just went back to read the op, which I guess I should have done before commenting. A plugin rescan, for me, takes maybe about a minute, so I guess I hadn't realised it could be such a P.I.T.A

Carry on

[incubus]

See?

Not everyone is simply whining when they have a problem

[Guillermo Navarrete]

Hello,

You just have to change the clock manually.

Best regards,
GN

I thought that what triggered the rescan was the adjustment of the clock. Why should Cubase care whether it was done manually or automatically?

We have a theory:

Cubase maintains a XML file containing the modification dates of the plugins it scanned to determine if they have been updated since the last scanning. From the discussion in the thread, it appears that these dates get out of sync with the actual modification dates when daylight saving time is adjusted. If the statements in the thread are true, it clearly points to what could be the cause of this.

Best regards,
GN

[Compyfox]

Then what are you (Steinberg) waiting for? You got enough hints to fix this.


Oh wait... it wasn't filed often enough as being an "issue"!
(see: viewtopic.php?p=6729112#p6729112 )


Nevermind then - looking forward to this fix in Cubase 12... unless DST was being "disestablished" until then. So you still got another 6 years or so...



Subnote: This is sarcasm, for those that don't get it...

[SJ_Digriz]

[fmr]

Just went back to read the op, which I guess I should have done before commenting. A plugin rescan, for me, takes maybe about a minute, so I guess I hadn't realised it could be such a P.I.T.A

So, if it takes a minute, you must have an EMPTY VstPlugIns folder. Good for you. But there are others who actually USE and HAVE plug-ins. Those are the ones that have a problem with scanning and rescanning.

For me, a scan actually takes more than half-an-hour, and it happens that, sometimes, a dialogo box opens, and the scan doesn't proceed until I hit OK. Or the scanner crashes and the host quits, and I have to start all over again.

So, I even cannot start the scan and go away do something else. I have to actually be there watching (or come to KVR write something). All these scanning routines are plainly stupid, and basically useless. User should get the option to stop the scanning and still use the plug-ins. Each plug-in would be scanned when it would be instantiated for the first time. So simple.

[el-bo (formerly ebow)]

Just went back to read the op, which I guess I should have done before commenting. A plugin rescan, for me, takes maybe about a minute, so I guess I hadn't realised it could be such a P.I.T.A

So, if it takes a minute, you must have an EMPTY VstPlugIns folder. Good for you. But there are others who actually USE and HAVE plug-ins. Those are the ones that have a problem with scanning and rescanning.

I HAVE plugins, USE plugins, and do not have an empty vst folder. Imagine a world where shades off grey exist between black and white

[fmr]

Just went back to read the op, which I guess I should have done before commenting. A plugin rescan, for me, takes maybe about a minute, so I guess I hadn't realised it could be such a P.I.T.A

So, if it takes a minute, you must have an EMPTY VstPlugIns folder. Good for you. But there are others who actually USE and HAVE plug-ins. Those are the ones that have a problem with scanning and rescanning.

I HAVE plugins, USE plugins, and do not have an empty vst folder. Imagine a world where shades off grey exist between black and white

Because each plug-in takes like two to ten seconds (some even more, so in average, I'll say around five seconds), and there is a gap between each plug-in, and admitting your "one minute" is true, you must not have more than 12 to 15 plug-ins.

Otherwise, you are LYING, and the scan takes more than one minute.

[zvenx]

I have a Cubase Mac and Nuendo PC with more or less the same plugins.
The Mac OS and applications are on an SSD the PC isn't.
The scan on the Mac are significantly quicker than the PC.
Nowhere near 5 sconds per plugin average, much quicker.
It is quite possible that he has a very different experience than you and not lying, oh wizard of everything.
rsp

[el-bo (formerly ebow)]

I have a Cubase Mac and Nuendo PC with more or less the same plugins.
The Mac OS and applications are on an SSD the PC isn't.
The scan on the Mac are significantly quicker than the PC.
Nowhere near 5 sconds per plugin average, much quicker.
It is quite possible that he has a very different experience than you and not lying, oh wizard of everything.
rsp

I just tested it, scanning on logic's boot-up (Trashed preferences to force it)

It scanned 94 plugins in 39 seconds, so maybe we are talking about something else