-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ASIO: License agreement #822
Comments
@rousseldenis are we readuy to sign the license agreement? |
@oleg68 I have it ready. Waited just for your feedback on this to go forward. |
@rousseldenis May we continue signing the ASIO agreement without creation of the non-profit association and without funding? |
Of course. I wanted to tell the whole options. I will send it from me in the name of 'GrandOrgue' if it's ok for you? @larspalo |
I agree |
Sure, go ahead! |
Does this mean full ASIO support can come into binary builds again? |
This is already the case. |
I am not seeing ASIO in the list of options when I choose sound devices. All the other non ASIO options do show up. Or does the ASIO option not show up with the four letters "ASIO" in the description when the software enumerates the available set of devices + driver modes? Speaking of availlable devices and driver modes having a flat list of [MODE1] x [DEVICE1] through [MODE8]x[DEVICE8] instead of TWO combo boxes, one for device driver type or category and the other for a device within that category is a really serious UI oversight, in my opinion. It's like the model of the underlying audio engine was designed with two tiers of enumerable settings and the results of both are dumped into a single array of very complex strings, which make no sense to human beings. I have extensive experience with DAWs and audio software and have never seen a wonkier representation. For a future revision a change to the ui such that there is:
Would make GrandOrge much like other systems. The other funny thing is that of course setting up the outputs within the device should be automatically creating a stereo pair by default when adding, instead of making people figure out how to do that. I may be able to help with making this as easy to get started with as other audio applications, if help is wanted from someone with Win32 API experience. |
Forget this one. Done |
Received today the countersigned licensing from Steinberg |
If you don't mind, I will send signed from me the ASIO license to Steinberg you can find here (in SDK zip file) https://www.steinberg.net/developers/
Drawback of this, I will be responsible of legal issues towards that (but I think there won't).
In another hand, depending on project evolutions, we can envisage a non-profit association creation that will protect us from those kind of issues, but imply a little bit more constraints (but can help for funding, sponsoring etc...)
The text was updated successfully, but these errors were encountered: