Could you tell me too! this
 is an interesting topic for me too!

Hi Davis,

Use for example a batch file who start HandySaw after a time elapsed.
You run your batch file then disconnect your session.

I tested my batch test.bat with the following command lines :

timeout /t 10
"C:\Program Files (x86)\Davis Software\HandySaw DS\HandySawDS" /s /x /r4 /k "myfile.mpg" /o"C:\temp"

Best regards,
David

Hello Davis,

Thank you for you response.
I am David and I work with Yan.
So, HandySaw works very well inside RDP if you start the process before closing session.
But if you start HandySaw after closing session, the process is waiting ??? and a timeout raised because the process doesn't start.
Could you check the starting of HandySaw inside RDP with your session always closed.
Thank you very much for your support.
Have a nice day
David

Hello Davis

Thank you for your reply
This happend during Scene Change Detection (we don't use Trimmer)

Yan

Is there any way to configure HandySaw for RDP/MSTSC use ?

My problem seems to be related to DirectShow Video Renderer :
- The computer running HandySaw is a Windows 7 PC (in a server room, without any display connected to it)
- We open the Windows Session from a Remote Computer using RDP/mstsc
- HandySawDS runs correctly in this configuration as long as the RDP/mstsc connection is open
- If we close the RDP/mstsc connection (without closing the Windows session on the HandySaw computer), HandySawDS remains "frozen" (suspended)
- If we re-open the RDP/mstsc connection, the HandySawDS instance returns to its "normal" active state and the current "suspended" Scene Change Detection terminates correctly

I guess this is because the Video Renderer is "lost" when the RDP session is disconnected
Are you aware of this ?
Is there any workaround ? (using "Overlay Mixer" or "Standard Render" instead of "System default video renderer" doesn't solve the problem)
Thank for your help
Yan