-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audiveris - a beginners experience and problems #694
Comments
These are not error messages, but just technical information. Perhaps too technical. But you can ask for more, such as debug messages for certain classes. This is specified via a |
Regarding the heap size, there is a statement in the file build.gradle (lines 49-50) that
Is this a compiler setting or can this be changed elsewhere? I assume it would help and maybe avoid the error message |
The The |
Thanks, I will check. I remember yesterday night when I skimmed through the handbook I vaguely remember seeing something. Yesterday I made a quick Audioveris run on the first movement of Dvorak's symphony #9 and checked the OMR quality. I used a Lilypond generated score as well as a score from IMSP. To my surprise the Lilypond conversion was not good. In particular it missed most 1/8 rests and many beams. I will come back to this in s separate post. By profession I'm a space engineer, satellite deep space navigation and control, software and operations. For navigation, one important sensor is the star tracker which autonomously determine in which direction the spacecraft is pointing. A star tracker identify, stars, cluster of stars and galaxies and based on for example their size, brightness and the angulsr separation between them determines where you are pointing. For this, pattern recognition and star catalogues are used. To improve pointing, the star "images" are defocused (to create a Gaussian distribution), which improve the determination of the centre of a celestial object as not all of them can be considered as point sources. A star tracker delivers a full attitude determination with up to 8Hz. Speed is the key so ADA or today C++ programming language is used. For extremely time critical operations, even machine coding is utilised. I've not a full understanding of Audiveris but from what I've read so far, it seems that some of these techniques are implemented. Great respect. |
As you noticed in #538, you can modify the maximum heap space as a jvm argument passed to Gradle.
This is OK when you launch Audiveris from Gradle. When launching Audiveris installed by the Windows installer, there are two system environment variables you can use to pass JVM arguments:
Set one of these to something like -Xmx2G, as above. I will need to update the handbook. |
Thank you ! |
I’m not sure if I should put my comments and problems under Issues or Discussions so you may have to correct me. This first one, I put under Issues.
I’m a beginner using Audiveris. Overall I think the initiative for such a program is great and, of course, it’s not perfect. In fact, none of the Music Recognition programs I’ve tested so far (so far I’ve used Audiveris, SharpEye and CapellaScan) deliver an error free output.
Computer / Software environment
As an experiment, I’ve performed OMR on Dvorak’s 9th symphony. At first on very good quality output from Lilypond (which I’ve engraved earlier) and secondly from a scanned score from an original I had at home but first a few word regarding Audiveris StartUp
Error messages
LogUtil. Property logback.configurationFile not defined, skipped.
LogUtil. No C:\Users\tommy\AppData\Roaming\AudiverisLtd\audiveris\config\logback.xml, skipped.
What is this, and is it important for the OMR process / performance? If yes, what must be done to correct it?
Storage of Audiveris “products”
Can’t this be setup such that both are stored in the same place, e.g. were the original pdf-file is stored. An additional subdirectory s not needed as far as I can judge but maybe there is a logical explanation for this.
As it is now, you “polluting” the mass memory with a lot of files and subdirectories which, in the end, you probably forget to remove when you are finished.
Memory Limits
Performing OMR I had to split Movement 1 in three parts as because of too many errors. One of the typical error messages is
Caused by: java.lang.OutOfMemoryError: Java heap space.
I’ve read some postings about this, e.g. #538. What is the default setting which you get when you use the Windows installer? It looks like it can be increased but can it be done without recompiling the code? This is something I never done before.
OMR Problems
If there is a need, theses will be covered in separate posting
The text was updated successfully, but these errors were encountered: