Log in
Register
Home
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Kevin Hunter" data-source="post: 98196" data-attributes="member: 2008"><p>Re: X32 Sync Link - Version 0.4 Beta</p><p></p><p></p><p></p><p>Hi Mark,</p><p></p><p>sucks eh ! If the value sent by OSC was the Same as what the console stored then this would be easy :razz:8)~<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite6" alt=":cool:" title="Cool :cool:" loading="lazy" data-shortname=":cool:" />~<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite6" alt=":cool:" title="Cool :cool:" loading="lazy" data-shortname=":cool:" /> but that's the way it is lol</p><p></p><p>I would say you need an individual routine for each fx type and you can then hard code the number and types of parameters. </p><p></p><p>I will have a look later but I'm surprised it sends the parameters first before the fx type.</p><p></p><p>if that is true then you could set up a 64 parameter wide array , store the values until you know the fx type, then process them.</p><p></p><p>Kev</p></blockquote><p></p>
[QUOTE="Kevin Hunter, post: 98196, member: 2008"] Re: X32 Sync Link - Version 0.4 Beta Hi Mark, sucks eh ! If the value sent by OSC was the Same as what the console stored then this would be easy :razz:8)~8-)~:cool: but that's the way it is lol I would say you need an individual routine for each fx type and you can then hard code the number and types of parameters. I will have a look later but I'm surprised it sends the parameters first before the fx type. if that is true then you could set up a 64 parameter wide array , store the values until you know the fx type, then process them. Kev [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
Top
Bottom
Sign-up
or
log in
to join the discussion today!