DVD2SVCD & locked/disconnected console

[mkanar]

DVD2SVCD:

I know that you changed the access method for CCE to one that is less likely to contribute to a CCE freeze and all of us appreciate that!

However, might it be possible, if it isn't too much trouble, to have an option so that DVD2SVCD will function properly with CCE while the system is locked/disconnected, even though a CCE-freeze is more likely?

The WinXP system that I use for encoding has a tendency not to freeze during the CCE encoding process. Actually, the encoding process has never frozen, but I realize that if I tried a trouble-some DVD, it would probably freeze.

Anyhow, the capability to disconnect the user session on my WinXP sessions during the 'DVD2SVCD process' is tremendously beneficial for me and probably some others as well. Even if the option is hidden, it would be really nice to have.

Regardless, I again thank you for an AWSOME APPLICATION. When I get a [good] job again, then you can expect my donation.

Thanks!
MKanar
http://kanar.net/resume

[markrb]

The reason DVD2SVCD had this limitation was that actual key stroke characters are/where used. If you lock the console or change users these commands won't be passed along.

At one time this was eliminated. If you find that it still does this and you need to change users or lock the console you could revert back to an older version.

I was under the impression that this no longer happened.

Mark

[dvd2svcd]

So was I. I should still work.

[chainsaw135]

Yes i've been watching what is going on when you switch users.and why the first time around cce wont start encoding...

What i've noticed is this..i'll use my remote desktop feature. I'll log in to the encoding machine with my other computer...and leave the window open ...while I watch dvd2svcd do its thing.....:)

Well when it comes 2 the first time running cce, it runs through everything but it just wont hit the encode button...If I click on encode it will start and go on..and then when its time 2 do the first second and third passes, it will send the keys or commands 2 encode so only on the first time around will it fall short of sending that little command or click encode button...


If I dont use user switching or remote desktop it goes through of course.........

[mkanar]

To clarify on chainsaw's message:

Everything works while 'disconnected/locked' except for DVD2SVCD hitting the 'encode' button that initiates the .VAF file creation. Everything else, including the .MPV/multipass encoding process is fine while locked/disconnect.

Chainsaw: DVD2SVCD doesn't rerun CCE for every pass on the video. It runs CCE once for the .vaf and once for the multiple passes on the .MPV file.

I appologize for assuming that DVD2SVCD was not supposed to work while locked. My assumption goes back to this quote from DVD2SVCD, which I remembered incorrectly:

"4. Sometime ago, I discovered that CCE had problems when using drag'n'drop on it, however, there was a lot of users who wanted the possibility to "Lock The Computer" (w2k) or Fast User Switching (xp), so I took the drag'n'drop a step further in the last release. This it seems was not wise (sorry). So, the last two days I have been trying to manipulate CCE with windows commands in a way so that you still would be able to "lock" or "switch" and still be sure that CCE was running. Today I succeded, and I actually succeded in a way so that the execution should still be as safe as it was before. However, it means tha the "Open File" and "Save File" windows will popup again, so be a little careful when CCE is about to execute."

Upon re-reading the above, I realize my error.

Anyhow, thanks!

[chainsaw135]

Nod I did make an error you are right it does this once for the Vaf file, and once for multipass Mpv file I should of made that more clear in my responce.

[dvd2svcd]

I think I have found the problem, and it'll be fixed in the next build. However, there's no immediate fix for it in the current build.

[mkanar]

chainsaw135: I was just clarifying for all, but I guess that I might have over-explained it. Sorry about that. :)

DVD2SVCD and all: thanks! :)

[chainsaw135]

Not a problem...i'm just happy that I wasent the only person with the problem. And now 2 hear that it seems 2 be fixed in the next up and coming build, i'm even that much more excited. Thanks alot dvd2svcd for a awsome time saving project well worth a donation or 2:)

[dvd2svcd]

look in the "should I support tmpgenc" thread, there's an alpha version (the alpha is only about tmpgenc), if you download the version in there you shouldn't have problems anymore.

[chainsaw135]

Well the problem I was having has gone away..thanks DVD2SVCD for such a fast solution Please everyone support dvd2svcd "DONATE"