Originally Posted by madshi
The same reasoning still applies: If madVR can successfully start a batch file with notepad.exe in it, but your node batch fails, the error is very very very likely not in madVR, but in your batch file. Maybe it's being called with different parameters, different working directory, different environment, different %path%, different user, different whatever? E.g. try chaining 2 batch files like "start another.bat", that way you might actually see what your batch file is doing. As I said, madVR starts the command line in hidden state. So you probably don't really see what's going on. If you chain the batch files, you might be able to make the batch file execution visible to see why it's failing...
It makes me crazy.
I spent hours on it yesterday evening and this evening again trying a lot of different ways...
Again: the batch works perfectly fine if:
1) I am in windows and double click on it
2) I am in a movie in MPC-BE with Madvr and I change to another profile and come back to the "correct" profile where I wrote the path to the batch
3) I am in a movie, go in Madvr, change something in the activated profile and press apply, and then the batch gets suddenly activated.
Conclusion: Madvr+MPC-BE do something slightly different on movie startup compared to when the movie is already launched and profile get changed.
Could you look at the difference in the code between startup and profile change if they are any? If they are, could you somehow convert the "start-up code" in a "change profile code? Maybe you you do with that with dummy profiles loaded and then you change to the correct loaded profile?
Or maybe it comes from the difference between loading a profile through "madvr shortcut" or "Madvr profile rules"? Anything different between those 2 in the code?
Could you also provide us a version which runs the batch in a non hidden state? Maybe that plays a role as well, who knows...
And yes, we did all that, same name, same path as another simple patch for opening editor which does work on startup. Changed nothing.
Chaining up the batch also does not do the trick.
The only workaround I see right now is to create 2 times the same REC709 profile and 2 time the same HDR profile... and on startup, it will will go in REC709_2 profile where I will call a programm entering a keyboard shortcut to go to profile REC709_1... This should work but seems really stupid
Thanks again for your help and time.