Conversation
…"Objective C++" option when compiling for iOS.
move mRecordingStream to public for DEBUGING (find devid)
| << "frames_in: " << frames_in << ",frames_out: " << frames_out << ",frames_filled_out: " << frames_filled_out | ||
| << ",in_callback_calls: " << in_callback_calls << ",out_callback_calls: " << out_callback_calls << ",ring_overrun: " << ring_overrun; | ||
| } | ||
|
|
There was a problem hiding this comment.
Why is this android file changing in an iOS change?
| * | ||
| * Author(s): | ||
| * ann0see based on code from Volker Fischer | ||
| * ann0see and ngocdh based on code from Volker Fischer |
There was a problem hiding this comment.
and the copyright date could do with updating.
ios/sound.mm
Outdated
| //vecsTmpAudioSndCrdStereo.Init ( iCoreAudioBufferSizeStereo ); | ||
|
|
||
| return iCoreAudioBufferSizeMono; | ||
| void checkStatus(int status){ |
There was a problem hiding this comment.
Why are these global?
Also style is wrong here. I think clang-format is ignoring the .mm files, which it should treat like .cpp files.
| connect ( action, SIGNAL ( triggered() ), this, SLOT ( close() ) ); | ||
| #endif | ||
|
|
||
| #if defined( ANDROID ) || defined( Q_OS_ANDROID ) |
There was a problem hiding this comment.
Again, this change is for iOS, so why this android change?
| pMenu->addMenu ( pEditMenu ); | ||
| pMenu->addMenu ( new CHelpMenu ( true, this ) ); | ||
|
|
||
| #if defined( Q_OS_IOS ) or defined( Q_OS_ANDROID ) or defined( ANDROID ) |
There was a problem hiding this comment.
I'd suggest this whole change - switching input device - be split out from the main pull request. It will make more sense as a separate change to have both iOS and android support then. Here the android bit looks lost.
|
OK, now I can see what's going on, I'd like the introduction of the new feature of selecting input device split into a separate change, dependent upon this one. There's a lot happening here already. Having that in as an "different thing" just makes this PR too big, in my opinion. Also, there are too many commits to simply merge this - we'd have to squash and that's a bit messy. Or someone would have to tidy it up a bit. |
|
Thank you @pljones for the thorough review. I’ll check the .mm file style. About the input selection feature, it would be complicated for me to split, now that the iOS PR is not yet merged. And yeah I’d love to have my commits tidied up. |
Review of jamulussoftware#1865 by @pljones revealed .mm extension was not checked.
Yes, but the other problem is we can't merge this as is (#1865 (comment)). Can you have a look at related commits and describe which features this PR exactly adds?
If we exactly know what you changed, we can try to get this into smaller commits. See solution 3 here: https://about.gitlab.com/blog/2018/06/07/keeping-git-commit-history-clean/ |
|
Ok so here comes some explanation for this PR:
The key here is: that additional feature could only have been implemented in a separate PR if the iOS sound support code had already been merged. |
|
Ok. Thanks for this explanation. This means that we can probably reduce the number of commits dramatically: Commit 1: Add iOS sound support This should also include the code which fixes the crash, formatting and the removal of the libraries to reduce the launch time. Commit 2: Allow automatic switching between internal/external audio devices (iOS) Commit 3: Add initial auto switching of audio device to Android You'd squash all the related commits into one or even better use |
|
I'm not sure what to do. The best thing I can do now, I think is to create a new branch from jamulus master, manually apply changes from this branch, and then remove all android related changes. That way I have a new iOS-only PR. Let's just say the feature comes with the sound support in iOS. Android can come later. |
|
Closing this as I've created #1875 for iOS, and a clean commit history. |
Review of jamulussoftware#1865 by @pljones revealed .mm extension was not checked.
* Add .mm extension to coding style check Review of #1865 by @pljones revealed .mm extension was not checked. * .clang-format for ObjC * Apply clang-format to sound.mm * Apply clang format on all .mm files Co-authored-by: ann0see <[email protected]>
|
unrelated: @hoffie I just ran your changelog-helper script and it listed this PR as being added to the next release? |
|
I'd just add CHANGELOG: SKIP |
|
Yes. It’s at least counter intuitive to have a closed PR in the changelog. On the other hand I think feature branch merges are not in the changelog (basically also an edge-case) |
* Add .mm extension to coding style check Review of jamulussoftware#1865 by @pljones revealed .mm extension was not checked. * .clang-format for ObjC * Apply clang-format to sound.mm * Apply clang format on all .mm files Co-authored-by: ann0see <[email protected]>
I messed #1512 up. So this is a brand new branch for iOS sound support. I hope this is not creating much trouble for the team.
TODO: clang-format