Cheryl, thanks very much for your (always) quick replies. I had tech support responsibilities for years and I know how relentless it can be. Not to mention that it's probably one of about six jobs you do? >8-0
Last night I reset the C: drive as the output target. Instead of the previous ~20 minutes of unfrozen video per session, I now get 23 OR MORE minutes. Problem is, I'm recording 100-minute streams. So I'm baby sitting: I stop each session at 27 minutes, harvest the unfrozen video, then start a new 27-minute session. I'll edit & assemble each webinar from its 5+ separate recorded chunks. OUCH!
Is there any way to monitor the RVC output file, either in real-time or delayed, so I can tell if/when the video recording has frozen? I've stopped two of these sessions at 27 minutes and they were still running fine. I hate to stop a session that might go the distance! OTOH, I can't risk wasting a 100-minute session when only 23 minutes might be usable. Any way of monitoring would be of tremendous help!
OF INTEREST: The earlier the video freezes in a session, the smaller the size of the resulting file. Maybe I can monitor the file-size counter on the RVC console display, on the assumption that the data rate will slow once the video freezes? That's a PITA but might save me from stopping a still-good session.
Can't wait to hear more about the new version!
Bookmarks