[Csnd] Sync to MIDI clock
| Date | 2013-01-18 21:48 |
| From | martin |
| Subject | [Csnd] Sync to MIDI clock |
| Attachments | None |
| Date | 2013-01-18 21:51 |
| From | Justin Smith |
| Subject | Re: [Csnd] Sync to MIDI clock |
while we are at it, the midi bits that would need to be read to track nrpn input are also not reported by any existing opcoe On Fri, Jan 18, 2013 at 1:48 PM, martin <csound@neoprimitive.net> wrote: My application is MIDI synced LFOs and delay time. |
| Date | 2013-01-18 21:53 |
| From | Justin Smith |
| Subject | Re: [Csnd] Sync to MIDI clock |
I hit post too soon While I was looking for a way to implement an NRPN input plugin, I ended up patching my copy of csound to track the messages needed for NRPN. A similar approach could be taken to adding support for MIDI timeclock messages, or some modification could be made so that opcodes (even UDOs?) could get the raw MIDI stream.
On Fri, Jan 18, 2013 at 1:51 PM, Justin Smith <noisesmith@gmail.com> wrote:
|
| Date | 2013-01-18 21:56 |
| From | Victor Lazzarini |
| Subject | Re: [Csnd] Sync to MIDI clock |
I think this is because midiin only reads channel messages. I see csound can output midi clock, but not receive it. On 18 Jan 2013, at 21:48, martin wrote: > My application is MIDI synced LFOs and delay time. > > I can only find a few threads about this from years past... > > http://groups.yahoo.com/group/csound--maths.ex.ac.uk/message/30577 > http://csound.1045644.n5.nabble.com/midi-realtime-clock-td1120457.html > http://comments.gmane.org/gmane.comp.audio.csound.tekno/155 > > The only specific idea among these threads is to read MIDI clock > messages with the midiin opcode and use them to drive a phase counter. > > But as far as I can see from the manual and my tests, the clock > message is still not a value reported by the midiin opcode. > > Does anyone have a solid approach for doing this? > > Cheers, > > Martin > > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" > Dr Victor Lazzarini Senior Lecturer Dept. of Music NUI Maynooth Ireland tel.: +353 1 708 3545 Victor dot Lazzarini AT nuim dot ie |
| Date | 2013-01-19 05:59 |
| From | Jim Aikin |
| Subject | [Csnd] Re: Sync to MIDI clock |
> I think this is because midiin only reads channel messages. I see csound can output midi clock, but not receive it. I'm surprised. I can only guess nobody has ever needed to do this, because it's the kind of basic functionality that one would expect to be implemented as a matter of course. Maybe what's needed is some sort of generic midibyte opcode, which would retrieve the next 8-bit byte from the input buffer, no matter what it is, and allow one to test its value. The issue that might arise is, would that byte then be removed from the input buffer after being read by a midibyte opcode? Because if it was removed, then a midibyte opcode would, whenever the input was a channel message, break most of the other MIDI receive opcodes. Not a good thing. Thinking a little further outside the box, MIDI clock is one of a number of system messages (system realtime, system-exclusive, and maybe something else that I'm forgetting -- I can look it up if anyone is interested, as I have the MIDI Spec here on my shelf). Possibly what's needed is a midisys opcode that would grab all system messages. System-exclusive messages can include an arbitrary number of data bytes, and they end with an EOX. To receive sys-ex, an opcode would have to store the data bytes in a table. Hmm.... --JA -- View this message in context: http://csound.1045644.n5.nabble.com/Sync-to-MIDI-clock-tp5719465p5719473.html Sent from the Csound - General mailing list archive at Nabble.com. |