Yes, that's what this test is about - the ASIO code in the Echo driver. This test bypasses that code. It shows the problem is related to the Echo ASIO code. However that's the same code used by all other ASIO applications and they work and haven't changed, so it's not a general failure. It also worked with earlier versions of MuLab, and the ASIO code hasn't changed. So it does seem to be specific to later versions of MuLab and the unchanged Echo code.mutools wrote:Are you sure about that? Maybe the failure is in the Echo ASIO specific code of the Echo driver. (outside the MME specific code)pljones wrote:2) Swap the application API -- MuLab works with the MME for audio output to the hardware -- that also swaps out the ASIO driver, of course, as they "bound" together.
I'd expect it to work as it doesn't sit on the Echo ASIO driver at all but it would test another part of the Echo code, true (i.e. the DirectAudio or whatever it is). I'd expect it to work even if it ran with the ASIO driver, as most applications still do. Even if ASIO4ALL had an issue, that would not necessarily mean it was related to the problem here - although it might be interesting to confirm whether it acted the same for all its clients. I may try it next weekend.mutools wrote:You could also try Asio4All.3) Swap the ASIO driver -- MuLab works with ASIO out to, e.g. Reaper via ReaRoute, with Reaper's main out to the Echo.
Yes, agreed - it's definitely not a general issue. That does make it more frustratingmutools wrote:And FYI: I did not receive any other similar report wrt M7.4 about failing ASIO functionality.
Ok, that doesn't 'prove' anything, but at least it's relevant statistical info.
.Sorry, yes, I was not meaning to imply otherwise - just summarising the position to that point.mutools wrote:Not only MuLab, the ASIO SDK hostsample doesn't work either. (when also built with VS2015/2017)To me it looks like it's the interaction between the application and the ASIO driver. One side or other isn't "quite right" and - for the specific combination of MuLab and the Echo ASIO drive - this causes a problem.
Yes, 2013 and 2017 -- I don't have 2015 and it had become unavailable.mutools wrote:You also built the ASIO SDK hostsample with VS2013 and it's also not working with the Echo Firewire? (didn't knew that, sorry for double-checking the VS2013 aspect)Note that compiling hostsample with VS2013 or VS2017 produced the same result -- no output -- so it doesn't appear to be compiler version. It could be some (Microsoft-updated) compile or runtime library.
Yes, that was my thinking in starting the thread. I really do see Firewire dying as an option in the near future. The problem is, MIDI seems to be almost an after-thought to most audio developers - zero connectors or a dongle/breakout cable.mutools wrote:And as firewire seems to be dying and as they're not updating drivers anymore, what about switching to another audio interface? Is that an option for you? (pragmatic solution)
(The breakout cables usually take up significant amounts of space compared with that needed for not having such a cable -- that's why they're not an option, for those interested. Things would start falling damaging distances...)
