Nightly build of 20150224 & Mixer & Burst Noise

• Feb 26, 2015 - 23:56

Hey,

I was trying out the different Sound Fonts I think they are called in the MuseScore Nightly Build of 20150224 with the Mixer & 'Burst Noise' and that caused MuseScore to be unable to play the score I had typed in.

However, restarting allows sound to play again.

Also, some sound fonts have what I can best descript as a bit of static. I'm not sure if this is in the sound fonts or has something to do with my hardware.

Thanks.

Ciao


Comments

It would be really helpful to see the score file and learn which sound fonts you tested with. Only this way we can try to reproduce the problem and fix it.

Could you definte what you mean by "Burst Nosie" in this context? Is that the name of a sound font? Or a particular sound within some particular sound font? Or you are you just trying to describe the effect you hear? Your score plays just fine on my computer. Is there something one needs to do using the Mixer to hear a problem?

EDIT: ouch - I figured it out, "Burst Noise" is the name of one particular sound within the default soundfont, and if I use the Mixer to change to that sound, bad things happen!

Also, you mention "static" in some sound fonts - which sound fonts did you try? Or did you perhaps mean, some specific sounds within the default soundfont?

In reply to by Marc Sabatella

OK, so you found the Burst Noise sound font I was talking about.

I tried also every sound font.

The static I spoke of was with regards to a few particular sound fonts chosen in the Mixer with the score I uploaded.

Some of that static might be intentional - like simulating fringe radio station play or an old analogue recording material but if that is the case it'd be nice to have that marked clearly in the title so we can know this is how the sound fonts is intended to sound and it's not a problem with hardware, MuseScore, or the sound font. e.g. Violin (AM Radio), Brass (Needle in Groove or RCA Victrola), and as on.

Before the end of today I will go through each sound font using the above score and list the ones with static or popping noises and those that don't. I'll include my hardware specifications and the drivers used too, at least for the audio portion of the HW.

Thanks.

In reply to by JackJura

BTW, to be clear: what you are describing are not sound fonts - they are individual sounds *within* the default sound font. When you open the Mixer, you are not changing sound fonts - you are changing from one sound to another *within* the current sound font. To change sound fonts, you need to go online, download & install some (into your Soundfonts folder), and use View / Synthesizer to select between them. Changing sound fonts means a whole new set of sounds - or more particularly, different sounds for the same instruments. So trumept is still trumept, but it will sound different. Just like changing from Times New Roman to Arial means you get the same lettersm but they all *look* different.

So anyhow, if you do find issues with particular sounds within the default soundfont, by all means do post about them. There is a known issue with Clarinet, and apparently Burst Noise as well (no idea what that one is even supposed to sound like). Anything else you find probably is not a known issue, although there are issues with Tuba in some versions, depending on which build you are using.

In reply to by Marc Sabatella

Thanks, I am learning about these midi and sound font things as I go.

I will post my results and possibly after I do that replace my audio driver with Windows Generic Drivers and retest to be sure it's not the drivers although they are distributed via Windows Update and over 2 years old I've learn that doesn't actually mean they are the best drivers.

I will try out other sound fonts later. It makes no sense now at my skill level but as an amateur and beginner I thought me trying MuseScore 2.0 Beta would be good test.

I think Burst Noise may be intended to do what it did - namely cause MuseScore to stop working as a test. Sound Font author would need to answer that.

In reply to by JackJura

If I were you I would leave your audio drivers alone.

You are almost certainly better with the manufacturer's drivers rather than the windows generic ones.

Please list the sounds there are issues with so i can see if anything can be done about it.

Unfortunately many of the problems with FluidR3Mono exist at sample level.

Hmm yes - I see what you mean!

A little bit of digging reveals that Burst Noise is part of the GS sound set namely Patch 126 Bank 9

The sound designers were obviously confusing Jovian Bursts with Burst Noise as the sound is supposed to sound like popping corn, but playing the sound in Viena reveals it is composed of Harpsichord and Seashore sounds processed with extreme modulation and envelope parameters.

This is overloading MuseScore's FluidSynth engine and causing the digital clipping you can hear.

The obvious solution is to remove the sound as it is not part of the GM sound set, and FluidR3 does not contain the full GS soundset anyway.

As I said in my other comment - please list the instruments you have found distortion in. I am in the process of trying to improve the quality of the FluidR3 sounds, and you can always get the latest version of the uncompressed SF2 here:

https://www.dropbox.com/s/soi5tj3s3113f26/FluidR3Mono_GM_sf2.zip?dl=0

In reply to by ChurchOrganist

OK, I am downloading FluidR3. I will listen and describe the results of both the default & FluidR3Mono.

I will leave my audio drivers as is.

I hope to finish this today.

As far as the level of authenticity of each instrument's sound I am not the best judge of that, I'm just reporting if I hear some type of static that clearly isn't the instrument(s).

I will say to my ears I don't hear my Casio CTK-6200 set on Stereo Grand Piano as sounding any better than the Yamaha Grand Piano or vice versa.

