Version 6: known crashes/bugs and upcoming updates
Known issues in version 6 will be listed here and as replies to this thread. Please comment below regarding any new or ongoing bugs in v6. Examples can be issues with editing, navigating the app, stability (e.g. crashes, freezing, slowdown, latency), and any other regressions from v5. Also provide (a) your iOS version, (b) SP version, and (c) any steps leading up to the bug/crash, if possible. We will then do our best to provide a workaround and fix the bug (as top priority) in the following update.
To be fixed in 6.3.0 (major update, planned release date 6/11)
- Inability to reposition or customize the position of slurs and other score symbols; symbol placement reverted to a previous position
- Similarly, customizing the playback or display properties of any score symbol (expression, tempo change, dynamic, articulation, etc.) failed to work. This was also a new bug introduced in 6.2.
- Recording on two staves (and sometimes one staff) was not working, displaying multiple error messages
- D.S./D.C. placement issues (example)
- Swing playback indications were not followed (example)
- Many other bugs
To be fixed in 6.2.0-6.2.1
- In 6.1.9, there is substantial difficulty dragging to transpose one or more notes.
- There is a major bug where slow performance, instability, and crashing can occur when working with any selected note via the Note Selection Area
- In 6.0-6.1 earlier, there is substantial slowdown in performance when copying and pasting a long passage (via the Region Selection Area), such as a sequence of ~100 or more notes.
- Custom Tuplets aren't intuitively specifiable in 6.1.9 and earlier, but will be at some point in version 6.2.
Less Serious Bugs:
- Note Adjust Mode > Cut/Copy Selected Notes will be rewritten to work as intended to selectively cut or copy the notes, then paste them exactly as those notes were written, even when those notes were from multiple parts/voices.
Bug fixes arriving after 6.2.0
- AudioBus compatibility with iOS 14 for multi-track MIDI-out (for the time being, CoreMIDI out is recommended instead)
Fixed in 6.0.11
- There is a major crash in 6.0.10 that occurs when going into Select mode and selecting a note via Input Cursor..
Fixed in 6.0.10
- Playback: fixes stuck/held notes issue, which occurred during and after playback (reference).
---
In the initial release of v6 (6.0.7, January 1), a large number of crashes will be fixed in the next update that is on the way:
Common crashes in 6.0.7
- Editing tempo changes in Quick Start (new project) menu and Playback Options menu (see below for workaround)**
- Adding instruments in the Quick Start (new project) menu (see below for workaround)**
- During record, playback, and editing text
Other major bugs in 6.0.7
- Tablature ledger lines written across frets numbers make them unreadable
- Occasional freezing
- Difficulty showing cut/copy/paste (Region Selection Area). Longer press may be necessary than before
- Slur endpoint locations/layouts are lost when changing visible parts, changing Score View Mode, and sometimes when printing
---
**To work around these two crashes, please follow the instructions here until 6.0.9 is released.
To be fixed in 6.3.0 (major update, planned release date 6/11)
- Inability to reposition or customize the position of slurs and other score symbols; symbol placement reverted to a previous position
- Similarly, customizing the playback or display properties of any score symbol (expression, tempo change, dynamic, articulation, etc.) failed to work. This was also a new bug introduced in 6.2.
- Recording on two staves (and sometimes one staff) was not working, displaying multiple error messages
- D.S./D.C. placement issues (example)
- Swing playback indications were not followed (example)
- Many other bugs
To be fixed in 6.2.0-6.2.1
- In 6.1.9, there is substantial difficulty dragging to transpose one or more notes.
- There is a major bug where slow performance, instability, and crashing can occur when working with any selected note via the Note Selection Area
- In 6.0-6.1 earlier, there is substantial slowdown in performance when copying and pasting a long passage (via the Region Selection Area), such as a sequence of ~100 or more notes.
- Custom Tuplets aren't intuitively specifiable in 6.1.9 and earlier, but will be at some point in version 6.2.
Less Serious Bugs:
- Note Adjust Mode > Cut/Copy Selected Notes will be rewritten to work as intended to selectively cut or copy the notes, then paste them exactly as those notes were written, even when those notes were from multiple parts/voices.
Bug fixes arriving after 6.2.0
- AudioBus compatibility with iOS 14 for multi-track MIDI-out (for the time being, CoreMIDI out is recommended instead)
Fixed in 6.0.11
- There is a major crash in 6.0.10 that occurs when going into Select mode and selecting a note via Input Cursor..
Fixed in 6.0.10
- Playback: fixes stuck/held notes issue, which occurred during and after playback (reference).
---
In the initial release of v6 (6.0.7, January 1), a large number of crashes will be fixed in the next update that is on the way:
Common crashes in 6.0.7
- Editing tempo changes in Quick Start (new project) menu and Playback Options menu (see below for workaround)**
- Adding instruments in the Quick Start (new project) menu (see below for workaround)**
- During record, playback, and editing text
Other major bugs in 6.0.7
- Tablature ledger lines written across frets numbers make them unreadable
- Occasional freezing
- Difficulty showing cut/copy/paste (Region Selection Area). Longer press may be necessary than before
- Slur endpoint locations/layouts are lost when changing visible parts, changing Score View Mode, and sometimes when printing
---
**To work around these two crashes, please follow the instructions here until 6.0.9 is released.
For editing metronome marks, we recommend tapping the marking directly within the score (in Select mode), then choosing the Edit menu item.
To edit tempo changes/metronome marks properly, the following illustrates the instructions quoted above of (a) first selecting the metronome marking (red) and (b) choosing the appropriate menu item (green):
Comments
Thanks for letting us know. We're still looking into this issue and recommend updating to the current latest release (6.2.2) here first.
We would also appreciate the following info if possible:
- An email of the project that was affected by this issue, along with your iOS version. Within SP, this info is most conveniently submitted by opening Help Menu > Feedback from an opened project.
- More specifically, it might have to do with SP's Dark Mode setting (App > App Settings > Dark Mode) being enabled, which is separate from iOS Dark Appearance. We're still unsure about this though. Do you recall this ever occurring without the first setting being enabled or either setting for that mater?
To edit tempo changes/metronome marks properly, the following illustrates the instructions quoted above of (a) first selecting the metronome marking (red) and (b) choosing the appropriate menu item (green):
I have repeatedly tried to insert a tempo change into a simple piano document for one of my piano students and, after editing manually using the method above, the tempo reverts back to the "Playback Options" setting. I keep changing the tempo mark and it reverts back to the original. Is this a bug or am I doing something incorrectly?
Very sorry about this bug. It was related to the "customizability of score symbols issue" that was mentioned, since it not only affected position but also the playback or display properties of most score symbols (including expressions, articulations, etc) that were attempted to be customized. We believe this to be fixed in update 6.2.5 (available for download now) and later. However, please let us know if it persists after updating.
Been using this app for almost 3 years now and absolutely love it. One bug has happened recently however.
When you tie pitches together (of course the same pitch), its supposed to hold the pitch for the tied time and not rearticulate it or rest. As an example, if the piece is in 4/4, if you tie 2 Whole Notes together then the pitch should be held for 8 beats.
I am unsure when this exactly became a problem. When I write the music on the app it works fine. However, when I export it and open the Midi in a different program (SynthFont), all of the pitches that were tied lose the next pitch thats tied. So like the example, if the piece is in 4/4, if you tie 2 Whole Notes together then the pitch should be held for 8 beats but its only held for four beats in SynthFont.
I have tested this very thoroughly to spot where the issue is happening by using new Midis, old Midis (Both from Symphony Pro) I have used in the past and by testing other notation programs with SynthFont. All of my old Midis work just fine and other notations Midis also work fine, but anything that Symphony Pro Exports now has this issue. This includes creating new Midis from old pieces that I have not changed anything with. So the problem is somewhere in Symphony Pro. Not sure if its when it exports it or if its in the score but it is happening.
I know it wasn't an issue in March of 2021, that was the last time I used it and it worked fine. I hope it gets fixed!! I love using Symphony Pro and have gotten to where its all I use!
This is version 6/ I am using iPad Pro the latest IOS version 15.3.1
I know disconnecting the Smart Keyboard helps close the document, but this not a solution!!
The app was my daily notation choice. However, I stopped using it !!
Very disappointing indeed. I was really hoping to further learn this application - even do online tutorials on it. But… if the app has been dropped, I wouldn’t want to waste my time either.
DEVELOPERS: Will you PLEASE give us an update and let us know if there is a future for SP. If not, can it be sold to another software company to resume it’s demanded continuance?