Topic: JB3 user questionnaire - JB3 / CD-Wave message: "File header reports a size..."

[Brian Skalinder]

When opening JB3-recorded WAVs in CD-Wave, I get this 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)"

Anyone else get this message regularly?  I've gotten it for a while and finally dug into it a bit.  Looks like the JB3 adds 8 bytes of "junk" at the end of the files I record on the JB3.  Turns out, in either case - selecting Yes or No - CD-Wave strips the "junk" 8 bytes out of the WAV file.  Cool Edit Pro does the same, but without presenting a message.  I suspect all other WAV editors strip the "junk" as well.

So, questions for all you JB3 users so I can get a handle on when / how frequently this occurs:

[1]  Do you encounter the same message from CD-Wave when opening in WAVs recorded onto your JB3?  [ yes | no ]
[2]  Do you record digital- or analog-in on your JB3?  [ digital | analog ]
[3]  I'm using firmware v.XXX:  [ 1.20.06 | 1.32.02 | 1.40.06 ]
[4]  I'm using CD-Wave v.X:  [ 1.82 | 1.90 | 1.91 | 1.92 | 1.93.3 | 1.94b3 ]
[5]  I've encountered similar messages in other audio editors:  [ Adobe Audition | Cool Edit Pro | Soundforge | Wavelab | Other (please list) ]

Just trying to get a handle on how widespread this issue is, etc.

[hexyjones]

Same results for both of my JB3s...

CD Wave v1.93.3

[1]Do you encounter the same message from CD-Wave when opening in WAVs recorded onto your JB3?

yes

[2]Do you record digital- or analog-in on your JB3?

digital and analog - same result

[3]I'm using firmware v.XXX:

[1.32.02]

[4]I've encountered similar messages in other audio editors:

[error seems unique to CD Wave]

[Brian Skalinder]

Yup, thanks corkscrew - added CD-Wave version.  I'm guessing all the other WAV editors strip the junk data behind the scenes instead of presenting the message.  Curious to see how others respond.  Thanks for the input!

[hexyjones]

might be a long shot - but - should we notate wether the digital feed is 16 or 24 bit?

[Brian Skalinder]

might be a long shot - but - should we notate wether the digital feed is 16 or 24 bit?

We could, but I wouldn't expect anyone to answer 24-bit since the JB3 is a 16-bit device that truncates 8 bits.  Though if people are, in fact, sending the JB3 24-bits I'm curious to hear if they encounter the same issue.  I'm guessing yes.

[hexyjones]

might be a long shot - but - should we notate wether the digital feed is 16 or 24 bit?

We could, but I wouldn't expect anyone to answer 24-bit since the JB3 is a 16-bit device that truncates 8 bits.  Though if people are, in fact, sending the JB3 24-bits I'm curious to hear if they encounter the same issue.  I'm guessing yes.

right - the variable being the truncation of bits...some users are sending a 16 bit signal...others are feeding 24 and just living with the truncation

...could that affect the JB3s disc write routine/program...which might be expecting a natural 16 bit output...?

Does the JB3 "know" it's truncating?

[twatts (pants are so over-rated...)]

[1]  Do you encounter the same message from CD-Wave when opening in WAVs recorded onto your JB3?  [ yes | no ]

Yes.  I get it every time with both my JB3s.


[2]  Do you record digital- or analog-in on your JB3?  [ digital | analog ]

Digital, though I do remember getting it the first few times running analog.


[3]  I'm using firmware v.XXX:  [ 1.20.06 | 1.32.02 | 1.40.06 ]

1.32 on one, 1.40 on the other.


[4]  I'm using CD-Wave v.X:  [ 1.82 | 1.90 | 1.91 | 1.92 | 1.93.3 | 1.94b3 ]

Not sure


[5]  I've encountered similar messages in other audio editors:

I use SF5.0 and have never encountered anything or any problems.



On another note, anyone encounter channel swapping, or the pop at the beginning of every recording???

Thanks,

Terry

[hexyjones]

On another note, anyone encounter channel swapping, or the pop at the beginning of every recording???

I've heard others mention this...and it might be a bigger problem than we think...
For reference...I should get in the habit of making some sort of reference noise on one channel...

Wish I had one of those clickers...

[Ed.]

[1]  Do you encounter the same message from CD-Wave when opening in WAVs recorded onto your JB3?  [ yes | no ]
I've had this happen before, but can't say its happen recently.  when it happened before it wasn't constant, just sporatic.

[2]  Do you record digital- or analog-in on your JB3?  [ digital | analog ]
digital, via optical mod V3

[3]  I'm using firmware v.XXX:  [ 1.20.06 | 1.32.02 | 1.40.06 ]
1.40.06

[4]  I'm using CD-Wave v.X:  [ 1.82 | 1.90 | 1.91 | 1.92 | 1.93.3 | 1.94b3 ]
don't know for sure, cuz i'm at work.  however, i do believe i have a different version on my laptop then i do at home, but both as of late have been fine.

[5]  I've encountered similar messages in other audio editors:  [ Adobe Audition | Cool Edit Pro | Soundforge | Wavelab | Other (please list) ]
none that i've noticed.

i do get pops and clicks through out my recording tho if i don't format/disc cleanup before i go taping.  actually i don't know if thats from the cable or fromt he hdd befing full of junk, but i take better care of both of those now and haven't had a problem in quite sometime.

i've also noticed that when i pause my recording my channels on the jb3 swap, at least the levels on the screen do, never paid enuf attention to see if they do on the recording.  once i noticed it happened once, i never did it again.

[bhtoque]

Do you encounter the same message from CD-Wave when opening in WAVs recorded onto your JB3?   yes

Do you record digital- or analog-in on your JB3?   digital

I'm using firmware v.XXX: I have 2 JB3's one of each 1.32.02  1.40.06 both have same problem

I'm using CD-Wave v.X:  Not sure off top of my head

I've encountered similar messages in other audio editors:  No, I use cool edit pro, and get no error messages. It must fix the problem though, because I only see it if I open in cd wav first.

I've noticed the channel swap issue with 1.40.06. Not just when I pause, but when I stop and start a new file (like second set) Never really caught it till the Bad Plus shows I did where it was so obvious on my svu-1 that the drums were on the left not right channel.

I have a feeling the junk is the pop you get when you start the recording. I usually record 5 seconds of crowd, then pause it till the band comes on stage so I can clip it off without worry.

JAson

[Humbug]

Never had this issue, so heres the questionnaire:

[1]  Do you encounter the same message from CD-Wave when opening in WAVs recorded onto your JB3?  [ no ] I never open with CD Wave - the file always get edited first.

[2]  Do you record digital- or analog-in on your JB3?  [ analog ]

[3]  I'm using firmware v.XXX:  [ 1.20.06 | 1.40.06 ] Both - I have two Nomads

[4]  I'm using CD-Wave v.X:  [ 1.93.3 ] - I think

[5]  I've encountered similar messages in other audio editors: N/A

[F.O.Bean]

i always get that lil click on my tapes, i simply open the wav in cdwave first, thgen i put a marker at the beginning(after the click) and the end of the set so there are no known SBE also

[Karl]

On another note, anyone encounter channel swapping, or the pop at the beginning of every recording???

Thanks,

Terry

I have definitely had channel swapping problems, but only after leaving the unit in pause for a period of time.  Just don't leave the unit in pause.  If you need to stop, just stop the recording completely and start over each time.  We all get the pop at the beginning of recordings, just plan for it and trim it out in post.