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: 121153" data-attributes="member: 1285"><p>Re: S16 and phantom pops</p><p></p><p></p><p></p><p>If indeed it is the case that changing the routing from from presumably AES50 A17-32 to AES50 A33-48 as source for channels 17 -32, with no other action involved, disengages the phantom on the second S16 (AES50 A17-32), than that clearly is a bug that needs to be addressed.</p><p></p><p>A slightly different wording in our private exchange left me with the impression that the chain of events in your test was slightly different, sorry.</p><p></p><p></p><p>- The preamp page controls 128 possible preamps, all of these settings are saved in the last section of the scene file.</p><p>- When preparing a scene and addressing these preamps, irrespective of whether one is using the preamps page or the channel settings, the scene file generated is exactly the same. </p><p>- When setting the the phantom from the channel view or using the phantom button on the surface, the phantom is also on in the preamps view.</p><p></p><p>If any of this changes when connecting extra S16s, as opposed to virtual S16s, then there clearly must be a bug that needs to be addressed.</p><p></p><p></p><p></p><p>If for some inexplicable reason phantom needs to be set from the preamps page to be stable, I'm quite happy to do so, and running a second CAT to avoid going into the preamps page surely seems a bit excessive.</p><p></p><p>Let's document the bug if there is one, and move on</p></blockquote><p></p>
[QUOTE="Per Søvik, post: 121153, member: 1285"] Re: S16 and phantom pops If indeed it is the case that changing the routing from from presumably AES50 A17-32 to AES50 A33-48 as source for channels 17 -32, with no other action involved, disengages the phantom on the second S16 (AES50 A17-32), than that clearly is a bug that needs to be addressed. A slightly different wording in our private exchange left me with the impression that the chain of events in your test was slightly different, sorry. - The preamp page controls 128 possible preamps, all of these settings are saved in the last section of the scene file. - When preparing a scene and addressing these preamps, irrespective of whether one is using the preamps page or the channel settings, the scene file generated is exactly the same. - When setting the the phantom from the channel view or using the phantom button on the surface, the phantom is also on in the preamps view. If any of this changes when connecting extra S16s, as opposed to virtual S16s, then there clearly must be a bug that needs to be addressed. If for some inexplicable reason phantom needs to be set from the preamps page to be stable, I'm quite happy to do so, and running a second CAT to avoid going into the preamps page surely seems a bit excessive. Let's document the bug if there is one, and move on [/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!