Lacking any official reply from CyberLink, I believe I have come up with my own work-arounds. First, deleting the temp files from within PowerDirector is, at best, an akward solution, because while a project is open, PD has those files locked, and the manual delete routine is not sophisticated enough to unlock them on-the-fly. Practically speaking, this means that when audio waveforms fail to render, one must first exit PowerDirector, so that the locks with be released. And then, one must start PD again, and before loading any project, perform a manual deletion. So far, that has always resulted in PD16 then rendering video thumbnails and audio waveforms as expected.
Without any official information to the contrary, I believe that PD16 assumes that files with the same name are, in fact, the same file, but in real life, that's not necessarily true. For example, I have a digital piano that always creates files starting with TAKE00.wav, and then continuing with TAKE01, 02, 03, and so on until the USB drive is full. At which point I would, without much thought, just go ahead and delete the files. And then it starts over again at TAKE00. I think it’s worth mentioning too that the piano gives all of the files exactly the same date and time too. Something very similar happens if one uses the voice-over feature in PowerDirector, since PD16 always uses the same filename sequence.
So if one is working with auto-generated files like that, it is very likely that one will eventually be working with some identically-named files. And at that point, I suppose it would depend upon whether PowerDirector had automatically deleted the cached files. Mine is set for 30 days, so I assume that to be the default. One solution might be to just change that setting to a much lower number.
I guess it depends upon one’s hardware, but on my PC, it only takes a few seconds to re-create the thumbnails and waveforms. For example, with a 30 minute/15GB video file, my machine generates the thumbnails in under 30 seconds, and the audio waveforms in less time than that. Considering how much time I’ve spent trying get PD16 to render audio waveforms, that seems like a pretty reasonable trade-off to me. Of course the most obvious solution would be for CyberLink to finally go ahead and just fix the problem. I mean, how hard could it be to check for file size and date in addition to name?
Failing that, the work-around that I have found is to simply avoid identical filenames to the extent that I can. For example, when working with the files from the piano, I consciously avoid deleting the last file in the numbered sequence from the USB flash drive. That way, the piano will always continue with its numbers sequence, always creating a unique filename. I’m not sure what will happen when I get to TAKE99, but I’ll face that when I get there. I don’t foresee it happening within the 30-day timeframe of PowerDirector’s auto-delete cycle. If one has a lot of such files to deal with, then I suppose that one could name them by date and time.
‘Not sure what to do about PowerDirector’s own tendency to create duplicate filenames, other than to proactively change the name of every capture to something other than “Capture”. But then if one does that, then one will be faced with manually naming every file in the series, because PD16 only increments the numbered filenames when using the default “Capture” prefix. Only then does PD automatically increment to Capture(0).wav, Capture(1).wav, etc. to the filename. And in case anyone with influence is reading this, those are some very ugly and hard-to-read filenames. I say lose the parenthesis and use a hyphen instead.
In any case, prevention is currently my best work-around because constantly having to bail out of PowerDirector, only to then restart and manually delete the temp files is very much a work-around. It seems pretty good the first time, after fighting to see a waveform for a while, but it gets old pretty fast. At the end of the day, the real solution would be for CyberLink to actually address the problem by comparing file date and size as well as name.
Meanwhile, if anyone finds a better work-around, please let me know!
--
-Mark
Cable Solutions