Helo Robin! ltc2amidi looks interesting. But where does the file: ltcsmpte.h belong to? I don't have it on my system. Kindest regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Julien, Sorry, late reply. I've been away last night.. Julien Claassen wrote: yes. Thanks for reporting this. fixed that in SVN. It's a curses console tool, that a) generates LTC from jack-transport b) displays incoming LTC c) relays LTC (parse incoming, generate new) It does not do any MIDI. only http://en.wikipedia.org/wiki/Linear_timecode

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Julien Claassen wrote: Yeah, but it does not solve my issue. I do require MTC (MIDI Time Code) not Midi-Clock to sync with external equipment here. I've been careless last night: MIDI Clock - though similar - is not MIDI Time Code. sorry for the noise, robin

Julien Claassen wrote: From the Cakewalk Pro Audio 8 User's Guide, Chapter 15 page 2 Synchronization Overview Clock Source.... Timing is determined by ... -------------------------- -------------------------------- Internal The clock on the computer motherboard Audio The clock on the computer's sound card MIDI Sync The clock on the external MIDI device SMPTE/MIDI Time Code (MTC) A time code signal (in SMPTE or some other format) recorded on some external medium SMPTE is the acronym for the Society of Motion Picture and Television Enginers. In SMPTE format, time is measured in hours, minutes, seconds, and frames. When I wanted to sync Cakewalk to my Roland MIDI modules, I used SMPTE recorded to an audio cassette, with the output from the audio cassette cabled back to my Winman 4X4/S MIDI controller PCI card in the computer box. My preference was always to use SMPTE for syncing up MIDI synthesizers and hardware. I've never gotten into video work, but perhaps some of the video software available to Linux will allow you to use SMPTE for your MIDI syncing. A reference you may find helpful in MIDI programming is Rob Young's The MIDI Files, ISBN 0-13-262403-6, copyright Prentice Hall Europe, 1996. The blurb on the back jacket says: Taking a light-hearted, informal approach, The MIDI Files guides the user through the initial 'getting to grips' stage to present full and detailed sections on all aspects of professional MIDI song-sequencing. A career change side-tracked me away from completing my study of this book. But what I did get through was easy to understand, came with a 3.5inch diskette giving examples of the techniques being discussed in the book. This is the best book on MIDI programming that I've found to date. Hope this helps you Julien, Stephen Stubbs.

On Sat, Aug 1, 2009 at 8:01 AM, Julien Claassen<julien(a)c-lab.de> wrote: MIDI Clock provides information about position along a timeline measured in musical time (beats & bars). MIDI TimeCode provides information about position along a timeline measured in hr:min:sec:frames (frames == video frames) They are not at related to each other in any way (other than both using MIDI to transmit positional information). Further, MIDI Clock is theoretically useless unless the receiver knows the tempo/meter map. In practice, many common pieces are in a single tempo and meter, and you simply set the receiver to match the sender. the MIDI Clock data stream contains no information about the tempo/meter map that it is derived from.

Hi Julien, I don't know enough about MTC to answer your other questions... but I can answer your MIDI Clock questions and explain a bit how it works (so you know its limitations).[1] On Sun, 2 Aug 2009, Julien Claassen wrote: Yes, and Yes. When they say that MIDI Clock is "realtime" it means that the commands are a single byte that can be sent anytime, anywhere (even in the middle of a SysEx dump). So, they are given priority on the MIDI bus. MIDI Clock works like this: The messages are START, STOP, CONTINUE, TICK. START: Start playing from the beginning of the piece on the _next_ TICK. STOP: Stop playing now. CONTINUE: Start playing where we left off, on the _next_ TICK. TICK: 1/24th of a beat. TICKs have to be evenly spaced in time... and they indicate the tempo. The faster the ticks come, the faster the tempo is. So, if we abbreviate TICK with a dot (.), a typically performance would look like this: START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . STOP CONTINUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . STOP Thus, the machines stay synchronized... but if there are any errors there is no means of recovery or indicating "In case you forgot or have lost count... the next TICK is the DOWN-BEAT." Nor is there any way to say "Position to bar 99, beat 3."[2] There's a little more to MIDI Clock usage (like song position pointers)... but this is the basic capability (and IN-capability). Peace, Gabriel [1] FWIW, my favorite MIDI reference is here: http://www.blitter.com/~russtopia/MIDI/~jglatt/ http://www.blitter.com/~russtopia/MIDI/~jglatt/tech/midispec.htm [2] With song position pointers, you can (sort of) specify the number of beats from the start of the song. But you can't say "bar 99, beat 3." You have to know the number of beats in measures 1-98, add 3 (for the 3rd beat), and then multiply the sum by 4. That's the number that you send.

