Symphony Pro 5 takes several steps toward our mobile notation future [updated]


Updated at 5:07 pm with comments from Philip Lee of Xenon Labs (developer of Symphony Pro).

In an ideal world, I would have an app that could run on my iPad Pro 12.9″, make use of my Apple Pencil to write as I would on paper, and still give me all the control, flexibility, and power of Sibelius, Finale, or Dorico. I know that I am not alone in my quest to find this miracle tool. Imagine being able to write as quickly and as freely as you might on paper, with all the expansive, creative space that comes with it, but yielding performance materials that were the match of anything from a major publisher. Symphony Pro 5 is not that app; but, after spending over a week exploring it, I’m pleased to say that it gets closer than anything I’ve used on iOS until now.

I first started looking into Symphony Pro after seeing some questions pop up in the comments to my previous write up on Komp. After reading about it and getting in touch with the developers, I spent a week or two exploring the application on my iPad running iOS 11. (Disclosure: Xenon Labs, the developers of Symphony Pro 5 sent me a complimentary copy of the app and in-app purchase for handwriting recognition, worth $25 combined.)

Getting started

From the beginning, Symphony Pro is clean and modern. The welcome interface is almost non-existent. It uses a shelf-like grid of scores that reminds me a bit of the iBooks grid view. Unlike many complex apps, there is no onboarding sequence. I often find these directed tutorials to be tedious and frustrating, preventing me from getting down to work, and I appreciate Symphony Pro’s more direct approach.

Extensive hints like this one help first time users with some of the harder-to-discover features.

The tools in Symphony Pro are relatively easy to discover and learn through experimentation. The symbols used are mostly self-explanatory for anyone familiar with music notation, and the layout and design will feel intuitive to any experienced computer user. Once a user begins digging in to the app, plenty of contextual pop-ups will help guide them through new tools and settings as they toggle each for the first time. For confident users, the tips can be turned off, and more forgetful users can reset them all over again.

Symphony Pro has extensive documentation online. The manual is viewable in the app, but it’s worth noting that this is just an embedded web view. The data itself is online and not accessible if you are not connected to the Internet. Users can download a PDF; but, you’ll have to remember to do that ahead of time. It’s worth the time to explore the documentation, or at least long-press all the buttons and toggles in the interface, as the options here run as deep as any iOS notation app.

Experienced desktop notation application users will be pleased to see some of the extensive options provided by Symphony Pro, such as the tuplet options (left) and the meter configuration options (right). The meter configurations in particular are a match for just about any desktop tool.

My only issue in getting up and running was that there are a couple of gesture controls that are difficult to discover, and from what I could tell, are only accessible through gestures. The primary example of this is the Measure Dialog, accessible by two-finger tap, is the only way I found to change key signatures, meters, and several other “global” parameters in the middle of a score. It turns out that there are actually two more equally sneaky ways of opening these controls, and I only discovered them from the manual.

Handwriting with Apple Pencil

Symphony Pro has been through several iterations (a positive sign on its own), and the focus of the current version 5 is handwriting recognition. In the few years since the release of the first iPad Pro and Apple Pencil, fast, accurate handwriting recognition, writing speed, and palm rejection have quickly become table stakes for any music notation app.

Symphony Pro 5 joins the surprisingly crowded category of apps that use the handwriting recognition engine from MyScript. If you haven’t used a MyScript-based application before, you might be surprised at how efficient and accurate this can be. Symphony Pro behaves much like the other MyScript-powered applications in that it focuses on one measure at a time, only rendering from handwriting to engraving after the user taps away. Using off-the-shelf components means Symphony Pro has to work a little harder to distinguish itself.

Symphony Pro’s handwriting recognition hits all the marks one would expect for speed and accuracy. It can read notes, articulations, and more. Best of all, it’s optimized for Apple Pencil.

Notably, Symphony Pro cleverly allows the user to switch between finger multitouch for tools and navigation (panning, pinch-zooming, etc.) and Pencil input. Other apps require the user to affirmatively enter a pen-writing mode that limits the ability to interact with most of the other controls, removing the illusion of working on paper; that’s not the case with Symphony Pro. While this will be great for Apple Pencil users, those who use non-Apple styluses will not see the benefits. Having said that, iPad Pro users without an Apple Pencil are missing the best part of the platform.

Speaking of the paper illusion, one of my favorite little bits of an excellent user interface in Symphony Pro is the full screen toggle, which hides all the tools and allows the closest thing to paper-writing I’ve found in a notation app yet. It also allows the user to use the Pencil for selecting passages for editing and deleting them (like the Lasso tools in Photoshop). This is a really clever idea for a feature and one that the developers tout proudly. Unfortunately, I found it to be very buggy, often switching to nearby staves and dropping my selection if I wasn’t extremely precise in my lasso work.

QWERTY and MIDI keyboards

Along with the intuitive note entry, Symphony Pro provides a large and welcome array of keyboard shortcuts for those using a hardware QWERTY keyboard. Best of all, the keyboard shortcuts are customizable.

My only quibble here is that the shortcut map itself does not use the standard iOS UI for displaying shortcuts, nor does it use the system-standard of long-pressing the Command key to review them. This is a very minor concern, and I suspect it may stem from the fact that the shortcuts are user-editable. Symphony Pro is mostly a good “app citizen” on the iOS platform, even going so far as to embrace Split View, allowing users to have a score up side-by-side with another app, like an orchestration reference, sketchpad, or media player.

Another pleasant surprise in Symphony Pro is the support for MIDI input. Yes, I know. I’ve now added a Bluetooth stylus, QWERTY keyboard, and a MIDI keyboard to my agile mobile rig. However, the Bluetooth MIDI support is notable here. While many mobile music apps work nicely with MIDI controllers, they tend to be audio synthesizers, not scoring applications. Bluetooth Low-Energy (BLE) MIDI is often poorly supported in those apps, requiring an external MIDI pairing app.

In Symphony Pro, though, I was able to pair my keyboard (an Xkey Air 25-key) directly from within the app. This feature will be a real boon to those who already have the hardware, but perhaps not worth the purchase for this single use. MIDI input works great both as step-time and synchronous recordings. I didn’t note much lag, even when Symphony Pro was playing back other staves alongside my recording.

Symphony Pro’s support for MIDI from other apps (left) and Bluetooth LE MIDI hardware (right) is reliable and a breeze to set up.


The fonts available in Symphony Pro are quite good. Typography connoisseurs will be pleased to discover that text in the score can be changed to access any installed system font, including user-installed fonts. This is something even many of Apple’s own apps don’t allow. Unfortunately, there does not seem to be a way to control fonts globally in the form of paragraph styles or text styles that you might find in desktop applications. If a user wants to apply any kind of house style, there will be lots of tiny taps to change each object individually.

Along with good support for text fonts, the music font in Symphony Pro is Bravura. I’m extremely pleased to see Bravura catching on with so many apps, as I’ve never been a big fan of Emmentaler and other free-to-use music fonts. It’s yet another reason to thank the Dorico team for their work and Steinberg for allowing them to release it under a liberal license. However, some of the individual expressions of Bravura symbols are less elegant here than you might expect in other applications. I saw several examples of too-short stems in particular that looked odd next to more correctly proportioned symbols.

These stems in an exported PDF of an individual part are too short.


In general, Symphony Pro’s notation and engraving defaults are very good. The downside of this is that the ones that are not stick out as downright bizarre in comparison.

For example, one of the templates provided is string quartet, which lists instruments as “Violin, Second Violin, Viola, Cello”. I’ve never seen a part marked “Second Violin”, and I’ve certainly never seen a Violin 2 part paired with one only labeled “Violin” rather than Violin 1. On top of that, the second’s abbreviation is “Se. Vln.”. Without seeing the first system with the full name, I’m not sure I would have even been able to figure out what “Se.” stood for. Transposing instrument part names also use a lowercase b instead of the flat sign and show inconsistent capitalization (Trumpet in Bb on the first line and Tpt. In Bb subsequently). Admittedly, these are somewhat pedantic concerns, but they’re exactly the sort of easy wins that I expect software to take care of on my behalf. Instrument names are user-changeable, but the defaults just look careless.

While on the subject of instruments, the array of instruments to include in the score seems to be populated from the General MIDI list, as it includes things like “muted trumpet” and “tremolo strings” which are not the sorts of things one would assign to a separate staff with these labels.

In addition to instrument names, Symphony Pro fails to follow some rather basic rules of music notation. For example, it fills empty bars with rests based on the beat size, rather than using the whole-bar rest (centered whole rest). Filling empty measures with rest is a step that must be taken manually as well. The upside to this is that you can easily over-fill a measure if you want to. It deals with this by turning the extra rhythms red. However, I found it a bit too easy to over-fill by accident. The user is presented with a warning when this happens; but, I found the warning to be more intrusive than helpful.

More alarmingly in notation, Symphony Pro deals incorrectly with tied accidentals. In the example here, Symphony Pro does not add a sharp symbol before the second note in the measure, even though it is entered in as a C-sharp and plays back as C-sharp. Ideally, the app would show either another sharp or a courtesy accidental.

The indicated note would be correctly interpreted C-natural. Symphony Pro reads it as C-sharp. And either way, it should take an accidental. (Note: The crushed 32nds and 16ths fixed themselves the next time the document reflowed, after I took this screenshot.)

Some of Symphony Pro’s engraving choices are also a bit perplexing. Articulations are one of the most obvious categories. Slur and tie arcs are sometimes very odd, to the point of being wrong. In fairness, it took the development teams on Sibelius and Finale decades to get slur arcs to to their current point which require only minimal manual adjustment. But some articulations should be a bit easier to manage. Symphony Pro often places accent marks are inside the staff, even sometimes intersecting staff lines in very unpleasant ways. This seems like it should be much easier to correct.

Output from Symphony Pro presents another set of challenges. Vertical and horizontal scrolling are nice and smooth while navigating the score, and users can choose infinite horizontal scroll, infinite vertical scroll with regularly spaced systems, and print layout. Viewing the print layout is marked “Legacy”, indicating that it will be removed. This is baffling for an application that presents so many print-focused features, such as parts, page size, margins, staff size, and more.

Knowing where pages begin and end is crucial to presenting useable materials to performers. While there are some missing controls for print, handling parts at all and offering some page settings both set Symphony Pro apart from its mobile competition. Often, mobile apps assume that users creating scores on tablets will use those same tablets to distribute and perform their work.


Despite some misgivings about the page formatting, export from Symphony Pro is another area where it really shines. Tapping the standard share icon (square with up arrow) brings up a menu which allows the user to select a format—MusicXML, MIDI, m4a audio, a number of PDF configurations — and a destination. Destinations include e-mail and AirPrint, as well as the catch-all Send To, which allows a user to select any option on the iOS Share Sheet, including any app that can handle XML, MIDI, or PDF files. This could include other music apps that can import MIDI files to drive synths, or PDF apps that might be useful in markup (like PDF Expert) or performance (like forScore). This is a seemingly small concern, but I appreciate iOS apps which take advantage of the tools Apple has provided to allow them to interoperate with other apps.

Symphony Pro’s export options menu.

I opened an exported MusicXML file from Symphony Pro in both Sibelius and Dorico, and both handled it nicely. It seems Symphony Pro includes some extra metadata that may need some cleaning up around clef, key signature, and meter changes. Other than that, every symbol from Symphony Pro came over accurately.

Thankfully, the engraving issues and most of the notation issues I discussed above will not will not follow a Symphony Pro-created score into a desktop application. Notably, Dorico’s import defaults did a lot of heavy lifting to clean up some of the rhythm notation problems (like whole-bar rests) that Symphony Pro created. Sibelius, on the other hand, seemed to take the MusicXML data more literally, and it would have required a bit more manual cleanup or fiddling with import settings, but it still does fix most of the shortcomings. In either case, I think that even though Symphony Pro isn’t ready to replace a desktop app in my workflow, it may find a place as a mobile scratchpad.

The “Pro” in Symphony Pro

I invited Philip Lee of Xenon Labs to comment on how he positions Symphony Pro in the context of professional users and powerful desktop scoring applications, and only received his comment after publication. Here is some of what he shared:

This product and business plan involve different reasons and perspectives: market constraints imposed by the mobile platform prevent from staying competitive given prices typical of software on traditional platforms; in an entirely different view, designing for a touch & stylus interface involves different UX approaches, not to mention software libraries supplied by Apple.

Though we really wanted to bring a worthy, differentiated competitor into the desktop ecosystem as to give our pro userbase a full-fledged partner app, … constraints definitely kept the company small, and the app limited to iPad/iPad Pro. That isn’t to say that SP may be brought to Mac or other platforms in the near future, to accommodate the many who’ve requested viewing/playback capabilities.

