For a couple of months now I've been working on a video to document my daughter growing up. It's a work in progress and when I have the time, I continue to work on the video.
When I needed to choose a video editor I wondered what I'd take. The video cutting software which came with the HD-Camera (Panasonic) was too simple and didn't even have some basic effects like fade. Back in the days when I was a Multimedia Producer for a couple of months I was using Avid, but that's way too expensive (and also too complex) for a simple home video. By chance I came across Wondershare Video Editor which could be installed for free to test. Besides the name, which honestly sounds anything but serious, I got hooked and was surprised by the interface, the possibilities of effects and yet it still featured the "expert" view to combine several multmedia layers in a video.
However when I recently updated to the latest Wondershare Filmora 6.6.0 version (in the meantime Wondershare Video Editor was renamed to Filmora), the application crashed. At first I thought this is due to the just updated version and I downgraded back to Wondershare Video Editor 5.1.1 - with the same result. The application crashed whenever I tried to go into the "Full Feature Mode" (even for a new project). Only the "Easy Mode" loaded fine.
I then started to keep track of the application log file, which was written in WondershareVideoEditorInstallFolder\log\log.txt.
The end of the log file contained a lot of such entries:
#2015-08-28 20:53:27# [MPDecSrc]: Mplayer Get ProgramInfo dMediaLength = 20.000000
#2015-08-28 20:53:27# [MPDecSrc]: Begin use Mediainfo
#2015-08-28 20:53:27# MPDecSrc Use Mediainfo timelen,pProgramInfo dMediaLength = 19.966000
#2015-08-28 20:53:27# MPDEC PrepareDecoder get mediainfo
#2015-08-28 20:53:30# [MPDecSrc]: Mplayer Get ProgramInfo dMediaLength = 4.000000
#2015-08-28 20:53:30# [MPDecSrc]: Begin use Mediainfo
#2015-08-28 20:53:30# MPDecSrc Use Mediainfo timelen,pProgramInfo dMediaLength = 4.022000
#2015-08-28 20:53:30# MPDEC PrepareDecoder get mediainfo
#2015-08-28 20:53:30# [MPDecSrc]: Mplayer Get ProgramInfo dMediaLength = 4.000000
#2015-08-28 20:53:30# [MPDecSrc]: Begin use Mediainfo
#2015-08-28 20:53:30# MPDecSrc Use Mediainfo timelen,pProgramInfo dMediaLength = 4.022000
#2015-08-28 20:53:30# MPDEC PrepareDecoder get mediainfo
#2015-08-28 20:53:30# [MPDecSrc]: Mplayer Get ProgramInfo dMediaLength = 4.000000
#2015-08-28 20:53:30# [MPDecSrc]: Begin use Mediainfo
#2015-08-28 20:53:30# MPDecSrc Use Mediainfo timelen,pProgramInfo dMediaLength = 4.048000
#2015-08-28 20:53:30# MPDEC PrepareDecoder get mediainfo
#2015-08-28 20:53:30# [MPDecSrc]: Mplayer Get ProgramInfo dMediaLength = 4.000000
#2015-08-28 20:53:30# [MPDecSrc]: Begin use Mediainfo
#2015-08-28 20:53:30# MPDecSrc Use Mediainfo timelen,pProgramInfo dMediaLength = 4.022000
#2015-08-28 20:53:30# MPDEC PrepareDecoder get mediainfo
#2015-08-28 20:53:30# [MPDecSrc]: Mplayer Get ProgramInfo dMediaLength = 4.040000
#2015-08-28 20:53:30# [MPDecSrc]: Begin use Mediainfo
#2015-08-28 20:53:30# MPDecSrc Use Mediainfo timelen,pProgramInfo dMediaLength = 4.066000
#2015-08-28 20:53:30# MPDEC PrepareDecoder get mediainfo
#2015-08-28 20:53:30# [MPDecSrc]: Mplayer Get ProgramInfo dMediaLength = 5.280000
#2015-08-28 20:53:30# [MPDecSrc]: Begin use Mediainfo
#2015-08-28 20:53:30# MPDecSrc Use Mediainfo timelen,pProgramInfo dMediaLength = 5.300000
#2015-08-28 20:53:30# MPDEC PrepareDecoder get mediainfo
Which seems to indicate a problem of a decoder - but only the application developers know what exactly these log entries mean...
On my Windows 7 64bit, I currently have the following Codec Packs and Media Players installed:
- X Codec Pack 2.7.1
- Xvid v1.3.0 CVS
I decided to uninstall these completely, reboot and try again.
After the reboot, I tried to open my project which opened Wondershare Video Editor 5.1.1.
After loading for around 1.5mins, the loading window disappeared. In the log file I now saw that the program has sent
a crash report "back home" to the Wondershare API:
#2015-08-28 21:05:41# MPDecSrc Use Mediainfo timelen,pProgramInfo dMediaLength = 1.844000
#2015-08-28 21:05:41# MPDEC PrepareDecoder get mediainfo
#2015-08-28 21:05:45# >>>>>>>>>>>>>>>>>>>>>>WSLogInit>>>>>>>>>>>>>>>>>>>>>>>
#2015-08-28 21:05:45# FLogPath= D:\Program Files\Multimedia\Wondershare Video Editor\Video Editor\Log
#2015-08-28 21:05:45# gConfig= D:\Program Files\Multimedia\Wondershare Video Editor\Video Editor\VideoEditor.ini
#2015-08-28 21:05:45# FDownloadFileURL= http://api.wondershare.com/interface.php?m=smtpinfo
#2015-08-28 21:05:46# XMLPath=D:\Program Files\Multimedia\Wondershare Video Editor\Video Editor\SMTP-xml.txt
#2015-08-28 21:05:46# Fetch(XMLPath) finished!
#2015-08-28 21:05:48# SendEmailAPI.Login Success!
#2015-08-28 21:05:48# GetSubject= T#hidden@claudiokuenzler.com#846#client:Contact from product#No Reply, crash log auto collected for R&D
#2015-08-28 21:05:50# SendEmailAPI.Send Success!
Now I gave the K-Lite Codec Pack a shot and installed the current version 11.4.0, followed by a reboot.
But the same issue happened. So I uninstalled the Wondershare Video Editor again and installed the newer Wondershare Filmora 6.0.1.
Here at least I was able to start into the "Full Feature Mode", although it took about 2mins to load (for a new empty project).
When I tried to load my existing project, the program now finally started up and it seemed that it was able to load the project. But after around 2-3 seconds, Filmora crashed and a window (Error Report) appeared where I could send an error report.
Last hope: Started up Filmora again, opened a new project in Full Feature Mode. Then went on Help -> Check for Update and clicked on Update now to launch the update.
So - the update installed and I'm back to where I was at the begin with Filmora 6.6.0. A new project in Full Feature Mode could be opened. Will it load my existing project?
To my big surprise: YES! The project loaded again. And I was able to follow the logfile to see when Filmora stopped loading the video files used for the import of the video sequences.
However strange is that the update to 6.6.0 automatically installed itself into a completely different path than the original installation path.
Original path was D:\Program Files\Multimedia\Filmora.
New path after I launched the update from 6.0.1 to 6.6.0 was C:\Program Files (x86)\Wondershare\Filmora.
But that's most likely not the source of the problem. So far I am able to continue on my project again with Filmora 6.6.0 but it's very slow, probably because there are many huge source video files (Full HD) to read in every time, create thumbnails and previews from, which is probably too much for the program. To handle this, I have now decided to continue on a new project, put together the next few months in there (splitting the whole video into several projects) and at the end combine the projects (without having to do any cutting anymore) and make one final video.
ck from Switzerland wrote on Aug 26th, 2016:
Hi Jeanette. Once I finished the "three projects" (basically a year of family videos split in three projects), meaning I exported each project as its own MP4 video, I simply created a new "project" and added the three mp4 video files once after another. And then exported this final project as one complete video file.
Jeanette from Laveen Arizona wrote on Aug 25th, 2016:
Hi CK,
Thanks for your input. I have a lot of problems with this program. It has a lot of good features and I hope that they will make some good updates. But i also found a lot of bugs like you have. I would love to combine projects since I had difficulty with some of mine I would like to know how you have were able to do that.
ck from Switzerland wrote on Jun 15th, 2016:
Hi Alex. Well, Wondershare can give you certainly a better answer than me but from a neutral point of view make sure you run a multi core CPU (for example AMD Athlon/FX or Intel i5/i7) and you can also use your graphics card as GPU and add additional rendering resources to it. However Wondershare is only compatible to a few of these GPUs (see https://www.wondershare.com/topic/gpu-optimization.html).
Alex from USA wrote on Jun 15th, 2016:
why my filmora is soo slow whene rendring
AWS Android Ansible Apache Apple Atlassian BSD Backup Bash Bluecoat CMS Chef Cloud Coding Consul Containers CouchDB DB DNS Database Databases Docker ELK Elasticsearch Filebeat FreeBSD Galera Git GlusterFS Grafana Graphics HAProxy HTML Hacks Hardware Icinga Influx Internet Java KVM Kibana Kodi Kubernetes LVM LXC Linux Logstash Mac Macintosh Mail MariaDB Minio MongoDB Monitoring Multimedia MySQL NFS Nagios Network Nginx OSSEC OTRS Office PGSQL PHP Perl Personal PostgreSQL Postgres PowerDNS Proxmox Proxy Python Rancher Rant Redis Roundcube SSL Samba Seafile Security Shell SmartOS Solaris Surveillance Systemd TLS Tomcat Ubuntu Unix VMWare VMware Varnish Virtualization Windows Wireless Wordpress Wyse ZFS Zoneminder