Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Clipchamp

clipchamp.com

Post reply on HN
Print view View original

131–136 of 136 posts

Re: Microsoft Clipchamp

#131

Post by disqard »

mackrevinack wrote: post #124
FractalParadigm wrote: post #14

I used this software (the app version) a couple weeks ago for the first time. I grabbed a great clip while playing a game and wanted to show it to a friend, but I didn't want to send the full 500MB 60s video when the clip was only ~6 seconds. I didn't want to spend a ton of time downloading proper editing software so I gave it a shot. It's a little clunky if I'm honest, it feels like an evolution of Windows Movie Mak…

LosslessCut is my go to for that sort of thing https://github.com/mifi/lossless-cut

Wow! Fantastic tool (just tried it out) -- thank you for the rec :)

Re: Microsoft Clipchamp

#132

Post by aliswe »

NordSteve wrote: post #107
kuratkull wrote: post #40

Firefox users are asked to please stay away: It looks like your browser is not supported To use Clipchamp, make sure you're using the latest version of Google Chrome, or the latest Microsoft Edge

Hi! Engineer who actually works on Clipchamp. Sorry you ran into that issue. Firefox support is in the works - we plan to support the same set of browsers as the other Office features, as described here: https://support.microsoft.com/en-us/office/which-browsers-wo... If this tech looks interesting, come join us! We have a bunch of open engineering positions in Brisbane that are 100% WFH from Australia: https://career…

Hi, am I being obstinate for thinking "Sorry you ran into that issue" is a bit strangely worded?

Re: Microsoft Clipchamp

#133

Post by lupire »

aliswe wrote: post #132
NordSteve wrote: post #107

Earlier quoted context omitted.

Hi! Engineer who actually works on Clipchamp. Sorry you ran into that issue. Firefox support is in the works - we plan to support the same set of browsers as the other Office features, as described here: https://support.microsoft.com/en-us/office/which-browsers-wo... If this tech looks interesting, come join us! We have a bunch of open engineering positions in Brisbane that are 100% WFH from Australia: https://career…

Hi, am I being obstinate for thinking "Sorry you ran into that issue" is a bit strangely worded?

It's just corpspeak.

Re: Microsoft Clipchamp

#134

Post by BuckRogers »

sorenjan wrote: post #110
BuckRogers wrote: post #105

Earlier quoted context omitted.

Stuff like that and late AV1[0] are one reason I moved to Edge after 19 years on Firefox. More so just that I was impressed with Edge when I tried it. Brave also stood out to me when I tested every browser. It’s fast but has the distinction of being the only semi-major browser that’s fully open source other than Firefox. Edge is still very good, I would say it’s the best browser going but I’d be tarred and feathered…

I think using Chrome or Edge for PWAs and Firefox for general browsing is an acceptable compromise. I don't need to use the same program for video editing and reading news articles etc, although it would be nice if I could.

For the technologist that wants that single program, and values privacy and transparency like most of us do, Brave fits the bill nicely. It’s currently my second favorite browser after Edge.

That said, I had Clipchamp installed from the MS Store before I went back to MS Video Editor.

Re: Microsoft Clipchamp

#135

Post by indrora »

mrtksn wrote: post #86
kuratkull wrote: post #40

Firefox users are asked to please stay away: It looks like your browser is not supported To use Clipchamp, make sure you're using the latest version of Google Chrome, or the latest Microsoft Edge

Feels like 2000s again, we are supposed to switch browser for each site again.

It helps when Mozilla has a backbone and shows up to the standards meetings.

Re: Microsoft Clipchamp

#136

Post by stnvh »

swores wrote: post #96
detaro wrote: post #94

Earlier quoted context omitted.

And not adding it and not testing for Firefox would cost nothing, and currently improve the user experience - because it actually just works, as a lot of things just do.

But then what if a bug in their code that only affects FF goes unnoticed due to testing, and causes significant problems for a big client, or a journalist reviewing it, or... Personally I feel a "We don't officially support this browser, it probably works but we only test for full compatibility in " is a better option if you're going to go in that direction. But I can understand why even that is a bit of a risk as if…

It seems more like the devs at MS know their code works on Firefox but have been asked by exec to push chromium(-esque) because edge is now webkit.

sidenote: this is a multi-billion $ company, no excuse to ignore any platform with their capacity, front face it looks like they can't build a good app anymore, especially if it works anyway with a simple string change in the browser - heck, web devs had to factor in ie7-8 polyfills built by the community only a few years ago. no excuse.

Post reply on HN