-
Notifications
You must be signed in to change notification settings - Fork 65
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
Add support for writing cue chunks #31
Comments
Could you elaborate? The only reference to “marker” on the linked page is
|
Yes. To be precise, I am looking for a method to place a "cue" point inside a wave, that is displayable through some audio software like Reaper. The "cue" chunk is explained here in more detail. |
Ah, that makes sense. I just merged #27 which allows writing arbitrary chunks, which enables this, although it is a bit low-level. It would be nice to have special support for writing a cue chunk too. I hope to go over all of the new features once more soon to make sure that the API works, and being able to implement cue points on top of that would be a good test for that. |
Any progress on a release with this? It would be nice to be able to use hound to write cues/markers! |
In case it might help you, there is a workaround posted on stackoverflow to have cue points being written to wav files. |
At the moment there is still no high-level API for writing cue points, the best you can do at this time is to write the chunk manually. |
For now, I haven't found a method to write a marker to a wave file at a specific position. Markers are place din the "format "data section in the "fmt" subchunk. See here for more details.
The text was updated successfully, but these errors were encountered: