This does offer a graphical 'waveform' display that helps to locate cuts but does not require a wav temp file - or at least not the huge files that WavePad and Switch generate. (EDIT: since first writing this, I discovered mp3DirectCut by Martin Pesch. It does not give a graphical representation of the file, so finding appropriate points for splitting is a bit more fiddly, but it *seems* to work 'in situ', without any huge demands on storage. So for now I'm using the old 'Mega MP3 Splitter'. Interestingly, the Koyote 'cutter' application is NOT the one to use: it creates a 'tempCut.wav' file in Docs&Settings that is as big as the problem files created when opening WMA files in Wavepad. By converting to MP3 first, one can then split the files with other applications. This used to be my first step, using WavePad - but that, of course, hit the TEMP1.WAV problem. Incidentally, I also often split the original recording first, so as to work on smaller, more manageable files (say the individual speakers at a conference). If I then open the MP3 files in WavePad, I still get the huge aud file, but without the equally large WAV file. (EDIT: I also tried NCH's 'Switch' for the WMA->MP3 conversion, but like WavePad it too created that huge Temp1.wav file in Documents&Settings. (Previously I had used WavePad to make the conversion.)
AUDFREE AUDIO CAPTURE TEMPORARY DIRECTORY FREE
Since I want my edited files to be in MP3 format anyway, a workaround is first to convert them to MP3 (I use the free Koyote converter) and then work on the MP3 file. The WAV file seems to be a byproduct of the DirectX decoding process. However, I now realise that this happens only when the original file is in WMA format: when I open a WMA file with WavePad I get a pop-up that tells me 'Decoding with DirectX'. My problem was that although I could successfully relocate the aud and grf files into an 'Audio Working Folder' of my own choosing, when I opened my original recordings, I found this TEMP1.WAV file created in my Docs&Settings folder *as well as* the aud and grf files. In trying to work out why it didn't work for me although it does for you, I think I've now got to the bottom of it. I hope that answers your question well enough. To answer your question, I'm pretty sure that if you rename the file and location, whatever name is on the C drive don't Matter, because the NEWLY DESIGNATED FOLDER/name/location is where it'll be doing its' work. " the 'Temp1.wav' file is nevertheless created in the 'Documents & Settings' folder on the C Drive. I doubt that nch has any plans to change that, since you already have the option of renaming it and where it goes at your own discretion. It will probably work, just don't try running thing without the drive connected I've never tried an external drive, but I did rename the working folder in my C drive to a new folder in the D drive and it solved a lot of anomalies I was getting. The problem, if it is not evident, is that my recordings of conferences are typically hundreds of megabytes of WMA, leading to more gigabytes of Temp1 than I have room for. I have searched the forum and found a thread with a similar title from which I infer that even having changed the 'Audio Working Folder' (to an external drive) the 'Temp1.wav' file is nevertheless created in the 'Documents & Settings' folder on the C Drive.Ĭould someone confirm whether that is correct, please? If so, could someone from NCH indicate whether they have any plans to enable the default location for 'Temp1' to be changed in a future version?
0 kommentar(er)
