Stuff you can't really do in Windows. Sort of but not really.
- Log in to post comments
More like this
...and I don't really have time today. Seriously, you've got to read the whinings of this idiot, and MTMB's response.
Maybe because my family of six pulls in less than 50K a year (as opposed to the 450K the gent in question is whinging about), and because I can identify still with the realities of…
Because Apple posted an advisory [a while back now] suggesting that an antivirus program be used, the Windows bigots have erected a strawman: Apple says it is immune from viruses, so now it looks like Macs aren't so great huh?
Of course, that's not what is happening at all. I have used a virus…
The other day, I wrote that I wanted to make things easier for my students by using the kinds of software that they were likely to have on their computers and the kinds that they are likely to see in the business and biotech world when they graduate from college.
More than one person told me that I…
It should not really matter how long it takes to boot your OS. Why? Because a good OS will start up once after a major system upgrade, then stay on forever after unless there is a power failure. If you want to shut down the computer you can hibernate the state to keep all your apps 'running' and…
Got that - and more - on the Mac. And with a very good GUI to go with it. You can actually see all of your choices and the results before committing to an encoding job. No command line to have to deal with - a biggie for me.
If you want a gui for ffmpeg look up winff. The linux version is pretty ugly (uses gtk1 widgets, although you can compile it to use gtk2), but the windows version is pretty good. It has presets for pretty much anything you can think of.
I still prefer the command line version myself, nothing beats ffmpeg is you want to copy the audio track from a video without converting it.
The command line isn't that fearsome, and once you've figured it out, you don't have to worry about it anymore. I convert plenty of stuff for my Treo phone, and once I figure out a good way to do it, I just wrap it in a script and forget about it. I've got scripts like "dvdtopalm", "flvtopalm", "flvtoavi", "mp3fromflv", etc.
For my birthday, I just got an HD camcorder, and now I'll have to see about converting high-bitrate AVC files...
I'm confused. What exactly in there are you not supposed to be able to do in windows?
Bye the bye, lest people think that the command line is the only way to convert things on Linux, see here.