openshot.developers team mailing list archive

["eolinwen@xxxxxxxxx" <eolinwen@xxxxxxxxx>]

Hi,

>>That is a good set of ideas - there are also a number of bugs in Launchpad
with patches. These should be reviewed and applied as necessary.

Totally agree with Andy.

A openshot user have done two news effects on our forum (flippo and
Equalizor); See :
http://openshotusers.com/forum/viewtopic.php?f=18&t=928
http://openshotusers.com/forum/viewtopic.php?f=18&t=860

>>As goocanvas was the last thing wich prevent us to port openshot to
gtk3/gobject introspection/gsettings (generic way to store settings with
backend for KDE, gnome(dconf and gconf) and windows(the registry)), the
1.4 release can be a good start point.

Good thing. Pygtk3 is called PyObject.

>>Oh and for the timeline theme, i think we should use clutter
possibilities (beautiful animations, fading, ...) and have only one
theme instead of changing between multiple theme which means using image
and a lot more code.

The fact to use Clutter will play more on the Motor Theme Engine rather than
on the Theme himself. No ?

Anyway, Jonathan you should intend to include him in the Framework. Ths it
will be more responsive/fast/quick and will have less code. And it is a good
idea to start to work on Clutter for replace Goocanvas. Saying that will be
finish for the next "big" release.

>>I*mprove SWIG Python bindings to MLT*
- I have learned many things about SWIG in recent days, as well as the
ability to add generic Python try/catch around all MLT method calls.  It
works great with C++, but I've never tried it with C, so no promises this
will work.  But, best case, no more "segmentation faults" from MLT that kill
the Python interpretor.  Instead, generic Python errors would be raised, and
we could handle them in some better way.

C++ is an evolution of C which brings some ++ .......Can we do something at
this level ? Is it not linked to MLT directly ?

(@Mael : et ces examens ? tu en es où ?)

Cheers.


2011/6/8 Maël Lavault <moimael@xxxxxxx>

> Oh and for the timeline theme, i think we should use clutter
> possibilities (beautiful animations, fading, ...) and have only one
> theme instead of changing between multiple theme which means using image
> and a lot more code.
>
> Le mercredi 08 juin 2011 à 11:25 -0500, Jonathan Thomas a écrit :
> > Greetings everyone!  I have a few ideas I wanted to bounce off
> > everyone.  Since the C++ library is taking longer than anticipated
> > (because of cross-platform slow down... mainly issues with Windows and
> > how much it sucks), I thought maybe we should knock out another MLT
> > powered release, and let's call this verison 1.4.
> >
> >
> > Here were a few things we could focus on:
> >
> >
> > Replace Goocanvas with Mutter (or another canvas)
> > - Goocanvas is giving us all sorts of trouble with performance (when
> > zoomed in) and not displaying the entire timeline, due to issues with
> > maximum width.  This is a MAJOR change, and will likely take a lot of
> > time to get right, but it could make a HUGE difference to the
> > performance and speed of OpenShot's timeline.
> >
> >
> > Relative File Paths
> > - This has been a long standing issue, and one that is easily fixed.
> >  The .OSP file only needs the relative path to the media, and at
> > run-time we locate the actual file path and use it.  This would make
> > moving projects easily, as well as sharing your project easier.  Easy
> > and low risk.
> >
> >
> > Improve SWIG Python bindings to MLT
> > - I have learned many things about SWIG in recent days, as well as the
> > ability to add generic Python try/catch around all MLT method calls.
> >  It works great with C++, but I've never tried it with C, so no
> > promises this will work.  But, best case, no more "segmentation
> > faults" from MLT that kill the Python interpretor.  Instead, generic
> > Python errors would be raised, and we could handle them in some better
> > way.
> >
> >
> > Improve ICON and THEME
> > - As much as I like the new timeline theme, I think we can improve it
> > a bit more.  This might go hand in hand with Mutter (or similar
> > canvas), but I want the clip representations to look as slick as
> > possible, spacing, play-head, etc... to all as good as possible.  Just
> > saying there are bound to be some small and significant changes we can
> > make to improve the look and feel.
> >
> >
> > Transitions and Effects and Titles
> > - We have many effects that are not being tapped into, including many
> > Frie0r effects, additional audio effects, color correcting effects,
> > etc...  We can also create a lot more transitions, or use the
> > community to generate many new transitions and title SVGs.  These are
> > low risk additions to any release, and add some fun for users.
> >
> >
> > In summary, the new C++ video editing library is coming along great,
> > but more slowly than I hoped.  So, a new release of OpenShot would
> > keep the momentum moving in our direction, and hopefully please our
> > users, fans, and critics. =)  What does everyone think about this
> > idea?
> >
> >
> > Thanks!
> > -Jonathan
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openshot.developers
> > Post to     : openshot.developers@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openshot.developers
> > More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openshot.developers
> Post to     : openshot.developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openshot.developers
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Olivier
Cenwen un elfe sur la banquise/ an elve on the ice
Mon blog perso  sur le multimédia, Ubuntu, Linux et OpenShot :
http://linuxevolution.wordpress.com/
Le forum d'Openshot où vous me trouverez : http://openshotusers.com/
http://openshotusers.com/forum/index.php