ProFire 2626

[Bitfiend]

what DAW are you running it with?

[nightscope]

Originally Posted by Bitfiend

what DAW are you running it with?

Hi Bitfiend,

As this profire will not connect to my PC correctly I cannot use any DAW.

About 20 driver installs & uninstalls down the road at this stage. All other cards, USB devices, etc are out of my PC.

This box will be going back to the clowns that made it rapidly.

ns

[zoff]

Originally Posted by nightscope

Hi Bitfiend,

As this profire will not connect to my PC correctly I cannot use any DAW.

About 20 driver installs & uninstalls down the road at this stage. All other cards, USB devices, etc are out of my PC.


This box will be going back to the clowns that made it rapidly.

ns

Which box the PC or the Profire

BTW The Profire works great with OSX 10.5.3 and Pro Tools 7.4.2.

[nightscope]

Originally Posted by zoff

Which box the PC or the Profire

BTW The Profire works great with OSX 10.5.3 and Pro Tools 7.4.2.

Hi Mr zoff,

The profire will be going back, my PC has always run very well up till now. I spoke with a techie at m-audio at some length. The long of it is that on PC's it a matter of luck whether or not the PC will see the 2626 as hardware or not. So some are lucky and some are not. It's my own fault, really. I vowed never to go near a firewire device. I relented in a moment of weakness as the 2626 has good features advertised and the price is OK. I will continue the search for something that functions properly.

Good that everything is OK with you.

ns

[nightjar]

Originally Posted by nightscope

Hi Mr zoff,

The profire will be going back, my PC has always run very well up till now. I spoke with a techie at m-audio at some length. The long of it is that on PC's it a matter of luck whether or not the PC will see the 2626 as hardware or not. So some are lucky and some are not. It's my own fault, really. I vowed never to go near a firewire device. I relented in a moment of weakness as the 2626 has good features advertised and the price is OK. I will continue the search for something that functions properly.

Good that everything is OK with you.

ns

Seems like you're blaming M-Audio when you should be blaming your PC.

[Dean7]

Originally Posted by nightscope

Hi Mr zoff,

The profire will be going back, my PC has always run very well up till now. I spoke with a techie at m-audio at some length. The long of it is that on PC's it a matter of luck whether or not the PC will see the 2626 as hardware or not. So some are lucky and some are not. It's my own fault, really. I vowed never to go near a firewire device. I relented in a moment of weakness as the 2626 has good features advertised and the price is OK. I will continue the search for something that functions properly.

Good that everything is OK with you.

ns

Well, just buy a PCI-based FireWire controller. Are you using your mobo's on-board controller? If so, they rarely work with firewire audio controllers.

I currently have a PCI-based FW controller and I had my 2626 up and running in under an hour (like from taking it out of the box to recording a test track). So, if you really want your unit to work, try a couple different PCI Firewire controllers. I can't remember off the top of my head the controller I'm using that works with the unit (if you REALLY want me to I can try to look it up), but something like this ought to work:

Newegg.com - Koutech PCI to 1394a Card Model KW-582V2 - Add-On Cards

If it doesn't work, you're out 20 bucks. Not a big deal. :)

Anyway, it WOULD be nice if M-Audio were maintaining a list of controllers that work with the 2626 and those that don't. I searched their web site a bit and couldn't find such a list.

Originally Posted by nightjar

Seems like you're blaming M-Audio when you should be blaming your PC.

Riiiiiiggghhhhtttt.

He's actually blaming M-Audio when HE is to blame. If you buy a FireWire recording interface, you have to be ready to buy a new firewire controller and do some basic troubleshooting in the event that it doesn't work right away when you plug it in.

When you buy a piece of audio equipment do you expect it to just work and sound great with no tweaking? Can I buy a nice guitar then whine to Fender's support when I don't know how to play it? No. So don't turn this in to some dumbass "zomg... it's totally the PC cuz PCs are lamexorz" thing.

[Bitfiend]

Originally Posted by Dean7

Well, just buy a PCI-based FireWire controller. Are you using your mobo's on-board controller? If so, they rarely work with firewire audio controllers.

completely not true.

couple things to try before you send it back.

turn the computer off completely. then the 2626 and unplug it from the computer. restart, then uninstall the drivers. run disk clean up tool, defrag, and if you have any registry cleaning software run that as well. then reboot. uninstall sp3 if it is installed. once you roll back to sp2 you can install the 2626 (once the 2626 is up and running you can safely re-install sp3).
DL the 1394 update (if you haven't already) and install it, http://www.microsoft.com/downloads/d...displaylang=en
reboot, then DL the newest drivers from the website, M-Audio. run them. it'll shut the puter down for you. then plug in the 2626 and turn it on. then start up the computer. It should run you thru the found new hardware wizard and you should be good to go.
Lemme know the outcome.

There is also a chance the issue could be the 2626 is "broken". I had to send my FW Card for the 1640 back to Mackie 4 times before they finally got me a working unit.

[Dean7]

Originally Posted by Bitfiend

completely not true.

couple things to try before you send it back.

turn the computer off completely. then the 2626 and unplug it from the computer. restart, then uninstall the drivers. run disk clean up tool, defrag, and if you have any registry cleaning software run that as well. then reboot. uninstall sp3 if it is installed. once you roll back to sp2 you can install the 2626 (once the 2626 is up and running you can safely re-install sp3).
DL the 1394 update (if you haven't already) and install it, Download details: Update for Windows XP (KB885222)
reboot, then DL the newest drivers from the website, M-Audio. run them. it'll shut the puter down for you. then plug in the 2626 and turn it on. then start up the computer. It should run you thru the found new hardware wizard and you should be good to go.
Lemme know the outcome.

There is also a chance the issue could be the 2626 is "broken". I had to send my FW Card for the 1640 back to Mackie 4 times before they finally got me a working unit.

Wow. You think you can tell me what's what in the world of computers, but you think a disk cleanup tool or defrag will possibly make a difference with a malfunctioning audio interface? That's priceless.

So, tell me how what I said about firewire controllers is completely not true? I've experienced it myself, and I know a lot of people have problems with different firewire controllers. In fact, check this Digidesign page:

Digidesign | Support | Support & Downloads | Windows Laptop Systems — M-Audio FireWire Devices with Pro Tools M-Powered 7.3

Originally Posted by Digidesign

Digidesign has confirmed that the O2Micro FireWire controller in the Dell Precision M65 will not recognize Pro Tools FireWire audio interfaces.
On the Dell Precision M90 (which uses a RICOH FireWire controller), Pro Tools throws unresolvable 6088 errors when recording to a FireWire drive with the FireWire audio interface connected.

So, to further prove my point here's Digi's supported hardware list:

Digidesign | Support | Digidesign-Qualified FireWire/1394 HBA Cards for Windows XP

Why would they have supported firewire controllers if what I said was completely not true and the firewire controller didn't matter? And to seal the deal, another quote:

Originally Posted by Digidesign

Some built-in 1394/FireWire ports may be incompatible with Pro Tools. if you experience FireWire-related issues or errors when using the built-in 1394/FireWire ports on your computer, Digidesign recommends installing a Digidesign-approved 1394/FireWire card.

On a side-note: I just saw that the list I just linked to is for M-Audio Firewire interfaces as well (they have tested and verified that they work) so that's a good list to buy from if you are going to try a new firewire controller.

Anyway, trust me when I say that I know a thing or 2 about computers, and trust me when I say that I am right and you are a moron for "calling me out" on something where you have no idea what you're talking about.

Thanks,

-Dean

[Bitfiend]

Originally Posted by Dean7

Wow. You think you can tell me what's what in the world of computers, but you think a disk cleanup tool or defrag will possibly make a difference with a malfunctioning audio interface? That's priceless.

So, tell me how what I said about firewire controllers is completely not true? I've experienced it myself, and I know a lot of people have problems with different firewire controllers. In fact, check this Digidesign page:

Digidesign | Support | Support & Downloads | Windows Laptop Systems — M-Audio FireWire Devices with Pro Tools M-Powered 7.3



So, to further prove my point here's Digi's supported hardware list:

Digidesign | Support | Digidesign-Qualified FireWire/1394 HBA Cards for Windows XP

Why would they have supported firewire controllers if what I said was completely not true and the firewire controller didn't matter? And to seal the deal, another quote:



On a side-note: I just saw that the list I just linked to is for M-Audio Firewire interfaces as well (they have tested and verified that they work) so that's a good list to buy from if you are going to try a new firewire controller.

Anyway, trust me when I say that I know a thing or 2 about computers, and trust me when I say that I am right and you are a moron for "calling me out" on something where you have no idea what you're talking about.

Thanks,

-Dean

wow, yet another Gs-er who thinks they are a god. relax there Martha. yes i think it can be an issue but it is not ALL FIREWIRE ports on every MoBo or third party PCI card. And i have never had an issue, neither has anyone i know personally.
so you were capable of finding a forum that listed some issues. ok, several thanks for the due diligence mattlock.

Umm, gee, let's see they recommend ones they've tested, ok, microsoft does that with drivers as well. how many things have you loaded on your system that you get the neat little "this driver is not certified....blah, blah, blah" and yet the drivers seem to work fine. over generalizing on a issue makes it a bit harder to trouble shoot.

called you out??? ok whatever. not all what i was doing but of course i happen to once again disagree with one of the holy-er-then-thou-crowd and sweet Jesus i'm a moron. classy, no, no really. my goodness look at the big brain on Dean. really just outstanding, big round folks, give it up to the amazing Mr. Please-Please himself....

[nightscope]

Originally Posted by Bitfiend

Lemme know the outcome.

Hi bit,

The box has been returned. Many thanks for your attempts to help. Also to Mr Dean for your input and links, much appreciated.

ns

[Dean7]

Originally Posted by Bitfiend

wow, yet another Gs-er who thinks they are a god.

I obviously don't think I'm God. That's preposterous. I merely took offense to you saying I was wrong then suggesting that a defrag might affect the issue (which is also preposterous).

Originally Posted by Bitfiend

relax there Martha. yes i think it can be an issue but it is not ALL FIREWIRE ports on every MoBo or third party PCI card. And i have never had an issue, neither has anyone i know personally.

I didn't say that ALL FIREWIRE ports had an issue, and the issues have nothing to do with ports. The only thing that I was talking about is the firewire controller. Did you not catch that?

I have personally experienced this with several motherboards. Maybe I've had bad luck with the controllers in the motherboards I've used, but my experience (and that of some of my friends) has been bad with on-board controllers.

Originally Posted by Bitfiend

so you were capable of finding a forum that listed some issues. ok, several thanks for the due diligence mattlock.

Did you read those links? I didn't find some forum that supported my claims. It was documentation from Digidesign's web site.

Originally Posted by Bitfiend

Umm, gee, let's see they recommend ones they've tested, ok, microsoft does that with drivers as well. how many things have you loaded on your system that you get the neat little "this driver is not certified....blah, blah, blah" and yet the drivers seem to work fine. over generalizing on a issue makes it a bit harder to trouble shoot.

You clearly don't know what you're talking about. Even if you have a Microsoft Certified driver that doesn't mean they test it with the audio interface in question. I didn't over-generalize the issue... I gave him a pretty specific troubleshooting step to try, and if he tries it I bet it would fix his issue (if he buys a supported device).

Originally Posted by Bitfiend

called you out??? ok whatever. not all what i was doing but of course i happen to once again disagree with one of the holy-er-then-thou-crowd and sweet Jesus i'm a moron. classy, no, no really. my goodness look at the big brain on Dean. really just outstanding, big round folks, give it up to the amazing Mr. Please-Please himself....

Your grammar is pretty bad so that was somewhat difficult to understand, but if you didn't mean any disrespect in your post I'm sorry I reacted the way I did. However, that doesn't change the fact that you are wrong.

Thanks,

-Dean

[Dean7]

Originally Posted by nightscope

Hi bit,

The box has been returned. Many thanks for your attempts to help. Also to Mr Dean for your input and links, much appreciated.

ns

No problem. Too bad that didn't work out for you, man! BTW, how was M-Audio support in general? Were they pretty easy to deal with or what?

[nightscope]

Originally Posted by Dean7

No problem. Too bad that didn't work out for you, man! BTW, how was M-Audio support in general? Were they pretty easy to deal with or what?

Hi Dean,

The m-audio tech was great. Very accurate and tried his best for me. We went thro everything in depth. I have at least 4 other m-audio products that have been rock solid. This one just wasn't for me and my system. Maybe it was broken from the outset.

I take back all my unkind and ungracious comments and about m-audio folks. People are more important than boxes.

Nice to meet you!!

ns

[Bitfiend]

yes dean you are absolutely right and i am absolutely wrong.

[RobDrmz]

To clear the air a bit, you are both right. Firewire cards can & cannot make a difference.

The CHIPSET is what is important. What is a chipset? Programming on the card. NEC cards usually work well, but look on the QVL for each product you buy, if there is one.

Oh and by the way, Qualified Vendor Lists and Dirver Signing are supposed ways to generate ad revenue, but again they do help in the testing phase.

[Dean7]

Originally Posted by RobDrmz

To clear the air a bit, you are both right. Firewire cards can & cannot make a difference.

The CHIPSET is what is important. What is a chipset? Programming on the card. NEC cards usually work well, but look on the QVL for each product you buy, if there is one.

Oh and by the way, Qualified Vendor Lists and Dirver Signing are supposed ways to generate ad revenue, but again they do help in the testing phase.

Well, controller would encompass chipset as well in the case of a PCI-based FireWire card. If you're talking about on-board I suppose you're correct in saying that it's the chipset that would cause issues, but it's specifically the firewire controller on said chipset that's causing the issue. So, I fail to see your point.

What, exactly, do you think controller means?

-Dean

[wakestyle]

I'm considering this unit for purchase, and since there seems to be a rep in the area, I'll ask 2 questions:

1. I want to make sure that when using stand alone mode with a card such as the rme hammerfall on a pc, will it operate 8 channels adat both ways?

2. What does the master volume switch on the front control? Outputs 1 and 2? or ?? is it only for when using with firewire?

thanks

[wakestyle]

3. One more question: When using the inputs xlr input, can you bypass the pre's (using xlr for line in levels)?

[stingray1122]

Hey wakestyle, Here are the answers to your three questions.

1. I want to make sure that when using stand alone mode with a card such as the rme hammerfall on a pc, will it operate 8 channels adat both ways?

Yes it will. After installing the drivers for the 2626 on your PC you can connect it and open the control panel to configure your settings for stand-alone mode. This will allow you to choose the clock source, sampling rate and other functions. Here is a snippet from the manual regarding stand alone operation in AD/DA mode.

A/D – D/A Mode:
When this parameter is set to “A/D - D/A” mode the interface operates like a standard analog-to-digital (A/D), digital-to-analog (D/A), and S/PDIF format converter The operation of this mode varies by the sample rate of the interface This is described in detail below:

44.1-48 kHz
(Optical Port B can only be set to S/PDIF at these sample rates)
Analog In 1-8 -> ADAT (port A) Out 1-8
ADAT (port A) In -> 1-8 Analog Out 1-8
Coaxial S/PDIF -> Optical S/PDIF
Optical S/PDIF -> Coaxial S/PDIF

88.2-96 kHz (when Optical Port B is set to ADAT)
Analog In 1-8 -> ADAT Out 1-8
ADAT In 1-8 -> Analog Out 1-8

88.2-96 kHz (when Optical Port B is set to S/PDIF)
Analog In 1-4 -> ADAT Out 1-4
ADAT In 1-4 -> Analog Out 1-4
Coaxial S/PDIF -> Optical S/PDIF
Optical S/PDIF -> Coaxial S/PDIF

176.4-192 kHz
(Optical Port B can only be set to ADAT at this sample rate)
Analog In 1-4 -> ADAT Out 1-4
ADAT In 1-4 -> Analog Out 1-4

2. What does the master volume switch on the front control? Outputs 1 and 2? or ?? is it only for when using with firewire?

The master knob on the front panel controls the output level of the analog DACs. It can be assigned to control any or all of the stereo analog outputs pairs. By default it is set to control outputs 1&2. This can be changed in the control panel via check boxes for analog outputs 1/2, 3/4, 5/6 & 7/8.

3. One more question: When using the inputs xlr input, can you bypass the pre's (using xlr for line in levels)?

No, the analog section of the 2626 is wired such that the XLR inputs are the microphone inputs and always pass through the preamp. The TRS input is dedicated to the line input curcuitry which does bypass the preamp in order to give a clean signal to the ADCs.

I hope this helps!

RayT

[spanktastic]

I would like to upgrade to this for drums so I can have each on its own track
but would I need a whole nother mixer for Eq? or could I just use the Dynamics EQ plug my m-powered has

basically is EQing before or after really a difference?

and if so would making a dynamics Eq on max msp for pre eqing be smart or would a whole nother mixer with the profire2626 be the best bet

[Bierce85]

Originally Posted by stingray1122

Yes the 2626 is based on the Dice DSP rather than the BridgeCo DSP. We've worked very closely with the Dice team to ensure a stable product. The 2626 has undergone extensive testing on various platforms. Of course there will still be some minor kinks to work out as they hit the streets (we can't test for EVERY setup) but things seem to be running pretty smooth so far. The best bet if your concerned would be to wait and see what others have to report on the matter. They are shipping now so it shouldn't be long before the comments start rolling in.

So, to clarify, does this mean that the drivers for the profire 2626 will be/are stable unlike the horrendous profire lightbridge?

I currently work with a digi 002, a digimax fs, API A2D and a benchmark DAC-1. I'm really interested in the 2626 because it would allow me to simplify my setup (lose the 002 and digimax) and use my A2D when tracking drums. There's no way to clock the digimax to the A2D or visa versa which means I can't take advantage of it on drums so the profire is very interesting in that regard since I could clock the 2626 to the API and have 10 inputs (2 A2D + 8 profire).

However, I previously owned a lightbridge and spent a very frustrating few months trying everything to get it to work with nothing but clicks, pops and often just getting no audio at all. M-audio tech support had the nerve to tell me the problems were on my end ("IRQ conflict" even when using a separate firewire controller after I told them I had been using a digi 002 in the EXACT same setup with no problems whatsoever). The unit even had the same problems on my macbook making it clearly obvious that the drivers were shit and m-audio wouldn't admit it. All they wanted to do was blame my computers and get me off the phone.

This left me really bitter towards them as a company and I even vowed not to touch another one of their products at one point but that damn grass is greener mentality has me looking at this thing with serious interest. I would be seriously pissed if I invested the time and money into this thing only to have it fail on me like the lightbridge did but the talk about a different driver from all other m-audio products is making me hopeful.


Has anyone here used a lightbridge and a 2626 and had success with the 2626 where the lightbridge failed? I know one user reported this earlier in the thread but I wouldn't mind hearing some more testimonials. I'm sure there are many who've read this thread and currently have the unit but haven't reported its stability so speak up.. even if you never had a lightbridge.

Thanks,
William

[wakestyle]

Originally Posted by stingray1122

No, the analog section of the 2626 is wired such that the XLR inputs are the microphone inputs and always pass through the preamp. The TRS input is dedicated to the line input curcuitry which does bypass the preamp in order to give a clean signal to the ADCs.

So your saying that the 1/4" jacks on the rear will bypass the preamp section and the instrument inputs (hi-z) aswell?

On my FW410 here, the 1/4" jacks on the front act as instrument inputs.

thanks again

[otobianki74]

so I took the plunge and bought one of these puppies cuz my PFLB was just crap. I'm basically using the unit for a very specific purpose. ideally, I want to run a hybrid logic symph/pro tools m-powered setup at my studio. I've found it very useful to have the ability to record/mix multi-track in either DAW, and as a small studio, at an efficient and cost-effective way.

16 i/o ADAT was my baseline requirement, and with a native pro tools system the options were limited. 8 adat was the most you could do with any of the 002/003 LE hardware family. PFLB promised 32 i/o channels, but in my eyes fell short when pushed to the limits...basically no place for it in a pro or semi-pro room.

if you are looking for an alternative option to run pro tools m-powered and get 16 adat i/o's, then this might be the unit for you.

after a struggle with the **mixer** (a reason I will tell you about later), the unit was up and running. seemed to be stable last night, and today I spent the whole day mixing on it and it rocked...rocked solid that is. none of the glitches, hiccups, crashes, farts, etc. the PFLB brought to the table were in sight. I was testing stability, loading native plugs and 2 uad-1e cards at it was driving beautifully. last night I recorded vocals in a dense mix/edit session at 128 on the buffer setting.

**the struggle** with the mixer occurred because I wanted to set the PROFIRE 2626 to act merely as a dongle (PT) and digital i/o box feeding conversion to my ad/da-16x setup. HOWEVER I wanted to utilize the 8 pres on the 2626, but go in and out analog, patching the analog outs into my ad-16x for conversion. it's a pretty flexible mixer, and thanks to a helpful/smart m-audio tech, he helped me configure it properly (thanks!). if anybody needs a screenshot of the mixer and routing setup for this identical rig, PM me and I'll e-mail it to you...might save you a few minutes.

also, a strange occurrence when using this setup routing an analog signal in and out of the pres on the 2626 into the ad-16x was no activity on the LEDs on the 2626 mic pres (which indicate signal and clip). what I realized, or half-ass concluded, is that the LEDs aren't triggered by some analog circuit in the hardware box receiving input, but are relayed from the computer to the 2626 upon the dsp mixer's receiving the signal.

sure you can always monitor input on the faders in pro tools or the dsp mixer, but what quickly resolved this issue was my ordering optical B input as the first 8 channels on the mixer (analog to/from the preamps were hitting the second optical ports on the a/d-16x -- 9-16 or optical B)...I can only guess the mixer wants to see activity on the first 8 channels of the mixer to relay LED activity to the hardware unit. ok maybe I lost some of you on this, but good to know in any case.

(NOTE: this current configuration allows me to record with my 8 other pres -- chandler, great river, ma5 -- and the eight 2626 pres totaling 16 channels, in either PT or logic, with apogees doing all the ad/da conversion.)

anyway, I dig this unit...I now have a stable i/o box to handle the 16 adat channels to my apogees, allowing me to toggle between my logic symphony system and pro tools m-powered rig. plus, it looks sexy, seems well built, and has 8 pres to spare. ;)

oto

[Dean7]

Originally Posted by otobianki74

so I took the plunge and bought one of these puppies cuz my PFLB was just crap. I'm basically using the unit for a very specific purpose. ideally, I want to run a hybrid logic symph/pro tools m-powered setup at my studio. I've found it very useful to have the ability to record/mix multi-track in either format, and as a small studio, at an efficient and cost-effective way.

16 i/o ADAT was my baseline requirement, and with a native pro tools system the options were limited. 8 adat was the most you could do with any of the 002/003 LE hardware family. PFLB promised 32 i/o channels, but in my eyes fell short when pushed to the limits...basically no place for it in a pro or semi-pro room.

if you are looking for an alternative option to run pro tools m-powered and get 16 adat i/o's, then this might be the unit for you.

after a struggle with the **mixer** (a reason I will tell you about later), the unit was up and running. seemed to be stable last night, and today I spent the whole day mixing on it and it rocked...rocked solid that is. none of the glitches, hiccups, crashes, farts, etc. the PFLB brought to the table were in site. I was testing stability, loading native plugs and 2 uad-1e cards at it was driving beautiful. last night I recorded vocals in a dense mix/edit session at 128 on the buffer setting.

**the struggle** with the mixer occurred because I wanted to set the PROFIRE 2626 to act merely as a dongle (PT) and digital i/o box feeding conversion to my ad/da-16x setup. HOWEVER I wanted to utilize the 8 pres on the 2626, but go in and out analog, patching the analog outs into my ad-16x for conversion. it's a pretty flexible mixer, and thanks to a helpful/smart m-audio tech, he helped me configure it properly (thanks!). if anybody needs a screenshot of the mixer and routing setup for this identical rig, PM me and I'll e-mail it to you...might save you a few minutes.

also, a strange occurrence when using this setup routing an analog signal in and out of the pres on the 2626 into the ad-16x was no activity on the LEDs on the 2626 mic pres (which indicate signal and clip). what I realized, or half-ass concluded, is that the LEDs aren't triggered by some analog circuit in the hardware box receiving input, but are relayed from the computer to the 2626 upon the dsp mixer's receiving the signal.

sure you can always monitor input on the faders in pro tools or the dsp mixer, but what quickly resolved this issue was my ordering optical B input as the first 8 channels on the mixer (analog to/from the preamps were hitting the second optical ports on the a/d-16x (9-16 or optical B)...I can only guess the mixer wants to see activity on the first 8 channels of the mixer to relay LED activity to the hardware unit. ok maybe I lost some of you on this, but good to know in any case.

anyway, I dig this unit...I now have a stable i/o box to handle the 16 adat channels to my apogees, allowing me to toggle between my logic symphony system and pro tools m-powered rig. plus, it looks sexy, seems well built, and has 8 pres to spare. ;)

oto

Glad it worked out for you. I have had nothing but good experiences with mine. I've been using reaper and have yet to see a single crash / glitch. It rocks.

-Dean

[stingray1122]

Hey guys, let me see if I can provide some additional insight here.

First Bierce85,

So, to clarify, does this mean that the drivers for the profire 2626 will be/are stable unlike the horrendous profire lightbridge?

In short, yes.

However, I previously owned a lightbridge and spent a very frustrating few months trying everything to get it to work with nothing but clicks, pops and often just getting no audio at all. M-audio tech support had the nerve to tell me the problems were on my end ("IRQ conflict" even when using a separate firewire controller after I told them I had been using a digi 002 in the EXACT same setup with no problems whatsoever). The unit even had the same problems on my macbook making it clearly obvious that the drivers were shit and m-audio wouldn't admit it. All they wanted to do was blame my computers and get me off the phone.