-
Notifications
You must be signed in to change notification settings - Fork 56
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
Multichannel audio #41
Comments
This is due to how things are defined in the original standard, they only specify behavior for 5.1 audio. I believe there has been more recent work to extend the standard to more multichannel formats. This is something we could look into building out in pyloudnorm. @rawrbw, did you have a particular use case in mind? |
Ok I see. I was under the impression that 5.1 is actually 6 channels as the ".1" specifies the LFE channel? I was trying out multichannel content and noticed it would not accept more than 5 channels. |
Ah, I see there is an issue. The standard states:
The code needs to be adapted to ignore the LFE channel in this case instead of throwing an error. Let me work on a patch for this. Thanks for raising this issue. I have not done much testing with multichannel content myself. |
Ok that explains it! Thank you for your excellent work! 👌 |
So after taking a second look I think the current behavior may be the best option, however, there could be more documentation to describe the expected usage. What is important is that the user feed pyloudnorm with the proper channel layout, and that may vary by use case. In other words, pyloudnorm expects that the channel layout as follows: |
What is the reason behind the 5 channel limit on multichannel audio?
The text was updated successfully, but these errors were encountered: