Very Close

Posted: Fri Mar 24, 2006 5:38 pm

There is always the possibility to make a safety backup of your C: before doing anything like this.

I do hope this will fix your problems, because you seem to have tried everything else. Otherwise I agree with Thomas W. that you go through it step by step. Keep us posted.

Posted: Sun Mar 26, 2006 12:15 am

Quote:

Make sure that you are not running anything that is not directly audio related such as virus, spyware

Good start... =P

sorry, couldnt resist. there isnt anything else running on the firewire bus is there?

twon

Posted: Sun Mar 26, 2006 2:44 pm

cfaalm,

Please explain. What am I to do with this download after I install it?
Just Run it? Do I have to follow instructions that tell me how to manually edit the Registry? Do I have to do anything besides run the update I download?

s

Posted: Sun Mar 26, 2006 4:05 pm

Cruel World,

I downloaded and installed KB885222. Then I searched the Registry for "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\1394_hc_hw_id\1394_instance_id|DeviceParameters". It wasn't there.
I found
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\", but there was no "1394" after it.
So I thought, well, maybe the "_id" means the particular controller identification. There was an "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\FW1884\", followed by, "*FDG007\6&3b7028b6&0&00000000", containing three folders, one of which was Device Parameters, so I tried the edit with that.
There was no "SidSpeed" so, as per the instructions, I added it and modified it. I modified it to "2", which didn't help, so I modified it to "3", which didn't help help either.
I had backed up my c:drive just to be safe, which took about 2 hours. And the edit itself took about an hour, considering I did it twice, checking Cubase each time. Thank God I didn't waste the whole afternoon.
So, what now?
Did somebody say, "Mactel"?

s

Posted: Sun Mar 26, 2006 6:07 pm

Okay. I've got it figured out. The Enum\PCI\1394_hc_hw_id\1394_instance_id\Device Parameters is actually Enum\PCI\VEN_104C&DEV_8020&SUBSYS_00D81028&REV_00\4&19FD8D60&0&60F0\Device Parameters for my Texas Instruments OHCI Compliant IEEE 1394 Host Controller.

Interestingly, in the right frame of VEN_104C&DEV_8020&SUBSYS_00D81028&REV_00\4&19FD8D60&0&60F0\Device Parameters, three things are listed:

1. (Default) REG_SZ (value not set);
2. SidSpeed REG_DWORD 0x00000002 (2);
3. SidSpeedOld REG_DWORD ffffffff (4294967295).

It appears the SidSpeed has already been modified to S400. Wouldn't you agree?

s

Posted: Mon Mar 27, 2006 11:35 am

You are going through all this system modification stuff and to tell you the truth, from the description of the problem, I don't think any of this is necessary.

Have you tried using a project where the audio is NOT on the same drive as your program drive?

I think everyone reading this thread missed that point and they've all been focused on another problem.

I'm not saying that what you are doing wont help. I'm just saying that the problem is more likely caused by running everything from the same harddrive.

Posted: Mon Mar 27, 2006 12:20 pm

Hi sibbeypeck, I have tried to watch this thread closely to see how things were, but I live in GMT+1 so I must have missed something Very Happy

Quote:

2. SidSpeed REG_DWORD 0x00000002 (2); It appears the SidSpeed has already been modified to S400. Wouldn't you agree?

Read the remark at point 5 carefully. From the knowledge base :

Quote:

Note If you try to use a value that is larger than 3, SidSpeed will use a value of 0 (S100 speed).

Put it on 3.

Did you run the hotfix already?

Posted: Mon Mar 27, 2006 12:46 pm

I'd like to agree with pr0gr4m on the separate disks. At a higher track-count you are sure to run into trouble.

Our keyboard player had no problems however to record 16 x 48KHz/24bits + 1 midi track on the same disk as his OS. It was only a separate partition. Even 4 x 44.1KHz/16bits on a 5400 rpm notebook drive can be done. These are stone cold facts.

Now that 16 track thing was just tracking (on a Maxtor SATA I 250GB 16MB), but it is to illustrate that it can be done to a certain extend.

Posted: Tue Mar 28, 2006 9:41 am

Gentlemen,

Thanks for staying with me on this.

