Re: [Finale] F25: First run, first crash [another Bailey reply]
I just opened up Sonar Platinum and for the protocol choices in the audio devices there are two options for WASAPI -- one is "Exclusive" and the other is "Shared." I know that WASAPI can be run either way -- I wonder why neither Finale nor Notion give us the option to use it exclusively or shared? Sonar Platinum works fine with WASAPI in either mode, so it's not WASAPI on my computer that's the problem -- it's the notation software that doesn't know how to interact with it that's the problem apparently. -- * David H. Bailey dhbaile...@comcast.net http://www.davidbaileymusicstudio.com ___ Finale mailing list Finale@shsu.edu https://lists.shsu.edu/mailman/listinfo/finale To unsubscribe from finale send a message to: finale-unsubscr...@shsu.edu
Re: [Finale] F25: First run, first crash
Hi Dennis, The ASIO (for Saffire) should work just fine with Finale25. It's odd that two random computers with different soundcards but both with WASAPI listed as audio output possibilities should have problems using it in Fin25. I just checked with Finale2014.5 and the same problem exists although I didn't need to restart Fin2014.5 in order to get a different protocol (ASIO) to work properly. Yes it is an odd situation, and I just did a web-search for "Finale 25 and WASAPI" and it seems as if many people are using it just fine. Maybe I'll reboot my system and see if anything changes. In the meantime Fin25 runs just fine with my ASIO driver from Creative for my soundcard so if nothing changes with WASAPI I'll just stick to the ASIO driver. I don't notice any difference between the ASIO output and the DirectSound output - they both work equally well for my machine. I just opened Notion6 and tried to switch to WASAPI as the audio output driver. When I selected it in the preferences in Notion6, I was presented with a list of possible physical output devices, including my Soundblaster ZxR speakers but when I selected them as my output device, WASAPI responded that "Speakers (Soundblaster ZxR) could not be opened" and the program reverted to the previous audio device. Interestingly, when I select ASIO, it works just fine, the same way Finale does. That makes me think that WASAPI may not be the great audio protocol many people say it is. I did typical installs of Windows10 on this computer and installed everything that came with my sound card, so I have no clue what might not be working properly. But since my ASIO driver works fine as does DirectSound, I'm not worried. Good luck! David On 7/13/2017 4:17 PM, Dennis Bathory-Kitsz wrote: > David, thanks very much. > > On Thu, July 13, 2017 3:32 pm, David H. Bailey wrote: >> WASAPI is an audio output protocol. Most computers have several >> different ones installed -- my Win10 machine has WASAPI as well as >> WindowsDirectSound. As long as there's one or another (like ASIO4ALL) >> that Finale25 will be able to interact with you'll be fine. > > I have four protocols. ASIO (for Saffire) is what I generally use. > >> Finale25 doesn't like my WASAPI either -- you can get around it though >> by starting Finale25 without WASAPI and then going to the MIDI/Audio >> menu and selecting Device Setup and then Audio Setup. In the dialog >> that pops up if you click the down-triangle at the right of the entry >> for Audio Driver you will see the list (including WASAPI possibly) of >> possible entries. Mine show DirectSound and ASIO as well as WASAPI. >> Selecting WASAPI on my machine gets the same error message you saw on >> your machine. > > Okay. I will try this. I just didn't want it disabling a core component for > other software. > > So does this mean that Finale's crash is only related to its own (non-)use of > WASAPI? I ran another dozen pieces of audio software, and none are using > WASAPI. In fact, only one (Audacity) even has it as an option. > >> For some reason Fin25 just doesn't like WASAPI -- so don't let it use >> it. > > Odd situation, it seems, since this is the latest Microsoft protocol and has > the best reviews among pro audio folks. > > Thanks again, > D > > > ___ > Finale mailing list > Finale@shsu.edu > https://lists.shsu.edu/mailman/listinfo/finale > > To unsubscribe from finale send a message to: > finale-unsubscr...@shsu.edu > > -- * David H. Bailey dhbaile...@comcast.net http://www.davidbaileymusicstudio.com ___ Finale mailing list Finale@shsu.edu https://lists.shsu.edu/mailman/listinfo/finale To unsubscribe from finale send a message to: finale-unsubscr...@shsu.edu
Re: [Finale] F25: First run, first crash
David, thanks very much. On Thu, July 13, 2017 3:32 pm, David H. Bailey wrote: > WASAPI is an audio output protocol. Most computers have several > different ones installed -- my Win10 machine has WASAPI as well as > WindowsDirectSound. As long as there's one or another (like ASIO4ALL) > that Finale25 will be able to interact with you'll be fine. I have four protocols. ASIO (for Saffire) is what I generally use. > Finale25 doesn't like my WASAPI either -- you can get around it though > by starting Finale25 without WASAPI and then going to the MIDI/Audio > menu and selecting Device Setup and then Audio Setup. In the dialog > that pops up if you click the down-triangle at the right of the entry > for Audio Driver you will see the list (including WASAPI possibly) of > possible entries. Mine show DirectSound and ASIO as well as WASAPI. > Selecting WASAPI on my machine gets the same error message you saw on > your machine. Okay. I will try this. I just didn't want it disabling a core component for other software. So does this mean that Finale's crash is only related to its own (non-)use of WASAPI? I ran another dozen pieces of audio software, and none are using WASAPI. In fact, only one (Audacity) even has it as an option. > For some reason Fin25 just doesn't like WASAPI -- so don't let it use > it. Odd situation, it seems, since this is the latest Microsoft protocol and has the best reviews among pro audio folks. Thanks again, D ___ Finale mailing list Finale@shsu.edu https://lists.shsu.edu/mailman/listinfo/finale To unsubscribe from finale send a message to: finale-unsubscr...@shsu.edu
Re: [Finale] F25: First run, first crash
On 7/13/2017 1:09 PM, Dennis Bathory-Kitsz wrote: > Hi all, > > I ran Finale 25 for the first time today, Windows 10 64-bit pro, and got this > message immediately: > > "The WASAPI audio device type has caused a crash while attempting to > initialize. Do you want to: > - Quit without disabling this device type, or > - Disable this device type and quit Finale? > Disabling the device type will prevent WASAPI devices from being initialized > when Finale is started." > > Anybody know what this means? I quit Finale. I don't want Finale messing with > my system. > [snip] I finally bit the bullet and bought the upgrade once they lowered the price to $95 for those few days earlier this month. WASAPI is an audio output protocol. Most computers have several different ones installed -- my Win10 machine has WASAPI as well as WindowsDirectSound. As long as there's one or another (like ASIO4ALL) that Finale25 will be able to interact with you'll be fine. Finale25 doesn't like my WASAPI either -- you can get around it though by starting Finale25 without WASAPI and then going to the MIDI/Audio menu and selecting Device Setup and then Audio Setup. In the dialog that pops up if you click the down-triangle at the right of the entry for Audio Driver you will see the list (including WASAPI possibly) of possible entries. Mine show DirectSound and ASIO as well as WASAPI. Selecting WASAPI on my machine gets the same error message you saw on your machine. I just tested things with WASAPI and got an error message. Then I tried both of the others, without first quitting Finale, and nothing played back. Then I restarted Fin25 and selected DirectSound and playback was fine. Then without restarting Fin25 I changed to the ASIO device and playback was still fine. For some reason Fin25 just doesn't like WASAPI -- so don't let it use it. I don't think it will remove it from your computer or disable it, Fin25 simply won't try to load it in the future. But if Fin25 disables it so it shows as disabled in Device Manager, it's a simple matter to re-enable it. -- * David H. Bailey dhbaile...@comcast.net http://www.davidbaileymusicstudio.com ___ Finale mailing list Finale@shsu.edu https://lists.shsu.edu/mailman/listinfo/finale To unsubscribe from finale send a message to: finale-unsubscr...@shsu.edu
[Finale] F25: First run, first crash
Hi all, I ran Finale 25 for the first time today, Windows 10 64-bit pro, and got this message immediately: "The WASAPI audio device type has caused a crash while attempting to initialize. Do you want to: - Quit without disabling this device type, or - Disable this device type and quit Finale? Disabling the device type will prevent WASAPI devices from being initialized when Finale is started." Anybody know what this means? I quit Finale. I don't want Finale messing with my system. Thanks, Dennis ___ Finale mailing list Finale@shsu.edu https://lists.shsu.edu/mailman/listinfo/finale To unsubscribe from finale send a message to: finale-unsubscr...@shsu.edu
