Extra notes and artifacts in WB

[LucidMusic]

Has anybody else experienced this:
When I run WB in stand alone mode, the key that I trigger on the midi controller does not match up with the key playing on the Kompakt. It is off by a consistant interval. Sometimes it might be a half tone, other times it might be a minor third. For example, I play an F on the controller and on screen an E goes down. What happens next is that as I release the note on the keyboard, another unrelated note on the Kompakt, usually two octaves in either direction goes down and creates and audible artifact, just a short blip of it's corrosponding note. I do not experience this when running WB as a plug in within my sequencer. I prefer working out the Votox in stand alone mode though because I can work in full screen. I am stumped. It would seem it is a midi issue and I have tried to isolate it. I have used both a USB controller keyboard and also run straight midi from another controller's midi out into the PCI based audio card's midi in but that has no affect. If it is a setting in the Kompakt, such as a filter, I can't find it and as I said it doesn't occur when I run WB and SC from within the sequencer. Any thoughts would be welcome.
Tom

Pentium IV windows XP pro 2 gigs of ram

[George Bellas]

Has anybody else experienced this:

For example, I play an F on the controller and on screen an E goes down. What happens next is that as I release the note on the keyboard, another unrelated note on the Kompakt, usually two octaves in either direction goes down and creates and audible artifact, just a short blip of it's corrosponding note.

Yes, this happens on my setup too. MacOSX 10.4.2, Logic Pro 7.1.1, WB 1.0.7, 1.0.8a, 1.0.9a (stand alone)

The extra erroneous notes have been showing up on my Score since I received the SC package back in May. I have been in contact with the developer and also a few people at EW's tech support to no avail. I was told that it was Logic's fault and has nothing to do with WB.

Hopefully this next WB update will sort this issue out.

[LucidMusic]

Thanks George for your input

Apparantly the problem has little or nothing to do with Logic. I paid closer attention to it today while in the studio and it can be quite a distraction. However if I run WB and SC from withing Sonar the notes on the Kompakt match up with the midi controller keys I am playing and the extraneous notes and artifacts don't occur. The audio track comes out clean. That leads me to believe that at least on my system it has something to do with the virtual midi connection between WB and SC when running in stand alone mode. I have checked and rechecked this several times but everything seems correct. When running as a plugin within Sonar this midi connectioin is handled automatically in the background. The fact that it is occuring under different circumstances and on different platforms would seem to indicate the problem may be difficult to track down. I guess the good news is that it is very repeatable and it is always easier to fix something that stays broke.
Tom

[kizzah]

I just got EWSC today and am having the same problem. Unfortunately I can't find a way to run EWSC and WB in Ableton Live, and therefore have no choice but to use them in standalone mode. For some reason (don't know if you find this) I only seem to get the artefacts/extra notes when I'm playing below middle C. Weird...

[Sam Fischmann]

When you are seeing these notes, are you using WordBuilder? The reason you see notes going up and down all over the keyboard is that WordBuilder is telling Choirs to play various consonants and vowels. Since the range of a single group in the choir doesn't stretch the whole MIDI keyboard, the consonants and vowels have been mapped in various sections over all 128 keys, throughout the 5 voices that load when you pull up a WordBuilder multi. They don't (and couldn't!) line up to what you physically play on your keyboard. This is why you'd have a lot of trouble trying to play a WB Multi directly.

You often won't see these notes because they're out of the range of the graphical Kompakt keyboard on the screen. I don't think that using WB as a MIDI plugin should cause it to behave differently; if only the notes on your controller were being played, you'd never hear the words you typed in WB.

The extra sounds you hear are most likely WB telling Choirs to play a consonant or vowel at the end of a word, after you release the key on your MIDI controller. Look at the time editor in WordBuilder. In your words, are there any colored bars to the right of the vertical divide? These are the sounds you should be hearing at note-off. If you don't want them there, delete the letter, or move the bar to the left of the divide.

[George Bellas]

The extra erroneous notes have been showing up on my Score since I received the SC package back in May.



Even after updating to Wordbuilder v1.1.0, I am still getting extra erroneous notes showing up in Logic Pro's Score window while using Step Input. It's been 7 months since I purchased EWQLSC and still can't use it to score. I work 99% of the time in the Score window and not being able to use WB/SC is a real bummer.

My System Specs:
*************************
Dual G5 2Ghz (3.5 gigs RAM)
Mac OSX 10.4.2
Logic Pro 7.1.1
Wordbuilder 1.1.0
Symphonic Choirs 1.0.9.001
*************************

I do have WB, SC and Logic setup and cabled precisely as Nuno, Sean and the manual have instructed.

[Doug Rogers]

Even after updating to Wordbuilder v1.1.0, I am still getting extra erroneous notes showing up in Logic Pro's Score window while using Step Input. It's been 7 months since I purchased EWQLSC and still can't use it to score. I work 99% of the time in the Score window and not being able to use WB/SC is a real bummer.

My System Specs:
*************************
Dual G5 2Ghz (3.5 gigs RAM)
Mac OSX 10.4.2
Logic Pro 7.1.1
Wordbuilder 1.1.0
Symphonic Choirs 1.0.9.001
*************************

I do have WB, SC and Logic setup and cabled precisely as Nuno, Sean and the manual have instructed.

As we have told you previously, there is nothing we can do about that, it is a 'Logic' problem that doesn't exist in other hosts and we have been lobbying Apple to resolve this ASAP. If SC users redirect their energy to Apple Logic tech support, this might result in a faster resolution.

- Doug