Skip to content
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

Fix waveform and iOS compilation issue #131

Merged
merged 4 commits into from
Sep 18, 2024
Merged

Fix waveform and iOS compilation issue #131

merged 4 commits into from
Sep 18, 2024

Conversation

alnitak
Copy link
Owner

@alnitak alnitak commented Sep 18, 2024

Description

fix #129
fix #128
fix #130

Type of Change

When changing the frequency of waveform sounds using the flutter_soloud package, after a while, some background frequencies are heard along with the original frequency.

The waveform generation (on C+ side) used float numbers, but higher precision was needed to compute the waveform. Changing to doubles fixed the issue!

Minor changes for the other 2 issues that fix compiling on iOS.

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@alnitak alnitak self-assigned this Sep 18, 2024
@alnitak alnitak added the bug Something isn't working label Sep 18, 2024
@alnitak alnitak merged commit cd692f4 into main Sep 18, 2024
1 check passed
@alnitak alnitak deleted the fix_waveform branch September 18, 2024 20:03
@alnitak alnitak restored the fix_waveform branch September 18, 2024 20:06
@alnitak alnitak deleted the fix_waveform branch September 22, 2024 07:11
MarklBcm pushed a commit to bcm-it-team/flutter_soloud that referenced this pull request Sep 24, 2024
…equoia

Fix waveform and iOS compilation issues
# Conflicts:
#	.vscode/tasks.json
#	example/pubspec.lock
#	src/player.h
@filiph
Copy link
Collaborator

filiph commented Oct 16, 2024

[nit] I think raising deployment target is definitely a breaking change. In the future, we should consider only doing it between major semver updates. This change broke the codelab and therefore might have broken others' code, too.

(Just to be clear, I'm glad these fixes landed regardless, and having the iOS version at 13 is probably good future-proof-wise. Just a heads up for the next time we need to change deployment targets.)

@alnitak
Copy link
Owner Author

alnitak commented Oct 16, 2024

Sorry, I had to think of that! 🫣

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment