Topic: Microtrack 24/96 1.3.3

[bconnolly]

I think everyone has that "problem" with the available recording time. I think either way (s/pdif or trs) you should be able to get 9 hours at 16/44.1 even if the available recording time screen says 4 hours. When you are recording, does it say 3 hours? That should be the right time for 16/44.1 (3 hours @ 16/44.1 = 2 GB).

Ok I just wanted to make sure it wasn't an isolated problem (sorry... i try to keep up on all the quirks but I miss a few).

So the time remaining on the recording screen is the time remaining for that file and if you start a new file, that counter will reset?

[gl0bber]

The zero-byte corrupted WAV, full card bug on 1GB CF seems to have been fixed as well.     This alone makes it much more useful for me.  As for the 2GB split, all they did was automate the process of flushing the buffers, then close the file, and then open a new one, all in sequence.  Before that one had to do it manually, which took longer.  So that is convenient too.  But please don't expect too much from the Portal Player platform.  As I mentioned before, I seriously doubt the CPU has nearly enough power to seamlessly flush the buffers, close the file, open a new file, and write to the new buffer all at the same time...  Also, the playback meters are still useless, so maybe they should be deleted. not so bad now.

But this is great news nonetheless.

Now I'm off to see if they fixed the dodgy battery charging software yet.

Edit:  Typo fixed, etc.

[alienbobz]

I think everyone has that "problem" with the available recording time. I think either way (s/pdif or trs) you should be able to get 9 hours at 16/44.1 even if the available recording time screen says 4 hours. When you are recording, does it say 3 hours? That should be the right time for 16/44.1 (3 hours @ 16/44.1 = 2 GB).

Ok I just wanted to make sure it wasn't an isolated problem (sorry... i try to keep up on all the quirks but I miss a few).

So the time remaining on the recording screen is the time remaining for that file and if you start a new file, that counter will reset?

Yeah the time is for that one file. If you stop the recording and start a new one, the time should reset itself. Either it will be another 2GB or if will be the space left (if you have less than 2GB left on your card, it will show the time remaining for the bit/sample rate you are using).

Edit: Did you use the new firmware last night? How did it go? I plan on using it on Thursday.

[NJFunk]

Can anyone confirm or disconfirm this problem I'm having with the MT? Maybe it's not a problem at all but it's certainly "an issue".

When I record via S/PDIF the MT sets the sample rate to auto which I understand because the ADC should supply the sample rate and the MT will use whatever it gets.  My problem is that the MT seems to always assume that the ADC will send it 96kHz so my estimated recording time is always very short.  I use a 6GB Hitachi microdrive and when recording at 16/44.1kHz via S/PDIF, I only get about four hours of recording time.  If I switch to the 1/4" TRS inputs it will give me nine hours of recording time.

What is going on?

I have had this problem.  When you format the media, the microtracker sets the available time to the bit depth and sample rate in your settings when the input source is analog.  To get it to calculate correctly, change your input to one of the analog inputs, then set the bit depth and sample rate to what you will be receiving digitally, then reformat the card, then set the input back to SPDIF.

[alienbobz]

No clue what it means. I have the same problem too with 24/48 files. I usually just press "No" and track out my wav. Doesn't seem to be a problem.

[rodeen]

This has happened since the MT came out.  The header is correct, just some zeros or garbage after the end of the data. 
Trust the header.

I don't know if this is necessarily a microTrack issue, but I've gotten it with both 1.2.3 and 1.3.3 firmwares. 

when I try to open a 24/48 wav file with cd wave I get this warning message:

File header reports a size that is different than the system reports.  Do you want to adjust the size? (Yes to override header, No to trust header, Cancel to abort)

What the hell does this mean?

[svenkid]

I don't know if this is necessarily a microTrack issue, but I've gotten it with both 1.2.3 and 1.3.3 firmwares. 

when I try to open a 24/48 wav file with cd wave I get this warning message:

File header reports a size that is different than the system reports.  Do you want to adjust the size? (Yes to override header, No to trust header, Cancel to abort)

What the hell does this mean?

I got this on my last recording, and Im still running the first firmware update

[F.O.Bean]

as others have mentioned, the auto-split featute doesn't really meet our needs.  it only took 5-9 seconds to stop a file and start a new one anyway, so nothing has changed.  myself, I'm never going to let it autosplit, because it might happen during a song.  I'm going to continue to do it manually, so that I know the split will happen between songs.  I guess it's a step in the right direction, but it really does need to be seamless...

no doubt, they fix that seamless split and i might be tempted to buy one

[bconnolly]

I think everyone has that "problem" with the available recording time. I think either way (s/pdif or trs) you should be able to get 9 hours at 16/44.1 even if the available recording time screen says 4 hours. When you are recording, does it say 3 hours? That should be the right time for 16/44.1 (3 hours @ 16/44.1 = 2 GB).

Ok I just wanted to make sure it wasn't an isolated problem (sorry... i try to keep up on all the quirks but I miss a few).

So the time remaining on the recording screen is the time remaining for that file and if you start a new file, that counter will reset?

Yeah the time is for that one file. If you stop the recording and start a new one, the time should reset itself. Either it will be another 2GB or if will be the space left (if you have less than 2GB left on your card, it will show the time remaining for the bit/sample rate you are using).

Edit: Did you use the new firmware last night? How did it go? I plan on using it on Thursday.

I did use the new firmware and it worked great.  Didn't run at 24/48 like I wanted to just because I didn't want to fuck up and miss some of the headliner's set.

[Roving Sign]

This has happened since the MT came out.  The header is correct, just some zeros or garbage after the end of the data. 
Trust the header.

I don't know if this is necessarily a microTrack issue, but I've gotten it with both 1.2.3 and 1.3.3 firmwares. 

when I try to open a 24/48 wav file with cd wave I get this warning message:

File header reports a size that is different than the system reports.  Do you want to adjust the size? (Yes to override header, No to trust header, Cancel to abort)

What the hell does this mean?

FWIW - the JB3 files do the same thing in CDWave...dont think its the MT - something in CDWave

[mwz]

I don't know if this is necessarily a microTrack issue, but I've gotten it with both 1.2.3 and 1.3.3 firmwares. 

when I try to open a 24/48 wav file with cd wave I get this warning message:

File header reports a size that is different than the system reports.  Do you want to adjust the size? (Yes to override header, No to trust header, Cancel to abort)

What the hell does this mean?

http://taperssection.com/index.php?topic=53348.0

[china_rider]

FWIW - the JB3 files do the same thing in CDWave...dont think its the MT - something in CDWave

Guess I am lucky... never had this with either the JB3 or the Microtrack... Hoping I did not just jinx myself.

[bconnolly]

FWIW - the JB3 files do the same thing in CDWave...dont think its the MT - something in CDWave

Guess I am lucky... never had this with either the JB3 or the Microtrack... Hoping I did not just jinx myself.

I hadn't had that error either. Until just now.  I think if you just transfer a file straight from the MT to CD Wave without editing it in a separate app (like Audacity or Wavelab) then it will throw this error at you.  That's my theory at least.

[china_rider]

FWIW - the JB3 files do the same thing in CDWave...dont think its the MT - something in CDWave

Guess I am lucky... never had this with either the JB3 or the Microtrack... Hoping I did not just jinx myself.

I hadn't had that error either. Until just now.  I think if you just transfer a file straight from the MT to CD Wave without editing it in a separate app (like Audacity or Wavelab) then it will throw this error at you.  That's my theory at least.

That could be.... I always transfer then open in Audition or whatever else to do levels,etc before splitting.  Think you hit the nail on the head.

[balou2]

FWIW - the JB3 files do the same thing in CDWave...dont think its the MT - something in CDWave

Guess I am lucky... never had this with either the JB3 or the Microtrack... Hoping I did not just jinx myself.

I hadn't had that error either. Until just now.  I think if you just transfer a file straight from the MT to CD Wave without editing it in a separate app (like Audacity or Wavelab) then it will throw this error at you.  That's my theory at least.

That could be.... I always transfer then open in Audition or whatever else to do levels,etc before splitting.  Think you hit the nail on the head.

I coule be wrong, but when I try renaming a file that I transferred direct from the Mictotrack, without opening any other processing software, I get a 'read-only' message.  When I transfer, open with an application, then rename, there are no issues.  Either way, it's a simple workaround.