![]() The issues for Modartt to consider are the difficulty in porting Pianoteq to iOS and maintaining a second codebase there, versus the huge potential market of iOS users, while considering their overall pricing structure. In one of the discussions, it was mentioned that Pianoteq is developed using the JUCE framework, which is mostly C++. There have been several discussions of the desirability of Pianoteq on iOS in the past, here and on the Pianoteq forum. ![]() If the port was even close to PC Pianoteq, I'd buy it in a heartbeat, and it would blow the competition out of the water in App Store. It's too bad they haven't ported it yet, I'd assume iOS market would be multiple times the size of their current market. However, considering quite mathematical background of Pianoteq, it could just be they did the huge modelling work with some hard-to-port-to-ios language, like Haskell, Python with Numpy, or even something more esoteric. Of course the performance might depend on some highly parallel commands on modern x86 processors, in which case even modern ARM instruction set might be lacking. I would assume Pianoteq is mostly coded in C or higher level language, in which case porting to iOS should not be too bad. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |