[BitPim-devel] Re: [bitpim-cvs-checkins] bitpim conversions.py,1.2 1,1.22 midifile.py,1.2,1.3

[d***@netzero.com]

What is the actual reason behind making this change?

pvconv (version 3.0 for Windows) just would not accept an output file name:

pvconv in.wav out.qcp
ERROR: Error opening file: No such file or directory

while:

pvconv in.wav

works fine and produces in.qcp. Maybe you have a different version of pvconv that works better. I agree, the work-around is ugly.

-Joe Pham


______________________________________________________________________
Speed up your surfing with NetZero HiSpeed.
Now includes pop-up blocker!
Only $14.95/month -visit http://www.netzero.com/surf to sign up today!

[Roger Binns]

Post by d***@netzero.com
works fine and produces in.qcp. Maybe you have a different version of pvconv
that works better. I agree, the work-around is ugly.

Ah, it all becomes clear. I am actually using version 2 of pvconv.exe
that does work correctly. I used filemon from sysinternals.com to
try and see if it was opening something stupid, and it doesn't even
try. This simply looks like a pure coding error in command line argument
parsing. Using ltrace on Linux I was able to figure out that what
actually happens is it tries to open a zero length filename for
the second file.

I couldn't find any way of working around the problem through command
line arguments. The argument parsing is terrible - you can put "-v"
anywhere!

Roger

[d***@netzero.com]

Post by Roger Binns
I couldn't find any way of working around the problem through command
line arguments.

Any suggestions?

-Joe Pham



______________________________________________________________________
Speed up your surfing with NetZero HiSpeed.
Now includes pop-up blocker!
Only $14.95/month -visit http://www.netzero.com/surf to sign up today!

[Roger Binns]

Post by d***@netzero.com

Post by Roger Binns
I couldn't find any way of working around the problem through command
line arguments.

Any suggestions?

Nope. I was trying things like giving other redundant command line
arguments, wierd quoting etc. They just have plain buggy code.

Roger