Given the design and polish that amounted over the years, it’s certain to me, with the agreement of my advisor, Daniel Wyman, that professional users are buying the app as a bargain at its current discount price. The layout & behavior of SP’s toolbar, context menus, and gestures for touch were deliberate decisions to allow a good user experience across a variety of user backgrounds in a single product, in breadth and depth.

I can’t argue with any of that. Given the thoughtful layout, controls, and hardware compatibility, Symphony Pro 5 with the Apple Pencil support is a steal at $25.


As just mentioned, Symphony Pro’s price is very reasonable; $15 for new users, and $10 for handwriting recognition as an additional in-app purchase. In addition, all of the items in the Version 4 Complete Features Bundle are available to Symphony 5 Pro users as a free in-app purchase.

Regrettably, the user is reminded of this every time a formerly paid feature is used, even when the premium features are unlocked. A modal dialog that interrupts your work to tell you that a feature “was previously part of the Version 4 Complete Bundle. This IAP is now offered free in Version 5. Write us a good review!” This is notably contrary to Apple’s review guidelines which were originally announced over the summer. I understand that the App Store is rough and competitive for developers and that good star ratings can make or break all the work that goes into creating good software. That doesn’t excuse the constant interruptions from an application that is so professional that it has “Pro” in its name.


Admittedly, it is completely unfair to hold a sub-$50 mobile application created by a small startup to the same standards as products created by multi-million-dollar corporate development studios employing teams that represent collective centuries worth of experience. While Symphony Pro 5 makes great strides for power users with uniquely thoughtful Apple Pencil support, keyboard shortcuts, MIDI input, typography, and user interface design, it falls down in some of the same ways as every other scoring app on the platform: it simply can’t make scores that I would be proud to put my name on. Sadly, I am beginning to think that we won’t see that app until Steinberg, MakeMusic, or Avid decides that it’s worth their investment. Symphony Pro’s namesake professional users will best use the app to augment, rather than replace, any part of their current workflow.

