arne;223224 Wrote:
> Found the reason for the foobar problem, but not the solution: HDCD.EXE
> only works if the parent process is cmd.exe or command.com
> It can't be run by another application. The only possible solution so
> far is to start it via cmd.exe/command.com:
>
> cmd.exe /c ""{path to tool}hdcd.exe"" < {source} > {dest}
>
> This works fine in Directory Opus. But there was some syntax problem
> with Foobar. I don't know how to fix this, but I think it's not very
> complicated, if you have programming skills.
>
> edit: ok, it now works with foobar. but there should be a better
> solution then the cmd.exe-workaround
Sorry, just seen this. I think what's going on is that a shell
(cmd.exe) is required to interpret the stdin and stdout redirections.
I'm not sure if this is quite a workaround, I'd guess it's probably the
approved way to deal with this sort of situation.
Nevertheless, I'll probably do some refinement, which'll almost
certainly allow the ability to specify an in-file and an out-file,
although they'll still default to stdon and stdout.
--
cjk32
------------------------------------------------------------------------
cjk32's Profile: http://forums.slimdevices.com/member.php?userid=5151
View this thread: http://forums.slimdevices.com/showthread.php?t=32967
_______________________________________________
audiophiles mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/audiophiles
