I don't have Windows Terminal installed to do a direct comparison, but I haven't had any problems testing with the normal windows Command Line.
If I create an External Tool entry for
cmd and use these parameters:
/K cd /d "<Path>" && echo "<Path>" && echo <Path> && echo "<URL>" && echo <URL> && ffprobe -i "<URL>"
everything works as expected. This opens a command window in the file's folder, displays its folder and path and opens it in the
ffprobe command line program.
"M:\Music\B\Beatles, The\1964.1 - A Hard Day's Night\"
M:\Music\B\Beatles, The\1964.1 - A Hard Day's Night\
"M:\Music\B\Beatles, The\1964.1 - A Hard Day's Night\01 - A Hard Day's Night.flac"
M:\Music\B\Beatles, The\1964.1 - A Hard Day's Night\01 - A Hard Day's Night.flac
The output suggests MusicBee just passes the folder and files path as is, without any special quote processing.
If I enclose the path in quotes they're included in the output. If I leave them off, they're not.
I don't see MusicBee treating "<Path>" as a literal string.
Probably a silly question, but you are putting the parameters in the
parameters field, not with the
application path?
Bee excellent to each other...