Open Bug 1800880 (clipchamp) Opened 2 years ago Updated 2 months ago

Clipchamp not supported in Firefox

Categories

(Web Compatibility :: Site Reports, task, P2)

Product:
Web Compatibility
Component:
Site Reports
Type:
task

Tracking

(Not tracked)

People

(Reporter: denschub, Unassigned)

References

(Depends on 3 open bugs,
URL
)

Details

(Keywords: webcompat:platform-bug)

User Story

platform:windows,mac,linux,android
impact:blocked
affects:all

Clipchamp, now a Microsoft product, isn't supported in Firefox. From the WebCompat bug, where one of their engineers commented, we've learned that there are a couple of platform features and bugs that are relevant here.

Let's use this metabug to keep track of those!

Depends on: webcodecs

Tentatively adding bug 1486454 as another dependency, as per the comment in the web-bug. It might be a different performance issue, but it's worth keeping track of that in some way.

Depends on: 1486454
Depends on: 1886472
Depends on: 1886474
User Story: (updated)
Keywords: meta → webcompat:platform-bug
Summary: [meta] Clipchamp support in Firefox → Clipchamp not supported in Firefox
Whiteboard: webcompat:unsupported
Severity: -- → S2
No longer depends on: webcodecs, interop-2024-requestVideoFrameCallback
Priority: -- → P2

I tested Clipchamp spoofing the UA on both nightly and my WIP rVFC implementation. On nightly, the video doesn't show at all, and neither video nor audio work when you click play. With the WIP patches, the video interface is visible, you can apply filters / etc, and you can navigate the timeline. Currently, when you click on play, it plays back audio but frames aren't updating properly. I should be able to get this working better with some changes.

Depends on: interop-2024-requestVideoFrameCallback
No longer depends on: 1886472
Whiteboard: webcompat:unsupported
No longer depends on: 1886474
Depends on: webcodecs

I did some brief testing of clipchamp and it seemed to mostly work. I've reached out to an engineer on the product in https://github.com/webcompat/web-bugs/issues/59616#issuecomment-2379433251 to see how things are looking now.

You need to log in before you can comment on or make changes to this bug.