Re: [Rosegarden-user] a few newbie questions

2017-08-03 Thread Yves Guillemot
Le samedi 29 juillet 2017, 04:33:19 CEST Andrew Kilpatrick a écrit :
>
> - Audio clips don't start when the transport is rewound and then
> played... it is necessary to press play and then rewind.
> 

Should be fixed in last SVN (rev. 15039).

Yves



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-08-03 Thread Lorenzo Sutton

Hi,

I'm no expert on external MIDI devices (for playback - I use them only 
for input) but I'll skip to your more use-oriented question...


On 29/07/17 04:33, Andrew Kilpatrick wrote:

- Audio clips don't start when the transport is rewound and then
played... it is necessary to press play and then rewind.

Overall I really want to like and use Rosegarden, but it seems very
fragile and so far just setting up a few MIDI and audio tracks and
configuring my studio's MIDI devices has led me to what seems like a
broken file which I can't load anymore.


I never used audio with Rosegarden, just MIDI. And I did a precise 
workflow choice related to how audio works in Linux. Having Jack (and 
Jack transport), it didn't make much sense to me to use Rosegarden for 
audio when I could use Ardour in parallel. I'm not bashing Rosegarden's 
audio features here, just reporting my personal view that Rosegarden is 
an excellent sequencer with fantastic notation support able to rival 
some of the commercial ones under some aspects.
It strength also lies in using Jack and some of its features. I was able 
to compose a feature film soundtrack with RG last year and sync it with 
the video through jack transport and the excellent xjadeo (jack 
transport-enabled video player).


Of course RG does have bugs and as 2020 approaches it would be nice to 
have e.g. Jack midi or LV2 and some UI updates (personally more the 
former than the latter as there are LV2 clients out there).


I have always thought that the 'unix philosophy' works well with linux 
audio as well, but today the trend seems to have all-in-one software. 
See Ardour introducing MIDI, which IMHO was unnecessary. If I could have 
my take on the rosegarden 'roadmap' audio would be low priority and 
would push on other 'midi'/jack features and improvements, but I can see 
this is not a very popular point of view


Well I see that was a bit more of an answer to your question, anyway my 
two cents as a relatively long-standing Rosegarden user (and strong 
estimator) ;)


Lorenzo.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-31 Thread Ted Felix

On 07/28/2017 10:33 PM, Andrew Kilpatrick wrote:
Well I discovered that the metronome must be set to a MIDI port of some 
kind before any MIDI clocks will be sent. That seems like a bug... what 
does MIDI clock have to do with metronome?


  The metronome code is responsible for generating MIDI clocks.  See 
MetronomeMapper::fillBuffer().  Also search on MIDI_TIMING_CLOCK.


Ted.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-31 Thread Ted Felix

On 07/28/2017 10:33 PM, Andrew Kilpatrick wrote:
I 
tried using gdb to check a stacktrace but I don't think I'm familiar 
enough with the codebase to really know what's going on.


  Best thing to do is to open a bug report in the bug tracker:

https://sourceforge.net/p/rosegarden/bugs/

  Include the stack trace and a sample .rg file that causes trouble and 
we'll get on it as soon as we can.  I can usually get to something like 
this within a week.


Ted.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-29 Thread Yves Guillemot
Le samedi 29 juillet 2017, 04:33:19 CEST Andrew Kilpatrick a écrit :
> Well I discovered that the metronome must be set to a MIDI port of some
> kind before any MIDI clocks will be sent. That seems like a bug... what
> does MIDI clock have to do with metronome?
> 

I can't reproduce this: the metronome seems to be _always_ connected to some 
MIDI device.
Even if I define a device assigned to "No port" and connect the metronome to 
it I still see the MIDI clock.

How exactly are the MIDI devices and metronome configured when you get no 
clock?

> - Audio clips don't start when the transport is rewound and then
> played... it is necessary to press play and then rewind.

I confirm this issue.
Another way to get the sound is to press stop then press play again.
I'll create a bug ticket about it.

Yves



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-28 Thread D. Michael McIntyre

On 07/28/2017 10:33 PM, Andrew Kilpatrick wrote:

Well I discovered that the metronome must be set to a MIDI port of some 
kind before any MIDI clocks will be sent. That seems like a bug... what 
does MIDI clock have to do with metronome?


That definitely needs a look.

- Sometimes when starting rosegarden, it complains about a missing MIDI 
device (they are all there) and then segfaults.


I've been involved with the project for 15 years, and I've added, 
subtracted, and changed MIDI devices around thousands of times over the 
years.  I've never seen this cause a segfault.  Changing the MIDI 
landscape around doesn't even generate informational messages. 
Rosegarden just tries to hook things up like they were last time, and 
when it can't, you have to go diddle the connections manually.


Rosegarden complains about a missing audio server, and I think it warns 
you when no audio server means no synth plugins.


I have no doubt you're running into some issue, but I will be surprised 
if it turns out you're describing it accurately.  Pasting actual error 
messages would be useful, as would a stack trace of the segfault.


It then seems to load 
some kind of autosave file, but it doesn't have the last saved state of 
the actual file I want.


Going off memory here, I'm pretty sure it detects the presence of an 
autosave file, and offers you the option of loading that instead of 
loading the file off disk.  You should be able to load the last saved 
state or the autosave version, at your discretion.  That's how it's 
_supposed_ to work, but I haven't tested this lately, and it might be 
broken.


- Audio clips don't start when the transport is rewound and then 
played... it is necessary to press play and then rewind.


I haven't run into that, but frankly I don't use Rosegarden for audio 
anymore.  I got into recording drums with multiple microphones, and I 
switched to Windows for that.  What this says about Linux audio is 
probably pretty damning, but it is what it is.


Overall I really want to like and use Rosegarden, but it seems very 
fragile and so far just setting up a few MIDI and audio tracks and 
configuring my studio's MIDI devices has led me to what seems like a 
broken file which I can't load anymore.


Rosegarden is embarrassingly quirky and fragile to have been in 
development so long, but that has a lot to do with how the 
volunteer-driven development model works.  People come and go, people 
work in fits and spurts, people work off of different ideas for how 
things ought to be, and project leadership can't be too strict without 
running off all the volunteers.  The result is something very organic, 
like a home-grown apple that tastes pretty good when you ignore the worm 
tracks and the superficial black blight on the peel.


On the bright side, when Rosegarden does manage to mangle a file, we can 
usually hack on it by hand to get it working again.  The storage format 
is gzip compressed XML, and it's often a matter of just deleting one 
errant tag or something.  If you pass me a copy of the file, I'll be 
happy to have a look and see if I can hack it back into behaving itself.


I haven't experienced a truly serious loss of work in quite a few years.

Are people actually using this successfully with multiple external MIDI 
devices?


Yes.

 Is there any way to debug things when a file doesn't load? I
tried using gdb to check a stacktrace but I don't think I'm familiar 
enough with the codebase to really know what's going on.


In this area, I know how to do more than I can explain how to do.  It's 
easiest just to let someone with more experience have a go with the file.


