>Here there is no requirement for low latency or synchronous execution. >The requirement is just that the app is told exactly how long it will be >between the next samples written to the driver, and >the sound actually coming out of the speakers.
there's another very important i forgot here. because JACK provides inter-app data routing, there is no way to ask questions like "how long till this sound comes of out the speakers?" because "this sound" may not be delivered to the speakers at all! ports can be connected quite arbitrarily, and an application may have no idea where and how its data is going to. this is part of what i mean about people's resistance to this kind of API - you're used to thinking of writing audio code that expects that the data is being delivered to an audio interface. in JACK (actually, in ALSA too), you cannot make this assumption. it may be delivered to another JACK client that just meters it and then throws it away. --p _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
