View Full Version : ProjectMix I/O problems - please help
KaresB
10-06-2006, 03:38 PM
Hello y'all,
(i just found this forum)
i have a problem with my ProjectMix ever since i bought it (in February) and by now it's really getting on my nerves: the LCD display is constantly acting up (characters or entire lines disappearing or freezing, etc) - and the LEDs on the buttons keep going off (for example after pressing the 'set up' button on and off).
Everything remains functional (that's the reason for my patience so far), it's "only" the display and the buttons' LEDs... Rather annoying...
The firmware is 10.19.05.A - actually, i'm checking m-audio.com for a new firmware biweekly but no luck... not even a beta.
The thing is, i read about these problems even before i made the purchase, so i can't say i wasn't warned, but i really had no idea that M-Audio wouldn't upgrade the firmware for an entire year...!
I would really like to know if there's just ONE user out there who does not experience these kind of problems at all.
And, of course, i would really appreciate help from M-Audio's support dept. Thanks!!!
Chrispy
10-06-2006, 06:48 PM
Yeah, happens to me occasionally, but doesn't really bother me because it corrects itself after a bit.
But I agree. They should have released a new firmware by now.
KaresB
10-07-2006, 03:39 AM
Another thing:
contrary to M-Audio's knowledge base article (http://www.m-audio.com/index.php?do=support.faq&ID=c9d161aac920b52a508de3167730a7ae), where it advises us to "power on the FireWire device, then turn the computer on last", i always have to boot up Windows BEFORE switching on the ProjectMix, otherwise i get no sound at all.
This is something i can live with if i have to, but still, it happens occasionally that when i have to reboot the PC i forget to switch off the PMix too, so when Windows is up and running again, there's no sound output on the PMix. Then i have to reboot the PMix and all is OK.
Is this normal?...
Thanks for any help or feedback, guys.
KaresB
10-07-2006, 03:44 AM
Yeah, happens to me occasionally, but doesn't really bother me because it corrects itself after a bit.
But I agree. They should have released a new firmware by now.
True, after using the buttons, most of their LEDs come back to life one after the other, but not the Select buttons, for example. After 8 months now, it irritates me.
Chrispy
10-07-2006, 05:15 AM
Another thing:
contrary to M-Audio's knowledge base article (http://www.m-audio.com/index.php?do=support.faq&ID=c9d161aac920b52a508de3167730a7ae), where it advises us to "power on the FireWire device, then turn the computer on last", i always have to boot up Windows BEFORE switching on the ProjectMix, otherwise i get no sound at all.
This is something i can live with if i have to, but still, it happens occasionally that when i have to reboot the PC i forget to switch off the PMix too, so when Windows is up and running again, there's no sound output on the PMix. Then i have to reboot the PMix and all is OK.
Is this normal?...
Thanks for any help or feedback, guys.
This is another problem I have experienced. I do the exact same procedure as you! I also sometimes power cycle the ProjectMix while in windows as the sound sometimes just stops working (I think it has something to do with my firewire, although it does it on both my Texas Instruments and VIA ports), sometimes it works when I turn it on before the PC.
Also, sometimes in Protools, I get the message 'Protools cannot communitcate with the HUI, power cycle the device or reconnect'; I was told by M-Audio tech support that it wouldn't be a problem with the ProjectMix (although I disagree).
It seems I'm not the only one having problems then!
KaresB
10-07-2006, 05:44 AM
This is another problem I have experienced. I do the exact same procedure as you! I also sometimes power cycle the ProjectMix while in windows as the sound sometimes just stops working (I think it has something to do with my firewire, although it does it on both my Texas Instruments and VIA ports), sometimes it works when I turn it on before the PC.
Also, sometimes in Protools, I get the message 'Protools cannot communitcate with the HUI, power cycle the device or reconnect'; I was told by M-Audio tech support that it wouldn't be a problem with the ProjectMix (although I disagree).
It seems I'm not the only one having problems then!
Yes, this PT-error message happened to me too, but i mainly use Cubase, so i forgot about it.
BTW: when i bought the PMix i was trying to use it with a VIA FW-chip, but it kept dropping connection so i had to get another FW card with the TI chip - and it's working ok (apart from the above mentioned problems, but i think those are firmware-related).
Chrispy
10-07-2006, 06:00 AM
Funnily enough, a VIA chipset was recommended to me by tech support. I might move the external HD onto the VIA and put the PMix onto the TI one then.
jlaudon@netviga
10-07-2006, 08:14 AM
It's interesting that you sometimes lose connection with the PC and the Projectmix - this has been my problem with the Mac as well, and also my dealer's (!) problem with his PC - it really shouldn't happen - what if you're recording a crucial take and it loses connection? My 828mkII and my new Saffire Pro 26 i/o work very reliably, but I;ve nothing but problems these past four months with the Promix - even sold it a few days ago to a guy with a PC who couldn't even get his PC to see the Projectmix - suffice it to say I gace him his money back, and will continue to mess with it for awhile.
I kind of question the quality of the actual physical Firewire connector on the back of the Promix (also my dealer thinks this is what causes loss of connection periodically) - it seems kind of loose - what do you guys think?
Chrispy
10-07-2006, 08:35 AM
what if you're recording a crucial take and it loses connection?
I kind of question the quality of the actual physical Firewire connector on the back of the Promix (also my dealer thinks this is what causes loss of connection periodically) - it seems kind of loose - what do you guys think?
It has cut out once while we were doing a take but it wasn't that crucial, but we did waste a fair bit of time rebooting and reopening protools etc.
TBH I haven't really looked at the firewire port on the back of the ProMix, but it seems to lose the connection if i move the laptop the slightest bit.
jlaudon@netviga
10-08-2006, 02:05 AM
The thing is, does any other interface (I haven't heard of one yet) lose connections like this? - we're talking about something that is at least semi-pro gear.
KaresB
10-08-2006, 05:26 AM
The thing is, does any other interface (I haven't heard of one yet) lose connections like this? - we're talking about something that is at least semi-pro gear.
I'm using it with Cubase SX3 and (with the Texas Instruments FireWire chip) it never dropped connection so far. (It did happen with PT once though.)
Did you experience the problems i described in my first post too?
jlaudon@netviga
10-08-2006, 08:06 AM
I haven't had any LCD problems, but when I would try to reinstall the firmware using my Mac, it would either not see the Mac, or when it finally did, halfway thru the install it lost connection, then the LCD went blank (just a yellow strip all the way across). I was able to finally reinstall using the dealer's PC (with a different Firewire cable, and even a different adapter- my adapter says 12v DC, and his was 9v DC, both came with the respective Projectmix so go figure... - the Promix specifies 9v Dc on the back next to the connecter, so maybe this is another potential problem - if the wrong voltage is used, I'm sure the LCD would weird out). Anyway, something else to think about...
KaresB
10-10-2006, 12:32 PM
(Not a very busy place, this is... :()
Chrispy
10-10-2006, 01:50 PM
(Not a very busy place, this is... :()
Better than nothing though!
Shame there aren't any reps from M-Audio surfing these boards.
David Muniz
10-11-2006, 02:02 PM
There are. I'm here.
Guys, the problems you are describing can typically be handled with a call to our tech support team. I haven't experienced this, except for the occasional loss of communication with Pro Tools, (which I've seen happen with a Command 8 and 002) on my Mac. A reboot fixes everything and I'm back to normal.
Do the regular check for IRQ sharing, etc and start there.
KaresB
10-11-2006, 02:10 PM
There are. I'm here.
Guys, the problems you are describing can typically be handled with a call to our tech support team. I haven't experienced this, except for the occasional loss of communication with Pro Tools, (which I've seen happen with a Command 8 and 002) on my Mac. A reboot fixes everything and I'm back to normal.
Do the regular check for IRQ sharing, etc and start there.
David, thanks for the response - and good to have you here.
But believe me, i have good reason for coming here and asking for your help. The problems i described (buttons' LEDs going out, misbehaving LCD display) are KNOWN to be common with the ProjectMix.
This was reported in some published reviews, trade mags. Even before i bought the thing. These problems are ACKNOWLEDGED by your local (Hungarian) distributor - who's a nice and helpful guy, btw, so i'm not blaming him - but the only advice he could come up with was "let's hope for a new firmware".
Please do not ask me to call the US support from here. I'd really appreciate if you could help.
Thanks.
David Muniz
10-11-2006, 02:18 PM
PM me and i"ll have the tech team contact you.
Thanks
D
KaresB
10-11-2006, 02:20 PM
PM me and i"ll have the tech team contact you.
Thanks
D
U got mail.
Thank You.
Kares
KaresB
10-13-2006, 07:38 AM
PM me and i"ll have the tech team contact you.
Thanks
D
David, have you got my PMs?...
Thanks...
K
Pershing02
10-17-2006, 09:40 PM
Well, after only 4 months my PMix just died on me.... I just submitted a trouble ticket on the M-audio website for technical support.
The system will not power up at all. Last night I closed out a Abelton live 6 session, and the faders went crazy! I shrugged it off, and proceeded to power down to switch to Pro-Tools mode. It came on and then went out....I switched off and back on again and it powered up as normal. Opened P-tools and the faders went balistic! The display started fading in and out everytime a fader would move because of automation. The playback sounds were a bit "off" and "boomy" so I turned everything off until about an hour ago I tried to power the Pmix up and .... nothing.... The 9v adapter lights up green as usual.
I had not dealt with an update since I purchased it in June of this year. I also saw a few posts on various sites mentioning issues, but they were the first ones to get them and I figured there would be a firmware update or two to clear up any problems. I hope M-Audio will resolve this quickly.
KaresB
10-18-2006, 02:01 AM
Well, after only 4 months my PMix just died on me.... I just submitted a trouble ticket on the M-audio website for technical support.
The system will not power up at all. Last night I closed out a Abelton live 6 session, and the faders went crazy! I shrugged it off, and proceeded to power down to switch to Pro-Tools mode. It came on and then went out....I switched off and back on again and it powered up as normal. Opened P-tools and the faders went balistic! The display started fading in and out everytime a fader would move because of automation. The playback sounds were a bit "off" and "boomy" so I turned everything off until about an hour ago I tried to power the Pmix up and .... nothing.... The 9v adapter lights up green as usual.
I had not dealt with an update since I purchased it in June of this year. I also saw a few posts on various sites mentioning issues, but they were the first ones to get them and I figured there would be a firmware update or two to clear up any problems. I hope M-Audio will resolve this quickly.
Sorry to hear that. To me it sounds like you'll definitely have to take it back for repairs or a replacement.
It's true that there wasn't a firmware update for a year now and it's desperately needed (to fix the problems i described in the first post), but your PMix obviously need urgent servicing.
KaresB
10-18-2006, 03:47 AM
my adapter says 12v DC, and his was 9v DC, both came with the respective Projectmix so go figure... - the Promix specifies 9v Dc on the back next to the connecter, so maybe this is another potential problem - if the wrong voltage is used, I'm sure the LCD would weird out). Anyway, something else to think about...
I just checked the ps that came with my PMix: it is 9V/3500mA so at least this one seems to be OK.
Chrispy
10-18-2006, 05:34 AM
I just checked the ps that came with my PMix: it is 9V/3500mA so at least this one seems to be OK.
Same as mine also.
Pershing02
10-18-2006, 10:50 AM
Yeah, mine is the 9 volt version also.
I did see somewhere that someone had a 12 volt version! :eek:
Still no answer or respose to my ticket yet :mad: . Not happy at all. I may just call them and see what can be done:( .
Pershing02
10-18-2006, 11:50 AM
Well, just got off the phone with Tech support, and got a RA number. I'm going to send it back tomorrow and pay to ship it - three to four weeks downtime :mad:
I'm in the "IT" profession as well and have also sold some higher end audio and video equipment in my sales day - and with an item this expensive (anything over a grand I consider expensive), the manufacturer would send a return shipment RMA and be done with it. Well you live and you learn...
jlaudon@netviga
10-19-2006, 08:27 AM
that's what I thought too... well, live and learn - at least I another interface that works for now (828mkII - can't do anything to make it crash:-)
Pershing02
10-19-2006, 10:44 PM
Well guys, its in the wind....:o M-Audio in California should get it by Wednesday of next week.....:( Then three or more weeks before I see it again...:mad:
KaresB
10-24-2006, 02:19 AM
bump
(still no reply from tech support...)
Pershing02
10-24-2006, 04:33 AM
bump
(still no reply from tech support...)
You still have not heard from them? Wow! I hope there is a good explanation for this.... I'm going out on a limb as say that there is a gap in communication between the US branch and yours, and that the message about our issue just fell through the cracks.... still not much comfort I know.
KaresB
10-24-2006, 04:37 AM
I'm going out on a limb as say that there is a gap in communication between the US branch and yours
No - i'm waiting for the US tech support to contact me.
KaresB
10-25-2006, 03:24 PM
Still waiting.
FYI: i contacted M-Audio Tech Support on October 13, filling in the online form. I immediately got an autoreply saying they will get back to me in 24-36 hours. Now it's the 25th and i've yet to see any response from them.
*update: i just realized i filled in the UK site's support form instead of the US - my mistake, apologies. (but someone from the UK support team could've responded at least.)
Pershing02
10-25-2006, 06:51 PM
Still waiting.
FYI: i contacted M-Audio Tech Support on October 13, filling in the online form. I immediately got an autoreply saying they will get back to me in 24-36 hours. Now it's the 25th and i've yet to see any response from them.
Yeah, I did the same thing - and being myself I also called in to the customer service department, after working techical support for several years I did not want to trust someone getting back to me...
Date: 10/17/2006 18:49:35 by:
Joe Ramsey Date: by:
[Joe Ramsey -- 10/17/2006 18:49:00]
Customer submitted a new incident
Incident Data 1: ID = NA49961,
Projectmix hardware failure!
Project mix will not power up. No lights, no power! I bought this thing in June of this year, and 4 months later this thing dies? I saw some post on Digidesigns page but dismissed it - my mistake!
Please tell me something, I spent to much money on this thing! I own your BX5 monitors, e49 keyboard, triggerfinger and the Project Mix! I read on another post where users were experiencing random letters displayed - I had this when I closed out any of the applications - Live 6, Pro-Tools M-Powered, Reason, Sonar5. Last Night when I closed out Live 6, the faders went nuts before it closed out.I powered done and restarted in Pro-Tools mode and the display faded in and out, went out and came back on. Then when I opened a session, the faders went balistic! I tried to play back the session, but the sound was off and echoing. I powered it down last night, and just attempted to power it up 45 minuites ago. What's going on!
Called in 10/18 - A.S.
joeramsey@bellsouth.net
Product ProjectMix Problem Area Hardware
Driver Version 1.0.0.5 CPU Speed Dual 2.6
Platform win xp pro sp2 RAM 2 gig DDR2
System Type Desktop RA # 42161-49961CR WARRANTY
jlaudon@netviga
10-27-2006, 08:26 AM
Yup. Me too - still waiting...
KaresB
10-27-2006, 10:57 AM
FYI: my complaint is already being investigated, thanks to David for the hook-up.
Jlaudon, as it turned out, there might be a problem with using the US support form from outside the States - they might not have even received your case, so i suggest to contact them in some other way.
jlaudon@netviga
10-28-2006, 09:07 AM
I had actually been forwarded to the US support guys directly thru David, as my problems have been pretty major with the Pmix, and the local dealer/tech guys in HK aren't that deeply familiar with these problems.
Thanks for the input.
KaresB
11-10-2006, 09:03 AM
Just a friendly bump to see if there are other PMix users out there NOT experiencing the problems i described in the first posts - or if someone has some different experiences, then please share them.
Thanks.
Pershing02
11-10-2006, 09:51 AM
Just a friendly bump to see if there are other PMix users out there NOT experiencing the problems i described in the first posts - or if someone has some different experiences, then please share them.
Thanks.
Well I guess this would qualify as a different experience.....on a positive note :) .
I received a replacement PMix last week :D and so far so good. They turned things around faster than expected ;) so props out to the M-audio guys in California for reponding in a timely manner to resolve my issue :cool: .
KaresB
11-10-2006, 09:57 AM
Well I guess this would qualify as a different experience.....on a positive note :) .
I received a replacement PMix last week :D and so far so good. They turned things around faster than expected ;) so props out to the M-audio guys in California for reponding in a timely manner to resolve my issue :cool: .
Glad to hear this.
Just to clarify though: so you're not experiencing any lcd-misbehavior (characters geting stuck or disappearing when flipping banks often), nor the leds in the buttons go out after pressing 'set up' twice?... Which sequencer are you using it with?
Thanks in advance.
Pershing02
11-10-2006, 06:08 PM
Glad to hear this.
Just to clarify though: so you're not experiencing any lcd-misbehavior (characters geting stuck or disappearing when flipping banks often), nor the leds in the buttons go out after pressing 'set up' twice?... Which sequencer are you using it with?
Thanks in advance.
On the first one, yes in abundance. This one I have not experienced anything yet. But then again I did not have any issues for the first two months on the previous one...
I use it with Live 6, Pro-Tools M-powered, Reason, Sonar 5 (not as much) Cubase (this is Atlanta GA and everybody is using something different!) etc.
KaresB
11-19-2006, 04:20 AM
update:
apparently M-Audio Support have reproduced and acknowledged the problems with the LCD display and the LEDs when used under Cubase - they are currently investigating if it's firmware-related or maybe caused by Cubase. Hopefully they'll come up with a solution soon.
No response on the power-up issue (if PMix is powered up before Windows, no sound will come out of it) though.
Chrispy
11-19-2006, 05:12 PM
You might all be interested in this, looks like we've got a driver update:
http://www.maudio.co.uk/index.php?do=support.drivers&k=driver&s=2&p=327212ef66595c9bc875d0dd268b96cb&o=15&f=760
Edit: Looks like it only adds support for a new piece of hardware rather than update the driver.
KaresB
12-02-2006, 07:22 AM
....bump....
Craig B
12-03-2006, 02:35 PM
I have been having the worst time...I used an audiofile card, with windows media xp, was working great, then upgraded to project mix...I kept getting error messages, HUI communication, clock not being able to record @ 44.1k, ...SO...M-Audio said the switch to XP home or Pro. I did...XP Pro...guess what?...Still the same messages, I'm at a standstill here...Has any one ever had this happen? If so, what is the cure?
KaresB
12-18-2006, 02:31 AM
bump
Still waiting for a solution (or any response) from M-Audio Support.
Pershing02
12-18-2006, 05:49 AM
Wow Kares, sorry to hear that. Is there anyone in the US branch that has a solution to this problem?
My Pmix is still funtional, but does still display the LCD error, and gets unusually hot in the right rear of unit when used with Abelton Live 6. Not sure why, but I have scaled back my use of this program for fear it will die on me like the last one.
globalhiccup
12-25-2006, 05:00 PM
Well, I am one of many more awaiting solutions for Project Mix problems - LEDs, etc. I find that with PT M-powered 7.3 (on Mac) some ProjectMix controls simply DONT function, or otherwise are erratic. For Cubase 4, ditto. I.M.O. both software and firmware updates are urgently needed to keep up, and a year is too long .... Having said all that, I have found M-Audio products in general to be EXCELLENT and stable, and the UK support team are friendly and accessible. If M-Audio continues in the direction of improved customer relations as well as improved and supported products, it is going to sail way ahead of companies like Native Instruments.
KaresB
01-02-2007, 01:19 AM
Still no news on any upcoming fixes or suggestions from M-Audio...
Last time i got a reply from one of the support engineers was in November - and while he was helpful and acknowledged the display/LED problems, couldn't tell whether they're caused by the PMix firmware or Cubase. Looks like they're still investigating.
jlaudon@netviga
01-07-2007, 11:37 PM
My Projectmix is still in for repairs (more than 3 months already) and NO NEWS, no contact, no nothing. Pretty soon I'm gonna start a boycott M-audio products thread...
KaresB
01-08-2007, 02:55 AM
My Projectmix is still in for repairs (more than 3 months already) and NO NEWS, no contact, no nothing.
Now that is ridiculous!... There's absolutely no excuse for them sitting on a product for 3 months - they should simply replace it if it takes so long to repair.
jlaudon@netviga
01-09-2007, 07:01 AM
Yeah, tell me about it - this isn't a minor piece of gear. I guess the dealer knows I have a couple other audio interfaces, hence the inaction.
I'm trying to sell my Oxygen 49 as well (I bought it to play and program drum parts to save the wear on my other controller, but when I play drum parts on it, it double triggers at high velocity - absolutely no use to me). After this, I'm done with Maudio stuff - bad service, bad quality, etc...
KaresB
01-19-2007, 03:37 AM
still waiting...
globalhiccup
01-19-2007, 04:32 AM
I was informed a couple of weeks ago by M-Audio in the UK that a firmware update for Project Mix is due fairly imminently. I have the feeling that all the focus for music companies at this time of year goes to the NAMM shows.
KaresB
01-19-2007, 07:10 AM
I was informed a couple of weeks ago by M-Audio in the UK that a firmware update for Project Mix is due fairly imminently. I have the feeling that all the focus for music companies at this time of year goes to the NAMM shows.
I hear ya, but excuse me, when was the last time a PM-firmware was released?...
I tell you: October 2005. No comment.
planetg
01-23-2007, 12:35 PM
Hey, I'm a bit late in joining this discussion, I've come across some strange LCD problems, when my ProjectMix is idle (i.e. not in a recording environment) characters are displayed on the LCD, it's usually always the same 3, however a new one has just popped up. Here's what it says:
Channel 1, Second Row: 7
Channel 2, First Row: C
Channel 4, First Row: s
Channel 5, First Row: d
As I said it doesn't give me any problems when recording, just a bit annoying when not recording. Makes it look faulty. :(
I've got the latest Firmware Version: 5.10.00.5036v2 which was released on October 31 - 2006, but no idea how I can stop it! Any help would be appreciated!
KaresB
01-26-2007, 02:08 AM
I've got the latest Firmware Version: 5.10.00.5036v2 which was released on October 31 - 2006,
That's a driver, not firmware. Firmware hasn't been updated since 2005... Looks like M-Audio forgot about ProjectMix already. Might be a good idea for me too.
Chrispy
01-26-2007, 08:12 AM
Well, Windows Vista is upon us and my mate installed it last night, apparently it works very well. But still, all we get from M-Audio is this http://www.maudio.co.uk/index.php?do=support.faq&ID=2b9102ba8e228823582720fb3beba029
Paradigm
02-13-2007, 09:16 PM
Well i just got my brand new ProjectMix Last night. I spent over 6 hours trying to figure out how to keep it connected. It works for about 2 mins and then no sound or control. Sometimes it crashes my computer and a have force the machine to shut down. Today i reinstalled the firmware and it work perfect for about 15 mins then began to screw up. So so far i havent even had the joy of using the projectmix for ant sessions. Im a little dissapointed as this is my first piece of M-Audio Hardware
KaresB
02-15-2007, 11:41 AM
Well i just got my brand new ProjectMix Last night. I spent over 6 hours trying to figure out how to keep it connected. It works for about 2 mins and then no sound or control. Sometimes it crashes my computer and a have force the machine to shut down. Today i reinstalled the firmware and it work perfect for about 15 mins then began to screw up. So so far i havent even had the joy of using the projectmix for ant sessions. Im a little dissapointed as this is my first piece of M-Audio Hardware
Which app are you trying to use it with? I'm asking because M-Audio tech support claims that Cubase's code is buggy that's why the PMix is acting up in Cubase mode. But frankly, i'm not buying this explanation. I had very similar experiences when i tested it with PT too.
On the other hand: make sure your firewire controller card has a Texas Instruments chip on it, because after testing a few different cards i found that the PMix only keeps connection if it runs on a TI controller.
Chrispy
02-15-2007, 02:00 PM
Which app are you trying to use it with? I'm asking because M-Audio tech support claims that Cubase's code is buggy that's why the PMix is acting up in Cubase mode. But frankly, i'm not buying this explanation. I had very similar experiences when i tested it with PT too.
On the other hand: make sure your firewire controller card has a Texas Instruments chip on it, because after testing a few different cards i found that the PMix only keeps connection if it runs on a TI controller.
Surely M-Audio should build their drivers AROUND Cubase and not make them so that they work with how they expect Cubase to work (if you know what I mean!!).
I've been using my PMix on a PCMCIA Firewire card with a VIA chipset and haven't had any problems as yet, so far the only problem has been poor firewire cables (I run my ext HD on the laptops built in TI controller).
Paradigm
02-15-2007, 03:23 PM
Which app are you trying to use it with? I'm asking because M-Audio tech support claims that Cubase's code is buggy that's why the PMix is acting up in Cubase mode. But frankly, i'm not buying this explanation. I had very similar experiences when i tested it with PT too.
On the other hand: make sure your firewire controller card has a Texas Instruments chip on it, because after testing a few different cards i found that the PMix only keeps connection if it runs on a TI controller.
Well im using it with logic express. But thats not the only problem. The pmix loses connention with my computer even if im not using the DAW software.
I am also using the built in firewire on my g4 tower and my brand new macbook,both with the same problem. I think i might just have a bad unit.
Zacchino
02-28-2007, 02:39 PM
KaresB,
Here's some workaround and dead-ends I found for you, for us :
I've been searching for a thread like this for about 5 or 6 month now (*sic*).
I have a ProjectMix I/O with the *ahem* "latest" firmware (indeed 2005, this is just like they don't give a **** about their acquired customers).
- (1) For the LCD Display Bug :
"Channel 1, Second Row: 7
Channel 2, First Row: C
Channel 4, First Row: s
Channel 5, First Row: d"
(I just get exactly the same letters after exiting my Sequencer, but times to times it changes... Looks like the ProjectMix is trying to tell me something... C, S, D... Crazy Stupid Dog... donno)
Good news : this happens also with Acid Pro 6.0d. Why is it a good news ? Cuz I'm a betatester for this software, so you can trust me on this one, it doesn't come from Acid Pro. It also happens to me on Cubase SX 3.1, conclusion : LCD Display Bug comes from the Firmware of the ProjectMix. Blame M-Audio's Firmware devellopers, even if they did a WONDERFUL piece of work, they should time to time try to update this Firmware (and include an Acid Pro mode ??? No Way ! Acid Pro, Tracktion, etc are not selling enough to interrest M-Audio).
- (2) For the "no sound if switched on before XP" issue:
Listen to this :
A first hotliner from the M-Audio France support told me that this Firewire issue you're having is due to the FireWire Interface (IEEE1394a) of your Motherboard...
...Hmmmm.... Let's dig in this hole :
I have an Asus P5WD2-E Premium motherboard that I know inside out (Bios tweaked for great reliability thanx to Asus's official Forums) with the Texas Instrument FireWire interface. Latest Texas Instrument's FireWire interface are known to be reliable and Rock Solid. And no, the Texas Instrument FireWire interface is not sharing any IRQ (yet it is on a virtual IRQ created by Windows XP, as it's on n°21, but it should be just Fine !).
Not to mention that I tryied the famous KB904412 (http://www.microsoft.com/downloads/details.aspx?familyid=A2091337-A0EA-4B34-B19F-B6EC04C1F2D2&displaylang=fr) firewire patch from Microsoft with NO changes on this issue. (Still, I highly recommend this patch as it basically rectify XP Service Pack 2 that turns down the speed of all your Firewire ports !!! this was Microsoft's *cough* wonderful *cough* idea, they thought it would make the communication between the peripheral and XP more reliable).
Anyway, I decided to trust, for once, another French Technical Support guy (who was awesome and very qualified compared to the former).
He suggested me to buy a professional PCI to FireWire Card (ADS Tech Pyro 1394, known to be great on Avid's video hardware) to avoid this issue of switching on the ProjectMix AFTER Windows XP has started (nor, no sound).
So, what I'm gonna do ?
I just don't have the money yet to invest in such a card. When I get the money and the Card, I'll keep you guys up to tell you if it really worked or not.
Hope this post will enlighten many other ProjectMix users in the same situation,
Cheers from France,
-Z.
KaresB
03-01-2007, 01:51 AM
Thanks for your input, Zacchino. (And welcome to the club.... :()
I have the same ADS Tech Pyro (Basic DV) FW card you mention. (I got it after 2 other models failed to provide an uninterrupted connection with the PMix.) This card is great indeed, no problems with the connection so far.
However, i always have to make sure that i boot up XP before turning on the ProjectMix, otherwise i get no sound out of it (even though the PMix control panel displays the signal). But if this would be the only problem, i could live with it.
The LCD and LED problems are much more annoying, and indeed these look most certainly firmware-related, regardless of M-Audio Support's claim. I mean, i KNOW that Cubase is far from being perfect or bug-free (i struggle with the bloody thing for 10 years now...), but i admit, i can't fully trust M-Audio's firmware either. I'm still hoping that they would come up with a fix for all these problems in the NEAR future, otherwise a lot of us will just give up and jump ship.
Zacchino
03-01-2007, 05:42 PM
>However, i always have to make sure that i boot up XP before
>turning on the ProjectMix
This is the only issue i'm tryin to avoid. So I'm not gonna buy this card then...
So we're in 2 dead ends here ?
Great.
I'm sure M-Audio will update the ProjectMix IO Firmware when they'll make a newer model, if they don't, I'll just go and buy an RME and a Mackie Control. I just can't live with awkward hardware, especially if the issue is software / firmware based.
Zacchino
03-01-2007, 05:51 PM
Okay just spoke too fast, the Digi003 is almost out. Now we know where M-Audio's been joining forces !
http://www.sweetwater.com/store/detail/Digi003Fact
KaresB
03-02-2007, 02:01 AM
>However, i always have to make sure that i boot up XP before
>turning on the ProjectMix
This is the only issue i'm tryin to avoid. So I'm not gonna buy this card then...
I don't think it has anything to do with the FW controller card. The card itself is great. Let me just add that i had similar powering-up issues with the Delta1010 (sometimes it didn't power up itself with Windows, i had to unplug its power cable and replug it, then it was working fine).
Anyway, in what order i have to switch on the PC and the PMix is not something i personally care about that much, it's only a little annoying if i reboot the PC but forget to power-cycle the PMix too. But as i said, if everything else would work flawlessly then i could live with this problem easily.
KaresB
03-02-2007, 02:06 AM
Okay just spoke too fast, the Digi003 is almost out. Now we know where M-Audio's been joining forces !
http://www.sweetwater.com/store/detail/Digi003Fact
Let me just say that the Digi003 is not gonna get me too excited, that's for sure... For me, the PMix still looks better - if only it would work properly....!
Mr_BOL
03-04-2007, 05:49 PM
Hello there,
Looks like there have been many faluts with the projectmix ... here's my story:
Bought one projectmix, couldn't get it working at all. Phoned M-Audio and they told me to take it back to the reseller.
Swapped it for another one (did the same setup as i did with previous projectmix) and it works (with LogicPro on mac g5).
With the new one however, i can't get any sound out directly from the projectmix (i.e. logic is sending the audio there, but the projectmix isn't sending it through the audio outs to my monitors).
Any suggestions? am i missing something? is it something to do with the control panel setup? ...
Any help would be gratefully received! [the manual is rubbish!]
Thanks.
Mr_BOL
03-05-2007, 05:22 AM
well, looks like i've got another faulty unit ...
spoken the m-audio, ran through a couple of things and still no sound out ...
how annoying!
any ideas? any one else had this problem?
KaresB
03-18-2007, 03:53 AM
Come on, M-Audio....! The ProjectMix needs a new firmware!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!
Chrispy
03-18-2007, 03:24 PM
Come on, M-Audio....! The ProjectMix needs a new firmware!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!
Seconded!!!
capitalp
03-23-2007, 01:09 PM
Just joined this forum as I was looking for some insight to my Project Mix I/O problem.
I boot up and the LED display doesn't even display. This was after I downloaded the new Driver 1.8.1v3. Just one day all of the sudden I booted up and the LED was an amber brown and my motorized faders stopped working. I contacted M-Audio and they suggested I send it in because it sounds like a hardware problem.
Sending it in this weekend if anyone else has experienced this problem let me know.
nobranddesign
03-27-2007, 07:33 PM
I am having serious issues with the mapping control software under a Conroe high speed desktop setup and my p4 laptop. Both exact same symptoms. four years apart in technology. Both freeze 6 seconds in after opening control software. Went through extensive troubleshooting with firewire networking, irq setting, installing pci firewire cards, removing other sound cards. nothing fixed it yet, any suggestions. Ill be taking this one back in a day or so if I cant resolve it. I got it to work great with cubase under normal cubase control. My primary uses are going to be mixed between audiomulch and max jitter/arkaos. really need the mapping capability to work with some sensor setups I have too. I also was only able to get the audio and transport controls to work with vegas. Couldnt write automation with the mackie control or the midi CC message mode. I deal with mapping and data translation professionally everyday and the fact that I can't dial this thing in even with maudio support on the phone for 2 hours is sad honestly. I really pitty the hobby user trying to plug it in and go. Maudio was great in there support with me but they cant figure it out either. they were able to recreate the problem with one of the computers in thier office but they dont know why yet. hoping they havent just forgot about me.
anybody have this software freeze issue?
Angelo
03-31-2007, 08:05 AM
Hi,
I have found a problem in the midi in port of my Projectmix (updated to the last firmware/driver). It looses note on messages when the master keyboard (Yamaha S90ES) transmits a midi clock. Furthermore, the modulation wheel control is not fluid.When I use Midisport 4x4 no problems at all.
I agree that a new firmware/driver is necessary.
Regards
Angelo
arniiie
03-31-2007, 11:05 AM
I bought a used PM three days ago. Now it is fried. I was uploading the firmware from my laptop and midway through the communication broke down.
When I started it again there was only a yellow stripe so the firmware is not there anymore. I had communication problems before the update as well. I have already emailed M-Audio tech support, but do you know how this can be fixed? Do i have to send it in?
nobranddesign
03-31-2007, 01:51 PM
It may not be electrically fried but if the communication chip for the firewire is bunk than youll have to send it in. Only exception to that would be if you have a little alligator clip, rom flash setup but even then you would have to get the comm protocol from m audio or you would be speaking garble to the chip. Just send it in if that's an option. Alot easier. Just a note. The firewire protocol is the biggest culprit of problems in this unit by far. It causes the led issues indirectly as well as the midi mapping issues myself and most other people had. I started another thread for this thing after I went through some major testing for three days. I took that brand new unit back after really sifting through it. That thing is a tack hammer and I needed a 10 pound sledge if you get my drift. Too bad the 10 bit fader's make the price so high for the actual usable performance you get from it. The 10 bit faders and open mapping it claimed to have were why I bought it. Didnt care in the slightest about the audio card although I love my Delta card made by them. 2 changes and it would be golden but they don't care really. There on to developing a new project now.
B
nobranddesign
03-31-2007, 01:59 PM
So I ended up figuring out my own issue with the control software bug and I posted my test results to another thread but I wanted to put one here in case people read my post with the question about it. main concern is don't have midiyoke installed when you are trying to remap the midi layer of the projectmix.
the other thread with the full test of many softwares and data mapping is here:
http://www.audioforums.com/forums/showthread.php?t=17697&highlight=projectmix
hope it helps
B
beatsbykev
04-12-2007, 08:14 PM
FOR DAYS AND DAYS I'VE BEEN TRYING TO GET MY PROJECT MIX TO WORK AND IT WON'T DO ANYTHING BUT TURN ON! NOTHING SHOWS ON THE LED SCREEN! AND WHEN I TRY TO HOLD THE AUX BUTTON DOWN TO TURN IT TO PRO TOOLS MODE A LIGHT OR THE NUMBER 88 SHOWS UP BUT NOTHING ELSE!:mad: ANYBODY HAVE THIS PROBLEM? PLEASE HELP!:(
the Cre8or
04-17-2007, 12:08 PM
beats,
you should contact M-audio or your distributor. Sounds like your Firmware is toast. Little you can do except send it in for repair. If you bought it from a store recently, just exchange it at the store. If it's more than 30 days, contact M_Audio.
beatsbykev
04-17-2007, 07:16 PM
man that sucks thanks for the reply
Chrispy
04-19-2007, 06:11 PM
Got a new one for you guys...
Not used my PMix for a while because I've been off work with a poorly foot (all better now!). It has done this to me a few times now... Sometimes when I throw the switch at the back to turn it on it flickers then goes off and needs turning back to the off position then back to get it to work. Do I send it back? Or is it another firmware bug? (Just done a fresh software install on my PC, re-format an all that!).
the Cre8or
04-19-2007, 10:12 PM
I'd see what M-Audio support suggests.
Chrispy
04-25-2007, 07:38 AM
They suggested a fault with the switch (quite possible), but I suggest some dust or something between the switch contacts as after a bit of on-and-offing with the power unplugged (excersizing the switch!) it worked normally again.
EDIT: Came back to it this evening and it's doing it again. I will be extremely peed if I have to send it for repair as it is literally a few weeks out of warranty.
natc4
04-25-2007, 09:37 PM
http://www.audioforums.com/forums/showthread.php?t=18122
It isnt anything i have read about in here yet, but noone has been replying and i really need help, i cant retype it cause it was too much so this is the link to my story so please guys if you could take a look it would mean alot. and tell if i have to send it away and get a new one or is there something incompatible with my system or something I NEED TO KNOW (im crying over here CRYING!)
Chrispy
04-29-2007, 08:13 PM
Sorry, me again, just very very very very very annoyed that I've spent over £800 on this piece of hardware that your appear to have to be a genius to setup without any problems.
Not only does my unit not power up until the 20th/30th flick of the switch, the problem that I've been having since day 1 is still annoying the hell out of me.
It constantly blips and stutters when recording in Adobe Audition (1.5) no matter what inputs I'm using (S/PDIF or Mic/Line) and I can't get to the bottom of it, recording ruined. Here's what I've tried:
1. Trying the unit on another firewire controller, the one I normally use it with is on its own IRQ, the other one I've tried (on-board) shares its IRQ with networking which I need on this machine.
2. Altering the ASIO/WDM Buffer size.
3. Unplugging everything BUT the PMix from my machine.
4. Disabling Clock Throttling (machine spec below).
5. Trying other recording software.
and
6. Numerous re-installs of the driver.
HELP ME BEFORE I TAKE A HAMMER TO THIS DAMN THING!!!
NOTE: It doesn't do this in my streamlined version of XP, but why should it do it in normal XP? It should have been released ready to be used on normal PC's!!
Thanks!
PC Spec:
Fujitsu Siemens Amilo A1630
SiS 755 chipset
AMD Athlon 64 3700+ CPU
1GB RAM
100GB internal 4200RPM drive
300GB external 7200RPM SATA drive
Texas Instruments onboard firewire
VIA PCMCIA card firewire
Have I missed anything??
jlaudon@netviga
04-29-2007, 11:45 PM
NOTE: It doesn't do this in my streamlined version of XP, but why should it do it in normal XP? It should have been released ready to be used on normal PC's!!
Thanks!
PC Spec:
Fujitsu Siemens Amilo A1630
SiS 755 chipset
AMD Athlon 64 3700+ CPU
1GB RAM
100GB internal 4200RPM drive
300GB external 7200RPM SATA drive
Texas Instruments onboard firewire
VIA PCMCIA card firewire
Have I missed anything??
One possibility of why it works with your streamlined version of XP is that you might not have enough available RAM with the full XP.
Chrispy
04-30-2007, 05:18 PM
OK, a follow up on the switch thing. I think it may be the power supply that is faulty, the LED on it is flickering erratically (seemed fine the other day when I checked it after discovering the power-up fault).
Will M-Audio replace the power supply if it turns out to be faulty? If not, will any old 9V Switch Mode PSU that can deliver 3500mA (or more) do the job??
Is a faulty power supply likely to be the source of my dodgy recording problems? Tried the streamlined XP again last night and it blipped and stuttered in that too.
Unkle Bunkle
05-03-2007, 03:54 PM
I recently purchased the Project Mix and hooked it up to my pc (Windows XP Pro - SP2). I am running Pro Tools MPowered V. 7.3.1. When i set up an audio track in Pro Tools and enable the track, you can hear the instrument/vocal but it is crackly. I contacted M-Audio support and they are saying it is the firewire card. I am using a PCI based firewire card and it uses windows drivers. Shows up as VIA OHI compatible 1394 and appears to be installed fine. I went out and purchased another PCI firewire card, Starcom 4 port 1394 card and installed it. Same result. Has anyone heard of this issue before? I tried different PCI slots and changed some IRQ settings, varied Buffer sizes, etc...same thing. They suggested a SIIG firewire card. Any feedback would be greatly appreciated.
itsplayed
05-04-2007, 09:20 AM
Did the firewire card come with it's own drivers?
If so, have you tried updating the drivers for it using the disk?
Is the card using it's own IRQ allocation(not sharing)?
What motherboard are you using?
In the control panel, go to 'network connections' and right click on the '1394 connection' and select properties. In the menu that opens deselect the Net Adapter ability for the card....this may help.
Mr_BOL
05-05-2007, 06:25 AM
Does anyone have a copy of the old firmware or know where i can get hold of one? (not 10.19.05A) [m-audio website only has the latest one on it.]
According to MAUDIO uk, in order to get sound out the ProjectMix with a Mac G5 Dual Processor you have to install the old driver 1.7.4 and an earlier firmware. (Is that actually true? - any1 with this setup with a PM working?)
Please help!! I've been without sound out on my PM for 5 months ...:mad:
Unkle Bunkle
05-08-2007, 08:35 AM
The firewire card did not come with a driver disk and i searched online for them and all i could find were sites stating to use windows generic drivers. The card is not sharing an IRQ setting with another piece of hardware. I tired disabling the net adapter portion of the firewire card but still received the same result. I am picking up an SIIG firewire card today which were recommended to me by M-Audio support. I will let you know how it goes. Cheers.
Unkle Bunkle
05-14-2007, 03:52 PM
I've since installed another firewire card..Belkin and it works like a charm. FYI. Crackly audio = incompatible firewire.
Now i have a different issue. I am running the Project mix with pro tools mpowered and use a midi controller that connects to the pc via usb. I can get pro tools to talk "somewhat" to the controller. I can hear the audio and if i create an AUX track and send it there, i can record the audio but it will not record the midi. I tried changing the HUI configuration but it knocks out my audio. Any suggestions?
Chrispy
05-14-2007, 04:28 PM
I've since installed another firewire card..Belkin and it works like a charm. FYI. Crackly audio = incompatible firewire.
So what chipset does the belkin have? Is it PCI card or PCMCIA? I may consider replacing my VIA one (once I get my new power supply for the PMix! How long does it take!!!??!!).
indiecodemonkey
05-15-2007, 11:35 PM
Chrispy, what is your setup for that? Like, what computer are you using, what brand of PCMCIA card are you using, what's your DAW, etc...
I'm only asking b/c I'm expeiencing problems with my PCMCIA FireWire card running the projectmix and my DigiDrive Firewire 80 external drive at the same time. I'm using a Dell Insprion 8500 laptop and Pro Tools M-Powered 7.3.x
indiecodemonkey
05-15-2007, 11:47 PM
The firewire card did not come with a driver disk and i searched online for them and all i could find were sites stating to use windows generic drivers. The card is not sharing an IRQ setting with another piece of hardware. I tired disabling the net adapter portion of the firewire card but still received the same result. I am picking up an SIIG firewire card today which were recommended to me by M-Audio support. I will let you know how it goes. Cheers.
Unkle, I don't know what you ended up gong with, but for my desktop system (sounds like I'm running the same setup as you, Win XP Pro SP2, PT M-Powered), I went out and got this SIIG PCI card:
http://www.siig.com/product.asp?pid=374
and that new card in combination with my exiting internal card did the trick. My ProjectMix works great now on my desktop...
too bad I can't get it working on my laptop to save my life:
http://www.audioforums.com/forums/showthread.php?t=18461
KaresB
05-18-2007, 01:46 PM
OK, no need for a firmware upgrade now. The bloody thing just died on me. No sign of life whatsoever.
Brilliant...
Chrispy
05-19-2007, 08:00 AM
OK, no need for a firmware upgrade now. The bloody thing just died on me. No sign of life whatsoever.
Brilliant...
My advice, check the power supply!
The light on the pack should stay constantly green, when the PSU for mine was faulty, when you turn the PMix on, the light would flicker.
KaresB
05-21-2007, 03:09 AM
Yeah, i'm hoping it's just the PS... but i can only find out later tonight..
Will let you know
thanks
KaresB
05-21-2007, 11:02 AM
Indeed, the power supply was the guilty one. I got a replacement from the local distributor and all is well now. (I mean: "only" the usual problems...)
Mr_BOL
05-25-2007, 12:10 PM
Hi there!
Just thought I'd let you guys know that I was so fed up with my ProjectMix not getting any sound out (setup is a MacG5 Dual Processor OSX 10.4.8 running Logic Pro7) that my reseller let me swap it for a Tascam FW-1884.
2 minutes from getting it home, my studio was up and running!
I'm on top of the world!
By the way, anyone with the same setup as me (lets face it, it's a common one), M-Audio are in the process of fixing the firmware for the PM. Although, there's no telling when that will come out - maybe a week, maybe a year.
All the best,
Mr_BOL.
Chrispy
06-26-2007, 06:26 PM
Has anyone ever had to order parts from M-Audio before? I've had my power supply on order since 15th May through DV247 and I'm starting to get withdrawal symptoms!
How long should it take!?
Chrispy
07-13-2007, 01:28 PM
Just thought I'd update.
Got my new power supply yesterday, and my PMix has been running better than ever. I haven't had a single pop or crackle out of it, not even a communication error! Superb!
PSU only took 2 months to arrive!
Jaybird
04-22-2008, 09:58 AM
At last I found out that if two toilets in my home are flushed at once it kicks on the water pump and my PJ will crash and need to be rebooted and my DAW restarted.
Its to the point that I hope the thing blows up.
Would a Battery Backup, power conditioner help?
I have a VIA firewire card as im in latin america and impoeeible to get a good TI card.
But what gives with the mixer turning off?
Put it this way, when its time to record my tube amp I need to cycle my DAW and PJ and sometimes several times and the crash will cause my DAW to default to the ASIO drivers so its rather a pain.
I love the mixer but mine does not work.
Any hints on the power issue? Its the only kit in my studio that goes off when the lights are turned on.
vBulletin® v3.8.4, Copyright ©2000-2010, Jelsoft Enterprises Ltd.