Hey guys, I didn't notice this thread yet. peacejet, I hope you don't mind me replying to somewhat off-topic posts - it seems this thread has some
kind of prosocial quality in which I would like to partake ;] of course your problem first;
reply to post by peacejet
The problem of the screen turning off has happened to me as well - in my case it was caused by ATI's own driver (which is quite good, but not always
as stable as your distro's own implementation of the open-source version for ATI videocards). The important thing is, you don't have to mind the
extra boot option; if you choose to reinstall Ubuntu, it will recognize the option and either delete or reuse it. Either way, no problems there.
Alternatively you could boot into Ubuntu with a previous working kernel or video driver and fix the problem, but that may take more time (to explain
;D) than just reinstalling. If you do want to go the long way, let me know!
reply to post by semperfortis
Originally posted by semperfortis
reply to post by Ian McLean
Can you, if you have the time, explain the process from start to finish.. I mean start me at my desktop and go from there?
Sorry to be a pain, but I get confused with a lot of the editing required in Linux and don't really understand where to go to put the text in..
Maybe it's not my place to jump in answer this question, but I'm just itching to!
*warning* Long answer *warning*.. skip through the first 3 paragraphs to get to a real answer
It's not strange to get confused by all the command-line activities - while most people only recognize this from the old DOS-days, the Linux
developers sometimes even prefer to be working in a console (the screen where you execute commands through text, also referred to as terminal
When how-to's and other documentation are written, the author often assumes the reader to have somewhat the same affiliation with the console. In the
end, this makes it hard for real newbies to get comfortable with the Linux way of life.
Ubuntu has made some terrific progress in that respect. A few years ago, it was virtually the ony distribution with a graphical install - one of the
most important thresholds for really new users. Since then, it has come a long way, and most of the daily activities on Ubuntu can be completely
managed through the GUI, much as in more popular operating systems.
But then there's the stuff Ian McLean posted. Mencoder is a gem of encoding software, and there is little you can't do with it - but as another
Ubuntu user says in his thread;
I'm not afraid of the command line by any means, but MEncoder is one of those programs that has so many options and switches that its nearly
impossible to keep track of them all. Just doing a moderately complex operation is a paragraph's worth of text.
Of all the command-line invocations I've seen, mencoder definitely has the longest by average. If there ever was a program that was in dire need of a
decent front-end (clickable stuff), then it's mencoder. The thread mentioned above does contain some posts referring to KMPlayer for example as a
possible front-end for mencoder.. But now that we've come this far, it would be a shame not to go the extra inch for some authentic console
So let's get back to that horrendously long command supplied by Ian McLean:
$ mencoder -of mpeg -oac lavc -ovc lavc -mpegopts format=dvd -ofps 30000/1001 -srate 48000 -af lavcresample=48000 -vf
-o outputfile.mpg inputfile.avi
I'll try to break down the syntax in a comprehensible manner. The first important thing is that all commands are an alphanumerical word. For example,
7zip is a program, and mencoder is in this example; but the dollar sign in front of that is not part of the command. It's meaning depends on the
source, but in this case it just represents 'being in a terminal' - you can safely ignore it completely.
Next, while it is possible to execute multiple commands (through the use of special characters like |, & and
, you can safely assume for now that
all the text behind a command gets sent to that command. So, the whole 'paragraphs worth of text' after 'mencoder' gets sent to the command
mencoder. While a program can do pretty much whatever it likes with the input you give it, most follow a certain format:
command -option1 valueforoption1 -option2 valueforoption2 -valuelessoption3 file file2/dir/etc..
All options are prefixed with a hyphen (-); some options have values, some don't. Sometimes options are complete words, sometimes two hyphens are
When referring to a file, the command tries to find the file from 'your' point of view. By default, a console opens in your home directory (e.g.
/home/banana). Say I've downloaded a file to the directory Downloads, then it would be found under /home/banana/Downloads. Now if I were to use
mencoder on the downloaded file, I would open the terminal/console via the menu (see System apps or similar); since the terminal already opens in
/home/banana, I can simply type "cd Downloads" to go into the Downloads dir. But, I can also supply mencoder with the path to the file instead of
going there myself;
mencoder -of mpeg -oac lavc -ovc lavc -mpegopts format=dvd -ofps 30000/1001 -srate 48000 -af lavcresample=48000 -vf
-o outputfile.mpg Downloads/inputfile.avi
The file 'outputfile.mpg' will get created if all is well. You can replace that name with anything you want - you could for example write the file
to /tmp, the temporary working directory (content deleted each reboot!), simply by supplying -o /tmp/outputfile.mpg
Hope that sheds some lights, out of characters now - good luck! May the OpenSource be with you.