Topic: MT II problems

[anhisr]

They just got back to me to try it with other cards.  I told them I tried it with two different 8gb cards and a 16gb card.  Pointed the person to the forum and this topic starting with page 8 so they could get on the same page.  I also mentioned that the recording is 24/44.1 when reading the card in windows even though the MT II thinks it is 24/96.  Maybe they will get what we are trying to tell them. 

[rustoleum]

I got this reply a day or two ago:

Today I ran a test recording to the MT II using the S/PDIF input and a 8GB CF Card.
The setting was set to S/PDIF 16-bit.
I connected a S/PDIF cable out of a PC (playing iTunes Radio) straight to the MT II.

So far, it's been recording for approx 5hrs. with the 2GB point being roughly 3hrs.
The only obvious problem that I can spot, without interrupting the recording or uploading the file is that the Right Channel cuts out for long periods of time, but it hasn't frozen or stopped the recording.

Since then, I've tried a 16/44.1 test and it stopped also.  I'm not at home so I don't have the exact size/time of each file, but I'd put money on it being the equivalent of a 24/96 or 16/96 file.  Interesting that this guys says he had an 8gb card given your tech support guys reply that he's using a 4gb and they don't have anything bigger.  Also interesting about his channel cut-out issue.  I haven't seen any problems like that. 

A question:  are you guys formatting through the MTII or through your computer?  I don't think it should make a difference, but who knows?  Also - is everyone at firmware 1.04?

[anhisr]

Yes I format with the MTII and I am using 1.04 Beta.  I get the feeling that all the tech support is not in one room. 

[busterr]

Yep, I also only format in the MTII, and I am running the 1.0.4 BETA.
And yeah, it could be 2 or more different people working on this, I forget who was working on mine.
Right now, I'm about 1hr into a 16/44.1 test w/ an 8gb card, but seeing as it was only showing 5:59:xx instead of ~12:xx:xx for available time I suspect it will stop then, as yours did.
I have not had any channel dropouts whatsoever, so I'm not sure whats going on there .

[NOLAfishwater]

gonna test out that time left in file issue tomorrow and see how mine looks. My computer recognizes the files the way they were supposed to be recorded with the seamless split and at the sample rate/bit rate they were recorded in.

[rustoleum]

Just replied to m-audio with the following info:

Hi Alex,
Did your recording exceed 6 hours non-stop?

I just ran a 16 bit/48 khz test with the following results:
At the conclusion of the test when the MT2 stopped recording and powered itself down, I had three files:
file 1: 1.86GB, 2:53:36 record time
file 2: 1.86GB, 2:53:35 record time
file 3: 36.0 MB, 0:3:16 record time

for a grand total of 5 hours, 50 minutes and 27 seconds.

With an "8GB" card (7.54GB avail for recording according to Windows) and 16/48 recording, I'd expect
= 11.7 hours (11 hours, 42 mins)

So, it turns out this 5 hours and 50 minutes and 27 seconds is the stop point I'd expect if I was running a signal at 16 bits, 96khz signal:
With 8Gb card and 16/96 recording, I'd expect
= 5.86 hours (~5 hours, 51 minutes) of record time [7.54 * 1024 (GB to MB) * 1024 (MB to KB) * 1024 (KB to B) * 8 (B to b) / 3072000 (bits / second of 16/96 recording) = 21083 seconds]

So my results seem to mimic the behavior I observed at 24/48 (where the stop point was calculated as though a 24/96 signal were being recorded). For a 16 bit recording, you would need to exceed 6 hours of record time with an 8GB card to have different results than what I've experienced, hence my initial question at the start of this reply. If a 24bit test were being run, you'd need to exceed 4 hours of record time (~3:54).

Thanks. Please let me know if you need more info, are unclear on my question or would like me to try anything else.

[busterr]

Nicely laid out there Rustoleum...

And Alex is the same person dealing w/ my incident FWIW.

@ 16/44.1 mine stopped at ~5:57:xx, like I expected. Unfortunately I did not try to fill the rest of the card, which I should have tried, because after the first file it only showed 3:14:xx remaining(obviously it calculated the remaining~4.5gb at 16/96). I should have checked to see if it would go past that, but I re-formated too quickly, and just don't feel like trying again .

[anhisr]

Got this reply about the 24/44 being read as 24/96 on time remaining.

