jdachtera
commented
10 years ago Hm my answer got lost somehow, so here is another try. First, the MTC class just displays what it get's from the daw software. It would be helpful to see what midi messages are being sent. By the way: Which os and software do you use?
Your observation is apparently correct. According to http://www.blitter.com/~russtopia/MIDI/~jglatt/tech/mtc.htm one should add 2 frames to the timestamp for displaying purposes since the quarter frame message constructed timestamp is always 2 frames behind.
test.js now works again. You can send whatever messages you want. But you would need to construct or parse them yourself. I think a higher level api would certainly make sense but this is out of scope of this project (actually also the MTC class isn't really related to the network transport thing). Maybe if I get some spare time I will start another project for this.
Isilwing
Hello Bro!
Reporting something i found, not sure if its daw related or node-rtpmidi related, but i think is good to report anyways. When transmiting MTC from the sequencer and i do a selection to play it in a loop, the timecode do the loop in the sequencer but in the console.log it keep going straight.
And the last thingy, again not sure if its the desired behavior as the sequencer is showing me SMPTE, i notice a difference in the Frames between the sequencer and the console.log, its only 2 frames sometimes other 4, i mean if i stop the sequencer in 00:00:20:10 in the console.log i see it at 00:00:20:12. Could be that im sending the data by socket.io each 33 ms, maybe this is causing some miss behavior, but reporting anyways just in case.
By the way i was checking the webapi.js ill try to test it soon, still getting used to all this but having so much fun, i notice that the sending message from the test.js is not longer working due the change in all the other scripts, its possible to send MMC like stop, play, record, etc?
Regards