(small) bug in Besweet GUI 0.6b51 ?

[theReal]

I hope this isn't old news, but it seems that BesweetGUI writes a wrong Besweet commandline when you want to convert from one frame rate to another.

The text in besweetGUI says "convert from x to y", but then the commandline is
BeSweet -core( -input "g:\test.wav" -output "g:\test2.wav" -2ch ) -ota( -r y x )
and the Besweet Dos-Window says "Source Frame Rate: y" and "Dest. Frame Rate: x"
I wanted to say that the source is x and the destination should be y, that's why I was filling in "convert from x to y"
Am I getting something wrong here, or is it a bug?

Sorry, I don't have log file right now - but in this case I think it wouldn't help (there's obviously nothing wrong with Besweet, only the values are entered in the wrong place in the commandline. Or, as I said before, maybe I don't get the meaning of "convert from x to y" correctly...)

[DSPguru]

i know it sounds weird, but it's okay.
maybe pacohaas can explain.. ;)

[theReal]

Sorry, I wasn't even using the latest version of BesweetGUI (I had just copied the new files to the old folder and didn't realize that the link still started the b51...).

Now, I'm very confused, because the newest version of BesweetGUI, b61, does it the other way round. So it seems I've reported an old bug that has already been corrected in the latest version (my fault, sorry!). But then, why haven't you posted your smilies that say "Read the FAQ" and "use latest version"? (like you always do when someone asks silly questions ;))
Instead you said that the behaviour of b51 is ok - was this just irony?

btw - I'm trying to convert a wave file from 30.068 fps to 29.970 fps - is this possible at all? The help file says that some non-standard conversions will not work...

EDIT: It didn't work with 30068/29970, but it worked with 1004/1001. I hope this ratio is close enough (what's it with the 1001 anyways?)

[DSPguru]

i haven't noticed you submitted a bugreport on an old product.
you know you shouldn't.. ;)