Hi, Reading through the porting docs and I come across this enlightening diagram of the Tizen Audio Stack:
https://wiki.tizen.org/wiki/Porting_Guide#Audio To me it has a glaring hole when compared to this diagram: http://linux-audio.com/images/linux-audio-stack.png Is there a specific reason that JACK is not included in the Tizen audio stack? Is it a global conspiracy against professional open source audio developers or is it just that no one in the dev team cares about professional audio on Tizen so no one has bothered to put any time/effort/funds into it? I am personally willing and able to spend a considerable amount of time/effort on this aspect of the Tizen Audio Stack if there is genuine interest in supporting professional audio requirements at the OS level and not just as a third party add on. It would be a fundamental differentiator when compared to Android/ChromeOS and their Development Team/s lacklustre support of professional audio where it seems after several years of inaction they actively work against professional open source audio developers and also want to reinvent the wheel at every opportunity. They appear to suffer from "not invented here" syndrome when it comes to professional audio. Currently the best that android is able to offer is 20ms latency. That is fine if you are playing the piano at home but if you are monitoring a live stage act or doing realtime audio it's a show stopper. Professional requirements are in the sub 5ms range. The less latency the better. Linux Audio has been able to provide this for over 10 years now as latency is limited only by hardware design so there shouldn't be any reason for it not to be a standard part of any new Linux OS. -- Patrick Shirkey Boost Hardware Ltd _______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
