Taperssection.com
Gear / Technical Help => Recording Gear => Topic started by: jtessier on May 25, 2006, 09:48:25 AM
-
M-Audio has a fix for the back to back recordings up on their site now.
http://www.m-audio.com/index.php?do=support.drivers&f=725&dl=yes
Or navigate to the Web site, go to Suport -> Drivers -> check the "Show Beta Drivers" checkbox, then choose USB Series -> MicroTrack 24/96 -> then choose any of the operating systems shown (they all lead to the same zip file as far as I can tell).
Here's the Read Me for this release:
This readme covers MicroTrack 24/96 Firmware v1.4.1 b1
NOTE: This is a beta release. As such, we do not recommend using this release in a critical use environment. Such use is at your own risk.
If you experience any issues with this release, please use our beta release support form to report it at:
http://www.m-audio.com/index.php?do=support.betaform
============================================================
Installation Instructions:
1) Connect the MicroTrack 24/96 to your Mac or PC (Please refer to your manual for details on this procedure).
2) Copy the three files from this update, "PP5020.mi4", "BL_MPR.rom" and "Resources.arl," onto a properly formatted Compact Flash card to the root (top) directory of your MicroTrack 24/96 (Do not put them in a folder).
3) Properly unmount the MicroTrack 24/96 from the computer (Again, please refer to your manual for complete instructions).
4) On the MicroTrack 24/96, navigate to Main Menu > System > Firmware Update and press the NAV button.
5) You will be asked to verify this action. Press the NAV button again to begin the firmware update. The MicroTrack will show a few messages on the screen while the update is in progress. The four LEDs around the level controls will flash sequentially during the update. When the firmware update is complete, the MicroTrack will automatically reboot. To verify the firmware update was executed, go to Main Menu > System > Version. If the firmware update was successful, it should now show Firmware 1.4.1 b1 and Bootloader 1.02
============================================================
Issue(s) addressed by this release
- When manually stopping a recording, if a second recording was started while the first was still being saved, the second recording wouldn't save to disk.
============================================================
-
NOTE: This is a beta release. As such, we do not recommend using this release in a critical use environment. Such use is at your own risk.
Isn't the Microtrack itself a beta release? :)
-
The B is because it's da BOMB! :D
-
The B is because it's da BOMB! :D
Sure explodes like one :)
-
The B is because it's da BOMB! :D
Holy shit that was funny. +T!!!
Sure explodes like one :)
Holy shit that was funny... +T!!!
-
I still like 1.2.3
-
The two button stop/start was the reason I reverted from 1.4.0 back to 1.3.3 - I'll jump on this one if it solves the issue.
Scott
-
The two button stop/start was the reason I reverted from 1.4.0 back to 1.3.3 - I'll jump on this one if it solves the issue.
Scott
It's working for me so far (finger's crossed).
J.T.
-
I still like 1.2.3
I think that's what I'm on too - no real problems other than the meters wigging after 30 minutes or so.
-
I still like 1.2.3
I think that's what I'm on too - no real problems other than the meters wigging after 30 minutes or so.
I rarely look at the meters, except when I start a recording.
-
used 1.4.1b1 tonight. community school concert 5 & 6 graders and middle school kids.
ran the usual mk-41 >vms 5 > kind kables > v-3 @ 24-48 > mt 24/96. got a dozen pops, big spikes on the wavs. they are not on the jb-3 back up.
going back to 1.4.0 no problems for me with that.
-
i've been running 1.2.3 ..... very tempted to upgrade to newer versions, but have not. My MT has been a rock @ 24/48 and I have yet to run into set of music long enough to make me stop/start a new file.
very unlike me to use the "if it aint broke, dont fix it" mentality w/my gear. i'm usualy the first guy to guinnea pig.
-
been running 1.4 since it came out, ran for two days at the Wu Li festival with no issues ...
-
used 1.4.1b1 tonight. community school concert 5 & 6 graders and middle school kids.
ran the usual mk-41 >vms 5 > kind kables > v-3 @ 24-48 > mt 24/96. got a dozen pops, big spikes on the wavs. they are not on the jb-3 back up.
going back to 1.4.0 no problems for me with that.
ouch, any further testing to see if it is repeatable?
I was about to throw in 1.4.1b1 for Summer Camp this weekend, guess I will hold off on that!
Thanks for sharing the info, +t.
-
I ran a dat from my r500 > digii to the MT using the new firmware and had no problems at all.
-
I've had no issues at all with the Mircotrack and all the firmwares. Only thing I wish the MT had was the ability to use throw away batteries instead of the internal one it uses.
Cheers,
Jim
-
After upgrading from 1.4, the record monitoring feature no longer works. Has anyone else noticed this?
-
After upgrading from 1.4, the record monitoring feature no longer works. Has anyone else noticed this?
It's working fine for me. At least on the 1/8" input. Are you trying the 1/4" jacks? Also, remember that there is no input monitoring support for S/PDIF recording.
J.T.
-
1/8" jack... I am aware that it doesn't work for SPDIF I/O :)
Wonder what is up. It also freaked out on a 4Gb CF card after the upgrade (recorded for a while at 24/96, then eventually wouldn't record at all, then claimed there was nothing on the media... reformatted it elsewhere, but the Microtrack still can't deal w/ it).
-
1/8" jack... I am aware that it doesn't work for SPDIF I/O :)
Wonder what is up. It also freaked out on a 4Gb CF card after the upgrade (recorded for a while at 24/96, then eventually wouldn't record at all, then claimed there was nothing on the media... reformatted it elsewhere, but the Microtrack still can't deal w/ it).
Wow, that's weird. Does it even throw an error message or does it just stare back at you blindly when you press the Rec button?
J.T.
-
I had a lexar 4gb card "freak out" on me. I don't know what firmware it happened with. It would not work at all. I sent it to lexar and they sent me a new one. I guess the card can go "bad". It did work before.
-
I'm not in town, so can't check the specifics. To memory, I hit "record" and the deck just sits there with "stop" on. I think if I go to look at files it gives me a "disk full" message even though the card is empty. I also can't format the card, I get the "disk full" message. I put the card in my HD-P2 and, after format, it works just fine in the tascam, but still wouldn't work in the MT, not even a re-format.
-
I'm not in town, so can't check the specifics. To memory, I hit "record" and the deck just sits there with "stop" on. I think if I go to look at files it gives me a "disk full" message even though the card is empty. I also can't format the card, I get the "disk full" message. I put the card in my HD-P2 and, after format, it works just fine in the tascam, but still wouldn't work in the MT, not even a re-format.
I guess I'd suggest (when you get back) going back to 1.4.0 or 1.3.3 or even 1.2.3 and see if the card starts working again. If it still doens't then maybe your card has failed in some weird way but if it works you could then (if you didn't at this point feel like chucking the MT across the room) try updating to 1.4.1b1 again to see if the earlier problems were repeatable.
J.T.
-
HI folks. I just upgraded to the latest firmware, and have run into the following:
4GB compact flash, 24-bit, 44.1KHZ, analog in. I let the recorder just run to test the file split capability, and to see how much battery life I could get. File 1 turns out to be 1.86GB and loads fine into various programs on the PC. File 2 ends when the unit runs out of battery power, at 1.32GB, and does *NOT* load into Sound Forge or similar programs on the PC. Sound Forge 6 reports it as an unsupported format. Has anybody else had this happen?
It seems like the last file isn't being saved correctly before the unit dies.
-
Hey all-
anyone running SPDIF in at 24 bit with the 1.4.1b1 firmware? Just wondering how it is working. Most of the people who have posted here that 1.4.1b1 is working well for them seem to be either running analog in or 16 bit SPDIF.
Peace,
Ben
-
Hey all-
anyone running SPDIF in at 24 bit with the 1.4.1b1 firmware?
...ran 2 shows with this firmware, 1 show was a single 2 hour set and the other was dual sets at 1 hour each. Both nights were recorded at 24/48 to a 4gb microdrive with no field problems aside from the startup bug where when it lies dormant for a while and kicks on after 10 or so mins being plugged up to a power source. That wierdness seems to have been around for its life so far..its a sleepy microtrack. :sleepy: The recordings themselves were fine though. I had header problems where I had to change them from 44 to 48 after transfer to fix the time length/pitch (using MT > Mac) thats a new one with me and this firmware.
-
HI folks. I just upgraded to the latest firmware, and have run into the following:
4GB compact flash, 24-bit, 44.1KHZ, analog in. I let the recorder just run to test the file split capability, and to see how much battery life I could get. File 1 turns out to be 1.86GB and loads fine into various programs on the PC. File 2 ends when the unit runs out of battery power, at 1.32GB, and does *NOT* load into Sound Forge or similar programs on the PC. Sound Forge 6 reports it as an unsupported format. Has anybody else had this happen?
It seems like the last file isn't being saved correctly before the unit dies.
try using audition / cep and open it as a raw pcm file. sounds like the file header didnt get written before it died
-
???
Loaded the 1.4 and now my windows media does not recognize the wav files, also the microtrack started to freeze up and took a very long time to power off. Going back to previous version of firmware. Looks like this version created a new problem instead of fixing it. :o
-
???
Loaded the 1.4 and now my windows media does not recognize the wav files, also the microtrack started to freeze up and took a very long time to power off. Going back to previous version of firmware. Looks like this version created a new problem instead of fixing it. :o
I thought newest version is 1.4.1b2. The 1.4.1b1 was quickly discovered to be flawed and corrected with the b2 version that seems quite OK so far.
-
well, this version of the firmware seems to be working fine for me up to this point. Keeping my fingers crossed.
-
my MT was totaly hosed after upgrading to 1.4 and then rolling back to 1.2.3.
I installed the 1.41b2 beta and now that thing runs like a freakin' top.
so thumbs up from my end on b2.