ORIGINAL: 6string7

Hi Gamergirl

I went through this whole scenerio with my Tascam 1884. I have dealt with Tascam support, searched their newsgroups
and ran my own tests. They play dumb and claim they don't have any issues with their 64 bit drivers when I contact them
on the phone. They won't reply to my emails.

Anyway, I built a new system and have 2 harddrives for the OS's. One is a dual boot with XP32 and XP64. The other is
a dual boot with Vista32 Ultimate and Vista64 Ultimate.
Here's what I found: The distortion occurs in XP64 when over 4 GB of ram is installed and distorts in Vista64 when over
2 GB of Ram is installed. The 32 bit versions work fine when any amount of ram is installed on the machine but of course
the OS only sees 3.2 GB.

I found threads on their forum with people dealing with the same issue and no one from Tascam support responds to them
even though Tascam charges $4.00 to register on the forum.

I also tested the 1.5 and 1.6 driver on XP64. Same results with both drivers. I did complete (clean) uninstalls according to Tascam's instructions.

The bottom line is that Tascam is turning a deaf ear to this. They know they have a problem but don't appear to have any intention of correcting it in the near future. Could be that Frontier Designs is the hold up.

My solution was to order an RME fire face 400. I got it today and it installed on all 4 OS's in record time. Not one issue. NO DISTORTION!! Seems more transparent than the Tascam. Should be according to the specs.

I loved the features on the Tascam for the price but I too want to push the 64 bit platform and now I'm trying to decide if I'm going to keep the Tascam for a controller or sell it to pay for the RME.
Very frustrating, but believe me, you're fighting a losing battle trying to get the Tascam to work (with audio) on x64.

The new MOTU 828 Mark3 looks very interesting but I didn't have the patience to wait and try it out. I'm told that the MOTU drivers are good also.

Good luck!

I feel your pain! I have an M-Audio Delta, and it too doesn't work (as far as audio) with >4GB on XP x64. So I got a MOTU 8pre, and it had the same problem at first, but thankfully MOTU has a beta driver that fixes the issue.

Wow, I can't believe Tascam charges to register on their forum!

Glad you got the RME FireFace, they are top-notch.

ORIGINAL: JoeBertin

Has anyone had a problem with Cakewalk vst plugins with WindowsXP 64 bit? I can't access
fxdelay, fxchorus and a few others.

There is presently no 64 bit Dxi plugin support in Sonar - VST only.

Wow, I can't believe Tascam charges to register on their forum!

I love my Tascam product, but that forum is NOT run by Tascam. Tascam has no forum.

http://tascamforums.com/ is established and maintained by users, hence the minimal charge. I have found it very helpful to be a member.

I have 2 64-bit systems, one with 4 gigs and a newer one with 8. I tend to use a Tascam FW1884 with the 4 gig system and its great. The 8 gig system is my mobile rig and I have an alternate boot drive which I've used to try out Vista64. I usually use an RME FF400 with this system and its as solid as a rock with XP64. Not so much with Vista but I haven't had a chance to try out SP1 yet.

I did have some install problems with 8 gigs. Had to cut back to 4 gigs otherwise XP64's install program would detect an AMD processor and go south. Also, Intel's chipset and bios flashers don't seem to like 8 gigs. Mobo's an Intel 975BX2, btw.

My sense is that 8 gigs vrs 4 doesn't do that much for me when I'm doing mostly multi-track wav recording. But I do tend to keep an external wav editor going in the background and extra memory helps do that. Its most useful, however, when I load lots of samples, like NI and GVI libraries. I've had good luck with BitBridge. Probably also helps loading lots of plugins but I don't do too much of that.

Howard

ORIGINAL: BATOSI

So I'm guessing that theres no solution for this as of yet? I really don't like the idea of having to take out my ram just to get my FW-1082 to work on my comp running 64-bit Vista.
Did anyone find a way to turn off some of the ram or somthing like that?

I think EasyBCD 1.7.2 will let you disable RAM. I'ts the next thing I'm going to try after I buy and install XP32 and get some work done. I'm hoping some one else gets to this first and reports back. My head is so sore from beating it against the Tascam wall that I need a break.

That is a interesting email from Tascam. I have received those before and they are still working on the fixes. I like my 1884 and the only way I could get it to work was in the Makie mode not Native and I could only use 2 Gb of RAM. The controller part of the 1884 will not work with Sonar using Vista 64. Also, ASIO mode seems to be the only way to go for some reason. I believe that the 1884 is outdated since Sonar 6. It needs a Firmware Upgrade if it is going to go into the Vista 64 age. Personally even though the V700 seems pricey I will go that route before I go Vista 64 with Sonar. I hope my investment in plugins will not go down the drain. I will keep a XP32 Sonar system and a VS700 System running until I am sure that the switch will not cause me unbarable stress as I have already experienced with the Tascam, Sonar, 64 Bit dream. Of course I will have to wait until I can afford the VS700 system and I do not own a Roland Keyboard. I play guitar. I am not sure I want the Roland synth accesories and I would prefer not to have to pay for them to get into the VS700 system.
I had a better recording experience with the 1884 using XP32 and Sonar 6 Producer. Sonar 7 P does not perform as well and I have been disappointed.
Peace, KM

