On Jan 18, 2012, at 10:54 AM, Alistair MacDonald wrote: > Joe B. - any chance I could get you to chime in on the following comment from Steve? (I feel your experience would be very useful here.) > > I'm still inclined to think that even in production/synthesis software it's best to hide this kind of thing away from the user and leave it to the underlying API and/or developer to manage. Something like firing an event to indicate when buffers are running low, or that an under-run has occurred, thus allowing the developer to adjust buffers accordingly in response. (Please forgive me if this kind of functionality is already in the spec - it's been a while since I've read it through and unfortunately right now don't have time to re-read.) > > In my experience, professional music production software has always offered the user buffer size controls, without exception. But I defer to Joe B. I think I agree with Steve that it's unlikely that a visualizer would offer the user this degree of control -- that sort of thing seems more relevant to UC 3 (which directly concerns audio production tool apps). ... . . . Joe Joe Berkovitz President Noteflight LLC 84 Hamilton St, Cambridge, MA 02139 phone: +1 978 314 6271 www.noteflight.com
Received on Wednesday, 18 January 2012 16:12:50 UTC