Announcement

Collapse
No announcement yet.

Lightworks Linux Beta Is Finally Public

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Ancurio
    replied
    Originally posted by zester View Post
    I don't have to see there code, I know what its dependance’s are and I know what its linking to, on top of that I helped maintain Gtk for 8 years prior to v3.
    I have no idea what you're talking about. Of course the app would link to GObject/GLib/GDK and the 6 or so other dependencies
    of GTK because that's what they are: dependencies of GTK. I don't have to touch Pango, or gettext, to use GTK. Same with GObject.

    Originally posted by zester View Post
    Other than there own personal library's I know how the rest of it was put together. Core system functionality is using Glib, anything remotely object related is using GObject.
    You're talking about GTK here, not Lightworks.

    Originally posted by zester View Post
    If there not using GObject for object related functions and instead mixing plane Gtk+ C and C++ there still going to be using GObject(See Below) but note that mixing
    Gtk+ C and C++ is an extremely complex issue to have to deal with on your own, hence the development of Gtkmm and Xfce's C++ SDK.

    Even if there entire interface is OpenGL based, other that the windowing system. There still using Gtk Widgets and Gobject to embed the OpenGL viewport.

    Gtk Widgets, GDK, Glib, GObject are not mutually exclusive, if your using one then your using all of them to some degree.
    Why the hell would they use GObject? I just told you they aren't even using Gtk widgets, there is no need whatsoever to extend Gtk.
    You're just throwing around baseless claims without any backup.

    Leave a comment:


  • zester
    replied
    I don't have to see there code, I know what its dependance?s are and I know what its linking to, on top of that I helped maintain Gtk for 8 years prior to v3.

    Other than there own personal library's I know how the rest of it was put together. Core system functionality is using Glib, anything remotely object related is using GObject.

    If there not using GObject for object related functions and instead mixing plane Gtk+ C and C++ there still going to be using GObject(See Below) but note that mixing
    Gtk+ C and C++ is an extremely complex issue to have to deal with on your own, hence the development of Gtkmm and Xfce's C++ SDK.

    Even if there entire interface is OpenGL based, other that the windowing system. There still using Gtk Widgets and Gobject to embed the OpenGL viewport.

    Gtk Widgets, GDK, Glib, GObject are not mutually exclusive, if your using one then your using all of them to some degree.

    Leave a comment:


  • Ancurio
    replied
    Originally posted by zester View Post
    And there not just using the Gtk Toolkit for windowing that's bullshit, there's a mess of Glib and GObject code in Lightworks also.
    You saw the code? =O I'd like to see it actually, can you link me?

    Leave a comment:


  • zester
    replied
    Originally posted by Ancurio View Post
    Just saying, using Qt wouldn't change anything user visible at all.
    Sure it would, if you wanted to write a plugin for Lightworks that could talk to Nuke or vise versa. Or any other professional VFX tool without wanting to tear your face off
    because they all use Qt C++ and Python for there SDK's.

    And there not just using the Gtk Toolkit for windowing that's bullshit, there's a mess of Glib and GObject code in Lightworks also.

    Leave a comment:


  • Ancurio
    replied
    Originally posted by zester View Post
    I understand that, but that's beside the point. There is no extra work that has to be done on there part in order to fall inline with every other application that is used
    in professional studios, there making false clams in regards to them being a professional NLE, and there not even close to standard compliance.
    Just saying, using Qt wouldn't change anything user visible at all.

    Leave a comment:


  • zester
    replied
    Originally posted by Ancurio View Post
    GTK is just their "Windowing level" layer, all they use it for is to create windows and receive input events.
    The widgets and UI are entirely custom made.
    I understand that, but that's beside the point. There is no extra work that has to be done on there part in order to fall inline with every other application that is used
    in professional studios, there making false clams in regards to them being a professional NLE, and there not even close to standard compliance.

    AFAIK Lightworks doesn't support (OpenEXR, OpenFX, OpenColorIO, ...) without these Lightworks is going to be completely useless and be in the same position as
    Gimp, Kdenlive etc.

    With out OpenColorIO your going to edit in Lightworks and then send it down the pipeline and have to redo any color correction you may have made pre or post edit. Hence
    why the above three are not only OSS but BSD/MIT, ... licensed because there mandatory!!!!, Adobe, Autodesk, The Foundry, .... Photoshop uses OpenColorIO and so Does Blender etc. They all do.

    Leave a comment:


  • Ancurio
    replied
    Originally posted by zester View Post
    They also choose to go with Gtk instead of Qt? That doesn't make any since at all Qt and Python are they standard in anything VFX related. Even the Color Correction Software(DaVinci Resolve) and blackmagicdesign SDK's are all Qt. Nuke and NukeX, Maya, Mudbox, Motion Builder, Mari, Katana, Realflow, Houdini, Maxwell Studio, .... Are all Qt with Qt SDK's.
    GTK is just their "Windowing level" layer, all they use it for is to create windows and receive input events.
    The widgets and UI are entirely custom made.

    Leave a comment:


  • zester
    replied
    Lightworks made the clam that they were the first pro NLE video editor for linux, but thats not true at all, None of there ports of Lightworks come any where close to having the same feature set as oss offerings, for god sakes Kdenlive has 200+ Effects, and supports just about every video codec know to man. Lightworks is even crippling the oss code there using for video encoding and decoding and then offering that functionality as a feature in the pro version. Thats just dirty.

    They also choose to go with Gtk instead of Qt? That doesn't make any since at all Qt and Python are they standard in anything VFX related. Even the Color Correction Software(DaVinci Resolve) and blackmagicdesign SDK's are all Qt. Nuke and NukeX, Maya, Mudbox, Motion Builder, Mari, Katana, Realflow, Houdini, Maxwell Studio, .... Are all Qt with Qt SDK's.

    Leave a comment:


  • brosis
    replied
    One of many advantages of Openshot and other opensource editors:

    Leave a comment:


  • ninez
    replied
    Originally posted by CFWhitman View Post
    It may be that they aren't planning on just using open source for publicity. However, so far, that is all they have done. A product road map doesn't mean much until you carry through on it. They aren't under any real obligation to release the source, or for any source release to be truly meaningful. Don't get me wrong; I'm still taking a wait and see attitude, but my past experience warrants a bit of skepticism on my part. I'm not going to cheer for them until they make good.
    well, in fairness - there on working on item 3 right now - the others have been completed. So clearly, so far - they are following their roadmap

    They also had no obligation to even consider open sourcing any code, in the first place ~ but that seems to be something that they actually want to do and seem to be working towards that goal.... Skepticism seems more than reasonable (on your part), but personally, i think they will end up releasing an OSS version, since there isn't any indication that they won't. I'm sure they make more money on the software/hardware combo and/or specialized services than they do from just the app itself...

    even if this app stays purely proprietary with no goals of opening up any code at all (which i don't think is likely) - i still think bringing Lightworks to Linux is good though, just as Autodesk bringing their titles to linux is a good thing. But the one key difference between EditShare and someone like Autodesk - Lightworks is reasonably priced (pro version) and accessible in comparison to some other pro-video editors... So far, the editshare guys seem reasonable to me.

    Leave a comment:

Working...
X