-
Notifications
You must be signed in to change notification settings - Fork 366
Pulseaudio: Update pulseaudio comments #1046
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
philburk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. These comments are more clear.
| { | ||
| PaPulseAudio_Lock(stream->mainloop); | ||
| /* Pause stream so it stops faster */ | ||
| /* The stream should be paused to facilitate a quicker cessation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original comment was more concise and more clear. How were these comments generated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly with GPT and then altered by hand
|
I've made more small adjustments to comments. Now they should be more shorter and precises. |
|
@illuusio I have pushed some edits (see my latest commit). Could you please review them? I have some additional remarks which I'll put into a review now. |
RossBencina
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added specific review comments on the lines where I think that there are obvious remaining issues. I found a few more minor grammatical issues during review and I will commit those now.
There are still a few places wher ethe code comments which have unclear meaning.
There are a some cases where the code comments indicate half duplex input-only code paths, but the logic of the code seems to activate for both input-only and input+output code paths. I don't know whether the code has a bug or the comments are wrong. Please review the code and the logic and let me know whether you see what I mean. Otherwise I can explain further.
I might have found a bug: missing usleep() call in PaPulseAudio_ReleaseOperation
I fear than many of the GPT translations were hallucinated and not consistent with the intent of the code. I am concerned that you did not already pick this up. Before we finalise the PR please make sure that every comment in the final diff is consistent with your understanding of the code. If there are remaining cases where no one understands the meaning of a comment then the comments can only serve to confuse and we should delete them.
Also please let's work methodically through my review comments, plase don't make other unrelated changes as that will only confuse things further.
| PaPulseAudio_UnLock( hostapi->mainloop ); | ||
|
|
||
| waitOperation --; | ||
| wait --; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?BUG: if the earlier comment is correct, and the retry loop runs for seconds/milliseconds, shouldn't there be a call to usleep() here at the end of the loop body?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes there should. Good catch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed this one also
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Each PR needs to address a specific issue. Changing code for an unrelated purpose is not appropriate in the current PR. Please factor all of the changes to PaPulseAudio_ReleaseOperation (including both the code and the comments) into a separate PR. The comments in this function may need to be clarified but we can discuss that in the new PR.
| while( waitOperation > 0 ) | ||
| /* Since the primary operations are conducted locally, a wait time | ||
| * of 1 to 3 seconds, followed by an additional 1000 milliseconds, | ||
| * is deemed sufficient to to detect successful completion or to detect an error. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"to to"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update this one.
0b26a76 to
1bc092c
Compare
|
Is this ready to merge? |
2152cb2 to
f62186b
Compare
…d for clarity and specificity. The comments in _PaPulseAudio_ProcessAudio required enhancement; therefore, the comments have been revised to provide greater specificity and improved clarity in the English language.
…ated. The remaining comments in the PulseAudio callback file should be updated to utilize passive voice and improved English for clarity.
Make more adjustments to pulseaudio cb comments.
As Ringbuffer it does not underrun but it does overrun data. Co-authored-by: Ross Bencina <rossb@audiomulch.com>
Simplify comment about buffer size calculation Co-authored-by: Ross Bencina <rossb@audiomulch.com>
Update unlocking comment wording to more understandable Co-authored-by: Ross Bencina <rossb@audiomulch.com>
f62186b to
a4e2d5d
Compare
|
Thanks for the updates. I have deleted two comments that were low-quality and redundant. Remaining issues:
|
This pull request addresses concerns regarding the comments in the file by updating several comments within the PulseAudio files.