CANOPUS inactivity timeout detected conversion was aborted

[Intuit]

ANyone ever get this message using Canopus Procoder? I just started getting it lately. I'm using Canopus to encode from DV-AVI type 1 to Mpeg2. Some footage converts fine, some doesn't.

UPDATE:

This seems to be doing this with almost every file now. And its always seems to be that the fragmented mpeg2 file that CANOPUS didnt finish is 46 seconds long...always 46 seconds. I'm so freaking frustrated! It seems just when you think your getting the hang of this stuff, something else pops up. GRRR...

My son's going to have moved out and headed off for College before I figure out how to get the baby movies I recorded of him onto DVD!!!! Someone please help! Thanks!!!!

[mikiem]

Welllll... can't fault ya' for not googling -- prob is the guy with the same question never got an answer almost 2 years ago.

Don't use procoder, so just guessing in case some comment is better then none.... :P

If it's some files, & not others, perhaps you can find out what's different about the files, checking audio format, what software you used to edit/create/transfer them etc. IOW, if there something they have in common.

Next guess is to suggest looking at your DV codecs -- which are installed, has one taken over as windows default, that sort of thing. Could be Procoder's having trouble reading/decoding the video. Might try encoding mjpeg avi test file, & see if it takes that.

Or... check network activity, & firewall, & task mgr. Is something happening at the time (or just before) every error. In task mgr might take more then one try, but watch for activity elsewhere, in other prog or processes/services.

Or, try procoder repair or remove/install, perhaps contact their tech support...

[lordsmurf]

Contact Canopus.

[guns1inger]

I was able to find quite a few references to this problem on non-English sites. With the dubious aid of Google's translation feature, I was able to come up with the following;

1. All references were to the 1.5 release of ProCoder
2. Most references were to 'cracked' or warez releases of the product
3. Most problems seemed to be solved by either uninstalling, running a registry cleaner, then re-installing, or in some cases, simply running a registry cleaner such as regclean.

Don't know if this helps.

Please note : Point 2 is not meant to be accusitory, simply stating what I found.

[Intuit]

Welllll... can't fault ya' for not googling -- prob is the guy with the same question never got an answer almost 2 years ago.

Don't use procoder, so just guessing in case some comment is better then none.... :P

If it's some files, & not others, perhaps you can find out what's different about the files, checking audio format, what software you used to edit/create/transfer them etc. IOW, if there something they have in common.

Next guess is to suggest looking at your DV codecs -- which are installed, has one taken over as windows default, that sort of thing. Could be Procoder's having trouble reading/decoding the video. Might try encoding mjpeg avi test file, & see if it takes that.

Or... check network activity, & firewall, & task mgr. Is something happening at the time (or just before) every error. In task mgr might take more then one try, but watch for activity elsewhere, in other prog or processes/services.

Or, try procoder repair or remove/install, perhaps contact their tech support...

I actually did Google it and saw that same post on CDfreaks website....




Mikiem, Gunslinger and Lordsmurf, thanks for the tips. I will try some of those and see if they work. No offense taken Gunslinger