BrainModular

Conductor PM recall problem

2011-07-18T23:36:39+02:00

oh,right--thanks!

Statistics: Posted by woodslanding — 18 Jul 2011, 23:36

Conductor PM recall problem

2011-07-18T21:11:17+02:00

Not in the menu, but probably on the top of the sub patch editing window

Statistics: Posted by GDLive — 18 Jul 2011, 21:11

Conductor PM recall problem

2011-07-18T20:00:37+02:00

I cannot figure out how to set the subpatch to 'not stored in conductor'.... it is not in the context menu for the subpatch.....

Statistics: Posted by woodslanding — 18 Jul 2011, 20:00

Conductor PM recall problem

2011-07-18T19:13:21+02:00

I'm not sure what you mean by target busses. The recieves don't have control of scope, only the sends right? I had all the sends set to 'top parent patch'. I figured I should use the smallest scope that is appropriate--is there a reason to prefer 'track only'?

Well, I changed them to track only, and also I tried removing the txtIN cable, and when that didn't work, I did one better--I removed the textfield object, and both the inputs to the script for it. I'd already taken all the processing for those inputs out of the script (to correct a much worse bug), and it compiled with no other changes.

It still exhibits the same symptom for me here.....

Maybe storing outside the PM is the only solution. I wil try that.

Thanks!
-e

EDIT: uploaded patch with fix....

http://www.sensomusic.com/forums/upload ... _23fix.zip

Statistics: Posted by woodslanding — 18 Jul 2011, 19:13

Conductor PM recall problem

2011-07-17T16:20:42+02:00

in PM subpatchs, dewire the txtin comming from the Pttextfield (it is stored inPM and so changes with it and might interfere)
also try to add setdonsave(txtin,true); in booth Pm scripts in init (idem, by default Pttextfield pins are saved) and
also im not sure but by security try to sel all your target busses you added in 256PM subpatchs to 'track only' as there are multiple same name send buses in the wksp. . here doing all of this the names seems to behave correctly.

Or the other solution could be to set booth your PM patchs to "not stored in conductor/preset", and put something to be stored at the upper level (ie fader recalling NUM)

Statistics: Posted by 23fx23 — 17 Jul 2011, 16:20

Conductor PM recall problem

2011-07-17T06:49:25+02:00

I have two near-identical channels in my mixer, each with a PM256 that I use to recall Kontakt patches (which can't be recalled via normal program changes.) The selected name from the list which controls the PMs is used to update the text in the slider which controls that patch's volume. I am commonly getting text from one of the PM lists sent to both sliders, even though they are on different channels, and the scope of both sends is 'track'. But, it doesn't happen every time.

http://sensomusic.com/forums/uploads.ph ... llProb.zip

The names of the conductor presets show the names for the sliders. Try using the arrows to move through the conductor presets, and see what comes up for the fader names. On my computer, I get wrong names for the faders anywhere from 5% to 50% of the time. I can't figure out why.

I replaced Kontakt with Synth1, for compatibility, before posting the WKP, but the symptom is exactly the same (though of course the PMs don't actually recall anything anymore)

There is a patch clock in one of the channels' gui subpatches, but I just removed it, and still get the same results

Any ideas????

EDIT: I should add that when the names come up wrong, the PM loads the wrong sound as well.....

Thanks!
-eric

Statistics: Posted by woodslanding — 17 Jul 2011, 06:49

Conductor PM recall problem

2011-07-18T23:36:39+02:00

oh,right--thanks!

Statistics: Posted by woodslanding — 18 Jul 2011, 23:36

Conductor PM recall problem

2011-07-18T21:11:17+02:00

Not in the menu, but probably on the top of the sub patch editing window

Statistics: Posted by GDLive — 18 Jul 2011, 21:11

Conductor PM recall problem

2011-07-18T20:00:37+02:00

I cannot figure out how to set the subpatch to 'not stored in conductor'.... it is not in the context menu for the subpatch.....

Statistics: Posted by woodslanding — 18 Jul 2011, 20:00

Conductor PM recall problem

2011-07-18T19:13:21+02:00

Statistics: Posted by woodslanding — 18 Jul 2011, 19:13

Conductor PM recall problem

2011-07-17T16:20:42+02:00

Statistics: Posted by 23fx23 — 17 Jul 2011, 16:20

Conductor PM recall problem

2011-07-17T06:49:25+02:00

Statistics: Posted by woodslanding — 17 Jul 2011, 06:49