Topic: Microtracker Firmware Update v1.1.5 Beta 10/7/05

[cmoorevt]

Just came out.  Beta version.


http://m-audio.com/index.php?do=support.drivers

Changes from v1.0.2 to v1.1.5:

General Fixes:
   - Fixed the behavior of the L/M/H switch (L and H were reversed)
   - Fixed a problem with the File menu (recorded files would not play from
     the Files menu until the machine was rebooted)
   - Fixed problem where "no media found" message didn't always show
   - Adjusted screen contrast range

Fixing Meters:
   - Fixed battery meter (if full and the external power was removed,
     the level dropped approximately 5-10%)
   - Fixed level meter length (the bar of the level meter maxed out
     about 8 pixels shy of the end of the track, so it appeared that
     the unit had headroom left, even though it was clipping)

Fixing Pops:
   - Eliminated pop noises on boot-up
   - Eliminated static noises at the end of tracks

New Items:
   - S/PDIF is enhanced to 24-bit/48kHz, and is more reliable
   - Spanish language added

<edit> fixed to show all the changes.  thanks tonyvt. </edit>

[BC]

damn, no fix for 24 bit on SPDIF in? 

[tonyvt]

It does appear there is a 24 bit SPDIF Fix. See below.

Changes from v1.0.2 to v1.1.5:

General Fixes:
   - Fixed the behavior of the L/M/H switch (L and H were reversed)
   - Fixed a problem with the File menu (recorded files would not play from
     the Files menu until the machine was rebooted)
   - Fixed problem where "no media found" message didn't always show
   - Adjusted screen contrast range

Fixing Meters:
   - Fixed battery meter (if full and the external power was removed,
     the level dropped approximately 5-10%)
   - Fixed level meter length (the bar of the level meter maxed out
     about 8 pixels shy of the end of the track, so it appeared that
     the unit had headroom left, even though it was clipping)

Fixing Pops:
   - Eliminated pop noises on boot-up
   - Eliminated static noises at the end of tracks

New Items:
   - S/PDIF is enhanced to 24-bit/48kHz, and is more reliable
   - Spanish language added

[cmoorevt]

Thanks dude.  First post has been updated.

It does appear there is a 24 bit SPDIF Fix. See below.

Changes from v1.0.2 to v1.1.5:

General Fixes:
   - Fixed the behavior of the L/M/H switch (L and H were reversed)
   - Fixed a problem with the File menu (recorded files would not play from
     the Files menu until the machine was rebooted)
   - Fixed problem where "no media found" message didn't always show
   - Adjusted screen contrast range

Fixing Meters:
   - Fixed battery meter (if full and the external power was removed,
     the level dropped approximately 5-10%)
   - Fixed level meter length (the bar of the level meter maxed out
     about 8 pixels shy of the end of the track, so it appeared that
     the unit had headroom left, even though it was clipping)

Fixing Pops:
   - Eliminated pop noises on boot-up
   - Eliminated static noises at the end of tracks

New Items:
   - S/PDIF is enhanced to 24-bit/48kHz, and is more reliable
   - Spanish language added

[tonyvt]

No problems with the update here using OS X 10.3.9.

I do seem to be unable to power my MBHO 603's with the built in phantom power.
I connected my sonosax to supply phantom to the MBHO's was then able to get levels using the 1/4" ins.

[neutrino]

couple initial items:
-filenumbering seems to get reset
-meters seem to have more "flashing" than i remember previously...i'm currently using the 1/8" mic input and the lights and peak indicators seem to be working correctly, but there are intermittent complete flashes across the entire meter....esp on the right channel..does not seem to be related to the input signal

since this is beta firmware, its probably worth people using it giving feedback to m-audio
http://m-audio.com/index.php?do=support.betaform

boogie

My file numbering has picked up where it left off. No renumbering here. "Audio Scrub" is now in the menu as well, as if that was a concern to anyone. I wish they would have given us meters on playback, but the 2gig file split is my main concern right now.
dB-

[Rick]

S/PDIF is enhanced to 24-bit/48kHz, and is more reliable

I'm not sure that means fixed... some needs to test this. and what about 24/96? Though 24/48 would be fine with me if it works.

[udovdh]

some quick tests with the L/M/H switch

doesnt appear that the "M" postion is any different from the "H" position when recording from 1/8" input

the "L" position does appear to be about 6dB less gain

On 1/8"?

I guess L/M/H interacts with the attenuator resistors attached to the ADC.

BTW: updated here.
1.00 stays on bootup, must be the PCB revision?

[pietje]

It does appear there is a 24 bit SPDIF Fix. See below.

Changes from v1.0.2 to v1.1.5:
....
New Items:
   - S/PDIF is enhanced to 24-bit/48kHz, and is more reliable
   - Spanish language added

