Topic: MT II problems

[JoeKiller]

It was good that you switched cards after the first problem.  That can make or break later recovery efforts.  That is a good reason to go with a couple of smaller cards vs. one giant 32GB, etc.

Good advice, I always carry a few 2 GB cards with me as well as my trust 8GB.  They are all Kingston.

[dactylus]

It was good that you switched cards after the first problem.  That can make or break later recovery efforts.  That is a good reason to go with a couple of smaller cards vs. one giant 32GB, etc.

Good advice, I always carry a few 2 GB cards with me as well as my trust 8GB.  They are all Kingston.

I do the same thing - Kingston cards with spares...  They are sooooooooo cheap now that it is easy to do.

[mblindsey]

Sorry to hear about what sounded like a great show not getting captured. 

Carbon/Silicon's sound guy was sympathetic to my plight and offered to mail me a copy of the show....he was running a matrix.  Really cool guy.

--Michael

[anhisr]

nice 

[jtessier]

Wow,

It's a bummer that the MT II has had so many issues. It really makes me feel bad that they (M-Audio) closed the office that I worked in last year and let me go since I would have been doing a majority of the testing and I'm fairly confident that because of my experience performing pretty much all of the testing on the MT I, I would have caught at least 80% of what your guys are seeing. Yes, the MT I had it's problems too but I always monitored this board to learn about any problems I didn't catch so I could get to work right away re-producing them and getting the info to the firmware programmers. But I just couldn't make the move to L.A. like they wanted (from Wisconsin where our office was located). I really do feel for you guys. I had hoped that the 'test' group they had in L.A. would be up to the challenge but I guess not so much.  They were at a disadvantage however, being that they (AFAIK) were all musicians (not that there's anything wrong with that) who just happened to test products there, whereas for me, testing and QA are my profession having been doing it since the late 80's. I've now moved on to a Medical Device Company where my skills are being put to good use).

J.T.

[guysonic]

ONLY real problems is using unbalanced 1/4" inputs being fed with mics, but will work again to be low noise being driven from unbalanced low output impedance preamplifiers with noise almost identical to graph below showing balanced preamplifier noise plot into TRS inputs.

damn that 1/4 unbalanced mic input plot is ugly!! 

ONLY real problems is using unbalanced 1/4" inputs being fed with mics, but will work again to be low noise being driven from unbalanced low output impedance preamplifiers with noise almost identical to graph below showing balanced preamplifier noise plot into TRS inputs.

just wondering, why would you get high noise with a mic feed but low noise from an unbalanced low output impedance preamp? Thanks for sharing your findings. +++

Most mics have higher >300 ohm impedance than typical ~50 ohm drive ability of solid-state preamplifier output.  With preamp driving unbalanced input, the ground reference noise is coupled into both -/+ TRS input in nearly equal manner, so noise is canceled (common-mode) in same way as balanced input.  With higher impedance like from mic input, the noise signal is strong going into -minus input, and less strong (due to mic output ohms) into + plus ohms, so there's far less common-mode rejection of the noise signal riding on the input ground reference.

Got word yesterday from M-audio tech my sent-in-for-repair or refund is NOT repairable for known issues, and purchase price for MT2 is being refunded.

So for sure unbalanced input noise issue is now officially an MT2 'product feature' as explained by M-Audio.

However, although not mentioned, the 88.2K bandwidth shortcoming with MT2 applying wrong filter may still be firmware corrected, but I'll never know for not getting the unit back to bench test.

I hope for owners of MT2 using 88.2K mode at least this issue is not a 'standard feature' and will eventually be fixed with a firmware update.  So those using 88.2K sampling rate might still have a non-addressed problem with ~ 20,000 cycle bandwidth limitation until further notice.

So I continue to use my MT1 as the better Microtrack model version for analog input performance reasons.

[dactylus]

Amazing, this is the first time i see the second generation of a product being worse than the first one 

Is there any custom solution to solve the sprinkler noise "feature" ?

Best.

Just for the hell of it I sent my MT II in to DPA to be tested with my 4061 mics & dpa mma6000 just to see if DPA could come up with a fix for the "sprinkler noise".  What did I have to lose?


dpa 4061 > dpa mma6000 > unbalanced 1/4" TRS > MT II

The results were as follows:  Using the unbalanced 1/4" TRS inputs a "sprinkler noise free" recording could be produced when turning the gain all the way down on the MT and doing all of the gain adjustment with the dpa mma6000 amplifier..


That is great news and that is the procedure I followed with my MT I anyway- Can't wait to try and duplicate it when my gear arrives back here!!  Thank you DPA! - Forget you M-Audio..

[endless_soul]

i read a few pages and i dont think this has been reported just yet.

i have been using the MTII about 10 times now, however in the last 2 weeks i had the same problem twice:

i started the recording, checked that the levels werent clipping, put it back in my pocket and enjoyed the gig.
just to give it a check up on the runnig time i took the mtII out of my pocket to find out both times that the recording wasnt actually going on.
when connecting to the computer both times i could see a file but it was resulting empty.

i was running the 1.0.4 beta version, the first time at 24/96 the second at 24/48.

any ideas?

[dactylus]

i read a few pages and i dont think this has been reported just yet.

i have been using the MTII about 10 times now, however in the last 2 weeks i had the same problem twice:

i started the recording, checked that the levels werent clipping, put it back in my pocket and enjoyed the gig.
just to give it a check up on the runnig time i took the mtII out of my pocket to find out both times that the recording wasnt actually going on.
when connecting to the computer both times i could see a file but it was resulting empty.

i was running the 1.0.4 beta version, the first time at 24/96 the second at 24/48.

any ideas?

You said that you had recorded 8 times before without a problem with this same device? 

It is VERY EASY to accidentally hit the STOP / RECORD on the MTs when slipping it in and out of a tight pocket or when someone bumps into you when you have it in a pocket.  You should check periodically throughout the show to confim that you haven't turned the machine off inadvertently...


 

[JoeKiller]

i read a few pages and i dont think this has been reported just yet.

i have been using the MTII about 10 times now, however in the last 2 weeks i had the same problem twice:

i started the recording, checked that the levels werent clipping, put it back in my pocket and enjoyed the gig.
just to give it a check up on the runnig time i took the mtII out of my pocket to find out both times that the recording wasnt actually going on.
when connecting to the computer both times i could see a file but it was resulting empty.

i was running the 1.0.4 beta version, the first time at 24/96 the second at 24/48.

any ideas?

You said that you had recorded 8 times before without a problem with this same device?

It is VERY EASY to accidentally hit the STOP / RECORD on the MTs when slipping it in and out of a tight pocket or when someone bumps into you when you have it in a pocket.  You should check periodically throughout the show to confim that you haven't turned the machine off inadvertently...


 

Hold button anyone?

[it-goes-to-eleven]

just to give it a check up on the runnig time i took the mtII out of my pocket to find out both times that the recording wasnt actually going on.

any ideas?

Yes... Be thankful that it didn't explode in your pants.

[dactylus]

just to give it a check up on the runnig time i took the mtII out of my pocket to find out both times that the recording wasnt actually going on.

any ideas?

Yes... Be thankful that it didn't explode in your pants.

NEVER had a problem with explosions or HEAT... 

 

[bhadella]

I've recently had a MTII related failure.   My walwart has stopped giving the MTII a full charge.  I've tested both the walwart vs. computer usb and have been able to replicate that the walwart will trick the MTII (and my McCally battery) into not charging.  Not good......

[dactylus]

I've recently had a MTII related failure.   My walwart has stopped giving the MTII a full charge.  I've tested both the walwart vs. computer usb and have been able to replicate that the walwart will trick the MTII (and my McCally battery) into not charging.  Not good......

I would definitely inform M-Audio about this - and then see if they respond.

[guysonic]

I've recently had a MTII related failure.   My walwart has stopped giving the MTII a full charge.  I've tested both the walwart vs. computer usb and have been able to replicate that the walwart will trick the MTII (and my McCally battery) into not charging.  Not good......

I would definitely inform M-Audio about this - and then see if they respond.

Why would M-Audios feel responsible for a malfunctioning aftermarket walwart (from wally world?), or is this THE original USB 'wall wart' that came with the  M-Audio deck?   

IF from M-Audio, check USB charger with a different cable just to be sure it's the wall wart, and not a defective cable you can replace in a pinch without waiting for warranty solutions.  However, I would think both are covered by manufacturers 1 year replacement warranty.

What IS NOT covered is using the M-Audio charger to charge A COMPLETELY DIFFERENT BATTERY other than what's inside the MT2, and if the charger breaks trying to charge a different battery, I would not tell then how you were using it as this is abuse NOT COVERED in the replacement warranty.