Skip to content

Should we invert real-time factor? #27

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.

Sign up for GitHub

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

Jump to bottom
Open
Blaizzy opened this issue Mar 12, 2025 · 0 comments
Open

Should we invert real-time factor? #27

Blaizzy opened this issue Mar 12, 2025 · 0 comments

Comments

@Blaizzy
Copy link
Owner

Blaizzy commented Mar 12, 2025

Should we invert the real-time factor? If so, why?

The source, states that values lower than 1 are better and above 1 are worse. Inverting it will cause rtf to have significant higher values.

Formula:

def real_time_factor(processingTime, audioLength, decimals=2):

    ''' Real-Time Factor (RTF) is defined as processing-time / length-of-audio. '''

    rtf = (processingTime / audioLength)

    return round(rtf, decimals)

Source: https://openvoice-tech.net/wiki/Real-time-factor

Originally posted by @Blaizzy in #24 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Blaizzy