revengineer 142 Posted December 24, 2024 Posted December 24, 2024 I am trying to run a post-processing script for Live TV to convert .ts to .mkv with MCEBuddy. The script is shown below. The script is called and recorded programs are added to the MCEBuddy queue. However, I sometime get access error and found that the timeout commands are not working when I call the script from within emby. It works find if I call the script standalone. I have tried using the full path for the timeout command (C:\windows\system32\timeout.exe) ut it does not work either. Something is funky with the emby environment and I cannot figure this out. Help please! @echo off timeout /t 60 /nobreak > NUL C:\Progra~1\MCEBuddy2x\MCEBuddy.UserCLI.exe --command=engine --action=start timeout /t 2 /nobreak > NUL C:\Progra~1\MCEBuddy2x\MCEBuddy.UserCLI.exe --command=addfile --action=%1 timeout /t 10 /nobreak > NUL :loop for /f "delims=" %%o in ('C:\Progra~1\MCEBuddy2x\MCEBuddy.UserCLI.exe --command=jobstatus --action=%1 --quiet') do set status=%%o if %status% == "not present" ( exit ) else ( timeout /t 2 /nobreak > NUL goto loop )
Solution revengineer 142 Posted December 24, 2024 Author Solution Posted December 24, 2024 (edited) OK, I figured this one out. The timeout command apparently has some idiosyncracies that prevent is from running correctly in a child process. The solution is to use waitfor or the start-sleep powers he'll command instead. All good now. Edited December 24, 2024 by revengineer 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now