• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Solved Why does S1 not load the GM sounds?

John Vere

Active member
I updated my title as the first one has resulted in zero answers.
So what my question is why does Studio one ask if you want to load GM sounds when you open a midi file? Then it switches to 44.1 ( very annoying) and then there is no instruments loaded. Just midi tracks.
Google say's it will use Presence?

that's not a GM synth? I tried manually adding it but it doesn't (by defualt?) recognize GM patches.

There’s nothing in the manual I can find as well as nothing in the tutorials.
 
Last edited:
I downloaded the VST 2 version of VST Synth Font and it works fine. But still want to know why it asks to load GM and nothing happens.
Did it used to use the MS Wavetable?
 
Last edited:
Why does Studio one ask if you want to load GM sounds when you open a midi file? Then it switches to 44.1 ( very annoying) and then there is no instruments loaded. Just midi tracks.

How - exactly - are you opening MIDI files?

I just drag and drop them via the Browser. Never get asked anything. The file simply appears on the track I drop it on - ready for work?

VP
 
As I said in the post. When I open a midi file.
This is the preferred method of using GM midi multi track files in the Daw’s that work this way. Example Cubase, Mixcraft and Sonar.

The reason you need to do this is that opening a GM file will import all the data and not just the notes. With out the data there is no tempo as example.
That is why you drag and drop midi if you don’t want tempo data.

Cubase and Sonar need a simple configuration in preferences to automatically insert the player.
Mixcraft just like S1 asks you if you want to use the Acoustica instruments.

I have a feeling in the past it might have directed the tracks to the MS Wavetable synth which is being phased out by Windows.

As example it is no longer an option in Sonar and Cubase.
And I see that S1 does not have MS Wavetable or Virtual midi synth as midi output options.

So once again, why does it ask if you want to use GM sounds. And then nothing happens. Does this need to be configured like in Sonar?
 
Last edited:
As I said in the post. When I open a midi file. This is the preferred method of using GM midi multi track files in the Daw’s that work this way. Example Cubase, Mixcraft and Sonar.

Well - that may be a "preferred" method to you - but there are always better and easier ways. One of which I just mentioned.

And you asked about why you were getting so many questions, sample rate changes and so on when opening a MIDI file. I offered a solution to your question.

VP
 
Last edited:
There's a difference bewteen dragging a MIDI track into an existing arrangement and dragging it onto the start page or other areas outside of the main arrangement.

The latter will create a new song - and ask you if GM sound should be loaded (if program changes or or other GM data is detected).

The question is if you have the Presence Artist Sound Set installed. It contains the GM sound bank and. If this Sound Set is missing, it might be the reason why nothing happens after choosing to load GM instruments.

If you do not like the answer - not much I can do about that. Maybe time to use one of those other DAWs you mentioned?
@Vocalpoint Please... stay friendly and constructive!
 
There's a difference between dragging a MIDI track into an existing arrangement and dragging it onto the start page or other areas outside of the main arrangement.

The latter will create a new song - and ask you if GM sound should be loaded (if program changes or or other GM data is detected).

The question is if you have the Presence Artist Sound Set installed. It contains the GM sound bank and. If this Sound Set is missing, it might be the reason why nothing happens after choosing to load GM instruments.

Would have been helpful to know these differences.

This is literally the first I have ever heard (since 2011) of how this works.

Thanks!

VP
 
I forgot as well, because from time to time, I'll see the General MIDI soundset, but never load it, as I simply dont use it. Good that its available for those that need it. Thanks for the solution, Lukas.

I was simply going to ask the OP which GM sound source were they going to load.

Anyhoo.... 👍
 
Must be this one...

1762449187738.png


Which I never load either.

VP
 
Thanks once again @Lukas that was the problem. I sort of skipped all the installation extras just to save time and I had not downloaded any of the files needed by Presence. So that was the mystery. It was trying to load something that was not there. Works great now.

And I can live with the stupid 44.1 thing, that takes 2 seconds to fix. Just remember not to have your volume up because of the click when it changes sample rates.

And for those who understandably don't know how to work with GM midi it is super important to OPEN a midi file in your Daw.

Try it it is easy to test. Grab any GM midi file. OPEN it in Studio one and you will see the correct tempo plus all the tracks a correctly labled and there are instrument assignments for each track. There's also a zillion other things might be in the midi file. And now I have the Presence set up, it plays the song more or less as it was intended to sound.

Now take the same midi file and drag it to a empty project. All you will get a a nice colorful bunch of midi tracks. No tempo, no channels, no nothing. Dragging midi is how you add midi clips to existing projects where you don't want that data. All Daw's that I have used work this way. The exception in Waveform which the only way is drag and drop, but it does ask if you want the tempo map.

Anyhow mark this as SOLVED thanks again, I new it must be a setting or something.
 
Last edited:
I made a quick tutorial on the subject seeing as how I couldn't find one anywhere.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
I made a quick tutorial on the subject seeing as how I couldn't find one anywhere.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
Cool video John

