Guys please suggest me a good video converter software for openSUSE to covert videos into multiple formats.it will be easy if it ask me to covert videos for a specific device like i-pod,Nokia,Samsung mobiles.thanks in advance:-)
Mediacoder is a good tool MediaCoder - Choose your MediaCoder edition. I use it all the time to convert videos for my phone. It has device specific settings and interfaces but also lets you pick and choose. It’s a windows program but works great in wine. The only thing is you need to have firefox for wine installed. It has device specific builds as well MediaCoder - Device
+1 for handbrake it has presets for ithings… also ensure you have
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.4 (x86_64) Kernel 22.214.171.124-0.5-desktop
up 2:26, 3 users, load average: 0.26, 0.13, 0.09
GPU GeForce 8600 GTS Silent - Driver Version: 270.41.06
Sorry for coming late.i installed both(handbrake and avidemux).i used to total video converter and any video converter(these two videoconverters are for windows).i have trouble with both(handbrake,avidemux).because i don’t know how to use both.in windows converters I’ll add videos and select formats(mp4,avi,flv) or devices(ipod,Nokia or Samsung)then I’ll click covert button.it will covert my videos and put them in my desired path.it is quite difficult to me covert videos in handbrake or avidemux.
handbrake does exactly what you just described.
handbrake is also available for MS-Windows and MacIntosh and I have a MacIntosh friend whose uses it (for his iPad) and thinks it great. In fact he was the one who recommended I use it to create videos for my wife’s iPod Touch 3G.
I recently used it to create a number of videos for my wife to test on her iPod Touch 3G. The videos played great on that device !
I will use video converter to play videos in my mobile.it’s screen resolution is 320*240.please tell how to convert a video in that resolution.
I suggest to take a look in the manual of the respective application.
vike4, there is more to this than ‘just’ resolution. There is the video codec. There is the audio codec. And there is the respective bit rates.
vike4 I think if you want help here, you need to point to your specific mobile model number, else this thread could go on for a LONG time before the necessary details are flushed out.
Hmm my mobile model:Samsung s5620(Monte).
@groupiuskalle i read the handbrake guide but can’t understand anything.
sorry I am not having enough knowledge in multimedia.
There are many programs online, you could google it.
Ok, thats a start. What does your information on the Samsung s5620(Monte)'s specs tell you ?
I note this:
Display resolution: Resolution: 240 x 400 pixels
Video capture resolution: 320x240 (QVGA) (15 fps)
Music Player: Supports: MP3, AAC, AAC+, WMA
Video Playback: Supports: MPEG4, H.263, H.264
I also read that one can not play back at the 240x400 resolution unless one has hacked their phone.
There is a handbrake guide here for a Galaxy Tab … just change the resolution to your 240x320 How to convert videos and transfer them to the Samsung Galaxy Tab - Know Your Mobile India (you may need to reverse numbers to 320x240, … and try different bit rates).
In Handbrake you could try the “Apple” “ipod” presetting as it should be close to 320x240.
okay i am in my hsc now so only i can’t reply i will check your sites and get back to you.
Getting this to work for You in openSUSE may require compiling FFMPEG with FAAC support on Your own. (because of legal issues)
“Compiling” sounds worse than it really is, but will require some careful research and reading.
i haven’t done so myself, yet, because of the following:
There are distributions that make it easier:
In Sabayon Linux the version of FFMPEG had everything i needed. (example: http://amoebios.wikispaces.com/Convert+videos+for+W995+with+FFMPEG+on+Linux)
Ubuntu required adding repositories (because of the legal issues), but that’s easier than compiling, and Ubuntu also provides lots of software, especially frontends, like
Transmageddon Video Transcoder,
WinFF, which is my favorite.
Why would FAAC support be essential ?
It does NOT require recompling with the Packman packaged ffmpeg for the Apple iPod format.
I seriously doubt that one needs to recompile ffmpeg for a Samsung Monte S5620.
That’s why i said “may”. i don’t like sending people off to other distros.
i just don’t want people to spend their life in front of a computer.
Further to this thread, I did encounter a case with winff that it assumed for creation of an aac codec that libfaac was installed and it failed. But correct me if I am wrong, but libfaac creates an aac codec (via proprietary means) and instead one can use the ‘aac’ codec in packman.
On this subject, last night I ended up playing with wiff. I found a packaged version by searching here: software.opensuse.org: Search Results
This provides winff-1.3.1-2.7.x86_64.rpm which is not quite the most recent version (as 1.3.2 is most current according to WinFF - Free Video Converter ). This packaged winff comes with a number of presets for different hardware (ipod, blackberry … ).
I gave it a try to convert a .flv downloaded from youtube, but immediately had a failure. Checking the conversion code (it uses ffmpeg) I noted it was use ’ -ab 128kb ’ where in fact the code should be ’ -ab 128k ’ with current ffmpeg versions. So I removed the ‘b’ from that and tried again.
I then had another failure in that it could not find the audio codec ‘libfaac’. I recall that libfaac codec support was removed from ffmpeg due to proprietary versions, but it appears the presets assume ffmpeg is built with ‘libffaac’ support. So I changed the ‘libfaac’ entry to ‘aac’ and tried again.
I then had another failure noting that ‘aac’ was an experimental codec, and to use it I had to also use the code ‘-strict experimental’. So I tried again, replacing ‘libfaac’ with ‘aac -strict experimental’ and the conversion worked.
I then went into /home/oldcpu/.winff/presets.xml and with a text editor replaced ALL occurences of ‘libfaac’ with ‘aac -strict experimental’ and also searched for all ‘-ab’ occurences and ensured the following number had no ‘b’ beside it. That took a bit of time, although I did find a way to optimise that had had that conversion completed in ~ 5 minutes of effort.
winff is now running nicely.