loading soundfonts larger than 32 MB

leogra1 · May 7, 2003, 09:54 AM

Hello,

How can I load soundfonts larger than 32 mb on Kx soundfont manager?

I use Windows Xp Professional and 256 MB RAM

Thank you.

RIV@NVX · May 7, 2003, 02:17 PM

I can load up to 119MB (it's Win2k/XP/2k3 server memory managment thing).
What's the problem?

leogra1 · May 8, 2003, 11:28 AM

when i try to load a sfbank with ie 64mb a message of error appears saying ERROR LOADING SOUNDFONT or something like that... excuse me for my english... i've been tweaking the windows xp memory managent register, but is the same... ERROR LOADING SOUNDFONT...

AUDIGY 2
256 MB RAM
Kx drivers v.3532

Thank you...

Whobetta · May 9, 2003, 11:47 PM

I've had the same problem for a while now. With creative drivers I can load the FLUID soundfont which is up to 141mb, but with KX drivers anything over 32mb gets an error no matter how much tweaking I do..

its_bagman · May 7, 2004, 11:01 PM

I finally got the KX drivers to work (thank goodness) after uninstalling and reinstalling win98 on my machine. I hope you are joking - most of my soundfonts are 42 megs in size, and I combine them all in many of my midi work...

I'm going to lurk the boards to hopefully find a reason for this (in fact, those that are over 10 megs seem to cause my system to hang). If this is the case, then why install the KX drivers in the first place if you can't use high-quality soundfonts?

lucioblues · May 7, 2004, 11:58 PM

Quote:

Originally posted by leogra1

Kx drivers v.3532

v.3532 ?!?!?!?!

try:

Latest driver version
5.10.0.3537

NightBreed · May 8, 2004, 04:57 AM

As of v3537 My soundfonts go well over the 200meg size. Keep in mind that you can only load half your physical memory size as far as soundfonts go. So if you have 256 megs, then the largest soundfont would be 128 megs.....

its_bagman · May 8, 2004, 02:34 PM

Ok, the soundfonts DO load, they just take longer

However, I'm still limited by a 138 (or so) Cap. Which is strange, because according to the FAQ, it should be at least 384 (I'm using win98se).

Other strange thing. I have a piano soundfont that's 120 megs large. When I try to load it, I get a BSOD. The 138 meg piano soundfont won't load (says it's too big).

Of course, I can't try the 'increase the page pool size' trick, because that option isn't in my registry (since I'm using win98se). So I'm a little confused.

Does anyone here have the same problem (win98se users only).

Thanks!

NightBreed · May 8, 2004, 11:05 PM

Soundfont memory also has alot to do with how much memory you have left over once everything else in windows has run. ie. you have your initial ram, for example, 256 megs installed.. then you boot to windows and it's programs and services takes up about, say 60 megs.. then you have 256-60 to work with... so that's 196 megs, then you can load half that in soundfont size which is a 98 meg file...

if you want to reduce alot of memory load, you can try using bblean as an alternative windows shell..
Check it out here http://bb4win.sourceforge.net/bblean/

That uses less memory then the standard windows explorer shell, so you should get more memory for soundfonts

its_bagman · May 9, 2004, 03:32 AM

Naw I have 512 megs of ram, with a 128 meg page file.
The soundfont "memory progress bar" in KXmixer seems to be maxed out around the 130 meg mark, and it appears to be hard wired somehow.

I'd be really curious to hear from win98se or ME users about their maximum soundfont size (since the FAQ informs it should be a max of 384 for SE and 164 (or so) in XP if you don't use the paged pool trick).

NightBreed · May 9, 2004, 04:39 AM

ever since the new sfman32.dll was released, the paged pool trick is not needed. That trick never worked with kx anyway.

May 7, 2003, 09:54 AM	#1
leogra1 DriverHeaven Newbie Join Date: Dec 2002 Posts: 13 Rep Power: 0	loading soundfonts larger than 32 MB Hello, How can I load soundfonts larger than 32 mb on Kx soundfont manager? I use Windows Xp Professional and 256 MB RAM Thank you.

May 7, 2003, 02:17 PM	#2
RIV@NVX Freedom is a feature. Join Date: Jul 2002 Location: Croatia, Rijeka Posts: 4,476 Rep Power: 0 System Specs	I can load up to 119MB (it's Win2k/XP/2k3 server memory managment thing). What's the problem? __________________ -- Vedran

May 7, 2004, 11:01 PM	#5
its_bagman DriverHeaven Junior Member Join Date: May 2004 Posts: 23 Rep Power: 0	you are kidding, right? I finally got the KX drivers to work (thank goodness) after uninstalling and reinstalling win98 on my machine. I hope you are joking - most of my soundfonts are 42 megs in size, and I combine them all in many of my midi work... I'm going to lurk the boards to hopefully find a reason for this (in fact, those that are over 10 megs seem to cause my system to hang). If this is the case, then why install the KX drivers in the first place if you can't use high-quality soundfonts?

May 8, 2004, 02:34 PM	#8
its_bagman DriverHeaven Junior Member Join Date: May 2004 Posts: 23 Rep Power: 0	Ok, there we go Ok, the soundfonts DO load, they just take longer However, I'm still limited by a 138 (or so) Cap. Which is strange, because according to the FAQ, it should be at least 384 (I'm using win98se). Other strange thing. I have a piano soundfont that's 120 megs large. When I try to load it, I get a BSOD. The 138 meg piano soundfont won't load (says it's too big). Of course, I can't try the 'increase the page pool size' trick, because that option isn't in my registry (since I'm using win98se). So I'm a little confused. Does anyone here have the same problem (win98se users only). Thanks!

May 9, 2004, 03:32 AM	#10
its_bagman DriverHeaven Junior Member Join Date: May 2004 Posts: 23 Rep Power: 0	memory Naw I have 512 megs of ram, with a 128 meg page file. The soundfont "memory progress bar" in KXmixer seems to be maxed out around the 130 meg mark, and it appears to be hard wired somehow. I'd be really curious to hear from win98se or ME users about their maximum soundfont size (since the FAQ informs it should be a max of 384 for SE and 164 (or so) in XP if you don't use the paged pool trick).

