|
From: Anthony K. <mai...@an...> - 2020-08-10 15:14:21
|
Sounds great! I tried the file -tb.rubak and as you said it doesn't seem to work correctly. I wonder if I broke the tick playback when I implemented the CoreMIDI driver? IIRC, there were some differences between OMS & the serial driver in the way MIDI messages were routed thru BP2 code. I didn't fully understand which code paths I should use in the new driver and maybe I chose incorrectly. In fact, there is a problem in BP 2.9.8 that I've noticed with MIDI input. It shows up when one enters many notes quickly with "type from MIDI". BP 2.9.8 seems to pause noticeably between displaying each note in the input window. I think this is due to the event loop being called in between the processing of each MIDI event. I should try to fix this problem for BP 2.9.9. Anthony On 8/9/20, 11:40 AM, Bernard Bel wrote: > I keep thinking about it when it gets too dark to walk in the forest! ;-) > > For the moment I try to reproduce procedures the very way they had been > designed in projects such as "-gr.tryCsoundObjects". I had designed a > few simple Csound instruments that for instance would "translate" > pitchbend messages to changes of frequency. THis may have an incidence > on the procedure of "translating" a MIDI sequence to a Csound score in > an object. I'll try to clarify how far it had been done. All this will > be taken care of by the interface when designing sound-object > prototypes, with no incidence on the console. > > Same thing with the Timebase: I am going to implement an advanced model > for generating "ticks", but mixing them with real-time MIDI output of > the console will be much easier than the former solution (which anyway > no longer worked). It is also very easy to merge MIDI files and this > method can be used now that machines have become much quicker writing > MIDI files! |
