Of course we hope that the application does its job without grumbling and murmuring. But even we make mistakes. Of course we do this to learn from. If you encounter an error, called a bug in computer language, in Musicdott, please let us know? Then we will do our best to resolve this as soon as possible. If necessary, we can help you quickly with a workaround.
Bugs found on these pages. Does it say * SOLVED *? Then the bug is already solved 🙂
If the last teacher account is deleted, the system will automatically log the teacher out and the teacher will not be able to access anything anymore. This is not a desirable situation. Fix by not offering the option to delete the very last account. When canceling Musicdott, no idea why someone would want that ;-), we will ensure that everything is deleted in accordance with AVG / GDPR. SOLVED The logged in teacher cannot delete his / her own account.
After a rhythm has been created in GrooveScribe and recorded in MusicDott, the speed (BPM) sometimes wants to be higher. This is correctable with the scroll bar, but it is not retained. Reinstallation of Groovescribe source code performed. Probably a bit fell over during the last update to a new web server 😉
A student with an account that has been set to inactive can still log in to Musicdott. Solved: Code changed. Status not active? Logging in is no longer possible. Did you know that you do not pay license fees for an inactive account? If your student returns after, for example, 3 months, his or her account can be used again. That saves work!