Topic: MicroTrack 24/96 Beta 1.2.3

[tubos]

Just updated from 1.0.2 to 1.2.3 the first thing i noticed
is that the rocker switch behaves too sensitive now,
i actually preferred the original less sensitive version.

[John Kelly]

Just updated from 1.0.2 to 1.2.3 the first thing i noticed
is that the rocker switch behaves too sensitive now,
i actually preferred the original less sensitive version.

Actually happened in the last update (1.2.0 I believe).  I think they toned it down a bit in this one, but IMO it needs to be even less sensitive.

[frankho]

Agreed. The [NAV] wheel and level control buttons are too sensitive. I probably will sell my MT for this reason, if it's not fixed in the next firmware update.

[jtessier]

I then hit "record time available", and it shows me two times

"Total time on media: 01:58:10"
and then right below it
"Max time per file: 00:57:52"

I noticed that on Aaron's as well, however, it didn't happen on mine with the microdrive.  So I'm thinking it only works on CF right now.

Also, from watching the levels on the MT, it looks like the channels were right no mine as well, but I haven't had the chance to make sure yet.

The 'max time per file' field shows up a cards and drives that are larger than the 2GB limit (on cards 2GB and less, the max time per file and the total time left on the media would always be the same). So the 'max time per file' number will show up on both Microdrives and Compact Flash cards if they are over 2GB. It should show up on 6GB Microdrives but doesn't when they are blank which is most likely intertwined with the problem where the Microtrack treats those drives as if they were 2GB drives until they have less than 4GB available on them.

J.T.

[Ed.]

makes sense.

[Nick Graham]

GODDAMN M-AUDIO.

They've not responded to my emails in 2 weeks. Last thing they told me was to contact them for return information, which I did, and they've never replied. They were supposed to send me a repair ticket # and an address/dept. to ship it to...which again they've never done.

So tonight I get home, find a phone number, and give 'em a call....and now 2 hours later I'm still on hold. They close in 33 minutes, and I can imagine at 9:00 I'll get a message saying their department is closed.

This is BS....

[udovdh]

Weird.
Even I get a reply from M-Audio after a day or two...

[neutrino]

Weird.
Even I get a reply from M-Audio after a day or two...

I think they have been fairly quick with support responses, but Nick has been waiting a ridiculous amount of time for an RMA.
dB-

[Nick Graham]

Weird.
Even I get a reply from M-Audio after a day or two...

I think they have been fairly quick with support responses, but Nick has been waiting a ridiculous amount of time for an RMA.
dB-

My prediction was correct. At exactly 9:00 CST I was informed their offices were closed.

I was extremely pissed last night, luckily I've calmed down considerably since. When I was originally emailing back and forth with tech support questions I'd always get an answer within a day, usually in a matter of a few hours. Ever since I convinced them the problem was not something that could be resolved with a firware update (unit will not even power up, so that's impossible to do anyway) or through email - that it was a legitimate repair issue - they've completely ignored me.

[cmoorevt]

That sucks.  Maybe get whomever you bought it from to get in touch with their rep.

[mmedley.]

Yeah, I'd take it back to GC and change it out. That is horse shit. You could always get a receipt dated within 30 days from someone and return it?

[alienbobz]

My experience with two different MTs and CF cards (both 4GB, Kingston Elite Pro 45x) indicates it's still a problem - for me.  I've not yet tested on 1.2.3, but I had the problem on 1.1.5 and 1.2.0.  I hope 1.2.3 fixes it - I rarely see performances longer than 2hrs at a stretch, so if the latest firmware allows the full 2hrs as it should (twice on each card), then I'm all smiles.

It was with 1.2.3 that I'm saying the behavior is as I've described. I've even narrowed down more closely when the problem happens (how much free space triggers the counter problem).

With less than 4,289,597,440 bytes free on the disk or card, everything works great.  A 4GB Hitachi microdrive formatted for me to have 4,087,689,216 bytes free so it didn't have the problem. A Trancend 4GB CF card had 4,063,481,856 bytes free so also was not a problem.  With more than 4,289,875,968 bytes free the problem surfaced. Again, since you can't get this many bytes free on the 4GB volumes you should not be able to encounter this problem at all. If you do I think it's a different problem with similar symptoms or a misunderstanding of what problem I am describing.

I hope this info helps.

Happy recording,

J.T.

J.T. - I am wondering how you fill up the 2 gigs. I have a 6GB Microdrive and I had this problem my last Friday. I know you said you used a wav file. Did you just recorde one that was 2 gigs? I have a few shows next week and don't want to run into this timing issue again. Let me know.

[udovdh]

If you find any problems:


PLEASE send them to the M-Audio support <techsupt@m-audio.com>. Describe clearly what you experienced, how to produce, etc, etc.
Please do so they can fix the issues.

[jsfrank]

Hopefully this firmware update will fix what nailed me at both Panic shows this weekend. First of all I'm only doing 16 bit 44.1 on a 4 gig card and I reformat my card before each show.

The first set on Friday was 1.06 gigs. After the set ended I save the file, shut down and restarte to reboot the firmware, and fired right up so I could not worry about when the 2nd set was going to start. It recorded about 50 minutes before the set started and the whole second set, but it stopped right before the encore at 1.54 gigs :Huh?

On Saturday there were 3 sets and I was putting much less lead time before each of them. The first one came in at 870 MB, the 2nd one was 546MB, and when I started up for the 3rd set the time remaing meter said I had 1:53 left. I knew if that held true I was going to get screwed. Sure enough during the encore it stopped when it hit the 1:53 mark saying "media full" which was 1.15 gigs. That was less than 3 gigs total!!!!! I should have had plenty of time left. In retrospect I should have saved the file during the encore break an started a new one, but it doesn't make any sense why it was stopping. 

[rodeen]

Which version of the firmware were you using??