Runboard.com
You're welcome.
Smart Score User Forum

runboard.com       Sign up (learn about it) | Sign in (lost password?)


 
clashway Profile
Live feed
Blog
Friends
Miscellaneous info

Registered user
Global user

Registered: 07-2018
Posts: 9
Karma: 0 (+0/-0)
Reply | Quote
Problem Changing Dynamic Properties


I'm using Windows 10 and SS X2.

When applying dynamic symbols like "mf" etc, I cannot reliably edit their value using properties. I am aware that each staff needs its own mark. The problem I'm seeing is the MIDI data is not responding to property changes in an expected way.

First off, according to the documentation, the default value for the "mf" is 80. Yet it seems to be closer to 70 in the MIDI data.

Second, if I make a change to this value, using the property of the given mark, nothing changes in the MIDI display or playback. It's as if the property doesn't get updated.

However, if I open the documents preferences dialog and either use the "Apply" or "OK" buttons. The MIDI data then updates. Though the update is still not correct. I.E. a value of 80 in the properties shows as about 70 in the MIDI view.

I would think this is simply a scaling error in the MIDI view, but I can set a crescendo to end on 80 and the MIDI data view shows this correct value.

To summarize:

1) Dynamic marker date (i.e., symbols like 'mf' or 'ff') do not update when their properties are changed unless I open and update the document preferences.

2) When dynamic markers are inserted or changed, the MIDI data is incorrect. For example, MIDI velocity is 70 when property is 80.

Has anyone else seen this or know if there is something I'm doing wrong.
8/2/2018, 7:00 pm Link to this post Send Email to clashway   Send PM to clashway Blog
 
mikey12045 Profile
Live feed
Blog
Friends
Miscellaneous info

Registered user
Global user

Registered: 02-2014
Posts: 250
Karma: 1 (+1/-0)
Reply | Quote
Re: Problem Changing Dynamic Properties


Keep in mind that SmartScore is primarily a program for scanning music. Beyond that, it has basic notation and playback abilities.

If you need better playback control, you might want to look at a DAW.

---
SSX2 Pro v. 10.5.8, Mac 10.13.3, Finale 25
8/3/2018, 6:02 am Link to this post Send Email to mikey12045   Send PM to mikey12045 Blog
 
clashway Profile
Live feed
Blog
Friends
Miscellaneous info

Registered user
Global user

Registered: 07-2018
Posts: 9
Karma: 0 (+0/-0)
Reply | Quote
Re: Problem Changing Dynamic Properties


Certainly a major aspect of it is creating MIDI files. And compared to the optical recognition, once you have that information creating corresponding MIDI data is close to trivial from a technical standpoint. It's work though. Even simple things are a lot of work in software when associated with a user interface.

And what I'm finding are bugs, not missing features. I don't expect it to do everything my DAW does. But, it is supposed to play and export MIDI data with articulations.

Now I have yet to check. It could be the MIDI data is correct when exported and the problem I'm seeing is just the MIDI view within the program. It might even be that it is playing back correctly. I was using the MIDI view to understand what the dynamic markings were actually doing.

In any case, the response I'm getting from Musitek support is that playback issues will be resolved in the 64 bit version coming out next year.

At this point nothing is a major obstacle. But being new to the software I'm wasting a lot of time trying to figure out what I'm doing wrong to ultimately find out it is a software bug.

Anyway, I'm going to study this a bit more and see if this is perhaps just a MIDI view problem.
8/3/2018, 9:16 am Link to this post Send Email to clashway   Send PM to clashway Blog
 
clashway Profile
Live feed
Blog
Friends
Miscellaneous info

Registered user
Global user

Registered: 07-2018
Posts: 9
Karma: 0 (+0/-0)
Reply | Quote
Re: Problem Changing Dynamic Properties


As a follow up, I did investigate this, and as near as I can tell, what the MIDI view shows is what gets exported or saved in the MIDI file.

So I've concluded that I need to open the either the "document preferences" or the "program preferences" dialogs and press "OK" to get the dynamic settings in the score applied to the MIDI data. Also, saving, closing and re-opening the file does this.

The scaling error is also real. Setting the values to the maximum of 127 results in MIDI data set to 107. Setting the minimum of 10 gives MIDI data of 8.

Not to say this is exact, but for me to get a desired value for the MIDI velocity using the dynamic markers, the marker value has to be set based on this formula (not proven) but approximate for a few values tested.

Property value = [sign in to see URL] x (desired value - 8) + 10

