Has anyone noticed a skipping of sorts in some of their MFC caps lately? Like a quick freeze every few seconds then it resumes fine and freezes again. Started Friday for me and it's only happened to a few models I record but none of those models that it occurred with have cammed again so I can't tell if it continues with the same model or if it's more random.
Here are 2 examples:
https://mega.nz/#!eL5GhapI!qBiqGSgB4...Jztutv1k-x741o
https://mega.nz/#!uLhAGALJ!eHhHJD_fw...PvohnRaJ N6UU
None of the recordings start out with the skip but it starts happening at some point in the show. Sometimes more near the beginning. Other times it starts near the last 3/4ths of the cap.
To see if it was just me or not I found the same model's session that I had the problem on and downloaded it from camvault. The skipping was also on the camvault cap at the same place I was having my problem. So it doesn't seem to be just me. I'm thinking it's something to do with MFC's stream because it happened using both mfc-node and ctbrec.
Is anyone else having this problem?
------
On a different note, I have a very noob question. Is it ok to have different mfc-nodes installed on the same system? Not all running at the same time, just installed. Over the past few months or so i've collected and installed a few different mfc-nodes and programs from different people. For instance I have horacio9a's 'mfc-node-master' installed from before the DMCA thing happened. I have 'StreamDVR' installed. I use horacio9a's 'mfc-node-2' most of all when I do use node to cap.
I'm wondering if doing all that unpacking and installing libraries could be bad for my system. Or when I download an updated version of an mfc-node I'm already using, should I delete or uninstall the previous version? Do I have to uninstall previous packages that were installed during 'npm install'? Could that be done with like: npm uninstall? I just don't want packages interfering or contradicting each other from different versions of mfc-node.