Frogman1206
Member
I have a sporadic problem I can't duplicate that my co-worker keeps having happen to him.
We have the Tricaster Mini HDMI that was purchased around 2021 so it is fairly new. The Encode option encodes 2 streams. We use one for our webcast and our second one we record direct to the Sessions folder on the D drive. Recently we have had the incident where everything appears to be working correctly. No errors from the stream or File Capture stopping. At the end of the program he goes to pull the file from the Sessions folder and it is either not there or very small (ex...108kb). The icon in the upper right that has warnings and errors never says there was a problem. We record that h.264 at 5mb just for our archives. We are also recoding to external recorders so we have not lost a program yet but it is much more work to get our replays published from the external recorders than that archive from the File Capture function.
Why is the file not recording. I told him to check the performance stats and make sure Drive D is functioning after the encoder starts. I am hoping it is a user issue but wanted to ask if this has happened to anyone else.
Thanks
We have the Tricaster Mini HDMI that was purchased around 2021 so it is fairly new. The Encode option encodes 2 streams. We use one for our webcast and our second one we record direct to the Sessions folder on the D drive. Recently we have had the incident where everything appears to be working correctly. No errors from the stream or File Capture stopping. At the end of the program he goes to pull the file from the Sessions folder and it is either not there or very small (ex...108kb). The icon in the upper right that has warnings and errors never says there was a problem. We record that h.264 at 5mb just for our archives. We are also recoding to external recorders so we have not lost a program yet but it is much more work to get our replays published from the external recorders than that archive from the File Capture function.
Why is the file not recording. I told him to check the performance stats and make sure Drive D is functioning after the encoder starts. I am hoping it is a user issue but wanted to ask if this has happened to anyone else.
Thanks