Logic matrix edit resolution

[bluey s]

Hi,

I am having a bit of trouble recording FSVA midi cc sweeps and then editing them in the logic matrix editor.

1. I assign midi cc 74 (the standard filter cutoff controller) to the cutoff in FSVA with "midi learn".

2. I record some sweeps going from zero right up to 127

3. I open the resulting region in the matrix editor to edit the sweeps

The problem is that the data shows up in three course steps rather than full range curves.
If I move the region to another midi track the data displays as it should but when I have the region on a FSVA track the data reverts to the course steps.
It plays back normally but can't be edited.

Is FSVA forcing some sort of incorrect data display on the track or is there a setting in logic which I should know about? Or am I just unlucky to be having a problem which no one else has ever heard of?

Any insight would be much appreciated

Bluey[/img]

[Urs]

Hiya,

First off, I have absolutely no idea why this would be.

Does this also happen with other knobs?

Could it be that there's 2 tracks for the sweep, one Midi (as desired) and one track automation? If so, can you just delete the track automation?

What if you do not record anything but use the Hyper Edit directly? (You mean the Hyper Edit window below the Matrix Editor?!?)

Which version of Logic do you use?

Cheers,

Urs

[bluey s]

Hi,
No there is no track automation data. If I start with a blank region in the hyper editor the result is the same.
One thing I noticed is that the three steps of data are named "few", "medium", and "many". These would seem to be parameters for the voices in FSVA but I am editing cc74.

I tried removing my autoload and starting with a default song but get the same results.

I'm using logic 6.4.3

Thanks

[Urs]

Hi,
No there is no track automation data. If I start with a blank region in the hyper editor the result is the same.
One thing I noticed is that the three steps of data are named "few", "medium", and "many". These would seem to be parameters for the voices in FSVA but I am editing cc74.

I tried removing my autoload and starting with a default song but get the same results.

I'm using logic 6.4.3

This is really confusing... "few", "medium" and "many" sounds very much like the track automation output for the number of voices parameter

How do you midi learn? - I can't remember if there was midi learn built into Logic 6.4 already (and my developer license for Logic is only 7, not 6 anymore ).

When you play back the track, does the number of voices change in the FSVA editor (Global section at the bottom of the window)?

To me it looks like there's something going wrong with the assignment in Logic, or maybe the midi learn table in FSVA is corrupted.

Can you send me the file Macintosh HD/Users/Yourname/Library/Application Support/u-he/com.u-he.FilterscapeVA.midimap.txt - I'd like to check if there's a problem with Midi learn assignments...

Cheers,

Urs

[bluey s]

mmmm, I noticed I'm getting similar things with other Virtual Instruments so maybe this is not a Filterscape issue. Plugsound keyboard inst for example restrains the cc74 matrix view to values 0 to 100. Any cc over 100 are just shown as 100.
When I move the sequence to a FSVA track they show as "few", "medium", and "many" and when I move it to an unassigned track the view as normal sweeps from 0 to 127.
I am working with a fresh os and logic install.

No the voices setting doesn't move when I play through the data but the filter does.

bluey

[Urs]

Wow. This is really weird. I would then guess that there's indeed a problem in Logic 6.4.3. It looks like it's triggering the correct MidiCC but then taking the meta information from an arbitrary parameter to display meaningful values.

I'm afraid that this might not be a solvable issue. If it's a bug in Logic, they won't fix it anymore and instead insist on 7.1.

Hmmm... What happens when you use another CC for the Cutoff? - Maybe you can use a transformer to map it to a CC who's "wrong" meta information has high resolution?!?

Cheers,

Urs

[bluey s]

Thanks for the reply Urs,
Yes your work around does work.
possibly an easier one for me is to create a new instrument in the environment and then cable that to FSVA. The data is not then transformed, and is fully editable.
So I can still get the sounds I need out of the little beauty, just a tad more fiddly.

bluey

[Urs]

Yeah... it's weird that such basic stuff needs a workaround

However, I'm glad that you got it to work!

Cheers,

Urs