All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Audio gaps with bcm2035 and Hama receiver
Date: Fri, 26 Oct 2007 00:48:14 +0200	[thread overview]
Message-ID: <1193352494.6184.290.camel@violet> (raw)
In-Reply-To: <4720C85B.1090300@hccnet.nl>

Hi Remy,

> I'd like to have my sound sent over from my laptop with a BCM2035 chip to a
> Hama receiver. Though it works fine under W*ws, the sound under Linux is
> broken off every minute for a second to continue afterwards. I used mplayer
> and xmms2. and both have this problem.

try the version from CVS or wait until I release a new one. These issues
should be fixed now.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-10-25 22:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 16:46 [Bluez-users] Audio gaps with bcm2035 and Hama receiver Remy Bosch
2007-10-25 22:48 ` Marcel Holtmann [this message]
2007-10-26 12:53   ` Remy Bosch
2007-10-26 16:20     ` Remy Bosch
2007-10-26 17:35       ` Brad Midgley
2007-10-26 20:26         ` Remy Bosch
2007-10-26 21:46           ` Brad Midgley
2007-10-26 23:40             ` Remy Bosch
2007-10-30 11:29               ` Brad Midgley
2007-10-30 11:49                 ` Remy Bosch
2007-10-30  6:25       ` Sumeet VERMA
2007-10-30 10:22         ` Remy Bosch
2007-10-30 10:23           ` Sumeet VERMA

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1193352494.6184.290.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.