-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Per track meters #5861
Open
Paul-Licameli
wants to merge
111
commits into
audacity:master
Choose a base branch
from
Paul-Licameli:PerTrackMeters
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Per track meters #5861
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Paul-Licameli
added
the
Experimental
Exploratory, proof-of-concept PRs, never to me merged
label
Jan 12, 2024
I just tested on W10 your branch: audacity-win-3.5.0-alpha-20240112+5d1bafd-x64 The per track meters seem to work properly. One thing to note: just like the main meters these per track meters can only be reset by stopping and restarting: See: #5658 |
Paul-Licameli
force-pushed
the
PerTrackMeters
branch
from
May 13, 2024 14:54
28c2480
to
72f5faf
Compare
... The UI will still be present, but won't work
... maybe changing how non-LTI stereo effects (reverbs?) apply to mono tracks
... Also possible slight change in graphical meter level as explained in comments
... because that atomic might otherwise change
... the other playback policy subclasses (scrub, cut preview, looping) were not used for recording; and recording never went backwards
... eliminating two member variables of AudioIO; fixing unused argument in UpdateTimePosition
... TimeQueueGrainSize affects this decision slightly.
... States are to be used only by the playback producer thread, not for recording. MIDI play synchronization is (still, but differently) wrong for changes of loop play bounds.
... Instead, it and the TimeQueue share a variable which is stored in PlaybackState. This allows PlaybackSchedule to be const qualified in all member functions of PlaybackPolicy.
Paul-Licameli
force-pushed
the
PerTrackMeters
branch
from
June 2, 2024 16:05
72f5faf
to
4f80347
Compare
... Control areas are narrower, for WaveTrack. For other kinds of tracks, which don't have meters, the control areas are now wider.
Paul-Licameli
force-pushed
the
PerTrackMeters
branch
from
June 2, 2024 19:43
597547b
to
df879bc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves: (direct link to the issue)
Depends on
(short description of the changes and the motivation to make the changes)
Recommended: