PlanetZ forums - scopeusers.com

I spent hours making my own Modular patch and when I go to open it, it can't because the presets are not 100% "compatible". Why does this happen and how can I prevent it form ever happening again? I can not stand this. It is making me even more insane than I already am.

Isn't it the talked about modular bug? I've encountered it and I don't know of any workaround. It didn't actually corrupt the patch but the presets could not be loaded anymore, which is pretty annoying. I wonder if one saved the whole patch with each preset what would happen... Unpractical yes but to loose your presets is even more unpractical...

Braincell, this is a known 'feature' of modular since introduction of new preset system (with separate .pre file)
Best way of avoiding this is creating .pre file after you finished tweaking the structure and cabling of the patch and only changes you plan to make is tweaking the knobs.

Is a .pre file the same a preset file? I save the preset then when I load the project don't change it? I don't understand. Sorry.

.pre = preset file

What Michu is saying, is that you should make your modular patch and make sure all the cables are in place and all modules are in place before making presets.

If you even -move- a module within a patch that has a preset file, it can corrupt the presets.

So - make your synth finalized before touching presets, then when you know you're never going to touch the wiring or modules again, make presets (in which you can edit the buttons, knobs, and faders for different sounds).

,

You also might want to save a backup of the Modular patch somewhere before making presets, if you think you might need to rearrange it someday.

_________________
Witek Radomski
Innovation is my Inspiration!

<font size=-1>[ This Message was edited by: Leper on 2006-09-02 10:49 ]</font>

I've lost hours of work that way ! CWA this is no small bug
The X amount of presets are compatible I can handle but this preset file doesn't belong to this patch ( !! ) preset file is not valid or just SFP that suddenly crashes on loading systematically.

I forget to mention all the times it's not able to record properly settings of a given preset, even a simple patch

I rely only on Mod2 shell to start with.

I think I'am not the only one to miss a control and move a module a fraction instead.

cheers Witek for translating me

yes, by .pre file i mean a preset file in your /Presets folder that is created via the preset manager of the patch.
it seems that preset file refers to a static snapshot of the patch in a state from the moment of it's creation, so if you make any changes to the structure of the patch after you created the file you most probably render it incompatibile. note that most often the settings that are not recalled are on the modules you changed or moved.

I love "presets not 100% compatible", especially with MIDI Clock module in the patch. On my patches, it stops the MIDI Clock from jumping around when switching presets while making a tune

Nothing bug, indeed just an indication that some reference to present module is (not) found in the preset list. This topic has been discussed lenghtly in previous posts...

Well, I thought and expected it would be fixed by now. We should launch a petition. The Modular was not cheap and this is not acceptable to me.

braincell, relax man. It's not an error nor a bug, it's a notification, to let you know some parameter currently in the patch wasn't there when you saved the presets. It wasn't Scope that 'corrupted' your patch, it was you who changed something inside after saving the presets. Scope doesn't do that, but it notifies you did. Whenever it comes up, just press space or enter.
If it really keeps you out of your sleep, re-load then re-save each preset, and then the preset list. This should make the pop-up disappear.

Thanks, I will try it again.

Put down the handbag...

I'm going to try it but the pop-up being meaningless is ok. What I don't like is that the patch does not work *at all* after the pop-up.

When I load a project. I want *everything* to be the way it was when I last saved it. It is bad enough that I have to load the SFP, then load my project (so far 2 projects have loaded), then Cubase then Reason and it all has to be in the right order, now you say you want me to load something else? Enough loading! This is wrong. This is not user error. This is poor design. If you disagree, you are not playing with a full deck.

The fact that there is a way around it is good. I will try that and I trust you are right. It is something that I wish nerver came up. I like everything to go smoothly. Yes, nobody is perfect but this is something that has been known about for years.

If they can't fix it, I would be happy if they just removed the preset option from the modular synth.



<font size=-1>[ This Message was edited by: braincell on 2006-09-04 09:54 ]</font>

You obviously did not read or think about what I wrote.

Good luck on your future scope sessions, and maybe try using what works for you.

You are saying I did something wrong and I am saying an error message is something I never want to see and should never come up. Even if it is something that can be avoided or ignored as you put it. If I made an error, it should not be possible to make that error.

I'll try again with a smaller patch until I get the hang of it and thanks for your help. Hit spacebar.


<font size=-1>[ This Message was edited by: braincell on 2006-09-04 12:29 ]</font>

If they can't fix it, I would be happy if they just removed the preset option from the modular synth.

preset option is just that, an option. you can save patch and it will reload in exactly the state you saved it. if you don't create preset files, the possibility of seeing the message that annoys you so much is zero.
in fact this is more or less the way i use modular, the patches i create are most often one trick ponies so presets for them make not much sense. AFAIK there are a few more users that work this way...

sounds good.