Page 1 of 2

Bass error handle

Posted: 10 Jan 2023 19:01
by jbmusic
Dear all,

i am preparing a new instance of proppfrexx. In the past i used a Orban Optimod 1101 for processing my sound.
I setup a output device Wave out 2 and processed my sound and with the input on wave in 2 i got the signal back so i could stream the processed signal.
So far so could. In the old situation this worked fine... but i am now re-installing everything and when i would like to add the input stream, he gives the error:
The INPUT stream could not be started!
Mixer in 1: Wave in 2 (orban optimod 1101) [Master Volume] WDM 48000 Hz (-> Rout)
Error: BASS_ERROR_HANDLE

for me it's strange because it worked in the past...

the out signal is working and is also processed in the optimod but signal return via the input is giving the error


Details hardware
Windows server 2022
Orban optimod 3.4.2.15
PF: Professional

Re: Bass error handle

Posted: 10 Jan 2023 19:26
by radio42
Please try the WASAPI driver model for all output and input mixer channels, as the WDM drivers are only there for backward compatibility to support older OS versions.
Since Windows 7 WASAPI is the new driver model for Windows.

And make sure, the input device isn’t already used with any other input mixer channel.

Re: Bass error handle

Posted: 10 Jan 2023 21:39
by jbmusic
Hi Bernd, thanks for the prompt reply.
When i use the WASAPI i get the following error:

WASAPI could not be initialized!
Error: Bass_OK

---
Init input Failed!
Wasapi could not be initilized
Mixer: in 1: Wave in 1 (orban optimod 1101) Wasapi
error 5003

i am not sure what is happening..

Re: Bass error handle

Posted: 10 Jan 2023 21:56
by radio42
Is the input device listed in the Windows sound control resp. already used by another app in exclusive mode?
As only this could explain such behavior.

If you still have issues and no other application is using any sound device, pls send a screenshot of your IO configuration from the general settings.

Re: Bass error handle

Posted: 11 Jan 2023 18:51
by jbmusic
ImageHi Bernd,

thanks for you rreply.
I have checked over and over but nope. I even re-install the drivers and all seems to be okay.
The issue is only on input to route back the processed signal from the orban 2 the streaming encoder.

as requested herewith the images of the settings
settings.gif
settings 3.gif
settings 2.gif

Re: Bass error handle

Posted: 11 Jan 2023 19:21
by radio42
Please try the WASAPI driver model instead of WDM.
And do this for ALL output and input mixer channels.
After you changed all. Please close and restart ProppFrexx.

Re: Bass error handle

Posted: 12 Jan 2023 16:40
by jbmusic
Hi Bernd,

i Did the "change" without succes
Untitled.jpg

Re: Bass error handle

Posted: 12 Jan 2023 19:45
by radio42
We made a TeamViewer session… but couldn’t find the reason. The recording device gave an ‚access denied‘ error. So it must be assumed, that the Orban card raises such issue- it could be a config, license or any other reason?
This needs to be clarified with Orban actually/unfortunately.

Re: Bass error handle

Posted: 12 Jan 2023 23:21
by jbmusic
Hi Bernd

Again thanks for your support from today.
I am pleased that we choose proppfrexx because today you once showed us what service is, even that we have to conclude that the issue is not in Proppfrexx! Compliment for that!

I have send out a message to orban to see if they can help me out on this topic …

I keep you posted

Re: Bass error handle

Posted: 13 Jan 2023 21:13
by jbmusic
Hi Bernd,

i had contact today with Orban. The responsible in the netherlands is taking action on this issue.
meanwile i have tried several other things and guess what, i had a "last hope' for 1 option..
In general the line in (mic) is switched on, but....

In the newer versions of Microsoft OS you have to grant MIC acces to apps (a privacy thing)... So, dont folow only the message: Microphone access for this device is turned on
The solution is to set the "switch" on for acces the apps as well.. this fixs the issue for the Line in
solution.jpg
So this means that the issue is solved and can be closed.
Once again thanks for your support.