help! damaged preset file? (stm2448)

katano · Post by **katano** » Wed Feb 01, 2006 7:03 am

hi all

this is really a pain in the a**. i worked the last days on 5 songs (mixing). all mixer settings saved in the same stm2448 preset file.

after booting up my daw today, the mixer channel settings do not load properly. it's very strange, only the selected channel will load the channel settings, but the wrong ones! i.e. if channel 10 (bass) is selected, it loads the settings of the last selected channel (i.e. hihat) from yesterday.... the other channels don't load anything, not even the faders move... aaaaarggh...

from this preset file, i can't load anything... all banks and presets seems to be corrupt.

did you ever have such a problem with stm presets? if yes, is there a way to fix the preset file? would be very nice to fix it, i worked 3 days on the songs and didn't remember als the settings of eq, effects, comp and so on...

thanx in advise
roman

[ This Message was edited by: katano on 2006-02-01 07:14 ]

katano · Post by **katano** » Wed Feb 01, 2006 7:20 am

hi again

may someone could reproduce the error with the corrupt setting file? here it is:

http://www.birdstudios.ch/STM%202448.pre

you'll see the problem when you try to load some of the presets in the bank "sparkling"

samplaire · Post by **samplaire** » Thu Feb 02, 2006 12:23 am

Hi,
I encountered similar problem described in this thread. Though I'm on Mac it may also work for you reinstalling the Scope software. Backup your projects first!!! And your custom preset files, as well. As Hubird suggested - replacing the cset.ini file with the one you, of course, backuped would work for you (for me it didn't).
Good luck!

Booster · Post by **Booster** » Thu Feb 02, 2006 1:49 am

Hi Katano,

I just tried to load some of your presets and indeed, like you said, only one channel (the selected one) loads. I once had similar problems with my mixer after I had a complete crash of my system. After the crash everything seemed to work fine, except for the STM mixer. It took me days to find and solve the problem but in the end I discovered the stm2448.dev file was corrupted. After a re-install the problem disappeared, but in your case I think you tried to save presets with a corrupted mixer. I doubt if a clean install will get your settings back (because I can't load them either on my system), but it sure is worth trying!

Good luck...

katano · Post by **katano** » Thu Feb 02, 2006 2:37 am

@samplaire: thanx. i think it's a different problem. nevertheless i'll reinstall my daw anyway...

@booster: thanx for testing the preset file. i'm shure you're right, a fresh install of stm2448.def or the full sfp will not solve the corrupt preset file. I think i'll send the preset to creamware. maybe they can fix it...

I can't imagine how the mixer.def should have become corrupt. and i never had problems with freezing xp or bluescreen. also sfp is very stable, no probs at all.

ah, another strange thing. sometimes when i change the eq settings of a 2448 channel, the q setting does not remain at it's value when i jump to another channel and back... any ideas?

greez
roman

Booster · Post by **Booster** » Thu Feb 02, 2006 3:25 am

ah, another strange thing. sometimes when i change the eq settings of a 2448 channel, the q setting does not remain at it's value when i jump to another channel and back... any ideas?

Same problem here. But I think it's only visible in the graphic and not audible. The value in the Q-box is still displayed correctly. Maybe Creamware could take a look at this?

Booster · Post by **Booster** » Thu Feb 02, 2006 3:27 am

BTW: the way to retrieve the correct visuals again is to click the value in the Q-box and push enter.

Booster · Post by **Booster** » Thu Feb 02, 2006 3:33 am

Hmmm... it only occurs here when a LowPass is added and only to one of the 4 Peaks.

katano · Post by **katano** » Thu Feb 02, 2006 4:06 am

On 2006-02-02 03:33, Booster wrote:
Hmmm... it only occurs here when a LowPass is added and only to one of the 4 Peaks.

correct, and only if the lowpass is not the first of the 4 bands?

i recognized that it works best when keeping bands in a proper order:

1. lowpass
2. lows/low mids
3. mids
4. highs/highpass

[ This Message was edited by: katano on 2006-02-02 04:44 ]

katano · Post by **katano** » Thu Feb 02, 2006 4:08 am

Same problem here. But I think it's only visible in the graphic and not audible. The value in the Q-box is still displayed correctly. Maybe Creamware could take a look at this?

are you shure that it's not audible?

Booster · Post by **Booster** » Thu Feb 02, 2006 6:35 am

Yep. No audible changes, just an incorrect graphic. Try it yourself with a noise-generator: make one of the Q-settings very narrow, change channels, go back and see the narrow Q changed in a very wide one. Look at it's value-box and you'll see it's still the amount you entered. Click it and enter (without changing it) and you will hear no difference, only the graphic view is updated.

Booster · Post by **Booster** » Thu Feb 02, 2006 6:38 am

On 2006-02-02 04:06, katano wrote:
correct, and only if the lowpass is not the first of the 4 bands?
[ This Message was edited by: katano on 2006-02-02 04:44 ]

Well.. you might be right here! This could be the ideal workaround for this bug. Thanks!

katano · Post by **katano** » Thu Feb 02, 2006 6:49 am

at this point i wonder why I couldn't find any thread about these "bugs" here on planetz.

Couldn't be true that we are the only ones recognizing this? where are all the 3000-and-more-posts-users?

anyway, sfp is still an amazing product for the price!

roman

Post by **garyb** » Thu Feb 02, 2006 10:03 am

i beleive that the visual bug is well known. the other? much more rare....

katano · Post by **katano** » Fri Feb 03, 2006 7:51 am

yes, i read about the visual bug. maybe i missunderstood the thread, thought this visual bug is different... so, how many different visual bugs are known?

and what about "the other, much more rare"? noone else some inputs, working advices to prevent these kinda problems? would be happy to hear a workaround (not the workaround to mix it again after preset crash, obviously)

thnx
roman

ps: garyb, you saved the honour of the more-than-3000-posts-users

[ This Message was edited by: katano on 2006-02-03 07:56 ]

Post by **hubird** » Fri Feb 03, 2006 10:13 am

Well, it should be clear that if someone doesn't respond, he doesn't have the problems that you have.
At least I don't

I'm on mac, so it won't help you to even let you know I don't

good luck anyway

symbiote · Post by **symbiote** » Fri Feb 03, 2006 1:50 pm

Best "workaround" is to just save the whole project along with just the presets.