These complaints are sometimes nitpicky and thankfully rare, and the things that Symphony Pro 5 does well, it does very well. I would go so far as to say that the things it does well, it does better than any other iOS notation application. However, for an iOS notation app to be a true replacement for one of the major Windows or macOS tools, it needs to support the same level of control over the final output. Symphony Pro is not that application, but I think it has some of the right ideas. I hope that the current, highly competitive Cambrian explosion of iOS music applications can push all of them toward that goal.


  1. Abraham Lee

    If the included music font is supposedly Bravura, why do all the images show Opus?

    1. David MacDonald

      Good eye, Abraham. The clefs and some other glyphs are definitely not Opus. I actually asked the devs at Xenon about this while writing my review, and here’s what they said.

      > We’ve been incorporating Bravura as the standard font across almost all of the basic glyphs for measures, notes, and expressions, though you’d be right that complete coverage isn’t quite there yet! It’s definitely more to work on.

      I left this out of my review for the sake of simplicity. And I think some of the non-font choices regarding stem length, slur position, and rhythm spacing are greater concerns. As I wrote, I’d use SP as more of an on-the-go MusicXML editor than anything for final work.

      1. Abraham Lee

        > The clefs and some other glyphs are definitely not Opus.

        I certainly don’t want to argue, but the design of many of the symbols shown in the example images are 100% Opus (or at least Opus-lookalike) while others are not. As long as Xenon got permission to use it, I have no qualms. Otherwise, they can potentially run into legal problems with Avid over it. Of course, just using Bravura would alleviate that, but I have yet to be convinced, even on the Symphony Pro website, that they aren’t using even a derivative of Opus, even though it says they are using Bravura. The images tell a different story. Just saying…

        > And I think some of the non-font choices regarding […] are greater concerns.

        Perfectly understandable. I was just concerned about a potential breach of copyright for using Opus. If I’ve misunderstood something, please ignore my comments.

  2. Kevin Gibbs

    In addition to everything mentioned in this review, It should be noted that Symphony pro has utilized the QWERTY keyboard to facilitate a remarkable degree of accessibility for blind and visually impaired users through Apple’s VoiceOver screen reader software which comes with every piece of hardware Apple makes.. Imagine the transformative possibilities afforded to blind composers and arrangers who now have a far easier path to sharing their work with their sighted colleagues. Currently, Symphony Pro represents the standard in this area when compared to any apps currently on the market.

    1. David MacDonald

      Wow! That’s fantastic to read, Kevin! I know Apple provides a lot of accessibility APIs, but had no idea how extensively they were being used in Symphony Pro. I imagine hardware keyboard support helps immensely and that the two probably go together nicely. Thanks for sharing.

      1. Kevin Gibbs

        Fact is, Xenon Labs has made a very conscious effort to focus on the accessibility component of Apple’s SDK. I only wish I had had the chance to contact you before you wrote the article so that this fact could have been included right up front.

        1. Phil from Symphony Pro

          Kevin: I sent the editors a note about SP’s current accessibility support in relation to QWERTY just earlier. I’m glad you pointed this out for other VO users. The extent of improvements through our collaboration with Kevin was significant from V4 to V5. Those interested can learn more from our online manual chapters below, though they’re yet to have complete instructional coverage:

          1. The Accessibility Guide:'baccessibilityvoiceover-0
          2. QWERTY Keyboard General Guide:'bqwerty-keyboard-0

  3. Michael Philcox

    Thanks for your thorough review, Phillip. My only quibble is with the inference that a comparatively inexpensive iOS notation app should be capable of replacing rather than augmenting much more expensive computer apps such as Sibelius, Finale or Dorico. I understand that even StaffPad, which is surely the touchstone for “handwritten” notation apps, is usually used in conjunction with a more powerful computer notation program. I think this was even acknowledged as the recommended course by StaffPad’s developer. Having said that, I agree with the current shortcomings you have identified in Symphony Pro and hope they are corrected as time allows.

    1. David MacDonald

      Thanks for reading, Michael. I do acknowledge exactly that in the review: “Symphony Pro’s namesake professional users will best use the app to augment, rather than replace, any part of their current workflow.”

      I don’t see this as a weakness; rather, I wanted to make sure that users expectations were clear. Symphony Pro is a great app, probably the best in its category on iOS. I am not a Windows user, so I can’t comment on StaffPad, but it sounds about right.

      1. Steve Steele

        Hi David, I’m reading your review right now. Curious about reading this comment, “Symphony Pro is…, probably the best in its category on iOS.”

        Even compared to Notion iOS? I think Notion iOS even stands up to Staff Pad. I’ve been using Notion iOS for about two years now in a professional environment and found that’s it’s certainly powerful enough for daily mobile use, especially on an iPad Pro with Apple Pencil, (it also now has full screen hardwriting recognition).

        Again, thanks for the review. I’m all about iOS apps these days as many have caught up or in some cases surpassed desktop versions due to gesture support.

        1. George Grella

          I want to second this comment. I’ve used both Symphony Pro and Notion, and Notion is way ahead of Symphony Pro, which is now where Notion was at about 18 months ago with Apple Pencil. Notion also has iCloud support and syncs with Notion 6 for the Mac. I wouldn’t use them for engraving, but for composing they are a superb combination.

          1. David MacDonald

            I’d be curious to hear more details, George. What do you like about Notion?

        2. David MacDonald

          Hi Steve, if you’re familiar with Notion, I’d welcome your thoughts on how it compares. I say “probably” precisely because I haven’t used Notion. In addition to Notion, there are probably a bunch I’ve never heard of. I have tried Symphony Pro, Komp, NotateMe, and MusicJot.

          Notion is interesting, and it uses the same handwriting recognition technology that all of these others (except Komp) share.

          1. Steve Steele

            Hi David, Sure I can tell you a few things. Like George said for engraving I go elsewhere. But for composing, Notion iOS is practically identical to Notion for the desktop. And on the desktop Notion is extremely fast at note entry, which makes Notion iOS very fast too. Btw, I can use my iPad Pro like a Wacom tablet using Duet and handwrite notation into Notion on the desktop. It’s great.

            But to stick to Notion iOS, with a 12.9” iPad Pro and the Apple Pencil, (I can also connect a midi keyboard and even my midi guitar for note entry), the feature set is very mature. And the speed of the new iPads are remarkable. Handwriting is very accurate and fast. Really a joy to use that way. But having alternate ways to enter notes makes it that much faster.

            I compose complete sketches with an orchestral template that I share with Finale and Digital Performer. And the iPad Pro will play it back no problem. The sample set is very good (same that comes with desktop Notion – maybe not as many velocity layers).

            Lead sheets, drum line charts, film score cues (full orchestra), classical guitar, fairly complex piano pieces (usually move to Finale at some point for that), I can do all of that just like I can do with Finale and Sibelius (not as much functionality of course, but definitely good enough that I have no problems calling it mature and professional).

            Except for a couple of minor differences, Notion iOS is almost identical to the desktop version, and to have that much power in my iPad Pro which I carry around like a clipboard, to be able to play any chart back, to be able to print parts or formated charts, I found it quite liberating. Once I got used to Notion’s layout limitations which aren’t bad, it was actually a bit of a relief because I could just compose and after messing with a few settings Notion ended up doing an adequate job at most layouts – at least good enough for some rehearsals or until I can import it into Finale.

            The main difference between Notion iOS and all of the other notation apps is that Notion iOS came from Notion. So it brought all the desktop features along and added handwriting for the iPad instead of the other way around. Imagine a Finale for iOS that didn’t have all of the dialog boxes but was fully capable of performing note entry and great playback. That’s what Notion iOS is like. Or how Cubasis is very much like Cubase. That’s a similar comparison too.

            When Staff Pad came out I was unsure if Notion iOS would stay relevant, but they added handwriting recognition in a strip at the bottom of the screen, then they made it full screen, kept improving it and although I haven’t spent time on Staff Pad, from the videos I’ve seen, they seem about the same.

            Last thing. Notion for the desktop has a bit of a reputation for being a second class citizen. Imo, it’s the simplicity and the features that stay out of your way on the desktop version that allowed Notion iOS to translate to the iPad Pro so well.

            If you get a chance to get your hands on a new 12.9” iPad Pro, try Notion iOS for a couple of weeks. I no longer use a MacBook. Just my Mac Pros at the studio and the iPad Pro as my mobile device. And my workflow has increased dramatically. Maybe it’s just me but Notion iOS and the 12.9” iPad Pro is like pencil and paper, but as a computer. And I love that freedom.

            Sorry for the long post. Hope that helped explain a few things. I do have Notate Me but I only use it for Photoscore although I don’t always need it because I’m fast with Notion iOS. I tried Komp but didn’t like the subscription method. And Notion iOS is ahead of Komp too (although Komp is on the right path I think).


  4. Michael Philcox

    My apologies to both David and Phillip for my above error in identifying the writer of this review!

  5. Tom

    I’d like to see a summary of the iOS notation market. How about a comparison of Komp, Notion iOS, and Symphony Pro, maybe even how they compare to StaffPad? NotateMe and MusicJot also if they’re worth it.

    1. Philip Rothman

      We don’t have a side-by-side comparison, but David reviewed Komp when it was first released, I wrote about MusicJot, and of course StaffPad and NotateMe have been well-covered here, along with Kawai Touch Notation.

    2. Steve Steele

      I’ll be comparing and reviewing all of these apps, especially Notion iOS and Symphony Pro, for my YouTube channel. Should be done in a couple of weeks. I want to spend equal time with each before I upload.

      Steve Steele

  6. Steve Steele

    I would be happy to make a “Notion iOS vs Symphony Pro and other iOS notation apps” video for my YouTube channel if anyone is interested. I was thinking of doing it anyway. Actually I already started.

    I’ve been comparing Notion iOS and Symphony Pro a lot lately. I’m keeping notes, composing with both, sending MusicXML back and forth and so on. So far I’m impressed by both. I may have underestimated Symphony Pro a bit in my first comment, but I still really like Notion iOS. Symphony Pro just released an update that added some nice new features. Seems like they’re moving fast.

    But I have discovered a couple of important differences.

    I’ll post back here when I’ve uploaded my YouTube review if that’s ok.

    Steve Steele

    1. David MacDonald

      That’s great Steve! Do you also use a desktop scoring application? I’d be curious to see how these mobile apps fit in to a larger workflow.

  7. Martin


    Nice review about SP. I Uwe „Notion“ to transcribe early music. Sometime its necessary to correct entry afterwards – and the the confusion starts – its nearly impossible to change the duration of a Note. So, I wonder, if SP does the job.
    Another impossibility on Notion is, it cant do syncopies oder a barline.

Leave a Comment

Your email address will not be published. Required fields are marked *