[linux-audio-user] Re: [MusE] Re: Syncing muse with ardour

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi ,

> I have also been testing sync scenarios with Ardour (CVS 14 June) +
> various apps. I've had success only with Hydrogen. I worked with MusE

hydrogen seems to understand only noteon/off, aka works as soft synth. 
That is what I could achieve so far in combination with muse. I never 
got control over hydrogen's transport :(

> (0.6.0pre5) for a while last night, nothing budged. I *thought* I had
> all connections designated: Ardour was set up for Send MTC and Send MMC,
> and MusE was set for external sync, recognizing MTC and MIDI clock. The
> Ardour sync output is the first virmidi port, so I used kaconnect to
> route virmidi 0 to MusE. The MusE console reports MMC stop and seek
> position signals for the Ardour playhead, but no start signal (should
> it?). Like I said, I got no sync joy. Audio is off in MusE, btw. Maybe
> I'm missing something obvious ??
> 

Exactly the same with my setup, see below...
...
> 
> I'm interested in learning about any successful sync arrangements, with
> or without external gear. What apps work well (or even sort of well)
> together via MMC, MTC, SMPTE, MIDI clock, or... ??
> 

Ok, the other way around works 'sort of well'... Muse is able to mmc 
ardour!
Here some pre-requisites, that I just found out:
1. Works only with newly created ardour sessions(1.0beta1-c), otherwise 
clicking 'MMC Control'  in ardour's options checkbox crashes ardour
2. ~/.ardour.rc uses a raw virtual midi interface provided by 
snd-virmidi. BTW, why doesn't ardour appear as send/receive midi 
interface in kaconnect?
3. the *same* virtual midi interface is configured as MIDI port in muse, 
and is configured under MIDI Sync as Master-MMC O-Port.

Though, transport is not reliably connected. Sometimes ardour seems to 
ignore the MMC sent by muse.

Regards

Martin

>>
>>On Wed, 2003-06-18 at 09:39, Martin Buechler wrote:
>>
>>>Hi at muse,
>>>
>>>  ardour-1.0 will not include a sequencer (AFAIK), and muse seems to be
>>>(I know, even more than) the complementary part to handle midi related
>>>recordings/overdubs. I thought, that all I would need is midi machine
>>>control with ardour as the master, muse as the slave.
>>>
>>>  What I tried was: Directing  ardour's - current is 1.0beta1-c - mmc to
>>>a virtual midi interface provided by the ALSA snd-virmidi module and
>>>driving muse as slave accepting mtc/midi clock/mmc with Id 127 and all
>>>ports.(Hmm, Whats the use of this Id anyway?)  Selecting ardour's MTC
>>>generation seems not to change the behaviour of muse/ardour. Selecting
>>>the third ardour MIDI option, which is called 'MMC Control' in ardour's
>>>options panel, crashes ardour instantly! That may be part of the
>>>problem, I guess...
>>>
>>>  Additionally, sync generation was turned off in muse. The transport
>>>grays out, and when I start ardour rolling, muse does exactly nothing.
>>>But, when I switch off/on the sync button in the transport panel of
>>>muse, then I am able to control stop/begin/end whithin ardour! Great,
>>>but it 's quite useless, when muse does not *start* with ardout, isn't it?
>>>
>>>Here's some output of muse -mMDs:
>>>
>>>ardour:
>>>->Goto end
>>>(another thing: the bar counts seems to be actually not the same in muse
>>>and ardour)
>>>--
>>>MidiInput: port:1 chan:193 port:1 chan:192 type:0xf0 a=8 b=0 data len 11
>>>mmcInput: n:11 06 44 06 01
>>>MMC: 156.560000 120238 seek 00:02:36:14:00
>>>MidiInput: port:1 chan:193 port:1 chan:192 type:0xf0 a=8 b=0 data len 4
>>>mmcInput: n:4 06 01 06 01
>>>   MMC: STOP
>>>--
>>>->Goto begin:
>>>--
>>>MidiInput: port:1 chan:122 port:1 chan:121 type:0xf0 a=8 b=0 data len 11
>>>mmcInput: n:11 06 44 06 01
>>>MMC: 0.000000 0 seek 00:00:00:00:00
>>>MidiInput: port:1 chan:122 port:1 chan:121 type:0xf0 a=8 b=0 data len 4
>>>mmcInput: n:4 06 01 06 01
>>>   MMC: STOP
>>>--
>>>
>>>-> Here I started ardour, but nothing happens..
>>>
>>>Stop:
>>>--
>>>MidiInput: port:1 chan:180 port:1 chan:179 type:0xf0 a=8 b=0 data len 4
>>>mmcInput: n:4 06 01 00 00
>>>   MMC: STOP
>>>--
>>>
>>>How did you get syncing done, maybe even with ardour? Do I expect too much?
>>>
>>>Thanks for reading.
>>>
>>>Martin
>>>





[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux