At 03:05 AM 4/30/2012, you wrote: >> But should OutputPosition lose resolution like that anyway? > >Well, OutputPosition goes up by frameCount in the internal callback. >So it should go up by some fixed value with every callback.
It's not; it's tied into SuggestedLatency in some way and you can tell this at higher values. I'm pinging it pretty heavily; for example if SuggestedLatency is .2 (200ms), OutputPosiiton only changes every 200ms. I ping it many times within 200ms and OutputPosition gives me the same value. That's why my wavehead cursor looked jumpy, because my app was drawing it in the same position because OutputPosition was giving it the same values until the next 200ms. This means less to me now, since I know now to set SuggestedLatency closer (or equal to) to what PortAudioDeviceInfoMBS.DefaultHighOutputLatencygives me. But I'm saying more for you in case it is a bug. It may not be, perhaps that what SuggestedLatency means by definition. Since not setting SuggestedLatency is now a no-no, I'd update the examples if you haven't already. I like setting it in respect to PortAudioDeviceInfoMBS.DefaultHighOutputLatency, like this: OutputParameters.SampleFormat = paFloat32 DeviceInfo = MyPortAudio.DeviceInfo(MyIndex) OutputParameters.SuggestedLatency = DeviceInfo.DefaultHighOutputLatency // CoreAudio on my computer seems around .01; that is 10ms ErrCode = MyStream.OpenStream(OutputParameters, MySampleRate, paFramesPerBufferUnspecified, paNoFlag) Garth Hjelte Sampler User _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
