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

Add SequencerSpecificEvent , and empty!(::MIDITrack) #173

Merged
merged 6 commits into from
Jul 19, 2024

Conversation

NeroBlackstone
Copy link
Member

Related issue #172

@NeroBlackstone
Copy link
Member Author

Thank you for your review. If you decide merge, please make a new release, thank you very much.

CHANGELOG.md Outdated Show resolved Hide resolved
Project.toml Outdated Show resolved Hide resolved
test/SequencerSpecific.mid Outdated Show resolved Hide resolved
@NeroBlackstone
Copy link
Member Author

NeroBlackstone commented Jul 18, 2024

Thank you for your review! I have finished all the suggested changes.

@@ -31,4 +31,11 @@
@test_throws errtype MIDI.readsysexevent(Int(input[1]), IOBuffer(input[2:length(input)]))
end
end

@testset "SequencerSpecificEvent" begin
midi = load("SequencerSpecific.mid")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't undertstand what you are doing here. You are loading this midi data, but you don't use them next in the test suite...? The current test suite is meaningless you are only testing whether you initialized the SequencerSpecificEvent with the values you initialized it with. Rather trivial, no?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I don't think it's necessary to actually use this midi data.
If the added code is incorrect, an error will be throwed on this line when initialization, and causing the test to fail.
The fact that no exception is thrown already indicates that SequencerSpecificEvent is being parsed and instantiated correctly.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests have been added

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What, no not at all. What we want to know is whether we correctly find this special midi type in an actual midi track that we load. Instantiating the type is trivial, you aren't testing anything really if you only test that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But now we have this midi file, and it is very small, so thank you, this is exactly what I was asking for!

@NeroBlackstone
Copy link
Member Author

NeroBlackstone commented Jul 19, 2024

Also implement empty!(::MIDITrack), #174

@NeroBlackstone NeroBlackstone changed the title Add SequencerSpecificEvent support Add SequencerSpecificEvent , and empty!(::MIDITrack) Jul 19, 2024
@@ -31,4 +31,11 @@
@test_throws errtype MIDI.readsysexevent(Int(input[1]), IOBuffer(input[2:length(input)]))
end
end

@testset "SequencerSpecificEvent" begin
midi = load("SequencerSpecific.mid")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But now we have this midi file, and it is very small, so thank you, this is exactly what I was asking for!

@Datseris Datseris merged commit 17119ff into JuliaMusic:main Jul 19, 2024
@NeroBlackstone
Copy link
Member Author

@Datseris Hi, would you mind make a new release? Thank you very much 😊👍

@Datseris
Copy link
Member

yes! JuliaRegistries/General#111445

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