> So, why don't merge the > better parts of these two softwares Let's put it this way: PiTiVi has about 26 thousand lines of Python code and OpenShot has over 10 thousand (Jonathan should correct me on that, I don't have the latest figures). The two codebases are very different. Do we have a volunteer? ;)
> (like using the GStreamer > non-lineare engine and UI of PiTiVi, core of OpenShot, etc) For the record: OpenShot used to use GStreamer + GNonLin in the beginning, and then switched to using ffmpeg + MLT later on. > But we can use code of UI from OpenShot. It exactly the same > technologies. The UI is not the most difficult part. The logic and backend and glue are the difficult part. > And for video effect, the library using in OpenShot (frei0r) have > GStreamer plugin: Yep, we already use that in pitivi git (along with other gstreamer effect plugins). ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Pitivi-pitivi mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi
