Support
Who this space is for
This space is for Music Eye View clients with an active engagement, and for the teams they appoint to manage it day to day: management, operations, IT, audiovisual teams, integrators or technical providers.
It provides a way to report a situation, define what is happening and share the information needed to address it.
A support request may concern an incident, but it can also reveal how a place is actually being used and how its sound identity is being governed over time.
Contact supportSupport entry point
For support, the main address is adrappier@musiceyeview.com. It receives requests concerning playback continuity, the use of interfaces, feedback from the field and the governance of active engagements.
Where an end client receives the service through a partner, routine requests go first to that partner’s support team; Music Eye View provides second-line support for the technical systems it operates, within the agreed framework.
Depending on its nature and the scope of the engagement, a request is handled by the usual contacts or, where it involves a change in scope or an editorial decision, by the contact responsible for governance of the engagement.
Priority depends on operational impact and the contractual framework: an interruption to playback or an inaccessible interface may therefore be addressed before a usage question or editorial feedback. This priority applies to the situation, never to the value of an engagement.
Contact supportIdentifying the type of request
A support request may concern technical continuity, editorial matters or a change in scope. Identifying which it is helps establish the right response from the outset.
Technical incident
A playback interruption, an inaccessible interface, a silent zone, abnormal or unstable volume, a device that no longer responds. Where provided for in the engagement, Music Eye View assesses the situation with the venue teams and the relevant technical providers.
Usage questions
How to use an interface, find information, apply an operating guide, check a local rule or understand expected behaviour. The documentation supplied with the engagement is the first reference; support steps in when the situation requires further interpretation, within the agreed scope.
Editorial feedback
Music that feels too prominent, too withdrawn, too dense or too far from the intention; recurring discomfort; a moment that no longer holds together; a question about the fit of a sequence. These observations feed editorial governance. Depending on the terms of the engagement, they may call for a documented revision or be addressed at the next governance review with the client.
Temporary event
A private event, an exceptional opening, a brand moment, or a temporary change of use for a day or a period. These requests should be flagged as early as possible: depending on their nature, they may call for an operational adjustment, an editorial decision or a new scope.
Change in scope
A new zone, a new schedule, a change in intention, a lasting change of use, a change in technical responsibilities, or any request that goes beyond the scope initially agreed. Music Eye View assesses such requests with the client before any operational commitment.
Describing a situation
A situation is easier to understand when it is described through a few precise points:
Venue
the venue or establishment concerned.
Zone
the specific zone of the venue if the situation is localised there.
Timestamp
the date and time of observation.
Description
the nature of what is being observed: interruption, disturbance, mismatch, usage question, editorial feedback or a request for change.
Environment
the device or interface in use when the situation involves it.
Change
any recent change on site that may have an impact.
Screenshot
a screenshot or photo when it helps clarify the situation, limited to what is necessary to understand what is happening.
Finding the engagement documentation
The engagement documentation is supplied as part of the collaboration: an articulated musical direction, programmes and rules for their use, operating guides for teams, reference technical documentation, and the record of decisions kept over time.
This page is deliberately general. Parameters specific to each engagement, particularly technical ones, remain in the documentation shared with the client and the people they appoint.
If a document is missing or needs updating, a message to adrappier@musiceyeview.com can clarify its status. Any additional documentation remains handled within the framework of the engagement.
Which playback environments can be supported?
Music Eye View can operate or work with playback set-ups running on Windows, macOS, Linux, Android or iOS, across centralised, decentralised or hybrid architectures. Depending on the project, the stream may be accessed in a web browser or media player such as VLC, through a dedicated web app, connected to a multiroom system such as Sonos, Bang & Olufsen, Google Home or JBL, or integrated with professional audio and IP infrastructure such as Barix or Dante.
The exact support perimeter is defined for each engagement. Music Eye View supports the streams, interfaces and systems it operates; local networks, cabling, amplification and physical intervention remain with the client or its technical providers unless the engagement states otherwise.
When a request calls for new scoping
Some requests remain within day-to-day support. Others alter the engagement enough to require a governance decision, an amendment or a new scope.
When a request affects the sound direction, playback scope, zones, schedules, technical responsibilities or the operational ecosystem of the engagement, Music Eye View assesses it with the client before any operational commitment. That assessment protects the coherence of the sound identity and keeps the engagement clear over time.
When a change is planned to the network, audio equipment, zones, operating hours or technical providers, Music Eye View should be informed in advance where possible. This makes it possible to understand the potential impact on playback continuity and sound identity governance.
The conversation begins with support or the usual engagement contacts. The nature of the request then determines what follows: operational follow-up, an amendment or a new scope.
Role of local technical providers
Where the engagement framework allows, Music Eye View can liaise with technical providers appointed by the client. Physical work on equipment, networks, amplification or cabling remains the responsibility of the client’s teams or the relevant specialists. In other cases, the client coordinates technical providers directly.
The links, access details and configurations supplied as part of the engagement should remain within their intended environment. Any change to a device, network, zone or access arrangement may affect playback and should, where possible, be flagged before intervention.
Governance memory
Where an engagement includes ongoing governance, some requests are worth recording because they reveal how a place is actually used: a recurring discrepancy, a change in context, a moment that repeatedly loses coherence, or an editorial decision that needs to be retained. Support then becomes part of the engagement’s governance record. It helps clarify what should be restored, adjusted or passed on.
Information sent to support
Information shared with support is used to handle the request and maintain continuity of the active engagement. Any request relating to your personal data can be sent to contact@musiceyeview.com, under the conditions set out in our Privacy Policy. Where specific contractual provisions apply to the engagement, they take precedence over the general information published on the site.
A situation that does not fit any category?
If the situation does not fit any of the categories above, simply describe what you are observing and share the information available to you. Support will determine the right point of entry.
Contact support