Log in

View Full Version : REQ: A pause button for god sakes


duckdown
18th September 2005, 17:30
A PAUSE button would be extremely nice.

Often times I go to bed, and set up like 4 movies in batch mode, and often times when I wake up they still aren't done.. I use CCE SP as my encoder, and a PAUSE button would be *really* nice.. I always have to cancel my movies at like 30% because thats my only option if I want to play a game..

Obviously you can't make a PAUSE button appear in the actual CCE SP window when it's doing the encoding, but even if it would PAUSE after it's current .m2v or whatever would be REALLY nice
I've had to abort over 10 movies now and it's extremely annoying.

Doom9
18th September 2005, 17:40
because thats my only option if I want to play a game..ever heard of idle priority? there is no need for you to abort anything, and since cce doesn't provide a method to pause, Rebuilder won't be able to pause it either.

Guest
18th September 2005, 17:41
Forum rule 9: no special characters in title. Please remove them. Thank you.

SpazzHH
18th September 2005, 19:00
How about resuming the one aborted project at a later time in 3-click mode? That way you're not out anything. You can pickup right where it left off. Then start the other projects in another batch if you desire.

scharfis_brain
18th September 2005, 19:16
there is a small command line utility called "process.exe"

it lets you set the process priority of a process to "suspend", which means effectively pausing every activity of the choosen process.

This thing saved my 'life' several times.

roux
18th September 2005, 20:46
Isn't it possible to pause rebuilder between reencoding two segments?

SpazzHH
18th September 2005, 21:09
Isn't it possible to pause rebuilder between reencoding two segments?
Not in Batch or 1-click mode. You have to resume in 3-Click mode any aborted projects.

johnhamler1
18th September 2005, 22:16
can someone explain me simply this batch processing, how do u encode 2-3 DVD in same time...???

thanks!

jdobbs
19th September 2005, 12:30
Just set up each job as if you were going to encode it and save it as a project file. Then load the project files in the batch window and run it. One thing to be careful of... don't use the same output directory for any of them. The last one will overwrite. It seems obvious -- but I still do it sometimes without thinking. :rolleyes:

Doom9
19th September 2005, 13:20
there is a small command line utility called "process.exe"Never heard of it, and technically speaking there's no priority suspended. It might be possible to join every thread of a process and suspend it, but if we're talking about multithreaded applications, doing this could potentially lead to disastrous results when threads depend upon each other (deadlocks, unexpected closing of a program, outright crashes, etc.)

scharfis_brain
19th September 2005, 13:29
C:\yourpath>process /?

Command Line Process Viewer/Killer/Suspender for Windows NT/2000/XP V2.03
Copyright(C) 2002-2003 Craig.Peacock@beyondlogic.org
Usage: process [-v] [-t] [-c]
process [-q] [Process Name/PID] [timeout sec(optional)]
process [-k] [-s] [-r] [Process Name/PID]
process [-p] [Process Name/PID] {RealTime|High|AboveNormal|
Normal|BelowNormal|Low}
process [-a] [Process Name/PID] [Mask(To Set)]
-v View Processes.
-t View Kernel and User CPU Times.
-c View Process Creation Times.
-q Send WM_CLOSE Message. Default timeout is 60 Sec
-k Kill Process. (Terminate)
-s Suspend Process.
-r Resume Suspended Process.
-p Set Process Priority.
-a Get/Set Affinity Mask of Process.

C:\yourpath>

At least it worked for me.

Doom9
19th September 2005, 14:09
I don't doubt it exists, I just outlined, based on my previous experience in working with processes and threads, why such a tool could have disastrous effects. Depending on how a program is written, even changing process priorities while running could have undesireable effects - I have previously written such a tool where in absence of thread synchronization, I had to use thread priorities to prevent premature abortion of certain operations.

Edsel
21st September 2005, 08:54
ever heard of idle priority? there is no need for you to abort anything, and since cce doesn't provide a method to pause, Rebuilder won't be able to pause it either.

Rebuilder could easily pause when CCE finished with the current segment.

Since it's such a processor hog (I'm pegged at 100% constantly on my Athlon 3000, even on low priority), and encodes take up to five hours, I think this is a hell of a good suggestion.

jdobbs
21st September 2005, 11:33
But you already can pause... just stop the process. Then you can resume the encoding at the next segment by selecting ENCODE in 3 click mode.

jptheripper
21st September 2005, 14:20
i think they were talking about a batch pause, batch continue

jdobbs
21st September 2005, 18:49
Hmmm... if you are interacting with it, it isn't "batch". But, regardless of whether it is in batch mode, you can still stop and resume in 3 Click mode...

jptheripper
21st September 2005, 18:59
i thought they were trying not to interact..

int 21h
22nd September 2005, 01:30
Never heard of it, and technically speaking there's no priority suspended. It might be possible to join every thread of a process and suspend it, but if we're talking about multithreaded applications, doing this could potentially lead to disastrous results when threads depend upon each other (deadlocks, unexpected closing of a program, outright crashes, etc.)

You don't set priority suspended, you suspend the thread. But as you suspected, it can cause deadlocks...

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/suspendthread.asp

RaistlinMajere
25th September 2005, 10:06
you could do what I do. When i open rb initially I sets its priority to lowest using a nice little free utility called powermenu http://www.veridicus.com/tummy/programming/powermenu/
then all the cce opened by rb are in lowest priority too meaning my system is still usuable should i need it to be.

zacoz
25th September 2005, 10:25
I'm pegged at 100% constantly on my Athlon 3000, even on low priorityThat is to be expected. The setting can be seen as what it's name implies - a priority of access to the CPU, not a CPU usage level. So at low priority it will use all the CPU available (ie up to 100% if necessary) after other processes with higher priority have grabbed what they want. (Apologies to the techno geeks who can likely explain it's not quite that simple)

I'd be pretty annoyed if my Athlon 64 3000+ ISN'T running at 100% when I am encoding.