dynamic soundfont caching?

vmirage · Jun 1, 2003, 01:41 PM

is the kxdriver going to implement dynamic soundfont caching in the future?

**Eugene Gavrilov** · Jun 2, 2003, 11:43 AM

dynamic caching isn't a perfect solution because all SoundFont data should be located in the RAM when needed. if soundfont samples are being swapped to disk it will introduce a very serious lock-up when the corresponding notes are triggered (this will cause ASIO / DirectX / Kernel streaming sync issue)

I know that Creative drivers support dynamic caching, however, their SoundFont implementation in the recent releases is completely different and requires additional CPU processing (and, btw, causes some problems with looped samples)

btw, try to load a huge soundfont (which is bigger than the amount of RAM you have) under Creative drivers (dynamic caching) and try to switch the patches and play the notes quickly

/Eugene

vmirage · Jun 2, 2003, 02:23 PM

is it not possible to load all the required samples into memory first b4 playing the midi? it's basically not dynamically loading the samples only when needed ... but preload only all the necessary samples b4 playing midi. so even if you don't have enough memory, it won't even load the samples.... i know... it's a bit tedious ... but heck... just wondering...

**Eugene Gavrilov** · Jun 3, 2003, 12:23 AM

I doubt dynamic caching and good latency are compatible terms...
as for playing MIDI files, the driver cannot distinguish between low-latency Cubase requests and latency-tolerant MIDI players...

/Eugene

mercurysquad · Jun 28, 2003, 06:08 PM

This is a sort of "manual" patch caching which I did a lot on creative drivers: is there a way to load only specific presets from a .SF2 file into the soundcard at a specific preset no. and bank? If not thru the built in sf2 loader, then is it possible thru third party soundfont loaders?

Jun 1, 2003, 01:41 PM	#1
vmirage DriverHeaven Newbie Join Date: Dec 2002 Posts: 5 Rep Power: 0	dynamic soundfont caching? is the kxdriver going to implement dynamic soundfont caching in the future? __________________ -- Kelvin Foo

Jun 2, 2003, 02:23 PM	Thread Starter #3
vmirage DriverHeaven Newbie Join Date: Dec 2002 Posts: 5 Rep Power: 0	is it not possible to load all the required samples into memory first b4 playing the midi? it's basically not dynamically loading the samples only when needed ... but preload only all the necessary samples b4 playing midi. so even if you don't have enough memory, it won't even load the samples.... i know... it's a bit tedious ... but heck... just wondering... __________________ -- Kelvin Foo

Jun 28, 2003, 06:08 PM	#5
mercurysquad DriverHeaven Junior Member Join Date: Mar 2003 Location: India Posts: 25 Rep Power: 0	Single instruments? This is a sort of "manual" patch caching which I did a lot on creative drivers: is there a way to load only specific presets from a .SF2 file into the soundcard at a specific preset no. and bank? If not thru the built in sf2 loader, then is it possible thru third party soundfont loaders?

Jun 2, 2003, 11:43 AM	#2
Eugene Gavrilov kX Project Lead Programmer and Coordinator Join Date: Dec 2002 Posts: 3,106 Rep Power: 73	dynamic caching isn't a perfect solution because all SoundFont data should be located in the RAM when needed. if soundfont samples are being swapped to disk it will introduce a very serious lock-up when the corresponding notes are triggered (this will cause ASIO / DirectX / Kernel streaming sync issue) I know that Creative drivers support dynamic caching, however, their SoundFont implementation in the recent releases is completely different and requires additional CPU processing (and, btw, causes some problems with looped samples) btw, try to load a huge soundfont (which is bigger than the amount of RAM you have) under Creative drivers (dynamic caching) and try to switch the patches and play the notes quickly /Eugene

Jun 3, 2003, 12:23 AM	#4
Eugene Gavrilov kX Project Lead Programmer and Coordinator Join Date: Dec 2002 Posts: 3,106 Rep Power: 73	I doubt dynamic caching and good latency are compatible terms... as for playing MIDI files, the driver cannot distinguish between low-latency Cubase requests and latency-tolerant MIDI players... /Eugene