You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some combinations of OS, video codec and graphics card/driver (looking at you NVIDIA), the HTML5 video player (which LosslessCut uses) will simply play back audio only, and not report an error via the API, meaning we can't programmatically detect that there's a problem. Not always clear how to solve this. For some codecs we use a blacklist but it's not always complete:
Could be related to a problem I'm having - I'm cutting a long HEVC mp4 video but have an AMD graphics card on Windows 10. LosslessCut plays the video fine in the preview, but when splitting the long video into several smaller ones, only the first exported video is has a valid video track, all the others seem to have no video track (although the size and codec information suggests the video track is there). It's definitely not a valid video track because VLC shows its logo, not just black. Is it related or should I make a new issue?
EDIT: seem to have fixed my issue by downloading the latest version of ffmpeg and directing LC to use it!
I think your problem is not related to this issue, because this issue is about preview. Ffmpeg is not used for preview. Your issue is about exporting. But thanks for reporting back. I guess your issue will be fixed once i upgrade ffmpeg version shipped with losslesscut
For some combinations of OS, video codec and graphics card/driver (looking at you NVIDIA), the HTML5 video player (which LosslessCut uses) will simply play back audio only, and not report an error via the API, meaning we can't programmatically detect that there's a problem. Not always clear how to solve this. For some codecs we use a blacklist but it's not always complete:
lossless-cut/src/renderer/src/util/streams.ts
Line 378 in 06cae06
In this issue I will gather info about such problems that occurred in the wild for future reference:
See also:
Workaround
The text was updated successfully, but these errors were encountered: