• VEGAS Pro

  Vegas captured audio file plays too fast

  Posted by John Romein on June 13, 2019 at 10:45 pm

  I captured an audio file in Vegas Pro 10 from a Tascam DAT player via an Echo Layala24 capture card. This card is capable of 96kHz 24bit audio.

  We set up Vegas to play back the audio as it recorded and this played fine. We can play the file back on the PC (Vegas, VLC, etc) with no problems. However, when we change the Echo Layal24 console from using the SPDIF to the internal “input clock” the captured file plays at about double speed. We tried the audio file on a few other PC’s and we have the same speed problem. So, it appears that switching the “input clock” via Echo Layal24 console switches the file playback speed.

  It the audio file being captured by Vegas missing something? Here’s a copy of mediainfo’s output from a sample file:

  General
  Complete name : R:\Business RAW\DAT\2019\Track 1 – 2.wav
  Format : Wave
  File size : 1.38 MiB
  Duration : 5 s 36 ms
  Overall bit rate mode : Constant
  Overall bit rate : 2 306 kb/s
  Encoded date : 2019-06-13 12:12:49

  Audio
  Format : PCM
  Format settings : Little / Signed
  Codec ID : 1
  Duration : 5 s 36 ms
  Bit rate mode : Constant
  Bit rate : 2 304 kb/s
  Channel(s) : 1 channel
  Sampling rate : 96.0 kHz
  Bit depth : 24 bits
  Stream size : 1.38 MiB (100%)

  Thanks, John

  John Romein replied 6 years, 11 months ago 2 Members · 4 Replies
• 4 Replies

• 

  George Dean

  June 13, 2019 at 11:07 pm

  John, can you post (upload) a sample file here, so we can do some testing?

  Best Regards……George
• 

  John Romein

  June 14, 2019 at 12:00 am

  Thanks George.

  Here’s the file I noted in the mediainfo previously:
  13436_track12.wav.zip
• 

  John Romein

  June 14, 2019 at 5:05 am

  Found something interesting….until now I’ve matched the Vegas project audio properties on the capture to the Echo Layal24 input, 9600 kHz, 24 bits. I left the input the same but changed the project audio projects to 48kHz , 24 bits and repeated the capture. Everything still worked fine on the capture PC, but this time the WAV file played fine on all the other PC’s too!

  Here’s the mediainfo for the 48kHz file:

  General
  Complete name : R:\Business RAW\DAT\2019\Track 1 – 4.wav
  Format : Wave
  File size : 1.51 MiB
  Duration : 10 s 960 ms
  Overall bit rate mode : Constant
  Overall bit rate : 1 153 kb/s
  Encoded date : 2019-06-13 17:14:26

  Audio
  Format : PCM
  Format settings : Little / Signed
  Codec ID : 1
  Duration : 10 s 960 ms
  Bit rate mode : Constant
  Bit rate : 1 152 kb/s
  Channel(s) : 1 channel
  Sampling rate : 48.0 kHz
  Bit depth : 24 bits
  Stream size : 1.51 MiB (100%)

  I’m puzzled, as we capture other inputs in 96kHz and have captured DAT in 96 kHz without any issues in the past. Why does this not work now?

  John
• 

  John Romein

  June 15, 2019 at 5:44 am

  I’ve done some further testing. We captured some reel-to-reel audio on the same PC. This time we set the Echo Layala24 capture card to use the “internal clock” instead of the SPDF “clock”. Capturing at 96kHz 24bits was no problem. The WAV file could be played back on any PC and different versions of Vegas…no speed up WAV file.

  What I noticed was that when we were capturing from the DAT player via the SPDF through the Echo Layala24 capture card using 96kHz 24bits and the Echo was set to use the SPDF clock….the file played fine in Vegas and VLC and Windows Media player. When we switched the input clock to internal on the Echo Layala24 console, the same WAV file played double speed. So, it appears that the changing of the input clock makes a diffence to the way the WAV file plays. Does anyone know why the input clock would impact how a WAV file is played?

  Cheers,
  John

Reply to this Discussion! Login or Sign Up