Struggling mightily with sfz

[FoxV]

I'm getting weird pops and outtages in sfz (in T1), and I thought it might be something weird running in the background of XP. That could be; but I'm starting to wonder if something weird is going on with my midi transmission to T1. (Have I used the word "weird" enough?)

Any ideas where I might look?

It even seemed at points that the sfz soundfont changed to another sound and then back again (I'm using sonicsmurfs drum soundfont). Maybe the clicks are programming messages being sent?

I'm grasping at straws!

[audiobot202]

Have you tried it in a sub host like eXT? I've had problems rendering from sfz to a file. The volume suddenly gets very loud and clips. I thyink sfz is known to do this in Tracktion though.

[P.T.]

Sfz is my main Vst sound source in Tracktion(T1) and I never have had these problems.

[mandolarian]

Are you playing back samples from RAM or using the Direct From Disk option? I had similar glitches using RAM mode and switched to DFD, but then there's the latency to anticipate. Pre-cognitive performance is always fun. What will I play 48.7 milliseconds from now?

In DFD mode sfz has been solid in T1, unless I try it realtime in Uber++ mode, then it just caks on my lowly PIII.

If you are getting unintended Program Change messages, filter them out before sfz.

Is this issue only with sfz or does happen with other VSTi samplers or synths?

[Toad]

If you are getting unintended Program Change messages, filter them out before sfz.

Definitely look into that - I had the same problem, especially if I had two or three tracks using different sound fonts with sfz. Also, sfz is a well-known CPU hog, especially on higher quality settings. That could account for your pops and clicks. Do you have plenty of RAM and CPU grunt? Even with 1GB RAM and a 2Ghz CPU there are still times when I have to use another SF player for certain sound fonts. It's just the nature of the beast, I think.

[FoxV]

Do you have plenty of RAM and CPU grunt?

Nope, very little: PIII 550 mHz, 512 MB ram.

...but it was working just fine (it seemed?!?) when I first installed tracktion.

...so I guess I'm hearing that streaming from the harddisk (DFD) causes latency...that explains the latency!

But not the pops and weird changes. I'll use a midi filter.

Thanks for the ideas!!!!

Is this issue only with sfz or does happen with other VSTi samplers or synths?

I'm getting very taxed CPU using other synths and samplers. Seems like my CPU is struggling more now that it was when I first installed tracktion. No weird program changes in any other apps. I'm betting it's not a program change, but just the CPU getting taxed and causing sfz to act up.

[P.T.]

I stream from disk all the time. No latency issues.

[rockstar_not]

DFD doesn't work for me on my lowly Win98SE T1 box. I have to use the PR16 mode - and with that, if I can get the font to load (sometimes it comes back and says not enough memory - hey, I've only got 256 MB) then it works flawlessly. DFD, besides latency, is depending on activity happening on the disk interface, so latency can get 'bad enough' to issue dropouts.

With a mightier PC, DFD is the preferred way to go, but with lowlier PC's like mine, PR16 is the mode that works best.

Don't forget there is an rgcaudio forum here on KVR and Rene checks in often.

-Scott