Topic: M-Audio MicroTrack 2496 - *actual* real-life experiences thread

[jcrab66]

Here's a picture my wife took (maintaining my anonymity):

either you have really big hands or that thing is much smaller than i thought it was......

[WiFiJeff]

One thing that could account for reduced battery time could be the use of high speed CF cards which I have not seen discussed.  In the R1, and I am making an assumption that it will be similar in the MicroTrack, regular speed, or even low speed CF cards are used and get significantly better battery time than SanDisk Extreme CF cards.

I've been using the Sandisk 2 GB and 8 GB Ultra II normal cards, not the Extreme.  I have a Lexar 4 GB 80x card, which gave slightly less good battery times in the R1, but I haven't used that in the MT yet.

Jeff

[WiFiJeff]

Here's a picture my wife took (maintaining my anonymity):

either you have really big hands or that thing is much smaller than i thought it was......

My hands are TINY.  The MT is MICROSCOPIC.  When the bugs are out it will be great.

Jeff

[WiFiJeff]

I got an email confirm from another user that the MT does lock up and require a reboot when you try to do SPDIF 24/96 in, so this is not just my cluelessness.  He also reports that while it seems to record SPDIF in at 24/48, the resulting file is labeled 16 bit.  No idea of what it sounds like.  I am not going to do anymore digital-in testing, since this feature is absolutely in need of a fix and the experimentation should be done with the fixed firmware. 

Jeff

[nic]

a little confusion from earlier posts...

when locking into a incoming s/pdif signal, you shouldnt be able to set the sample rate or the bit depth as that info is contained in the signal stream.
only when recording from a analog source do you have the ability to set bit depth and sample rate.

[wbrisette]

i dont say it going to be the main one , but some times i need more tracks ,and i prefer for this small unit go digi in
not to say that sometimes i do fx or small budgets  while my 744 making money on the side , was thinking to have "dv" recorder :-)
  about the sanosax , few shekels more and i buy deva4 while my 744 becomes a back up:-)

Oleg! Welcome to the TS section.

(For those who don't know Oleg, he is a regular on RAMPS, while I'm mostly a lurker there).

I always knew you have Deva envy. 


Wayne

[WiFiJeff]

a little confusion from earlier posts...

when locking into a incoming s/pdif signal, you shouldnt be able to set the sample rate or the bit depth as that info is contained in the signal stream.
only when recording from a analog source do you have the ability to set bit depth and sample rate.

Agreed.  When you choose SPDIF the sample rate showing in the menu is "automatic" as one would expect.  But the bit depth shows as "16" NOT "automatic" and putting in a 24/96 signal causes the machine to lock up and hang, showing either a saving file or a deleting file message forwever or until you reboot it.  Perhaps a 16 bit 44.1 signal will record, but I bought this machine to do 24/96 and with the current firmware it doesn't. 

I expect that this issue will be ressolved with new firmware, the battery issue is an iffier one I think.  I have been running a couple of hours this morning with lithium AAs in the USB power box, and the battery meter when I disconnect the box shows full charge, so I think this will be okay, I'll know more in the afternoon.  Then I can see if the sound quality is any good!

Jeff

[udovdh]

I got an email confirm from another user that the MT does lock up and require a reboot when you try to do SPDIF 24/96 in, so this is not just my cluelessness.  He also reports that while it seems to record SPDIF in at 24/48, the resulting file is labeled 16 bit.  No idea of what it sounds like.  I am not going to do anymore digital-in testing, since this feature is absolutely in need of a fix and the experimentation should be done with the fixed firmware. 

For a device named Microtrack 2496 how did this escape testing!? 

[noahbickart]

One, albeit clumsy, way of assuring long battery life would be to use a usb car charger see (http://www.boxwave.com/products/carcharger/) and run it into a 12 v sla. If one were running a 12 volt for a V3 or a MME anyway, this wouldn't be so bad.

It would be a huge environmental and financial waste to blow through 4 lithium AAs every show.

-Noah
 

[WiFiJeff]

I would be a huge environmental and financial waste to blow through 4 lithium AAs every show.

-Noah
 

I will try out the MyPower lithium rechargeable from Tekkeon as well, they have a USB out that should work (if I can figure out the polarity without frying the MT!).  But it a hell of a lot larger than the 4 AA box.  On the financial side, there is a web site that has generic lithium AAs (made by the same plant in China as the Energizers, I think) for $1.  Also, my hope is that I'll be getting way over 8 hours with this, and thus be able to get two or three concerts with it.  The alternative is rechargeable alkaliines, there is a new device that will recharge ordinary alks as well, reported to restore them to original vigor:

http://www.the-gadgeteer.com/review/battery_xtender_alkaline_battery_recharger

Jeff

[BayTaynt3d]

I got an email confirm from another user that the MT does lock up and require a reboot when you try to do SPDIF 24/96 in, so this is not just my cluelessness.  He also reports that while it seems to record SPDIF in at 24/48, the resulting file is labeled 16 bit.  No idea of what it sounds like.  I am not going to do anymore digital-in testing, since this feature is absolutely in need of a fix and the experimentation should be done with the fixed firmware. 

For a device named Microtrack 2496 how did this escape testing!? 

No doubt! The answer to that is clearly that they shipped anyway, despite the lockup problems. There's no way they didn't know about that bug considering that's the freakin' NAME of the product (like you said). Not that I personally care too much about 24/96 recording myself, but that seems kind of sleezy, and makes you wonder what other "known" problems are out there right now. Let's hope that firmware fix is REALLY just around the corner, if not...

[The Kilted Taper]

I got an email confirm from another user that the MT does lock up and require a reboot when you try to do SPDIF 24/96 in, so this is not just my cluelessness.  He also reports that while it seems to record SPDIF in at 24/48, the resulting file is labeled 16 bit.  No idea of what it sounds like.  I am not going to do anymore digital-in testing, since this feature is absolutely in need of a fix and the experimentation should be done with the fixed firmware. 

For a device named Microtrack 2496 how did this escape testing!? 

Just because it has issues taking a 24/96 signal, doesn't mean it can't do it's own sampling at that rate with an analog signal. 

[wbrisette]

Has anybody tried feeding this an AES signal yet? I'm curious if this is like the D8/D7 and thinks the signal is some copy protected signal.

Wayne

[jason]

I wonder if this battery pack would be a good alternative. Its pricey, but rechargable and 4.4 AH @ 5v... 

http://www.socketcom.com/product/AC4009-541.asp

But I don't see a real problem with 5hr run times, as its not a big deal to have extra AA's on hand to switch up at festivals, and other than Big Cypress, I can't remember the last time I taped a set >5hrs.

[udovdh]

I sent M-Audio support something like:

Why, in the 21st century, does a device power down when new media is
inserted?
The device *does* detect that new media is present, so why not act
accordingly? We live in a Plug and Play era, not the 1995 version but
the 2005 version.

With the device slowly getting available and news/info spreading I start
to worry. The L/M/H issue, the battery life, the power down when CF is
inserted (combined with the slowish startup timings), etc, etc.
This may look like peanuts to you but it gives and indication of
quality, both of the design and testing procedures.

Please improve whatever you can on this device!


As a reply I got (from an American person):

I have forwarded your comments to the top of the company, thanks for your
feedback.

Hopefully we will be able to fix some of the issues you mentioned in a
forthcoming firmware update, which will be available from our website soon.



(sounds good but nothing set in stone yet)