2.3.0: too finicky?
Posted: Wed Jul 28, 2010 5:48 am
Hi,
There's a completed download Alfa. Say, MyDownloads/Alfa/alfa1.m4b. Since my player can't play m4b, I converted it to mp3: MyDownloads/Alfa/alfa1.mp3, leaving m4b file intact. The new file used to be ignored, but as soon as I upgraded to qBittorrent 2.3.0, the client somehow created a new Alfa download from scratch: MyDownloads/Alfa/alfa1.m4b, right next to the old one (MyDownloads/Alfa/alfa1.m4b(+alfa1.mp3) :shock: ), marked with [!]. Is this behavior a feature (I'd prefer the old tolerant way)? Is it optional?
System: Archlinux, i686
There's a completed download Alfa. Say, MyDownloads/Alfa/alfa1.m4b. Since my player can't play m4b, I converted it to mp3: MyDownloads/Alfa/alfa1.mp3, leaving m4b file intact. The new file used to be ignored, but as soon as I upgraded to qBittorrent 2.3.0, the client somehow created a new Alfa download from scratch: MyDownloads/Alfa/alfa1.m4b, right next to the old one (MyDownloads/Alfa/alfa1.m4b(+alfa1.mp3) :shock: ), marked with [!]. Is this behavior a feature (I'd prefer the old tolerant way)? Is it optional?
System: Archlinux, i686