May 8, 2003, 11:28 AM	Thread Starter #3
leogra1 DriverHeaven Newbie Join Date: Dec 2002 Posts: 13 Rep Power: 0	when i try to load a sfbank with ie 64mb a message of error appears saying ERROR LOADING SOUNDFONT or something like that... excuse me for my english... i've been tweaking the windows xp memory managent register, but is the same... ERROR LOADING SOUNDFONT... AUDIGY 2 256 MB RAM Kx drivers v.3532 Thank you...

May 9, 2003, 11:47 PM	#4
Whobetta DriverHeaven Junior Member Join Date: Dec 2002 Location: Canada Posts: 30 Rep Power: 0	I've had the same problem for a while now. With creative drivers I can load the FLUID soundfont which is up to 141mb, but with KX drivers anything over 32mb gets an error no matter how much tweaking I do..

May 8, 2004, 04:57 AM	#7
NightBreed DriverHeaven Addict Join Date: May 2003 Location: Philadelphia, PA Posts: 380 Rep Power: 0	As of v3537 My soundfonts go well over the 200meg size. Keep in mind that you can only load half your physical memory size as far as soundfonts go. So if you have 256 megs, then the largest soundfont would be 128 megs.....

May 8, 2004, 11:05 PM	#9
NightBreed DriverHeaven Addict Join Date: May 2003 Location: Philadelphia, PA Posts: 380 Rep Power: 0	Soundfont memory also has alot to do with how much memory you have left over once everything else in windows has run. ie. you have your initial ram, for example, 256 megs installed.. then you boot to windows and it's programs and services takes up about, say 60 megs.. then you have 256-60 to work with... so that's 196 megs, then you can load half that in soundfont size which is a 98 meg file... if you want to reduce alot of memory load, you can try using bblean as an alternative windows shell.. Check it out here http://bb4win.sourceforge.net/bblean/ That uses less memory then the standard windows explorer shell, so you should get more memory for soundfonts

May 9, 2004, 04:39 AM	#11
NightBreed DriverHeaven Addict Join Date: May 2003 Location: Philadelphia, PA Posts: 380 Rep Power: 0	ever since the new sfman32.dll was released, the paged pool trick is not needed. That trick never worked with kx anyway.