Taperssection.com

Gear / Technical Help => Recording Gear => Topic started by: Kevin Straker on March 07, 2005, 01:54:35 PM

Title: JB3 recording at 48khz problem
Post by: Kevin Straker on March 07, 2005, 01:54:35 PM
I'm trying to transfer a show onto the drive on my JB3 from dat. The dat is recorded at 48khz. I'm running through a hosa odl and into the jb3 from my dap1. It seems to record fine, but after the show is saved, the time is shortened. It shrinks from 45:00 to 29:00. Sounds like a sampling rate issue, but the jb3 says it is recording at 48khz. In the Help portion of the JB3 manual is says that it will only do 44.1 khz. The FAQ says it will do 48khz. Do I have a setting wrong? Any help is apreciated.

Also, what is the "sync" function for in the recording screen?

Thanks-Kevin
Title: Re: JB3 recording at 48khz problem
Post by: The Kilted Taper on March 07, 2005, 02:00:23 PM
Not sure were the problem is here, but the JB3 will record in 48. It's one of the options when you record via an analog signal. Have you tried transfering the file to a computer and see what's happening, or are you just going off the time?
Title: Re: JB3 recording at 48khz problem
Post by: Kevin Straker on March 07, 2005, 02:03:34 PM
Not sure were the problem is here, but the JB3 will record in 48. It's one of the options when you record via an analog signal. Have you tried transfering the file to a computer and see what's happening, or are you just going off the time?

Yep, I'm going by time. I have it on my pc and will check it out later. FWIW, I'm using the opti in.

Title: Re: JB3 recording at 48khz problem
Post by: hexyjones on March 07, 2005, 06:35:07 PM
Just to be sure - you did see your levels moving and such? (during the transfer) and are certain you had "Optical" selected as the source...? The JB3 should just sync up to whatever the sampling rate of the source is...

If you record with the optical input - with NO - optical signal...the time will elapse very slowly - like 1 second will show on the display for every 5 seconds of recording...

The "sync" function - might be for cutting a cd into tracks as it is recorded - dividing it at the silent parts betweeen tracks...not sure what it does...but you might want to make sure it is OFF...
Title: Re: JB3 recording at 48khz problem
Post by: Todd R on March 07, 2005, 08:11:50 PM
45 to 29 seems drastic.  Nevertheless, I've had problems transferring DATs to the JB3 when I started the DAT after the JB3.  You should start the DAT going and get past any leader tape if need be, to get the 48k subcode info going before starting the JB3 so that it reads it right.  When I've started the JB3 before the DAT, it has recorded at 44.1k even though it said it was recording at 48k.
Title: Re: JB3 recording at 48khz problem
Post by: F.O.Bean on March 07, 2005, 09:27:20 PM
bingo, i didnt know how to say that that well todd, that should work if it was originally recorded at 48k
Title: Re: JB3 recording at 48khz problem
Post by: todd e on March 08, 2005, 10:15:55 AM
45 to 29 seems drastic.  Nevertheless, I've had problems transferring DATs to the JB3 when I started the DAT after the JB3.  You should start the DAT going and get past any leader tape if need be, to get the 48k subcode info going before starting the JB3 so that it reads it right.  When I've started the JB3 before the DAT, it has recorded at 44.1k even though it said it was recording at 48k.

i have had the jb3 read 44k when i know it is in fact receiving a 48k file.  the way to fix is to change the header file with cdwave or wavelab.  then the timing is corrected.
Title: Re: JB3 recording at 48khz problem
Post by: Kevin Straker on March 08, 2005, 01:50:13 PM
45 to 29 seems drastic.  Nevertheless, I've had problems transferring DATs to the JB3 when I started the DAT after the JB3.  You should start the DAT going and get past any leader tape if need be, to get the 48k subcode info going before starting the JB3 so that it reads it right.  When I've started the JB3 before the DAT, it has recorded at 44.1k even though it said it was recording at 48k.

i have had the jb3 read 44k when i know it is in fact receiving a 48k file.  the way to fix is to change the header file with cdwave or wavelab.  then the timing is corrected.

Thanks for the advice. FWIW, the time goes along fine until the wave file is saved on the jb3. It counts up to 45:00, and after it saves the file the time changes to 29:00. I'll try the wavelab fix after work and report back. Thanks alot and +t's for the help all around. I have lots of dats that I'd like to transfer and for now this seems like my best bet.