Audio driver could not be opened

[gorangrooves]

I compiled stand-alone app 3 times, using HISE export, Projucer, and Hise-Exporter. I am using the up-to-date Scriptnode branch.

Regardless of which one I used, neither resulted in an app that plays back the sound. I get the warning upon opening exe file:
"Audio driver could not be opened".

The last time I compiled a standalone app, it had a nice little menu on top where you could specify the driver etc, but that is no longer present. The app used to have a nice window heading, but now it looks like a typical Windows app header.

On top of that, the midi channel list floating tile contains no data.

In my custom settings panel, I have everything to do with the audio driver set to false.

I saw this issue reported in 2018, but it seems to have crept back.

Any solutions to this issue?

[d.healey]

@gorangrooves said in Audio driver could not be opened:

The last time I compiled a standalone app, it had a nice little menu on top where you could specify the driver etc,

That hasn't been there since HISE verion 1.6 or something. You have to add it in the custom settings floating tile to access those settings.

[gorangrooves]

@d-healey I think you misunderstood. @Christoph-Hart removed some of those elements from the floating panel with v2, but they have been available by default in compiled standalone apps. There is supposed to be a little audio settings menu by default (top left, if I remember correctly). It is not there now and the app throws an "audio driver could not be opened" error upon initializing.

@Christoph-Hart Do you know what is going on here?

[d.healey]

@gorangrooves said in Audio driver could not be opened:

but they have been available by default in compiled standalone apps.

Got a screenshot? As far as I know there are no default controls put onto your UI.

[gorangrooves]

I can not provide a screenshot it as I am unable to compile it successfully at the moment. It seems I deleted previous version I had, as it was not the final software version. The controls do not get put over your GUI. They get included in the build-in menu of the app header. Any Windows app has a header and part of the header is where this menu is found (at least it used to be).

[d.healey]

@gorangrooves Ah I see, was this just a Windows thing?

[gorangrooves]

@d-healey I am not sure.

[Lindon]

@d-healey said in Audio driver could not be opened:

@gorangrooves Ah I see, was this just a Windows thing?

theres no audio settings in the top left of any stand alone windows app I ever built...

[gorangrooves]

@Lindon What about Mac? Seems like I'll have to go back and recompile using older versions of HISE to demonstrate. It has definitely been there.

[gorangrooves]

Are you guys compiling the standalone apps with no issues?

[Lindon]

@gorangrooves yes.

[d.healey]

@gorangrooves said in Audio driver could not be opened:

Are you guys compiling the standalone apps with no issues?

Yup, did you get rid of your extra versions of the source code yet?

[Casey Kolb]

@gorangrooves This seems to happen occasionally on Windows. I've experienced it with some of my test users. If they try to open the standalone, it may default to some weird audio device that shouldn't be used and it throws an error and breaks the app until you pick a proper audio device. Windows is pretty bad about this. If you add a Settings floating tile to your interface you can correct it by just changing the Audio Device right from the exported plugin.

[gorangrooves]

@Lunacy-Audio Thanks so much. I'll try that. @d-healey Yes, I deleted all old stuff and recompiled HISE. Let's see if including an audio device in the settings on GUI will fix the issue.

[gorangrooves]

Happy to report that including the driver settings in the GUI panel enabled me to change it after the fact and solve the issue. @Lunacy-Audio Thanks for the tip and everybody else for your time!

[Casey Kolb]

@gorangrooves Nice! Glad to hear it

[d.healey]

@gorangrooves said in Audio driver could not be opened:

including the driver settings in the GUI panel enabled me to change it after the fact and solve the issue.

I told you to do that 3 days ago :p

[hisefilo]

@d-healey Similar issue here!! I need to compile an old project. Need to use Hise 1.5
Original project lacks of CustomSettings panel (Audio driver, Output, sample rate, etc) and I want to add it but... No matter what I do, I always get an "audio-driver-could-not-be-opened" dialog on Standalone compiled instrument

Any clue?

[ustk]

@hisefilo Is it hard to make your old project work with a newer version?
I imagine the differences lie in the XML only so it should be editable

[hisefilo]

@ustk I've used Harmonic Filters on that old project. Cannot get the same sound on 2.0. I don't know why. (at some point Harmonic Filters were updated to monophonic I guess)