PlanetZ forums - scopeusers.com

Conqueror's Reign wrote:When using the midi learn function within scope volume is cc7, check.

Not necessarily. It sounds as though you're trying to allocate cc7 to all faders on the same MIDI channel. That won't work (and would result in the symptoms you describe).

If you use only cc7 for volume faders then you need to assign each fader to cc7 on a DIFFERENT MIDI channel. The downside with this method, though, is that you only get 16 independently controllable faders per MIDI port (one per MIDI channel) since there are 16 channels available per MIDI port.

An alternative (and more flexible) way of setting up would be to assign consecutive cc numbers to consecutive faders in scope (starting with, say cc33, then cc34 etc.) on the SAME MIDI channel. You would, of course, need to make sure that none of these cc numbers conflicts with any other controls you may have set up that use the same MIDI port.

I hope this helps.

The same thought I had, speaking on the use of controller #7.
I just was expecting CRein coming with that discovery by him self
all information was in my post, only the conclusion had to be drawn
Let's see if he yet has a bug or it was him.

CRein, you better don't use controller #7 for specific destinations.
It's good use to reserve it for master volume controls, specificly of instruments.
It's a master volume controll for the current Midi channel.
You wouldn't like to have to have the Pan controller (#10) for that, isn't it?
It is possible tho
The controller's naming is for convenience and compatibility between project files in general (between studios f.e.).
It also helps you to keep uniform settings in your different projects, you can make templates where possible

Like Badger says, use controllers up in the rank to serve different faders.
look at the list on the left on this page:
http://www.borg.com/~jglatt/tech/midispec.htm
It declares a lot on it's own

Thanks guys for your help i will let you know how it goes when i get scope back up. I went thru a computer crash and when i reopened scope after trying to select a project all of the presets were bright blue . I could still select them and they would open but something must have gotten screwed up bigtime.

sorry to hear that

did you save your preset file (in the right preset window) to your song folder?
When you then safe the project, SFP asks you to confirm if the change in the right preset list should be saved...to be in the project itself that is

thanks for the tip hubrid, but it just wasnt the the presets it was other stuff too. When i went to the scope folder there were many things that were now bright blue, i think its when the file is supposedly missing when its blue like that but everything seems to work when selected, i just dont understand why the color change, its strange.

STM 24/48 also works fine with controllers.
After rebooting/restart SFp everything is still there
Only strange thing is, the mixer does only react to Midi channel one, or at least my PC1600 spits all data out on channel one, even when faders are programmed for another channel.
Hm, strange problem that I didn't see before.

the folder i should have said was the examples folder that were all in blue letters the ones creamware already made but there were some that didnt change and looked normal, black lettering. I reinstalled scope and everything looks normal now.

Since we are talking so much on mixers has anyone felt a mixer was what made their setup more productive?

Anyone else like to add anything that made SFP a better experience in their music?