IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
foobar2000 1.1.15 broke fooCDtect2.1?
SUPERCOOLMAN
post Oct 21 2012, 22:24
Post #1





Group: Members
Posts: 57
Joined: 11-April 06
Member No.: 29380



regression or new feature of the latest foobar2000?

1st failed scenario. fooCDtect result is "error"
fooCDtect 2.1 commandline: --output %d --mode 0 --tpath "D:\BB" --lfor 3 --lenc 2 --autodel
foobar2000 1.1.15 output directory: "D:\BB"

2nd failed scenario. fooCDtect result is "error"
fooCDtect 2.1 commandline: --output %d --mode 0 --tpath "D:\GG" --lfor 3 --lenc 2 --autodel
foobar2000 1.1.15 output directory: "D:\BB"

3rd failed scenario. fooCDtect result is "error"
fooCDtect 2.1 commandline: --output %d --mode 0 --tpath "D:\NG" --lfor 3 --lenc 2 --autodel
foobar2000 1.1.15 output directory: "D:\AA"

1st passed scenario. fooCDtect result is "CDDA-100%"
fooCDtect 2.1 commandline: --output %d --mode 0 --tpath "C:\GG" --lfor 3 --lenc 2 --autodel
foobar2000 1.1.15 output directory: "D:\BB"

2nd passed scenario. fooCDtect result is "CDDA-100%"
fooCDtect 2.1 commandline: --output %d --mode 0 --tpath "C:\GG" --lfor 3 --lenc 2 --autodel
foobar2000 1.1.15 output directory: "C:\CC"


after a few trail and error, it look like fooCDtect2.1's temp directory cannot be on D drive to work with foobar2000 1.1.15.

this only happens with recent foobar2000. I'm using foobar2000 1.1.15, but I didn't have any problem until I upgraded foobar2000 from 1.1.11 to 1.1.15 and everything else remain unchanged. I've checked that the patch changing GUI to Console was already done, but this shouldn't matter as changing temp directory to C drive works. any suggestion/help is greatly appreciated


========
added third failed scenario

This post has been edited by SUPERCOOLMAN: Oct 21 2012, 22:29
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 31st July 2014 - 01:47