title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Quality setting in CLI (aoTuV) Not working

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

    • Feb 2005
    • 37

    Quality setting in CLI (aoTuV) Not working

    I've got the CLI encoder pointed to oggenc.exe, and conversion works with no problems, except my quality selection is ignored. The string that I'm using is, as Spoon suggested:

    -q 4.35 -a "[IDArtist]" -t "[IDTrack]" -l "[IDAlbum]" -d "[IDYear]" -G "[IDGenre]" -N "[IDComment]" [InFile]

    I've tried every other possible integer after -q and invaribly the output file is the same size, with a nominal bitrate of 112 kbps (which corresponds to q3, strangely enough). Furthermore, none of the tags are preserved, despite the long string used.

    I originally used: -q 0 [InFile]

    It produced the same exact result. Evidently, my CLI is not getting read at all, and it's just doing some sort of default conversion.

    Any suggestions?
  • MikeCerm

    • Feb 2005
    • 37

    #2
    Re: Quality setting in CLI (aoTuV) Not working

    Hmm, I feel a bit like a moron. I seems that I've gotten it working by adding "oggenc" to the beginning of my string. Ok, I don't feel that stupid, because I thought the the Generic CLI codec would do that part for me.

    The Tags? Well, that's another issue entirely. It appears as though the files I was transcoding (APE -> Ogg) were not tagged at all. That explains why the tags weren't preserved: They weren't there in the first place.

    So, in the case someone else reads this and I'm not just talking to myself and answering my own questions, I will give you some advice: My initial insticts were right. Add the filename of the encoder to my original string, and it works, tags and all.

    The full string: oggenc -q 0 [InFile]

    Of course, feel free to subsitute your favorite quality in place of the 0. Now it will actually work.

    Comment

    Working...

    ]]>