Totem low streaming performance when accesing smb shares

[Alex Lopez]

Binary package hint: totem

I am using Gutsy amd64.
With this version totems succeds to play smb networked media, but performances is poor and video playback is horrible (stops playing for buffering, etc).
If I mount the smb share through mount smbfs, video plays correctly, so I discard any network related problem.

This happends both, using gstreamer or xine.

[Basilio Kublik (sourcercito)]

Hi there
I wasn't able to reproduce this issue against a linux samba share nor a windows one, even using a wireless connection works like a charm, i'm using i386 though.
does make any difference if you try to reproduce this from a livecd environment?.

[Alex Lopez (alfitovdkiv)]

Hi!

I am also testing over a samba share on a feisty server.
I have the same problem either with my gutsy amd64 laptop over wireless or with a gutsy i386 wired desktop.

I will try to check if a connection between the desktops gives the same results.

Thanks

[Iulian Udrea (iulian)]

Thank you for your bug report. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try to reproduce this bug with latest Ubuntu release?

[Alex Lopez (alfitovdkiv)]

Hi.

I'm very sorry. I forgot to update this issue.
I had the same problem in similar scenario. Looks like a proble with samba server, not totem.
Anyway, with a gutsy server run correctly.
Maybe is some missconfiguration and not a package problem. I am not sure.

Best regards.

[DFreeze (dfreeze)]

Same amount of sorry here ;-) I have to really look into it again. Just the
other day though, with an alpha version of Hardy I tried to view a movie
over my network connection, and it would come to a halt after some 15
minutes. Don't know if it's related, because I didn't skip to that part, but
just streamed the movie until it faltered. Skipping a few seconds back to
try another time to get past the freeze point didn't help.
I ended up copying the movie to the harddisk before watching on, but I'll
try to see whether I can replicate the behaviour (or something similar).

On Fri, Mar 14, 2008 at 12:30 AM, Alex Lopez <email address hidden> wrote:

> Hi.
>
> I'm very sorry. I forgot to update this issue.
> I had the same problem in similar scenario. Looks like a proble with samba
> server, not totem.
> Anyway, with a gutsy server run correctly.
> Maybe is some missconfiguration and not a package problem. I am not sure.
>
> Best regards.
>
> --
> Totem low streaming performance when accesing smb shares
> https://bugs.launchpad.net/bugs/164580
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[DFreeze (dfreeze)]

I just did a check with Totem in Hardy, and I can still reproduce the behavior. Streaming a movie through the network did work, even scrolling through the movie with the mousewheel. But placing the glider halfway by dragging, the movie stops playing. I get about two screen-refreshes per minute, and even waiting for five minutes, Totem can't get it to resume normal playing. So in short - yes, the bug is still buggin'.

...Oh wait, I just tried to stream a movie from my other PC (most movies are on my NAS), and from there, I could skip to anywhere in the movie. So the prime suspect isn't Totem anymore. I guess my NAS can't keep up (cheapo external disk with an ethernet socket). So as far as I can judge, this bug can be closed.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Intrepid Ibex. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Pedro Villavicencio (pedro)]

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.