← Back to team overview

openshot.developers team mailing list archive

Re: Next Version of OpenShot (1.4)

 

Here is my Thursday update.  I have tested my way up through 509.  Here are
my commits:

   - Updating all translations (i.e. MO and PO files) for all languages.
   - Update the translations POT template file
   - *BUG FIX:* Removed "Bit Rate" from the "File Properties" screen, since
   it was actually displaying FPS.  And then, I realized, the FPS was simply
   the current profile's FPS, and not the actual file's FPS.  So, I just
   removed the line and cleaned up the File Properties screen a bit.
   - *BUG FIX:* Fixed a regression with rev 505, which caused relative file
   path arguments to be added twice, due to the "queue" and "lock" file not
   checking for the ABS path.
   - *BUG FIX:* Fixed a translation bug on the "Convert to Image Sequence"
   feature.
   - *BUG FIX:* Fixed regression with rev 504, which caused the "Convert to
   Image Sequence" to stop working.  Also fixed a related issue where the
   "please wait" cursor does not appear, due to the GUI being starved by the
   conversion process.  This feature now works from the Detail View, Thumbnail
   View, and from the Clip Right Click.
   - *BUG FIX:* Fixed a few missing translations on the "Titles" screen.

I got stuck on *revision 509*, which has broken the "Edit Simple" for SVG
files... or at least many of the SVG files I tested it with.  It has
something to do with the initializing of the color pickers.  So, I'm calling
it a night.  If anyone wants to try and fix rev 509, please be my guest. =)

Thanks!
-Jonathan


On Thu, Sep 1, 2011 at 1:44 AM, Jonathan Thomas <jonathan.oomph@xxxxxxxxx>wrote:

> Okay, here are the updates for today.  I have tested my way up to revision
> 501, and found a few issues and fixed them.  Here are the commit notes:
>
>    - Updating the translation *POT template* again, due to new strings.
>    - *NEW FEATURE:* This is really cool! Added a new feature to move the
>    timeline / canvas when the middle mouse button is pressed and dragged,
>    similiar to other graphic programs. (lp:838600)
>    - *BUG FIX:* I found a very serious bug, which I would like to say is a
>    regression, but I can't figure out when it broke...  However, this was
>    preventing the "Clip Properties" video preview from applying effects
>    correctly.  The effects were being placed on the timeline at the clips
>    actual "position", and not starting at frame 0, which is what the preview
>    needs.  So, in other words, If an effect was starting on frame 100, the clip
>    preview would not show any effects until frame 100.  Fixed!
>    - *ENHANCEMENT:* Adjusted the text that was added in revision 491,
>    regarding the "There is already a project named...".  Removed the word
>    "export".
>    - *NEW FEATURE**:* Fixed the "Create Folder" screen to handle the
>    "return/enter" key, and save the folder.  Before, the user had to click the
>    "OK" button.
>    - *ENHANCEMENT: *Since we can't silence the MLT stdout list of formats,
>    codecs, and filters, I figured we could put some text in front of it, to
>    explain what's happening during the launch of OpenShot.
>    - *BUG FIX:* Fixed 2 different regressions on the "Import Transitions"
>    screen and "User Transitions" IconView code.  The new icon_size preference
>    broke a few things, but now it all works again. =)
>    - *BUG FIX:*  ANDY fixed a regression with the animated titles not
>    being added to the project tree, bug #837888.
>
> Only 23 commits left to test, so hopefully I'll be done tomorrow (or the
> next).  This release is looking great so far, so a big "Thanks!" to everyone
> who has helped and submitted patches.
>
> Thanks!
> -Jonathan
>
>
> On Wed, Aug 31, 2011 at 11:10 AM, eolinwen@xxxxxxxxx <eolinwen@xxxxxxxxx>wrote:
>
>> Greetings everyone,
>>
>> Like you have seen with the comments of Jonathan and Andy, a lot of things
>> have done on this milestone. Same if all is not finished, we have began some
>> tests on this one. But we have yet some features to work. And we need some
>> time.
>> So, it will be helpful for us if the others members of the Team could do a
>> lot of tests on the development branch but not only this one.
>> Some others branchs need too some tests.
>>
>> The Mael branch is on the port of GTK3 and you can have this one here :
>> lp:~moimael/openshot/gtk3
>>
>> On my own branch in another domain needs to have some tests mainly on the
>> new titles 2D :
>> lp:~eolinwen/openshot/OlivierThor-1.4
>>
>> Thanks a lot for all your feedback.
>>
>> Cheers
>>
>> Olivier
>>
>>
>> 2011/8/31 Jonathan Thomas <jonathan.oomph@xxxxxxxxx>
>>
>>> Andy,
>>> I just finished reviewing and testing the *21* commits on your initial
>>> 1.4 branch merge.  I'm going to go through every change over the next day or
>>> two to help test everything.  Most commits look great.  I did find a few
>>> regressions and bugs so far... and fixed them.  Details below... more emails
>>> to follow. =)
>>>
>>>    - *Rev 485.1.3* (bug #520941) - I don't *think* this will fix the
>>>    problem.  It's related to an incorrect FFmpeg length estimate, and the fact
>>>    transitions are "absolute" frame numbers, and clips are "relative" frame
>>>    numbers that just keep stacking on top of each other.  If a clip is actually
>>>    shorter than the estimate, MLT just starts the next clip earlier, and thus
>>>    our transition is now wrong.  So, there is really not much that can be fixed
>>>    in OpenShot to prevent this.  This change might fix one scenario, but break
>>>    others.  Not sure, we just need to test this alot.
>>>    - *485.1.7 FIXED* - My only comment is that I think the "icon size"
>>>    should be the same on the transitions and effects tabs.  Added a new option
>>>    to the preferences: Icon Size: small or medium?
>>>    - *485.1.11 FIXED* - Regression. The change stopped all other
>>>    languages from filtering the list correctly.  This code already supports all
>>>    languages.
>>>    - *485.1.12 FIXED* - Regression. The change stopped all other
>>>    languages from filtering the list correctly.  This code already supports all
>>>    languages.
>>>    - *Updated POT* template file, so all translations should now be in
>>>    LaunchPad.
>>>
>>> Everything else looked good and worked good during my testing.  I've made
>>> my way to Rev 487 tonight.  Only 37 commits to go.  I'll continue tomorrow.
>>>  Be sure to "bzr pull" before you work, especially now that I'm back into
>>> the code and working with you. =)  Thanks again for all the help!
>>>
>>> Thanks!
>>> -Jonathan
>>>
>>>
>>>
>>> On Tue, Aug 30, 2011 at 12:21 PM, Jonathan Thomas <
>>> jonathan.oomph@xxxxxxxxx> wrote:
>>>
>>>> Thanks for your help with this release!  You've really done all the hard
>>>> work this time, keeping up with all the patches, commits, etc...  So, thank
>>>> you so much.  Yes, I do have a few things I would like get done this
>>>> release, including a few new Blender animations I've been working on,
>>>> titles, and transitions.  I'll try and finish up those things this week.
>>>>
>>>> There are 4 branches which relate to translations:
>>>>
>>>>    - lp:openshot
>>>>       - The /language/Generate_POT.py file generates an updated POT
>>>>       with all strings from OpenShot.  When this file gets committed, LaunchPad
>>>>       will automatically find the new translations and update their website.
>>>>    - lp:~openshot.code/openshot/translations
>>>>       - This branch gets updated daily, with all translations.  Just PO
>>>>       files.
>>>>    - lp:openshot/openshot-docs
>>>>       - This branch holds the help manual, including instructions on
>>>>       how to generate a POT file for the help manual.  When the POT file is
>>>>       committed, it gets automatically processed by LaunchPad.
>>>>    - lp:~openshot.code/openshot/openshot-docs-translations
>>>>       - This branch gets updated daily, with all translations for the
>>>>       help manual.  Just PO files.
>>>>
>>>> The final steps of translations require a "compile.py" file to be run,
>>>> inside each of the "translation" branches.  This converts all the PO files,
>>>> into compiled MO files.  These MO files are then copied into our /locale/
>>>> folders, and the /doc/ folders, etc...  There are still a hand full of
>>>> undocumented steps, and I should probably created a "Deployment" document
>>>> which details all of these steps for us.
>>>>
>>>> I will go ahead and update the translations for both OpenShot and
>>>> OpenShot-Docs today, and assist with all these steps as needed... since I've
>>>> done them quite a few times. =)  But, in-case I get hit by a bus, at least
>>>> it's partially documented now.
>>>>
>>>> Thanks!
>>>> -Jonathan
>>>>
>>>>
>>>> On Tue, Aug 30, 2011 at 5:00 AM, Andy Finch <we.rocked.in79@xxxxxxxxx>wrote:
>>>>
>>>>> Hi Jonathan,
>>>>>
>>>>> I've been making good progress on 1.4, there are a couple more patches
>>>>> I need to look at and there were a couple more effects I was going to
>>>>> try out, but after that I'm more or less done on what I was going to
>>>>> do.
>>>>>
>>>>> Were you going to try and get to any of those items on your list?
>>>>>
>>>>> We also need to get the translation files updated as there are plenty
>>>>> of new strings - are you able to do this?
>>>>>
>>>>> Overall, it's looking good - there have been some good patches
>>>>> contributed that help make Openshot more usable and solid, with some
>>>>> good new things:
>>>>>
>>>>> New frei0r effects - flippo, equaliz0r, levels, colouradj_RGB,
>>>>> primary_colors, RGB Parade, letterbox (I'm going to look at a couple
>>>>> more). So there should be plenty of colour correction options now.
>>>>> New transitions - bubbles, clouds, clouds 2 (maybe more to come).
>>>>> Can now convert a clip on the timeline to an Image sequence.
>>>>> Can set the start time & length of a transition/mask exactly via the
>>>>> properties
>>>>> Can set the start time of a clip exactly via the clip properties
>>>>> Lots more validation in place to prevent such things as overwriting of
>>>>> project files, title files etc. In general, more user feedback.
>>>>>
>>>>> Plus loads of bugfixes.
>>>>>
>>>>> Anyway, let me know what you think.
>>>>>
>>>>> Cheers,
>>>>> Andy.
>>>>>
>>>>>
>>>>> On 8 June 2011 17:25, Jonathan Thomas <jonathan.oomph@xxxxxxxxx>
>>>>> wrote:
>>>>> > 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
>>
>
>

Follow ups

References