Cubase and Daylights Savings again...

[JonSolo]

This time, however, please, no Nazi comments to get this thread locked.

Cubase+Daylight Savings=Rescan of my plugins...TONS of them. Long night just to get going.

Before anyone says anything, I did an update and somehow my Auto Daylight Savings got ticked again in Windows. I forgot about it all day till I just loaded Cubase. I know Steinberg came on here and their fix was to turn it off in Windows.

Maybe fixed in 9.5????

Doubt it. But not a deal breaker. Just a pain, twice a year.

No donuts and coffee.

[Jace-BeOS]

Why the heck does changing the time cause Cubase to rescan all the plugins?

[JonSolo]

You can change the time and it makes no difference. But if you have Auto Daylight Savings checked in Windows, when your OS clock changes, a rescan takes place.

Never been explained by Steinberg. They just commented that they would rather spend their time on something else than worry about those of us who complain twice per year. Oh well. I just wanted to start a topic, ha ha ha.

[VitaminD]

How odd. I never noticed this until now... yes, my Cubase Artist 9 is 'initializing' (ie Scanning VSTs) now that daylight savings has concluded.

[UltimateOutsider]

Oh. Haha, so THAT's why I just had to sit through a plugin rescan today. I didn't think I had installed anything new.

[JerGoertz]

Yeah, happened here too... One thing I like about Live vs. Cubase is that this shit is avoided.

[Googly Smythe]

My 350-ish plugins took about 5 mins. If it took hours for you, you must have 10,000 of the little buggers. I doff my hat to you sir.

[fmr]

You can change the time and it makes no difference. But if you have Auto Daylight Savings checked in Windows, when your OS clock changes, a rescan takes place.

Never been explained by Steinberg. They just commented that they would rather spend their time on something else than worry about those of us who complain twice per year. Oh well. I just wanted to start a topic, ha ha ha.

Yes, I had that last weekend (in Europe, the clock changes a week earlier). And here we went again, with a full rescan.

[don1thedon]

Yes, I had that last weekend (in Europe, the clock changes a weel earlier). And here we went again, with a full rescan.

Likewise, but to be honest I had not picked up that it was this old chestnut. I must power up my backup PC & let it run through the scan so that one doesn't catch me out when I need it most! Thanks for the heads up TJS.

[JonSolo]

It was hours last time because I was fighting some bad plugins. This time, after eliminating some of the Izotope mess and a few others, my 1000+ plugins took about 20 minutes. I run so many plugins to accommodate various projects.

[SJ_Digriz]

Never been explained by Steinberg.

Actually, I think they did explain it a long time ago on the old borg forum. Can't find it though. From what I remember it has something to do with the GUID mapping of the plugin. IIRC it was going to be monumentally invasive to try and "fix" it. It's like at the core of how they identify/manage plugins. That's what I recall, but my memory doesn't work so great sometimes these days.

EDIT: and by monumentally invasive, I mean support for legacy project files and things like that. It would cause more user grief than simply rescanning twice a year.

[Terrafractyl]

Yep its annoying! Especially when you have a ton of plugs. and now i have a few from companies like UAD that make you install their entire output despite only have 5 licenses. Then of course because i have old projects on my comp i have cubase5-9 and 32 and 64 bit versions of all plugs. Loading c5 the other day took a very long time!

[Jace-BeOS]

Never been explained by Steinberg.

Actually, I think they did explain it a long time ago on the old borg forum. Can't find it though. From what I remember it has something to do with the GUID mapping of the plugin. IIRC it was going to be monumentally invasive to try and "fix" it. It's like at the core of how they identify/manage plugins. That's what I recall, but my memory doesn't work so great sometimes these days.

EDIT: and by monumentally invasive, I mean support for legacy project files and things like that. It would cause more user grief than simply rescanning twice a year.

GUIDs... yuck. That's the kind of crap that resulted in Sonar losing plugins. I hate the registry. But why would a GUID change when the DST changes??

[SJ_Digriz]

Never been explained by Steinberg.

Actually, I think they did explain it a long time ago on the old borg forum. Can't find it though. From what I remember it has something to do with the GUID mapping of the plugin. IIRC it was going to be monumentally invasive to try and "fix" it. It's like at the core of how they identify/manage plugins. That's what I recall, but my memory doesn't work so great sometimes these days.

EDIT: and by monumentally invasive, I mean support for legacy project files and things like that. It would cause more user grief than simply rescanning twice a year.

GUIDs... yuck. That's the kind of crap that resulted in Sonar losing plugins. I hate the registry. But why would a GUID change when the DST changes??

Like I said I don't remember exactly, but i think it was a hash or something built out of timestamp to uniquely identify plugin versions, especially back when versioning of plugins was such a disaster. I could be full of crap. I just remember the long thread. I could remembering the person who was explaining their understanding and they were wrong. The only thing I remember clearly is that there is a reason, and it isn't an easy fix.

[jancivil]

I've had many restarts, never noticed any plugin scan. Maybe a Windows thing? (I saw 'hate the registry', and yeah.)