title
Products            Buy            Support Forum            Professional            About            Codec Central
 

AACPlus v.2 Bitrate problems

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tcbb

    • Mar 2007
    • 18

    AACPlus v.2 Bitrate problems

    I'm setting the DbpowerAMP converter to encode a 44.1 16 bit WAV to AAC at 48kbps "Force HE V2" , however the files generated all come out at 52kbps, why is this happening? I need 48kbps.
  • Spoon
    Administrator
    • Apr 2002
    • 44574

    #2
    Re: AACPlus v.2 Bitrate problems

    It could be reporting the size wrong, where the file is 48kbps.
    Spoon
    www.dbpoweramp.com

    Comment

    • tcbb

      • Mar 2007
      • 18

      #3
      Re: AACPlus v.2 Bitrate problems

      I must admit im a bit new to ACC and dBpowerAMP, very cool app by the way , however the incorrect bitrate is reported in both the properties info when I right click the file as well as displayed when the file is played back in Winamp. In fact when Winamp starts the playing the file , it reports 49kbps, then jumps to 51kbps. Im using the CBR option.

      What might be causing this?

      Comment

      • Spoon
        Administrator
        • Apr 2002
        • 44574

        #4
        Re: AACPlus v.2 Bitrate problems

        It could be the nature of neros encoder that cbr is really a constrained vbr.
        Spoon
        www.dbpoweramp.com

        Comment

        • Deano
          dBpoweramp Enthusiast

          • Jan 2006
          • 130

          #5
          Re: AACPlus v.2 Bitrate problems

          Exactly, as far as I am aware Nero's encoder does not do "true" constant bitrate files. I am sure I read this on HydrogenAudio, but I could not seem to find where.

          Comment

          • tcbb

            • Mar 2007
            • 18

            #6
            Re: AACPlus v.2 Bitrate problems

            Thanks for the replies on this one, I ended up Using the Winamp based codec that I found on this forum as a solution, that working great fo my needs.

            However I now have an entirely different issue using the "RUN EXTERNAL" action.
            see this post: http://forum.dbpoweramp.com/showthread.php?t=12508

            Thanx!

            Comment

            Working...

            ]]>