Is there a reason why all modules are being redownloaded in relatively short intervals?

[woau]

Happens sometimes every day, or every other day. Sometimes the stand-alone version has them downloaded but then the vst plugin needs to redownload them, even though i use them about the same amount.

Stops your flow. I unfreez a VM track and have to wait 10-15 min or longer before i can finally hear the patch again

[ColinP]

This shouldn't happen. I use VM every day and if I recall correctly my modules have only automatically downloaded twice in the past three years.

Contact support as I'm pretty sure they'll be able to sort it.

[Taddx]

I have the same problem.

[huggermugger]

A total re-download has only happened to me once, but once was too many. It's annoying, just like their slow, buzzkill log-in routine...

Retrieved User Info...
Getting Your Stuff...
Updating Catalog...
Getting Your Stuff...
Updating Catalog...
Retrieved User Info...
Updating Catalog...
Getting Your Stuff...
Getting Your Stuff...
Getting Your Stuff... (really? I've been using the same "stuff" for almost two years now. What exactly do you have to "get"?)

[seal58]

If there is an internet connection, VM will look for available module updates every time, when it gets started. It compares content of user's library with versions on VM server.

In the VM settings there is an option "Ask before downloading updated modules". As default it is unchecked. So VM will download updated modules automatically. I checked this option ON. So I prevent existing presets from getting defective because of an updated module, that still contains a little bug. I use to initiate module updates time by time manually.

Since a while I'm watching these updates and I could see, that there are several module updates every month. Sometimes only module surface has got small changes and user will not realise it on first view, why that module was updated. Sometimes module developer fixed a bug or added a new feature.

But when VM downloads all modules at each start, it seems to be a problem for VM support.

[Jo Beatz]

I think CA is simply not interested in fixing it. Convince me otherwise...

[Steve W]

I think CA is simply not interested in fixing it. Convince me otherwise...

I think your comment is oversimplification. It is not up to any of the forum members to convince you otherwise.

[cherryaudio Greg]

Hi,

Anyone having this problem or a similar one, please be sure to contact support directly: https://cherryaudio.kayako.com/conversation/new

Greg

[Jo Beatz]

I think CA is simply not interested in fixing it. Convince me otherwise...

I think your comment is oversimplification. It is not up to any of the forum members to convince you otherwise.

I am addressing CA here. The problem has been reported several times (including by me) and nothing has happened since then. I'm not going to lie, but it's probably been almost a year now.

[cherryaudio Greg]

Hi,

Jo Beatz, are you having this problem? Did you send in a support request? You can do that here: https://cherryaudio.kayako.com/conversation/new

It's not a universal issue, and it's not happening for us, so the details are important.

Greg