The Sibelius Cloud Publishing viewer provides a rich score viewing
and interaction experience for your customers.

Customising the viewer experience

First, a word about customisation. The power of Sibelius Cloud Publishing comes
from the ability to customise the viewer experience using the Cloud
Publishing API. This allows you to tailor Cloud Publishing to the needs of your
digital sheet music publishing business.

Virtually all features below are customisable on a per view basis. Let’s
say for example, you want to display a single page of your score as a taster
for your users, and then display that same score in its entirety once the
user has purchased it - the Sibelius Cloud Publishing API lets you do just that,
with no need to create and publish separate scores.

The viewer displays each page of your score using the same fonts as found in
Sibelius. Since fonts are vector-based, your score displays with the same
clean and crisp quality that you get from Sibelius itself.

Users may navigate through your score by clicking the page forward/back
buttons in the transport bar, or by swiping on trackpads and touch-screen
devices.

The viewer is fully responsive, automatically adapting the content of the
transport bar to accommodate a variety of screen sizes.

The number of visible pages may be customized using the pageRange
parameter of the getScoreView route.

Playback

Clicking the play button in the viewer starts playback of your score. A
playback marker is drawn on the score (just like Sibelius!) indicating progress.
Page turns are handled automatically, so that the music currently being heard
is always visible on screen.

Sibelius Cloud Publishing uses the same Sibelius 7 Sounds library that can be
found in Sibelius itself. This means that any score created in Sibelius will
sound the same once you publish it to the web using Sibelius Cloud Publishing.

The length of playback is linked to the number of visible pages - so, if your
score is four pages long, but you’ve specified that you’d only like to display
the first page of that score, then only the first page of the score will play
back.

NB: Playback is not available for PDF-based scores.

Transposition

Clicking the transpose button allows a customer to change the transposition
of your score. By default +/- 3 semitones are provided.

NB: Transposition is not available for PDF-based scores.

Printing

Clicking the print button allows a customer to print the score on their
printer.

The printing feature may be enabled/disabled using the printable parameter on
the getScoreView route.

Licensing watermark

To encourage legal use of scores, the viewer may also embed a license string of
your choosing into the score (for example, ‘Licensed to Joe Bloggs for 20 copies
only’). This is set using the licenseString parameter on the getScoreView
route.

Localization

The viewer is localized into several languages. More details
here.

Hooks

Sometimes you’ll want to hook into events in the viewer itself - for example,
when a user clicks the print button, you might want to trigger your own code
to track printing using your own systems, or perhaps to display a help message.
The viewer provides a series of hooks for you to use for this purpose.

For more information, see here.

Viewer features