- This topic has 6 replies, 4 voices, and was last updated 1 year, 11 months ago by
.
-
Posts
-
subj: Breakaway One 3.30.93, Win10 x64, ESI Juli@, Wave-interface: Unable to open device
Clean installation of Windows 10 x64. Breakaway, AIMP-player and, of course, all drivers are installed. No updates were installed on Win10 (this is the next step). In the BO1 configurator, the following is selected:
Basic FM Cores Input (all outputs ‘Disabled’)Audio Input Settings:
Interface: Wave
Juli@ Ch12 (Juli@ Audio) <- physical input
Clock Master: not selected
Adaptive Sample Rate Conversation: selected by default
Channel 2 (I have tried other channels and no effect)
Sample Rate: 48000When I click on ‘Auto-configure Block Size’ BO1 answer me ‘Unable to open device’
So cute…Then I (with the same settings) select the audio card built into the motherboard, press ‘Auto Block Size’ and… yes, the same thing, ‘Unable to open device’.
I choose Juli@ again, but the interface ‘Kernel Streaming’ and – bingo! – interface is working.But in this case, MPX-output will not work, since the internal clock of Juli@ will be set either to 48000Hz (MPX-output does not work) or to 192000Hz (input does not work).
The only way: input as Kernel Streaming, MPX-output as Wave Output. But is a wrong way.In the old versions (BBP ASIO), you may select a sampling frequency of 192000Hz for both input and output, and everything worked amazingly. For what reason it is NOW possible to select only 41000/48000 for input i-face and why the interface ‘Wave’ does not work completely – it is impossible to understand.
-=-
Thank you for reading. 🙂I don;t have an instant answer, but I am also certain that the changes that were released in 3.30.93 were only relatively minor, to address long-standing requests. I very much doubt that the core processes were touched at all. I will try to source a Juli card to see if I can replicate your situation. Meanwhile, what happens if you roll back to the previous, working version?
Hi Karl!
First, are you using the latest drivers from Juli@? I’m attaching it below in case it isn’t. I’ve had similar problems and they were driver related.
Also check that the samplerate in the control panel if is not below 48 kHz. I think it’s interesting to keep it at 192 kHz since the BA1 can run the conversion by its own.
If Windows is using Juli@ in exclusive mode can also cause this issue. In the audio control panel, try disabling Juli@’s audio inputs and outputs (also digital IN-OUTs), as Kernel Streaming does not depend on these WASAPI settings.
I’m not sure, but there is a patchbay (DirectWire) at Juli@ driver and it may have an influence on how it understands interface inputs and outputs. As I recall, it manages the MME, which I believe is the same thing as Kernel Streaming.
By the way: have you ever tried to use Juli@ through the ASIO driver? I think it will be even more efficient and has lower latencies.
ESI Juli@ latest drivers (also compatible with Windows 11)
https://download.esi-audiotechnik.com/download/ESI/Juli@/Juli@-x2v-v1_51.zipMME is not Kernal Streaming, to my understanding. It is a separate … API (??). Not sure what to call these.
Both MME and WDM are kernel streaming.
MME is older (from Windows 3.1) and WDM newer (from Windows 98).
In my point of view, if another API (MME) requires a streaming adress, it could restrict the access to other API allocates (as WDM, for example). All Windows audio runs through kernel drivers, only ASIO bypasses it.
At least that’s how I understood Windows audio management…
Ah, so if I see “KS” in a software, I can assume it’s supposed to be “WDM” if said software also has a separate “MME” setting?
Or is this a semantics thing where it’s all technically streaming through the kernel even if it’s not the “KS” API? I was under the impression WASAPI did not use KS, but my understanding of this whole audio API situation in Windows is muddy as heck.
edit: sorry to derail
In Juli@ control panel theres MME and WDM options, separate. This is what I was talking about.
I understand BA1’s KS is WDM, but MME is KS too, and as far I know, evetytime ‘someone locks the WC door’, its no possible to enter before it is opened again.
I guess even WASAPI runs through a ‘different kernel streaming’ way. I need to learn more about it.
As you said, its a little bit of semantics too and Windows is some kind of hell living inside electronic devices.
I like this kind of thread. I’m trying to remember things I learned 10-15 years before. That’s great!
- You must be logged in to reply to this topic.