In reply to by JackJura

Hey everybody,

While I'm listening to all the instruments in the default sound font I noticed a bug. On the second Piano (the teacher's accompaniment) on the 5th measure is a rest that shouldn't be there and I can't delete.

I suspect MuseScore introduced it but I haven't a clue how. I've compared the score I uploaded in this thread and it is correct but the one I've been using to try out different instruments has the stray rest I mentioned above.

???

Attachment Size
Good_Night,_Ladies.mscz 7.65 KB

In reply to by Marc Sabatella

Ah, thanks. CTL-R works. I couldn't delete because MuseScore keeps me from making impossible music. :-)

Is it possible to make a score as read-only that can be toggled on-off for the sheet music once completed to satisfaction? I mean in the markup language MuseScore uses, not in the OS.

In reply to by JackJura

No, that is not currently possible, but it's something we would like to see. There is *partial* support for this internally, but unfortunately, it makes some things impossible that should not be (I forget what, exactly). Probably at some point after 2.0 this will be revisited to try to find a good solution.

In reply to by ChurchOrganist

OK, thanks.

I have went through the default MuseScore 2.0 sound font up to Vibraphone and rather than continue on it since you are in the process of updating it I will list what I've already listened too and use the new sound font to evaluate.

Here is what I've done although my opinion of what I think is happening to create static probably
isn't technically accurate.


hmm...I'll upload as a plain Windows 7 bit text I typed in notepad

Thanks & now I'll switch to the new font you gave the download link to and start again.

OK, I copied into the MuseScore 2.0 soundfonts directory:

(*\Documents\MuseScoreDevelopment\Soundfonts) all the example fonts from the MuseScore Soundfont page and the sountfonts linked to here earlier (103) and then in the nightly added FluidR3Mono_GM2-103.sf2 and as it was already at the top of the list I made it the default. The MuseScore\sound directory still has the SF from the nightly build of 20150224. So the score I created and saved will now use the soundfont FluidR3Mono_GM2-103.sf2 I set as default correct?

Attachment Size
SF Eval.txt 6.27 KB

In reply to by JackJura

OK, this is a long list and maybe I start again from the beginning after I get the Logitech speakers to hook to my PC rather than the Panasonic earbuds. I will also be able to compare my Casio CTK-6200 against MuseScore and instrument selected to be used in the soundfont, but I am and I think most that use MuseScore are more interested in clean sound at reasonable volumes that doesn't break down when very loud than with how close my ear thinks they sound is like the CTK-6200.

At any rate, I'm to Ocarina and generally most everything sounds good at 75%, more at 65%, more at 50% and very few at 95% or higher with these earbuds.

I will attach my opinion of each that I've evaluated in a text file.

I am using the FluidR3Mono_GM2-103.sf2 soundfont.

I don't know how relevant this is but somewhere around 12K Hertz I don't hear anything so maybe I don't hear very high synth, sine, saw, and odd generated frequencies others do.

Ciao

Attachment Size
SF Eval - FluidR3 103.txt 4.6 KB

In reply to by JackJura

Thank you for doing this.

I've checked the reed organ, and there is no popping in the samples or when I played back via MuseScore 2 latest build, so this must be something to do with your system.

The synth brass is supposed to sound electronic :) The clue is in the prefix "synth".

There are known problems with the clarinet sound at sample level which I am in the process of rebuilding from scratch using fresh samples. Sadly this won't be ready for the MuseScore 2 release as finding loop points is extrememly time-consuming.

Not sure what you mean about the popping in the Acoustic bass?

In reply to by ChurchOrganist

I know some synth is desired to sound like electric noise but some synth is desired to sound like the real instrument. Anyway, it is the trumpet and other brass, not the synth brass 1 & 2, I was talking about. I feel the problem might go away when the speakers arrive and I'll do the list again.

I did notice that some of what I think I hear as popping static coincides with changing measures and tends to happen more frequently after a rest. For some of them at least I think my ears are detecting a slight difference when the notes are struck and it's not really a popping static noise like it seems. Again, the speakers should help be determine that.

Ciao

In reply to by ChurchOrganist

I wonder, since the clarinet seems to be a sore point for several users - would be possible to swap it out entirely for the one in another soundfont? The one in TimGM6mb is pretty terrible in other ways, but maybe S. Christian Collins would be amenable to us borrowing that and mybe a couple of other sounds from GeneralUser GS? I assume that's easier than building a sound from scratch given just WAV files, but I really don't know the process at all.

In reply to by Marc Sabatella

The problem with that Marc is the licencing.

GeneralUser GS contains samples of unknown origin.

TimGM6mb is GNU General Public Licence version 2 which does not cover the extraction and use of the samples.

It would be better, therefore, just to be patient and wait for me to finish the new clarinet. I'm expecting to have something useable (ie beta) by Easter.

Do you still have an unanswered question? Please log in first to post your question.