View Full Version : [RV10] Producer temporary files
Kaiousama
3rd March 2004, 12:03
I noticed producer makes a temporary file during the encoding process into my windows\temp directory and, when the encoding reaches 100% moves that temporary file into destination directory renaming as my desidered clip.rmvb file.
Is there a way to specify custom temp directory for the temp file or, in a easyer way, to directly write into destination's path without the needing of a temp file?
I said that because it is usually for me to create diskspace for the encoded file only in the HD partition where the destination forlder is located, and not in the partition where windows resides, so more thant one time i risked the whole encoding process to fail due to lack of diskspace. That's an annoying thing.
damrod
3rd March 2004, 12:08
you can specify the temp dir in job files...
but producer will still create a tmp file... which will be renaming in rmvb at the end...
karl_lillevold
3rd March 2004, 18:27
Hi, Look for the producer.pref file in Producer's directory. It should contain a line like this:
<paths audiences=".\audiences\" servers=".\servers\" tempDir="%TEMP%"/>
You can set tempDir to wherever you like. As you have already noticed, this is very useful...
Sirber
3rd March 2004, 18:31
<paths audiences=".\audiences\" servers=".\servers\" tempDir="%TEMP%"/>
Paths don't understand "..\". I reported the bug to HC.
Kaiousama
4th March 2004, 10:26
@Karl : Thanks for the explaination, is there a way to set tempDir value to videoclip output directory, something like tempDir="%DEST%" (in the same way windows temp directory is declared as tempDir="%TEMP%") ?
damrod
4th March 2004, 18:46
good question
usually i recreate producer.pref for each file...
karl_lillevold
4th March 2004, 18:46
Kaiousama: it is your lucky day :) This feature already exists : %OUTPUTDIR% I am being told should work.
EDIT: Correction: it's %OUTPUTDIR%, not %OUTPUT%
Sirber
4th March 2004, 19:33
Interresting question: Does producer delete them all after encoding?
damrod
4th March 2004, 20:52
%OUTPUT% ??
yeah!!! it's better than using a dospath!!!
i don't know if producer delete them...
what i know is that producer rename the tmp as rmvb ie : change them in rmvb since if you rename the tmp in rmvb...it sucks in mpc !!!
btw if you stop encoding with producer.exe... the tmp still exists...
Kaiousama
4th March 2004, 23:07
Originally posted by karl_lillevold
Kaiousama: it is your lucky day :) This feature already exists : %OUTPUT% I am being told should work.
Sure it is, but maybe not so lucky:
I tested this option but producer refuses to recognise the path (and to encode), the error reported in producer.log after changing tempDir into %OUTPUT% is :
,Error,File Output,2004/03/04 22:54:31,0,Disk drive for Temporary directory C:\Divx\Encoders\producer_10\%OUTPUT% is either unavailable or an unwritable type. Unable to write file.
So i started thinking... i' usually using a job file for the encoding process and the destination filename is written into that job file; so i simply start the producer with the following commandline:
producer.exe -j "[job] Elfi.rpjf" -lc w,i,d,e
I thought producer arise an error because it is trying to retrieve %OUTPUT% from command line passed output path ( -o parameter)
So i changed my command line into this:
producer.exe -j "[job] Elfi.rpjf" -o "D:\Elfi12.rmvb" -lc w,i,d,e
Hoping that temp file would now be created into d:\ directory, but the same error as before arises.
Have i done something wrong? works the %OUTPUT% parameter well on your PCs?
btw. i'm running the latest Producer10 build on my pc.
karl_lillevold
4th March 2004, 23:20
Oops, sorry. I was given the wrong information and did not double check. The correct parameter is %OUTPUTDIR%. I have verified that this works. Post above edited.
Kaiousama
4th March 2004, 23:48
I also tested %OUTPUTDIR% on my pc and now all's going right.
The %OUTPUTDIR% is well recognized even if no -o parameters are passed to commandline and output filename is only stored into job file.
It is my lucky day, afterall :D
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.