khaver
Member
Warmuptill, I just tried your latest Github version and it worked as expected, but with a slight modification to my macros. On the 2nd macro that unpauses the 3rd macro (the one that stops the recording after some time of silence), I had to have it pause the 1st macro so it wouldn't just keep pausing the 3rd macro and the stop recording after silence condition would never be met.
Also, it seems when a macro is paused, it's state in the macro list becomes disabled. If a macro is in a paused state and OBS is closed, that macro gets saved as disabled, so when OBS is reopened, that macro stays disabled. Is pausing supposed to be the same as disabling? Seems to me just pausing a macro shouldn't disable it, but whenever OBS is opened, all macros should start in an enabled state unless specifically unchecked in a previous session by the user. Is this possible?
The problem I see now is if for some reason the mic never gets muted so the silence is never detected and the user instead stops the recording manually, the 1st macro is still in a paused (and disabled) state when OBS is closed. The next Sunday when OBS is started again, the 1st macro that pauses the 3rd macro is now disabled and the 3rd macro will start testing for silence immediately, and I'm back to my original problem. This logic stuff can sometimes lead to an never ending rabbit hole.
Also, it seems when a macro is paused, it's state in the macro list becomes disabled. If a macro is in a paused state and OBS is closed, that macro gets saved as disabled, so when OBS is reopened, that macro stays disabled. Is pausing supposed to be the same as disabling? Seems to me just pausing a macro shouldn't disable it, but whenever OBS is opened, all macros should start in an enabled state unless specifically unchecked in a previous session by the user. Is this possible?
The problem I see now is if for some reason the mic never gets muted so the silence is never detected and the user instead stops the recording manually, the 1st macro is still in a paused (and disabled) state when OBS is closed. The next Sunday when OBS is started again, the 1st macro that pauses the 3rd macro is now disabled and the 3rd macro will start testing for silence immediately, and I'm back to my original problem. This logic stuff can sometimes lead to an never ending rabbit hole.