VideoHelp Forum

Our website is made possible by displaying online advertisements to our visitors. Consider supporting us by disable your adblocker or Try ConvertXtoDVD and convert all your movies to DVD. Free trial ! :)
+ Reply to Thread
Results 1 to 6 of 6
Thread
  1. Member
    Join Date
    May 2009
    Location
    United States
    Search Comp PM
    Topic. Got an AAC track extracted from a rather poorly-encoded MKV. MKVExtract recognizes it as AAC. So does MediaInfo. But the latest Ffmpeg doesn't know what to do with it, and neither does the AAC filter for Premiere Pro. Just trying to convert it to WAV for editing.

    I'm not used to running into scenarios with audio where there's literally nothing left for me to do but post asking for help. But hopefully somebody will have an idea what I might try.
    Quote Quote  
  2. Maybe it's corrupted ? Does it play in a media player ?

    Did you try converting the audio while still in the mkv container, instead of extracting first ?

    You can try audacity or foobar2000
    Quote Quote  
  3. Member
    Join Date
    May 2009
    Location
    United States
    Search Comp PM
    Audacity doesn't know what to do with it, though I do grasp that this is because Audacity doesn't by default know what to do with AAC files and relies upon Ffmpeg to make it work (which in turn means it would never work in this case).

    Foobar2000 surprisingly does play the file correctly.

    So the question is... Will the fact that Foobar2000 can play the file eventually lead me to a way to convert it?
    Quote Quote  
  4. yes, foorbar2000 can convert/encode audio for sure. But I haven't used it in a few years so I'm probably not the best person to walk you through it

    for ffmpeg did you try specifying -f aac as input option ?

    ffmpeg -f aac -i input.ext .....
    Quote Quote  
  5. Member
    Join Date
    May 2009
    Location
    United States
    Search Comp PM
    Interesting. Using that syntax got Ffmpeg to play nice. Thanks.

    Past versions of Ffmpeg were able to recognize the stream without my specifying anything, or at least to guess based on the .AAC extension. I wonder why it was decided that this should be changed.
    Quote Quote  
  6. you probably have raw / headerless aac , so it can't identify it

    (but then how does foobar2k identify it... ? I don't know)

    or at least to guess based on the .AAC extension
    good point
    Quote Quote  



Similar Threads