Hi Josh, hmm good question, in this case I would just set the tempo in seq24 and make it jack master (seems to work here), would this be possible in your setup? Cheers PS: thanks to Kevin Meinert's additions seq24 can now also be MIDI slave (bzr version), but then of course it won't handle jack transport. --- En date de : Ven 31.7.09, Josh Lawrence <hardbop200(a)gmail.com> a écrit :

Thanks for this Gabriel! I never stumbled upon klick...will test :) Frank --- En date de : Ven 31.7.09, Gabriel M. Beddingfield <gabriel(a)teuton.org> a écrit :

All: On Fri, 31 Jul 2009, Gabriel M. Beddingfield wrote: I'm pleased to announce "JACK MIDI Clock," a small command-line utility that will send out MIDI Clock pulses based on the current state of the JACK Transport: http://www.teuton.org/~gabriel/jack_midi_clock/ http://www.teuton.org/~gabriel/jack_midi_clock/jack_midi_clock-0.1.0.tar.bz2 git://gabe.is-a-geek.org/git/jack_midi_clock.git Comments, suggestions, and patches are welcome.[1] Peace, Gabriel [1] This includes the not-so-imaginative name. :-)

Hi Julien, On Sat, 1 Aug 2009, Julien Claassen wrote: I've been starting JACK with "-d alsa -Xseq" -- which enables me to send the pulses over ALSA. Does that not work for you? Peace, Gabriel

Sorry, another reply here too. So I'm really confused now and don't know what is what and where it belongs anyway. Here's what I imagined I could do: Start the jack_midi_clock app, send the clock data to my alsa sequencer based midi-recroding app and use this to sync it with an audio app. Can I do this, or not? Best regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

So you just use jack_midi_clock to adjust some tempo based effects of you hardware machine. OK. But would it be possible for you to add start/stop. Start would be the main thing. I can manage a stop somehow. :-) I wouldn't even need a special locate, if locate is forward, rewind, jump to a sppecific position. A real nice first would simply be: load my midifile, start my jack-audio client and then kick them off togeter. I don't mind who starts whom, as long as they do it. :-) And if they somehow keep in sync. So I can record a midifile track by track (or clearer speaking: instrument by instrument) and afterward listen to all instruments combined and see they fit right up until the end of the piece. That would be a dream of mine. :-) Kindest regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

Gabriel, I don't know if this takes the wrong way ion someonce's ears: But you're an angel! Really great thing to do. I think it might enable me to do a few things I've hungered for! Thanks for the work you put in this! Friendly regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

Hi! I can build from git, no problem. I'll clone it in a minute. As to follow MIDI start/stop, midish should be able to do it. Get midish: http://caoua.org/midish Install it and then in the example .midishrc in your home dir, which you can copy from the manual you can do something like: dnew 0 "20:0" rw # your ALSA sequencer soundcard client You connect your app to the soundcard, the you load a midifile: import "test.mid" Then you set your soundcard as master: devsetmaster 0 # set device 0 as master dclkrx 0 # set device 0 to be the clock source Then send a jack-transport start with i.e. ecasound: ecasound -c -i jack_auto,fluidsynth -o out.wav -G:jack,eca,send jack_auto,fluidsynth will take input from fluidsynth, use some other clientname if you use another softsynth. Hope that helps! Kindest regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de

Hi Gabriel! Sorry, I didn't get around to it. At the moment there's a lot to do here. My father is in hospital, it takes a bit time to get there and of course here at home we also have to rearrange a couple of things. And on friday I'm off until monday. But maybe I'll get around to jmc before that. It shouldn't be too dificult. We'll see. Kindest regards Julien -------- Music was my first love and it will be my last (John Miles) ======== FIND MY WEB-PROJECT AT: ======== http://ltsb.sourceforge.net the Linux TextBased Studio guide ======= AND MY PERSONAL PAGES AT: ======= http://www.juliencoder.de