SilverAzide, I think you were close with your suspicion, I approached this in a different way by focusing on ffmpeg output where the error happened, and lo and behold, it was about it being "too interactive":
https://unix.stackexchange.com/questions/36310/strange-errors-when-using-ffmpeg-in-a-loop
So I added -nostdin to the ffmpeg parameters and the error was gone. The culprit wasn't Rainmeter or RunCommand after all, but I might let this thread here just in case some other crazy guy like me (who tries to do way too much with Rainmeter, lol) encounters a similar problem in the future. By the way, I already eliminated the 75 MB ffmpeg from my process anyway in the meantime, so I won't be actually using the fix going forward. Still, good to know the solution was simple. Thanks for taking a look and trying to help, much appreciated - and sorry for bothering other folks who checked the thread with a NON bug issue unrelated to Rainmeter (the fact that it seemed not to happen at the command line wrongly led me to believe Rainmeter had something to do with it).![;)]( "Wink")
https://unix.stackexchange.com/questions/36310/strange-errors-when-using-ffmpeg-in-a-loop
So I added -nostdin to the ffmpeg parameters and the error was gone. The culprit wasn't Rainmeter or RunCommand after all, but I might let this thread here just in case some other crazy guy like me (who tries to do way too much with Rainmeter, lol) encounters a similar problem in the future. By the way, I already eliminated the 75 MB ffmpeg from my process anyway in the meantime, so I won't be actually using the fix going forward. Still, good to know the solution was simple. Thanks for taking a look and trying to help, much appreciated - and sorry for bothering other folks who checked the thread with a NON bug issue unrelated to Rainmeter (the fact that it seemed not to happen at the command line wrongly led me to believe Rainmeter had something to do with it).
Statistics: Posted by Yincognito — Today, 5:37 pm