TASCAM has posted the Windows Vista 1.7 drivers, loaded them up and system is running
fine on 8 GB RAM, this should be very good news to many FW-1884 users.

NOTE: Despite the asinine replies of some of the participants in this thread, I have been contacted about this issue multiple times for people seeking (and, as below, offering) advice, assistance, and to discuss the problem. Needless to say, this remains a HUGE problem and a hot-button issue among many users. Fortunately, TASCAM fixed the issue I was having but others remain.

I offer the following for your perusal and for the personal information of those who are still having issues with this subject. In the end, I had to buy another mixer to get me through the interim while I waited for TASCAM to post a driver, which they did- finally (more than 18 months later).

Enjoy.
GG

I too have been running into problems trying to go "All 64 Bit". My RME Hammerfalls have no driver support and my Frontier design Dakota does but Frontier no longer makes the Montana and I need at least 32 channels of light pipe. I've been at a stalemate as of late but.....a spark has flickered. My oldest brother (super geek!!) turned me onto ubuntu opensource linux. The OS is free (and very fast) and many multi-track audio programs exist (also free). I was sold when I found 64 bit Hammerfall drivers! Finally, the ability to use my 2 outdated cards in a 64 bit environment and everything is free. I'm buying a new hard drive to experiment with. I won't try to sell you on it but I'll keep you posted. Someone, somewhere, is fed up with the ****ty drivers and support that all products have. For the "Bleeding Edge Users" the only answer and solution is to evolve to a place where GEEKS live. Millions of geeks dismantle and recompile source code everyday on linux. I admit that I haven't yet used it but I'm sold by the idea of the world's best geeks working for me for free and me them.
More to follow if interested.

Hello Count,

I'm guessing your message here is old, but for some reason I only just now got it. I've been around and around with people about x64 drivers, especially with Tascam and Roland, for years, and very little help has come along.

I appreciate your suggestion, although I was already aware of this option, and I would have switched a LoNG time ago if not for 2 things:

1. I paid a lot of money for Cakewalk Sonar and I'm damn well going to use it. Further, I've been using Cakewalk products for years, since 1993, in fact, when all it was was a MIDI sequencer. I'd rather not switch to anything else.

2. The system I use for music production (I am not a pro studio) doubles as a gaming system and a benchmarking speed demon. As you know, there are virtually no "Class A" games for Ubuntu and Linux out there. Solitaire and Minesweeper and their ilk do NOT count. I'm talking of course about those PC-punishing games with hyperrealistic graphics that push your system to the limit- I have poured quite a few bucks into this system to soup it up, and periodically I participate in benchmark competitions.

I know, I know- many have said to use your computer for NOTHING other than music production. For gaming, etc., get another computer. And I have another computer, I could do it, and I would if I were a pro-audio music studio. Since I am not, however, I am a firm believer in the power of the PC to be stretched far beyond the capabilities of other electronic platforms, the PC has the power to do far more than ONE thing, and using it so is a philosophy with me (unless it is a pro business situation, in which case that is a practical, even desireable, solution, since you would lose money having to troubleshoot all the time).

The PC has far more power and capability than people use it for; I think many folks waste the power of their PCs by buying an expensive, souped-up system and then using it for nothing besides playing World of Warcraft and answer emails on (WOW doesn't take that much processing power). That's a shame and a huge waste of resources, not to mention metal, IMHO, and I will NOT be one of those folks. What they do could be done on a netbook or even one of today's cell phones if it had a game controller and/or a keyboard hooked up to it.

However, my problem was finally solved. Last month, Tascam released driver v. 1.07, which claimed that the issue I was having was only caused by having an x64 system and more than 1 or 2 gigs (I don't remember the exact amount- but it was really low) of RAM. Riddle me this: Who in their right mind is going to switch to an x64 OS if they have less than 4 gigs? You are infinitely better off using an x86 OS whenever possible, and the ONLY reason to run an x64 OS- as far as I'm concerned- is to be able to have up to 12 gigs of RAM. Any other advantage is cancelled out by the problems. So while I still think Tascam is full of s&^$t, I am forced to admit that they did finally come thru (although it took them over 18 months).

Anyway, I appreciate your suggestion on this subject. There should be an open, frank dialog about this so that developers can know how we, as endusers or power users, feel. I hope you don't mind, I am going to post this at the end of the original thread (if it remains unlocked) so others searching the web for answers on this issue can see and join the discussion.

Courtney Patricia "GuitarNGamerGirl" Parsons
Cerridwen Productions