And just a gentle FYI on the sample rates. Ideally - for most music production (espeically on Windows), 44.1kHz/24-bit is industry standard.

If you are on a Mac or doing video, 48 kHz is often preferred.

However - at the end of the day - if it is audio - there is zero benefit to choosing 48khz over 44.1khz. Staying in 44.1khz would solve your "glitch" that you showed in your video.

Been doing professional work here since 2002 and not a single client has ever asked me about 48K or requested any delivery of it. It has been 44.1/24bit for as long as I have used a pro DAW.

VP
 
Thanks @Vocalpoint for your kind words.
The 48 / 44.1 thing is definitely due to the fact I work with video. An example is when I am making a tutorial I need the Daw audio running as I screen capture.

The fact Studio one defaults to 44.1 is a small problem and a few weeks ago I was doing a project where I took about 50 of my backing tracks and I needed to swap out the Ample P bass for the Rapture Acoustic bass as well as simplify the drums. The goal was I now don’t play at parties and dances. I now do an acoustic set. All I need is the Bass but a little bit of drums is sort of a fancy click track.
It was also a great way to get used to S1.
These are my own midi files many are my original songs. They are not GM.
So I very quickly developed a workflow that was fast and easy. Changing the sample rate took literally 5 seconds out of the 5 , 10 , 20 minutes to do the other tasks.
By about the 12 th song I was just cranking them out in no time. I think I got it down to under 5 minutes per song unless I found something that needed changing.

Open midi file
Change sample rate
Add loud max to master
Drag and Drop Rapture add patch
Drag and drop SSD drums and choose kit
Remove all the other instruments like piano and keyboards.
Open editor for drums and lower velocity of snare or swap to side stick.
Export as 48/16 wave file.
Drag and drop into You lean Loudness meter to make sure LUFS are around -14.
Done and save and start over.

What this showed me was how fast you can work using Studio one. It did a great job of keeping everything the same song to song.
 
Being on a Mac has nothing to do with 48K sampling rates. Also nearly every video editor I know will import a 44.1K audio file. More than likely up samples it internally.
 
Well I have used 48 exclusively for about 10 years now as far as computer systems go.

I actually started using it back before I used computers. I had 2 Sony DAT recorders I used for mastering. You definitely heard a difference between using the 44.1 and 48.
But I also had( still have) a Yamaha 01/v digital mixer that is only 44.1 / 20 so when I used the SPDIF I was stuck with 44.1.
So even though I knew to my ears that 48 was better, I was stuck on 44.1 until around 2015 when I retired the 01/v.
I truly don’t hear the difference anymore because I’m 72 and you need to yell at me to get my attention!
But I will never forget that I most certainly heard that difference back in 1996.
 
I've also used 48k exclusively for several years. I can't hear the difference but it saves hassle when I score to video, which is only very occasionally.

I'm surprised that S1 changes to 44.1k when dragging a midi file to the home page. Doing the same in Cubase uses keeps the 48K and assigns a piano to the track. Midi files know nothing about audio or sample rates so this feels like a bug in S1.

Apart from that, the only time I see 44.1k is when I fire up some new bit of audio software and it rudely changes the ASIO driver to 44.1K without asking.
 
Well I have used 48 exclusively for about 10 years now as far as computer systems go.

I actually started using it back before I used computers. I had 2 Sony DAT recorders I used for mastering. You definitely heard a difference between using the 44.1 and 48.
But I also had( still have) a Yamaha 01/v digital mixer that is only 44.1 / 20 so when I used the SPDIF I was stuck with 44.1.
So even though I knew to my ears that 48 was better, I was stuck on 44.1 until around 2015 when I retired the 01/v.
I truly don’t hear the difference anymore because I’m 72 and you need to yell at me to get my attention!
But I will never forget that I most certainly heard that difference back in 1996.
I use a Yamaha 01V It has both 44.1K (internal) and 48K sampling rates. If it is locked to incoming sync it will switch to whatever sampling rate it is receiving. (48K max) It is 32 bit internal processing and 20 bit on the input A/D

There is no way you can hear the difference between 44.1K and 48K sampling rates in a controlled blind A/B test.
 
Last edited:
@Davey To be clear- Dragging a midi file will retain sample rate. Opening a midi file is where it will change. I would not call it a bug but a glitch due to probably old coding that was never updated. Im sure it is not hard to fix but I’m probably the only user who noticed so I’ll leave them to fuss with more important things.

@Jemusic My O1v is the very first model that came out. I think they added the higher resolution later. I used to belong to a Yahoo user group based out of Australia and they had a data base of stuff to modify it. I remember downloading something that turned the O1V into a controller for Sonar. It works.
In the late 90’s I had fully automated mix down of 12 tracks digital and 16 tracks of midi. The compressor in them is still considered to be very good as compared to most consumer products that will cost more than $300 each. Problem is that my Motu interface doesn’t have the SPDIF. But I still have my Old Focusrite 6i6 if I want to use that.
 
Back
Top