Dolby at NAMM 2020

Content Creation Station

Dolby Atmos Music is supported on multiple content creation tools that creatives use today. Guests were welcome to mix music in their preferred digital audio workstation.

Dolby Atmos Living Rooms

Plenty of lounge seating offered visitors a place to relax and enjoy Dolby Atmos Music on a 5.1.4 speaker system. A separate living room area streamed Dolby Atmos Music on Amazon Music HD with Echo Studio.

Dolby Atmos Music on TIDAL

Compatible Android devices gave visitors a free trial listen of Dolby Atmos Music on TIDAL.

Dolby On Demos

Walk-in guests were introduced to Dolby On, our mobile recording app with automatic mixing technology to balance out any recording.

Learn More

For a majority of visitors, NAMM was their first experience of Dolby Atmos Music. A dedicated living room for Echo Studio demos highlighted the first smart speaker to support our listening experiences. Compatible Android phones playing top hits in Dolby Atmos drove traffic to our second partnered streaming service, TIDAL. The Dolby Lounge provided many avenues to engage with guests of all backgrounds while showcasing our growing music libraries on Amazon Music and TIDAL.

Dolby Employee Being Interviewed at NAMM 2020

Dolby Recreational Vehicle Outside NAMM Event

In addition to the Dolby Lounge, we created a second space for visitors to relax in the Dolby Airstream Experience, parked at the main entrance of NAMM. The Airstream provided ample privacy for comprehensive demonstrations of Dolby Atmos Music with an Echo Studio, a Sennheiser AMBEO sound bar, and a 5.1.4 Pro Tools setup in the mixing studio area. Take a peek inside:

Crowded People In Front Of Dolby Stand in NAMM

// This view acts as a rendering template to render InitScript(and server-side Form's descriptor) in FormContainerBlock's client-side for Form[d4daa1c4-8561-4f34-ae0c-3d1e293c2a7e]. // TECHNOTE: all serverside (paths, dynamic values) of EPiServerForms will be transfered to client side here in this section. (function initializeOnRenderingFormDescriptor() { // each workingFormInfo is store inside epi.EPiServer.Forms, lookup by its FormGuid var workingFormInfo=epi.EPiServer.Forms["d4daa1c4-8561-4f34-ae0c-3d1e293c2a7e"] ={ Id: "d4daa1c4-8561-4f34-ae0c-3d1e293c2a7e" , Name: "Newsletter Form (Form Container GTM)" , // whether this Form can be submitted which relates to the visitor's data (cookie, identity) and Form's settings (AllowAnonymous, AllowXXX) SubmittableStatus : {"submittable":true,"message":""}, ConfirmMessage: "", ResetConfirmMessage : "", ShowNavigationBar : false, ShowSummarizedData : false, // serialize the dependency configuration of this form to clientside DependenciesInfo : JSON.parse("[]"), // keep all fieldName which are not satisfied the field dependency conditions DependencyInactiveElements: [], // Validation info, for executing validating on client side ValidationInfo : JSON.parse("[]"), // Steps information for driving multiple-step Forms. StepsInfo : { Steps: [] }, FieldsExcludedInSubmissionSummary: [], ElementsInfo: JSON.parse("{}"), DataSubmitController: "/EPiServer.Forms/DataSubmit" }; /// TECHNOTE: Calculation at FormInfo level, and these values will be static input for later processing. workingFormInfo.StepsInfo.FormHasNoStep_VirtualStepCreated=false; // this FLAG will be true, if Editor does not put any FormStep. Engine will create a virtual step, with empty GUID workingFormInfo.StepsInfo.FormHasNothing=true; // this FLAG will be true if FormContainer has no element at all workingFormInfo.StepsInfo.AllStepsAreNotLinked=true; // this FLAG will be true, if all steps all have contentLink= ="" (emptyString) epi.EPiServer.SystemSettings = { RequestVerification: { FormFieldName: "__RequestVerificationToken", HeaderName: "RequestVerificationToken" } }; })();

Keep in touch