samplerates and timing

jorge · 28 May 2005

There's a component called "settings" that is suposed to give you the current sample rate as a float output but it doesnt seem to be working, should be easy to fix anyway.

unkargherth · 28 May 2005

AFAIK, grease, only one question should be took into account:

Every time you use the sample rate for anything, Dont' assume nothing. Take the Timing info component and use waht cames form it as SR. Never, let me repeat , NEVER use hard coded values like 44100, 22050 and so on. Get the float output on Timing info component and Multiply of divide to obtain parts or multiples of it

The only situation i've found where you can do this is when initilizing arrays in code module, as they should be initialized with a known value at Link time. The only solution i've found to this is to use the higher value you want to support (maybe 192000) and limit manually inth code depending on a polyinput connected to you code module from the Timing info component

I've heard rumours that timing info component only works for first and second level in schematic depth. Jorge, could you confirm/rebate this ?

jorge · 28 May 2005

unkargherth wrote: Take the Timing info component and use waht cames form it as SR.

oh yeah, I forgot about the TimeInfo component so please ignore my previous post. I didnt try using the TimeInfo inside an exported VST so if it doesnt pick up the correct sample rate please let us know as it would be a bug.

JMH · 28 May 2005

Hi Jorge

The last time I tried TimingInfo, it didn't seem to work in an exported VST (or VSTi to be accurate).

I was supposed to post a question about this a while ago, but reading the forum, I assumed it is working correctly for others as they often referred to using it and that gave me the impression that everybody's actually using it...

So yes, I'd count it as a possible bug. Good to know your attention is on it 🙂

Regards,

JMH

platinumears · 30 May 2005

I guess this is why my Tarrabia filter didn't work as a vst until i replaced the settings module with a fixed 44100.. I tried exporting a vst with nothing but the settings module and a readout, and the display reads 44100 whatever the actual sample rate.

I wondered if there was a problem with the readout however, because even in SM I need to disconnect and reconnect the float module to see the value update (If I open the saved project at 96k it will open up reading 44100 at first) and if it was really kicking out 44100 all the time the results should be the same as when I use a constant..

Dan

unkargherth · 30 May 2005

platinumears wrote: I wondered if there was a problem with the readout however, because even in SM I need to disconnect and reconnect the float module to see the value update (If I open the saved project at 96k it will open up reading 44100 at first) and if it was really kicking out 44100 all the time the results should be the same as when I use a constant..

Dan

AFAIK teh Samplerate it's not saved with schematic. It depends on your io Drivers (timing info return 44.100 if i use DS Out, but 48000 if i Use ASIO Out with my Kx drivers on audigy 2). Also Seetings module has a known bug an sample rate

Wehn you export to VST the Sample Rate depends on Host, so you need to read itfom somewhere. That's what is suposed yoiu do with VST>>Timing Info Module, althought rumours say that it only works on first level in scematic

platinumears · 30 May 2005

unkargherth wrote: . That's what is suposed yoiu do with VST>>Timing Info Module,

Aha!! Thanks for that.. 🙂