Run custom .bat file at start and end of recording

[bm_00]

The light and script work perfectly with the test

[sub]

The light and script work perfectly with the test

Great.

Unfortunately it sounds like whatever you're trying to run in your script doesn't play nicely when run from a different account. It probably is something like I mentioned earlier, with the utility trying to talk to something else using WM_COPYDATA.

[JavaWiz]

You might try redirecting the output of your commands to a text file. That way you might be able to determine where things are going wrong. There are some examples on the wiki, or if you attach your .bat file to a post, I suspect we can help with some logging...

[johnsonx42]

I have tried modifying the service but when I both type in and search for the correct username and enter the correct password and try to restart the service it throws an error of 1069 login failure. Research shows that usually means an incorrect password but it is the right one as its the same I use to login

The account may not have the "logon as a service" privilege. If you have windows pro you can set that by running secpol.msc; it's under Local Policies->User Rights Assignment. No idea if you can do it with Windows Home... I don't have it, never use it.

[scJohn]

I was writing script files to transcode (using ffmpeg, Handbrake, qsvc, or Divix) the just finished show. I was running into a lot of problems with not having the "right privilege" to do things. I gave up on CMD(aka .bat files) and switched over to Powershell. Problems went away because PS has the commands to give you the "write privilege" and is just more robust with the the things that you can do. I rewrote all of my .bat file to .ps1 files.

Sub. In version 5.0, could you give us the option of having NxtPvr call postprocessing.ps1 instead of postprocessing.bat.

[sub]

Sub. In version 5.0, could you give us the option of having NxtPvr call postprocessing.ps1 instead of postprocessing.bat.

From what I've read after a quick google, you can run your powershell scripts from a batch file.

[scJohn]

True.

Here is an example of the code

Code:

PowerShell -NoProfile -ExecutionPolicy Bypass  -Command "& {Start-Process PowerShell -ArgumentList '-NoProfile -ExecutionPolicy Bypass -WindowStyle Minimized -File """"%DIRLOC%Scheduler.ps1"""" """%ARG1%"""  """"%Run%"""" ' -Verb RunAs}"  >> %LOGFILE%

With version 5.xx, maybe it's time to say good bye to .bat files. Microsoft will never pull CMD from Win 10 but at the say time they are no longer maintaining it. Just something to consider. I would just prefer not to have the intermediate step.

[sub]

With version 5.xx, maybe it's time to say good bye to .bat files.

Ultimately there is already lots of people with batch files, so no point in breaking that for them. I could investigate looking optionally letting users use powershell scripts though.

On Linux it looks for .sh scripts.