Re: Ardour as a midi timecode slave
robertlazarski <[email protected]> Sun, 25 Apr 2021 10:21:55 -1000
| Newsgroups | gmane.comp.audio.ardour.user |
|---|---|
| Message-ID | <CABpPLBXX2j9zKR1t36ruopQ8Pz_Pu7nnxGFxJ8qFP==HaQh8ww@mail.gmail.com> |
--===============3251008358743621631== Content-Type: multipart/alternative; boundary="000000000000adba0305c0d1c851" --000000000000adba0305c0d1c851 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Apr 25, 2021 at 9:43 AM Ralf Mardorf <[email protected]> wrote: > On Sun, 25 Apr 2021 08:36:42 -1000, robertlazarski wrote: > >it only showed midi connections in the qjackctl alsa pane, not the > >midi pane > > Hi, > > the MIDI tab is for jack MIDI and the ALSA tab is for ALSA MIDI. > Actually connecting to external MIDI hardware is done via ALSA MIDI. > Depending on the used setup, you need to bridge jack and ALSA MIDI. > Keyword "a2j_control", while it's not the one and only universal > keyword. However, there are a few questions, are you using jack1 or > jack2 and what version of jack1 or jack2? Even if you should be able to > connect all MIDI devices, MIDI jitter could be, but not necessarily be > another issue. And apart from this, if you should use several equal MIDI > devices, automatically connecting could become a PITA. While you can > make it possible to distinguish between several identical audio > devices, there's no way to do the same for MIDI devices. > > Your approach, as far as I understand or misunderstand it, is asking for > trouble. If it's impossible to use the > one_DAW/sequencer_only+plugins_approach, then at least try to > reconsider, if time code sync, let alone clock sync, is a reasonable > solution. > > The reply from Chris Caudle mentions another approach, that seemingly > doesn't fit to your needs. Maybe you should describe what you actually > want to archive, by describing the real scenario. > > Regards, > Ralf > > -- > =E2=80=9CAwards are merely the badges of mediocrity.=E2=80=9D > > =E2=80=95 Charles Ives > _______________________________________________ > Ardour-Users mailing list > [email protected] > To unsubscribe or change your mailing preferences please visit: > http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org > Thanks for the reply. Here's what I am trying to accomplish. I have a youtube channel that captures "live in the studio" multi camera performances that are synced with LTC. Nearly all of my gear is analog, even my sequencers. Up until now, my sequencers have run the entire track from start to finish. For my track in progress, I am using the Analogue Solutions Oberkorn for the main sequencer. After the intro and for the first verse only I want to start and then a few seconds later stop arguably the most ambitious hardware midi sequencer in history - the Genoqs Octopus. To start the track and finish the track I want to run a short sample. Midi start and stop on the Octopus as a slave requires a continuous midi clock to set BPM. Midi jitter and timing perfection isn't that important as the sequence is short. So I need a midi clock generator. And possibly several midi clock output connections, for future expansion. Ardour can handle the sample parts with oscsend via jltctrigger. I can run midi commands from jltctrigger. Getting a midi clock generated via jack is my current problem to overcome. Before I buy a midi interface, I am testing with Linux sequencers to see if they can be slaved to start/stop on the bpm from the jack_midi_clock project. I am using Jack2 1.9.12. I have been on OpenSuse since 2003 so that's my distro for now, on leap 15. The other approach suggested was a Python project - not one of my languages and it has no Jack support. Thanks! Robert --000000000000adba0305c0d1c851 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Sun, Apr 25, 2021 at 9:43 AM Ralf = Mardorf <<a href=3D"mailto:[email protected]">ralf.mardorf@alic= e-dsl.net</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style= =3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding= -left:1ex">On Sun, 25 Apr 2021 08:36:42 -1000, robertlazarski wrote:<br> >it only showed midi connections in the qjackctl alsa pane, not the<br> >midi pane<br> <br> Hi,<br> <br> the MIDI tab is for jack MIDI and the ALSA tab is for ALSA MIDI.<br> Actually connecting to external MIDI hardware is done via ALSA MIDI.<br> Depending on the used setup, you need to bridge jack and ALSA MIDI.<br> Keyword "a2j_control", while it's not the one and only univer= sal<br> keyword. However, there are a few questions, are you using jack1 or<br> jack2 and what version of jack1 or jack2? Even if you should be able to<br> connect all MIDI devices, MIDI jitter could be, but not necessarily be<br> another issue. And apart from this, if you should use several equal MIDI<br= > devices, automatically connecting could become a PITA. While you can<br> make it possible to distinguish between several identical audio<br> devices, there's no way to do the same for MIDI devices.<br> <br> Your approach, as far as I understand or misunderstand it, is asking for<br= > trouble. If it's impossible to use the<br> one_DAW/sequencer_only+plugins_approach, then at least try to<br> reconsider, if time code sync, let alone clock sync, is a reasonable<br> solution.<br> <br> The reply from Chris Caudle mentions another approach, that seemingly<br> doesn't fit to your needs. Maybe you should describe what you actually<= br> want to archive, by describing the real scenario.<br> <br> Regards,<br> Ralf<br> <br> -- <br> =E2=80=9CAwards are merely the badges of mediocrity.=E2=80=9D<br> <br> =E2=80=95 Charles Ives <br> _______________________________________________<br> Ardour-Users mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">ardour-u= [email protected]</a><br> To unsubscribe=C2=A0 or change your mailing preferences please visit:<br> <a href=3D"http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org" re= l=3D"noreferrer" target=3D"_blank">http://lists.ardour.org/listinfo.cgi/ard= our-users-ardour.org</a><br></blockquote><div><br></div><div>Thanks for the= reply. Here's what I am trying to accomplish. <br></div><div><br></div= ><div>I have a youtube channel that captures "live in the studio"= multi camera performances that are synced with LTC. Nearly all of my gear = is analog, even my sequencers. Up until now, my sequencers have run the ent= ire track from start to finish. <br></div><div><br></div><div>For my track = in progress, I am using the Analogue Solutions Oberkorn for the main sequen= cer. After the intro and for the first verse only I want to start and then = a few seconds later stop arguably the most ambitious hardware midi sequence= r in history - the Genoqs Octopus. To start the track and finish the track = I want to run a short sample.=C2=A0</div><div><br></div><div>Midi start and= stop on the Octopus as a slave requires a continuous midi clock to set BPM= . Midi jitter and timing perfection isn't that important as the sequenc= e is short. So I need a midi clock generator. And possibly several midi clo= ck output connections, for future expansion.=C2=A0</div><div><br></div><div= >Ardour can handle the sample parts with oscsend via jltctrigger. I can run= midi commands from jltctrigger. Getting a midi clock generated via jack is= my current problem to overcome. Before I buy a midi interface, I am testin= g with Linux sequencers to see if they can be slaved to start/stop on the b= pm from the jack_midi_clock project. <br></div><div><br></div><div>I am usi= ng Jack2 1.9.12. I have been on OpenSuse since 2003 so that's my distro= for now, on leap 15. The other approach suggested was a Python project - n= ot one of my languages and it has no Jack support.=C2=A0 <br></div><div><br= ></div><div>Thanks! <br></div><div>Robert<br></div></div></div> --000000000000adba0305c0d1c851-- --===============3251008358743621631== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ardour-Users mailing list [email protected] To unsubscribe or change your mailing preferences please visit: http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org --===============3251008358743621631==--