Herbster, thanks for this detail.

In another post somewhere, I went over the history, and yes, it was SONAR 6 that broke the 1.21 driver and required the making of the 1.22 driver.  Frontier Design wrote that driver, still in beta, but Tascam never released it on their websites.  The 1.21 driver was introduced with SONAR 4 and works with SONAR 4 and 5.

I have written to Frontier Design about a 64-bit version of 1.22.

FYI Tascam includes Cubase LE with their interfaces now. Maybe they have switched product loyalty away from Sonar so therefore have abandoning any development that supports Sonar leaving you guys in a lurch. Just a thought.

Thanks, Still Kicking.  I can't count how many expressions of frustration I have read about not buying Tascam equipment ever again.  Even if they have fixed this problem, a lot of damage has been done.

Forgive me for asking you to clarify your post.  I want to be very clear on this point.  You say you are successfully running the 1.21 SONAR Control Surface driver with Windows 7 64-bit and SONAR 8.5 64-bit, but that 1.21 driver is only 32-bit.  This is what it says on the Tascam USA website for the FW-1884:

FW-1884 Sonar Control Surface Drivers:
Sonar V 1.21 Control Surface driver 32-Bit (download)
 Sonar 64 Bit Installer (download)

And those of us who use 32-bit Windows never knew eactly what that meant, since the names are different.  Does it mean there is one driver, version 1.21, and a separate install for 32-bit and 64-bit?

If so, it would seem that the 64-bit version could not work fully, since we know that the 1.22beta driver is required for SONAR 6 or newer when using 32-bit SONAR installations.

I'm traveling until the weekend so will need to get back to you later on the details.

I had all of this running reasonably well in 64bit under the 1.70 driver, which I installed a month or two ago.  At that time, I ran the Sonar x64 installer.  I'm not sure what else I installed at that time.  The FW1082 plug-in does show up as installed on my system, but when I open the PlugIn configuration tool and select Controller plug-ins, it points to the FW1884.dll that is identified in my e-mail. 

I didn't have time to do much with it, but the transport controls, the select in/out buttons and the track controls for mute, solo, and select seemed to work fine.  Are there specific functions you'd like me to test when I'm back in town?

Act can allso be used to get the remote controller working..... hopefully.

SK,
Thanks for the update!

My issues with record bit depth solved, for what ever reason
my Win7x32 install defaulted to 24bit, but my Win7x64 did not!
It probably goes back to the original chipset install, I might not
have installed the audio drivers for the on-board audio.
I had completely forgotten about  OPTIONS>GLOBAL>AUDIO DATA
having a drop down for record, render, import, etc.

Tom

It's official! We DO have a friend at Tascam.

The v1.22x32 and v1.22x64 Sonar plug-ins are up on the Tascam European site.

Click on FW-1884 under "Updated Windows Drivers for FireWire Interfaces".

I have S8.5.3 PE on an XP System, but formatted and installed all the new drivers and all is working well.

I know a guy with with a 1082 on Win7 that I helped out with the new drivers and his seems in good order as well.

Was happily surprised that we got new versions, now I may get a new Win7 machine.

Just had a chance try out my old fw1884 on a Win7x64 audio recording session with Sonar 8.53.  All I've run is the v1.80 exe driver install. 

The mobo is an Intel 975bx2. Had a bit of trouble getting the 1884 fw port to initialize if I turned it on after Win7 was already booted. Sometimes the fw led would just blink. But if I powered up the unit ahead of time, it would init every time once Win7 came up.

I did all the audio recording through the spidif port using a 128-bit buffer. Rock solid, no dropouts at 44.1 or 88.2. Also did a solid nonstop hour of 44.1 k spidif-send/return recording to a parallel track with a hardware reverb unit.  I routinely test with a 1-sample spike to make sure the parallel track synchs exactly. Entering the offset into Sonar's audio page. I noticed using Asio that the reported automatic checkbox offset wasn't exactly right... the driver reported a latency adjustment of 158 samples but testing indicated a true spidif latency of 154 samples... maybe the difference is the converter latency spidif bypasses.  The fw1884's spidif latency was spectacular, btw, using wdm/ks... measured 26 samples with 2 buffers (128-bit again) and 28-samples with 3 buffers.  I decided to go with wdm/ks using 2-buffers and unchecked the "compensate for converter delays" checkbox in the driver screen since I only use spidif anyway.

Unfortunately, the big fly in the ointment for me was that my Win7 machine would reboot if I turned the fw1884 off after a recording session with Sonar.  Seems to turn on and off fine if I didn't use it with Sonar.  Hope they resolve this because it's a really great performer otherwise.  I did the same latency tests with an RME FF400 which measured a 197 sample latency (asio reported 173 samples). The ff400 (v3.016 drivers) didn't work at all with wdm but 32-bit mme drivers did work with Sonar 8.53 x64 (???) but measured a 2,274 sample latency... not sure why they bothered.

Have not installed the 32-bit Sonar or the fw1884 control surface drivers on this system yet. Will report back when I do.

Howard

Thanks, Tom.  I think it might be the fact that my win7x64 system uses an ssd with trim enabled. Not having any problem with the rme ff400 so I've been using that lately.  I have a new fw interface coming in next week which I'm hoping doesn't have the same issue... I'll report back when I do some more testing.  

Howard

Just took the time to try a few things and they both seem to work. Shutting off trim on the ocz vertex boot ssd worked, as suggested on their site. But so did changing to the legacy version of the TI firewire driver, as suggested by Tom above.  I'd rather not be mucking with trim so I'm sticking with that approach.  The ff400, my Canon HD video camera, and various fw hard drives I use on occasion don't seem to care. Got a new converter coming in next week that I understand also uses a TI fw chipset with Win7 64-bit drivers provided by TC.  I'm optimistic it'll be good too.

Howard

Know this is an old thread, but I'll have a go anyway:

Have some of you replaced the FW ports on the FW-1884?
Seems that this is happening to a lot of the Tascams (mostly due to the possibility to force a FW cable the wrong way into it? ) and therefore it has to be changed.

I have an offer for an FW-1884 with a broken FW port for 100$.
If its possible to change the FW ports for not much money, this must be a bargain?

If not - is it possible to only use it as a DAW controller via MIDI?