-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difference between the node and this and some use cases #5
Comments
mfc-node v2 uses MFCAuto, which has been shown to be a better choice. |
What about pure rtmp for all recordings - have you compared that to hls? |
In most cases rtmp showed better than hls. Specifically, with MFC Recorder v.3.0.3 for some models, apart from the resolution problem that is bigger than the actual one, streamlink also have problem of not accepting the stream so in that case it will be better to switch to rtmp. |
So indeed HLS (regardless livestreamer or streamlink) is inferior compared to RTMP apart from the excess resolution you are saying? For MFC recorder 3.0.3 I am assuming you are referring to the mfc-node v2 you are working on. You mention that you modified the MFCD.exe, but I cannot find the source code for it - was this script meant for autorecording via rtmp? |
I'm not a programmer but I took a look at the code I think there are some html elements in v2, but most of the recording comes out of main.js Secondly or |
Author of mfcdump.exe is @Ruzzy, look here: http://stream-recorder.com/forum/showpost.php?p=95959&postcount=1393 ... that file I renamed to MFCD.exe because already exist MFCDump.exe by @ElGero, look http://stream-recorder.com/forum/showpost.php?p=73164&postcount=376 |
So MFCD can only do eight models at a time. I'm using streamlink right now. As I don't want stuttering and want HD |
Author of MFCD.exe, @Ruzzy conceived it as a standalone program so not only has a limit of 8 connections but it always uses the same mfc server. All these limitations are not in the case of HD models because they are in charge of rtmpdump that does not have these limits. |
So if one wants to record unlimited models |
I've already answered that question, but I will repeat it again. All three types of resolutions (LD, SD and HD) can only be recorded using rtmp protocols. |
@horacio9a So basically if Ruzzy's MFCDump was updated to have the patched version of KSV's rtmpdump, it would be a versatile or perfect recorder? |
I originally wanted to post this to the mfc-node v2 repo, but it seems like issues are disabled there, so if you can re-enable them for such cases it would be great!
The question I have is what is the correct use case of this repo compared to the mfc-node. I see that the some .exe dependencies are not needed with this python script like MFCD.exe for example, so I am guessing this is a more reliable option of a linux environment? You also have the master and V2, am I missing something in the master that V2 doesn't have? More_ importantly I see the mfc-node (v2) repo supports streamlink, livestreamer, ffmpeg, rtmp, all the major capturing methods, so what I want to know is what is the exact use of having them all, what is the need or when there is a need to choose between livestreamer and streamlink, also I know ffmpeg is not working pretty well right now, so I can choose rtmp, but then why choose hls over it.
If you can further explain me some of the use cases I would be very thankful.
The text was updated successfully, but these errors were encountered: