I would have though so, but e.g.
Error converting to Windows Media Audio 10, 'xxx.flac' to 'xxx.wma'
md5 did not match decoded data, file is corrupt.
leaves an output file, condition unknown.
I would have though so, but e.g.
Error converting to Windows Media Audio 10, 'xxx.flac' to 'xxx.wma'
md5 did not match decoded data, file is corrupt.
leaves an output file, condition unknown.
There is no file? if not overwriting then even the corrupt file should be left after conversion.
Spoon
www.dbpoweramp.com
Yes
Spoon
www.dbpoweramp.com
Thanks, but no workaround seen there.
Corrupt output files are a nightmare in well-managed projects. They wreck build management systems like MAKE and pollute data sets. Compliant command-line tools e.g. compilers leave either good output files or none.
Please do consider remedying this. I suggest CoreConverter.exe simply ensures that in event of error, no output file is left. Even if there was one present previously. Also, from Microsoft Command Line Standard http://technet.microsoft.com/en-us/l.../ee156811.aspx
This would be a big improvement and make the program much more attractive to developers of production-grade integrations.Required:
* Error messages (as well as VERBOSE and DEBUG messages) must be written to STDERR.
* Commands must terminate with an exit code indicating success (0) or failure (non-zero).
Thanks.
Last edited by chrisjj; 06-25-2011 at 06:37 PM.
Please ignore that - I see http://www.dbpoweramp.com/developer-cli-encoder.htm says error messaes already optionally go to STDERR.
The do, normally nothing would go to stderr
STDERR if supplied is the process of getting error messages out of the converter.
Spoon
www.dbpoweramp.com
It is not always, a calling program can pass NULL handles.
Spoon
www.dbpoweramp.com
Perhaps for the next version.
Spoon
www.dbpoweramp.com
Copyright © illustrate 2024, All rights reserved