|
|
Screenshot 2024-07-26 090350.png (84,321 bytes) |
|
|
Some "modern" onboard soundcards can only do 48kHz. Have you tried that? I'm also surprised that there is an ASIO driver for that card. For some ASIO drivers that have a dedicated control-app the settings must match the ones configured there. Try "Device Control Panel" Other than that, try Driver: MME (windows default). or https://asio4all.org/ |
|
|
I'm using Steinberg WaveLab Pro and Steinberg's ASIO driver works just fine, But when I used Ardor, the Steinberg ASIO driver crashed! |
|
|
Does "Buffered I/O" help? |
|
|
No. I think the problem is with your program. It fails even with Windows WASAPI driver! |
|
|
@Phantom - Please try the 48kHz option. Also on my system, Windows was taking over the device and not allowing it to be used by Ardour. If the 48kHz suggestion does not work, In the Sound Control panel, you can try disabling the soundcard for the windows system (See attached picture) . This will hopefully allow Ardour control of the sound card. @x42. I will have to slightly agree with Phantom and say that Ardour/Mixbus is the least user-friendly DAW for sound-card setup in Windows. Other DAW's do not need intervention to work on Windows. I had to put a little time and effort into making Ardour work well with Windows. As for the cause of what is making Ardour behave this way, I have no Idea . Maybe PortAudio is not requesting proper usage for the soundcard in windows ? BitWig, Cubase, and ProTools have not needed any special attention, and work right after install. Ardour Linux works fantastic! image.png (15,977 bytes) |
|
|
@Schmitty2005 I did everything you said, it has no effect! |
|
|
@Phantom, did you disable both the playback and record devices ? Sorry, I did not mention disabling the record devices in my previous post. If you did disable both playback and record devices in Windows, another setting you can try is the "Allow applications to take Exclusive Control" option. Check or Uncheck it and give that a try and see if that works. Just make sure to set that back to what it was if it does not work. As far as the MME Drivers not working , a suggestion would be to make sure your bit-depth is correct. I don't know the proper setting for your system, if it should be 16 or 24 bit. The Sample rate also has to match in Ardour as well for the MME drivers to work. I do know that certain ASIO drivers from other manufactures can also be a little glitchy. The Windows Generic ASIO driver is absolutely horrible on my system. Constant Crashes no matter what DAW is used. ASIO4ALL may work for you, but you may get a little bit higher than desirable latency. My system can run at about 5-10ms latency, but with ASIO4ALL, the latency gets worse, about 50-60ms. https://asio4all.org Just curious, what shows up when you select 'Device Control Panel' on the Ardour Setup ? What kind of audio work are you planning to do with Ardour ? Recording Live Instruments ? Using VST Instruments ? Do you only have the onboard audio to work with ? image-2.png (20,237 bytes) image-3.png (18,418 bytes) |
|
|
Only MME works, but when I select Steinberg ASIO driver, Ardour crashes. Empty template. Screenshot 2024-07-27 100035.png (53,073 bytes) |
|
|
Even my Multi-Channel ASIO Renderer (DirectShow) works great on MPC-HC and PotPlayer, but not Ardour! |
|
|
Even thought I would think Ardour should be working with these settings, could you please change your default format that is currently set to 32bit 192kHz to a 16 or 24 bit with 48kHz and give that a try. Possibly with the the RealTek ASIO and not the Steinberg ASIO? I may have had the Steinberg ASIO drivers on my system as well, and I do not recall them ever working properly, or if they did, it was only with Steinberg software. @x42 this is the same kind of issue I was having when trying to setup my Windows system as well. PortAudio may not be functioning as well as it could on Windows machines. It was a bugger and I had to try semi-random settings until I got it to work. Once it was setup, it was fine. |
|
|
It didn't make any difference!: In my opinion, a program that has such a terrible problem and is well made only for Linux, it is better to change Port Audio to Core Audio. |
|
|
Sorry that none of these suggestions helped. It would be nice to see Ardour work as well on Windows as it does on Linux. They do not have a developer that specializes in Windows systems. Ardour is potentially one of the best DAW's available, but these little caveats in Windows prevent me from being able to switch to Mixbus / Ardour. Also, many VST's and VSTi's that I own and like are only available in Win / Mac format. |
|
|
@Schmitty2005 Thank you very much for your complete guidance. I am waiting for the next update of this good DAW. |
|
|
It is a bit of mystery. So far we've not come across an issue like this. And with Mixbus (Ardour derivative) there are tens of thousands of Users for whom it works with a wide variety of devices. @Schmitty we only use Portaudio as indirection to ASIO (for licensing reasons), but generally speaking it's a direct ASIO API under the hood. @Phantom does it work with other audio interfaces? |
|
|
@x42 MME: Apple Type-C to Headphones Jack: Yes. |
|
|
@x42 Ok. So PortAudio is used as the ASIO API. Just curious, if PortAudio is not doing the scanning of the sound cards, what is? Is that a custom Ardour windows only routine ? I was assuming PortAudio did all the device scanning and requesting, as it is only used on Ardour Windows that I know of. There is a grey dialog box with a blue progress bar that scans all of the Audio Devices. I have seen other users have issues with Windows sound cards not setting up properly, but they do get them to work eventually, although not as seamless as it is with other DAW's. |
- Anonymous
