Log in
Register
Home
Forums
New posts
Search forums
What's new
Featured content
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
What's new
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="Per Søvik" data-source="post: 66841" data-attributes="member: 1285"><p>re: X32 Discussion</p><p></p><p></p><p></p><p>I totally get you, as someone who relies on meters to set a lot of things in a live situation, my ears are basically worthless (or at least I'm afraid they are) and any help I can get is greatly appreciated. However, short of having a meter post filter, aren't we reasonably well served by the reduction meters on the main display? They are certainly beating the reduction meters on the gates/compressors in my rack. </p><p>Experience have also told me time and time again to not fiddle with these things after the sound check, and adding tools that in theory would help me immensely, like rta on solo outs and what have you just seems to add to the things to ignore when I feel like starting to make mistakes :razz:</p><p></p><p></p><p></p><p></p><p>Yes, annoying one that, but given that you can only trim 12dB unless you reroute, in the future I'm going to normalize to -6 dB. I don't agree that the clip light should only come on at real clip, that is like having the first warning sign telling you: "Warning! You have just driven off a cliff".</p><p></p><p></p><p></p><p>Yes the scenes are OSC, but not the exact format, so translation is needed. Most of it makes sense though so shouldn't be too hard once we get the hang of it.</p><p></p><p>Touch isn't different from any other controller as far as I can tell, the daw registers movement of the fader as touch and can either latch or release after the movement is finished. Since actual touch is not detected, keeping the finger on the fader won't keep the daw in write mode if you're in non latch mode, and I'm still waiting to see a good piece of software to detect resistance in the fader when daw tries to move and thus keep the automation in write mode (isn't this how most controllers gets worn out or ruined?)</p><p></p><p>Have a look at <a href="http://www.x32user.net" target="_blank">www.x32user.net</a> for some more in depth on the subject of OSC etc, would be good if the whole x32-related developer/hacker community could post or link their stuff there for everybody to enjoy when it is not really suited for the mainstream of this forum.</p></blockquote><p></p>
[QUOTE="Per Søvik, post: 66841, member: 1285"] re: X32 Discussion I totally get you, as someone who relies on meters to set a lot of things in a live situation, my ears are basically worthless (or at least I'm afraid they are) and any help I can get is greatly appreciated. However, short of having a meter post filter, aren't we reasonably well served by the reduction meters on the main display? They are certainly beating the reduction meters on the gates/compressors in my rack. Experience have also told me time and time again to not fiddle with these things after the sound check, and adding tools that in theory would help me immensely, like rta on solo outs and what have you just seems to add to the things to ignore when I feel like starting to make mistakes :razz: Yes, annoying one that, but given that you can only trim 12dB unless you reroute, in the future I'm going to normalize to -6 dB. I don't agree that the clip light should only come on at real clip, that is like having the first warning sign telling you: "Warning! You have just driven off a cliff". Yes the scenes are OSC, but not the exact format, so translation is needed. Most of it makes sense though so shouldn't be too hard once we get the hang of it. Touch isn't different from any other controller as far as I can tell, the daw registers movement of the fader as touch and can either latch or release after the movement is finished. Since actual touch is not detected, keeping the finger on the fader won't keep the daw in write mode if you're in non latch mode, and I'm still waiting to see a good piece of software to detect resistance in the fader when daw tries to move and thus keep the automation in write mode (isn't this how most controllers gets worn out or ruined?) Have a look at [URL="http://www.x32user.net"]www.x32user.net[/URL] for some more in depth on the subject of OSC etc, would be good if the whole x32-related developer/hacker community could post or link their stuff there for everybody to enjoy when it is not really suited for the mainstream of this forum. [/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!