DGV RowHeaders and Granularity

[operatortwo]

The values in the cells looks a bit redundant. Maybe you could set RowHeader Text:

 Private Sub ShowDgvRowHeader()
        Dim offset As Integer = 24

        For Each row As DataGridViewRow In DataGridView1.Rows
            row.HeaderCell.Value = (row.Index + offset).ToString()
        Next

    End Sub

This looks like this:

Now cell value is free for other information.

---

Maybe you can increase the granularity of the Grid to allow different note durations. Now a cell = 1 quarter Note. How about 1 cell = 1/16 Note ? (or 1/32 Note) Then a note can have 1 or more cells to make difference in duration.

[CIRCE-EYES]

Hello ! Thank you very much for your suggestions about the program, I like the idea of ​​adding an offset value as integer and being able to use the cell value for something else. But there is a catch in the whole program and it is about being able to modify the value of the notes beyond what they have to be inside a cell. Let me explain ... now how it is done, it works very well like a drum machine, because in each reading of colored cells the sound is triggered, but it also makes a stopnote first. I mean, first stop and then it sounds. Therefore my wish would be that the sound of a certain note could be lengthened until I want to. I have done two tests.

[CIRCE-EYES]

First test was using a different color cell.
So cells in yellow color had different time value but was a crapp.
Second was using a specific value text in cell.
I used "X" In random cell text so could read like yellow above example time note duration. Results were bad.

[CIRCE-EYES]

The main issue/ problem is that the cells have the same phisic space.
But I have now discovered a trick to replace the cells values using a chart pictures.
But this is only an idea. Maybe to use a datagridview was the first error.!

[CIRCE-EYES]

Let me find in my pc to send this idea about chart instead cell datagridview.
And about your progress in your app, must say that the piano.dll its great !!!! Id like to have the source to add some things !!!!

[operatortwo]

.. And about your progress in your app, must say that the piano.dll its great !!!! Id like to have the source to add some things !!!!

Do you mean 'Midi_Keyboard' ? It has it's own repository. Midi_Keyboard repository

[CIRCE-EYES]

This is the future piano roll !!!

[CIRCE-EYES]

https://www.mediafire.com/file/kwajvmh0efpkcsr/Gantt+Chart+0.55+circe.zip/file

Have a look ! And see if its posible to replace datagridview for this idea !!!

[operatortwo]

Looks interesting.
I think writing a PianoRoll is a difficult task. I've just started a new attempt for a pattern -player / -editor /-creator but I won't write the PianoRoll view until later because it's so difficult.
Another difficulty is the need for the NoteOn - NoteOff pairs. I'll try to get rid of the NoteOffs in the pattern-player using NoteDuration instead. That would make editing easier. I'm thinking of a NoteOff list managed by the player. (somehow)
At the moment i'm starting from scratch with TimerTick, the internal DataStructure, maybe some Diagnosis values and so on.

[CIRCE-EYES]

Wow ! I will follow your project. May be working in pianoroll could be the first issue before main features, if not...you will have a drum box like mine. May be adapting the code attached above could help you.
Thanks.

[CIRCE-EYES]

I forgot to show you another proyect finished.
Its about Yamaha Style player chords sequences.

[operatortwo]

I'm not sure what do you require.
With a loop option, do you mean a restart after the midi-file was played, or do you mean loop playing between a start and end mark somewhere in the midi file, or maybe something else ?

[CIRCE-EYES]

I mean a clasic loop . So from begin to end and again .
When file ends, repeat again. But without delay in time, so the loop its perfect.

[operatortwo]

Okay. I will try. This can take a few days

[CIRCE-EYES]

Thanks a lot !

[operatortwo]

Midi-File is now updated with loop-option.
I also made a short test with drywetmidi. It seem that DWM uses the last NoteEvent as a Loop-point, while some midi-loops uses the EndOfTrack event as Loop-point.
On the other side: Some midifiles have the last EndOfTrack far behind the last note, in this case drywetmidi works better, while my solution has a long time of silence at the end.
A possible workaround for a single midi-loop with drywetmidi is maybe setting an event to the same time as EndOfTrack, for example a control-change with an unused controller number.