PlanetZ forums - scopeusers.com

many times i notice that stm channel presets do not affect only the channel but also affect the mixers STM4896 or ST2448 general mix 1,2,3,4 effects setings.

you might notice that happening after setting some values of the channel... after change some values of the Mix effect and....... when going to a channel to select
a preset then also Mix effect goes to previus value
also if you have multiFx loaded in a mix effect and you have loaded an effect in it lets say a EQ... then you try agai channel preset in a random channel and.. suddenly the effect of the multiFx box will be unloaded(remembering the previus state).

incredibly embarassing.... is there any chance i can fix it without waiting for scope 6 ??

if there is something wrong in presets parameters, it can be fixed with scope sdk as i have done with the vocodizer bug.

I think i have understood how to reproduce the bug, but if you can, post a step by step, simpler and clearer procedure to reproduce one of the above bugs, so i can work to fix it.

1. load multiFX into Mix insert1. have it saved as a preset of STM mixer.
2. load an effect module in a channel insert and save it as a preset.
3. insert an effect into the multiFx (of the insert of the Mix)
4. try to recall the channel preset.......... The multiFx (of the insert of the MIX) effect will be unloaded.

This is one example.


Another example is if you have an EQ in one of the the MIX inserts... when selecting a STM channel preset the EQ changes values and is not independent from the channel.

ok,
i have tried the first example and you're right.
Then i tried inserting a parametric eq as master insert and it unloaded after recalling channel preset.

I'll take a look with sdk an hope it can be fixed.

Sal

Djmicron, just one thing : THANKS ! For all your actual work !

The STM2448 has another little bug : it forget midi controler numbers : if you assign some midi controler to faders, fx knobs or any controler, when you reload the project, the don't respond even if it's still there in the midi control assignment fader window. It's possible to recall them via a midi controler preset each time you load the project but if it did not forget, it would be less tiring !

thanks djmicron for your time.

it looks like the parameter assignments are ok, maybe something is wrong inside the circuit which is protected, it seems there is a relationship between channel inserts and master insert slot 1.
This bug is not present in v4.5 and i have tried everything i can do by modifying parameters defaults, but i'm sure it's something to be modified at circuit level.

The STM2448 has another little bug : it forget midi controler numbers : if you assign some midi controler to faders, fx knobs or any controler, when you reload the project, the don't respond even if it's still there in the midi control assignment fader window. It's possible to recall them via a midi controler preset each time you load the project but if it did not forget, it would be less tiring !

I think this can be partially fixed, if you send me your midi preset with the cc assignments, i can save the device with preconfigured cc assignments, this is fast to accomplish.

EURIKA!!!!!!!!!! The bug exists but I found a solution.

Whenever saving an STM channel preset you must be sure that Mix inserts are EMPTY.


So for faster.... I have STM4896 preset FLAT with MIX inserts loded and a second preset FLAT WITHOUT THE INSERTS (named..whatever... in my case I name it "FLAT empty")
ALWAYS do not forget to create the STMchannel presets with the MIX inserts empty. After you can load the inserts again and the modules of the MIX inserts will not be affected by the channel presets recalls.

This bug will prove to be pretty handy itself.. You could even have STM presets that are made with inserts loaded so the Mix inserts will be affected by choice

In that case you have to name which presets are saved with the Mix inserts loded(you have to specify because these will affect the modules of the MIX inserts)

i have seen this strange behavior, else it makes sense to have master effects outside of the mixer, it is less tricky

I think this can be partially fixed, if you send me your midi preset with the cc assignments, i can save the device with preconfigured cc assignments, this is fast to accomplish.

I don't remember untill which Scope version it was possible to save the entire device. I believe it was at the Creamware begining... The STM mixers didn't exist, anyway, I remember a blue big mixer.

( ...I found it ! : http://www.planetz.com/Pulsar/image/Big/BigMixer.jpg )

The problem is that I set new midi controlers each time I need them, different projects, different settings. I cannot know before which FX I'll use in which insert and which parameter I'll need to automatize. (I'm not sure for the word 'automatize' but it sounds nice )
I thank you anyway, Djmicron !

djmicron wrote:i have seen this strange behavior, else it makes sense to have master effects outside of the mixer, it is less tricky

with master effects out of the mixer is ok, but i tend to avoid it because the vu's of the MIX do not show the actual(final) mix levels.
also in that case the multiFx module outside of the mixer is ok, except that Optimaster crashes(checked in MultiFx module..and on realtime view of normalizing)
So a second mixer would do the job better(there you can load the optimaster without the crash fear), outside of the main STM.

Now I noticed another bug into STMchannel presets. The "compare"(blue,green colour) basically does not happen, so there is no possibility for checking back the values.
Whould that be easy to deal with?

And offcourse djmicron..........In bocca lupo... for tonight's soccer game. Mi piace la coultura italiana prima in musica e in football. xaxa

for metering you can use dedicated external metering.
I use the wolf audio meter, which also does rms.
I like the stm mixer because of very good signal separation and i can avoid using an analog signal adder.
About other bugs you mentioned, i didn't know, but with scope you have always workarounds, for example you could try using the modular shell for master effects chaining.

JoPo wrote:I don't remember untill which Scope version it was possible to save the entire device. I believe it was at the Creamware begining... The STM mixers didn't exist, anyway, I remember a blue big mixer.

( ...I found it ! : http://www.planetz.com/Pulsar/image/Big/BigMixer.jpg )

The problem is that I set new midi controlers each time I need them, different projects, different settings. I cannot know before which FX I'll use in which insert and which parameter I'll need to automatize. (I'm not sure for the word 'automatize' but it sounds nice )

ok, if you assign cc without following a schema it's not useful what i suggested before.
I like the old style preset management where you can save all the device to a new one, as it still happens with the modular shell