Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Is Totem getting deprecated?

  1. #1
    Join Date
    Jul 2010
    Location
    Stockholm, Sweden
    Posts
    85

    Default Is Totem getting deprecated?

    With a special to wolfi323 & jdmcdaniel3

    Having been a Gnome user since SuSE9 (up to the iPhone-look) Totem has been a favorite mediaplayer. It was always fairly simple to make it play restricted formats (if I remember right installing libxine1, xine-ui and w32codec-all was enough). I think the problems started with gstreamer and possibly also pulse-audio.
    -From around the SuSE11-versions I went over to SMPlayer2 and VLC that I have used since then, together with Kaffeine. They can handle most of my media files (but with a more tricky and opaque installation of the gst*-plugins).

    I thought I should give Totem a final try in SuSE13.1, and failed!
    I should first explain that I've got a working gstream- and ffmeg-installation (with just Packman as repo) and that this installation makes VLC and SMPlayer2 able to handle mpeg1 mpeg1 layer3 mpeg2 mpeg4 mpeg4-aac h.264 and vmv8 wma8 wmv9 and wma9.

    -Now following the guidelines in:
    http://forums.opensuse.org/showthrea...-missing-codec
    https://forums.opensuse.org/showthre...mpga-h264-mp4a
    https://forums.opensuse.org/showthre...ht=totem+mpeg4
    and completed my gst*-installation with
    gstreamer-plugins-libav (For AAC support)
    gstreamer-plugins-bad-orig-addon
    gstreamer-plugins-ugly-orig-addon (For H264 support)
    libx264-142
    The pkg gstreamer-plugins-ugly-addon I could not find in Packman repo.
    and made a
    # zypper dup --from Packman
    Then finalized with checking if the latest guide could complete my installation in any way, using:
    https://forums.opensuse.org/entry.ph...allation-Guide.

    Now, Totem still complains about missing decoders for
    mpeg4-video-decoder
    h.264 decoder
    gstreamer-element videoconvert (though I've got gstreamer-plugins-base installed)
    mpeg-1 audio-decoder
    mpeg-1 layer 3 audio-decoder
    wmv video8 screen-decoder
    wma audio8 decoder

    Is it time to give up Totem?

    (I've got similar problems with Totem in SuSE12.3)

    Best regards
    Lars

  2. #2
    Join Date
    Jun 2008
    Location
    West Yorkshire, UK
    Posts
    3,611

    Default Re: Is Totem getting deprecated?

    No; not sure why you have been installing codecs by hand rather than using http://forums.opensuse.org/showthrea...a-in-One-Click

  3. #3
    Join Date
    Jul 2010
    Location
    Stockholm, Sweden
    Posts
    85

    Default Re: Is Totem getting deprecated?

    Because I'm a masochist trying to become a nerd
    ...or in fact, I like to understand what I do

  4. #4

    Default Re: Is Totem getting deprecated?

    Quote Originally Posted by Larsed View Post
    Is it time to give up Totem?

    (I've got similar problems with Totem in SuSE12.3)
    Well, I never used (or liked) totem much, but it does work fine here with all audios/videos I throw at him for a test.
    But I prefer KDE anyway.

    And I always preferred to avoid gstreamer as well (mainly because of the higher use of resources).

    I did a comparison test on my system recently (but with mp3s only), and Mplayer was the best regarding CPU usage, with VLC second.
    Please read here, if you're interested: (since then I'm not too fond of xine anymore either... )
    http://forums.opensuse.org/showthrea...47#post2630247
    Btw, there is no gstreamer-plugins-ugly-addon.
    I would find it strange though that you have those problems, even after doing a zypper dup to Packman, because as I said it does work fine here.

  5. #5
    Join Date
    Feb 2014
    Location
    Romania
    Posts
    87

    Default Re: Is Totem getting deprecated?

    although i am a bit offtopic, i am trynng to avoid the gstreamer too. the mplayer and VLC are more CPU efficient.
    unfortunately, some audio players like clementine, amarok, qmmp depend on gstreamer.

  6. #6

    Default Re: Is Totem getting deprecated?

    Quote Originally Posted by rich1974 View Post
    unfortunately, some audio players like clementine, amarok, qmmp depend on gstreamer.
    Amarok does NOT depend on gstreamer, and never has.
    Amarok uses KDE's phonon, which has a VLC backend as well. Just install phonon-backend-vlc (included in openSUSE 13.1) and select it in KDE's (or Amarok's) audio settings.

    And qmmp doesn't use gstreamer either AFAICS. It has its own plugins, and apparently even can use MPlayer as engine (qmmp-mplayer).

    You're right about clementine though.

  7. #7
    Join Date
    Jul 2010
    Location
    Stockholm, Sweden
    Posts
    85

    Default Re: Is Totem getting deprecated?

    Well thank you wolfi323 !

    Sorry about the delayed answer! You see your reply opened up (at least) two jungles in front of me that set me in a state of despair.

    The first jungle: the matter of optional backends and resource consumption.
    Even if I knew that Amarok today has the option to switch between gstreamer- and vlc-phonon-backends I thought that all mediaplayers -except vlc- were bound to gstreamer. Now I understand how wrong I was.
    I read your comparison test with interest! I saw you had the same processor. That made me curious about trying the same in a limited way. amarok, vlc and smplayer2 playing the same mp3. -The result was horrifying:

    Code:
      PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND            
     5161 larse     20   0 5554684 182572  79400 R 29,45 8,887   0:12.97 amarok         
     2906 larse     20   0 1289704  57636  37908 S 4,312 2,805   0:09.05 vlc                
     2945 larse     20   0  729280  38384  24684 S 0,995 1,868   0:01.81 smplayer2
    amarok above used the phonon-gsteamer-backend. -After I switched to the phonon-vlc-backend
    Code:
      PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND   
     3897 larse     20   0 5497716 167380  75396 R 13,61 8,147   0:21.95 amarok    [vlc-backend]
    The second, and worse jungle: I realized that I simply do not have a clue about the Linux sound system and how it has developed!
    Perhaps I have got a vague idea about the "bottom part": the hardware and drivers (in my case Creative Audigy2 - snd_emu10k1) and the top: the mediaplayer and a few of their decoders.
    But I'm totally lost when it comes to everything "in between" and how it's related to each other, or succeeded by, or made obsolete. I simply do not understand the concepts of ALSA OSS PulseAudio GStreamer Xine Phonon and/or Jack.
    Personally I find the first few lines in http://tuxradar.com/content/how-it-w...explained#null very comforting.
    5 or 6 years ago, in the times of the SuSE10's, I had the ambition to try to learn the Linux sound system. But something always came in the way like it often tends to in my Linux-world. Sometimes voluntary (like learning Slackware, setting up at stripped Slackserver & writing material to it, OnionRouter, GNURadio, et c), sometimes involuntary (like systemd and related).
    I will not bother you with my incompetence concerning the Linux sound system, but if you know some reference book och guide that also covers the later development I would be very thankful if you mentioned it!

    But, to return to my initial Totemquestion, I'm very thankful for your looking through my setup description! I think I read my referenced links very careful. Where I got the "gstreamer-plugins-ugly-addon" from I don't remember, but it was anywhere among those links. And as it seemed consistent with the gstreamer-plugins-bad-addon (and gstreamer-plugins-bad-orig-addon) I looked for it.

    After having read your comparison test I also checked for libmad0 and libmpg123 and found I had them installed.

    So, with all things considered, Totem should work! But it doesn't. With the help of ffmpeg I made a final check about which decoders Totem could not handle in this final state. Totem handles:
    Audio: handles uncompressed wav, not compressed flac
    further; handles compressed aac, not mp2, wma2 or most mp3's
    Video: handles mjpeg, not mpeg1video, mpeg4, h.264 or wmv2.

    On the other hand, I've after SuSE10.3 never got Totem to work in a decent way. Since then I've also found me a few better mediaplayers (MPlayer2 and VLC). So there's really no great loss! I only thought I should give Totem a final try.

    Besides, when Gnome switched to the iPhoneDE, I switched to Xfce .

    Best regards! And thank you again!

    Lars

  8. #8
    Join Date
    Jul 2010
    Location
    Stockholm, Sweden
    Posts
    85

    Default Re: Is Totem getting deprecated? [Solved!]

    Well well, I got a hint from the Ubuntu-people (not very seldom I must admit ).
    http://ubuntuforums.org/showthread.php?t=1502057

    The problem was never a decoding problem, but a registry-one.
    Could I see the video thumnails? No.
    Could I play my videos with Totem ran as root? Yes! (Something I almost always try when something fails in Linux, but tottally forgot here.)
    Then it's probably a problem of permissions or a registry error.

    Now the solution suggested in the Ubuntu-thread was not as simple to apply in SuSE.
    Consulted the gstreamer FAQ http://gstreamer.freedesktop.org/dat...ad/faq/faq.pdf (page 11) and found it must be a version dependent solution.

    In SuSE12.3 and 13.1 there seems to be a coexistence between gstreamer 1.0 and 0_10. Therefore there are two gstreamer registry files in two different directories:
    ~/.gstreamer-0.10/
    and
    ~/.cache/gstreamer-1.0/
    each one containing a registry file "registry.*.bin" (the * substitutes architecture)
    It's in the following important that you delete both! Or the remaining will conflict with the one you are about to create.

    Now dependent of which gstreamer version your system mainly relies on install gstreamer-0_10-utils and/or gstreamer-utils, both containing a tool "gst-inspect" that can check your gstreamer installation and build a registry.

    The rest is simple:
    As already said: check if you have got more than one registry.*.bin, delete them!

    If mainly gstreamer version 0_10, as user run
    $ gst-inspect-0.10
    That will build a new registry (in this case in ~/.gstreamer-0.10/. Don't worry, the other will build automatically in due time)

    If mainly gstreamer version, as user run
    gst-inspect-1.0
    That will build a new registry (in this case in ~/.cache/gstreamer-1.0/. (The other will build automatically in due time)

    That's it!

    I finally got back my video thumbnails that I have missed since SuSE10.3!
    And of course Totem now can play most of my audio and video formats .

    Greetings

  9. #9

    Default Re: Is Totem getting deprecated? [Solved!]

    Well, I was about to suggest to delete the gstreamer plugins registry...

    But AFAIK it should not be necessary to run gst-inspect manually, as it should get recreated automatically (I'm not 100% sure though).

    And the gstreamer-0_10 cache has absolutely no influence to gstreamer-1.x, so it's NOT necessary to delete both for totem, ~/.cache/gstreamer-1.0/ should be enough.

    gstreamer-0.10 and gstreamer-1.x are designed to coexist on the same machine, but they are completely different things.

  10. #10
    Join Date
    Jul 2010
    Location
    Stockholm, Sweden
    Posts
    85

    Default Re: Is Totem getting deprecated? [Solved!]

    It's possible that you're right, I didn't write from OSS knowledge as I stated, just from trial-and-error and the only thing I had at hand was the old Ubuntu hint.

    the gstreamer plugins registry.... ...should get recreated automatically (I'm not 100% sure though)
    I'm not sure either, I didn't wait.

    And the gstreamer-0_10 cache has absolutely no influence to gstreamer-1.x, so it's NOT necessary to delete both for totem, ~/.cache/gstreamer-1.0/ should be enough.
    It's very possible that you're right here, which also could indicate that you were right above. -Going out from the Ubuntu hint I didn't know that there were a second registry, just the one in ~/.gstreamer-0.10/. Deleting and recreating that one didn't change a thing. -It was first when I found the second registry ~/.cache/gstreamer-1.0/ and deleted that one too and recreated ~/.gstreamer-0.10/ with gst-inspect the Totem issue was solved. -Using $ gst-inspect-0.10 or $ gst-inspect-1.0 didn't matter, running one "seemed to recreate the other" in my eyes. That could indicate that it ...should get recreated automatically, as you say. -And as you probably understand I had no idea that Totem relied on gstreamer-1.0 only.

    Looking back I can only ask myself how it comes that year after year with fresh installs since the SuSE 11's up to 13.1 on my same AMD x86_64-machine this registry obviously has been built in a way I should call corrupt? Just made plain installations of the media requirements with Yast2, later with zypper, normally following one of the current guides on the forum (remember esp. oldcpu, my favourite ;-). -I've never been aware of that registry, or that gstreamer tool. -Should it really only depend on "**** behind the keyboard" as we say in swedish?
    Now solved I also noticed that the solution also affected Kaffeine in a very positive way.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •