On my system, I have xauth running, so my $DISPLAY is limited to access to the key. I haven't gotten this working with unix sockets in the lxc (I like to hear how to do that) but I commented out...
Type: Posts; User: paul.gevers; Keyword(s):
On my system, I have xauth running, so my $DISPLAY is limited to access to the key. I haven't gotten this working with unix sockets in the lxc (I like to hear how to do that) but I commented out...
You should be fine just deleting your ~/.winff/presets.xml file. The rest is up-to-date. Please see http://code.google.com/p/winff/issues/detail?id=131 for more details.
If it helps you, I maintain Winff in Debian an have a ppa available here: https://launchpad.net/~paul-climbing/+archive/ppa/+packages.
I found that on my system I needed to install lzma. Continuing from there succeeded. This should be considered a bug. I continue my investigation and will report it.
For me it worked to tell "startup disk creator" to first format the pen drive. Just writing the image failed to boot just like your description.
Please install libavcodec-extra-52 and you will have libx264 available in ffmpeg.
Please read /usr/share/winff/README.Debian. As I mention there and before in this thread, I removed the presets which include ffmpeg functionality which is NOT available in the ffmpeg in Ubuntu.
...
What do you mean by "are gone"? Since you reinstalled? I removed the presets that use libfaac because that is not included in Ubuntu Lucid anymore, but the complete presets are still available in...
No, it is not. It just means that the string is not correct. The correct string is (without any koala thingy, and without capital letters)
deb http://winff.org/ubuntu karmic universe
and it is...
ffmpeg error? Then you probably need to install libavcodec-unstripped-51 or libavcodec-unstripped-52 or libavcodec-extra-52 depending on which version of Ubuntu you are running.
Winff is a GUI for ffmpeg, so that is basically the same. Probably your problem is that the preset (at least for Winff) is specifying a lower quality than you want. The same goes for memcoder. So...
Could you please help me fix this problem. Winff should not crash. So, as a starter, what is the output if you start winff from a terminal? And crashes immediately, does that mean you don't see...
Do you have libavcodec-extra-52 or libavcodec-unstripped-52 installed?
I am not familiar with the info in the screenshots, but maybe it helps to get the info from ffmpeg. What does
ffmpeg -i <filename> give for a video that works? Try to get the same settings.
When...
I haven't inspected myself, but seeing this behavior it looks like this option has been removed. And if you have the libavcodec-extra-52 or libavcodec-unstripped-51 (depending if you are using Jaunty...
Test if the same happens with libavutil-extra-49... They are binary compatible.
[edit]: Nevermind you already have that installed, so this does not solve your problem. For your problem libavutil49...
I believe even upstream thinks so, see:bug 412063 comment 6.
If it is known that it is non-free and in main or universe, a bug should be filed and the stuff should be removed from the repository. What you most likely will find is that non-free stuff got in...
Could you tell us what you did and what you expected. Other than, follow the instuctions (which you already did), I can not say now. So, which letter did you follow, the command line OR synaptic...
Are you running Ubuntu Karmic? libfaac has not been build into ffmpeg in Ubuntu because it is deemed non-free.
It is a bug that the libfaac containing presets are still present in winff. I don't...
ffmpeg (winff is the gui for that) comes with it's own libraries. You need libavcodec-unstripped-51 or libavcodec-unstripped-52 or libavcodec-extra-52 (depending on which version of Ubuntu you are...
Install libavcodec-unstripped-52.
If indeed your winff presets are using mp3 as the codec you are using old an old preset file. If you started using winff a long time ago, you will have old presets in ~/.winff/presets.xml (which were...
Yes there is a way to reconfigure the sources.list, but the problem is NOT there. The error clearly says and . As both do exist this means a problem with apt and resolving:
paul@elbrus ~ $ host...
To the last answer, no.
It looks like your domain resolving is buggy at the moment. But apparently you are still connected to the internet? I would try (I know, M$ Windows solution) to restart...