Live data from Hacker News

OpenShot 4.0 – Open-source video editor

openshot.org

131–140 of 148 posts

Re: OpenShot 4.0 – Open-source video editor

#131

Earlier quoted context omitted.

What do you mean? Like it can export audio to a separate file?

Provides a simple baked workflow to normalize audio in a manner that survives YT encoding. Warning for headphone users, the tutorial has examples of what not to do. =3 https://www.youtube.com/watch?v=xYFbOKDgSbw

Am I missing something? This is a very regular workflow that works the same in all software. It seems to provide you with a LUFS meter, then you manually adjust volume to what youtube expects you to.

> normalize audio in a manner that survives YT encoding.

> Discover how to avoid YouTube's compression and achieve crystal clear sound.

Youtube won't audibly compress your audio. It will just turn it up or down to the desired LUFS level. You being at a -8 LUFS will not cause any more compression compared to you being at -14. I'd argue that this video is misinformation presented as something useful.

Re: OpenShot 4.0 – Open-source video editor

#132
post #56

Earlier quoted context omitted.

> Most people want a video editor to splice and concatenate video files without any loss or transcoding You can do this with mpv. It's an open source cross platform media player. For example, here's how I set up a tiny Lua script extension[0] to be able to visually cut videos in an intuitive way. It does it in seconds without re-rendering the video by shelling out to ffmpeg. Years ago I did the same thing with a shel…

This is very cool! Do you have a similar workflow for stitching those cut clips together?

Video editor app that generates FFmpeg commands https://news.ycombinator.com/item?id=42207002

Re: OpenShot 4.0 – Open-source video editor

#133

I've supported OpenShot financially in the past, but I'm currently leaning towards LosslessCut and Shortcut. Most people want a video editor to splice and concatenate video files without any loss or transcoding. I believe this behavior (lossless) should be default on all of these editors.

Try Kdenlive

Re: OpenShot 4.0 – Open-source video editor

#134

Earlier quoted context omitted.

Provides a simple baked workflow to normalize audio in a manner that survives YT encoding. Warning for headphone users, the tutorial has examples of what not to do. =3 https://www.youtube.com/watch?v=xYFbOKDgSbw

Am I missing something? This is a very regular workflow that works the same in all software. It seems to provide you with a LUFS meter, then you manually adjust volume to what youtube expects you to. > normalize audio in a manner that survives YT encoding. > Discover how to avoid YouTube's compression and achieve crystal clear sound. Youtube won't audibly compress your audio. It will just turn it up or down to the de…

Audio dynamic compression means something different from file data compression.

https://en.wikipedia.org/wiki/Dynamic_range_compression

It is a trick abused by advertisers for years, to be perceived as "loader" at the same volume setting. If one blindly exports whatever standard you edit in... ymmv =3

Re: OpenShot 4.0 – Open-source video editor

#135
post #121

Earlier quoted context omitted.

Designers have it really hard in free software because good design is about understanding the big picture, knowing what to leave out, have product vision to follow. That's tough to do in environment where goal is to make everyone happy and the biggest say have programmers who are developing the thing who are usually not interested in design, inexperienced in design or have their personal very specific product vision.

I think you definitely identified the issue well. Changing the design of an existing project, especially if you're not already involved in the project is a daunting task. You have to try and convince a core group of users that the design is going to be better to entice new users. But the problem is that those core group of developers likely don't care that the UI isn't up to par, and likely don't want it to change. I…

I don't agree about the AI at all. AI is terrible at design (compared to programming).

Having relatively nice UI skin doesn't equal good design. They are surprisingly unrelated as i am sure people know highly usable well designed software with bad UI and also know super beautiful UIs that are unusable - badly designed.

AIs are bad at design because they don't understand and can't keep context of the whole together. Just like in programming they are much better at solving single well defined problem. Design is very much opposite of that, it's always about reharmonizing in context with the whole after you make a change.

Re: OpenShot 4.0 – Open-source video editor

#136

Earlier quoted context omitted.

Am I missing something? This is a very regular workflow that works the same in all software. It seems to provide you with a LUFS meter, then you manually adjust volume to what youtube expects you to. > normalize audio in a manner that survives YT encoding. > Discover how to avoid YouTube's compression and achieve crystal clear sound. Youtube won't audibly compress your audio. It will just turn it up or down to the de…

Audio dynamic compression means something different from file data compression. https://en.wikipedia.org/wiki/Dynamic_range_compression It is a trick abused by advertisers for years, to be perceived as "loader" at the same volume setting. If one blindly exports whatever standard you edit in... ymmv =3

> Audio dynamic compression means something different from file data compression.

This is what I was trying to say. "You being at a -8 LUFS will not cause any more compression compared to you being at -14. "

You ignored my points and bring up something unrelated. The guy in the video shaved off 1 or 2dbs if I remember correctly, which would be barely noticeable. And Resolve didn't do this automatically, he had to manually measure LUFS, insert a limiter and dial in the settings. Not sure what's your point is. LUFS is designed in such a way to give a reliable metric on loudness. The reason compression is abused on TVs is because they use a naive dB metric in the regulations (iirc) so it's possible. YouTube doesn't do this. The use LUFS as shown in the video, that again, gets automatically adjusted to compensate. What the video shows is NOT AUTOMATIC (the worklow is not simple, nothing special nor baked in), and arguably pointless.

Re: OpenShot 4.0 – Open-source video editor

#137

Earlier quoted context omitted.

Audio dynamic compression means something different from file data compression. https://en.wikipedia.org/wiki/Dynamic_range_compression It is a trick abused by advertisers for years, to be perceived as "loader" at the same volume setting. If one blindly exports whatever standard you edit in... ymmv =3

> Audio dynamic compression means something different from file data compression. This is what I was trying to say. "You being at a -8 LUFS will not cause any more compression compared to you being at -14. " You ignored my points and bring up something unrelated. The guy in the video shaved off 1 or 2dbs if I remember correctly, which would be barely noticeable. And Resolve didn't do this automatically, he had to man…

https://en.wikipedia.org/wiki/Sealioning

Best of luck, bye =3

Re: OpenShot 4.0 – Open-source video editor

#138

Earlier quoted context omitted.

> Audio dynamic compression means something different from file data compression. This is what I was trying to say. "You being at a -8 LUFS will not cause any more compression compared to you being at -14. " You ignored my points and bring up something unrelated. The guy in the video shaved off 1 or 2dbs if I remember correctly, which would be barely noticeable. And Resolve didn't do this automatically, he had to man…

https://en.wikipedia.org/wiki/Sealioning Best of luck, bye =3

Resolve isn't special in what it's doing. This is a regular workflow that works like this in all software and isn't automated at all like you are claiming it is. It does not "prepare your audio". Bye

Re: OpenShot 4.0 – Open-source video editor

#139

Earlier quoted context omitted.

https://en.wikipedia.org/wiki/Sealioning Best of luck, bye =3

Resolve isn't special in what it's doing. This is a regular workflow that works like this in all software and isn't automated at all like you are claiming it is. It does not "prepare your audio". Bye

It literally prepares the audio for export, though. There is an export setting that allows you to choose the audio codec, channels, encoders, target true peak or LUFS level, and then normalize or "optimize" (built in limiting and compression) the audio to that level. For example, you can choose "Youtube" to optimize your audio automatically for Youtube. It also has a built-in dialogue leveler, for example. It has more audio capabilities built-in than many other video editors, although there are paid ones with the same capabilities.

You can easily do the same in Reaper, of course, but it will require you to export audio, then process externally, and import it again, so it's not the ideal workflow.

Post reply on HN