{"id":402,"date":"2019-10-10T23:49:51","date_gmt":"2019-10-10T23:49:51","guid":{"rendered":"http:\/\/blogs.qsc.com\/systems\/?p=402"},"modified":"2020-08-02T12:46:48","modified_gmt":"2020-08-02T19:46:48","slug":"whenever-possible-go-native","status":"publish","type":"post","link":"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/","title":{"rendered":"Whenever Possible, Go Native!"},"content":{"rendered":"<div class=\"trp_language_switcher_shortcode\">\n<div class=\"trp-language-switcher trp-language-switcher-container\" data-no-translation >\n    <div class=\"trp-ls-shortcode-current-language\">\n        <a href=\"#\" class=\"trp-ls-shortcode-disabled-language trp-ls-disabled-language\" title=\"English\" onclick=\"event.preventDefault()\">\n\t\t\t English\t\t<\/a>\n    <\/div>\n    <div class=\"trp-ls-shortcode-language\">\n                <a href=\"#\" class=\"trp-ls-shortcode-disabled-language trp-ls-disabled-language\"  title=\"English\" onclick=\"event.preventDefault()\">\n\t\t\t English\t\t<\/a>\n                    <a href=\"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/posts\/402\" title=\"Deutsch\">\n             Deutsch        <\/a>\n\n            <a href=\"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/posts\/402\" title=\"Fran\u00e7ais\">\n             Fran\u00e7ais        <\/a>\n\n            <a href=\"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/posts\/402\" title=\"Espa\u00f1ol\">\n             Espa\u00f1ol        <\/a>\n\n            <a href=\"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/posts\/402\" title=\"English (UK)\">\n             English (UK)        <\/a>\n\n        <\/div>\n    <script type=\"application\/javascript\">\n        \/\/ need to have the same with set from JS on both divs. Otherwise it can push stuff around in HTML\n        var trp_ls_shortcodes = document.querySelectorAll('.trp_language_switcher_shortcode .trp-language-switcher');\n        if ( trp_ls_shortcodes.length > 0) {\n            \/\/ get the last language switcher added\n            var trp_el = trp_ls_shortcodes[trp_ls_shortcodes.length - 1];\n\n            var trp_shortcode_language_item = trp_el.querySelector( '.trp-ls-shortcode-language' )\n            \/\/ set width\n            var trp_ls_shortcode_width                                               = trp_shortcode_language_item.offsetWidth + 16;\n            trp_shortcode_language_item.style.width                                  = trp_ls_shortcode_width + 'px';\n            trp_el.querySelector( '.trp-ls-shortcode-current-language' ).style.width = trp_ls_shortcode_width + 'px';\n\n            \/\/ We're putting this on display: none after we have its width.\n            trp_shortcode_language_item.style.display = 'none';\n        }\n    <\/script>\n<\/div>\n<\/div>\n<p>In recent years, the term \u201cnative\u201d has entered the lexicon of the AV industry as the ultimate level of platform integration, and is closely correlated with providing the highest level of customer experience.&nbsp; Make sense on the surface, right?&nbsp; Theoretically, if a solution is \u201cnative\u201d, all of the pieces fit nicely together like a puzzle, requiring less effort for integration and allowing less room for error for the end user.&nbsp; Well, to the astute observer, that\u2019s really only half the story!&nbsp; So what\u2019s the difference between integrated and native?<\/p>\n<p>Let\u2019s take an example from Microsoft. Microsoft Office is native to the Windows OS. Each individual program is tightly tuned to interact well with the other, and moreover, the total experience within the Windows environment seems natural. However, anyone who\u2019s tried to make the transition to the Mac environment knows the pain associated with trying to get the full Microsoft Office experience outside of its \u201cnative surrounding\u201d.&nbsp; Is it technically integrated? Sure. But the cringe-worthy quirks, nuances, incompatibility issues sometimes compel a user to heave their computer out the window!<\/p>\n<p>True \u201cnative\u201d solutions add additional value beyond just being \u201cintegrated\u201d. &nbsp;Of course, we expect a native solution to work seamlessly together across the signal chain (which means less time you need to spend creating those \u201cintegration\u201d points). But you should ALSO expect that by combining all of these native pieces that they maximize the performance AND value of the greater platform. &nbsp;For example, when you combine a given manufacturer\u2019s processor with the same manufacturer\u2019s network amplifiers and loudspeakers, you would expect that not only do these components work together, but the entire system as a whole is performing better than if it was comprised of disparate manufacturer components, right?!<\/p>\n<p>Let\u2019s take that example one step further to issues that are not always apparent on the invoice.&nbsp; A native solution also infers that its manufacturer has fully vetted each component in the portfolio and knows precisely how it performs in the wild, knows its limits, and knows how to troubleshoot the entire system. If you combine a given manufacturer\u2019s processor with NON-NATIVE amplifiers (for example), you are integrating a device that is <em>untested <\/em>and <em>unsupported<\/em> by the processor\u2019s manufacturer.&nbsp; Aside from the added installation time (and cost!), there\u2019s no guarantee the non-native solution will work the way you expect it to. And if that device fails, you might spend more time troubleshooting and potentially more time re-integrating the device, leading to much higher costs over the lifetime of the system.<\/p>\n<p>While no system is completely bulletproof, a native solution means that there is a single source to turn to when issues arise. You get the peace of mind of knowing that someone intimately knows the signal chain of each component and is able to support the whole system.<\/p>\n<p>Native is so much more than being integrated. Native means each component is designed to work seamlessly together AND draw the very best performance across the signal chain in a way that cannot be matched by a disparate collection of non-native devices. It means simpler integration, expedited deployment and an overall better performance for your customers. So next time you are designing an AV&amp;C system, it\u2019s time to go native.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In recent years, the term \u201cnative\u201d has entered the lexicon of the AV industry as the ultimate level of platform integration, and is closely correlated with providing the highest level of customer experience.&nbsp; Make sense on the surface, right?&nbsp; Theoretically, if a solution is \u201cnative\u201d, all of the pieces fit nicely together like a puzzle, &hellip; <a href=\"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/\">Read More<\/a><\/p>\n","protected":false},"author":17,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[28],"class_list":["post-402","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-german"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.9 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Whenever Possible, Go Native! - Q-SYS<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Whenever Possible, Go Native! - Q-SYS\" \/>\n<meta property=\"og:description\" content=\"In recent years, the term \u201cnative\u201d has entered the lexicon of the AV industry as the ultimate level of platform integration, and is closely correlated with providing the highest level of customer experience.&nbsp; Make sense on the surface, right?&nbsp; Theoretically, if a solution is \u201cnative\u201d, all of the pieces fit nicely together like a puzzle, &hellip; Read More\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/\" \/>\n<meta property=\"og:site_name\" content=\"Q-SYS\" \/>\n<meta property=\"article:published_time\" content=\"2019-10-10T23:49:51+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-08-02T19:46:48+00:00\" \/>\n<meta name=\"author\" content=\"Martin Barbour\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Martin Barbour\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/\",\"url\":\"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/\",\"name\":\"Whenever Possible, Go Native! - Q-SYS\",\"isPartOf\":{\"@id\":\"https:\/\/blogs.qsc.com\/systems\/#website\"},\"datePublished\":\"2019-10-10T23:49:51+00:00\",\"dateModified\":\"2020-08-02T19:46:48+00:00\",\"author\":{\"@id\":\"https:\/\/blogs.qsc.com\/systems\/#\/schema\/person\/2ce5a7e361fd40e5e62f120855c0b33c\"},\"breadcrumb\":{\"@id\":\"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blogs.qsc.com\/systems\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Whenever Possible, Go Native!\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blogs.qsc.com\/systems\/#website\",\"url\":\"https:\/\/blogs.qsc.com\/systems\/\",\"name\":\"Q-SYS\",\"description\":\"System Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blogs.qsc.com\/systems\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blogs.qsc.com\/systems\/#\/schema\/person\/2ce5a7e361fd40e5e62f120855c0b33c\",\"name\":\"Martin Barbour\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blogs.qsc.com\/systems\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/356df539b26bd8b0c6352e745715f317a6cded67825b88f84c808d6cef1f413d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/356df539b26bd8b0c6352e745715f317a6cded67825b88f84c808d6cef1f413d?s=96&d=mm&r=g\",\"caption\":\"Martin Barbour\"},\"url\":\"https:\/\/blogs.qsc.com\/systems\/author\/martinbarbour\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Whenever Possible, Go Native! - Q-SYS","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/","og_locale":"en_US","og_type":"article","og_title":"Whenever Possible, Go Native! - Q-SYS","og_description":"In recent years, the term \u201cnative\u201d has entered the lexicon of the AV industry as the ultimate level of platform integration, and is closely correlated with providing the highest level of customer experience.&nbsp; Make sense on the surface, right?&nbsp; Theoretically, if a solution is \u201cnative\u201d, all of the pieces fit nicely together like a puzzle, &hellip; Read More","og_url":"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/","og_site_name":"Q-SYS","article_published_time":"2019-10-10T23:49:51+00:00","article_modified_time":"2020-08-02T19:46:48+00:00","author":"Martin Barbour","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Martin Barbour","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/","url":"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/","name":"Whenever Possible, Go Native! - Q-SYS","isPartOf":{"@id":"https:\/\/blogs.qsc.com\/systems\/#website"},"datePublished":"2019-10-10T23:49:51+00:00","dateModified":"2020-08-02T19:46:48+00:00","author":{"@id":"https:\/\/blogs.qsc.com\/systems\/#\/schema\/person\/2ce5a7e361fd40e5e62f120855c0b33c"},"breadcrumb":{"@id":"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blogs.qsc.com\/systems\/2019\/10\/10\/whenever-possible-go-native\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blogs.qsc.com\/systems\/"},{"@type":"ListItem","position":2,"name":"Whenever Possible, Go Native!"}]},{"@type":"WebSite","@id":"https:\/\/blogs.qsc.com\/systems\/#website","url":"https:\/\/blogs.qsc.com\/systems\/","name":"Q-SYS","description":"System Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blogs.qsc.com\/systems\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blogs.qsc.com\/systems\/#\/schema\/person\/2ce5a7e361fd40e5e62f120855c0b33c","name":"Martin Barbour","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.qsc.com\/systems\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/356df539b26bd8b0c6352e745715f317a6cded67825b88f84c808d6cef1f413d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/356df539b26bd8b0c6352e745715f317a6cded67825b88f84c808d6cef1f413d?s=96&d=mm&r=g","caption":"Martin Barbour"},"url":"https:\/\/blogs.qsc.com\/systems\/author\/martinbarbour\/"}]}},"_links":{"self":[{"href":"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/posts\/402","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/comments?post=402"}],"version-history":[{"count":0,"href":"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/posts\/402\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/media?parent=402"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/categories?post=402"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.qsc.com\/systems\/wp-json\/wp\/v2\/tags?post=402"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}