Jump to content

Banging all channelstrip values


gummigudm

Recommended Posts

I know that i'm not able to bang plugin parameters with regular methods, but I just noticed that the values of my sends do regularly not get sent. I thought I could send them all using a meta button with output meta 1 -99- but now i see, that only sends 1,2,3 and 4 get sent, as control messages but not fader?, insert status (on/off) and sends 5678 don't get banged out of channelstrip?

I would expect :

F 1 56 through F 1 70 (insert On/Off)

F 1 28 through F 1 35 (send amounts)

C 1 7 (volume)

C 1 10 (pan)

F 1 3 (solo)

F 1 9 (mute)

 

But i get :

C 1 28 through C 1 31 (send amounts) (notice C and only to 31, not 35!)

C 1 7 (volume)

C 1 10 (pan)

C 1 3 (solo) (notice C!)

C 1 9 (mute) (notice C!)

 

somthing i'm missing?

 

-G

Link to comment
Share on other sites

Define "normal"! :mrgreen: Seriously: not that I have a whole ton of experience banging channel strips, but since it's the results you're getting and I can verify those same results here with another version of Logic on another version of OS X etc... then that's what we have to work with.

 

Using other meta events you could store those values in different ways. For example Meta #98 sets a fader value. Cabling the output of a channel strip into a transformer set as below cabled into a fader will "store" the volume value in the fader:

 

914534864_Picture5.png.3269d771ec6d6c09cc6ce071e7f5a90f.png

Link to comment
Share on other sites

Yes, I always get the last send value twice.. That however does not affect what i'm doing;) i can successfully store the values within transformers, id just rather not tweak each parameter to get the channelstrip to send each value out. My workaround idea was to somehow increase the value by one and decrease again, so the value set, would be the latter and would get to my transformers and change them again after the increment of one.. have no idea how to make this possible though.
Link to comment
Share on other sites

My workaround idea was to somehow increase the value by one and decrease again, so the value set, would be the latter and would get to my transformers and change them again after the increment of one.. have no idea how to make this possible though.

That's a smart workaround idea - unfortunately apparently increment/decrement with Meta #99 doesn't seem to work with channel strips objects. :(

Link to comment
Share on other sites

I've mangaged to keep hold of my information, after initially setting them once! using two large arrays of transformers that do exactly the same thing. Every fader/knob/status on the channelstrip is tweaked once, initially, this sends the information which gets changed to meta and values are stored as 'fix' in databyte 2 in the transformers.. once happy those values get banged (stored) to a second array which stores the same data. changing values after the 'store' only affects the first array and i can keep other info for A/B comparisson with two of those array setups. (current data, saved data) Since the transformers save the position and not faders, they get stored even though i close and reopen my project!

These speculations led to a result! Fantastic! :mrgreen:

Link to comment
Share on other sites

ofc! didn't realize that:s.. there was some scenario where i used the transformer to store the value as well as changing other databytes at the same time.. guess that got me stuck on that idea;) Damn I'm glad that you pointed that out to me, very basic fact i turned my head away from.

But having to do a transformer operation, where i can store data within the same transformer, I would not be benefitting from having a fader store the value externally from the transformer that has to be there anyway?

Link to comment
Share on other sites

Stable result, sure, no reason why not. But I'm not talking about stability. Talking about accuracy. In other words, if your intention is to store (say) channel strip fader values in a transformer for the purpose of reading them back out later, you'll find that your faders will not always return to the value you think you stored.
Link to comment
Share on other sites

Aah i understand, yeah i knew that the division of info between 128 values yealds a slight ofset from the original data. And that ofc goes the same for faders as transformers.

The reason I am doing this is not for an accurate snapback console, but rather simpler tasks of storing multiple cue mixes on one bus and for A/B comparisson of a few elements at a time :)

I am f.ex. recording vocals and the three singers have different preference in what they'd like to hear while recording.

Its convenient to have a small framless floating with a dropdown menu of different presets of cuemixes, than using multiple sends and routing them to multiple outputs and whatnot.

Same booth, same headphones, same output, same send, different cue mixes. Works for me.

Link to comment
Share on other sites

Using a transformer to store a value seems overkill, especially if you're working with large environments...

 

On that note, what do you guys use for summing of signals? I often find myself cabling multiple objects to one transformer for summing to one line. That transformer is nonfunctional and only takes in all midi values and spits them out again (thru). I use this alot for a 'Macro-In' or 'Macro-Out' object.

Would it take less prosessing to use a monitor perhaps, for this purpose -- or does it not matter since there is nothing going on inside the transformer?

 

These changes are completely irrelevant in small setups, but with large environments, would this render a difference?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...