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

Use frame_offset instead of frame for Cue Point position #10

Merged
merged 3 commits into from
Sep 28, 2021

Conversation

atoav
Copy link
Contributor

@atoav atoav commented Aug 16, 2021

As described in issue #9 cuepoints from a Sound Devices MixPre-Series recorder are returned with the wrong frame value of always 0. I tried the suggested fix in a fork and it worked for me as expected with both files. I tried running the tests, but as I am currently on a windows machine I guess I am out of luck with that one.

Feel free to modify, deny, etc this PR if there are things which I overlooked.

@iluvcapra
Copy link
Owner

Would you be able to create a small test file from the MixPre and add it to the test cases?

@atoav
Copy link
Contributor Author

atoav commented Aug 16, 2021

I will check tomorrow. This is mostly just about adding it to tests/test_media.tgz right?

@iluvcapra
Copy link
Owner

Yes if you can please add your file to the test_media.tgz file I'll take it from there thanks!

As described in issue iluvcapra#9 the function cue_points() didn't display the
expected frame values for cue points created on a Sound Devices
MixPre-Series recorder. The file added by this commit
(sounddevices_6_cue_points.wav) is short and mono channel, but has 6 cue
points in it.

The expected frames for the cue points are:
0: 90112
1: 176128
2: 237568
3: 294912
4: 380928
5: 385024
@atoav
Copy link
Contributor Author

atoav commented Aug 17, 2021

Okay I added it. I also took the freedom to delete all (invisible on macOS) ._* files (._DS_STORE etc) in the tar-file that might have been added by your file system.

@iluvcapra
Copy link
Owner

Hey just a Q- what is this test file PaxHeader/ff_pink.wav in the updated zip file?

@iluvcapra
Copy link
Owner

Also for the file you added, could you please document for me here what you expect the value to be? I'll add a unit test for it!

And unit tests for cue metadata.
@iluvcapra iluvcapra merged commit 468ed12 into iluvcapra:master Sep 28, 2021
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.

2 participants