Hi Michael, after some more tests I found out that the caching is enabled for exporting. :-( That means for users with 3,6GB free mem: (and enabled caching during import) - videos till 1,8 GB: max speed at exporting (mem->disk) - videos from 1,8GB till 3,6GB: more or less performance boost at exporting (at the beginning it's a mem->disk later disk->disk) - videos above 3,6 GB: no performance advantage or disadvantage, just like pure disk->disk export as today
Summary: For me it's the best to enable cache for import and disable cache for export. (disable the cache for export is not tested be me; my C++ knowlegde is too old to change the source code of dvbcut myself) Therefore I have another proposal: Add two options in .qt/dvbcut.sf.netrc - AllowImportCache=yes/no - AllowExportCache=yes/no Default values can be import=no, export=yes (this is equivalent to the current coding) And for me and other guys with more ram: import=no, export=yes for best performance. The default values should not harm users with problems you mention in your last mail. (video recording and cutting at same time => holes in recording) What do you think of the proposal? advantage: - backwards compatible if default values are used - better performance if other values are used disadvantage: - not known, except: new coding is necessary ;-) best regards Dominik ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DVBCUT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dvbcut-user