Regarding SidSpeed, my interpretation is that a value of 2 configures Windows for 400 mbps, and a value of 3 configures Windows for 400 or 800 mbps. Since the FW1884 runs at 400 mbps, I thought setting the value at 3 would be unnecessary.

I have run the hotfix - at least, I think I have. I downloaded and installed and ran KB885222.

I have not tried putting the project files on a separate drive. Such was not necessary with Cakewalk. I have uninstalled Cubase, and will try putting the project files on a separate drive after I re-install Cubase.

An interesting aside: since downloading and installing the hotfix, the colors are gone from this forum, and I get an error message with each screen change.

s

Posted: Tue Mar 28, 2006 4:02 pm

Have you done a testdrive since the hotfix yet? We are all very curious of course.

I have read a little more on the microsoft page and sidspeed 3 S400/S800 speed turns out to be the Windows XP Service Pack 1 [SP1] value. My PC has a Gigabyte K8NF9 Ultra with onboard 1394b. There was no question what value. But even with your SIIG card I'd put it on the value that XP had before SP2 threw it all to the birds.

I think right now the only other company that makes a PCI-E FW-card is Belkin.

Posted: Fri Mar 31, 2006 8:42 pm

Hey man...

Fellow FW-1884 user here.

Love it, but it has also caused a LOT of pain in the past. Seems to work
great with some Texas Instrument Firewire cards and NOT with others.

But your not alone, a TON of people have obtained drop-outs. With
some tweking you can get rid of it though.

For me it took disabling my 'firewire' connections in "Network Connections"
and also making sure that my onboard soundcard was selected in windows
audio manager instead of the FW-1884.

Here's a thread with a TON of different things you can try:

http://tascamforums.com/index.php?showtopic=8729

Seach those TascamForums for other threads... tons of stuff about drop
outs on there.

Btw, to any possible new buyers of the FW-1884. Even though it's been
a pain to set up completely, it's worth it. This is a great piece of heavy
duty gear that has streamlined my work process a ton.

Posted: Fri Mar 31, 2006 8:55 pm

PCI Audio is where it is at!!! Never a peep of issues like these on any 3 of my Intel DAW's with RME PCI DSP cards... Firewire can be wonderful, it is just not 100% yet IMO...

Cool

Posted: Sun Apr 02, 2006 1:45 pm

I uninstalled and re-installed Cubase. And, I started a new project with the project files on an external USB drive.
Result: I can record and play back audio at 512, with fewer pauses of shorter duration.

I do not like having to go to extraordinary lengths only to make audio processing work better than it did, but still not as well as it should. I do not know what the answer is. My computer system should be adequate. I have optimized it for audio in so many ways that I get error messages when Internet screens change.

I feel like maybe 5% of the changes I've made have had any positive effect on audio performance, while 90% have had detrimental effects on system performance, overall. I may reset everything but the registry edit and the file location to default, and proceed from there. I suspect those are the only two changes I've made that have helped.

treysmith,

You say, "it took disabling my 'firewire' connections in 'Network Connections'". Does that mean: Start > Control Panel > Network Connections > LAN or High-Speed Internet > 1394 Connection 2 > Disable?

And, what exactly do you mean by, "making sure that my onboard soundcard was selected in windows audio manager instead of the FW-1884."?
Which is my "onboard soundcard"? - the SB LIVE! card?, or the A/D converter in the 1884?
And how do you get to "windows audio manager"?

s

Posted: Tue Apr 18, 2006 5:12 am

Where'd everybody go?

Posted: Tue Apr 18, 2006 3:09 pm

sibleypeck: I can fix all your problems in one procedure....................
you ready? ............It involes a shotgun and your PC and then later a ride to the apple store. If this is too drastic for you or you really can't afford a Mac (understandably) , then you have ONLY 2 options:

1. Quit using your PC as a general computer

2. Quit using your PC as a general computer and get another inexpensive computer for your general computing.

You will never ever ever ever have a stable, efficient Daw if you use it for email, websurfing,or anything other than Audio. There are just to many misc. drivers, hardware conficts, SPYWARE, etc. etc. etc. Get EVERYTHING off of your computer (printers, freeware, MS office). Reinstall Windows and your DAW software and thats it !!!!!! Update both and unplug your ethernet to it. You should then have a very stable DAW. (for a PC anyways)

Good Luck

This topic sponsored by: