I've just uploaded all versions and source to Rarewares. This fixes the problem that some people were encountering where the quality setting was functioning only in integer increments.

He-he. Thanks. I though I was the only one had that problem.
I have some suggestions on this nice tool. Can I speak it here?

well, if you're thinking of making a suggestion, I might as well make one.

I would like the option to create folders based on artist/album and place the files in the appropriate folder when encoding many files at once. Perhaps an extra option in the auto tagging setup?

I do it manually right now, but I keep thinking it would be nice if a program did it for me.

That said, I absolutely love oggdrop. Great work!!

Suggestions are always welcome. Can't promise what will get done, or when, but by all means keep them coming.

1. I would like 'quality' status duplicate in any corner of window using bigger, bolder, red font.
2. Drop interface is good, but why not to add simple 'add folder' or 'add files' option
3. I would like to see bits distribution while encoding (if it is possible)
4. The poor fish is going to have vertigo , you could make it swim at speed appropriate to quality.

Old suggestions:

- rehuff implementation
- ssrc resampling

Thanks! It works fine now.

Hurray ! it works now. Thank you John ! Thank you very much

By the way, what was the problem ?

I'm almost too embarassed to say!!

I completely overlooked the role reversal of '.' and ',' as numeric delimeters in many countries!!

One little bug in oggDropXPd 1.7.5

Hi John,


First of all, sorry for my poor english.

Now, the problem is with the tagging feature, do this:

- Choose a separator, I use " - " //space - space
- Then in the "encoded by" field: oggDropXPd v1.7.5 LibVorvis 1.0.1
- Fill the other fields and accept until here thats all write, but if you go to the tagging properties again the "encoded by" field turns:

"oggDropXPd v1.7.5 LibVorvis 1.0. - "

if the separator is " + "

"oggDropXPd v1.7.5 LibVorvis 1.0. + "



If you write in this field somethig with more than 32 characters, the separator "overwrites" the 32+ characteres

The first time you go to the tagging properties everything works ok when you encode, but if you go back to the tagging porperties the encoded by field is overwritten, and the encoded file does not have the correct tag!

You're quite correct. It was limited to 32 chars. I've increased it to 64. I'll upload again during the course of today and post when the new compiles are available. I'll keep the same version number as it seems unnecessary to uplift the version number for such a small change.

All new compiles are now available that allow upto a 64 char "Encoded by" tag.

Version number is the same, it just carries today's date in the compile.

If you don't need the extra tag space, there is no reason to d/l this version. It is, in all other respects, absolutely identical to the first version.