-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Record video's output is only 700k which is nothing. #401
Comments
I'm very sorry, the video cannot be recovered if it was not written to disk. Does this happen for every recording you make? In that case, please let me know the settings you were using, your system specifications and the FFmpeg log so that I can figure out what happened. |
I just started to use this tool. First time the video recording is successfully and it's great. But yesterday I used again and got this issue. Not sure how to give you the setting, but below is the FFmpeg log for yesterday: ARGS:-thread_queue_size 512 -framerate 10 -f rawvideo -pix_fmt rgb32 -video_size 3840x2160 -i \.\pipe\captura-dbbb72c4-d769-47b9-82da-666f18481edc -thread_queue_size 512 -f s16le -acodec pcm_s16le -ar 44100 -ac 2 -i \.\pipe\captura-83906731-23d2-4567-a56f-2cb02c86da83 -r 10 -vcodec libx264 -crf 15 -pix_fmt yuv420p -preset ultrafast -c:a aac -strict -2 -b:a 256k "D:\CapturaStore\2019-04-30-17-03-33.mp4" OUTPUT:ffmpeg version N-93649-gd0ca749adb Copyright (c) 2000-2019 the FFmpeg developers I will capture some screenshot on the setting as below: Let me know what else do you need. Please do let me know if there is anything that we can accelerate this process because I don't want this to happen again. Thanks. |
I think it is due to large resolution of recorded area (3840x2160). Captura is not optimized for recording large screens. I'm working on it but it might take some time. Try recording smaller regions. Upto 1920x1080 should work fine. |
Hi @MathewSachin , Thanks for the reply. But I remember that the first time I was also capturing the video on that area, the 3840x2160. Why did that work? And which information in the log indicated this error? How can I avoid this kind of thing in the future? Thanks. |
The pipe error happens only when using FFmpeg. Please test this in the latest dev build. Also, did some optimizations for larger screens. Please try that too. Thank you |
Hi Mathew, Got error when clicking on the recording button. SharpDX.SharpDXException: HRESULT: [0x80070057], Module: [General], ApiCode: [E_INVALIDARG/Invalid Arguments], Message: Invalid Arguments。 at SharpDX.Result.CheckError() Please check why this is happening. Thanks. |
Not sure why this error is happening. I can't reproduce this error on the multiple systems that I tried. In the meantime, the only alternative left is to use the |
Hi Mathew, Ok, switched to SharpAvi, seems working fine for now. May I know the difference here? Is avi file larger than mp4 file? Thanks. |
Yes, the AVI file created by Captura is larger than Mp4 file. |
Hi Mathew,
Please keep investigating the issue. BTW, are u sure SharpAvi will be very
stable without any issue?
Thanks.
Mathew Sachin <notifications@github.com> 于 2019年5月4日周六 20:25写道:
… Yes, the AVI file created by Captura is larger than Mp4 file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#401 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHWLZ6PYPA3QB224QRDYTDTPTV6EDANCNFSM4HJMNLUQ>
.
|
I can't guarantee that there won't be any issue but at least the pipe broken error will not happen. |
Hi Mathew, You are correct, the dev build cannot capture video using SharpAvi. Error message here: at SharpDX.Result.CheckError() Do you want something like a remote session to look at my PC or something like that to determine the root cause? Thanks. |
I'm currently busy with my exams, so don't have the time to completely investigate the issue. For now, as per the error I'm seeing this time, please let me know the following:
|
Is your system a laptop or a desktop? Also, try running the dev build on the integrated graphics, if available.
|
Also, does recording with OBS Studio work on your system. If not it might be a driver or hardware issue. |
Hi,
Yes, OBS is working perfectly.
Thanks
Mathew Sachin <notifications@github.com> 于 2019年5月5日周日 03:58写道:
… Also, does recording with OBS Studio work on your system. If not it might
be a driver or hardware issue.
https://obsproject.com
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#401 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHWLZ6MOGP42JWGBM2M3QADPTXTHVANCNFSM4HJMNLUQ>
.
|
Hi, Did not find the Integrated Graphics setting in the NVIDIA control panel. Out of curiosity, why the formal version of Captura can at least record on my PC, that's just having some issue, but the dev build failed totally? Also, is it possible that I install back the formal version and use SharpAvi? Thanks. |
The formal version of Captura used GDI for capture which has high CPU usage and low FPS. Yes, since the build I gave you was a portable one, you could continue using SharpAvi with the older version but I won't really recommend that because the performance is not good enough. BTW, I've tried doing some tweaks to the code. Please test this new dev build: |
Hi Mathew, This one worked! Not sure what you have done, but I can use MF to record video. Will test more in daily usage. Thanks. |
Thats awesome 👍. Please test and let me know how it works. |
Sure thing!
Thanks for the great work! Really appreciate it.
…On Sun, May 5, 2019 at 5:30 PM Mathew Sachin ***@***.***> wrote:
Thats awesome 👍. Please test and let me know how it works.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#401 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHWLZ6OH7JRF645PF5364V3PT2SJ5ANCNFSM4HJMNLUQ>
.
--
Thanks and Best Regards,
Allen Liu
|
I recorded screen video today, and after I stop recording, it showed that the file has been saved to the path that I set.
However, when I checked on the video, it's only 680kb and nothing can be played.
This video is really important to me, anything I can do to recover it? It's an one and half hour video that I recorded with important information!
Please let me know the solution! Thanks!
The text was updated successfully, but these errors were encountered: