LiVES Activity
LiVES is a Video Editing System. It is designed to be simple to use, y
Brought to you by:
gfinch
Activity for LiVES
-
Salsaman posted a comment on discussion newbie issues
Nameer is quite, and thanks for responding in my abscence, I apologise for the delay in answering. I'm curently taking a small break from LiVES and I'm developing a next gen AI narration framework. LiVES 4.0 is about 80% done, but I needed a break fro the heavy tech development On Fri, 30 May 2025 at 17:35, Nameer Shah nimmi1231@users.sourceforge.net wrote: LiVES software isn’t designed for automatic face swapping in video. For your use case, tools like DeepFaceLab, FaceSwap, or Runway ML are better...
-
Nameer Shah posted a comment on discussion newbie issues
LiVES software isn’t designed for automatic face swapping in video. For your use case, tools like DeepFaceLab, FaceSwap, or Runway ML are better suited, as they use AI to replace faces across frames automatically. These tools require some setup and training, but once done, they can apply the face swap throughout the video without manual frame-by-frame editing.
-
Alan Corey modified a comment on discussion compiling/installing
I'm working on posting full output to pastebin. The configure output is at https://pastebin.com/8xuQeUUg The compiler output is at https://pastebin.com/tc4LB5uD but that may have a private tag because it tripped something in their spam detector, so I emailed them, it may be fixed already. I'm building on a 64 bit ARM machine, a chromebook actually, which may be a little unusual.
-
I'm working on posting full output to pastebin. The configure output is at https://pastebin.com/8xuQeUUg The conpiler output is at https://pastebin.com/tc4LB5uD but that may have a private tag because it tripped something in their spam detector, so I emailed them, it may be fixed already. I'm building on a 64 bit ARM machine, a chromebook actually, which may be a little unusual.
-
May be related to https://github.com/PyAV-Org/PyAV/issues/735 but I suspect it's a simpler missing header. The depends lists could be better. I made up little Bash scripts (from the Lives README) to do the installs, I'm not seeing the main one right now, just a little one for the git version to use after the main ones. It looks like: apt-get install autogen automake autopoint libtool gettext. I was FTPing them around, they're probably somewhere. OK, they're quite simple but they make it easier to...
-
OK, I didn't imagine it. Crouton is the replaceable chroot system on Chromebooks. I was seeing this problem so I wiped my chroot and started over with a clean install of ffmpeg, that worked fine. Then for Lives I installed from git first and ended up with weed library errors. Tried to build in a new dir from a tarball instead and it looks like a missing header again. In file included from libav_stream.c:33: ../../decoders/libav_helper.h: In function ‘av_set_pts_info’: ../../decoders/libav_helper.h:91:3:...
-
Reloading the Linux, that should cure it. Nothing significant has been done under this crippled Linux. I'm not a Chromebook fan but my Pinebook Pro had a hinge failure that left me stranded needing to replace it.
-
I had Lives installed from Debian debs (Bullseye), and when it turned out to not be entirely suitable I removed bits of it however I could and built from sources. I'm fairly sure I didn't get it all out, I hoped it wouldn't matter. Before starting to build lives from sources I uninstalled an ffmpeg which was also from debs and replaced it with one built from sources. This is under Linux on an Acer Chromebook. I see 2 possible cures. In Debian/Ubuntu there's a file /var/log/apt/history.log which contains...
-
I had Lives installed from Debian debs (Bullseye), and when it turned out to not be entirely suitable I removed bits of it however I could and built from sources. I'm fairly sure I didn't get it all out, I hoped it wouldn't matter. Before starting to build lives from sources I uninstalled an ffmpeg which was also from debs and replaced it with one built from sources. This is under Linux on an Acer Chromebook. I see 2 possible cures. In Debian/Ubuntu there's a file /var/log/apt/history.log which contains...
-
I'm trying to build current lives after having just built and installed ffmpeg. I get implicit declarations on several functions, at least one of which was deprecated and removed from ffmpeg a while ago. I'm probably not linking something I need to. Maybe I have an old binary somewhere? make[4]: Entering directory '/usr/src/misc/lives/lives-3.2.0/lives-plugins/plugins/playback/video' /bin/bash ../../../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"LiVES\" -DPACKAGE_TARNAME=\"lives\" -DPACKAGE_VERSION=\"3.2.0\"...
-
ovizii posted a comment on ticket #232
thanks for pointing me in the right direction.
-
H, the current bugtracker can be found at https://github.com/salsaman/LiVES/issues You are welcome to repost there.
-
it looks like the screenshot disappeared. :-( The text was along the lines of "lives cannot write to and make sure you have write access to (null) If anyone is interested to help I can share my Dockerfile as well as my docker-compose.yml
-
Trying to run lives within a docker container
-
LiVES released /lives/3.2.0/ChangeLog
-
-
-
-
-
David posted a comment on discussion development
First of all thank you guys so much for a video editor which can be run on more modest hardware. I beat my brains out trying to find a program that would do what I need yet not need weeks to create a finished product on my quite modest 11yr old hardware. Other than that the subject pretty much says it all. Is there any chance the option to pass off most of the encoding to the video card could be implemented in the not too distant future? I run Plex Media Center on this pc, and I can transcode video...
-
Hi Guenter, I'm not sure if you are still monitoring this, but the current git version of LiVES has even more extensive safeguards to try to ensure nothing like this ever happens again. If you recall, the root of the problem was that your config file was damaged, leading to the program unfortunately falling back to its default working directory, without prompting for it to be set. Here is a summary of the safeguards in the upcoming release. Firstly, on startup, the program will check for an existing...
-
GGBce created ticket #231
LiVES 2.8.3 on Debian 9
-
Teppo Saari created ticket #230
Crashes on OpenBSD 6.4
-
LiVES 3.0.2 released
-
-
-
-
-
Rich Howell posted a comment on ticket #229
In software manager it shows Lives 3.1 but installs 2.8.7 . Get the same result with sudo add-apt-repository ppa:ubuntuhandbook1/lives sudo apt update sudo apt install lives lives-plugins So how do i install 3.0.1 ?
-
HI this version is no longer supported, please update tothe latest version 3. 0. 1
-
White text
-
LiVES 3.0.1 released
-
-
-
-
-
-
LiVES 3.0.0 released
-
-
-
-
-
-
OK, just to update you I have been working on this all day. It proved to be a little more tricky than I imagined, since LiVES performs a lot of checks on startup. With the new failure mode it was detecting the (simulated since I was testing) config file error much earlier, then trying to show a warning. The problem being that in order to show the warning dialog it was first trying to create the GUI, and in order to create the GUI it needed to read in a lot of preferences, thus creating a kind of...
-
OK, just to update you I have been working on this all day. It proved to be a little more tricky than I imagined, since LiVES performs a lot of checks on startup. With the new failure mode it was detecting the (simulated since I was testing) config file error much earlier, then trying to show a warning. The problem being that in order to show the warning dialog it was first trying to create the GUI, and in order to create the GUI it needed to read in a lot of preferences, thus creating a kind of...
-
All changes done: https://github.com/salsaman/LiVES/commit/a68ad304392102a1b383d24a0a75d5e078d47b28 https://github.com/salsaman/LiVES/commit/22ded0e9e8f8dcd976cd6ea2137062f5cf07ee35
-
OK, just to update you I have been working on this all day. It proved to be a little more tricky than I imagined, since LiVES performs a lot of checks on startup. With the new failure mode it was detecting the simulated config file error much earlier, then trying to show a warning. The problem being that in order to show the warning dialog it was first trying to create the GUI, and in order to create the GUI it needed to read in a lot of preferences, thus creating a kind of chicken and egg situation....
-
BTW, for recovering lost files I can personally recommend ddrescue: https://www.gnu.org/software/ddrescue/ it has worked very well for me in the past after a hard disk crash. It will link any orphaned inodes into /lost+found. -the filenames will be missing, but you can list the fragments is order of descending size and try to play them through mplayer. or vlc or another player. If you find a missing clip then you can rename it and move it back to its old location.
-
BTW, for recovering lost files I can personally recommend ddrescue: https://www.gnu.org/software/ddrescue/ it has worked very well for me in the past after a hard disk crash. It will link any orphaned inodes into /loast+found. -the filenames will be missing, but you can list the fragments is order of descending size and try to play them through mplayer. or vlc or another player. If you find a missing clip then you can rename it and move it back to its old location.
-
Guenter Grau posted a comment on ticket #228
I don't remember that I've seen such a warning. The initial one I might have missed because I might have started lives at <2.5G. My expectation of where the tmpdir should be (/local/livestmp or /tmp/livestmp) versus where it has been (~/livestmp) was different - a matter of permanent over-utilization of these tiny 2.5" disks...I languish for a 16TB drive ;-) What happened next is that I tried to find options to change brightness/contrast/denoise and apparently I started a conversion by accident (was...
-
Further investigation has revealed a couple of interesting things. Currently we return an error code if either the temp settings file cannot be opened or if the rename operation fails. This check was inadvertantly omitted when setting a colour type preference, so this needs to be added (colour prefs were added pretty recently). On receipt of the error code, the front end will show a warning, however I am going to change this to a retry / abort dialog. The same code will now also be triggered if the...
-
Again my apologies for the dataloss, and thankyou for helping focus my attention on this serious issue.
-
There is another possibility which I had not considered, which is that the new (temp) file may be truncated. Thje actual file writing is done by a background perl process, so it would seem wise to check for errors during the write process. As a further check one could also calculate the size of the new file and then check that this matches what is in the file system and abort if the two values do not match.
-
Thanks, all good suggestions, I will look into implementing them right away. Regarding your suggestion of creating a new file then renaming it, that is already how LiVES operates. So it appears that in your case the diskspace must have run out during the rename operation, which is indeed very unfortunate. I guess a better soultion might be - create the new file, -copy rather than rename, -make sure the file sizes match (old and new), if the sizes match, delete the temp version, otherwise delete the...
-
Thanks for the quick feedback! Unfortunately I'm still a bit busy to sort out >100k files ;) I should mention that ext4magic is a great tool to recover files which you would normally consider lost. I think your suggestion does provide enough safety, because there are several dangerous points. If a user really wants to trash his homedir with temporary files, he should actively set it and get a warning. A safe default would be ~/livestmp and in case it's missing upon first access the program can simply...
-
Hello Guenter ! First of all my sincere apologies for the dataloss. Under normal circumstances this should never happen. However, your analysis was correct. It seems likely that your ~/.lives file was damaged and the <tempdir> (which is actually the LiVES woirking directory - however the name is set like that for historical reasons) setting was not saved correctly (most probably due to the disk being full). </tempdir> In normal circumstances what would happen is, the tempdir setting should only be...
-
I just inspected the ~/.lives file. I have been running into some crashes and a "disk full" on a prior version, and I believe that I have seen this file to be quite small (but not empty). Right now it is much bigger and actually contains the answer, the file is attached. The tempfir section points to my homedir instead of the livestmp link inside :-S I don't know if the case of disk full could leave behind a damaged .lives file which has been "recovered" with defaults? In any case, the tmpdir should...
-
Clean up Diskspace amok run in 2.10.2
-
LiVES 2.10.2 released
-
-
-
-
-
-
Faiz Qureshi posted a comment on discussion newbie issues
Hi there, I am trying to use the Live software to edit a video and replace or swap a face with another face. Instead of doing this frame by frame I would like to do it once. Is this possible ? Or is there a better way to do this If yes can you please explain how can I do this ? Thanks IQ
-
updates
-
experimental mingw branch
-
fix bugette in widget-helper
-
mingw
-
mingw
-
mingw
-
mingw updates, format code
-
mingw updates
-
mingw updates
-
fix typos
-
mingw updates
-
fix typo
-
fix typo
-
fix typo
-
fix typo
-
mingw updates
-
mingw changes
-
mingw changes
-
mingw changes
-
mingw
-
mingw
-
av sync fixes
-
pango fixes, add some missing frees
-
small fix
-
improve rt recording
-
various updates
-
allow retry when clip not found
-
whitespace cleanup
-
updates
-
various
-
various
-
mingw updates
-
update po
-
update
1 >
