LuckSiege / LuckSiege/PictureSelector
录制视频后,在部分手机上回放的时候会出现画面拉伸变形的现象
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 13.6k
- Forks
- 3.1k
- PR merge metrics
- No merged PRs in 30d
Description
在使用录制视频功能时,录制完成后自带的回放功能,回访时出现了画面拉伸变形的现象。
我使用的是如下代码:
PictureSelector.create(this)
.openCamera(PictureMimeType.ofVideo()) // 全部.PictureMimeType.ofAll()、图片.ofImage()、视频.ofVideo()、音频.ofAudio()
.imageEngine(GlideEngine.createGlideEngine()) // 外部传入图片加载引擎,必传项
.isUseCustomCamera(true) // 是否使用自定义相机
.setCustomCameraFeatures(CustomCameraView.BUTTON_STATE_BOTH) // 设置自定义相机按钮状态
.setCaptureLoadingColor(ContextCompat.getColor(this, R.color.normal_red))
.isAndroidQTransform(true) // 是否需要处理Android Q 拷贝至应用沙盒的操作,只针对compress(false); && .isEnableCrop(false);有效,默认处理
.setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_UNSPECIFIED) // 设置相册Activity方向,不设置默认使用系统
.isDisplayOriginalSize(true) // 是否显示原文件大小,isOriginalImageControl true有效
.isCameraAroundState(true)
.setCameraVideoFormat(PictureMimeType.MP4) // 相机视频格式后缀,默认.mp4
.isCompress(true) // 是否压缩
.synOrAsy(false) //同步true或异步false 压缩 默认同步
.recordVideoMinSecond(10)
.recordVideoSecond(11) //录制视频秒数 默认60s
.forResult(object : OnResultCallbackListener {
override fun onResult(result: List) {
videoPath = result[0].realPath
Timer().schedule(300) {
uploadVideo()
}
}
override fun onCancel() {
}
})
有人遇到过吗?怎么解决的呢?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the distortion with the provided PictureSelector.openCamera configuration, especially on the affected phones, and compare the recorded video with its built-in replay. Trace the recording and replay path to identify where the video dimensions or orientation diverge. Done means recorded videos replay without stretching across the affected devices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100