PlanetZ forums - scopeusers.com

Anybody has the same problem, that when moving mixer faders & co. on basssounds there is a digital noise in the background?
It happens also when interpolating faders. Strange.

With this "passive" faders I heard no noise. I will use them now to midi-control (bass) sounds with fast volume change.

Martin

EDIT:
- Version2 with controllable reacting-time.
- Yes, nothing special, but usefull

I like the way that when something in Scope bothers you, SDK can make a fix.

I wish I had the knowledge that you guys have aquirred.

Thanks, I will see if I find a use also.

Version 2

I am downloading it again. Version 2 'eh.

I was always wondering what this was in my CW folder.

I check this baby out, ankyuvarymush.

Version 3 will come with exponential fader-behaviour-control
& still it will be the most simple device

Thanks for uploading the new version. Unfortunately it still cannot keep up with rapid volume changes via MIDI. It skips some of the changes.

Hm. I'd bet that that's a midi-problem. Should have nothing to do with the internals which are (except the fader itself) at sync-speed & I haven't seen any sync faders yet within sdk.

I will try 2 things next, which could change something again to positive, but I can't promise anything.

Midi definitively has some limits concerning control changes-speed, because with fast movements there is a hughe amount of data to be transferred (compared to the capabilities of midi).

i would also suggest a Gate for your use peksi.

MCCY wrote:Midi definitively has some limits concerning control changes-speed, because with fast movements there is a hughe amount of data to be transferred (compared to the capabilities of midi).

on the contrary, it has much less data with fast movements (it goes faster from start to end and doesn't have to go through all values).

the problem seems to me to be caused by peski trying to make a volume gate out of his mixer. in scope there much better ways to do this (devices, modular patches etc).

You're right of course. Another point learned. I'm not a MIDI-expert.

I allways feel proud having an answer from one of the real big ones here on my threads. Thanks Mehdi!

In fact I meant that there can't be more than 127, and that for fast movements there should be less (as drawn in a sequencer for ex, i'm not talking about live". fast movements on faders shouldn't be a problem neither (i sometimes assign a button to an aux send, or other controls, and it works fine, goes straight from 0 to 127, and from 127 to 0). But may be i'm missing something here (not sure what is the problem in fact)

mccy: you're welcome

It's possible to get 14-bit midi control in sfp giving you a range of 0-16383 (internally scaled to the full 32-bit range). It would be cool to build at least one such control into our devices as a modulator that could be assigned to whichever parameter the user chooses.

I can't figure out why no one has developed a new MIDI protocol (MIDI 2, MIDI Pro, or something) and let synths and DAWs begin to use it. This 128-step limitation is ridiculous in 2007. We're using almost 25-year-old technology here!

Shayne

Shayne White wrote:I can't figure out why no one has developed a new MIDI protocol (MIDI 2, MIDI Pro, or something) and let synths and DAWs begin to use it. This 128-step limitation is ridiculous in 2007. We're using almost 25-year-old technology here!

Well there is Turbocharged MIDI. Only problem is only Elektron devices use it.

The elektron turbo midi is just standard midi protocol. It's only called turbo because it's a method of delivering midi to the SPS-1, UW etc much faster via USB (afaik).

OSC is the replacement for MIDI - slowly but surely

(p.s. 14 bit NRPN midi has been around for 20 years also - so there are existing standard to get around the 128 level problem - just not used as it should be)

I have this strange embedded memory of reading an article in Practical Electronics in about 1982 (yes I was a teenage geek) shortly after midi was invented about how it was too limited and would not last long!

husker wrote:(p.s. 14 bit NRPN midi has been around for 20 years also - so there are existing standard to get around the 128 level problem - just not used as it should be)

Yep, it's implemented differently from product to product, especially since continuous rotary encoders became common on midi controllers. Different controllers have different downfalls though. The behringer BCR/BCF NRPN implementation isn't a fully blown NRPN spec, while a Kenton Control Freak or Peavey PC-1600 do have a fully blown NRPN spec but don't make full use of it because you can't get a good feel for a 0-16383 value range on a 60mm Alps fader.

My control changes are quite simple and quick: just 0s and 120s a few times in a second. It is not a problem with midi since it can easily be done with the Scope's ControlRoom mixer device's input and outputs. Especially the input is precise as hell but it also makes a little *snap* sound when making changes, output does not make the sound but is too smooth.

husker wrote:OSC is the replacement for MIDI - slowly but surely

still seems to be more slowly than surely at the moment though
OSC has been around for a while but AFAIK still none of the major sequencers support OSC at this point and until at least one of them starts supporting it I don't see it replacing midi any time soon.
We'll have to wait and see if Scope 5 will support it but tbh I don't expect it will.

the question is... WHY NOT?

(if it does I will gladly eat my words though)