Re: [Rosegarden-devel] Some ideas (based on my own designs)

[Pedro Lopez-C. <ped...@gm...>]

Hi,

On Saturday, 3 June 2006 04:32, mai...@si... 
wrote:

> Hi :)
>
> I haven't used Rosegarden before, but having looked at the screenshots it
> looks pretty much like what I'm looking for.
>
> But I'm not here to talk about how to use it, etc. - I just would like to
> share a few ideas I had for a project of my own, and maybe I'll be able to
> build my dream sequencer upon Rosegarden?

There is people using Rosegarden as a sequencer framework. It has been used at 
least for one big project based on its code base (Rosegarden Codicil):
http://markov.music.gla.ac.uk/CMT/cmt.py/Projects/rgtracker.html
It is also part of the Rosegarden Subversion repository:
http://www.rosegardenmusic.com/getting/

Rosegarden is GPL licensed. It is free software, which means that you can use 
it as is, or modify it to fit your needs. You can also redistribute your  
modified version, according to the GPL license.

> It's pretty much a case of being able to edit things quickly and easily.
> I've used Cubase before and found it to be one of the most ugliest,
> disorganised programs I've ever used.

I agree. I use Rosegarden instead of another MIDI sequencer project existing 
on Linux, precisely because it looks and feels like Cubase.

> So I tried to invent my own solution 
> - which I've done so, with partial success. I just haven't coded it yet.
>
> Part of the idea is to have the arrangement, possibly organised into
> groups (tracks of which may all have the same assigned channel - eg: kick
> drum on separate track to snare), 

This concept is named an "Instrument" in Rosegarden. Several tracks may share 
the same Instrument, which means that each track will be played by the same 
device, with the same channel, bank and program change, among other 
parameters. If you change any parameter for one Instrument, it takes effect 
for all the tracks sharing the same Instrument.

> with some form of graphical 
> representation of the data each segment/part contains.

Rosegarden has two graphical views for editing segments: 
- Matrix view: it is like a piano roll, and it has also a drum flavor. 
- Notation view: staffs on the score.

There is another text view: the event list.

> This is all pretty much standard stuff so far.
>
> But the main idea is to have an area underneath the tracks, where you can
> edit a segment/part without having to open another window. This may seem
> pointless but my main gripe with Cubase is the way the windows overlap and
> you can end up with loads of different parts open in different windows.
> Ditto with VST instruments/effects.

The Event Rulers work like that: an area under the main Matrix and Notation 
views, to graphically edit Controller and Pitch Bend events, or Note Velocity 
values. I think you could do the same for the main window, embedding a little 
Notation or Matrix view under the track list. I like the idea. Of course, you 
should do it optional, because existing users may want to use a full Matrix 
or Notation window.

> So, single click a segment/part and you see it underneath the arrangement,
> ready to edit. Click another segment/part and it updates to show the newly
> selected segment/part. Double-click to open a new window with the data in
> it.
>
> Different editors could be employed - eg: piano roll and waveform editor -
> depending on the type of track being edited.
>
> Each segment/part could have a "take" list, so you could record or create
> several versions of the same segment/part, and then come back later and
> pick the one you like best. A similar idea could be employed for sample
> recording (does Rosegarden support samples? I haven't looked into this
> yet.)

Yes. Rosegarden supports audio tracks, having digital audio data instead of  
MIDI events. There is not yet an internal waveform editor view for it, 
though.

> Finally, it'd be nice to have a "scrap" area, where you can drag
> segments/parts you're not sure of into, or segments/parts you like. You
> could build up a library of "scraps" to re-use in future songs. This would
> be similar (but quite different in practise) to the older versions of eJay
> (drag and drop music creation.)
>
> I'm keen to see something like this, and perhaps Rosegarden would be a
> suitable starting point?
>
> Would you guys be interested in this? Or would it be best I work on it as
> a completely separate project?
>
>Regards
>
>
>Andrew Greenwood

I am a simple contributor and user for this project, and I can't speak for 
other people, but I'm interested on your ideas.

Regards,
Pedro