Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Weird problem with Audition 1.5

New Here ,
Apr 08, 2020 Apr 08, 2020

Hi,

 

I'm using a really old version of Adobe Audition (1.5) on both Windows 7 and 10. It does everything I need but today I had a really odd experience. An MP3 I was importing is 52:12 in length and shows that way in file listings and when playing in Winamp and other programs. However, when I import it into Audition, it's only 50:09. While there's silence at the end of the file, it cuts off in the middle of audio, plus I've never known Audition to skip over silence so I doubt that's related. The audio is 82 Kbps, 48000 Hz and was created from a Facebook video. I hope there are enough clues here for someone to figure out what could be causing this. I appreciate any insight.

 

TOPICS
Import , Version 3 and earlier
1.4K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 08, 2020 Apr 08, 2020

Not really enough clues, I'm afraid. If you open it and look at the metadata in Audition, what does that say? I don't have Audition 1.5 installed on anything any more, so I can't give you steps to get at this, although I'm sure it's possible to find without too much difficulty. The usual cause of indicated time being in error is when MP3 files are VBR rather than CBR - it's almost impossible to estimate the length of a VBR file without actually decoding it, whereas with a CBR it's pretty straightforward to calculate. As for the cutting off - well it shouldn't do that, certainly. Without actually looking at the file itself, I can't really comment on that, I'm afraid.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 08, 2020 Apr 08, 2020
LATEST

You gave me enough info to solve the problem. It was indeed a VBR issue. Once I changed that to CBR and imported at that point, the time was correct. Thanks!

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines