Topic: Microtrack Bug Report

[John Kelly]

There seems to be some corelation between hangs and non-standard SPDIV

Not true.  The unit hangs on anything other than 16/48 - including 16/44.1 and 16/96.

[WiFiJeff]

There seems to be some corelation between hangs and non-standard SPDIV

Not true.  The unit hangs on anything other than 16/48 - including 16/44.1 and 16/96.

Hmmm.  Worked for me when I fed 16/44.1 from a Denecke Inbox.  But not 24/96 from
a V3, that hung it good.

Jeff

[mmedley.]

Has anyone tried running various sample rates and bit depths via SPDIF from say an Audiophile 192 or 2496? Seems some people can record one thing and others can't? I think it might be worth a shot. Maybe some strange compatibility issue going on?

[WiFiJeff]

I'm wondering if there are different versions out there.  Mine is firmware 1.00, but if you go to Version on the System menu I have version 1.0.2, anything else out there?

Jeff

[neutrino]

I'm wondering if there are different versions out there.  Mine is firmware 1.00, but if you go to Version on the System menu I have version 1.0.2, anything else out there?

Jeff

Got the same 1.0.2 version here.
dB-

[SClassical]

One reason why M-Audio delayed their shipment/release was to correct the problem with recording 24bit using digital in. They knew about this bug a few months ago. What is the point shipping it if they did not fix the problem? After so many weeks/months they just gave up trying? Shipping it without solving anything after a few weeks/months of delay is irresponsible.
Simon

[cascademedia]

thanks for the feedback everyone, I have sent off the compiled list to the powers-that-be at M/Audio.   Hopefully we will see some action on the firmware side of things shortly.

- Frank

[cascademedia]

hey real quick.....   when the unit hits the 2GB limit does it simply just stop?   How quickly can you get a new file started?   With the 7 Series it can be stopped and started in a couple secs.    Fill me in....

thanks,
Frank

[Brian Skalinder]

S/PDIF defines audio up to 20 bits, 24 bit is no standard. Many implementations are limited to 16 bits. see http://www.tech-faq.com/spdif.shtml

Just because it's not defined in the standard doesn't mean it can't be done.  Other devices produce and/or receive 24-bit digital streams, no reason M-Audio can't do the same.

The 2GB file size limit implies you should split recordings longer than 2 hours (48000/24) in two takes.

Only enabling continuous recording of 60min at 24/96, on a 24/96 device - i.e. not implementing a buffer for either auto or manual seamless new file creation - is simply poor design.  For those wanting to record more than 60 continuous minutes, it's absolutely a showstopper.  The "workaround" of splitting the recordings manually - and losing content in the process - isn't a workaround if it doesn't solve the problem of lost content.  But maybe I'm mistaken and starting a new file is, in fact, seamless?  I don't think so, though.

[MattD]

hey real quick.....   when the unit hits the 2GB limit does it simply just stop?   How quickly can you get a new file started?   With the 7 Series it can be stopped and started in a couple secs.    Fill me in....

thanks,
Frank

With the 7-Series, you don't even need to stop and start the recording. As long as you have the autosplit enabled, it creates a new file on the fly.

[John Kelly]

hey real quick.....   when the unit hits the 2GB limit does it simply just stop?   How quickly can you get a new file started?   With the 7 Series it can be stopped and started in a couple secs.    Fill me in....

thanks,
Frank

It simply stops recording.  Takin a few seconds is unacceptable IMO - as is monitoring for when the 2 gig limit is reached.  It should be an automatic file split and the recording should continue...

[cascademedia]

I forgot about the auto split feature in the updated firmware...thanks for the clarification

[pietje]

Just because it's not defined in the standard doesn't mean it can't be done.  Other devices produce and/or receive 24-bit digital streams, no reason M-Audio can't do the same.

I understand you want it, but I would "not working with non-standard formats" not classify as a bug.

Only enabling continuous recording of 60min at 24/96, on a 24/96 device - i.e. not implementing a buffer for either auto or manual seamless new file creation - is simply poor design. 

I understand you want it. Recording media used to have time limitations. 60 minutes of 24/96k or 120 minutes of 24/48k is not even too bad. It is not unusual for merformers to have a break after 45-60 minutes. I would not classify it as a bug.

If you really need these features, and you need them now, there are other solutions with a different pricetag.

[Todd R]

Frank --

If you see this and can add more:

From my experience, when recording long files (more than an hour or so?), the level meters stop working.  The peaks keep working and keep changing with the changing signal level, but the actual levels for the signal disappear.  This continues even after you stop recording one file and start a new one.  Only way to get the meters to reappear is to shut the unit down and power back up again.  This is just the level meters -- it keeps recording perfectly, you just can't see level meters.

Also, from my experience, you can record at 16/44.1 -- I've done it numerous times.  But the spdif is not reliable, probably 1 times out of 3 when I try to record off spdif (16/44 or 16/48), the unit locks up and must be re-booted.  And on the lock-up, I've never had it lock up at any time other than when trying to start a spdif recording.  Once the spdif recording starts successfully, it records without a glitch for hours (though the level meters disappear).

[JasonSobel]

Just because it's not defined in the standard doesn't mean it can't be done.  Other devices produce and/or receive 24-bit digital streams, no reason M-Audio can't do the same.

I understand you want it, but I would "not working with non-standard formats" not classify as a bug.

Except that it was advertised that the unit would be able to record at 24/96 from all inputs, including S/PDIF.  If they say they are going to do it, and it doesn't work, than it classifies as a "bug" and not a "feature request"