lossyWAV Development
Reply #957 – 2008-03-19 02:24:50
1. Strange results (at least to a non-technical person) I've been running a few tests with WavGain & lossyWAV, taking into account what jesseg and 2Bdecided have said. I had thought that "1.wav" encoded via FLAC Drop then decoded to WAV would give me "1.lossy.wav" (i.e. the result of the lossyWAV processor. (for why I was doing this -- see 2 below) But when I encoded 1.lossy.wav (without any other processing) back to FLAC using foobar and latest flac.exe (1.2.1) at -5, the file was much larger (522kbps) than the FLAC Dropped 1.lossy.flac (475kbps). Can someone explain why? Additionally, I copied the 1.lossy.wav" and WavGained it and then encoded that to FLAC using foobar and flac.exe (1.2.1) and the file was much, much larger (628kbps). I'm assuming this is to do with WavGain undoing some of the work done by lossyWAV?2. Request for help: I was trying to get foobar to convert to lossy.wav (rather than direct to lossy.flac) but kept getting a can't flush file error. Error flushing file (Object not found) : file://C:\Documents and Settings\[...my edit...]\test1.lossy.wav I'd set it up as per wiki. The only difference was the batch file, which I edited to leave out the FLAC encoding (though I didn't really know what I was doing ). @echo off D:\lossywav\lossyWAV %1 %3 %4 %5 %6 %7 %8 %9 -below -nowarn -quiet Can someone tell me where I've gone wrong. Thanks C.