Become a Site Supporter and Never see Ads again!

Author Topic: Microtrack Bug Report  (Read 84236 times)

0 Members and 1 Guest are viewing this topic.

Offline udovdh

  • Trade Count: (0)
  • Taperssection Member
  • ***
  • Posts: 986
Re: Microtrack Bug Report
« Reply #210 on: November 05, 2005, 11:41:50 AM »
Anybody know when (+/-) the updated firmware should be here? Before Christmas?


I asked M-Audio this earlier in the week.  Their response:

"Unfortunately, due to the nature of firmware releases (testing/verifications/fixes/features) we cannot specify any official dates on when the next firmware may be available."

Obviously doesn't tell us much.  I wrote back looking for a general timeline and will report when they respond.

I can understand they don't want to pin temselves down but they can give us a rough goal date and keeping their list of bugs to be squashed before that date for themselves?
I'd rather see more often released firmwares with a few bugs less (or more features) than released farther apart with less chance to give feedback on fixes or progress.
Did anyone check out the limiter in the ADC?
AKM EK5365 I read somewhere here.
I am no limiter expert but can anyone if it can be useful?

Offline John Kelly

  • Been a while...
  • Trade Count: (1)
  • Needs to get out more...
  • *****
  • Posts: 9753
  • Gender: Male
    • The Jokell
Re: Microtrack Bug Report
« Reply #211 on: November 05, 2005, 12:22:14 PM »
Anybody know when (+/-) the updated firmware should be here? Before Christmas?


I asked M-Audio this earlier in the week.  Their response:

"Unfortunately, due to the nature of firmware releases (testing/verifications/fixes/features) we cannot specify any official dates on when the next firmware may be available."

Obviously doesn't tell us much.  I wrote back looking for a general timeline and will report when they respond.

I can understand they don't want to pin temselves down but they can give us a rough goal date and keeping their list of bugs to be squashed before that date for themselves?

Don't hold your breath. 
Sennheiser MKH8040st > SD 702
XBL/PSN/Steam ID: thejokell

cmoorevt

  • Guest
  • Trade Count: (0)
Re: Microtrack Bug Report
« Reply #212 on: November 07, 2005, 01:56:45 PM »
I heard back from M-Audio this morning.  They said the firmware update would be available hopefully within the next month, but they cannot guarantee that.  The metering issue(meters go haywire after a while) is one of the issues they are working on for the next update.

Offline neutrino

  • Trade Count: (1)
  • Taperssection Member
  • ***
  • Posts: 628
  • Gender: Male
  • **Team Chicago**
Re: Microtrack Bug Report
« Reply #213 on: November 07, 2005, 02:38:09 PM »
I heard back from M-Audio this morning.  They said the firmware update would be available hopefully within the next month, but they cannot guarantee that.  The metering issue(meters go haywire after a while) is one of the issues they are working on for the next update.

Heard the same thing here as well. I was told this is a much bigger firmware upgrade which is supposed to correct the bulk of the issues. We shall see.
dB-
CA14/OM14 > A10
Sony SBM-1 Oade mod

Offline prof_peabody

  • Trade Count: (4)
  • Needs to get out more...
  • *****
  • Posts: 4339
  • Team Houston
Re: Microtrack Bug Report
« Reply #214 on: November 07, 2005, 03:35:25 PM »
Anybody know when (+/-) the updated firmware should be here? Before Christmas?


I asked M-Audio this earlier in the week.  Their response:

"Unfortunately, due to the nature of firmware releases (testing/verifications/fixes/features) we cannot specify any official dates on when the next firmware may be available."

Obviously doesn't tell us much.  I wrote back looking for a general timeline and will report when they respond.

I can understand they don't want to pin temselves down but they can give us a rough goal date and keeping their list of bugs to be squashed before that date for themselves?
I'd rather see more often released firmwares with a few bugs less (or more features) than released farther apart with less chance to give feedback on fixes or progress.
Did anyone check out the limiter in the ADC?
AKM EK5365 I read somewhere here.
I am no limiter expert but can anyone if it can be useful?

My software engineering background tells me that it makes more sense for M-Audio to release one large update as opposed to several smaller updates.  If they are following a rigorous testing scheme then it is easier to do all the tests once as opposed to many times (with each update).  One fix could break another part of the code, probably best to avoid this happening multiple times.

Most MT users probably have adequate functionality at this point, so M-Audio are probably not rushed to release updates.  On a side note, I noticed a couple reporters using the microtrack in my area. 

