search for: usherwood

> You can ask. A bug report with priority 'enhancement' is probably the > best way to do that. I'd consider it. Thanks for your help, Michael. I have entered this as an enhancement request. <p>Also, for the record, I originally made this comment: > I am actually trying to get OggEnc up and running nicely with > AudioGrabber, but so far I no joy I

Hi, When I encode a file, with the command line (for example): oggenc h:\wavs\abc.wav -a sunshine as expected, it creates a file h:\wavs\abc.ogg. However, adding the '-t' command line option: oggenc h:\wavs\abc.wav -a sunshine -t MrSunny causes it to now create a file called MrSunny.ogg This behaviour could be expected if I had used the '-n' option, but I have not, so

I have noticed that when playing OGGs in Winamp, the bitrate displayed is always much higher than the average bitrate of the file. This was using the plugin that comes with Winamp v2.80 (v1.2 b7) For example, the latest oggenc encoded a song to 77kbps - I verified that this matched the filesize correctly. Apart from the first and last few seconds of the song, Winamp always displays between 85 -