This issue has been escelated* to verifications where we will attempt to re-create the behavior.

Then if we can re-create we can begin the resolution process.


* they need to turn on a spell checker.  escalated 

[rustoleum]

I got this today:

Thank you for your test results.
It appears that the problem currently occurs with 8GB cards.
We have logged this issue and are addressing it in a future release of the firmware update for the MT II.
I would advise for you to find a temporary work around this problem, by keeping your recordings within the limited time span, until the new firmware version is released.
If you have any questions regarding this issue, please let me know.

[anhisr]

Maybe I need to tell my people that your people have obliviously recreated the problem and are working on a fix.  Or I could just leave them alone.

[busterr]

Unfortunately I have to chime in and say mine has now locked-up twice this month with 2 separate scenarios...running the 1.0.4 FW, Transcend 8gb 120x and the other time transcend 8gb 133x card, never had an issue w/ lockups in ~70 files run on these cards.

First time was somewhat user error(although still possibly a flaw in design/FW), having used a 4xAA battery pack with not exactly fresh batteries, battery pack died ~40min in, and the MTII apparently couldn't switch to the internal battery, and simply locked up at that point. That was running @ 24/48 via spdif. File has yet to be recovered after 3 attempts with 3 different programs.

Last night at Claypool it happened again(had no intentions of even using it, but his new policy dictated it)...this time I was running on the internal battery the whole time @ 24/48 via 1/8" mic input. It made it 1:43:xx in and that's where it stayed..locked up. No file visible on the card, although in the properties it shows ~ the correct size of said file, currently trying to recover that one.

Not really looking for help (unless someone can help recover the file/s  , my attempts have been unsuccessful so far)...I will never trust this thing again, not that I ever did...but I will no longer be using it, it's just time for me to move on.

[mblindsey]

I wonder if the MTII is just picky about media size/brand/speed??  I have recorded hours of stuff with SanDisk Ultra II 4GB cards and am not having troubles.

--Michael

[dactylus]

If I were running dpa4061 > dpa MMA6000 > MTII

Is the output of the dpa MMA6000 balanced or unbalanced?  I'd be connecting the stereo 3.5 mm Mini-jack from the dpa MMA6000 to two 1/4" cables > the MTII.

Would I get the "sprinkler" noise that you get when running 1/4" unbalanced into the MTII?  I'm sorry if this is a dumb question...

 



Type MMA6000

Miniature Microphone Amplifier

Description  Specifications  Related products  Related pages  Graphs and more     


Frequency range, ± 2 dB:
20 Hz - 20 kHz (+1/-1.5 dB)
Total harmonic distortion (THD):
<0.03%
Maximum output voltage:
+/- 1.5 V peak before clipping
Weight:
235 g (8.3 oz) excl. batteries
Operating temperature range:
-10° C to +50° C
Dimensions:
123 x 85 x 35 mm (4.8 x 3.3 x 1.4 in)
Colour:
Black
Input impedance:
>3 kOhm
Output impedance:
<50 Ohm
 Crosstalk:
<-60 dB at 1 kHz
Battery life time:
>24 hours (professional quality Alkaline batteries within temp. range)
No. of channels:
2
Output connector:
3.5 mm Mini-jack, stereo
Input Connector:
2 MicroDots
Low cut:
Switchable: Flat or 100 Hz, 12 dB/octave
Equivalent input noise:
At 0 dB gain: <3 µV (RMS A-weight); At 37 dB gain: <1,5 µV (RMS A-weight)
Gain:
0 dB-37.5 dB in steps of approx. 2.5 dB
External input voltage range:
12-30 VDC
Power consumption:
20 mA, both channels loaded.
 
 
 

[rustoleum]

that's too bad busterr.  I've been pretty happy with mine despite the 8gb and larger issue.  I've used it in the field a couple times and have also been digging the ease of DPA 4060 -> MTII for when I want to record myself on the guitar without the hastle and time consumption of breaking out the big rig.

I'm afraid I don't know the answer to your question, dactylus, but the 3.5mm jack does not exhibit the "sprinkler" issue so you could always go  MMA6000->3.5mm out -> MT II (3.5 in) if you do notice any issues with the 1/4"s.

[anhisr]

Today M-Audio closed both of my tickets.  Either their is a new update coming soon or they don't care.  If no update happens I am going to reopen the tickets. They have a box for that.