You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FastFlix Version:
5.82 Operating System:
windows 11 B22631 Describe the bug
Selected CUSTOM from drop out menu in CRF choice, then entered 1 in the CUSTOM box.
Gave the PROFILE a name .
When I click on that customized PROFILE, CRF reverts to 19
To Reproduce
Steps to reproduce the behavior
VIDEO dropped into the internal play window or queued
Click on saved profile title.
But instead of a CRF of 1 as I saved, 19 appears. The rest of my customized choices are saved, including dimensions, speed etc. Screenshots
If applicable, add screenshots to help explain your problem.
Logs (If applicable) In FastFlix you can go to Help > Open Log Directory and sort by latest to find the newest log file to add here.
Please make sure to remove any personal information or video names in the screenshots and logs!
THANK YOU for a very useful product. Hope to donate in the near future, even if this issue is not adjusted because on the whole it's a very human friendly and useful app..
The text was updated successfully, but these errors were encountered:
FastFlix Version:
5.82
Operating System:
windows 11 B22631
Describe the bug
Selected CUSTOM from drop out menu in CRF choice, then entered 1 in the CUSTOM box.
Gave the PROFILE a name .
When I click on that customized PROFILE, CRF reverts to 19
To Reproduce
Steps to reproduce the behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Logs (If applicable) In FastFlix you can go to Help > Open Log Directory and sort by latest to find the newest log file to add here.
Please make sure to remove any personal information or video names in the screenshots and logs!
THANK YOU for a very useful product. Hope to donate in the near future, even if this issue is not adjusted because on the whole it's a very human friendly and useful app..
The text was updated successfully, but these errors were encountered: