All of lore.kernel.org
 help / color / mirror / Atom feed
From: agraham <agraham@g-b.net>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU VNC Audio - All audio data null
Date: Sat, 14 Jul 2012 23:16:14 +0100	[thread overview]
Message-ID: <5001EFAE.1020009@g-b.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1207150005580.6908@linmac>

On 07/14/2012 09:09 PM, malc wrote:
> On Sat, 14 Jul 2012, agraham wrote:
>
>> On 07/14/2012 06:20 PM, malc wrote:
>>> On Sat, 14 Jul 2012, agraham wrote:
>>>
>>>> On 07/14/2012 01:55 PM, agraham wrote:
>>>>> On 07/14/2012 11:44 AM, malc wrote:
>>>>>> On Sat, 14 Jul 2012, agraham wrote:
>>>
>>> [..snip.]]
>>>
>>>>>>> I've just rebuilt QEMU 1.0 (and all of its dependencies) and it has
>>>>>>> the same
>>>>>>> problem (zero bytes), so some incompatibility was introduced between
>>>>>>> 0.15.1
>>>>>>> and 1.1.0.
>>>>>>>
>>>>>>> Anyone got any clues ?
>>>>>>
>>>>>> Please try to bisect the issue.
>>>>>>
>>>>>
>>>
>>> [..snip..]
>>>
>>>>
>>>> I cannot seem to get any further trying to find the source of this issue,
>>>> except to say that QEMU Audio over VNC used to work in QEMU 0.13 until
>>>> about
>>>> QEMU 15.1 then it appears to have stopped working as described above.
>>>
>>> As i said, try bisecting, doesn't involce too many brainwaves only raw
>>> machine power.
>>
>> Well, the problem is I'm rebuilding from Fedora spec file and that contains
>> about 122 patches very many relating to spice that could cause the problem and
>> it's in one of these that the bug may be introduced.
>
> Sorry, but i do not have Fedora and if you insist on using patched
> version do talk to Fedora people.
>
>>
>>> FWIW i just built a fresh checkout and it works for me with my own
>>> client...
>>
>> Which Client are you using?
>
> http://repo.or.cz/w/qemu-vcap.git
>
>>
>> Are you sure you're not using spice protocol?
>
> Yes.
>
>>
>> I've just rebuilt qemu package from:
>> http://koji.fedoraproject.org/koji/buildinfo?buildID=329768
>>
>> This is the latest Fedora 17 Package which builds qemu-kvm-1.1.0.tar.gz + a
>> bunch of patches.
>>
>> The only patch I've included is:
>> 0001-kvm-Enable-use-of-kvm_irqchip_in_kernel-in-hwlib-cod.patch, because it
>> will not compile without that patch. So it should pretty much match stock
>> 1.1.0
>>
>> I can confirm that the QEMU VNC Audio still does _not_ work and I get the
>> exact same results, i.e. when I read the sample format data from the socket it
>> contains the right amount of data, but the data contains zeros bytes, this
>> results in silence.
>>
>> Also I found this:
>> http://www.digipedia.pl/usenet/thread/19179/2346/#post2351
>>
>> The QEMU version they refer to is Fedora 16 which contains 0.15.x, which
>> confirms my own findings as stated above.
>
> Get a vanilla git version and try to reproduce if it's reproducible -
> bisect, if not try to seek help through Fedora channels.
>

I got the git version and created a tarbal and used the F17 Spec file to 
build all the packages - and it worked!

So this is now plain stock QEMU  (v1.1.50).

The problem still exists, exactly the same as previously described, and 
what I was expecting given my previous testing.

I also tried your client, and could not hear anything, the output was as 
follows:

# ./acap
5
server is `"QEMU (windows-xp-1)"'
Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 44100 Hz, 
Stereo
underrun!!! (at least -1342018345912.717 ms long)
underrun!!! (at least -1342018345917.003 ms long)
underrun!!! (at least -1342018345912.526 ms long)

So I modified the acap.sh script to save all received data to a file as 
follows:

#!/bin/sh
inputfd=$1
echo "$@" 1>&2
cat > file <&$inputfd
#aplay -t raw -c 2 -f S16_LE -r 44100 <&$inputfd

And this confirms that my original findings.

# hexdump -C file
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
|................|
*
000bf690  00 00 00 00 00 00 00 00                           |........|
000bf698

So now, I am assuming that you did _not_ "hear" actual sound, but 
assumed it was working because the output of the above script shows
data was being received.

Can you confirm this?

Does QEMU have a bug reporter ?


Albert

  reply	other threads:[~2012-07-14 22:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-14  2:17 [Qemu-devel] QEMU VNC Audio - All audio data null agraham
2012-07-14  5:37 ` agraham
2012-07-14 10:44   ` malc
2012-07-14 12:55     ` agraham
2012-07-14 17:10       ` agraham
2012-07-14 17:20         ` malc
2012-07-14 19:30           ` agraham
2012-07-14 20:09             ` malc
2012-07-14 22:16               ` agraham [this message]
2012-07-14 22:23                 ` malc
2012-07-14 22:42                   ` agraham
2012-07-14 22:52                     ` agraham
2012-07-14 23:23                       ` malc
2012-07-14 23:01                     ` malc
2012-07-14 23:13                       ` agraham
2012-07-14 23:21                         ` malc
2012-07-15 19:22                           ` agraham
2012-07-15 19:48                             ` malc
2012-07-16  0:03                             ` malc
2012-07-16  2:10                               ` agraham
2012-07-16  8:12                                 ` Daniel P. Berrange
2012-07-16 10:56                                   ` agraham
2012-07-16 19:58                                   ` agraham

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=5001EFAE.1020009@g-b.net \
    --to=agraham@g-b.net \
    --cc=av1474@comtv.ru \
    --cc=qemu-devel@nongnu.org \
    /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.