Live data from Hacker News

Video: A Language for Making Movies

lang.video

51–60 of 60 posts

Re: Video: A Language for Making Movies

#51

Earlier quoted context omitted.

I clicked off for this reason. Sounds really interesting but nowhere does it even show a screenshot or capabilities.

Author here. Yikes, I didn't realize that Racket's documentation builder broke. It looks like it has for some time. I'll fix that momentarily. In the meantime, you can look at the source for the documentation at: https://github.com/videolang/video/blob/master/video/scribbl...

Oh, it also looks like @arm found a wayback snapshot at:

https://web.archive.org/web/20210419191239/https://docs.rack...

Still will fix that ASAP, thanks!

Re: Video: A Language for Making Movies

#52

Unfortunately not updated anymore, but in essence it was just an interface to ffmpeg options. So either create pre-defined script modules for all your ffmpeg tasks, or video language scripts. Practically it doesn't really matter, but I think I'd go for simple scripting modules out of familiarity.

Ya, I haven't updated video in years. I'm perfectly happy to do it, but I just haven't had a need, and no one asking for updates. :D

There is a lot of overlap between video and ffmpeg's filtergraph. The biggest difference, however, is that video tries to provide a full language on top of it, that tries to use NLVEs as an abstraction, rather than pure filters.

It worked out very well for lots of videos with very similar composites (in my case it was making conference recordings). But frankly, OBS also fit the bill almost as well so we started using that.

Re: Video: A Language for Making Movies

#53
post #31
post #28

Earlier quoted context omitted.

No: https://github.com/videolang/video/commits/master/ . Last commit November 2019.

Im not sure, but I think Leif has graduated

That I did. You can find my dissertation here: https://www2.ccs.neu.edu/racket/pubs/#dissertation-andersen

Re: Video: A Language for Making Movies

#54

I'll be that guy: curious name :/

Author here:

Ya...its a terrible name. Most of the people I work with tell me I shouldn't be allowed to name things. And frankly, I agree. I mean, for fuck sake, I named my latest project (hybrid visual-textual programming languages): VISr:

https://visr.pl

It was supposed to stand for visual and interactive syntax realized, buuuut....ya.

(For the record, I got started working on VISr because I wanted interactive code snippets in my Video programs. And while I 'technically' got a prototype of it, as documented in my dissertation, its very...lacking...)

Re: Video: A Language for Making Movies

#55
post #7

I'll be that guy: curious name :/

I wish people would stop using common nouns for program names, not only is it hard to search for, but it's kind of ... arrogant? Like you think you're the best there is and will ever be for that particular noun? Imagine if Google Chrome renamed to 'Browser'

Author here:

The idea for calling it Video originated from it just being a library in Racket for editing videos. The name `video` fit the trend for packages in Racket at the time:

* `pict` - was an existing library for making pictures * `slideshow` - was an existing library for making slideshows * `math` - was an existing library for...well..math (beyond what the language natively provided) * `web-server` - was an existing library for making webservers.

You get the idea, extending it:

* `video` - was a new (and thus far only in Racket) library for making videos. (note the lower case `v`)

Unfortunately video grew far beyond what I expected it to (yes still small, but I honestly expected to be the only user ever, rather then one of a dozen or so users). Unfortunately as mentioned in previous comments, I suck at naming things. But also unfortunately, no one else offered another name. So video just sort of...stuck. I eventually tacked `Lang` onto the end of it, and made the initial `V` uppercase in a desperate attempt to give it a slightly more unique name. But then that became too close to videolan...which...sigh...did I mention I fucking suck at naming things?

Re: Video: A Language for Making Movies

#56
post #49

Cool! I am the maintainer of a project that does very similar things. Maybe this is relevant for people trying to compose videos in JS or TS. https://github.com/redotvideo/revideo It's based on the browser canvas and allows for instant preview of compositions. We recently rebuilt our renderer on top of the web-codecs API which makes it super fast. Would love some feedback!

Author of videolang here:

Oh wow, that's really neat!

I'd also love to plug Remotion https://www.remotion.dev/ That also has a video making product. (I don't work with them, but would love to!)

Re: Video: A Language for Making Movies

#57

Earlier quoted context omitted.

This looks interesting. Thanks for digging that up. I've done a little video editing using Adobe Premiere (mid-2000's) and Shotcut (2022). The UI for both seemed overwrought and difficult to get what I wanted out of. A text description of timecodes and filter parameters sounds a ton easier to use. Having said that, I assume that would exist if the market actually wanted it.

Avisynth+ does that. It is well supported and has a huge community. http://avisynth.nl/index.php/Main_Page

Author of videolang:

Avisynth+ is awesome.

Interestingly enough, the first version of video was actually built on top of libmlt: https://www.mltframework.org/

I was just dissatisfied with it due to its lack of functions. I can't remember why I didn't just use avisynth as it does actually have functions.

Re: Video: A Language for Making Movies

#58
A clever name, but not a good one.

Makes the headline read weirdly, doesn’t tell me anything about what it is and probably has poor SEO.

Also, as someone with literally 0 video editing experience, why would I want my video editor to be programmable?

Re: Video: A Language for Making Movies

#59
post #9

Archive.org link for the v0.2 documentation: https://web.archive.org/web/20210419191239/https://docs.rack...

This looks interesting. Thanks for digging that up. I've done a little video editing using Adobe Premiere (mid-2000's) and Shotcut (2022). The UI for both seemed overwrought and difficult to get what I wanted out of. A text description of timecodes and filter parameters sounds a ton easier to use. Having said that, I assume that would exist if the market actually wanted it.

I agree the UI for Premiere can be overwhelming to a new user. Also, the keyboard shortcuts are clearly assigned by engineers and not editors.

When I switched from tape-to-tape editing to NLEs in 2005, I started a new keyboard shortcut layout that was more intuitive, and was all on the left side of the keyboard, allowing the right hand to never have to leave the mouse.

I made a tutorial teaching Premiere by way of these shortcuts (although these shortcuts work on just about every NLE, with slight variations). The tutorial is long, but if you just go through the first part, explaining each shortcut, you can get pretty far along learning how to edit with Premiere.

The video and shortcut layout download is here: https://davidblairportfolio.com/daves-premiere-pro-tutorial

This might be the only editing tutorial that uses as an editing example the editing of the tutorial you're watching.

Post reply on HN