{"id":3207,"date":"2018-02-22T13:08:05","date_gmt":"2018-02-22T18:08:05","guid":{"rendered":"http:\/\/www.aviom.com\/blog\/?p=3207"},"modified":"2021-12-21T11:59:03","modified_gmt":"2021-12-21T16:59:03","slug":"a360-modes","status":"publish","type":"post","link":"https:\/\/www.aviom.com\/blog\/a360-modes\/","title":{"rendered":"A360 Modes"},"content":{"rendered":"<p><img loading=\"lazy\" class=\"aligncenter size-full wp-image-3241\" src=\"https:\/\/www.aviom.com\/blog\/wp-content\/uploads\/2018\/02\/A360-Mode-Switches-960.jpg\" alt=\"\" width=\"960\" height=\"300\" \/><\/p>\n<p>It&#8217;s important to understand how the A360 Personal Mixer&#8217;s rear-panel switch affects the incoming A-Net digital data. The four-position switch has three channel-based modes and one utility setting. \u00a0Remember, in an A-Net network, <em>all<\/em> channels are available in <em>all<\/em> the Cat-5 cables <em>all<\/em> the time.\u00a0\u00a0The A360&#8217;s three channel-based modes essentially act as filters, telling the A360 how to use the A-Net network&#8217;s mono and stereo channels and map them to its channel buttons, using some channels and ignoring the rest.<\/p>\n<h2>Switch Settings<\/h2>\n<p>Not getting the channels you expect on your A360 channel buttons? There are a couple of things to check. Most likely there is nothing wrong with your Personal Mixer. It\u2019s probably just a switch setting.<\/p>\n<p>Here is how the\u00a0rear-panel switch on an A360 Personal Mixer works:<\/p>\n<p>&#8211;\u00a0 In <strong>Pro16<\/strong> mode, the first 16 network channels are mapped to the A360 buttons in numerical order, 1-to-16. All buttons are assumed to be mono. If you only have one 16-channel input module (or digital console card), this is the mode you should be using. The A360 will ignore network channels 17-64 if they exist.<\/p>\n<blockquote>\n<p style=\"padding-left: 30px;\"><span style=\"color: #44697d;\"><strong><em>Here&#8217;s how to test that you have your A360 in its Pro16 mode.\u00a0 <\/em><\/strong><\/span><\/p>\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li style=\"padding-left: 30px;\">Select channel button #1 on the A360; its LED will light to indicate that it is selected.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li style=\"padding-left: 30px;\">Look at the Pan LED in the Stereo Placement section of the A360. There should only be one LED lit.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li style=\"padding-left: 30px;\">Now, at your input device, move the first Stereo Link switch (or DIP switch on a console card) to the <strong>Stereo<\/strong> position. Channel buttons 1 and 2 should both be lit (selected), indicating that they are now a pair. There should be two Pan LEDs lit in the Stereo Placement section for the channel pair.<\/li>\n<\/ul>\n<p style=\"padding-left: 30px;\">You can toggle between the mono and stereo settings at the input device as often as needed while testing. Updates are instant throughout the network. There is no need to power cycle the Aviom devices or your mixing console.<\/p>\n<\/blockquote>\n<p>&#8211;\u00a0 In <strong>Default<\/strong> mode, all A360 channel buttons are assumed to be stereo and network channels are mapped in pairs. A360 channel button #1 uses network channels 1 and 2,\u00a0A360 channel button #2 uses network channels 3 and 4, and so on, up to\u00a0A360 channel button #16 that uses network channels 31 and 32.\u00a0\u00a0The A360 will ignore network channels 33-64.<\/p>\n<p>A stereo channel is always an odd-even pair such as channel 1-2 or 7-8.\u00a0\u00a0The network&#8217;s input devices (multiple AN-16\/i v.2 Input Modules, console cards, or a Dante network) control the stereo pairs globally for the entire network. When a stereo channel is selected on the A360, you&#8217;ll see the Stereo LED in the Stereo Placement section lit, and there will be two Pan LEDs.<\/p>\n<div id=\"attachment_3245\" style=\"width: 970px\" class=\"wp-caption aligncenter\"><img aria-describedby=\"caption-attachment-3245\" loading=\"lazy\" class=\"wp-image-3245 size-full\" src=\"https:\/\/www.aviom.com\/blog\/wp-content\/uploads\/2018\/02\/Two-stereo-views.jpg\" alt=\"\" width=\"960\" height=\"400\" \/><p id=\"caption-attachment-3245\" class=\"wp-caption-text\">The left example shows a mono channel; only one Pan LED is lit in the Stereo Placement section of the interface. On the right, a stereo channel is selected. The Stereo LED is on and there are two Pan LEDs lit.<\/p><\/div>\n<p>To use a mono source (like a vocal or a kick drum), assign it to the odd-numbered channel and leave the Stereo Link set to mono. The even-numbered channel is ignored.<\/p>\n<p>This post explains stereo pairs in more detail:\u00a0\u00a0<a href=\"http:\/\/www.aviom.com\/blog\/map-stereo-links\/\">http:\/\/www.aviom.com\/blog\/map-stereo-links\/<\/a><\/p>\n<h4>Advanced Settings<\/h4>\n<p>&#8211;\u00a0 The <strong>Program<\/strong> mode is for saving\/loading data via the USB port. All mixing functions are disabled while the switch is in this position.<\/p>\n<p>&#8211;\u00a0 <strong>Custom<\/strong> mode assumes you have created and loaded a custom channel map to rearrange the incoming network channels on an A360\u2019s channel buttons. You can make a custom channel assignment using the free <a href=\"http:\/\/www.aviom.com\/AviomSupport\/A360_Channel_Manager\/A360_Channel_Manager_v3014.zip\">A360 Channel Manager<\/a> software. Remember, set up your stereo links first at the input source.<\/p>\n<p>This post explains the use of<a href=\"http:\/\/www.aviom.com\/blog\/using-a360-channel-manager\/\"> A360 Channel Manager<\/a> in more detail.<\/p>\n<p><a href=\"http:\/\/www.aviom.com\/blog\/using-a360-channel-manager\/\"><img loading=\"lazy\" class=\"size-full wp-image-2061 alignleft\" src=\"https:\/\/www.aviom.com\/blog\/wp-content\/uploads\/2015\/03\/A360-Channel-Manager_450x300.jpg\" alt=\"\" width=\"450\" height=\"300\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn how the A360 4-position switch affects its use of the incoming A-Net data. <\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[59,89,71,58],"_links":{"self":[{"href":"https:\/\/www.aviom.com\/blog\/wp-json\/wp\/v2\/posts\/3207"}],"collection":[{"href":"https:\/\/www.aviom.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.aviom.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.aviom.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.aviom.com\/blog\/wp-json\/wp\/v2\/comments?post=3207"}],"version-history":[{"count":28,"href":"https:\/\/www.aviom.com\/blog\/wp-json\/wp\/v2\/posts\/3207\/revisions"}],"predecessor-version":[{"id":3406,"href":"https:\/\/www.aviom.com\/blog\/wp-json\/wp\/v2\/posts\/3207\/revisions\/3406"}],"wp:attachment":[{"href":"https:\/\/www.aviom.com\/blog\/wp-json\/wp\/v2\/media?parent=3207"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.aviom.com\/blog\/wp-json\/wp\/v2\/categories?post=3207"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.aviom.com\/blog\/wp-json\/wp\/v2\/tags?post=3207"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}