Taperssection.com
Gear / Technical Help => Recording Gear => Topic started by: gmm6797 on November 14, 2006, 12:26:45 AM
-
MAC: http://www.m-audio.com/index.php?do=support.drivers&f=761
PC: http://www.m-audio.com/index.php?do=support.drivers&f=762
Micro Track 2496
Version: 1.4.5
Release Date: November 13, 2006
Applies to:
MicroTrack 24/96
Operating System(s):
Windows 2000, Windows XP
Release Notes:
All this information is available inside a readme.txt included with the download.
Changes from v1.4.3 to v1.4.5:
- Increased data transfer speed when the MicroTrack is used as a card reader
- Fixed compatibility issue with some media (media would continually ask to be reformatted)
- Date fields would not flash when changing them in date menu. Fixed
- Playback meters would stick at about 80% on MP3 files after restarting MicroTrack. Fixed
- Right channel clip light would sometimes flash when recording a high level signal on the left channel. Fixed
- If a file was recorded and then deleted, the next file name would not be incremented. Fixed
- Corrected some incorrect German translation strings
- Loop mode now activates when you have held the menu button down for 2 seconds (it no longer waits for you to release the button to activate). Also, after activating loop mode, the next press of the menu button will place a small plus (+) sign on the left side of the loop mode icon. This signifies that a loop start point has been marked. Pressing the menu button one more time will place a small plus (+) sign to the right side of the loop mode icon to indicate that the loop end point has been placed. The MicroTrack will automatically start looping between these points. To stop looping and exit loop mode, press and hold the menu button again for 2 seconds.
- MicroTrack could freeze if the unit was powered on by plugging into the AC charger, left until fully charged at the screen with the AC power plug on it, and then unplugged from AC power. Fixed
-
Thanks, but where is the 2GB versus 2 billion bytes fix? ???
Where is the seamless auto-reopen fix?
Is it never happening?
-
I would think not. :(
-
I would think not. :(
Me neither. Just my opinion though.
J.T.
-
but, when I see that there is an update ;D, I look to see if just maybe they did it :o . Only to go, it will never happen. :'(
-
I somehow think that if it could be implemented, it already would have happened.
-
Wish they will fix the forward and rewind function....respond so SLOW - hardly does anything. Sometimes not even slow...it pauses the music!
-
thanks man, good looks!
-
For anyone who may be interested I can verify a couple of the changes in 1.4.5
- Increased data transfer speed when the MicroTrack is used as a card reader
I copied a 2GB audio file to and from a PQI Hi Speed 100 4 GB CF card and see the following data transfer times.
time to copy 2GB file from CF card to PC (Windows XP on HP laptop):
Using 1.4.3/1.02 bootloader: 26 minutes 34 seconds
Using 1.4.5/1.04 bootloader: 12 minutes 17 seconds
time to copy 2GB file from PC to CF card (Windows XP on HP laptop):
Using 1.4.3/1.02 bootloader: 23 minutes 07 seconds
Using 1.4.5/1.04 bootloader: 19 minutes 18 seconds
For reading from the card to the PC that's a pretty decent increase. Copying "to" the card, not such a great increase but that's much less important to me than read speed. Of course with my dedicated Lexar card reader it's still much faster than that (4:55 to read and 10:38 to write) but now, if I don't have the Lexar with me I can use the MicroTrack to offload my media without having to catch a movie while it's copying.
And the PQI media I used, had the issue of the MicroTrack continually asking to reformat with 1.4.3 but it's fine now with 1.4.5, so this must be one of the cards that's covered by the statement "- Fixed compatibility issue with some media (media would continually ask to be reformatted)"
My tests probably weren't the most scientific but they were pretty well controlled. So you're results may vary but I would expect you'd see similar results.
I'm happy.
J.T.
-
I ran this firmware Tuesday night (11/14) for Particle and had no problems. As always I just use this for 24/48 bit dump via S/PDIF from my mini-me.
-
I just upgraded my MT firmware to the latest version, but I'm not sure that my Bootloader is updating.
When I look at my version from the System menu, it shows firmware 1.4.5 but for Bootloader - it is blank.
When its actually booting the M-Audio splash shows 1.0 in the lower right hand corner.
I re-updated the firmware and even noticed the "Bootloader update complete" message.
Has anyone else experience this or found a fix for it?
TIA for any help,
Manley
-
Checked mine after the update and all is fine. Call Tech support and see if they have a clue.
-
I just upgraded my MT firmware to the latest version, but I'm not sure that my Bootloader is updating.
When I look at my version from the System menu, it shows firmware 1.4.5 but for Bootloader - it is blank.
When its actually booting the M-Audio splash shows 1.0 in the lower right hand corner.
I re-updated the firmware and even noticed the "Bootloader update complete" message.
Has anyone else experience this or found a fix for it?
TIA for any help,
Manley
What version of the firwmare were you running previously? If you were still running bootloader 1.0, that implies you were still running really old firmware (or else the bootloader not updating problem happened to you long ago too and you are just now noticing it). Maybe it doesn't like updating from such an old version (though the read me says noting about requiring you to do an interim update). I would try updating to 1.4.3 first and see if the same thing happens. Then try 1.4.0, etc. until you get that bootloader to change. Then try the 1.4.5 again.
-
Great advice, and that had already crossed my mind...
So, I updated to each and every version. After updating to 1.3.3, the blank bootloader - issue came up.
It still says "Booting Firmware 1.00" on the splash screen during boot. The application firmware is up to date, and it seems to be working fine.
I'm going to try and call M-Audio support now that I've registered it.
Update to come....
-
wow, the new firmware allows me to use my pqi flash card
-
wow, the new firmware allows me to use my pqi flash card
Cool. I'm not the only one.
J.T.
-
wow, the new firmware allows me to use my pqi flash card
Cool. I'm not the only one.
J.T.
What capacity pqi cards?
-
wow, the new firmware allows me to use my pqi flash card
Cool. I'm not the only one.
J.T.
What capacity pqi cards?
I just have the one. A 4GB Hi-Speed 100 Card
J.T.
-
I was wondering if anyone had tested to see the different times associated with the CF vards base don their speed ratings when the card performs the auto file split function. My 4 GB Kingston Elite Pro 45X speed card loses approximately ten seconds of audio in the interval between a "write to card" and starting a new file. I am interested in learning how much faster the 150X speed card is between the "write to card" and starting a new file. Is it safe to assume that it would take about 1/3rd of the time a 45X speed card takes meaning about 3 seconds?
-
Is anyone using the Transcend 4GB Digital 150X speed CF cards with the Micro-Track 24/96 ? These cards are on sale now for $74.99 after rebate which is a great price (I think). If the piece is compatable I will purchase one for recording use as the enhanced speed of the card will allow faster transfer rates to my pc when I retrun from recording a concert.
-
I was wondering if anyone had tested to see the different times associated with the CF vards base don their speed ratings when the card performs the auto file split function. My 4 GB Kingston Elite Pro 45X speed card loses approximately ten seconds of audio in the interval between a "write to card" and starting a new file. I am interested in learning how much faster the 150X speed card is between the "write to card" and starting a new file. Is it safe to assume that it would take about 1/3rd of the time a 45X speed card takes meaning about 3 seconds?
The shortest gap I've even seen is between 6 and 8 seconds. I think the processor or the buffers configurations won't go any faster no matter what speed the card is (IMO). This was (I think) on a Sandisk Ultra II card (I can't recall what 'x' this card is but it's plenty fast).
J.T.
-
I just spoke with M-Audio regarding the read/write speed of CF cards with the MicroTrack 24/96 and they advised me that it is directly related to the card speed. They also advised that the buffer size in the recorder is not large enough to ever make the auto file split function seemless so that their will always be some data lost in the transition between files. It would seem to me that at this point in the firmwares development they are not able to provide too much more that one could want that is of any real significance. I would like the ff/rw control to work better to review the recording on the machine but if i really need to do this I simply perform the function via software on my pc so it is relatively unimportant.
I use the MT as a bit bucket so the mic preamplifier stage and phantom power are not a concern of mine since I use an external a/d converter mic preamplifer with my DPA 4061 microphones. The sound quality that I am gettng is really quite amazing even when I compare to far more expensive recorders such as a Sound Devices SD 722 used with more expensive microphones. The MT is in my opinion the best of the stealth recorders available. Having attended shows where small size is a major concern or you simply will not be able to get past security I can say this is not only the right choice but one of the only choices for equipment thatyou might have to record certain concerts with.
-
Is anyone using the Transcend 4GB Digital 150X speed CF cards with the Micro-Track 24/96 ? These cards are on sale now for $74.99 after rebate which is a great price (I think). If the piece is compatable I will purchase one for recording use as the enhanced speed of the card will allow faster transfer rates to my pc when I retrun from recording a concert.
Prior to the new firmware, the Trancend 4gb 150X did not work. It would run for a while and then shut down. If I get a chance, I'll test it this weekend. I have 2 of the cards, and they work great in my Tascam and in my Canon camera. If I get the chance, I'll report back on it.
-
BTW- my Bootloader update issue was resolved by loading the firmware with the supplied 128mb CF card from M-Audio.
The Bootlaoder firmware would not properly update from my 4gb Kingston CF card. I think I'll keep the 128mb card with me at all times with the latest firmware on it in case of field emergencies.
FYI- I also learned that by holding down the menu and power button on boot will force it into emergency recovery mode, and force it to load the firmware from the CF card.
Ready for UM now!
Manley
-
If you think about it.... These are some goofy ass problems. Especially the "incorrect German Translation Strings" ;D "All your bass is belong to us" ;)
- Playback meters would stick at about 80% on MP3 files after restarting MicroTrack. Fixed
- Right channel clip light would sometimes flash when recording a high level signal on the left channel. Fixed
- If a file was recorded and then deleted, the next file name would not be incremented. Fixed
- Corrected some incorrect German translation strings
-
I use the MT as a bit bucket so the mic preamplifier stage and phantom power are not a concern of mine since I use an external a/d converter mic preamplifer with my DPA 4061 microphones. The sound quality that I am gettng is really quite amazing even when I compare to far more expensive recorders such as a Sound Devices SD 722
When running digital in, the recording device has absolutely nothing to do with the sound quality whatsoever. Whether you're running the $300 MT, the $2400 SD 722, or the $10,000 Cantar the results wll be identical.
-
wow, the new firmware allows me to use my pqi flash card
Cool. I'm not the only one.
J.T.
What capacity pqi cards?
I just have the one. A 4GB Hi-Speed 100 Card
J.T.
ditto
-
When running digital in, the recording device has absolutely nothing to do with the sound quality whatsoever. Whether you're running the $300 MT, the $2400 SD 722, or the $10,000 Cantar the results wll be identical.
Exactly.. And, in fact, this blind comp had the r09 A/D, when running behind the v3 analog, preferred over the v3 A/D > microtrack, 8 votes to 3.. My point is that the compact a/d's continue to significantly improve and running digi out from something like a v3 isn't always better..
http://taperssection.com/index.php?topic=70847.0
And no way does it mean the r09 a/d is better than the v3 a/d. Just that most folks preferred that sound on this source. FWIW, my comps suggest the r09 a/d is still significantly inferior to the 722 a/d. I wish that weren't the case...
What I'd still REALLY like to see with the mt is the ability to record as two mono tracks, each up to 2GB in size. That would allow 2 hours of continuous record time at 24/96. I'd seriously think of getting a mytek if the mt could do 2 hours continuous.
-
The Bootlaoder firmware would not properly update from my 4gb Kingston CF card. I think I'll keep the 128mb card with me at all times with the latest firmware on it in case of field emergencies.
Seems as if your 4GB Kingston CF is now not "COMPLETELY" compatible with the new firmware..
-
Seems as if your 4GB Kingston CF is now not "COMPLETELY" compatible with the new firmware..
You may be right. I've also noticed that I quite often get the MEDIA FULL message, even though its completely blank and freshly formatted (I'm using the Kingston 4gb Elite Pro with the Lizard on it). Every time, I hit record again and it works. This does make me nervous though.
First night out with it this evening to see UM here in STL. This little MF MT better be solid. I love it so far, let's see how it works when it really counts....
-
Im still getting incremental file names even after i format my card. What gives, i thought this was supposed to fix that? what happens when you reach 10,000.mp3, your MT blows up?
-
Thanks, but where is the 2GB versus 2 billion bytes fix? ???
Where is the seamless auto-reopen fix?
Is it never happening?
It will never happen...
-
Thanks, but where is the 2GB versus 2 billion bytes fix? ???
Where is the seamless auto-reopen fix?
Is it never happening?
It will never happen...
It's got to be a buffer issue. As long as MT owners have been asking about it, they'd have implemented it now if it was possible. Such a shame too, as it's gotten more stable and user friendly with every firmware update.
-
Im still getting incremental file names even after i format my card. What gives, i thought this was supposed to fix that? what happens when you reach 10,000.mp3, your MT blows up?
The MicroTrack resets to file 0001 when you set to defaults. And also presumably when you get to the 10,000 file like you said.
J.T.
-
Im still getting incremental file names even after i format my card. What gives, i thought this was supposed to fix that? what happens when you reach 10,000.mp3, your MT blows up?
The MicroTrack resets to file 0001 when you set to defaults. And also presumably when you get to the 10,000 file like you said.
J.T.
what do you mean when i set it to defualt? like i have to reset all my settings just to do what this firmware claims to do on its own? According to this firmware it should reset itself everytime i format my card. the file numbers should reflect the number of files on the card.
-
mine never resets the file number rather i updated the firmware or i formated the card
-
Im still getting incremental file names even after i format my card. What gives, i thought this was supposed to fix that? what happens when you reach 10,000.mp3, your MT blows up?
The MicroTrack resets to file 0001 when you set to defaults. And also presumably when you get to the 10,000 file like you said.
J.T.
what do you mean when i set it to defualt? like i have to reset all my settings just to do what this firmware claims to do on its own? According to this firmware it should reset itself everytime i format my card. the file numbers should reflect the number of files on the card.
Unfortunately (for you), that's not the way the MicroTrack firmware works and not how (IMO) I think it should. If it worked that way you'd end up with conflicting file names on multiple pieces of media. I'd end up with a file0001.wav on each of my CF cards. I want it to increment for every audio file it creates until I reset it. That's how my digital camera works. I don't end up with multiple dsc0001.jpg files.
And yes by set to defaults I mean using the set to Factory Defaults command from the system menu which will set all the changeable settings back to the defaults (input source, bit depth, contrast etc.).
What gave you the impression that it worked differently than this? Maybe M-Audio has an issue in their manual?
I hope this helps make things clearer for you.
J.T.
-
so after some time now
all in all
this update is good and worth doing in most peoples opinions?
-
While running the openers to the Duo 12/2 I experience my first channel flip. I was strange I have no idea how it happened or what the circumstances were. Everything else ran fine after I reset the MT.
Note this was my first flip with any of the firmwares, and I am up to 190 or so on recordings.
-
Sometimes I am using the MT as a bit bucket with input from a CoreSound MIC2496.
When I upgraded the firmware to the 1.4.5 I had the pleasant surprise to have the MT meters actually working!!!
I have not seen this reported so far, so I think this info could be useful to somebody
Giovanni
-
Which version of the firmware did you upgrade from? I've had pretty good luck with the meters since the 3rd? version of the firmware. I forget what version number that was but it's been while. Once I figured out the scale (thanks GuySonic) of the meters I found them very useful. I've been able to run my levels much hotter than I had with my M1 without "overs" and I think my recordings sound better for it.
-
I had 1.4.3 before. However the point I want to make is that with the 1.4.5 the meters actually work with the MT used as bit bucket, i.e. recording a digital signal via the SPDIF digital input.
This is very convenient to me because the MIC2496 has only 2 leds to set the level and this is one thing I don't like of it. With the MT meters it is easier to set the right input level.
Giovanni
-
I always used mine as a bit bucket too. Can you describe what changed? I'm not doubting it, I just missed it.
Thanks!
-
Nothing has changed with this update relevant to the merters working with the spdif input to the MT 24/96 I have the same set up and it has worked correctly on previous releases without problems. The Mic 2496 lights are much faster repsonse than the meters on the recorder and allow you to accurately set a -12.5 db level and forget looking at the meters after that! I am recording exclusively at 24/96 so using the -12.5 db level provides substantial headroom so that over saturation is not an issue. The levels indicated on the Microtrack recorder seem to correspond well with the LED lights on the Mic 2496 as well.
-
Nothing has changed with this update relevant to the merters working with the spdif input to the MT 24/96 I have the same set up and it has worked correctly on previous releases without problems. The Mic 2496 lights are much faster repsonse than the meters on the recorder and allow you to accurately set a -12.5 db level and forget looking at the meters after that! I am recording exclusively at 24/96 so using the -12.5 db level provides substantial headroom so that over saturation is not an issue. The levels indicated on the Microtrack recorder seem to correspond well with the LED lights on the Mic 2496 as well.
I agree, and mostly I am now using mt MT as a little portable recorder, using a various mics into a battery box that accepts the 1/8 jack on many mics, uses the MT's TRS jacks and sits atop the unit. I have always thought the meters were ok, but slow, (it took some time to understand them and what they are trying to communicate) but the leds were right on and I can record hot without distortion. The unit is pretty forgiving too, so it is ok to see them glow red occasionally. I do not think anything changed on this firmware upgrade regarding the meters. The biggest difference I noticed was that the unit is now more accepting of some CF cards that it struggled with before. Specifically for me I had a 4gb Kingston (45x or 50x I cannot recall which), and it would stop recording after a time. It works fine now with that card.
-
Nothing has changed with this update relevant to the merters working with the spdif input to the MT 24/96 I have the same set up and it has worked correctly on previous releases without problems. The Mic 2496 lights are much faster repsonse than the meters on the recorder and allow you to accurately set a -12.5 db level and forget looking at the meters after that! I am recording exclusively at 24/96 so using the -12.5 db level provides substantial headroom so that over saturation is not an issue. The levels indicated on the Microtrack recorder seem to correspond well with the LED lights on the Mic 2496 as well.
I agree, and mostly I am now using mt MT as a little portable recorder, using a various mics into a battery box that accepts the 1/8 jack on many mics, uses the MT's TRS jacks and sits atop the unit. I have always thought the meters were ok, but slow, (it took some time to understand them and what they are trying to communicate) but the leds were right on and I can record hot without distortion. The unit is pretty forgiving too, so it is ok to see them glow red occasionally. I do not think anything changed on this firmware upgrade regarding the meters. The biggest difference I noticed was that the unit is now more accepting of some CF cards that it struggled with before. Specifically for me I had a 4gb Kingston (45x or 50x I cannot recall which), and it would stop recording after a time. It works fine now with that card.
Was the kingston card an elite one ? I've used a Elite Kingston 45x since the beginning and never had a problem with it. I also use a sandisk, non ultra and have no problems either ...
-
Nothing has changed with this update relevant to the merters working with the spdif input to the MT 24/96 I have the same set up and it has worked correctly on previous releases without problems. The Mic 2496 lights are much faster repsonse than the meters on the recorder and allow you to accurately set a -12.5 db level and forget looking at the meters after that! I am recording exclusively at 24/96 so using the -12.5 db level provides substantial headroom so that over saturation is not an issue. The levels indicated on the Microtrack recorder seem to correspond well with the LED lights on the Mic 2496 as well.
I agree, and mostly I am now using mt MT as a little portable recorder, using a various mics into a battery box that accepts the 1/8 jack on many mics, uses the MT's TRS jacks and sits atop the unit. I have always thought the meters were ok, but slow, (it took some time to understand them and what they are trying to communicate) but the leds were right on and I can record hot without distortion. The unit is pretty forgiving too, so it is ok to see them glow red occasionally. I do not think anything changed on this firmware upgrade regarding the meters. The biggest difference I noticed was that the unit is now more accepting of some CF cards that it struggled with before. Specifically for me I had a 4gb Kingston (45x or 50x I cannot recall which), and it would stop recording after a time. It works fine now with that card.
Was the kingston card an elite one ? I've used a Elite Kingston 45x since the beginning and never had a problem with it. I also use a sandisk, non ultra and have no problems either ...
Kingston elite pro 45X 4GB. I would get a message the first time I pressed record, saying media full, and then have to press it a second time. It would fail sometimes a few minutes into recording. I don't have this problem anymore with it.
-
I get this message, too. I have to press REC 2 times before it can start recording...that is using the 4GB 45X Kingston Elite and with the current firmware.
-
I get this message, too. I have to press REC 2 times before it can start recording...that is using the 4GB 45X Kingston Elite and with the current firmware.
I have NEVER had this happen usingthe 4GB 45X Kingston Elite and with the current firmware - wonder what is up there for you guys??
-
Neither have I. In fact I never had that error at all. Have you both reformatted the cards before each new recording ?
FWIW I am still running FW 1.4.3 ...
-
Neither have I. In fact I never had that error at all. Have you both reformatted the cards before each new recording ?
FWIW I am still running FW 1.4.3 ...
I usually reformat, but do not always remember to. I think the Kingston is more sensitive to needing an occasional reformatting. My 5GB Seagate never required it, it made absolutely no difference, and the Sandisc I use currently does not seem to require or especially react if I reformat or not.. The message I get with the Kingston 4GB, is no longer an issue because it records fine, but strange that it happens. I have a 2GB Kingston, and I do not get the message with that CF card. Now I tend to use the Kingston 4GB in my Camera or Tascam, because of that one extra button push required, but I would not hesitate to use it if I needed it.
Strange that not everyone gets that message. I am running the newest 1.4.5, which I think is the best firmware to date.
-
When I use my 2GB card I never get this message only with the 4GB. Do not know why... I do digital in, using the USB external power, and recording at 24/96 with the 4GB Kingston 45X. You people doing the same setting and setup? Maybe it is dependent on the setup & settings. Yes, I always format the card before using it.
-
When I use my 2GB card I never get this message only with the 4GB. Do not know why... I do digital in, using the USB external power, and recording at 24/96 with the 4GB Kingston 45X. You people doing the same setting and setup? Maybe it is dependent on the setup & settings. Yes, I always format the card before using it.
These days I am only going in via the TRS jacks, so the settings do not seem to be the reason. I record usually at 16/48. I also only get the message on the 4GB, not the 2GB Kingston.