Topic: Microtrack 24/96 1.3.3

[gl0bber]

Thanks for speaking the (sometimes) unpleasant truth guysonic - +t for that...

Cheers

[schoff]

"Because even with its problems it still does more than any other current device at its price point and size."

[/quote]

Is this still a valid point with the Roland Edirol R09 coming onto the scene soon?

[Ed.]

"Because even with its problems it still does more than any other current device at its price point and size."

Is this still a valid point with the Roland Edirol R09 coming onto the scene soon?

yes.  there is no digital in on the R09.

[svenkid]

I still rock the MT with 1.1.5 y0! no problems here 

[Nick's Picks]

i'm running 1.2.3 and afraid to upgrade to the newer ones in fear of killing my working deck.
its been flawless at 24/48.  several tracks per card has been a non issue.

[JoeKiller]

I decided to run like Nick suggested at 1.2.3 last night for Lotus.  24/4816/48, got my longest recording ever off the MT and it worked flawlessly.  2 hours and 5 minutes.  Also got the opener but they were only 45 minutes.

For stability, stick with 1.2.3 for now.

[scoper]

I decided to run like Nick suggested at 1.2.3 last night for Lotus.  24/48, got my longest recording ever off the MT and it worked flawlessly.  2 hours and 5 minutes.  Also got the opener but they were only 45 minutes.

For stability, stick with 1.2.3 for now.

I've been running 1.3.3 with no issues at all, so no reason to downgrade.

How do you get a 2:05:00 recording at 24/48? The 2GB File limit cuts you off at 1:55:00, correct?

[JoeKiller]

How do you get a 2:05:00 recording at 24/48? The 2GB File limit cuts you off at 1:55:00, correct?

24/48 can do about 240 minutes of recording.
I think 24/96 is the 1:55 cutoff
http://taperssection.com/index.php?topic=199.0

[china_rider]

24/96 = ~2 gig an hour
24/48 = ~1 gig an hour

http://24bit.turtleside.com/pcm.wav.file.sizes.pdf

[JoeKiller]

How do you get a 2:05:00 recording at 24/48? The 2GB File limit cuts you off at 1:55:00, correct?

24/48 can do about 240 minutes of recording.
I think 24/96 is the 1:55 cutoff
http://taperssection.com/index.php?topic=199.0

I'm an idiot and had the MT on 16bit. DOH!  Thusly it was very capable of getting the whole show.

[eskin]

1.4 is up on the M-Audio site!

[it-goes-to-eleven]

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


Issues addressed by this release

-Sometimes wouldn’t use the entire available space of the media and would report media full before it actually was. Even after deleting previous recordings from the media.

-Sometimes reported incorrect file sizes on MP3s.

-Outputs would turn off during playback of some files.

-Autosplit feature would not always record to full 2GB file size when source is S/PDIF

-Files sometimes were not saved properly if the battery would run out during a recording.

-Sometimes would revert to default settings if the battery charge were to run out during use.

-Recordings would sometimes stop early (before filling media or reaching 2GB) when using S/PDIF as the source.

-Some French characters and translations were incorrect.

-Would not always display the full media message when it should.

-Could not play files from the ‘Files’ menu if the files were inside a folder.

-Sometimes would hang on writing very short (less than 1 second) recordings.

-Some S/PDIF recordings failed to start recording if they immediately followed an analog recording.


Edit: Add
User Interface change:

While charging with the unit in the Application, the battery icon will contain the letters CHG. This will remain until the battery voltage reaches 100% and remains there for one hour. At that time, the CHG will be replaced with a plug icon (indicating it is plugged in and supplying power but no longer charging the battery). This one hour ‘timer’ will be reset only if power is removed for longer than 3 minutes (which will prevent the unit from overcharging if the power is removed and returned for short periods of time).

[SClassical]

i'm running 1.2.3 and afraid to upgrade to the newer ones in fear of killing my working deck.
its been flawless at 24/48.  several tracks per card has been a non issue.

The last time I used 1.2.3 (last weekend) wasn't so lucky. I recorded 1 hr of music and after that I stopped the recording and started the recording again to the end of the CF (over 1 hr) at 24/48 using a 2GB card. The 2nd track was compacted to a approx 20 min of audio (which should have been about 1 hr). It sounded strange, too. The speed was more or less doubled and the pitch was above normal. I was hoping the recording will stop as soon as the card was full but it didnt but compacted the last track and continued recording. I was recording via SPDIF. This happened to me 2X now ever since I went back to 1.2.3. from 1.3.3.

[SClassical]

Regarding backing up to firmware 1.2.3 from firmware 1.3.3,

You'll notice that unlike the previous MicroTrack updates, the 1.3.3 update contains 3 files instead of just two. The three files are updates to 1) The boot loader (BL_MPR.rom), 2) the Application (PP5020.mi4) and the menus / languages etc. (Resources.arl). The boot loader portion of the update contains the code that boots the unit up (hence the name) but it also contains the Rescue Disk mode code to help reload firmware just in case the Application or Resource portions of the firmware ever become corrupt or fail to update properly during a firmware update. The Rescue disk mode can't of course help if it's the Boot loader itself that has become corrupt (perhaps during a failed firmware update).

Because of this I would not recommend repeatedly updating the Boot loader portion. If for some reason you need to regress to an earlier firmware and then return to 1.3.3, it is not necessary to re-update the Boot loader during this update since when regressing for instance to 1.2.3, the 1.2.3 update does not contain a boot loader update (there is no BL_MPR.rom file). So in effect, once you regress to 1.2.3 from the 1.3.3 update, you will really be running application 1.2.3 on top of boot loader 1.02 (where originally you would have been running application 1.2.3 on top of boot loader 1.00). When you regress to 1.2.3 you can tell that you still are running the 1.02 boot loader because the startup screen doesn't have the 1.0 on it that used to be there when running boot loader 1.0. So, this being the case and since at least one person has already ended up with a dead unit after the update to 1.3.3 I would shy away from updating the boot loader code more than once.

So far 1.3.3 is good for me so I won't be going back to 1.2.3 (fingers crossed).

J.T.

Hey, I guess if you want to go to 1.4.0. you have to upload the boot loader code again (more than once).

[jtessier]

Hey, I guess if you want to go to 1.4.0. you have to upload the boot loader code again (more than once).
[/quote]

Must not have had many failures from all those who updated to 1.3.3. Makes me feel pretty good about it. If it's the same exact bootloader though, in theory you could delete it and make your firmware update faster but what's the point?  I'm only (he said wishfully) going to go to 1.4.0 once and stay there (finger's crossed).

J.T.