Menu item to set day and time, so files get the correct date/time.

[SonicSound]

I hope this not the last upgrade for the year!

[JasonSobel]

S/PDIF is enhanced to 24-bit/48kHz, and is more reliable

I'm not sure that means fixed... some needs to test this. and what about 24/96? Though 24/48 would be fine with me if it works.

the 24 bit S/PDIF input is the first thing I'm going to test.  I also want 24/96 via S/PDIF, but honestly, until I get an 8gig CF card, I'll be running 24/48 anyway.  So I'll give M-Audio a little leeway there, until the price on CF cards drops to a reasonable level

[it-goes-to-eleven]

Good news.. I think we now have real 'line in' mode on the 1/8" input!

Someone has already posted some noise floor charts which suggest the 1/8" input is more quiet than the 1/4, so I'd guess that us mini-mic users will want to use it where possible. Of course, not all units may perform the same and noise floor doesn't predict which *sounds* better.

I'm going to try and do a couple quick gain measurements this morning.  I have a show tonight and I hope to run 4061>MT as a backup.

[udovdh]

Good news.. I think we now have real 'line in' mode on the 1/8" input!

Someone has already posted some noise floor charts which suggest the 1/8" input is more quiet than the 1/4, so I'd guess that us mini-mic users will want to use it where possible. Of course, not all units may perform the same and noise floor doesn't predict which *sounds* better.
I'm going to try and do a couple quick gain measurements this morning. 

Cool! Info on how the 1/8" line in compares to the Sony D100/M1 line in would be welcome.

So this leaves the 5V on the 1/8"...
Is it also on in L mode? Or just in M/H mode?

[it-goes-to-eleven]

Okay, tests complete. As updated in this thread: http://taperssection.com/index.php?topic=51534.0

The 1/8" still does not support line mode

                  gain
              min      max
              ---      ---
1/4 line in   +14      +26
1/8 Line in   +29      +41
1/8 M         +41      +49

[sleepypedro]

Just came out.  Beta version.

New Items:
   - Spanish language added

por fin puedo usar el microtracker!  ay, dios mio!

[udovdh]

Okay, tests complete. As updated in this thread: http://taperssection.com/index.php?topic=51534.0

The 1/8" still does not support line mode

                  gain
              min      max
              ---      ---
1/4 line in   +14      +26
1/8 Line in   +29      +41
1/8 M         +41      +49

Ah, so there is a difference in L and M modes for 1/8" input but not as required for real line level operation.

[BayTaynt3d]

doesnt appear that the "M" postion is any different from the "H" position when recording from 1/8" input

I believe that is clearly stated in the manual to be that way. Not sure though...

[Kevinlane]

doesnt appear that the "M" postion is any different from the "H" position when recording from 1/8" input

I believe that is clearly stated in the manual to be that way. Not sure though...

yes it is stated in the manual.

[BC]

the 24 bit S/PDIF input is the first thing I'm going to test. 

How'd it work?

[JasonSobel]

the 24 bit S/PDIF input is the first thing I'm going to test. 

How'd it work?

24/96 doesn't work at all.  but then, the firmware update text says that S/PDIF has been improved to 24/48.

24/48 S/PDIF seems to work great.  I recorded a few 5 minute files, then transferred them to my computer to take a look.  they open up in Cool Edit 2000 just fine, as 24 bit files

I am now about an hour into my test to see what happens when it hits 2 gigs.  about another hour to go to see what happens.  here's a funny thing though.  I am using a Sandisk 4 GB card.  freshly formatted.  when running at 24/48 with the S/PDIF input, and recording a file, the "time left" at the start of my test was just under 2 hours, or what the total recording time of the card would be running at 24/96.  with a 4 gig card, I should get close to 4 hours of recording at 24/48.  maybe it just knows that this is when it will hit the 2 gig limit.  I'll post again when this test is done.

and as far as general stability goes with the S/PDIF input, it appears to be much better.  hasn't frozen up on me yet.  even when sending it a 24/96 signal, the unit won't record it, but if I hit the "record" button a 2nd time, it goes into the "writing file" routine, and I then have a 24/96 file that is 0 seconds long and something like 5kb in size.  but then I can go do other stuff on the unit.  So while it won't record a 24/96 S/PDIF signal, the unit won't completely lock up either.

one other thing, based on my earlier test of the S/PDIF input (with the old firmware, and at 16 bit), and I am assuming that it is bit-accurate.  in the short 5 minute 24/48 samples that I did, there weren't any noticeable spikes or clicks, but that doesn't necessarily mean that it's bit-accurate.  I guess I should record some 24/48 data into the MicroTrack and also into my computer (via EgoSys Waveterminal 24/96 soundcard), and then compare the files.  that will tell us if it's bit-accurate at 24 bit or not.  however, I don't think that I'll have time to do that test today.  hopefully tomorrow.

other things that I've noticed with the new firmware.  start recording a file, engage the hold switch.  and then press and hold the power button.  my unit still turns off.  M-Audio said that they fixed that with this firmware, but I don't think they got it right yet.  however, that seems to be a bigger concern for other folks, but I'm not really worried about it.  on the other hand, I never plan on using the analog inputs and I rarely stealth any shows.

[JasonSobel]

ok, my 2 hour test is complete.  when recording at 24/48 via the S/PDIF input, it hit the 2 gig limit and displayed this message: "media full"  but because I was using a 4 gig card, the media was obviously not full.  I could start another 24/48 recording, and again, it told me I had just under 2 hours (another 2 gigs to use).  I then recorded 4 or 5 more, short (i.e. 1 to 2 minute) files, just to play around.  all the files transferred and opened in Cool Edit 200 with no problems.  nothing got corrupted when it hit 2 GB, just that the recording stopped.

another test I did was use a stopwatch and time how long it would take for me to stop/save a file, and start a new recording.  about 10 seconds.  with this firmware, I have two issues:

• no autostart of new file at 2 gig limit
• no 24/96 S/PDIF input

but really, at this point, I'm happy recording at 24/48 (until I get an 8 gig CF card), so the 24/96 S/PDIF is a lower priority for me.  but the 2 gig limit thing, that is HIGH priority for me.

if this firmware actually is as stable as it seems to me right now (no freezes yet), then I am ready to use my D8 not for a full back-up, but only sparingly.  basically, my idea, so I don't have to buy any more blank DATs, is to record at 24/48, and watch for when it gets close to 2 gigs (2 hours).  many times, a set is shorter than 2 hours, so it won't be an issue at all.  however, there are also many times when a set will go longer than 2 hours.  I'll get the DAT rolling just before I stop/save the MicroTrack recording, and then stop the DAT recording again after a new file is being recorded with the MicroTrack.  that way, I'll just have to splice in the 10 seconds or so from the DAT.  not ideal, I know, but until M-Audio can get a work-around for the 2gig limit, it seems to me a good option.   also, the 2 gig issue seems to me a bigger issue when recording 24/96, because then you've only got an hour of straight time before you hit 2 gigs.

they are getting closer, but not quite there yet.

[sygdwm]

good info jason. +t. have you tried or can you manually start a new file before it hits 2gb limit? or does it have to be stopped/saved?

another test I did was use a stopwatch and time how long it would take for me to stop/save a file, and start a new recording.  about 10 seconds.

[JasonSobel]

good info jason. +t. have you tried or can you manually start a new file before it hits 2gb limit? or does it have to be stopped/saved?

another test I did was use a stopwatch and time how long it would take for me to stop/save a file, and start a new recording.  about 10 seconds.

with this firmware, you cannot start recording a new file until after the last one is stopped/saved.  you press the record button again to stop/save the file, and then it creates the file.  then you can press record again to start a new file.  as mentioned above, this process is takes approx. 10 seconds.

[BC]

great info Jason, thanks for running these tests and sharing the info with us!

+t in 12.

[onebear]

Thanks for the info much appreciated

[Simp-Dawg]

my rec time available now shows only 3:01:59 with a freshly formatted 4gb card...that's not right.  it didn't do that before the firmware upgrade.

[jbraveman]

my rec time available now shows only 3:01:59 with a freshly formatted 4gb card...that's not right.  it didn't do that before the firmware upgrade.

It seems like it calculates available time based on the 2g fiile limit and not the total available on the card.  In some ways, that's more relevant information since the recording will stop at that point anyway.

[JasonSobel]

my rec time available now shows only 3:01:59 with a freshly formatted 4gb card...that's not right.  it didn't do that before the firmware upgrade.

It seems like it calculates available time based on the 2g fiile limit and not the total available on the card.  In some ways, that's more relevant information since the recording will stop at that point anyway.

yes, that is exactly what it does for me.  gives me the available time up to the 2 gig limit.  but this requires a little more effort on the part of the user, because you need to keep track on your own how much space is actually on your card.

[Todd R]

Great info, Jason, thanks!

Hopefully it will still test out to be bit-perfect on spdif in with this latest firmware.

[BLOODYJACK]

I was under the impression that the 1/8th inch jack was consumer line in and the 1/4" was pro-line in
I would also guess that firmware canot change the gain structure.

[John Kelly]

Great info, Jason, thanks!

Hopefully it will still test out to be bit-perfect on spdif in with this latest firmware.

Why would a firmware update change that? 

[Todd R]

I wouldn't think that it would, but it seems prudent to actually test it.

[F.O.Bean]

i would love to get one of these, but until they fix the 2gb file spilt problem, i wont be

wonder if they'll get to that this year?

the pmd671 is looking better and better

anybody have an estimate how long the MT took to transfer thru usb 2.0 to a HD/OTG drive what about usb 2.0 CF card reader>OTG drive times

[eric.B]

i would love to get one of these, but until they fix the 2gb file spilt problem, i wont be

wonder if they'll get to that this year?

the pmd671 is looking better and better

anybody have an estimate how long the MT took to transfer thru usb 2.0 to a HD/OTG drive what about usb 2.0 CF card reader>OTG drive times

dunno..  but 2 gigs at 24/48 over usb 1(no card reader, MT hooked directly to usb on computer) took about 45 minutes..   

[F.O.Bean]

i would love to get one of these, but until they fix the 2gb file spilt problem, i wont be

wonder if they'll get to that this year?

the pmd671 is looking better and better

anybody have an estimate how long the MT took to transfer thru usb 2.0 to a HD/OTG drive what about usb 2.0 CF card reader>OTG drive times

dunno..  but 2 gigs at 24/48 over usb 1(no card reader, MT hooked directly to usb on computer) took about 45 minutes..   

wow, i thought someone told me it took that long i was hoping i heard wrong info

so what is one top do at festies gotta have 2 4gb cards, which isnt that bad, still only 750 for the whole setup

wonder how long the pmd-671 takes

[John Kelly]

i would love to get one of these, but until they fix the 2gb file spilt problem, i wont be

wonder if they'll get to that this year?

the pmd671 is looking better and better

anybody have an estimate how long the MT took to transfer thru usb 2.0 to a HD/OTG drive what about usb 2.0 CF card reader>OTG drive times

dunno..  but 2 gigs at 24/48 over usb 1(no card reader, MT hooked directly to usb on computer) took about 45 minutes..   

wow, i thought someone told me it took that long i was hoping i heard wrong info

so what is one top do at festies gotta have 2 4gb cards, which isnt that bad, still only 750 for the whole setup

wonder how long the pmd-671 takes

Bean he said that was USB1.

And if previous M-Audio driver releases are any indication, we should see constant updates to this thing until it's completely rock solid.  When I owned a Firewire 410 they probably averaged at least one update per month.

[JasonSobel]

via a USB2 card reader, 2 gigs took me about 15 minutes to transfer to my computer.

[Steelcorner27]

USB 1.0 - 1.64GB - 34 minutes for me

Brad

[BLOODYJACK]

from talking to the m-audio guys at the show they do not have any plans to fix the 2gig thing they think its fine and not a bug at all.
Mind you they were sales guys

[silentmark]

via a USB2 card reader, 2 gigs took me about 15 minutes to transfer to my computer.

Well I used a card reader over USB2.0 and 2gigs took about 35 minutes to transfer.

[John Kelly]

via a USB2 card reader, 2 gigs took me about 15 minutes to transfer to my computer.

Well I used a card reader over USB2.0 and 2gigs took about 35 minutes to transfer.

Are you sure the card reader was rated for USB2?

[F.O.Bean]

thanks guys!

keep em coming

[pfife]

Isn't the speed of the card going to make a big difference as far as uploading speed goes?

[it-goes-to-eleven]

I don't think it will in these cases.  The recorders just aren't optimized to read the cards quickly like cameras are.

[pfife]

I don't think it will in these cases.  The recorders just aren't optimized to read the cards quickly like cameras are.

Would it for card readers though?

[it-goes-to-eleven]

Good cardreaders should be fast and the card speed more of a factor.

[silentmark]

via a USB2 card reader, 2 gigs took me about 15 minutes to transfer to my computer.

Well I used a card reader over USB2.0 and 2gigs took about 35 minutes to transfer.

Are you sure the card reader was rated for USB2?

When I bought it, it said USB2.0, so I would hope so. Here is the one I have: ImageMate cf reader sddr-92, as far as I can tell it is USB2.0

[L Ron Hoover]

Would the hardware in your computer have any effect on transfer speeds?

[F.O.Bean]

as a more portable solution, id also ove to know how the usb 2.0 card readers pair w/ the OTG drives as well

[scb]

can this thing record to split mono files instead of a stereo file?  then 2 gigs per file would actually be 4 gigs

maybe something to request in a future update if they won't do an autosplit?

[udovdh]

from talking to the m-audio guys at the show they do not have any plans to fix the 2gig thing they think its fine and not a bug at all.
Mind you they were sales guys

Even then.
They don't know their market and the 2496 implications.
Its is a BIG BUG! It's a sign of very simple implementation.
(devices like the Archos Gmini have the same issues at 2G, they did not stop but crashed more or less, corrupting teh filesystem and the recorded file; so the MT is a small step ahead.. wow)

[slowburn]

good info jason. +t. have you tried or can you manually start a new file before it hits 2gb limit? or does it have to be stopped/saved?

another test I did was use a stopwatch and time how long it would take for me to stop/save a file, and start a new recording.  about 10 seconds.

with this firmware, you cannot start recording a new file until after the last one is stopped/saved.  you press the record button again to stop/save the file, and then it creates the file.  then you can press record again to start a new file.  as mentioned above, this process is takes approx. 10 seconds.

Do I actually have to wait for it to be saved before I can press record again or can I press record twice quickly and it would then "remember" to start recording again? Will be important for stealth situations

[JasonSobel]

good info jason. +t. have you tried or can you manually start a new file before it hits 2gb limit? or does it have to be stopped/saved?

another test I did was use a stopwatch and time how long it would take for me to stop/save a file, and start a new recording.  about 10 seconds.

with this firmware, you cannot start recording a new file until after the last one is stopped/saved.  you press the record button again to stop/save the file, and then it creates the file.  then you can press record again to start a new file.  as mentioned above, this process is takes approx. 10 seconds.

Do I actually have to wait for it to be saved before I can press record again or can I press record twice quickly and it would then "remember" to start recording again? Will be important for stealth situations

good question.  when I get home from work today, I'll test that out.  It won't be until 7 or 8 pm tonight though, so maybe someone else can test this during the day.

[it-goes-to-eleven]

can this thing record to split mono files instead of a stereo file?  then 2 gigs per file would actually be 4 gigs

That would be an excellent work-around, Scott!

I have to make a call to them about some issues and I'm going to try and push some of this stuff hard.

[cmoorevt]

good question.  when I get home from work today, I'll test that out.  It won't be until 7 or 8 pm tonight though, so maybe someone else can test this during the day.

I just tried this.  You do NOT have to wait for it to be saved to begin the second recording.

As my file was recording, I hit the REC button twice quickly.  The unit stopped the first recording, saved it, and then immediately started recording again.  Took about 5 seconds to do everything after I hit the REC button twice.   I would suppose for stealth situations, when we get near the 2gb limit, hit REC REC and start the second file.  Certainly faster than swapping dat tapes, but the auto split would still be ideal.

FWIW, I tried this with both the 1/4 inch inputs and the SPDIF in. 

[Ed.]

?

alright, just to get this clear, when you get close to the 2gig limit, you can just hit record twice and it'll start a new file and save your old one?

well, i guess its time for me to get one of these.



edit: fat fingers

[rdvdijk]

I just tried this.  You do NOT have to wait for it to be saved to begin the second recording.

That's cool. Does the saving process take longer when the file gets bigger?

Also: how much time is missed exactly during this 'tape flip' ?

Roel

[cmoorevt]

Ed.-Yes.  Exactly.  Hit REC twice, it stops the first recording, saves it and automatically starts the second recording.

rdvdijk-The "tape flip"  took a total of five seconds.  However, you bring up a good point about the length of the file.  I only ran about a minute of signal for my first file before I tried this.  Perhaps it will take longer with a larger file.   I have to leave for the day, so hopefully someone else can give it a try, or I can try again tonight.

[Ed.]

+t for the great news...

its still not exactly perfect, but it keeps getting closer for my needs.

[udovdh]

rdvdijk-The "tape flip"  took a total of five seconds.  However, you bring up a good point about the length of the file.  I only ran about a minute of signal for my first file before I tried this.  Perhaps it will take longer with a larger file.   I have to leave for the day, so hopefully someone else can give it a try, or I can try again tonight.

Just run the MT at 24/96 and buffers (if at all..., how much total RAM does the MT have? 16Megs? 8?) will be full within half a minute if they were 16 megs big (which I doubt).

[spyder9]

from talking to the m-audio guys at the show they do not have any plans to fix the 2gig thing they think its fine and not a bug at all.
Mind you they were sales guys

Sales guys don't know sh*t.  They can't think on their own.  They get told what to say by the techies for those shows.

[svenkid]

so I downloaded the update, now what? usb into the computerto the mt and click?

[eric.B]

so I downloaded the update, now what? usb into the computerto the mt and click?

the instructions for adding the firmware are on the site where you downloaded it..

[John Kelly]

so I downloaded the update, now what? usb into the computerto the mt and click?

the instructions for adding the firmware are on the site where you downloaded it..

And in the file you downloaded as well.

[Steelcorner27]

Ed.-Yes.  Exactly.  Hit REC twice, it stops the first recording, saves it and automatically starts the second recording.

rdvdijk-The "tape flip"  took a total of five seconds.  However, you bring up a good point about the length of the file.  I only ran about a minute of signal for my first file before I tried this.  Perhaps it will take longer with a larger file.   I have to leave for the day, so hopefully someone else can give it a try, or I can try again tonight.

Seems to me that my 1.6 GB file took only about 1\2 sec to save..at least thats how long the message was up for  the actual wording escapes me right now.

Brad

[F.O.Bean]

Ed.-Yes.  Exactly.  Hit REC twice, it stops the first recording, saves it and automatically starts the second recording.

rdvdijk-The "tape flip"  took a total of five seconds.  However, you bring up a good point about the length of the file.  I only ran about a minute of signal for my first file before I tried this.  Perhaps it will take longer with a larger file.   I have to leave for the day, so hopefully someone else can give it a try, or I can try again tonight.

Seems to me that my 1.6 GB file took only about 1\2 sec to save..at least thats how long the message was up for  the actual wording escapes me right now.

Brad

and it only took about 5 seconds? I'm still not too fond of the whole 'tape flip' thing anymore, thats why I moved to DAT/Digital anyway

[JasonSobel]

in a reply from the M-Audio tech support email:

Jason,

Thank you very much for your feedback! We are working towards a solution to both issues you mentioned (S/PDIF at higher sample rates / eliminate 2 GB file size limit) and you should see an improvement in a future firmware update.

Thank you again for your feedback and best regards,
 

Roland
M-Audio Tech Support

FYI, the only "issues" I asked them about was S/PDIF recording at 24/96 and a work-around for the 2 gig file size limit.  I asked them nothing about analog inputs or battery life.

while it's the same thing they've said all along, (i.e. "it's coming in a future update"), it is somewhat reassuring to know that they are aware of the issues.

hopefully we'll see these sooner rather than later.

[cmoorevt]

Seems to me that my 1.6 GB file took only about 1\2 sec to save..at least thats how long the message was up for  the actual wording escapes me right now.

Brad

Sweet. So it looks like it probably works with larger files as well.


I also received an email from M-Audio today.  Roland must have been busy.

"We are actively working towards a solution for the 2 GB file size limit. You should see an improvement in a future firmware update. "

[neutrino]

"We are also looking into various possibilities to overcome the 2 GB file size limit as this is a very popular request. An automatic stop- / restart recording function is one of the options that is being looked at."  -Roland

Poor Roland.

Let's give him HELL!

[F.O.Bean]

is roland from M-Audio or from the actual Roland company sorry, I honestly have no clue?

[Sebastian]

here's what I got from him:

Sebastian,

 

Thank you for your feedback! The problem you are describing (level meters
never peak but LEDs do) was a known issue with the firmware version the
MicroTrack 24/96 shipped with, but this should be resolved after updating
the MicroTrack 24/96 firmware to version 1.1.5. From the Main Menu of the
MicroTrack, select System and then Version. If the Version number shown here
is not 1.1.5 then the firmware update wasn't yet successfully applied.

Thank you for your suggestion to label the meters according to the dB levels
and the comment about the lagging level meters. I will pass this on to our
engineering department. We are currently running additional tests regarding
the average battery life since we received a couple similar reports when it
comes to this.

 

We are actively working towards a solution for the 2 GB file size limit.
There are also plans for an improvement regarding the labeling of the
recorded files

You should see these improvements in a future firmware update.

Roland
M-Audio Tech Support

[F.O.Bean]

here's what I got from him:

Sebastian,

 

Thank you for your feedback! The problem you are describing (level meters
never peak but LEDs do) was a known issue with the firmware version the
MicroTrack 24/96 shipped with, but this should be resolved after updating
the MicroTrack 24/96 firmware to version 1.1.5. From the Main Menu of the
MicroTrack, select System and then Version. If the Version number shown here
is not 1.1.5 then the firmware update wasn't yet successfully applied.

Thank you for your suggestion to label the meters according to the dB levels
and the comment about the lagging level meters. I will pass this on to our
engineering department. We are currently running additional tests regarding
the average battery life since we received a couple similar reports when it
comes to this.

 

We are actively working towards a solution for the 2 GB file size limit.
There are also plans for an improvement regarding the labeling of the
recorded files

You should see these improvements in a future firmware update.

Roland
M-Audio Tech Support

+T man, I'm gonna let ya'll test these out until springtime, and then if theyre stable enuf, which they sound serious enough in fixing the issues, i'm gonna grab one of these and two 4GB flash cards

[udovdh]

and it only took about 5 seconds? I'm still not too fond of the whole 'tape flip' thing anymore, thats why I moved to DAT/Digital anyway

That's true but it appears to be quite reliable, 5 seconds and a new file is open.
Until the real 2GB auto-open fix this is OK.

[F.O.Bean]

and it only took about 5 seconds? I'm still not too fond of the whole 'tape flip' thing anymore, thats why I moved to DAT/Digital anyway

That's true but it appears to be quite reliable, 5 seconds and a new file is open.
Until the real 2GB auto-open fix this is OK.

very true, im sure id make due

maybe i will get one sooner then!

[sunrisemusic]

via a USB2 card reader, 2 gigs took me about 15 minutes to transfer to my computer.

Well I used a card reader over USB2.0 and 2gigs took about 35 minutes to transfer.

Even if the card reader is USB2.0, what speed is your card?  Surely a faster speed card = faster transfer rates.  When I called M-Audio after first getting the MT and asked them what speed card to get they said "faster is better", (though there seems to be differing opinions here about whether or not faster cards would affect battery life). 

(BTW I haven't got a card yet, still using the stock card, running mp3 files for rehearsals and rough recordings of some of my little dinky gigs, though I will need something bigger within about a month for some stuff I want to do.)

[silentmark]

Nice, now if we can get the meters issues squared away, yah mon 

[cmoorevt]

Nice, now if we can get the meters issues squared away, yah mon 

I had an email response from Roland the other day in which he said he would pass along the metering issues (lack of numbers on the meters, meters freezing at around the 20-30 minute mark) to the engineering department.  At the very least they know about it and if enough people kindly point out that there is a problem, they seem to take things seriously-see the 2gb issue.

[F.O.Bean]

great customer support

Im torn between this thing and the pmd-671

the pmd-671 can be used as an all-in-one w/ the ACM mod but is def more pricey than these

or I can get the MT and 2 (4) GB cards for about 750, w/ a battery setup already ready to go taboot!

[zowie]

It's kind of amusing that M-Audio's rep is named Roland.

[Fatah Ruark (aka MIKE B)]

It's kind of amusing that M-Audio's rep is named Roland.

Yeah thats what I was thinking. I guess it could be worse. I wouldn't want to be named Yamaha or Tascam.

[bagtagsell]

I got a similar response.  Stating they will have another new firmware out soon and the 2gb file split is a top priority. 

[Ed.]

bean, i'm with you on the decision between this and the 671...only i figure i'll never trade in my v3, so i'll really only need the 671 to record.

i think right now i'm leaning toward the mt more so...i think the future updates will bring it up to par, and i think it'll be a pretty solid 24bit recorder, at least as solid as the jb3 is a 16bit recorder.  plus powering it seems pretty simple.

[silentmark]

Nice, now if we can get the meters issues squared away, yah mon 

I had an email response from Roland the other day in which he said he would pass along the metering issues (lack of numbers on the meters, meters freezing at around the 20-30 minute mark) to the engineering department.  At the very least they know about it and if enough people kindly point out that there is a problem, they seem to take things seriously-see the 2gb issue.

I just filled out the support form on the beta driver page at their website describing what I was seeing with the meters. This inverse meter bug I think is caused by the new firmware as it didn't do it before ... First field 24 bit run to happen on Friday for My Morning Jacket at the TLA, Philly, gonna run AKG568's>V3>MT, yeah busting out the shotguns 

[clarson]

via a USB2 card reader, 2 gigs took me about 15 minutes to transfer to my computer.

Well I used a card reader over USB2.0 and 2gigs took about 35 minutes to transfer.

Even if the card reader is USB2.0, what speed is your card?  Surely a faster speed card = faster transfer rates.  When I called M-Audio after first getting the MT and asked them what speed card to get they said "faster is better", (though there seems to be differing opinions here about whether or not faster cards would affect battery life). 

(BTW I haven't got a card yet, still using the stock card, running mp3 files for rehearsals and rough recordings of some of my little dinky gigs, though I will need something bigger within about a month for some stuff I want to do.)

I transfered about 2.5 gigs from the MT last night to the laptop and it only took 10 minutes with the a 4 gig microdrive card. Not bad at all! Beats the dat transfer!

[silentmark]

via a USB2 card reader, 2 gigs took me about 15 minutes to transfer to my computer.

Well I used a card reader over USB2.0 and 2gigs took about 35 minutes to transfer.

Even if the card reader is USB2.0, what speed is your card?  Surely a faster speed card = faster transfer rates.  When I called M-Audio after first getting the MT and asked them what speed card to get they said "faster is better", (though there seems to be differing opinions here about whether or not faster cards would affect battery life). 

(BTW I haven't got a card yet, still using the stock card, running mp3 files for rehearsals and rough recordings of some of my little dinky gigs, though I will need something bigger within about a month for some stuff I want to do.)

I transfered about 2.5 gigs from the MT last night to the laptop and it only took 10 minutes with the a 4 gig microdrive card. Not bad at all! Beats the dat transfer!

I used the Kingston 4gig one that Dell has been selling, so this must be the issue of transfer speed I have been getting ...

[jefflester]

It's kind of amusing that M-Audio's rep is named Roland.

Yeah thats what I was thinking. I guess it could be worse. I wouldn't want to be named Yamaha or Tascam.

Or Edirol. 

[sunrisemusic]

via a USB2 card reader, 2 gigs took me about 15 minutes to transfer to my computer.

Well I used a card reader over USB2.0 and 2gigs took about 35 minutes to transfer.

Even if the card reader is USB2.0, what speed is your card?  Surely a faster speed card = faster transfer rates.  When I called M-Audio after first getting the MT and asked them what speed card to get they said "faster is better", (though there seems to be differing opinions here about whether or not faster cards would affect battery life). 

(BTW I haven't got a card yet, still using the stock card, running mp3 files for rehearsals and rough recordings of some of my little dinky gigs, though I will need something bigger within about a month for some stuff I want to do.)

I transfered about 2.5 gigs from the MT last night to the laptop and it only took 10 minutes with the a 4 gig microdrive card. Not bad at all! Beats the dat transfer!

I used the Kingston 4gig one that Dell has been selling, so this must be the issue of transfer speed I have been getting ...

Microdrive is quicker than CF for transfers, right? Thanks for letting us know your cards (or microdrives). I'm curious as to what the card speed was in the original post

Anyone see any battery improvement with the new firmware? I haven't have a chance to use it yet.

[thegreatgumbino]

great customer support

Im torn between this thing and the pmd-671

the pmd-671 can be used as an all-in-one w/ the ACM mod but is def more pricey than these

or I can get the MT and 2 (4) GB cards for about 750, w/ a battery setup already ready to go taboot!

bean, i'm with you on the decision between this and the 671...only i figure i'll never trade in my v3, so i'll really only need the 671 to record.

i think right now i'm leaning toward the mt more so...i think the future updates will bring it up to par, and i think it'll be a pretty solid 24bit recorder, at least as solid as the jb3 is a 16bit recorder.  plus powering it seems pretty simple.

I hear you on this.  I can't see ditching my M148 > V3, unless the mod 671 ends up smoking the V3.  So, I'm looking for a 24 bit capture device. 

Additionally, someone raised the question with Doug as to whether or not he could do a PMD-660 mod to incorporate 24-bit capabilities.  Here's Doug's to whether or not a PMD-660 mod for 24-bit recording is in the works and if so when.

"That is at about one year off if it gets done. It will take a PCB and a firmware hack, time consuming work ! If the microtrackers digital noise audible i the analog circuit is not fixed, I will move forward with it, otherwise I will work out an analog upgrade for the M-Audio piece. I have looked inside it and daydreamed long enough to have a few good ideas....Doug"

Sounds like he's hoping to get a moded Microtracker out.  That could be sweet since it would probably be the cheapest 24 bit capture device available even with his mod. 

[silentmark]

Sounds like he's hoping to get a moded Microtracker out.  That could be sweet since it would probably be the cheapest 24 bit capture device available even with his mod. 

Yeah when I talked to him about the 671, R-1 & MT and how I was leaning towards the MT, he told me to wait a few months and he might have something up his sleeve  Needless to say I couldn't wait, heh ...

[mfoley]

Has anyone heard when there will be a "Mono" selectable parameter added to the firmware (#7 parameter record settings menu)  Currently in the manual it states "In a later version of firmware, this option will cause the MicroTrack 24/96 to only record one channel of audio instead of two"

[F.O.Bean]

Has anyone heard when there will be a "Mono" selectable parameter added to the firmware (#7 parameter record settings menu)  Currently in the manual it states "In a later version of firmware, this option will cause the MicroTrack 24/96 to only record one channel of audio instead of two"

just record the stereo signal and convert to mono in soundforge 7.0 or something similar

[mfoley]

I understand how to deal with the audio...that was not my question...   Once there is a mono parameter, record times should double....

[JasonSobel]

I understand how to deal with the audio...that was not my question...   Once there is a mono parameter, record times should double....

M-Audio has been saying all along that this feature will be coming in a firmware update.  Since most of us here record in stereo anyway, it is not a priority for most of us here.  Because of that, we haven't been pressing M-Audio for this feature, we don't really know if it's a priority for them or not, and we don't know if it'll be in the next firmware or somewhere further down the line.

You'd probably get a better response just asking M-Audio directly.

[JasonSobel]

the mono x2 would be something that could be used in lieu of the 2GB autosplit fix to 2X longer runtimes than would be possible with poly/stereo wav file...it would require later mixing to get the merged stereo wav, but you cut in half the number of times you need to force a stop/start when recording

while dual-mono would be nice, I'd say in addition to the 2GB autosplit feature, definitely not "in lieu" of.

at 24/96, 2 gigs is about an hour.  if you record it dual-mono (with two different files), you can get 2 hours at 24/96.  I know I routinely tape sets that are 2 and a half hours in length, and need something to be able to continuously record for that time.

So it'd be a nice feature, but we still need a 2GB autosave and seamlessly start a new file.