-
Notifications
You must be signed in to change notification settings - Fork 151
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
Feature request: whammy modulation #786
Comments
@TheNathannator and @RileyTheFox, I was wondering if either of you could comment on what went wrong with whammy modulation in the past? I see #487 and #513 as attempts, but it appears they were rolled back. I believe I may have fully implemented it tonight, though this is my first attempt at modifying the YARG codebase. I did connect it up to FiveFretPlayer and updated existing features that were there but commented out. My two pull requests for this feature are: YARG.Core: YARC-Official/YARG.Core#192 YARG Front End: #812 These PR's include details on what was changed / added. Probably the most controversial change is updating WHAMMY_FFT_DEFAULT in GlobalAudioHandler to 512 in an attempt to reduce latency between the guitar track and other tracks when pitch change is enabled. I am aware that there are notes mentioning that changing the FFT size causes BASS to crash, but I was not able to reproduce that. I don't know if the BASS version has been updated in this past year. I can of course remove this change. Another option would be to remove the pitch filter after whammy has been sitting at 0 for a period of time, but I couldn't figure out how to get an update tick in FiveFretPlayer. I will join the Discord server to make it easier to discuss this PR there. |
This has been merged to our |
On multitracks where we have an isolated guitar channel, can we have the return of the whammy modulation? It would be great to have an option for a number of semitones to modulate through. I believe the default from the official games was either 1 or 2 semitones.
The text was updated successfully, but these errors were encountered: