qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: "Christian Schoenebeck" <qemu_oss@crudebyte.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-devel@nongnu.org
Cc: devel@daynix.com
Subject: Re: [PATCH v3 1/2] coreaudio: Commit the result of init in the end
Date: Thu, 16 Jan 2025 14:17:46 +0900	[thread overview]
Message-ID: <7f183c25-2e70-4bc7-b3bb-0f488743f13e@daynix.com> (raw)
In-Reply-To: <7790509.UIITUpbOhM@silver>

On 2025/01/16 2:10, Christian Schoenebeck wrote:
> On Wednesday, January 15, 2025 4:37:28 PM CET Akihiko Odaki wrote:
>> On 2025/01/16 0:14, Christian Schoenebeck wrote:
>>> On Wednesday, January 15, 2025 1:06:55 PM CET Akihiko Odaki wrote:
>>>> init_out_device may only commit some part of the result and leave the
>>>> state inconsistent when it encounters an error. Commit the result in
>>>> the end of the function so that it commits the result iff it sees no
>>>
>>> Typo "if".
>>
>> I meant if and only if.
>>
>>>
>>>> error.
>>>>
>>>> With this change, handle_voice_change can rely on core->outputDeviceID
>>>> to know whether the output device is initialized after calling
>>>> init_out_device.
>>>>
>>>> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
>>>> ---
>>>>    audio/coreaudio.m | 49 +++++++++++++++++++++++++++----------------------
>>>>    1 file changed, 27 insertions(+), 22 deletions(-)
>>>>
>>>> diff --git a/audio/coreaudio.m b/audio/coreaudio.m
>>>> index cadd729d5053..b9e1a952ed37 100644
>>>> --- a/audio/coreaudio.m
>>>> +++ b/audio/coreaudio.m
>>>> @@ -355,7 +355,10 @@ static OSStatus audioDeviceIOProc(
>>>>    static OSStatus init_out_device(coreaudioVoiceOut *core)
>>>>    {
>>>>        OSStatus status;
>>>> +    AudioDeviceID deviceID;
>>>
>>> I would probably preserve the name 'outputDeviceID' to make it more clear that
>>> it's for output.
>>
>> I omitted output because this function is for the output device; every
>> variable in this function is for output and prefixing them with output
>> makes the code verbose.
> 
> Disagree. When you review audio driver code there are many 'devices', so it is
> helpful to see the context straight away. Especially on large functions like
> this one.

It is not special to the device ID. Other variables like frameRange, 
audioDevicePropertyBufferFrameSize, and ioprocid are bound to this 
output device. In theory we could have similar corresponding variables 
for the input device so they should be prefixed with "output" if it 
matters. Prefixing only this variable is inconsistent.

> 
>>>
>>>>        AudioValueRange frameRange;
>>>> +    UInt32 audioDevicePropertyBufferFrameSize;
>>>> +    AudioDeviceIOProcID ioprocid;
>>>>    
>>>>        AudioStreamBasicDescription streamBasicDescription = {
>>>>            .mBitsPerChannel = core->hw.info.bits,
>>>> @@ -368,20 +371,19 @@ static OSStatus init_out_device(coreaudioVoiceOut *core)
>>>>            .mSampleRate = core->hw.info.freq
>>>>        };
>>>>    
>>>> -    status = coreaudio_get_voice(&core->outputDeviceID);
>>>> +    status = coreaudio_get_voice(&deviceID);
>>>>        if (status != kAudioHardwareNoError) {
>>>>            coreaudio_playback_logerr (status,
>>>>                                       "Could not get default output Device\n");
>>>>            return status;
>>>>        }
>>>> -    if (core->outputDeviceID == kAudioDeviceUnknown) {
>>>> +    if (deviceID == kAudioDeviceUnknown) {
>>>>            dolog ("Could not initialize playback - Unknown Audiodevice\n");
>>>>            return status;
>>>>        }
>>>>    
>>>>        /* get minimum and maximum buffer frame sizes */
>>>> -    status = coreaudio_get_framesizerange(core->outputDeviceID,
>>>> -                                          &frameRange);
>>>> +    status = coreaudio_get_framesizerange(deviceID, &frameRange);
>>>>        if (status == kAudioHardwareBadObjectError) {
>>>>            return 0;
>>>>        }
>>>> @@ -392,31 +394,31 @@ static OSStatus init_out_device(coreaudioVoiceOut *core)
>>>>        }
>>>>    
>>>>        if (frameRange.mMinimum > core->frameSizeSetting) {
>>>> -        core->audioDevicePropertyBufferFrameSize = (UInt32) frameRange.mMinimum;
>>>> +        audioDevicePropertyBufferFrameSize = (UInt32) frameRange.mMinimum;
>>>>            dolog ("warning: Upsizing Buffer Frames to %f\n", frameRange.mMinimum);
>>>>        } else if (frameRange.mMaximum < core->frameSizeSetting) {
>>>> -        core->audioDevicePropertyBufferFrameSize = (UInt32) frameRange.mMaximum;
>>>> +        audioDevicePropertyBufferFrameSize = (UInt32) frameRange.mMaximum;
>>>>            dolog ("warning: Downsizing Buffer Frames to %f\n", frameRange.mMaximum);
>>>>        } else {
>>>> -        core->audioDevicePropertyBufferFrameSize = core->frameSizeSetting;
>>>> +        audioDevicePropertyBufferFrameSize = core->frameSizeSetting;
>>>>        }
>>>>    
>>>>        /* set Buffer Frame Size */
>>>> -    status = coreaudio_set_framesize(core->outputDeviceID,
>>>> -                                     &core->audioDevicePropertyBufferFrameSize);
>>>> +    status = coreaudio_set_framesize(deviceID,
>>>> +                                     &audioDevicePropertyBufferFrameSize);
>>>>        if (status == kAudioHardwareBadObjectError) {
>>>>            return 0;
>>>>        }
>>>>        if (status != kAudioHardwareNoError) {
>>>>            coreaudio_playback_logerr (status,
>>>>                                        "Could not set device buffer frame size %" PRIu32 "\n",
>>>> -                                    (uint32_t)core->audioDevicePropertyBufferFrameSize);
>>>> +                                    (uint32_t)audioDevicePropertyBufferFrameSize);
>>>
>>> 'audioDevicePropertyBufferFrameSize' is declared as UInt32, so I guess the
>>> cast can be dropped.
>>
>> It had a cast even though core->audioDevicePropertyBufferFrameSize is
>> also UInt32. I suspect there are some cases where uint32_t and UInt32
>> are defined as different types and the compiler complains for "wrong"
>> print format.
> 
> This was introduced by cbc36cb05. While changing the format specifier made
> sense, the cast was unnecessary, but ... never mind.
> 
>>>
>>>>            return status;
>>>>        }
>>>>    
>>>>        /* get Buffer Frame Size */
>>>> -    status = coreaudio_get_framesize(core->outputDeviceID,
>>>> -                                     &core->audioDevicePropertyBufferFrameSize);
>>>> +    status = coreaudio_get_framesize(deviceID,
>>>> +                                     &audioDevicePropertyBufferFrameSize);
>>>>        if (status == kAudioHardwareBadObjectError) {
>>>>            return 0;
>>>>        }
>>>> @@ -425,11 +427,9 @@ static OSStatus init_out_device(coreaudioVoiceOut *core)
>>>>                                        "Could not get device buffer frame size\n");
>>>>            return status;
>>>>        }
>>>> -    core->hw.samples = core->bufferCount * core->audioDevicePropertyBufferFrameSize;
>>>
>>> Are you sure this should be deferred to the end of the function?
>>
>> Yes. Setting core->hw.samples only makes sense after
>> AudioDeviceCreateIOProcID() succeeds, which starts generating samples
>> according to the set value.
> 
> OK, I just reviewed the pathes in this function that return zero, and realized
> that these were added by you (3ba6e3f6), however I don't see any comment on
> why you have treated them as returning as non-error cases there.

kAudioHardwareBadObjectError and kAudioHardwareBadDeviceError imply the 
device was unplugged. They are not fatal as eventually we will get 
another active device with the handle_voice_change callback.

Regards,
Akihiko Odaki

> 
> In general I highly recommend to be more verbose on your changes. For instance
> for this patch here it would have helped to see a comment which error path
> exactly you encountered. Because it makes it more easy for other people to
> understand what you are trying to fix exactly.
> 
> /Christian
> 
> 



  reply	other threads:[~2025-01-16  5:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15 12:06 [PATCH v3 0/2] coreaudio fixes Akihiko Odaki
2025-01-15 12:06 ` [PATCH v3 1/2] coreaudio: Commit the result of init in the end Akihiko Odaki
2025-01-15 15:14   ` Christian Schoenebeck
2025-01-15 15:37     ` Akihiko Odaki
2025-01-15 17:10       ` Christian Schoenebeck
2025-01-16  5:17         ` Akihiko Odaki [this message]
2025-01-16 10:31           ` Christian Schoenebeck
2025-01-15 12:06 ` [PATCH v3 2/2] coreaudio: Initialize the buffer for device change Akihiko Odaki
2025-01-15 15:31   ` Christian Schoenebeck
2025-01-15 15:40     ` Akihiko Odaki

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=7f183c25-2e70-4bc7-b3bb-0f488743f13e@daynix.com \
    --to=akihiko.odaki@daynix.com \
    --cc=devel@daynix.com \
    --cc=kraxel@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu_oss@crudebyte.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).