Lightworks Video Editor To Go Open Source
Art3x writes "EditShare will release its video editor as open source this summer. Lightworks handles high-definition media, DPX, and RED, shares projects with Final Cut Pro and Avid, and was recently used by Academy-award-winning editor Thelma Schoonmaker on Shutter Island. Introduced in 1989 and bought by EditShare last year, it 'has come from over one million hours of software development,' says EditShare's James Richings. But he says releasing the source will 'generate concepts and capabilities never seen before. I expect that the Lightworks Open Source initiative will transform not only the technology, but also the opinions on what a professional editing tool can achieve.'" From the press release's description, it sounds like the "open source" phase will follow a period of free-as-in-beer downloading.
I hope it's released under a truly free license like the BSD or the MIT license. That's the only way to maximize everyone's freedom.
People can use instead of their stolen Adobe Premiere programs.
And we all know what runaway success that GIMP is.
It's dead is what it is, that's all. Nothing like a million more to each contribute an hour to get another million hours. Yeah, baby!
You can edit RED with the open source version, but you have to pay if you want to edit blue or green.
Are they going to continue to provide developers and push some form of direction?
From what I've seen the only successful OS projects are grown from scratch or 50%+ maintained by a single company.
Paying taxes to buy civilization is like paying a hooker to buy love.
Beer is not free, unless you brew it yourself, scam on some rich cougar, or steal it. Free as in beer is a better analogy for piracy or convincing your drunk boss he hasn't yet bought a round, despite having done so, thrice, at friday drinks.
After logging in slashdot still does not take you back to the page you were on. It's been that way for 20 years.
That's 18 developers working 8hrs a day, every day for 20 years.
All the important open source commercial products are free BSD style licences:
* The OS X base OS parts
* The fastest webbrowser Chrome
* And Google's upcoming Chrome OS
* The amazing LLVM compiler tools that people are dumping that massive pile of fail GCC for
Companies now know to avoid the nightmare the GPL is.
Yay! Yet another open source project that will likely stagnate at best, or (more likely) will end up with a million different forks due to all of the inevitable bickering about which direction development should go. The only way to prevent this would be some kind of centralized development effort, and I'm not holding my breath. Besides, if they've decided to go the open source route, EditShare has effectively acknowledged that the tool provides them little commercial value, and that in turn implies that the company more or less considers the tool to be dead.
I'm really excited about this move. The first editing system I ever experienced when I was young was a Lightworks/Heavyworks system. My dad (a film editor, now director) loves the Lightworks systems due to their natural and intuitive control systems. I still have an old Lightwave controller sitting around that I've thought about hacking to work with the Avid.
Currently we work on Avid Media Composer, since it remains the only true pro-level editing software. Final Cut has it's pros but, at least to me, it's more for video editing (by which I mean not sourcing or finishing to film) and smaller projects (promos, commercials, shorts). If you want to cut a feature film - you use Avid. I have arguments with co-workers about FCP versus Avid but we usually arrive at the agreement that Avid is simply the standard to which all other systems are currently judged.
With the open sourcing of Lightworks I can only hope that the best of modern systems like Avid and FCP can be integrated with the very intuitive Lightworks way of working. At the very least, I hope it scares Avid and Apple at least enough to make them fix some of the problems that currently exist with their systems. More competition is always better for the end user.
I read the press release and even visited the website. I can't find ANYTHING that reveals the system requirements for this software. Is it a Mac application? Windows? Linux? If it won't run on my OS of choice, why should I care about it?
This appears to be an application that was never available in retail channels in the first place and has no market share or brand equity.
Translation:
It sounds like the "open source" hype, in combination with a free-as-in-beer download, will win massive marketshare, followed by the release of a "premium" version to capitalize on that.
Note that this works whether it's released as (netscape-style) open-source, or whether that promise fades away -- as long as everybody got their free copy, and knows that open-source is "around the corner", you can go quite a long way without a shred of code released.
and was recently used by Academy-award-winning editor Thelma Schoonmaker on Shutter Island
That's funny, because I remember specifically thinking that the editing was horrible when I saw Shutter Island in the theater. If anything such a claim makes me wary of using this software. Although I suppose you can't blame bad editing on the software, but rather on the people using the software.
For the past few years, all my video splicing has been done with the mediocre editor built into Blender. Which works well enough for a feature built into a 3D modeling/rendering program, but is far less usable and efficient than any dedicated one.
Maybe thats just me, but does anyone see any system requirements on anywhere? I read the press release, looked all over the company website and still could not find anything even remotely looking like system requirements anywhere.
I would guess that there is a Windows version and since it seems to integrate with Final Cut Pro, a Mac version seems likely as well, but there is no way to be sure and strangely, I could not find anything.
Also, it seems that Lightworks was only recently (August 2009) acquired by EditShare. Making it OpenSource now could mean that EditShare maybe was not able or willing to continue developing, selling and supporting the program and now tries to salvage something by open-sourcing it, hoping the community will pick up the slack.
Dude, get over yourself. Yeah, C and C++ are not ideal in every way; but no language is. They are still quite useful. There is a lot of good software out there written in them (such as Firefox itself).
If you really want to contribute, and help fix said security issues, it would behoove you to learn them. Otherwise, I'd recommend finding a project written in the language of your choice, and contributing to that. It doesn't make that much sense to complain about a project not being in your favorite language and asking for an extension mechanism using another language just so you can contribute.
I'll push it a little further by saying. What really makes Richard Stallman the true genius behind Linux is not his code or gcc, but the little bit of virus he put in every GPL.
How's that sound?
Deleted
I refuse to ever use C/C++, because I consider its outdated design [...] and its inelegance and programming inefficiency to be a pain to my brain.
No problem. All Lightwave development is done in LOGO. Just tell the turtle what you want it to do.
This ain't rocket surgery.
But I refuse to ever use C/C++, because I consider its outdated design to be the cause of pretty much every security exploit out there, and its inelegance and programming inefficiency to be a pain to my brain.
I bet you were told you were special when you were a kid right?
All the important open source commercial products are free BSD style licences
And that is your list of important products?
HAHA
OSX- used by no one in the enterprise and pointless as a server OS
Chrome: a browser with no marketshare, even opera is more popular
Chrome OS: will be linux, meaning GPL kernel!
LLVM: nice idea, but no one is using it.
Chrome is also a bad example. It's based on WebKit, and portions of WebKit are under the LGPL. I doubt they've stripped out and rewritten all of WebCore.
Check out my sci-fi/humor trilogy at PatriotsBooks.
LLVM: nice idea, but no one is using it.
Or, nice idea, implemented in a terrible language. Could have been much nicer if it had been designed along the lines of COLA/OMeta. And - that's a wild guess, though - much, much shorter.
Ezekiel 23:20
Let's see.
On the one hand you have LLVM taking over the compiler tech world like no other project in the history of the field.
On the other hand you have some random idiot on Slashdot...
Go back to that laughable turd GCC dummy.
I only found a press release written in marketingdroidese claiming a lot of things, mostly vapid. However I found no publicly available source code. Nor even what the released source code will actually be, since the press release is so vacuous you cannot understand which parts of the application will be open source, or if it is the whole application. Nor even in which license the source code is supposed to be released in.
Or, nice idea, implemented in a terrible language.
pcc looks promising!
Writing any compiler in C++ is kind of like using a seized up jackhammer with one hand to thread a needle, except you'll be happier with the results from the analogy.
What's the appeal of a supercompiler anyway? Systems languages that can't be self hosted aren't complete systems languages.
Oh no an internet toughguy!
An anonymous one at that, what a surprise.
Your comment is beyond awesome. That comment makes the FSM smile upon you and will get you closer to an eternity spent in the shadow of the beer volcano and within walking distance of the stripper factory.
You got owned.
That would i
Well, you have to admit it's hard being a touch guy when you're 5'2, weigh 80 lbs and are 12 years old.
Thanks. May you be touched by his noodly appendage.
This ain't rocket surgery.
On the one hand you have LLVM taking over the compiler tech world like no other project in the history of the field.
Making shit up or you got a citation for that?
Even the projects built with llvm page shows nothing all that interesting.
On the one hand you have LLVM taking over the compiler tech world like no other project in the history of the field.
Uhhm, sorry? I see no such thing. The field of programming language compilers is diverse and LLVM most certainly does not fit all scenarios, and perhaps not even all languages. (One of my friends tried to implement some sort of Scheme-like system language, he had rather strict requirements and he found the LLVM IR model deficient - tail calls, continuation, type system...I can't remember now what exactly was the problem, it was a few years ago - but perhaps they have extended it by now.)
Ezekiel 23:20
Looks like you'll have to register to get more info :
http://www.editshare.com/index.php?option=com_wrapper&Itemid=208
If only I had mod points, you'd definitely get some
> What a bunch of retards.
>
> Do you GNU idiots actually think anyone is falling for your lame attempts at word games to cover up your shitty viral license?
I was thinking the exact same thing about you lot that have a notion of "freedom" that neglects human nature.
A Pirate and a Puritan look the same on a balance sheet.
OSX is a bad example because you need to use highly proprietary software to get anything out of it.
It's not like anyone uses OSX for the BSD.
BSD just enabled Apple to get the underside of the OS for free.
Bring the iphone/ipad into the picture and it only gets worse.
A Pirate and a Puritan look the same on a balance sheet.
FYI. I consider Haskell my favorite language. So coming up to an elitist like me, by using elitism... not such a great idea... ;))
Any sufficiently advanced intelligence is indistinguishable from stupidity.
It's entirely clear from the press release that they have no intention whatsoever of opensourcing the "feature rich underlying technology" of the "NLE 's core engine".
This is the same sort of thing that Xara tried to pull... using the open source community to add additional power and functionality that all ultimately still depended on a proprietary close-source rendering engine. That went well!
---
the pen is mightier than the sword, the sword is mightier than the court, the court is mightier than the pen.
OSX- used by no one in the enterprise and pointless as a server OS
But has more than 5x the overall share of Linux, and makes up a disproportionately large percentage of the pro media market.
Chrome: a browser with no marketshare, even opera is more popular
I don't know where you're getting your numbers, but Opera isn't more popular than Chrome. A more sensible argument would have been pointing out the the rendering engine is GPL.
LLVM: nice idea, but no one is using it.
Apple is heading the development of LLVM/CLANG and is very much using it, the free BSDs are all working to move over to it (FreeBSD is about 80-90% there last I heard). Others will follow suite.
Though I could say the same about what it's aiming to replace; nobody really uses GCC either, the BSDs are all moving to PCC/LLVM, Apple is moving to LLVM, MSVC sees the most use on Windows systems, Sun Studio sees the most use on Sparc systems, ICC on Itanic, GCC is only really significant on Linux, and less than 1% of the market uses that.
I'd like to throw in that the most deployed Unix system (SFU/SUA) is BSD derived as well.
Apache is under the BSD-like Apache license, as are Derby, Catalina and Tomcat/Jakarta.
PHP is under the BSD-like PHP license.
PostgreSQL is under a BSD-like license.
SQLite is public domain, and thus closer to BSD than GPL.
Firefox is tri-licensed, but people like to forget about the other two licensing options.
GlassFish, the j2ee referrence implementation is under CDDL.
Mono, RoR, XWindows and Lua are MIT-licensed.
That's just off the top of my head.
One of my friends tried to implement some sort of Scheme-like system language, he had rather strict requirements and he found the LLVM IR model deficient - tail calls, continuation, type system...I can't remember now what exactly was the problem, it was a few years ago - but perhaps they have extended it by now.
"Type system" complaint doesn't make much sense, to be honest. LLVM is really just "portable assembly". Type system? It offers the basic primitive types, aggregates thereof (arrays, structs), and pointers to them. That is sufficient to build a data structure of any complexity. Any actual type system of your language would be entirely separate, and may not even trivially map to any of LLVM types - the latter are implementation details.
With respect to tail calls, LLVM has them - unlike C, and that one is actually a big deal because you really have to have tailcall support even on such a low level, because it is something that cannot be efficiently worked around (you can do it if you provide your own call stack, which is obviously not efficient).
Continuations? If we're talking about full-fledged re-invokable ones (which is what call/cc is), then you can't have them without spaghetti stack, anyway - meaning that you have to ignore whatever the platform (and therefore LLVM) provide you, and roll out your own. If it's just a rewinding facility, then LLVM has it.
To sum it up: if you can write a compiler of some language to assembly, you most assuredly can write a compiler for the same language to LLVM.
I'd like to take the opportunity to plug video editing with AviSynth. No, there's no GUI and it only runs on Windows. But, if you want to take the power of scripting and programming to the world of video editing, this tool is for you.
There was at one time a project to make a version that ran cross-platform, but it ran out of steam.
Computers are useless. They can only give you answers.
-- Pablo Picasso
Yeah, that's how I read it too. They're releaseing it for free (as-in-beer) with an SDK. Then they plan to make money off of it by running an "App Store" like service for the plugins.
Don't get me wrong, a no-cost video editor is a good thing. But I think Linux and/or Open Source fans are going to be dissapointed.
BSD license:
freedom to see, modify, and redistribute the source code of an application that I use = 0
GPL license:
freedom to see, modify, and redistribute the source code of an application that I use = 3
Clearly, the freedom I get with the GPL is bigger than the freedom I get with the BSD license.
Your so-called freedoms are the "freedom" of people who didn't contribute to the software to restrict other people from modifying and redistributing the software. Sometimes software developers grant these additional freedoms in order to achieve some other goals, but they are of no intrinsic value to the developer or the user.
By analogy, if we legalized fraud and murder, people would have more freedom, but that doesn't make legalizing fraud and murder desirable.
Do you BSD idiots actually think anyone is falling for your lame attempts at word games to cover up your shitty corporatist agenda? You want companies like Microsoft, Apple, Sony, and others to profit from volunteer work while at the same time making systems more and more closed.
GPL is clear about what freedom it intends to protect: the freedom to develop and modify software.
Retards like you are the enemies of that freedom.
BSD based OS X has kicked the shit out of the stinking pile of fail that the GPL Linux desktop
There is some BSD software in OS X, there is also tons of GPL software. Apple wouldn't exist without it.
I think Apple fanboys fear the GPL so much because they know that if Apple couldn't rip off BSD software and other people's inventions, they'd be out of business.
It's not like anyone uses OSX for the BSD
*cough* hello?? Loads of geeks use OSX precisely because it has BSD under the hood. I know it's fashionable to bash Apple at the moment for some reason, but wind the clock back 2 years and plenty of people were buying a MacBook so they could have the best of both worlds.
What complete and utter drivel. You have no idea how many systems use BSD licensed code for the very reason that they have closed sourced it.
The license came into existence purely so that big business, and maybe development team members, could privatise the code, which had been produced in government funded educational institutions. It was a clever ruse.
Releasing bits of the code upstream while keeping the most important bits closed is just another technique to keep the dimmer members of the programming community on board and contributing.
BSD is freer in much the same way that the type of democracy they had in Germany before the war was freer - because it allowed them to vote away their democratic rights.
Yoda I am, insensitive clod.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
"Ripping off" ??? If the BSD creators felt this way and would not approve such use, they would have used a different license... Apple does what it's allowed to do with the software. They don't want to reinvent the wheel, unlike some Redmond-based company, and are prepared to go for the best sollutions for their customers. They use/support webkit, they distribute Apache and countless other opensource applications with their OS. Want it or not - that's what they are allowed to do.
Most people here have to shut up about licenses - since 99% have never even written any code. It's the developer that decides what someone else would be able to do with his code, and that's nobody else's decision.
Great detailed information, I ll be visiting you more frequently, here is very interesting information. green world
So, now where can I find a good video capture and playback card, which deliver all video formats in a unified open I-frame-only compressed format (e.g. Dirac) to the software, along with the audio in perfect sync (e.g. audio chunks grouped and tagged with video frames), and also accept exactly that same stream (even if re-ordered frame by frame) on output. Compression is important to avoid having to process 250 megaBYTES of data for HD. Also, this hardware needs to have the various forms of audio/video input/output that are in common use in the marketed region, including genlocked synchronized output. For the USA this would include the SDI and HD-SDI commonly used in broadcast, as well as Firewire, HDMI and preferably also analog. And, of course, its driver needs to be full open source suitable for use on BSD and Linux. If the hardware to software interface is designed in a straight-forward simple manner, with basic commands to set modes, query detected input modes, and read/write data blocks frame by frame, there would be no secrecy needed in the driver.
now we need to go OSS in diesel cars
The difference in security of programming between the C/C++ languages and higher languages, is that in the former case, security is the responsibility of the programmer, whereas in the latter case, security gets delegated to the language framework. Not all programmers can get it right for the former. OTOH, the latter risks programmers doing something really stupid because they think their arse is covered.
now we need to go OSS in diesel cars
why so sore? why so stupid? doesn't it suck to play foul and still lose? just... move over already.
Or if they want to make sure their developers get paid, they could release it dual license GPL / proprietary. That way everyone brings something to the table: cash or code.
And, no, despite the talking points from this season's blusterings from M$partners, the project maintainer is not required to accept the code. That stands regardless of the license used, GPL, BSD or other. And regardless of the license, they are still in the best position to earn money from customization or deployment. Even if something is FOSS and easy to deploy, there are still a lot of companies that would rather pay you to set it up right the first time and walk their staff through the process. Do it in a way that they're happy about and they'll call back with more orders.
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
That comment makes the FSM smile upon you and will get you closer to an eternity spent in the shadow of the beer volcano and within walking distance of the stripper factory.
WTF, don't they ship?
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"