View Full Version : DVD-RB Pro 1.23.3 ProCoder2 hanging
FredThompson
7th April 2007, 15:42
I'm running pro build 1.23.3 on a Centrino duo machine. ProCoder2 will run then DVD-RB Pro will not start new instances of ProCoder2 and interlaced source. The Stop/Pause button is enabled and clicking on the close button in the upper right of the window brings a window saying, "You must ABORT..."
It looks like DVD-RB Pro is not aware that ProCoder2 sessions have ended. I've seen this with 2 different sets of source files and I've also removed and reinstalled both DVD-RB Pro and ProCoder2.
The script appears to work properly. This setup has run dual HC encoders and progressive source with no problems. Because of this, I doubt there is a problem with multiple instances of any of the script components.
Has anyone else had this problem? Better yet, anyone had the problem and found a solution?
Here's the script:LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\ColorMatrix.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\DeGrainMedian.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\DeSpot.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\RemoveGrainS.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\RepairS.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\SSEToolsS.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\WarpSharp.dll")
Import("C:\Program Files\AviSynth 2.5\plugins\DeHalo_alpha.avs")
Import("C:\Program Files\AviSynth 2.5\plugins\LRemoveDust.avs")
ColorMatrix(hints=true, opt=0)
i:ConvertToYV12(Interlaced=True)
i:SeparateFields()
i:DeGrainMedian(limitY=2,limitUV=3,mode=3,interlaced=true)
i:evn=SelectEven().DeHalo_Alpha().LRemoveDust_YV12(10,1).UnsharpMask(strength=25,radius=5,threshold=10)
i:odd=SelectOdd().Dehalo_alpha().LRemoveDust_YV12(10,1).UnsharpMask(strength=25,radius=5,threshold=10)
i:Interleave(evn,odd)
i:weave()
p:ConvertToYV12(Interlaced=False)
p:DeHalo_Alpha()
p:DeGrainMedian(limitY=2,limitUV=3,mode=3,interlaced=false)
p:LRemoveDust_YV12(10,1)
# DeSpot for film dropouts
#p: i = ConvertToYV12()
#p: vf = MVAnalyse(i, isb=false, lambda=2000)
#p: f = MVCompensate(i, vf)
#p: vb = MVAnalyse(i, isb=true, lambda=2000)
#p: b = MVCompensate(i, vb)
#p: Interleave(f, i, b)
#p: DeSpot(p1=30, p2=12, mthres=20, dilate=2, fitluma=true, blur=2, seg=2)
#p: SelectEvery(3,1)
p:UnsharpMask(strength=25,radius=5,threshold=10)
jdobbs
7th April 2007, 17:00
When DVD-RB uses ProCoder it never actually starts that app, it starts ECLPRO.EXE... it then waits for ECLPRO to exit. From your description it sounds like ECLPRO is not terminating for some reason. You might want to check the task manager -- my guess is that ECLPRO will still be there.
You may want to check ECLPRO.INI for anything odd also.
Maybe a silly question... but you are pointing to ECLPRO and not the ProCoder executable, right?
FredThompson
7th April 2007, 18:49
Here's the ECLPRO.ini file. Does it look odd?[Options]
Delay=0
Pause=10
Priority=0
Minimize=1
NoPathWarn=0
Procoder=C:\Program Files\Canopus\ProCoder 2\Procoder2.exe
[Quality]
Quality=4
AlwaysGOP15=1
AutoParameters=1
[Debug]
StrictGOPBrateControl=0
Legacy=0I'll restart the project. It does look like the hang happens after one instance of ProCoder2 finishes. A third instance won't start and the second finishes then the process hangs.
Rippraff
7th April 2007, 20:51
Hi Fred,
maybe your timeout is too short, default setting is 20.
Here's mine:
[Options]
Procoder=D:\Programme\Canopus\ProCoder 2\Procoder2.exe
Delay=0
Pause=20
Priority=0
Minimize=1
NoPathWarn=0
[Quality]
Quality=4
AutoParameters=1
AlwaysGOP15=0
Alwaysframe=0
[Debug]
StrictGOPBrateControl=0
[Temp]
Filename=
Cu Rippraff
blutach
8th April 2007, 01:25
Might be but I have no problems at pause=10
Regards
robot1
8th April 2007, 16:28
Could you try without multiple instances in DVD-RB?
FredThompson
10th April 2007, 04:40
No doubt about it, EclPro isn't killing the ProCoder 2 instances when they are done.
Replacing the EclPro files with fresh copies from the source thread didn't solve the problem, nor did setting the delay to 100. Encoder and ProCoder2 instances show as active processes. WinAmp isn't running, nor is any other keyboard monitor which looks at the keys used by EclPro, as best I can tell. Multiple HC processes works so the problem is somehow related to just EclPro and ProCoder 2
FWIW, I'm using a dual core Gateway laptop with XP SP2.
I'm testing now with the multi-encoder setting disabled.
jdobbs
10th April 2007, 17:43
What version of ProCoder 2 are you using? Maybe your's is recent and something has changed that is confusing ECLPRO?
robot1
10th April 2007, 17:48
EclPRO calls ProCoder using thess switches:
/Start /CloseApp
/Start should let the encode start without user interaction
/CloseApp should close the program at the end of the encoding.
ProCoder2 should close automatically at the end of the encoding.
Have you tried with other sources?
FredThompson
11th April 2007, 00:38
Procoder 2 is 2.04.02
I don't think there has been a release lately. Canopus was bought a while ago and the new owner wants people to buy again.
I'm seeing the same problem with 1 encoder session. Have already tried 2 different source rips. I'll try a third. Everything was working fine until I upgraded DVD-RB Pro but I doubt there is a problem. The ini file for ProCoder should be proper, yes?
Does EclPro support the /CloseApp argument? If so, how? (I'm off to research now...)
SpazzHH
11th April 2007, 00:40
I don't have problems with anything hanging, but I am using Procoder 2.04.02 and have noticed that if I have to abort a project, Procoder never terminates when RB sends the command. I always have to stop it manually.
FredThompson
11th April 2007, 03:10
Hmmm...maybe something did creep into the recent build. I don't keep the old versions so can't "roll back" to verify that.
robot1
11th April 2007, 23:05
I don't have problems with anything hanging, but I am using Procoder 2.04.02 and have noticed that if I have to abort a project, Procoder never terminates when RB sends the command. I always have to stop it manually.
I will try to fix this in next version.
Procoder 2 is 2.04.02
Does EclPro support the /CloseApp argument? If so, how? (I'm off to research now...)
Yes, EclPro always calls ProCoder with that argument.
If I've understood the problem, ProCoder finishes the encoding, but doesn't quit. EclPro waits for ProCoder, and you end in a loop. I don't know how to solve. It seems a procoder problem.
Can you test with a plain .avs? You have used a lot of filter.
SpazzHH
11th April 2007, 23:10
I will try to fix this in next version.
Thanks for all your time and efforts. :)
FredThompson
12th April 2007, 07:56
Same status with the recent DVD-RB Pro release. I'm going to try a proper uninstall/registry purge/reinstall of ProCoder with reboots and reg scans. Maybe, just maybe, something has crept into the ProCoder configurations.
blutach
12th April 2007, 10:38
Just to report - using same version of Procoder as Fred and DVDRB 1.24. Just ran a quick encode with no issues at all. Even ran a couple of simple filters with the source (Undot and Deen).
After clicking Stop/Pause and aborting, Procoder finishes the segment and both instances exit gracefully.
One day, I'll figure out how to get the instances to run minimised. :) (My eclpro.ini has minimize=1 and My DVDRB Setup has this option ticked).
Regards
FredThompson
13th April 2007, 08:40
Minimize the sessions when they pop up then subsequent sessions will be minimized.
I uninstalled ProCoder 2, removed Canopus entries from both Software sections of the registry and the Application Data folders, ran some reg cleaners, rebooted, ran them again, rebooted, installed ProCoder 2.
Same results. The first 3 or 4 segments encode just fine then the encoder sessions won't close. It's really odd.
A job I had running on another computer worked flawlessly. I'm going to dig into the registries and maybe something is in there. You know those illegible strings used for registry linking (HKCU\Software\Canopus\Procoder 2)? Maybe I missed something like that. I've even searched all the files for anything containing "canopus" or "procoder" with nothing unexpected showing up.
It's all very odd.
blutach
13th April 2007, 08:59
This is gunna sound frustrating, but can you remember a time when it worked properly? If so, and it wasn't that long ago, perhaps a system restore can help.
Regards
robot1
14th April 2007, 01:47
I don't have problems with anything hanging, but I am using Procoder 2.04.02 and have noticed that if I have to abort a project, Procoder never terminates when RB sends the command. I always have to stop it manually.
EclPro v1.0 final (http://www.savefile.com/files/637223)
In this version DVD-RB can stop Procoder.
I've used the latest version of AutoIT to compile, but I haven't tested much EclPRO. I would be glad if you could test it. If there are no problems, I will update the original EclPRO thread.
SpazzHH
14th April 2007, 02:39
Thanks for the work. I'd be more than happy to test it. I'll get back soon with the results.
Spazz
P.S. Seems to work just fine. Exits on command. Nice work.
Rippraff
15th April 2007, 15:12
Another confirmation, Procoder exits with EclPro v1.0.
Good job, Mich, thanks! :)
Cu Rippraff
jdobbs
15th April 2007, 16:32
@robot1
Let me know if/when you think it's stable -- I'll update the DVD-RB Installer with the new version. :)
FredThompson
16th April 2007, 09:50
One day, I'll figure out how to get the instances to run minimised. :) (My eclpro.ini has minimize=1 and My DVDRB Setup has this option ticked).
Regards[/color]Click on the middle square in the upper right of the ProCoder window. Does that do it? It does for me but I've also clicked on the minimize button. There is some combination of those which should make minimization "sticky."
robot1
16th April 2007, 21:43
@robot1
Let me know if/when you think it's stable -- I'll update the DVD-RB Installer with the new version. :)
I need a couple of tests. I'll PM you when ready, and I will update the main EclPRO thread.
blutach
17th April 2007, 06:17
Click on the middle square in the upper right of the ProCoder window. Does that do it? It does for me but I've also clicked on the minimize button. There is some combination of those which should make minimization "sticky."
I'll give that a try next time. I used to have one instance minimised and one maximised. Now it seems both are max.
Thanks for the help.
Regards
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.