Re: [Lmuse-user] =?iso-8859-1?q?MusE_0=2E9pre1_-_Pbm_with_midi_cc_+?= =?iso-8859-1?q?=09sync=09observations?=

[Chris C. <ca...@al...>]

On Thursday 07 Dec 2006 16:39, Allan Klinbail wrote:
> It says it does but on it doesn't seem to be sending or receiving
> correctly from external devices.
>
> Correction of my previous post, in Rosegarden, only with the mtpav
> driver nothing happens on receiving.
>
> With the usb-audio driver it receives continue and stop but not start or
> positional sync from MMC/midi clock.  (i.e. pressing start on the
> external sequencer will not take the rosegarden transport back to the
> start (continue behaviour) and moving the transport on the external
> sequencer does not affect the rosegarden transport at all)
>
> MusE receives positional sync from both drivers but is ahead of the sync
> time sent from the external sequencer
>
>
> With sync out
> Rosegarden works as described below with the mtpav driver.
> With the usb-audio driver it only sends updated positional sync when
> pressing play. (not when the transport is moved on screen)
>
> With MusE, sync out appears to be reliable for both drivers.

I can't comment on the difference between the ALSA drivers, I'm afraid.  We 
just get our data from the ALSA sequencer.

Which version of Rosegarden is this?  While it's true that RG still won't 
follow transport repositions when slaving to anything other than MTC (which 
has long been our best bet for both master and slave), both of the other 
things you mention should work in current versions -- rewind on start when 
receiving system messages was fixed in 1.4.0, reposition on transport move 
when mastering MMC has been there since 1.2.4.

I guess you don't want to get bogged down in trying to debug another sequencer 
as well, but I'd like to know if you're using 1.4.0 and these things still 
don't work for you!


Chris