this post was submitted on 25 Jul 2023
3 points (100.0% liked)

Programming

20 readers
1 users here now

This magazine is dedicated to discussions on programming languages, software development, and coding. Whether you are a beginner programmer or an experienced developer, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as coding languages, software engineering, web development, and more. From the latest trends and frameworks to tips and tricks for debugging, this category covers a wide range of topics related to programming.

founded 2 years ago
 

https://github.com/ZILtoid1991/pixelperfectengine/blob/117ffcf785b5fadf4324902d4944238d34668e65/pixelperfectengine/src/pixelperfectengine/audio/base/midiseq.d#L125

I have some issues with understanding the documentation on how set tempo events and time divisions work, so it's really not well calculated, and thus causes my code to just zoom through the MIDI file I'm throwing at it. Maybe there's some other chunks I'm not processing at the function that should be processing MIDI events here, so I don't really know.

top 2 comments
sorted by: hot top controversial new old
[โ€“] VeeSilverball@kbin.social 2 points 1 year ago

An overview of PPQN:

http://midi.teragonaudio.com/tech/midifile/ppqn.htm

Some reference code I've used, which might help with architectural issues: https://github.com/triplefox/minimidi/tree/master/minimidi

[โ€“] ZILtoid1991@kbin.social 1 points 1 year ago

Potential solution: It seems like multiplying the time by 10 solved it, at least now it doesn't zooms through the MIDI track in an instant.

https://github.com/ZILtoid1991/pixelperfectengine/blob/5cc5834f931783b5553d9959cfe66fe8f9ea6cfe/pixelperfectengine/src/pixelperfectengine/audio/base/midiseq.d#L125