You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as I try to get rtaudio on windows working, I found that the windows low-latency asio drivers of RTAudio are not included with the files tonic ships, because they need additional cpp files.
I don't know how important that is, because I'm using OSX for Audio.
I'd like therefore to get the complete rtaudio package, maybe in some vendor folder.
Maybe as git-submodule, but this requires an additional git submodules init for the end-user.
RTAudio uses Cmake so it could be easily included as a library. We could maybe also let the RTAudio folder of the examples intact, so that nobody needs to change the Xcode/MSVC Projects there.
The text was updated successfully, but these errors were encountered:
Thanks @andik. I'd like to avoid requiring an additional git submodules init, or packaging compiled binariy files with Tonic. I think including the source files in the Tonic repository is probably my first choice. @ndonald2, what do you think about including a more complete rtaudio inside the Tonic repo so that windows asio people can compile and run Tonic without too much fiddling? Rather than creating a vendor folder, why not just inclucde the extra .cpp files in the rtaudio file? That seems simplest to me.
Hey guys,
as I try to get rtaudio on windows working, I found that the windows low-latency asio drivers of RTAudio are not included with the files tonic ships, because they need additional cpp files.
I don't know how important that is, because I'm using OSX for Audio.
I'd like therefore to get the complete rtaudio package, maybe in some
vendor
folder.Maybe as git-submodule, but this requires an additional
git submodules init
for the end-user.RTAudio uses Cmake so it could be easily included as a library. We could maybe also let the RTAudio folder of the examples intact, so that nobody needs to change the Xcode/MSVC Projects there.
The text was updated successfully, but these errors were encountered: