-
Notifications
You must be signed in to change notification settings - Fork 8
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
Octet stream files #744
Comments
Hi,
This should work much better with the new ingest system. I will set mime
types based on the extension instead since it's usually self-evident.
We'll work on expanding those rules if we notice issues.
Once the new ingestions system, I'll use the same code to validate al the
current mime types which should fix these.
Cheers,
John
…On October 23, 2023 at 9:33 AM, jodiekell ***@***.***) wrote:
We have some issues with larger audio files where the Nabu catalog is
presenting some of these files as ‘octet stream’. They can be
successfully downloaded and played as wav files, but look different in
the catalog (see the screenshot below).
[image: Screen Shot 2023-09-21 at 3 31 41 pm]
<https://user-images.githubusercontent.com/20469903/277195953-bb43c884-cb62-4c6a-b546-8d228ea9a0d9.png>
There are 496 octet stream files in the catalog and they are all between
2-4gb.
To explain about larger audio file formats, Dobbin formats them as RF64
which is a standard extension of wav files intended to support large
files over 4gb and multichannel audio.
In this case, we choose to output mbwf wav files in Dobbin, but if they
are large files, they are processed as RF64 files with a bext metadata
chunk.
Stefan Zachau from Cubetech support explains it like this:
“The RF64 format doesn't have the BEXT chunk. You should use the "MBWF"
format instead. MBWF is based on RF64 - basically it is an RF64 plus BEXT
(like BWF is a standard WAV plus BEXT).”
Usually this does not cause a problem except in the case of the octet
stream files.
Whilst the octet stream files do download correctly as wav files, it
would be best if they were listed as wav files to avoid confusion.
—
Reply to this email directly, view it on GitHub
<#744>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAKMXVDQ2IB264ETVVQ4H3YAWNMRAVCNFSM6AAAAAA6LGNWDSVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2TMMBYGE3DKNA>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thanks John. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have some issues with larger audio files where the Nabu catalog is presenting some of these files as ‘octet stream’. They can be successfully downloaded and played as wav files, but look different in the catalog (see the screenshot below).
There are 496 octet stream files in the catalog and they are all between 2-4gb.
To explain about larger audio file formats, Dobbin formats them as RF64 which is a standard extension of wav files intended to support large files over 4gb and multichannel audio.
In this case, we choose to output mbwf wav files in Dobbin, but if they are large files, they are processed as RF64 files with a bext metadata chunk.
Stefan Zachau from Cubetech support explains it like this:
“The RF64 format doesn't have the BEXT chunk. You should use the "MBWF" format instead. MBWF is based on RF64 - basically it is an RF64 plus BEXT (like BWF is a standard WAV plus BEXT).”
Usually this does not cause a problem except in the case of the octet stream files.
Whilst the octet stream files do download correctly as wav files, it would be best if they were listed as wav files to avoid confusion.
The text was updated successfully, but these errors were encountered: