Draft
Conversation
warning: code is a mess right now.
|
Hi~ 我的改动初衷是自用需求,能帮助到广大网友优化主项目是我的荣幸。
祝中国新年快乐! |
This file contains hidden or 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
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.

Process()way of getting logs, rather than relying onOSLogStore, from 🚀🚀🚀 LosslessSwitcher (通用版) / Universal Audio Sample Rate Switcher #195, special thanks to @FantasticSkyBaby, which hopefully solves High disk writes? #115IMPORTANT, for beta 1, a profile is needed, which can be downloaded and installed from https://eclecticlight.co/2023/03/08/removing-privacy-censorship-from-the-log/
Profile Direct Link: https://eclecticlight.co/wp-content/uploads/2023/03/enablelogprivatedata.zip
You should always exercise caution by reading the above blog post to know what you're installing. Do also note that the profile is external, not made by me, and not signed by me either.
This profile lets the app map sample rate data to whichever track its supposed to belong to, which helps with the #159 issue.
For beta 1, it will not work properly without the profile. This is because I'm slightly drained right now after a day spent on this, not logically clear how to infer which data belongs to which track, if that makes sense to you.
As per always, I make no guarantees that it will work. Hopefully it does though.
Warning: Code right now is a mess.