satvik upadhyaya

thanks and yeah that's exactly why i wanted the target size interface instead of making users deal with CRF values themselves. currently fp uses a bounded CRF search, encoding candidates and measuring their actual output sizes rather than relying solely on bitrate calculations and it doesn't automatically drop audio when the target is tight yet but an optional --no-audio flag sounds useful especially for the screen recordings. appreciate the suggestions.