asioforall drivers

[larspalo]

Originally posted 2019-10-13 10:47:55.337000 by Paolo Gilardi in GrandOrgue discussion forum on SourceForge

hi,
i have installed asioforall drivers 2.14 english but i canno see them listed in audio & midi settings/output.
WHat am i doing wrong ?

[larspalo]

Originally posted 2019-10-13 11:06:44.046000 by Paolo Gilardi in GrandOrgue discussion forum on SourceForge

btw... i remember in the past it was best to choose windows-wdm or windows-asapi (now i dont remember well) but anyway, asioforall was listed as an option while not today...

[larspalo]

Originally posted 2019-10-16 17:52:05.191000 by Martin Koegler in GrandOrgue discussion forum on SourceForge

GO ASIO builds are gone.

[larspalo]

Originally posted 2019-10-31 21:35:03.065000 by muttiwilson in GrandOrgue discussion forum on SourceForge

I was having an issue using anything other than DirectSound which had terrible latency. I adjusted my soundcard's playback settings under the advanced tab in the control panel for sound to match GO's bitrate settings and then I was able to select the WDM options without errors. My latency is now at 5ms and the sound is working great.

[larspalo]

Originally posted 2021-06-06 06:11:02.904000 by Oleg Samarin in GrandOrgue discussion forum on SourceForge

My GrandOrgue fork build at https://github.com/oleg68/GrandOrgue/releases supports ASIO

[larspalo]

Originally posted 2021-06-07 07:07:07.988000 by csw900 in GrandOrgue discussion forum on SourceForge

GO was right to remove support for ASIO. In all my many years of using keyboards and organs on many different systems I have never found any need or benefit from ASIO.
csw900

[larspalo]

Originally posted 2021-06-07 07:41:19.606000 by ggoode_sa in GrandOrgue discussion forum on SourceForge

The reason ASIO support is not part of the main sourceforge builds is
that it has a different license to the other drivers, which does not
conform to the opensource standards.

ASIO is critical for windows users who want high performance / low
latency when working with other programs. While WASAPI can do just as
well, ASIO is still the sound industry standard for virtual instrument
technology.

GrahamG

On 6/7/21, csw900 <csw900@users.sourceforge.net> wrote:
> GO was right to remove support for ASIO. In all my many years of using
> keyboards and organs on many different systems I have never found any need
> or benefit from ASIO.
> csw900
>
>
>
> ---
>
> asioforall
> drivers
>
>
> ---
>
> Sent from sourceforge.net because you indicated interest in
> <https://sourceforge.net/p/ourorgan/discussion/962124/>
>
>
>
> To unsubscribe from further messages, please visit
> <https://sourceforge.net/auth/subscriptions/>

[larspalo]

Originally posted 2021-06-07 07:38:54.594000 by Oleg Samarin in GrandOrgue discussion forum on SourceForge

> GO was right to remove support for ASIO.

GO did not remove support of ASIO. Instead the ASIO sourcecode was removed from the GO source tree. But GO still supports building with external ASIO sources.

> In all my many years of using keyboards and organs on many different systems I have never found any need or benefit from ASIO.

I don't use windows at all so I cann't agree or disagree you. But I've received a user request to enable ASIO in github builds oleg68/GrandOrgue#8 (comment).

I think existance of choice is allways better than lack of choice.