KVR Audio

Jace-BeOS · Post by **Jace-BeOS** » Tue Nov 07, 2017 8:45 pm

Definitely a Windows thing.

Sg1122 · Post by **Sg1122** » Wed Nov 08, 2017 5:21 am

i am on windows 8.1 and my cubase rescanned because of this but not so annoying for me i dont have too many plugins

Googly Smythe · Post by **Googly Smythe** » Wed Nov 08, 2017 7:11 am

Windows + Auto-update Daylight Saving Time + Cubase = plugin rescan. Twice a year without fail. Hey ho. Put it in your diary/calendar and be prepared for the next one in March.

Benutzername · Post by **Benutzername** » Wed Nov 08, 2017 1:12 pm

Cubase does this since the first Cubase VST version where the Plugins didn't even have GUIs.

I was prepared to wait for ages when I started Cubase 9 yesterday. But it started as "fast" as usual. Then I noticed that I haven't used Cubase for at least half a year.

Guillermo Navarrete · Post by **Guillermo Navarrete** » Wed Nov 08, 2017 3:53 pm

Hi,

thejonsolo wrote: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.

Quoted from JIRA:

"the root cause is that FNFileSystem::getFileTimes() on Windows returns the time as local time and not as universal time.
And the issue was analyzed by our QA and the conclusion was: changing this had high risk.
So if you use FNFileSystem::getFileTimes() to cache something then you will have the same problem."

Basically that's it, it is not catastrophic, it happens twice a year and repairing it will take many valuable resources and it is risky (which means, repairing it might break something else).

Best regards,
GN

SJ_Digriz · Post by **SJ_Digriz** » Wed Nov 08, 2017 3:57 pm

Guillermo Navarrete wrote:Hi,

thejonsolo wrote: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.
Quoted from JIRA:

"the root cause is that FNFileSystem::getFileTimes() on Windows returns the time as local time and not as universal time.
And the issue was analyzed by our QA and the conclusion was: changing this had high risk.
So if you use FNFileSystem::getFileTimes() to cache something then you will have the same problem."

Basically that's it, it is not catastrophic, it happens twice a year and repairing it will take many valuable resources and it is risky (which means, repairing it might break something else).

Best regards,
GN

Hey G,

I think what people want to know is not why the time error as much as why it has anything to do with plugins.

Jace-BeOS · Post by **Jace-BeOS** » Wed Nov 08, 2017 7:22 pm

Because they're generating VST registry GUIDs with the value retuned by the get time function...?

SJ_Digriz · Post by **SJ_Digriz** » Wed Nov 08, 2017 7:35 pm

Jace-BeOS wrote:Because they're generating VST registry GUIDs with the value retuned by the get time function...?

I don't know that they are registry GUIDs, but as I wrote earlier I thought I remembered that they do a "version" check using that function, I'm not sure if they had the guid in the VST xml file back in the day. Can't remember.

MFXxx · Post by **MFXxx** » Wed Nov 08, 2017 8:12 pm

This is why I love alternatives to c/r etc. Korg is a PITA for official users since the dropped the dongle support

But it is only once a year. hellishly annoying none the less!

SJ_Digriz · Post by **SJ_Digriz** » Wed Nov 08, 2017 8:44 pm

MFXxx wrote:This is why I love alternatives to c/r etc. Korg is a PITA for official users since the dropped the dongle support But it is only once a year. hellishly annoying none the less!

I don't believe this had anything to do with copy protection. I think it was version identification.

JonSolo · Post by **JonSolo** » Thu Nov 09, 2017 4:21 am

I understand somewhat the explanation offered as to what is happening in the background. But I do NOT understand why it triggers a RESCAN of the plugins.

It seems to me that we should be able to TURN OFF scanning for plugins if we so desire. I mean if I don't want something scanning my computer, I should be able to turn of that feature without removing it.

Either way...this is dead until the Spring. Move along, ha ha ha

JonSolo · Post by **JonSolo** » Mon Mar 12, 2018 2:25 am

AAAAAGGGGGGGGGGGGGGGHHHHHHHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Spring. GEEEEZZZZZZZZ.

JerGoertz · Post by **JerGoertz** » Mon Mar 12, 2018 2:48 am

Yup... Me too.

Was all set to make music and *BAM* 2 hours gone doing the rescan, manually editing blacklist files, etc.

SJ_Digriz · Post by **SJ_Digriz** » Mon Mar 12, 2018 3:59 pm

2 hours??? took 5 minutes here, no editing anything after.

Reefius · Post by **Reefius** » Sun Oct 28, 2018 12:04 pm

Once again rescanning all plugins

Cubase and Daylights Savings again...