Offline it-goes-to-eleven

  • Trade Count: (58)
  • Needs to get out more...
  • *****
  • Posts: 6695
Re: Microtrack Bug Report
« Reply #215 on: November 07, 2005, 03:47:07 PM »
If they are following a rigorous testing scheme then it is easier to do all the tests once as opposed to many times (with each update).

Rigorous testing scheme?  In all seriousness, that would be a change from the process they seem to have employed in the past.

Given the serious problems, I'd vote for more frequent, minor, bug fix releases. The team that does this code hasn't demonstrated that they can even do a quality release yet. So holding off for that ideal pie in the sky release seems like an odd way to go. Hope they surprise us.

Quote
Most MT users probably have adequate functionality at this point, so M-Audio are probably not rushed to release updates.

The number of bugs in this thing when it was first released would barely qualify it as an alpha product.  Given the number of problems with the current firmware, I don't really even consider it beta.  A normal beta has obvious issues resolved. It doesn't take more than a couple of minutes to find bugs in the MT and serious omissions in the documentation.

Based on reports here, a significant percentage of recordings are still being lost.

I'd get an R-1 except it looks like that firmware will Never get updated (2gb fix)  :P

(hugs 722)

Offline prof_peabody

  • Trade Count: (4)
  • Needs to get out more...
  • *****
  • Posts: 4339
  • Team Houston
Re: Microtrack Bug Report
« Reply #216 on: November 07, 2005, 05:16:48 PM »
If they are following a rigorous testing scheme then it is easier to do all the tests once as opposed to many times (with each update).

Rigorous testing scheme?  In all seriousness, that would be a change from the process they seem to have employed in the past.

Given the serious problems, I'd vote for more frequent, minor, bug fix releases. The team that does this code hasn't demonstrated that they can even do a quality release yet. So holding off for that ideal pie in the sky release seems like an odd way to go. Hope they surprise us.

Quote
Most MT users probably have adequate functionality at this point, so M-Audio are probably not rushed to release updates.

The number of bugs in this thing when it was first released would barely qualify it as an alpha product.  Given the number of problems with the current firmware, I don't really even consider it beta.  A normal beta has obvious issues resolved. It doesn't take more than a couple of minutes to find bugs in the MT and serious omissions in the documentation.

Based on reports here, a significant percentage of recordings are still being lost.

I'd get an R-1 except it looks like that firmware will Never get updated (2gb fix)  :P

(hugs 722)


Testing and the managers' push to market are always tough to balance.  Products are often released much earlier than engineers would like, usually because the projects have tight capital plans.  In custom software that, as a customer, I beta test everyday I always find the first release is putrid followed by a quickly released patch, and then wait a much longer time for more significant patch or full release. 

The managers get some relief with the initial release and this usually allows time for engineers to do more thorough testing.  Exhaustive software testing is a very time consuming process. 

Having said all this, in my humble opinion, I would expect the next real firmware upgrade will take some time, but address a significant amount of bugs.

Offline prof_peabody

  • Trade Count: (4)
  • Needs to get out more...
  • *****
  • Posts: 4339
  • Team Houston
Re: Microtrack Bug Report
« Reply #217 on: November 07, 2005, 05:49:08 PM »

IMO this is a complete exageration of the situation, past or present

people are entirely too sensitive over the "edge" condition problems with this device...sure not all the features advertised work perfectly yet, but....

pure and simple the basic functionality of this device is solid, stable and reliable....someone using this device for recording using the mic input to a 16/44.1 file will have what problems exactly?

contrary to what people here want...24/96 over the SPDIF is NOT a function even 10% of the market for this device needs/wants/cares about


i have been regularly using the MT for 24/44.1 recordings and haven't lost one...sure i use the analog inputs, a more expensive name-brand CF card and a name-brand micro-drive, i reformat the media between sessions, and i have used many different recorders so i'm pretty familiar with how they work, but i dont feel the majority of "reported" problems i have seen on this site are the fault of the device as much as user inexperience/error/lack of understanding of the inherent issues with solid state media, file formats, etc

the 722 you are hugging had by comparision more significant issues with basic functionality in its initial releases..file corruption was a major issue with the 722...it got fixed....just like the m-audio problems will get fixed....be patient, or use another piece of gear



boogie

+T, I agree with you.  Most people are using this in analog-in situations.

 

RSS | Mobile
Page created in 0.054 seconds with 32 queries.
© 2002-2025 Taperssection.com
Powered by SMF