Openshot 1.4.3 Video Editor

[Pelo]

Installing openshot in only the first step. Untill now i just succeed in viewing one video, not editing anything. further help about editing is welcome. Tutos show Openshot working well, not to make it work well.

Trim the fat

[Pelo]

thin slacko 5.3.3 is the distro to run openshot
feedback 2016 rufwoof, england
and i agree.
Applications are like washing machines.
Once delivered and switched on, our puppy's agent consider their job is finished.
Openshot works well only with a few puppies.
(cinelerra never does its Job, Kdenlive only take mkv extension in count)
Avidemux is fine, but it's not the same function as openshot.

[Pelo]

Openshot 1.4.3 Video Editor included in tahrpup Puppybang. Click the blue, nothing to do. Just edit your videos.
Tahrpup 6.0.2
Fatdog 64 has openshot available in packages (Flowblade too) . Does it work.. I feed back soon.

[mikeslr]

Further discussion about Openshot under various Slackos: http://murga-linux.com/puppy/viewtopic. ... 777#971777

[mikeslr]

Hi All,

Following Mike Walsh's recipe here, http://murga-linux.com/puppy/viewtopic. ... 73#1005173 I used PaDS 1.1.4 to put together an SFS which appears to run fine under BionicPup64. Figure I'd save anyone interested in Openshot for BionicPup64 the trouble of duplicating the effort.

Credit should go to Mike Walsh for discovering that Ubuntu still supported 1.4.3 and what was necessary to get it functional under BionicPup64; and to ITSMERSH for creating PaDS which makes it easy to build applications requiring many source files.

The SFS and md5sum can be obtained here: http://www.mediafire.com/?13c9khbba4s0q

[Terry H]

Hi Mike, I've never used openshot, but have used flowblade a fair bit and am familiar with kdenlive, so thought I'd give this openshot.sfs a try. Unfortunately on this Bionicpup64 install, it won't run. I checked the md5sum following download, which was correct. Output when running in terminal:

Code: Select all

root# openshot
Added /usr/share/openshot to system path

------------------------- ERROR 1 ------------------------------
Failed to import 'from openshot import main'
Error Message: cannot import name main
----------------------------------------------------------------

------------------------- ERROR 2 ------------------------------
Failed to import 'from openshot.openshot import main'
Error Message: No module named gtk
----------------------------------------------------------------

OpenShot has failed to import some of the Python files or libraries 
required for our application to run.  Here are some trouble shooting
tips:

Tip 1) Check if MLT can be successfully imported in Python.  Run the 
 following commands, and see if any errors are displayed.  If you get 
 an error, you need to investigate the correct way to install MLT.
 NOTE:  Do not type the $ or >> characters in the examples below.

       $ python
       >> import mlt
       >> mlt.Factory().init()

Tip 2) If MLT is working from the first example, then the next tip is 
 to look at the above error messages very closely, and google for more 
 help.  It's likely the problem is already reported, and maybe there is
 a simple work-around.  Also, you can search for bugs or report a new 
 bug at https://bugs.launchpad.net/openshot.  Good luck!

[mikeslr]

Hi Terry H,

I was going to respond with a long explanation about the difficulties that can arise when an application uses python as a framework, with suggestions for a work-around. But I see that 666philb has just published an revised BionicPup64 in which "openshot 2.4.1 now installs from the PPM ... a bit hacky, it fires up sc0ttmans 'pkg' to grab the remaining deps"*.

I'm going to try that. But if you still want to use the 1.4.3 version, the most likely cause of the problem you experienced is that it's python conflicts with some other application's version of python. The only work-around I can think of is to convert the SFS into a pet and install the pet**. The downside of this work-around is that its version of python may overwrite the conflicting version breaking the application which depends on it.

** There's a Openshot 2.4.x AppImage, which doesn't run. I think rockedge posted a recipe for decompressing an AppImage. It might not have been rockedge and, in any event, I haven't been able to find the post. AppImages are supposed to be self-contained but they aren't built with Puppy in mind. To run in Puppies some additional libs may be required. The best solution would be to modify an AppImage and repackage it again as an AppImage. Then, being self-contained again, it could be used without conflicting with other applications.

* Short recipe: mount SFS, copy its files to a folder, dir2pet that folder, install the pet.

[Mike Walsh]

Hi Mike, I've never used openshot, but have used flowblade a fair bit and am familiar with kdenlive, so thought I'd give this openshot.sfs a try. Unfortunately on this Bionicpup64 install, it won't run. I checked the md5sum following download, which was correct. Output when running in terminal:

Code: Select all

root# openshot
Added /usr/share/openshot to system path

------------------------- ERROR 1 ------------------------------
Failed to import 'from openshot import main'
Error Message: cannot import name main
----------------------------------------------------------------

------------------------- ERROR 2 ------------------------------
Failed to import 'from openshot.openshot import main'
Error Message: No module named gtk
----------------------------------------------------------------

OpenShot has failed to import some of the Python files or libraries 
required for our application to run.  Here are some trouble shooting
tips:

Tip 1) Check if MLT can be successfully imported in Python.  Run the 
 following commands, and see if any errors are displayed.  If you get 
 an error, you need to investigate the correct way to install MLT.
 NOTE:  Do not type the $ or >> characters in the examples below.

       $ python
       >> import mlt
       >> mlt.Factory().init()

Tip 2) If MLT is working from the first example, then the next tip is 
 to look at the above error messages very closely, and google for more 
 help.  It's likely the problem is already reported, and maybe there is
 a simple work-around.  Also, you can search for bugs or report a new 
 bug at https://bugs.launchpad.net/openshot.  Good luck!

Hiya, Terry.

Sorry for the late reply; I've only just found this!

From the look of things, you'll need to install the 'pygtk' module from the Bionic repos. Make sure it's for Python 2, NOT Python 3.

It didn't come up for me when I was working out the dependencies, because I already had it installed as a dependency for RecordMyDesktop; again, Python-based.

Let me know if that 'fixes' it for you. If not, give us a terminal read-out, and we'll see what's what. That'll fix error 2.

-----------------------------------------------

As for error 1, I've found it's usually caused by the way .deb packages install in Ubuntu itself; slightly different to how it works in Puppy. There's a missing sym-link.

Go into /usr/lib/python2.7. You'll find two directories need investigating;'site-packages', and 'dist-packages'. See which one the 'openshot' directory's been installed to. A pound to a penny it's been put in 'dist-packages'.....but, for Openshot to work with Puppy, it needs to be in 'site-packages'.

If it's the first, but not the second, just sym-link 'openshot' (in 'dist-packages') across to 'site-packages'. Have a ROX window open on each, drag it across from 'dist-packages' to 'site-packages', drop it, and use 'Link(absolute)'.

That should fix it. Now try starting Openshot again from the terminal, and see what happens. If it's still playing up, give us some output, please.


Mike.

[josejp2424]

Here is an Openshot package for Slacko 14.2 complete with dependencies

https://sourceforge.net/projects/shivai ... ibaInu.sfs

MD5 : ce7c0291b5d97419695a9f4a35285ee2