-
Notifications
You must be signed in to change notification settings - Fork 1
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
Extension freezes Safari #4
Comments
Hey, this is some weird behavior. Can you check if you have the audio compressor enabled after importing your settings? I had some heavy freezing issues when the compressor was enabled. |
In the FFZ Control room, I unchecked "Enable Audio Compressor and add an "Audio Compressor" button to the controls." Now the Compressor button disappeared. I think that fixed the issue with freezing, but sometimes the Audio sounds robotic. I can't send you any Clip where this appears. |
Weird bug, I can't really do anything about tbh. I just inject the official ffz/ bbtv scripts that one would do via Tempermonkey, Userscripts, ... Maybe you can play around with your settings and let me know what one should not activate. I will put a section on the readme with known issues/ buggy settings. |
Wouldn't it be a good idea to provide two programs? One with FFZ and one without. I don't use FFZ, so for me that is useless. A user can decide whether to download with or without. |
Good question and you're totally right! Someone brought this up in this #2 issue and there is already a beta release I linked in a comment in there. It includes new logos and a UI if you click on the extensions icon in Safaris toolbar. In there, you can check and uncheck BTTV & FFZ. Feel free to check this one out and see if it works for you. |
I have followed your instruction and installed on Safari, but the Extension "freezes" for me. I can't few Stream on Twitch, Browse Websites anymore or even Reload Pages. To Mention, I have imported my BTTV Setting from Firefox.
Could it be the FFZ Extension that causes this?
The text was updated successfully, but these errors were encountered: