PlanetZ forums - scopeusers.com

Right now I'm pulling my hair and my computer in my studio is shattered into... well, too many pieces. I'm trying to pinpoint an irritating MIDI problem in my system and I need a reference of some kind.

Been in touch with CW but they haven't got back to me, and guess they won't until the mess with SFP4 registration has been sorted out.

If ANYONE would be interested in helping me out I would be forever grateful (not kidding).

It won't take more than 5-7 minutes and just involved simple routing in the routing windows.

Greetings from (a cold, but sunny) Sweden

Carl.

<font size=-1>[ This Message was edited by: Ganool on 2004-04-27 16:03 ]</font>

Just post your question here.
But before, if you use a keyboard and the OS is crashing with a blue screen, set it so that it doesn't output clock signals (Slave situation).

No. The problem is far more weird than that. Nothing crashes, nothing appears to be wrong ANYWHERE (my computer is in fact rock-solid and extremely rarely crashes).

I'm more and more getting the feeling I've stumbled upon a huge bug. The only thing is that it's so blooooody huge, and me being the first person to find it is way unlikely.

But I just can't see any other way it could be. I've just set up a fresh installed computer, with new OS, new motherboard and new processor (AMD instead of Intel).

Same problem.

INSTRUCTIONS

Load a synth into the routing area.

I use the Uberplastic demo (http://www.track0.com/wavelength/) because it's quite complex and gives very obvious results.

Listen to some of the sounds so you get a brief idea how the sound.

Right-click on the first knob so you can input a MIDI CC. I've started with MIDI CC #75.

You can do this manually.

Assign all parameters in OSC 1, OSC 2, MIXER and FILTER to a unique MIDI CC. You can't go higher than MIDI CC #119. SFP appears to not assign codes that high (no big problem).

Change preset and listen.

Now the sound is COMPLETELY different.

Or? Are there ghosts in my cards or can anyone else notice the huge difference?

Carl.

<font size=-1>[ This Message was edited by: Ganool on 2004-04-27 14:35 ]</font>

Isn't this the same problem as this? Try saving a CC map then load it first, then change the presets and see what happens.



<font size=-1>[ This Message was edited by: Mr Arkadin on 2004-04-27 14:46 ]</font>

ditto mr. arkadin's post....

Yes. It's the same problem, but why I'm bring it up again is that I just want to make sure that this is a bug and nothing in my system.

Got a mail from Wavelength and he told me he didn't have any problems with MIDI CCs.

I actually found a work-around re. the Pro-One, but that just ended up with me having done some 30 patches which in fact are unusable.

I'll try loading the MIDI CC map before. And post my results.

Garyb & Mr. Arkadin:

No that did not change the situation the slightest.

I first assigned the MIDI CC codes and saved the template in the preset file. Then I unloaded the synt from the memory and loaded it again. Recalling the MIDI template and after that I tried the patches. The presets are still in a mess.

A new observation.

If I use older devices, which do not use the new preset-selector, but the old big chunky blue one, there are no problems what so ever.

Just tried Orbitones Synchrome and it works just as it should.

Hm. I'll give CW another call tomorrow, and see what they've got to say. Will wait with buying that Scope Pro card for a while.

On 2004-04-27 14:34, Ganool wrote:
You can't go higher than MIDI CC #119. SFP appears to not assign codes that high (no big problem).

These high CC#'s are reserved for Channel Mode messages as per MIDI specs and they are not commonly used to tweak knobs:

120 All Sound Off
121 All Controllers Off
122 Local Keyboard (on/off)
123 All Notes Off
124 Omni Mode Off
125 Omni Mode On
126 Mono Operation
127 Poly Operation

<font size=-1>[ This Message was edited by: at0mic on 2004-05-03 21:28 ]</font>

Gave CW a call again, and they promised to look into it. Send the problem to their technicians blah blah blah.

It's just that this is the third time they say that. They don't reply my mails. Not even a confirmation they received it. I've been trying for weeks.

Carl.

Got a mail from Ralf saying their technicians are looking into it. Good...

Have anyone else tried assigning MIDI CCs with their systems? Would be nice to hear your experiences and ways how you work around this problem.

Hi Ganool,

i forwarded this thread to our developers.
We have to check out if it is a private system bug or a global one in the SCOPE PLATFORM 4.0 ( because i cannot reconstruct this failure ).

Moreover . . . if i will start to inform all senders that a mail was received, than my work still becomes more difficult than it is now - not possible and i hope for your understanding.


cheers
Ralf

On 2004-04-28 07:52, Ganool wrote:
Gave CW a call again, and they promised to look into it. Send the problem to their technicians blah blah blah.

It's just that this is the third time they say that. They don't reply my mails. Not even a confirmation they received it. I've been trying for weeks.

Carl.

On 2004-04-30 16:21, Ganool wrote:
Got a mail from Ralf saying their technicians are looking into it. Good...

Have anyone else tried assigning MIDI CCs with their systems? Would be nice to hear your experiences and ways how you work around this problem.

I have had no end of problems dealing with MIDI CC's and the Creamware card. Whenever I assign CCs directly or recall a preset containing them, the presets generally no longer get called up properly (sometimes you can find workarounds, like certain knobs not to assign in Minimax). Experimenting with the Celmo BAM demo, I can assign a MIDI controller to toggle the 'Bypass' switch (that way I can use a footswitch to help me A/B an effect). I switch to another patch, and the controller stops working; if I right-click on the switch, it's still assigned. If I remove the assigned controller and re-assign it, it works again (till I change the patch). Using the B2003 plugin, any assignments to Rotor Fast/Slow do not get saved as either a Midi Controller Preset or as part of the device when you save it in a project file - I have to re-assign it everytime I load up the project.

My solution is to get the instrument sounding roughly the way you want and cut an audio track of it right away, and hope Creamware eventually fixes all the bugs associated with MIDI CCs. I have spent enough evenings fighting with this, and have never spent 5 MINUTES working out how to use outboard gear with MIDI CCs (they just work and that's that). I like Creamware's general implementation of MIDI CC's, it's very flexible, but until the problems are fixed I won't be using (to the extent I'd like) that particular facet of the cards. Hope I don't offend anyone with this post, I admit I could be missing some detail on the cards' operation, there's lots of details. Also it could be the plugins themselves, if the developers didn't follow Creamware's specs to the letter. The fact that there seem to be different problems in each plugin would support that idea.

On 2004-05-03 16:34, Liquid Len wrote:
I admit I could be missing some detail on the cards' operation, there's lots of details. Also it could be the plugins themselves, if the developers didn't follow Creamware's specs to the letter.

What goes for you goes for the development: there is no CW specs, there is DP. Every DP'er implements available options how he wants and feels necessary, within his possibilities, just like we do with SP4/SFP.

On 2004-05-03 14:38, Ralf wrote:

i forwarded this thread to our developers.
We have to check out if it is a private system bug or a global one in the SCOPE PLATFORM 4.0

Moreover . . . if i will start to inform all senders that a mail was received, than my work still becomes more difficult than it is now - not possible and i hope for your understanding.

Ralf,

I am aware of your awful situation right now, and I hope the flood of support mails will end soon.

I actually spent last weekend building up a new computer (new motherboard, new processor) and installed Scope 4 into a fresh WinXP Pro. The same bloody results.

As I never rely on presets when making music MIDI CCs is fundamental for my music. Right now my 16 DSPs can only be used for advanced signal processing (which is not bad).

If you want, I can write down a complete step-by-step guide how I can reproduce these problems with MINIMAX, Pro-One and Überplastic.

Regards,

Carl.

Hello,

yes, please write what you're doing exactly.
I will try to check and reconstruct.

cheers
Rakf

I had a problem like that because of cubase sending CC information (automation) that coresponded to the midi CC of the device (some track CC in SX are "fixed"). It reseted some controllers on loop start (seq start). A part from that, no problem, but i don't use a lot of CC so I can't really tell.

<font size=-1>[ This Message was edited by: spacef on 2004-05-05 01:31 ]</font>

Alright... I'll upload an even more extensive description.

and please to rb@creamware.de


cheers
Ralf

On 2004-05-05 03:37, Ganool wrote:
Alright... I'll upload an even more extensive description.