Closed Ogane001 closed 2 years ago
Hey @Ogane001, can we get the full logcat output for the failed capture (details on how to grab it are here). It would also be really good to know what device it is you're using.
Hey @Ogane001, can we get the full logcat output for the failed capture (details on how to grab it are here). It would also be really good to know what device it is you're using.
Hello. I have the same problem. Of the errors only:
2022.07.29 15:02:19.430 1372 8092 Error C2AllocatorIon >>>SEC mapUsage Mapper1 1
2022.07.29 15:02:19.430 1372 8092 Error C2AllocatorIon >>>SEC C2AllocatorIon::mapUsage ion_is_legacy++++++++
2022.07.29 15:02:19.430 1372 8092 Error C2AllocatorIon >>>SEC mapUsage 0, 1
This error appears on Samsung s9+ (Android 10), On Redmi (Android 10) (Miui 12.0.11) everything is recorded perfectly and the recording files weigh more than 0 bytes
@dom98111 could you please attach here the full log cat from ADB so we can work out the solution tot his problem :-) thanks!
@dom98111 could you please attach here the full log cat from ADB so we can work out the solution tot his problem :-) thanks!
Thanks @dom98111 From the output I can see that stop is being called almost immediately after start. This is due to one of the stop modes other than manual being used with a very low frame count or time. There is a little more information available here
Thanks @dom98111 From the output I can see that stop is being called almost immediately after start. This is due to one of the stop modes other than manual being used with a very low frame count or time. There is a little more information available here
So the file was recorded for 3 seconds. Isn't that enough? Everything works fine on my second phone
I can see from the log output that the first frame hadn't been processed by the time stop was called. Are you using the stop mode settings or calling stop yourself?
It would be really helpful if you could tells us the following:
Do our demo scenes work on that device?
All our demo scenes have been tested on a Samsung A50 which has a similar specification (albeit not as good) to the S9+.
I can see from the log output that the first frame hadn't been processed by the time stop was called. Are you using the stop mode settings or calling stop yourself?
It would be really helpful if you could tells us the following:
- what version of Unity you're using
- which capture component you are using
- how the capture component is set-up
Do our demo scenes work on that device?
All our demo scenes have been tested on a Samsung A50 which has a similar specification (albeit not as good) to the S9+.
unity 2021.3.5.f1 (with trial UnityPlugin-AVProMovieCapture version 5.0.1)
I am using capture from camera component
i am following the manual, when setting up it
I just tested two test scenes: Screen Capture and Camera Capture. After the recording starts, the video duration increases on the recording control panel, but the file size does not increase (the recording control panel displays 0.0 mb)
Everything works fine on the computer and the second (also worse) phone, but files weighing 0 mb are created here and that's it:(
Immediately after the recording starts, даже, на тестовых сценах, где я не менял дефолтные параметры, errors continue to be displayed to me:
2022.07.31 14:33:18.934 10299 14444 Error C2AllocatorIon >>>SEC mapUsage Mapper1 1 2022.07.31 14:33:18.935 10299 14444 Error ion ioctl c0044901 failed with code -1: Invalid argument 2022.07.31 14:33:18.935 10299 14444 Error C2AllocatorIon >>>SEC C2AllocatorIon::mapUsage ion_is_legacy++++++++ 2022.07.31 14:33:18.935 10299 14444 Error C2AllocatorIon >>>SEC mapUsage 0, 1
I advise you to pay attention to a similar case, also related to mp4 encoder: https://github.com/dbof10/Bitmp4/issues/3
I just bought the paid version of the Mobile edition, but it didn't help and there are problems in the same way :(
Sorry for the delay. I will put my own because the error is different in my case.
Device used is SonyXperia 1 II
Have you made sure to remove Vulkan from the API list in player settings?
Hey @Ogane001, thanks for sending that on. I can see the following line in the output:
2022/08/01 09:23:05.215 25065 25090 Info AVProMovieCapture ⚠️ Vulkan API is not supported
We're working on Vulkan support but it is not available yet. Please make sure "Auto Graphics API" is unchecked and OpenGLES3 is top of the list of graphics APIs in the Android player inspector as shown below:
Hello, I also have the same problem. I cannot record videos on Android. The recording size is always 0KB, and the video file is damaged and cannot be opened.
Hey @dom98111, have you tried capturing using the H264 video codec? Have you tried capturing with Audio set to none?
Hey @Fighter0286, please provide as much information as possible including the following:
嘿@Fighter0286,请提供尽可能多的信息,包括以下内容:
- 统一版 unity 2020.3.35f1c2
- 设备品牌和型号 小米8
- 安卓版 Android 10
- 使用的捕获组件 Capture Form Camera
- 用于捕获组件的设置 设置没有过的的修改,您的手册为主,测试demo和自己的demo表现相同。
- 失败捕获的 logcat 输出 在unity上面没有任何报错信息。
"Unified version of unity 2020.3.35f1c2 Device Brand and Model Mi 8 Android version Android 10 Capture Components Used Capture Form Camera Settings used to capture components Set up unmodified, your manual is the main, the test demo and your own demo behave the same. The logcat output of the failed capture has no error message on Unity."
@Fighter0286
So you are saying that this has happened using an Mi8 phone and the capture from camera demo?
Can you follow the process to get an logcat from here please: https://www.renderheads.com/content/docs/AVProVideo/articles/platform-android.html#collecting-logs The windows tool mentioned mlogcat is really helpful for showing us more information
“统一版unity 2020.3.35f1c2 设备品牌和型号 Mi 8 Android 版 Android 10 捕获组件 使用捕获表单 相机设置 用于捕获组件 设置未经修改,您的手册是主要的,测试演示和您自己的演示行为相同。失败捕获的 logcat 输出在 Unity 上没有错误消息。
@Fighter0286
所以你是说这是使用Mi8手机和相机演示捕获的吗?
你能按照这个过程从这里获得logcat吗: https://www.renderheads.com/content/docs/AVProVideo/articles/platform-android.html#collecting-logs 提到的windows工具mlogcat对于向我们展示更多信息真的很有帮助
我不知道是否正确,但这是我的log,请您查看 log.txt
Hey @Fighter0286, you're using the Vulkan API which is not supported yet. Please see here
Hey @dom98111, have you tried capturing using the H264 video codec?
Have you tried capturing with Audio set to none?
Yes, I tried h264 and different audio recording options and delay before start, but everything is exactly the same. Does not work on s9 :(
@dom98111 And this is opening a clean project and just running one of the demo scenes without any changes, apart from removing Vulkan from the graphics API list?
@dom98111 And this is opening a clean project and just running one of the demo scenes without any changes, apart from removing Vulkan from the graphics API list?
Yes, deleting Vulkan helped me, although it wasn't in the logs. Thank you so much for your help in solving the problem
Thanks for letting us know :)
Describe the bug Cannot record on Android Your Setup (please complete the following information):
To Reproduce Steps to reproduce the behavior:
After opening the scene, build Demo03-CameraCapture for Android without making any changes. (The same problem occurs outside of this scene as well)
Start recording During this recording, the FileSize does not increase and remains 0 after a number of seconds. 3.Ends recording A corrupt mp4 file with 0 bytes has been created in the destination of the video.