DM3200 with firewire card and no cable error

[Ronan McGuinness]

I have a tascam DM3200 with a firewire and an adat card installed and connecting Mac Pro. since the mac only has thunderbolt and the DM has firewire i am converting through a OWC thunderbolt 2 dock.

I have follow a couple of videos on youtube but the DM 3200 firewire card still says no cable.

I am trying to connect it to Logic.

Any help greatly appricated.

 

[Gerk]

Make sure that you've connected both firewire and USB from the Dm3200 to the computer and that you have loaded the latest drivers (look for the thread here and find the post that has the page location username and password, not just the direct download as you want the latest driver).

Also what OS version are you using? If it's El Capitan then the driver is not working under that OS yet.

I will likely also be trying an OWC2 dock in the near future with mine so I'm hoping it's not the dock! I don't suspect that it is because my setup works fine with a standard Apple thunderbolt to Firewire adapter.

 

[Ronan McGuinness]

yes it is El Capitan which the latest updates. it appears today that my mbox3 is not working either and has disappeared from my sound options which had been working for a couple of years fine. would you recommend downgrading (if that is possible without reinstalling?).

 

[Gerk]

You can't downgrade without doing a reinstall, but I do recommend that you go back to 10.10.5. ALmost no audio manufacturers have approved El Capitan yet .. there are some big issues for pro audio users with it.

 

[AudioWave]

it appears today that my mbox3 is not working either and has disappeared from my sound options which had been working for a couple of years fine.

Note that native Firewire support from Apple appears to now have been finally depreciated ( i.e - Removed) in El Capitan just as Apple announced they were going to do well over a year ago before Yosemite was released. If you have a Firewire device that does not have or that never had it's own specific Firewire driver that was required to be installed, that device may not work any longer.

It is possible that if you had the native Firewire driver already installed and updated to El Capitan from Mavericks and maybe updated to El Capitan from Yosemite that it could still work, but it would be expected that installing a native Firewire device directly to a virgin Mac with El Capitan would result in it not working or no longer being recognized.

Many audio interface makers may have not yet said publicly to avoid fierce backlash, but it is very unlikely that the makers of such native Firewire devices will spend the time and effort and resources to develop new specific Firewire drivers for what Apple considers a dying and dead protocol.

 

[RedBus]

Apple did _not_ remove any Firewire audio support in any way in El Capitan, I've verified that directly.

 

[Gerk]

@RedBus: Is there any chance in the near future that you'll have time to look at the DM-3200/4800 FW drivers for us with El Capitan?

It's very odd about the whole FW is deprecated or not deprecated thing ... Apple definitely changed something up last minute (not a surprise, it happens quite often) but companies like Apogee throwing a big fit and pulling support on their FW products were a bit of a shocker. I notice that they have taken down their original statement about Apple no longer supporting FW and now they are just stating that their FW products are EOL and not going to be supported any longer and they are offering upgrade incentives to their customers still using FW devices ...

 

[RedBus]

There have been no complaints about the V1.30f10 beta not running on El Capitan, so that's the state of that... I'm not aware of any tweaks that need to be made.
I still have some minor control panel work to do to officially support Windows 10, and (throwing them under the bus) our QA department won't look at the Mac driver until they have the Windows driver to test at the same time.

Ignore what Apogee may or may not have said. At the end of the day, for whatever reason they wanted to discontinue an older product that should otherwise be viable on El Capitan.
Apple has confirmed that this is not triggered by any API changes in the new OS.

 

[Gerk]

ok interesting. Thanks RedBus. I think the results have been mixed according to the people on the El Capitan thread on here ... but I have no idea what they have been testing. It seems like there has been some difference on upgrade installs vs clean installs, but again I don't know what everyone has done in terms of testing ...

I haven't made the jump yet because UAD is not yet calling it a supported environment (and honestly my 10.10 setup is running fine so I don't want to jump ship yet).