The UI of rosegarden is as close to my dream app as I can imagine... 
simple, great notation editing, audio and MIDI recording... but if I'm 
worried that I won't be able to reload the file I'm working on, it's 
unfortunately not that useful. :(


I think this is mostly growing pains.  Rosegarden is definitely quirky, 
and will occasionally have serious glitches, but again, I haven't 
experienced a truly serious loss of work in quite a few years.  Almost 
everything that goes wrong is recoverable, but learning how to speak 
those incantations probably qualifies as some kind of black art.


It ain't perfect, but for no-cost software it's worth ten times the price!
--
D. Michael McIntyre

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-28 Thread Andrew Kilpatrick
Well I discovered that the metronome must be set to a MIDI port of some 
kind before any MIDI clocks will be sent. That seems like a bug... what 
does MIDI clock have to do with metronome?


A few other things:

- Sometimes when starting rosegarden, it complains about a missing MIDI 
device (they are all there) and then segfaults. It then seems to load 
some kind of autosave file, but it doesn't have the last saved state of 
the actual file I want.


- Audio clips don't start when the transport is rewound and then 
played... it is necessary to press play and then rewind.


Overall I really want to like and use Rosegarden, but it seems very 
fragile and so far just setting up a few MIDI and audio tracks and 
configuring my studio's MIDI devices has led me to what seems like a 
broken file which I can't load anymore.


Are people actually using this successfully with multiple external MIDI 
devices? Is there any way to debug things when a file doesn't load? I 
tried using gdb to check a stacktrace but I don't think I'm familiar 
enough with the codebase to really know what's going on.


The UI of rosegarden is as close to my dream app as I can imagine... 
simple, great notation editing, audio and MIDI recording... but if I'm 
worried that I won't be able to reload the file I'm working on, it's 
unfortunately not that useful. :(



Cheers,

Andrew

On 2017-07-26 04:54 PM, Yves Guillemot wrote:

Le mercredi 26 juillet 2017, 19:22:38 CEST Andrew Kilpatrick a écrit :


Thanks for the info. I checked aconnect and sync out seems to be
connected to every MIDI device, even ones that are not set up in
rosegarden. (my sound interface has a port which I don't use... it's
assigned)

But when I start and stop I can see that a port sends START, Song
Position, and STOP, but never sends any ticks. I viewed the data with
MIDI-OX on another computer.


Are you sure MIDI-OX is not filtering out the ticks which are generally hiding
the useful data the monitor is recording ?

Here is the output of RG seen by a tiny MIDI monitor coming as a test of the
RtMidi API ( https://www.openhub.net/p/rtmidi ) and which can be easily
compiled (I'm currently unable to compile Kmidimon on my new computer :-( ).

$ ./cmidiin

Would you like to open a virtual input port? [y/N] y

Reading MIDI input ... press  to quit.
Byte 0 = 192, Byte 1 = 0, stamp = 0
Byte 0 = 176, Byte 1 = 121, Byte 2 = 0, stamp = 2.4e-05
Byte 0 = 176, Byte 1 = 10, Byte 2 = 64, stamp = 4e-06
Byte 0 = 176, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 176, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 176, Byte 1 = 91, Byte 2 = 0, stamp = 4e-06
Byte 0 = 193, Byte 1 = 0, stamp = 3e-06
Byte 0 = 177, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 177, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 177, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 177, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 177, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 194, Byte 1 = 0, stamp = 3e-06
Byte 0 = 178, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 178, Byte 1 = 10, Byte 2 = 64, stamp = 4e-06
Byte 0 = 178, Byte 1 = 93, Byte 2 = 0, stamp = 2e-06
Byte 0 = 178, Byte 1 = 7, Byte 2 = 100, stamp = 4e-06
Byte 0 = 178, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 195, Byte 1 = 0, stamp = 5e-06
Byte 0 = 179, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 179, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 179, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 179, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 179, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 196, Byte 1 = 0, stamp = 3e-06
Byte 0 = 180, Byte 1 = 121, Byte 2 = 0, stamp = 2.7e-05
Byte 0 = 180, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 180, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 180, Byte 1 = 7, Byte 2 = 100, stamp = 4e-06
Byte 0 = 180, Byte 1 = 91, Byte 2 = 0, stamp = 4e-06
Byte 0 = 197, Byte 1 = 0, stamp = 3e-06
Byte 0 = 181, Byte 1 = 121, Byte 2 = 0, stamp = 4e-06
Byte 0 = 181, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 181, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 181, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 181, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 198, Byte 1 = 0, stamp = 3e-06
Byte 0 = 182, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 182, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 182, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 182, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 182, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 199, Byte 1 = 0, stamp = 4e-06
Byte 0 = 183, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 183, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 183, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 183, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 183, Byte 1 = 91, Byte 2 = 0, stamp = 4e-06
Byte 0 = 200, Byte 1 = 0, stamp = 3e-06
Byte 0 = 184, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 184, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 184, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 184,

Re: [Rosegarden-user] a few newbie questions

2017-07-27 Thread Andrew Kilpatrick

Hi Yves,

Yeah, it's very strange. I do a lot of MIDI hardware development, so I'm 
99% sure that I'm receiving all the messages. They are definitely not 
coming through. Maybe there is something else wrong with my setup.


Also, an unrelated problem I noticed that when playing back a project 
with audio tracks, they don't playback if I just press Play. I have to 
press Play and then Rewind (while playing) for them to actually be heard.



Cheers,

Andrew

On 2017-07-26 04:54 PM, Yves Guillemot wrote:

Le mercredi 26 juillet 2017, 19:22:38 CEST Andrew Kilpatrick a écrit :


Thanks for the info. I checked aconnect and sync out seems to be
connected to every MIDI device, even ones that are not set up in
rosegarden. (my sound interface has a port which I don't use... it's
assigned)

But when I start and stop I can see that a port sends START, Song
Position, and STOP, but never sends any ticks. I viewed the data with
MIDI-OX on another computer.


Are you sure MIDI-OX is not filtering out the ticks which are generally hiding
the useful data the monitor is recording ?

Here is the output of RG seen by a tiny MIDI monitor coming as a test of the
RtMidi API ( https://www.openhub.net/p/rtmidi ) and which can be easily
compiled (I'm currently unable to compile Kmidimon on my new computer :-( ).

$ ./cmidiin

Would you like to open a virtual input port? [y/N] y

Reading MIDI input ... press  to quit.
Byte 0 = 192, Byte 1 = 0, stamp = 0
Byte 0 = 176, Byte 1 = 121, Byte 2 = 0, stamp = 2.4e-05
Byte 0 = 176, Byte 1 = 10, Byte 2 = 64, stamp = 4e-06
Byte 0 = 176, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 176, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 176, Byte 1 = 91, Byte 2 = 0, stamp = 4e-06
Byte 0 = 193, Byte 1 = 0, stamp = 3e-06
Byte 0 = 177, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 177, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 177, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 177, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 177, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 194, Byte 1 = 0, stamp = 3e-06
Byte 0 = 178, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 178, Byte 1 = 10, Byte 2 = 64, stamp = 4e-06
Byte 0 = 178, Byte 1 = 93, Byte 2 = 0, stamp = 2e-06
Byte 0 = 178, Byte 1 = 7, Byte 2 = 100, stamp = 4e-06
Byte 0 = 178, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 195, Byte 1 = 0, stamp = 5e-06
Byte 0 = 179, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 179, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 179, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 179, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 179, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 196, Byte 1 = 0, stamp = 3e-06
Byte 0 = 180, Byte 1 = 121, Byte 2 = 0, stamp = 2.7e-05
Byte 0 = 180, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 180, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 180, Byte 1 = 7, Byte 2 = 100, stamp = 4e-06
Byte 0 = 180, Byte 1 = 91, Byte 2 = 0, stamp = 4e-06
Byte 0 = 197, Byte 1 = 0, stamp = 3e-06
Byte 0 = 181, Byte 1 = 121, Byte 2 = 0, stamp = 4e-06
Byte 0 = 181, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 181, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 181, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 181, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 198, Byte 1 = 0, stamp = 3e-06
Byte 0 = 182, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 182, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 182, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 182, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 182, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 199, Byte 1 = 0, stamp = 4e-06
Byte 0 = 183, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 183, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 183, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 183, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 183, Byte 1 = 91, Byte 2 = 0, stamp = 4e-06
Byte 0 = 200, Byte 1 = 0, stamp = 3e-06
Byte 0 = 184, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 184, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 184, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 184, Byte 1 = 7, Byte 2 = 100, stamp = 4e-06
Byte 0 = 184, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 201, Byte 1 = 0, stamp = 3e-06
Byte 0 = 185, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 185, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 185, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 185, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 185, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 202, Byte 1 = 0, stamp = 3e-06
Byte 0 = 186, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 186, Byte 1 = 10, Byte 2 = 64, stamp = 4e-06
Byte 0 = 186, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 186, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 186, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 203, Byte 1 = 0, stamp = 1.1e-05
Byte 0 = 187, Byte 1 = 121, Byte 2 = 0, stamp = 4e-06
Byte 0 = 187, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 187, Byte 1 = 93, Byte 2 = 0, stamp =

Re: [Rosegarden-user] a few newbie questions

2017-07-26 Thread Yves Guillemot
Le mercredi 26 juillet 2017, 19:22:38 CEST Andrew Kilpatrick a écrit :
> 
> Thanks for the info. I checked aconnect and sync out seems to be
> connected to every MIDI device, even ones that are not set up in
> rosegarden. (my sound interface has a port which I don't use... it's
> assigned)
> 
> But when I start and stop I can see that a port sends START, Song
> Position, and STOP, but never sends any ticks. I viewed the data with
> MIDI-OX on another computer.

Are you sure MIDI-OX is not filtering out the ticks which are generally hiding 
the useful data the monitor is recording ?

Here is the output of RG seen by a tiny MIDI monitor coming as a test of the 
RtMidi API ( https://www.openhub.net/p/rtmidi ) and which can be easily 
compiled (I'm currently unable to compile Kmidimon on my new computer :-( ).

$ ./cmidiin

Would you like to open a virtual input port? [y/N] y

Reading MIDI input ... press  to quit.
Byte 0 = 192, Byte 1 = 0, stamp = 0
Byte 0 = 176, Byte 1 = 121, Byte 2 = 0, stamp = 2.4e-05
Byte 0 = 176, Byte 1 = 10, Byte 2 = 64, stamp = 4e-06
Byte 0 = 176, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 176, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 176, Byte 1 = 91, Byte 2 = 0, stamp = 4e-06
Byte 0 = 193, Byte 1 = 0, stamp = 3e-06
Byte 0 = 177, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 177, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 177, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 177, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 177, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 194, Byte 1 = 0, stamp = 3e-06
Byte 0 = 178, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 178, Byte 1 = 10, Byte 2 = 64, stamp = 4e-06
Byte 0 = 178, Byte 1 = 93, Byte 2 = 0, stamp = 2e-06
Byte 0 = 178, Byte 1 = 7, Byte 2 = 100, stamp = 4e-06
Byte 0 = 178, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 195, Byte 1 = 0, stamp = 5e-06
Byte 0 = 179, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 179, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 179, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 179, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 179, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 196, Byte 1 = 0, stamp = 3e-06
Byte 0 = 180, Byte 1 = 121, Byte 2 = 0, stamp = 2.7e-05
Byte 0 = 180, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 180, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 180, Byte 1 = 7, Byte 2 = 100, stamp = 4e-06
Byte 0 = 180, Byte 1 = 91, Byte 2 = 0, stamp = 4e-06
Byte 0 = 197, Byte 1 = 0, stamp = 3e-06
Byte 0 = 181, Byte 1 = 121, Byte 2 = 0, stamp = 4e-06
Byte 0 = 181, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 181, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 181, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 181, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 198, Byte 1 = 0, stamp = 3e-06
Byte 0 = 182, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 182, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 182, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 182, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 182, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 199, Byte 1 = 0, stamp = 4e-06
Byte 0 = 183, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 183, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 183, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 183, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 183, Byte 1 = 91, Byte 2 = 0, stamp = 4e-06
Byte 0 = 200, Byte 1 = 0, stamp = 3e-06
Byte 0 = 184, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 184, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 184, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 184, Byte 1 = 7, Byte 2 = 100, stamp = 4e-06
Byte 0 = 184, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 201, Byte 1 = 0, stamp = 3e-06
Byte 0 = 185, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 185, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 185, Byte 1 = 93, Byte 2 = 0, stamp = 4e-06
Byte 0 = 185, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 185, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 202, Byte 1 = 0, stamp = 3e-06
Byte 0 = 186, Byte 1 = 121, Byte 2 = 0, stamp = 3e-06
Byte 0 = 186, Byte 1 = 10, Byte 2 = 64, stamp = 4e-06
Byte 0 = 186, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 186, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 186, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 203, Byte 1 = 0, stamp = 1.1e-05
Byte 0 = 187, Byte 1 = 121, Byte 2 = 0, stamp = 4e-06
Byte 0 = 187, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 187, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 187, Byte 1 = 7, Byte 2 = 100, stamp = 4e-06
Byte 0 = 187, Byte 1 = 91, Byte 2 = 0, stamp = 3e-06
Byte 0 = 204, Byte 1 = 0, stamp = 3e-06
Byte 0 = 188, Byte 1 = 121, Byte 2 = 0, stamp = 4e-06
Byte 0 = 188, Byte 1 = 10, Byte 2 = 64, stamp = 3e-06
Byte 0 = 188, Byte 1 = 93, Byte 2 = 0, stamp = 3e-06
Byte 0 = 188, Byte 1 = 7, Byte 2 = 100, stamp = 3e-06
Byte 0 = 188, Byte 1 = 91, Byte 2 = 0, stamp = 4e-06
Byte 0 = 205, Byte 1 = 0, stamp = 3e-06
Byte 0 = 189, Byte 1 = 121, 

Re: [Rosegarden-user] a few newbie questions

2017-07-26 Thread D. Michael McIntyre

On 07/26/2017 01:22 PM, Andrew Kilpatrick wrote:

Are there any other kind of settings I need to make? It would also be 
nice if it wouldn't connect up non-related MIDI devices since I do other 
MIDI things on my computer which might be upset by receiving useless 
clock messages.


In your case, it would probably be better to connect things manually. 
I've always used QJackCtl to do MIDI assignments.  It shows up off the 
Connect button, the ALSA tab, if I recall correctly.


I'd like to back up what Ted said about the color scheme.  We used to 
use a stylesheet for this, which was user-editable in theory.  In 
practice, it cannot be overstated what a complete nightmare the 
stylesheet was.  I jumped at the chance to have that train wreck 
replaced with code.  This does mean changing the style requires getting 
waist deep in code now.


--
D. Michael McIntyre

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-26 Thread Andrew Kilpatrick

Hi Yves,

Thanks for the info. I checked aconnect and sync out seems to be 
connected to every MIDI device, even ones that are not set up in 
rosegarden. (my sound interface has a port which I don't use... it's 
assigned)


But when I start and stop I can see that a port sends START, Song 
Position, and STOP, but never sends any ticks. I viewed the data with 
MIDI-OX on another computer.


Are there any other kind of settings I need to make? It would also be 
nice if it wouldn't connect up non-related MIDI devices since I do other 
MIDI things on my computer which might be upset by receiving useless 
clock messages.



Cheers,

Andrew

On 2017-07-26 06:42 AM, Yves Guillemot wrote:

Le mercredi 26 juillet 2017, 05:30:03 CEST Andrew Kilpatrick a écrit :

I'm not seeing a "sync" port anywhere in the program or the docs. The
MIDI Sync tab has an option "Automatically connect sync output to all
devices in use" which I have checked. I assume this means that any MIDI
device in my project will get clocks, but that doesn't seem to be true.



aconnect utility shows the ports
(on my system, "sync out" is 128:1):

$ aconnect -i
client 0: 'System' [type=kernel]
0 'Timer   '
1 'Announce'
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 20: 'E-MU XMidi1X1' [type=kernel,card=1]
0 'E-MU XMidi1X1 MIDI 1'
client 128: 'rosegarden' [type=user,pid=9511]
1 'sync out'
2 'external controller'
3 'out 1 - General MIDI Device'


When "Automatically connect sync output to all devices in use" is checked,
aconnect -l shows "sync out" and "out 1" connected to the MIDI device "E-MU
XMidi1X1":

$ aconnect -l
client 0: 'System' [type=kernel]
0 'Timer   '
1 'Announce'
Connecting To: 128:0
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 20: 'E-MU XMidi1X1' [type=kernel,card=1]
0 'E-MU XMidi1X1 MIDI 1'
Connecting To: 128:0
Connected From: 128:3, 128:1
client 128: 'rosegarden' [type=user,pid=9511]
0 'record in   '
Connected From: 0:1, 20:0
1 'sync out'
Connecting To: 20:0
2 'external controller'
3 'out 1 - General MIDI Device'
Connecting To: 20:0

When I start the Rosegarden transport (the play button) without any
composition loaded (ie no note sent to the output) the clock is sent to the E-
MU XMidi1X1 and I see its "out" LED blinking fastly.

Yves



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-26 Thread Ted Felix

On 07/26/2017 06:42 AM, Yves Guillemot wrote:

When I start the Rosegarden transport (the play button) without any
composition loaded (ie no note sent to the output) the clock is sent to the E-
MU XMidi1X1 and I see its "out" LED blinking fastly.


  Also, I see "SYS MESSAGE" in the "out" section of the transport. 
That's the clocks going out.


Ted.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-26 Thread Yves Guillemot
Le mercredi 26 juillet 2017, 05:30:03 CEST Andrew Kilpatrick a écrit :
> I'm not seeing a "sync" port anywhere in the program or the docs. The
> MIDI Sync tab has an option "Automatically connect sync output to all
> devices in use" which I have checked. I assume this means that any MIDI
> device in my project will get clocks, but that doesn't seem to be true.
> 

aconnect utility shows the ports
(on my system, "sync out" is 128:1):

$ aconnect -i
client 0: 'System' [type=kernel]
0 'Timer   '
1 'Announce'
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 20: 'E-MU XMidi1X1' [type=kernel,card=1]
0 'E-MU XMidi1X1 MIDI 1'
client 128: 'rosegarden' [type=user,pid=9511]
1 'sync out'
2 'external controller'
3 'out 1 - General MIDI Device'


When "Automatically connect sync output to all devices in use" is checked, 
aconnect -l shows "sync out" and "out 1" connected to the MIDI device "E-MU 
XMidi1X1":

$ aconnect -l
client 0: 'System' [type=kernel]
0 'Timer   '
1 'Announce'
Connecting To: 128:0
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 20: 'E-MU XMidi1X1' [type=kernel,card=1]
0 'E-MU XMidi1X1 MIDI 1'
Connecting To: 128:0
Connected From: 128:3, 128:1
client 128: 'rosegarden' [type=user,pid=9511]
0 'record in   '
Connected From: 0:1, 20:0
1 'sync out'
Connecting To: 20:0
2 'external controller'
3 'out 1 - General MIDI Device'
Connecting To: 20:0

When I start the Rosegarden transport (the play button) without any 
composition loaded (ie no note sent to the output) the clock is sent to the E-
MU XMidi1X1 and I see its "out" LED blinking fastly.

Yves



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-25 Thread Andrew Kilpatrick

Thanks for the responses!

On 2017-07-25 10:11 PM, Ted Felix wrote:

  I think the clock sync goes out the Rosegarden "sync" port.  You'll
need to manually connect that to something.  It's not configurable via
the Device Manager.  I usually use patchage to connect things up.  It
crashes a lot, but it gets the job done.


I'm not seeing a "sync" port anywhere in the program or the docs. The 
MIDI Sync tab has an option "Automatically connect sync output to all 
devices in use" which I have checked. I assume this means that any MIDI 
device in my project will get clocks, but that doesn't seem to be true.


Out of curiosity I checked the Rosegarden config file but it doesn't 
seem to have any mention of a specific port.




Andrew

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-25 Thread Ted Felix

On 07/25/2017 06:05 PM, Andrew Kilpatrick wrote:
1. MIDI clock sending - I turned it on in the MIDI Sync panel but no 
clock ticks are sent during playback. I could find no mention of this in 
the manual.


  I think the clock sync goes out the Rosegarden "sync" port.  You'll 
need to manually connect that to something.  It's not configurable via 
the Device Manager.  I usually use patchage to connect things up.  It 
crashes a lot, but it gets the job done.


3. Themes? I like the simple UI, but the colours are a bit bright for my 
dark studio. Is there a pref file I can modify to tone things down a bit?


  Our current style is implemented in code.  I don't think there is a 
simple way to tweak the colors.


Ted.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] a few newbie questions

2017-07-25 Thread Abrolag via Rosegarden-user
On Tue, 25 Jul 2017 18:05:13 -0400
Andrew Kilpatrick  wrote:

> Hi folks,
> 
> I'm trying to get familiar with Rosegarden but can't figure out a few 
> things. If someone can help out that would be great! I'm running 17.04 
> on Linux Mint - built from source.
> 
> 1. MIDI clock sending - I turned it on in the MIDI Sync panel but no 
> clock ticks are sent during playback. I could find no mention of this in 
> the manual.
> 
> 2. WAV file location - I would like to keep WAV files with my project 
> somehow but they go into the $HOME/rosegarden directory. How can I 
> change this?

There's probably a 'proper' way to do this, but I just close Rosegarden, then
move all the files into the dsame directory as the .rg file. Next time you open
it seems to find them OK, and also then saves any future files there.

> 3. Themes? I like the simple UI, but the colours are a bit bright for my 
> dark studio. Is there a pref file I can modify to tone things down a bit?
> 
> So far I really love this program... the notation editor and strong 
> support for hardware MIDI are awesome!
> 
> 
> 
> Cheers,
> 
> Andrew
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Rosegarden-user mailing list
> Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user


-- 
W J G

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user