Re: [Rosegarden-user] Serious MIDI recording problem -fixed - ish!

2012-12-15 Thread Abrolag
A bit of a ramble here - stay with me guys :) Last week, I screwed up an update on my 'office' machine so badly that the only sensible option was a re-install. However, because of the problems I've been having I decided to install Squeeze, instead of Wheezy. For Rosegarden I got the 13164 svn,

Re: [Rosegarden-user] Serious MIDI recording problem

2012-12-05 Thread Abrolag
On Mon, 03 Dec 2012 21:30:04 -0500 D. Michael McIntyre rosegarden.trumpe...@gmail.com wrote: I can't reproduce it. MIDI routes thru normally here. I think it's doing the same here too. Test situation: MIDI keyboard - Edirol UM-2 - ALSA - Rosegarden - ALSA - Edirol UM-2 - MIDI synth

Re: [Rosegarden-user] Serious MIDI recording problem

2012-12-05 Thread D. Michael McIntyre
On 12/05/2012 01:40 PM, Abrolag wrote: Also, I now have to use ./configure --with-qtlibdir /usr/lib/x86_64-linux-gnu I never needed to do that before, so that suggests something is quite wrong. I think pretty much everybody on a 64-bit system has to specify the path manually now, including

Re: [Rosegarden-user] Serious MIDI recording problem

2012-11-25 Thread D. Michael McIntyre
On 11/18/2012 01:01 PM, Abrolag wrote: When an external MIDI source is feeding into Rosegarden, Such as routing something like pmidi into Rosegarden? the incoming events are shown in the transport window, and if the transport is running on record the material is correctly laid down, but

[Rosegarden-user] Serious MIDI recording problem

2012-11-18 Thread Abrolag
This occurs with git builds 12920 13099 It doesn't occur with 12726 or earlier. When an external MIDI source is feeding into Rosegarden, the incoming events are shown in the transport window, and if the transport is running on record the material is correctly laid down, but the MIDI messages