Please have the option to keep the converted files and working file set on the same as source file's drive within the source file's folder.
I have 4 low bandwidth Hauppauge PCIe 1x TV tuners operating on C: and separate tuners with huge bandwidth on F: and i: drives. Trouble is that MCEBuddey 2.3 release 13 x64 puts all converted files onto C: thereby overloading that drive while having lots of space available on both F: and i:.
The F: and i: are removable storage USB 3.0: 1 Terabyte and 4 Terabyte HDDs that I migrate from separate over-the-air (OTA - antenna ATSC receiver/PVR) set top boxes (Mediasonic Homeworx hw150pvr). The originating ATSC broadcast station has complete control over the high bandwidth used so is not a user-configurable thing whereas the SD low bandwidth Hauppauge generated mpeg-2 .ts files are much smaller by comparison to the Mediasonic mpeg-2 .mts files.
I have MCEBuddy 2.3 set to remove original files so that the original F: and i: source HDD will end up with even more free space available--why not use that?
Comments: Fxed in newer versions
I have 4 low bandwidth Hauppauge PCIe 1x TV tuners operating on C: and separate tuners with huge bandwidth on F: and i: drives. Trouble is that MCEBuddey 2.3 release 13 x64 puts all converted files onto C: thereby overloading that drive while having lots of space available on both F: and i:.
The F: and i: are removable storage USB 3.0: 1 Terabyte and 4 Terabyte HDDs that I migrate from separate over-the-air (OTA - antenna ATSC receiver/PVR) set top boxes (Mediasonic Homeworx hw150pvr). The originating ATSC broadcast station has complete control over the high bandwidth used so is not a user-configurable thing whereas the SD low bandwidth Hauppauge generated mpeg-2 .ts files are much smaller by comparison to the Mediasonic mpeg-2 .mts files.
I have MCEBuddy 2.3 set to remove original files so that the original F: and i: source HDD will end up with even more free space available--why not use that?
Comments: Fxed in newer versions