This only applies to the markings like "mf" "p" "ff" etc. This scaling wouldn't matter much at all except other things do not have this same error. For example the hairpins (crescendo etc), values seems correct.

Also, because of this, it's not possible for these dynamic markers to go above a MIDI velocity value of 107.

I'm running on Windows 10 and SS X2 version of [sign in to see URL]

Another way to look at this is to ignore the issue and adjust the hairpin properties to match the default dynamic values. Since the hairpins don't automatically match the dynamic levels on each side anyway, these need to be edited. So in that case, invert the previous equation to adjust hairpin values to match the property value of the dynamic markers.

Hairpin value = (dynamic marker property value - 10 )/[sign in to see URL] + 8

I know this is likely only of interest to the more nerdy and obsessed types, but here is what is happening for me for what it may be worth to someone else.
8/3/2018, 1:23 pm Link to this post Send Email to clashway   Send PM to clashway Blog
 
ZootS Profile
Live feed
Blog
Friends
Miscellaneous info

Registered user
Global user

Registered: 10-2008
Posts: 748
Karma: 14 (+14/-0)
Reply | Quote
Re: Problem Changing Dynamic Properties


Although it isn't a concern for my use of SSX2, thanks for the info on the dynamics and contacting Musitek support. As you have seen, this forum is a user forum with little traffic and even less participation by Musitek.

I agree with Mike that the principal use of SS is for scanning and correction of the scans and I'm sure he'll agree that doesn't mean that the program can't be improved especially if the fixes concern some basic functionality. The Pro version is not an inexpensive giveaway program and thus the "implemented features" should work properly.

Did you get your earlier problem of weak Garritan sounds playback resolved?

---
SmartScore ProX2 - since it came out, SmartScore ProX before it
Windows 10 - since officially released, Win 8.1, Win 7 before it
8/4/2018, 6:09 am Link to this post Send Email to ZootS   Send PM to ZootS
 
mikey12045 Profile
Live feed
Blog
Friends
Miscellaneous info

Registered user
Global user

Registered: 02-2014
Posts: 250
Karma: 1 (+1/-0)
Reply | Quote
Re: Problem Changing Dynamic Properties


OK, you've certainly gone deeper than I would have. And I'll agree that setting A should equal setting B.

What did tech support say?

---
SSX2 Pro v. 10.5.8, Mac 10.13.3, Finale 25
8/4/2018, 6:33 am Link to this post Send Email to mikey12045   Send PM to mikey12045 Blog
 
clashway Profile
Live feed
Blog
Friends
Miscellaneous info

Registered user
Global user

Registered: 07-2018
Posts: 9
Karma: 0 (+0/-0)
Reply | Quote
Re: Problem Changing Dynamic Properties


quote:

ZootS wrote:

Did you get your earlier problem of weak Garritan sounds playback resolved?



No. They simply said that this too would be fixed in the upcoming 64-bit version. Which makes no sense to me since there's no reason at all this shouldn't work properly in a 32-bit version. I don't think this problem with Aria Player/Garritan is new. Same with the dynamic editing problem of this thread. That's purely a user interface issue. Something completely within their control to fix at any time.

I really hate to throw stones, but it seems that "it will be fixed in the 64-bit release" is going to be the response on any issue at this point. Of course I understand that they have to bundle problems and address them in future release and cannot create a release every time a problem comes up.

It's frustrating because I'm finding this program bugging and unstable. Not something I expected in a program that cost me $300.

It crashes (closes unexpectedly) several times a day. I pretty much save after every edit now. My system is otherwise quite stable. I don't have problems with other programs. Of course, that doesn't mean it isn't specific to my system, but when all the Musitek has to say to every problem, is "we'll fix it in the 64 bit release next year", that's not helpful.

It's really unfortunate, because I think the real meat of this software, the optical recognition is quite powerful. Not perfect, but really does get about 99% or more right. But, these bugs in the otherwise straight forward things shouldn't be there. And frequent crashes are simply unacceptable on a commercial piece of software.

But, ultimately I'm getting done what I want, warts and all. So I'll be looking forward to the release when it happens. But, software releases (from any company) have a way of getting delayed, and delayed again. So, I'm not going to wait on it.

I really do like being able to scan in music and convert it to MIDI. And SS X2 allows me to do that, if a bit frustrating. So it's sort of a love-hate relationship right now.


8/4/2018, 8:40 pm Link to this post Send Email to clashway   Send PM to clashway Blog
 


Add a reply





You are not logged in (login)