PlanetZ forums - scopeusers.com

I have a question.
A made a big Modular IV patch with +/- 60 midi cc's.
Tweaking knobs and saving presets.
I noticed some knob movements are not stored.
Is there a limit for midi cc's?

you should make a midi preset for that.

Gary, you never sleep!
Midi peset for in a sequencer you mean?
I can't.
It is for live without sequencer but with a Behringer midi controller.
The presets are to change quickly when needed.
Should I kill some les important cc's

no sir, a midi preset for the modular patch. there are more than one type of preset. one kind is just for midi assignments. pfft! engineers...

seriously, i think thats what you need to do. load the patch then recall a midi preset.

I have to look it up what you mean Gary. Back to the Scope manual.

FOUND IT, thanks!
I'll give it a try!

I hope I'm still worthy the name 'Mangler'.

it's a talent! not everyone can do it.

But now, how does it work?
Turning the knobs on the Behringer, save the midi presets.
3 LFO's won't move by changing the preset.
They have a cc and marked with an x(working).
And has anyone counted the amount of changes that can be saved in a 'normal' preset?

Does the LFO still respond to the BCR ?

If you remove all CC assignments will varying positions be recalled by presets ?

If the LFOs are the only controls in the project, will they then respond to program changes ?

The LFO's are still reacting on Midi from the Behringer.
All assigned knobs do. But the 3 LFO knobs aren't changing position after calling a preset or midi preset.

check with sonic core

as some things dont have presets assign switched on

i had some problems like this with bc modular and sharc rectified it

it might just be that the lfo is not saving as preset

try doing a smaller patch just with some lfo and a sound source and see if you can save presets

I made a new patch with the same LFO's and they were saved as presets.
Tomorrow an other day.

also roland did you finish the circuit before saving any presets as if you swap modules out while still building it adds a preset bug and if you save presets and then change the circuit

it can cause the problem your having

What's the fix? Load a buggy preset, tweak the LFO, (or reassign MIDI?), and then save into a new preset file?

No fix, I just had a start in rebuilding the patch in an other DSP.
Tested different settings and making presets. That works.
I'm very anxious when they will stop working when adding more modules and control data.

I had little contact with Holger.
But as we speak, he is on his way to China!
So the burning question, how many parameters can be stored as preset has to wait.

btw, did you know you can copy, 1 by 1, modules in the Modulars AND paste even in a separate Modular?
I hope we can copy/paste more in the future in 1 go.

ctrl+D just copy one module at a time, but you can use sub modulars to split and arrange modular patches into multiple re-usable patches that you can open in other modulars without need to re-connect all the modules.
About the presets bug, if a module doesn't store midi cc into presets, it can often be fixed with scope sdk, not always, but often.

what it means is if you create a modular patch dont save any presets until finished your total patch

thats it

by all means create patches but just write down them on paper dont save

then wjhen you have totally finished the patch then save as presets

i learnt this early on and when loading them you can get errors saying presets dont match device

but its not really a bug but its our fault of working by removing and adding mdl from projects and changing patches you cause glitches due to the software looking for stuff thats not there any longer

if you were doing it in c++ coding it would be bad coding

the story is when messing about dont save presets and then when you are ready to save presets there wont be any modules missing and it will respond properly

@jhulk,
you're right, the preset file must be generated after the patch is finished, but sometimes there can be some module(not just for modular) that doesn't store cc assignments and i was referring to that case.
Also the use of sub modulars is a time saver to re-use partial circuits and can also be duplicated between different modular shells by ctrl+d.

yes i know some dont have it assigned

i found this out in bc modular and also poly not being set so that its only mono

but with simon you let him know and he changes it quickly in the sdk

but i dont know about sonic core if they change them if notified

if a module is protected as you have the sdk can it be switched so that it can be set