Minor problem with built-in transcoding

[A_Brass]

I discoverd an unwanted result of using built-in transcoding to reconvert a file.

This was the situation.

I started with "Move.avi" about 700mb. I had created a transcoding profile to create a AVI for my PocketPC @ 320x240.

I entered the Video Libary selected "movie.avi" went to transcoding, changed the profile to my PPC profile and pressed start. It transcoded for a few seconds and stopped. I didn't understand what the problem was, but when I checked the movie.avi it was no longer 700mb it was about 4mb. But checking the demsions I could see it was now 320x240.

Turns out the transcoder grabbed the file and started transcoding but it started saving the new file with the same file name. So it overwrote my existing file.

So, just a warning to others who try to use the the transcoding to create several different AVI's.

Anybody have any thoughts on how to avoid this? Besides transcoding outside of GBPVR?

Thanks

[HtV]

There is an easy work around. You have to edit config.xml for that as follows;

Code:

<Conversion name="XviD" cmd="-y -i {SOURCE_FILE} -f avi -ab 224 -ac 2 -acodec mp3 -vcodec mpeg4 -b 1400 -vtag XVID {DEST_FILE}" targetExtension=".avi" />

Change the last part to e.g. targetExtension="1.avi

Then the file won't be saved under the same name, but gets a 1 added to the filename without changing the extension.
You would ofcourse have to do that for all commandlines under customffmpegconversions.

[A_Brass]

That's a good idea. I think I'll try it like his targetExtension="-ppc.avi" and see how that works.

I didn't even think of doing it that way. Thanks!

[HtV]

Cheers, it works for me, I just tried. I never use the transcode option, I'm kind of surprised no-one ever stumbled on this before.:confused: