Crash when deleting soundfont after Load from score (load doesn't update synth window)

• Feb 8, 2014 - 03:28
Type
Functional
Severity
S2 - Critical
Status
closed
Project

Just thought I'd mention I found it difficult to convince the nightly build to switch soundfonts. When it does load up the new soundfont, it crashes. (Win 8.1 Pro, 64-bit, Core 2 Quad 2.66 2.67HGz, 8GB Ram)

Attachment Size
angscopy-soundfont-switch-crash.txt 40.65 KB

Comments

What soundfont are you trying to switch to? If not one easily found online, can you post it? Does it crash every time? Or perhaps just for certain scores? Precise steps to reproduce always help.

(Sorry I responded to this, but must have forgotten to click send.)

It happens when switching from GeneralUser to Sonatina. To get it to switch, I have to delete the existing sound font from the main list, add the Sonatina font, and as soon as I click save, it crashes immediately. (I did get the sound font to work on V1.3. Turns out it's not as great as someone thought.)

You can get the Sonatina sound font here:
https://dl.dropboxusercontent.com/u/1071779/Sonatina_Symphonic_Orchestr…

I've come across a few other little glitches or things that are a bit annoying (the page jumps when cutting/pasting measures, for example), but aside from that, I really, really love the new version so far. Much more intuitive and overall nicer to use.

You say you have to delete the GeneralUserGS soundfont first to get it to switch - what do you mean? Are you saying that if you press the Add button, nothing happens? Or that if you then select Sonatina, it doesn't show up in the list? Or that it shows up, but when you play the score, it still uses GeneralUser? I have no trouble adding Sonatina whether I first delete GeneralUserGS or not. It automatically adds to the top of the list. But if you want the score to actually use sounds from that soundfont, you need to bring up the mixer and select which sounds you want to use for which staves- otherwise it keeps using the sounds it was already using.

As for the crash, I cannot reproduce it, so maybe it is specific to the score you have open. Could you post it, and precise steps to reproduce?

FYI, the page jump issue is reported as #24243: Paste scrolls to top of system.

Status (old) needs info closed

Yes that's exactly what was happening. I was removing GeneralUser from that first list to get it to use the new sounds on the current score. It wouldn't select the sound fonts (didn't realize I had to select them in the mixer). Think that's why it was crashing... it was trying to use a sound font that was no longer there... So, user stupidity. (Bacon sandwich for you?)

Is the crash when attempting to add a subtitle to an existing score reported as well? I can't seem to add one to either of the two scores attached here

Attachment Size
Rod_Alexander's_Reel.mscz 2.08 KB
Royal_Majestic_Waltz.mscz 27.53 KB
Status (old) closed active

Well, no matter what you do with soundfonts, it shouldn't crash. And it doesn't for me if I do the following:

1) load a score
2) View / Synthesizer
3) Select existing soundfont (which I have previously set to be GeneralUser GS)
4) Delete
5) Add
6) Select Sonatina Symphonic Orchestra
7) Play score

It plays using the new soundfont as best as it can - instruments may have wrong sounds or missing sounds, but it plays. And definitely doesn't crash.

So, again, it would help if you posted the score you are having problems with and exact steps to reproduce. Whether you are doing it right or wrong, it shouldn't crash.

Oh, and regarding crash adding subtitle - there was a period of a few days a couple of weeks ago where the builds would crash any time you added text to a score. That was fixed maybe two weeks ago? I don't see a problem adding a subtitle to your score using a recent build. If you do, then you should post a separate issue, include the score again and steps to reproduce (all I did was open, Add / Text / Subtitle, type hit Esc, and all was fine).

Steps for the soundfont issue:

1 - open program
2 - load score
3 - open synthesizer
4 - delete "GeneralUser" (existing) sound font
5 - click "add" and choose sontina (new font)
6 - click "load"
7 - click "x"
8 - reopen synthesizer
9 - highlight the Sontina font in the list
10 - click "delete"
*crash*
*potential soft weeping if you forgot to save*

I will double check to make sure I have the most recent nightly build. I've attached the score here for you

Attachment Size
Lux_Aeterna_in_Tenebris2.mscz 19.72 KB
Title Crash when switching soundfont Crash when deleting soundfont after Load from score (load doesn't update synth window)

The good news (?) is that I can confirm that following that series of steps with that score *does* crash.

The problem seems to be with the "Load" step. Not sure why you're doing this, but if you skip it, it works.

I think "Load" is supposed to load soundfonts whose names were previously saved in the score. Looking at your score in an editor, I can see that GeneralUser and Fluid are the sounfonts that were saved with the score. So when you hit "Load", those soundfonts were loaded, and the dialog should have been updated to reflect this - I think that's the bug. I think Sonatina should have been removed from the list, and GeneralUser and Fluid displayed instead. So Sonatina should not have been available for you to delete. Trying to delete a soundfont that is not even loaded - that's what caused the crash.

I've updated the title to more accurately reflect the problem - thanks for providing the necessary information to allow this to be reproduced!

I think it was a misunderstanding on my part. The instruments weren't updated in the mixer. I assumed I would have to "load" the font to the score. I assumed it was attempting to load the deleted font, but wasn't sure. So glad you were able to pinpoint the issue. Thank you so much for your time.

If you need help "breaking" anything else, just give a shout. I'm pretty good at finding the silly stuff.

Cheers and thank you again!

Angie

Status (old) active closed

I can no longer follow the steps in #9; GeneralUser is not on the list to delete. I'm going to mark this closed, although it's certainly possible there is still a way to trigger the underlying problem.