<![CDATA[Modartt user forum - Bug? Could not read the specified file]]> https://forum.modartt.com/viewtopic.php?id=4045 Tue, 06 Oct 2015 10:32:28 +0000 PunBB <![CDATA[Re: Bug? Could not read the specified file]]> https://forum.modartt.com/viewtopic.php?pid=939749#p939749 Sorry for the noise. I was using not an alias but a wrapper script, and this was indeed changing the current directory. Stupid :-)

]]> Tue, 06 Oct 2015 10:32:28 +0000 https://forum.modartt.com/viewtopic.php?pid=939749#p939749 <![CDATA[Re: Bug? Could not read the specified file]]> https://forum.modartt.com/viewtopic.php?pid=939748#p939748 I can't reproduce that, are you sure that your alias is not changing the current directory ?

]]> Tue, 06 Oct 2015 09:29:54 +0000 https://forum.modartt.com/viewtopic.php?pid=939748#p939748 <![CDATA[Bug? Could not read the specified file]]> https://forum.modartt.com/viewtopic.php?pid=939746#p939746 On my Linux commandline I frequently do things like (PIANOTEQ being an alias for my path-to-the-pianoteq-binary)

PIANOTEQ --headless --midi myfile.mid --wav myfile.wav

and this used to work perfectly. But today I tried again, and it doesn't work as expected anymore. The output shows pianoteq is working on a conversion of something, but without resulting in myfile.wav file.
Maybe a regression in Pianoteq 5.4.x ?

This is what I see (among others):

Could not read the specified file

I have found that it does work if I use a complete path like

PIANOTEQ --headless --midi /home/m.tarenskeen/Music/Midifiles/myfile.mid --wav /home/m.tarenskeen/Music/Wav/myfile.wav

This looks like a regression to me. Please let pianoteq search in the current working directory. BTW: 

--midi ./myfile.mid

doesn't work either.

]]> Tue, 06 Oct 2015 07:04:48 +0000 https://forum.modartt.com/viewtopic.php?pid=939746#p939746