On Thursday 15 May 2008 20:39:09 Sam Clemens wrote:

Kevin Dupuy wrote:

...

On Wed, 2008-05-14 at 10:52 +0100, Ying Shi wrote:

...

Hi, all:

I have used suse for several days now. I am a home user, frequently watching movies and online video clips. I also have Windows XP in my PC.

As I notice, there is big performance difference between SUSE and XP when playing video media. For example, RealPlayer in XP plays video well. But in OpenSUSE, the same video also played in RealPlayer, it gets jitter and missing frames. When playing some online video clip embeded in webpage, XP is smooth and I can do other things and browse other pages. Everything is fine. But in SUSE, I can hardly do other things. Any other thing responds slowly. Other web page in firefox come up really slow.

Does anyone else have similar experience?

I need your help. Thanks

I've noticed this as well. If you're running Compiz or Compiz Fusion (Desktop Effects) that tends to slow down the video for me. And Beagle shouldn't cause that kind of problem.

If only that could be said for all systems.

Shouldn't cause that kind of problem, but often does.

Beagle can use an absolutely huge amount of memory. It can also have a dramatic effect on file access times. Try disabling it. I don't rate realplayer in linux and even less on xp ect. It's very intrusive. There is a one click media update on the opensuse.org web site http://opensuse-community.org/Restricted_Formats/10.3 From memory you can select several things to install. Select them all. Make sure you include mplayer even though that may fail to install. If you have 10.3 64bit you may run into trouble but it will hopefully be ok otherwise. Think you will then find either Xine or Kaffeine will play everything including streaming. In the case of 10.3 64bit there are lots of dependency problems but at some point you can select not to look for you "optimum architecture". That will leave one dependency that can't be found. Select not to install it. It may all seem a little complicated to a windoze user but it's down to the fact that there is a much much wider variety of software available on linux. If you find you eventually want full blown mplayer find and go to the web site and follow the install via cvs instructions in a console. Make a directory called say mplayer. Click on it. Right click - actions - open consol here. When the cvs has finished type. ./configure <> ./make <> su <> your root password <> make install <> make clean <>. Where <> is return. Don't worry about what they instructions mean just do it. It might even do all that for you. You will need to have the gnu c compiler and cvs support installed. Yast will do that for you. Use Yasts search and then install. You will also need the codec packages found on the same site. These will need an extract here and the same actions I outlined above in the directory formed. You can install any source package in the same way. Very useful if you can't find a specific suse rpm. You compile from scratch instead. Sometimes you will get a can't find what ever while compiling. Search for the what ever with yast and install it. Then go back to the ./configure etc. John -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 16 May 2008 01:53:32 Charles philip Chan wrote:

John writes:

...

If you find you eventually want full blown mplayer find and go to the web site and follow the install via cvs instructions in a console.

However, depending on the codecs and funtionalities you want it to support, getting all the dependency can be quite confusing for a new user. For example to get rstp support one would need the live555 library and/or libnemesi.

Charles

I agree but it's the 1st one I did that way. Prior to that I had installed other software via compiling source. Yast can usually supply the missing elements. Others can be found via google or by asking on a mailing list such as this. A file in the extracted directory called README or INSTALL etc will usually list the steps needed to install this way too. In mplayers case the instructions for getting the source via cvs is given in some detail. I went through the motions of describing the actions needed because many suse users may at some point find software they want available as source but not via yast. It's a better option than some rpm that's not really intended for there specific version of linux etc. Ok they may finish up with dependencies that can't be fixed for a variety of reasons but in my experience that's rare from source and common with rpm's. John And OK I'm a software engineer but I'm sure many people could manage it if they tried. Older windoze users might like to think of these missing libs/dependencies as dll's. They will be uniquely available or part of some package of similar items. This means more installs from source if yast can't supply them and maybe even more needed. Makes me wonder why Yast will not compile and install source. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org