Hi.
I believe I've found a bug in oggdropXPd, but I'm not sure to whom or how to report it. I googled and searched rarewares to no avail.
Does anyone have any information on filling a bug report for oggdropXPd??
Thanks.
Post the bug here so other people can confirm it.
And so I can look into it if it is real.
Great! Here is the problem I'm having. I'm a classical music fan (and no that isn't the problem ) and I have been using the unicode character for sharp (♯) and flat (♭) in my flac filenames when appropriate. When I use oggdropXPd (oggdropXPd V.1.9.0 using aoTuVb6.02) and drag-n-drop a flac file whose name contains one of these characters, I get this error "Cannot open input file "<filename>' error is Invalid argument (22)".
If I rename the file, removing the sharp or flat character, oggdropXPd works fine.
oggenc2 from the command line doesn't have this problem, so that has been my workaround. But I would really like it if oggdropXPd could handle flac filenames with these characters.
Thanks for looking into this!
Great! Here is the problem I'm having. I'm a classical music fan (and no that isn't the problem ) and I have been using the unicode character for sharp (?) and flat (?) in my flac filenames when appropriate. When I use oggdropXPd (oggdropXPd V.1.9.0 using aoTuVb6.02) and drag-n-drop a flac file whose name contains one of these characters, I get this error "Cannot open input file "<filename>' error is Invalid argument (22)".
If I rename the file, removing the sharp or flat character, oggdropXPd works fine.
oggenc2 from the command line doesn't have this problem, so that has been my workaround. But I would really like it if oggdropXPd could handle flac filenames with these characters.
Thanks for looking into this!
OK, thanks for the info. I'll look into this, but unless I find a resolution in the next couple of days, it'll have to wait until after I return on 2 May from an Easter trip to France.
Edit: This is a unicode issue and will not be trivial to resolve, so it will not happen until some time during the first half of May, at the earliest.
Wonderful. Don't hurry for a fix on my part...oggenc2 is working fine.
Thanks for all of your work on these ogg tools!