Skip to content
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

[r6] Add 4 files, some small corrections #3

Merged
merged 1 commit into from May 8, 2022

Conversation

ktmf01
Copy link
Collaborator

@ktmf01 ktmf01 commented Feb 1, 2022

This adds 4 mono files. 60 is just a mono file, 61-63 have short bursts of high-frequency sine waves added to speech to trigger predictor overflow in decoders that do not use 64-bit ints when appropriate

File 26, 27 and 55 had small changed to their metadata as I came across a decoder (Symphonia) that was much more strict than libFLAC and warned me about some things that were not strictly compliant with the specification

@ktmf01
Copy link
Collaborator Author

ktmf01 commented Feb 2, 2022

I'm marking this as draft as I found a potential problem with file 63. It has a few residual samples larger than 2^31, which makes ffmpeg complain.

@ktmf01
Copy link
Collaborator Author

ktmf01 commented May 1, 2022

The issue with ffmpeg has been fixed as of https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/296d3bbe167f06168ac54724626006b43002833f I suppose ffmpeg 5.1 will be the first release able to play file 63.

This adds 4 mono files. 60 is just a mono file, 61-64 have short
bursts of high-frequency sine waves added to speech to trigger
predictor overflow in decoders that do not use 64-bit ints when
appropriate

File 26, 27 and 55 had small changed to their metadata as I came
across a decoder (Symphonia) that was much more strict than libFLAC
and warned me about some things that were not strictly compliant
with the specification

Also a LICSENCE.txt file is added, readme.txt is changed to
README.txt and a license statement is added
@ktmf01
Copy link
Collaborator Author

ktmf01 commented May 8, 2022

I've just force-pushed this PR to add a LICENSE.txt and to add a license statement to README.txt

@JeromeMartinez
Copy link
Contributor

@ktmf01 just to be clear, the encoder input is also CC0? If not, the output can not be CC0, more a "fair use".

@ktmf01
Copy link
Collaborator Author

ktmf01 commented May 8, 2022

Obviously I cannot guarantee all files are completly free of any copyright, but I think I made a reasonable effort to use only material either free of copyright, material licensed under CC0 where it seems reasonable to believe the uploader created the material, or material I created myself. Being able to state that these files are licensed CC0 was the reason all files were remade for revision 5, I just forgot to state it in the README.

In an attempt to make this CC0-claim reasonably verifyable, I'll list my sources.

  • All files feature text-to-speech generated by Amazon Polly. To the best of my knowledge there rests no copyright on this as there is no artistic input in text-to-speech. Furthermore, Amazon Polly FAQ states the following:

Q: Who owns Polly recordings?
As between you and AWS, your Polly output belongs to you. If you input text into Polly that belongs to a third party, we require that you have the rights to do so. For more information, please see our Customer Agreement and how it handles “Your Content”

@mcr
Copy link
Contributor

mcr commented May 8, 2022

I think you have gone way above and beyond due diligence here. Thank you.
Merge away!

@JeromeMartinez JeromeMartinez merged commit 7ba6e41 into ietf-wg-cellar:main May 8, 2022
@JeromeMartinez
Copy link
Contributor

I think you have gone way above and beyond due diligence here.

Agreed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants