garageCube

Hi,
Never bothered me much before, as i ran things pretty much on the fly....
But now, I am creating various 'scenes' using layer sets; yesterday I got 3/4 basic scenes done - saved the project, opened
it today expecting everything to be as I saved it, but no...... the modules have gone back to default settings, or switched themselves off.

Is this right?

Thanks,
tdog.

Doesn't sound right. You can have up to 8 'saved' work spaces, from Window > Workspaces > command 1 - command 8.
Every now and again i'll have a module shift from where i had it before but never in saved projects. Maybe there's something else going on.?

Hy, I've noticed in the 8.2.5 the same problems... some modules had lost their settings or just went off..

I'hope with the 8.2.6 it's better, I'll need it in a few weeks for a "more than 12 hours VJing" project

8.2.6?

orion wrote:Doesn't sound right. You can have up to 8 'saved' work spaces, from Window > Workspaces > command 1 - command 8.
Every now and again i'll have a module shift from where i had it before but never in saved projects. Maybe there's something else going on.?

At the moment, I set up some stuff and just - 'save project' - however, when i open the project later, a number of settings are not saved;
I was under the impression that after saving a project, it would open in the exact state it was saved in..?

tdog

at-om-vision wrote:Hy, I've noticed in the 8.2.5 the same problems... some modules had lost their settings or just went off..

I'hope with the 8.2.6 it's better, I'll need it in a few weeks for a "more than 12 hours VJing" project

This is my experience as well, all was good up until the update to 2.6.4 ....

tdog

I have certainly heard reports of settings not getting saved after re-opening them, not just from 2.6.4 but even prior. However I have not been able to reproduce this at all. It could very well be that this is related to modules that have their own settings that overwrite the file settings somehow. A more methodical approach should be used to determine exactly what is happening.

As I have mentioned before, I have a series of project files for a performance that I have been working on since 2004 that is dependent on several modules and uses an M-Audio Trigger Finger and in each instance of opening these files they have worked. The thing to note here is that all of the modules I was using were either stock GarageCUBE ones or custom ones that were not very complex (i.e. no code).