Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[madbrain]

I am experiencing an issue with my ECHO Audiofire 12, a Firewire audio interface.

Ever since I upgraded to MC 23 64-bit, there is no sound at all when using the ECHO Firewire ASIO device. If I use DirectSound or WASAPI, there is soon.
If I switch to 32-bit MC 23, it works in ASIO mode. All device settings are the same in both cases (channel offset 0).

I have other 64-bit apps that work properly with this card, namely Reaper 64-bit for both recording and playback.

I know this is an old card for which drivers are no longer updated, but I am wondering if any diagnosis could be made and a possible fix, as it seems this is an issue specific to MediaCenter 64-bit.

One thing that complicates the debugging matter is that it's not possible to run the both 32-bit version and 64-bit versions of MC side by side on the same machine. The 64-bit installer deletes the 32-bit version, and vice-versa. Is there any way workaround to keep both versions ?

I have a fairly large collection, so would much prefer to use the 64-bit code if possible.

[Hendrik]

Its possible the 64-bit driver of your device just doesn't function properly, in which case there is nothing we can do about that.

[madbrain]

Hendrik,

Its possible the 64-bit driver of your device just doesn't function properly, in which case there is nothing we can do about that.

Sure, it's possible, but since the 64-bit driver for my device functions with another 64-bit application, is it also possible that there might be something wrong with Media center as well.
Just to clarify Reaper x64 works in ASIO mode in 64-bit mode with my device.

Here is a Media Center log that might help shed some light on the issue, I hope.

[madbrain]

Here is an additional log from the 32-bit version of Media Center (working version).

[Hendrik]

The log doesn't show any issues. The audio device is opened properly and playback appears to commence.
I would suggest to validate the settings of the ASIO device itself, if volume is actually turned up, and things like that. I don't see anything wrong on this side.

[madbrain]

The log doesn't show any issues. The audio device is opened properly and playback appears to commence.
I would suggest to validate the settings of the ASIO device itself, if volume is actually turned up, and things like that. I don't see anything wrong on this side.

Thanks for looking into it. I already checked in the ECHO Firewire mixer consoler, and there was no playback signal going out, even though the levels were set at the max.

Is there anything else that can be done ? Like logging all the specific ASIO API calls to see if there is any difference between the two cases ?
Ideally, there would be a way to do this with my other Asio 64-bit apps that are working too. Maybe some kind of ASIO passthrough driver that would just log calls to the real driver. I think there are a few open-source ASIO drivers that could probably be hacked to do this instead of their current purpose (ASIO proxy, foo_dsd_asio), but haven't looked at the source, and I don't have to look at this myself. Such a logging driver might be useful to debug ASIO device issues in various applications in general, if it existed.

[trajanmcgill]

I guess you could try installing ASIO4ALL, which can create an ASIO interface to the built-in sound card that I assume you probably have in addition to the firewire one, then you could experiment to see if JRiver MC has trouble with all ASIO cards or just your ECHO interface.

I use ASIO myself with my Komplete Audio 6, and I know I have with MC 22, 23, and 24, but I don't think I started using a 64-bit build until version 24, so I am not sure about the version you have.

[Awesome Donkey]

AISO4ALL is just a wrapper for kernel streaming, which I'd not recommend using.

[trajanmcgill]

AISO4ALL is just a wrapper for kernel streaming, which I'd not recommend using.

I'm not recommending it for actual listening use, only for investigating the apparent problem with being able to play to an ASIO driver.

[madbrain]

Hendrik,

The log doesn't show any issues. The audio device is opened properly and playback appears to commence.
I would suggest to validate the settings of the ASIO device itself, if volume is actually turned up, and things like that. I don't see anything wrong on this side.

Yes, the volume is turned up . There is a software console from ECHO which shows this.

I hear some clicks when I start playback in MC, as if the DAC is being setup. But then, no audio.

If I reinstall the 32-bit version of MC 23, it works fine in ASIO mode.

Reaper works fine with the same card in ASIO mode, both x86 and x64 versions of it.

[madbrain]

I'm not recommending it for actual listening use, only for investigating the apparent problem with being able to play to an ASIO driver.

I also have a Korg USB DSD DAC with an ASIO driver. MC23 plays fine on it, both 32-bit and 64-bit versions.

[madbrain]

I also have a Korg USB DSD DAC with an ASIO driver. MC23 plays fine on it, both 32-bit and 64-bit versions.

Also, just checked with the free version of Hauptwerk, which is 64-bit only, and it works fine with my ECHO Audiofire 12 also in ASIO mode.

This interface works with every ASIO app I have tried, except MC23 64-bit . Something strange is going on with this combination. I have no idea what it is. But I would appreciate some further help, since I can only point to an app problem at this point. I know that the manufacturer no longer supports the interface/drivers as it is EOL, but it is strange that it works everywhere but MC 64-bit.

I would gladly upgrade to MC24 / 25 if this problem could be resolved.