Rosegarden

On Wednesday 04 November 2009, cjnfryer@... wrote:

> All rulers appear misligned to me in the Notation View. Maybe that's just
>  me!

Seems broadly OK to me, but I got sidetracked while trying to look at this.  I 
happened to pick a file with lots of parts and open a multi-staff view.  I 
have lots of staffs here, and I have no idea which staff's velocity ruler I'm 
looking at.  Either the velocity ruler should always show velocity for the 
active segment (and by extension, staff) or I should be able to open one 
velocity ruler per segment, in which case it would be helpful if I knew which 
one was which.

Currently, hitting the "show velocity ruler" button a second time toggles the 
ruler off, but that's not necessarily what I want to do in this situation.

I suppose now that there's a multi-segment matrix, the matrix faces the same 
problems.  We should sort all of this out and figure out what we want to do.  
The same thing will apply to control rulers too, because they actually work 
per instrument.  Note that "per instrument" is more complicated than per 
track, because there might be 2 or 6 or 42 tracks all using the same 
instrument, so these controllers...

Ugh.  Kind of hearkens back to what Emmanuel was bitching about the other day, 
really.  Events for the controllers are stored in segments.  Segments are 
portable.  What happens if you have controllers set up for your Ubitron 3000 
in a segment and you move it to a new track?  Although now that I start to 
chew on that a little bit, I quickly realize I need to slam that door shut and 
run away, because there is no sane solution to that one unless maybe it 
involves blowing up a big chunk of our foundation and starting over again, 
which ain't happenin' at this juncture.

Um.  Anyway, I'm getting all sidetracked up again.  Bottom line, I can see 
arguing that if there are multiple segments, declining to show any property or 
control rulers might be an acceptable solution, although when I think about 
it, I don't think it would be strictly necessary, and it's probably workable 
to have "Velocity - Violin I" on the tab or something.  Especially for 
velocity.  Control rulers are vastly more evil.

Well, let me stop digressing before I digress again.

-- 
D. Michael McIntyre

Bump.

Michael, is there a problem with this patch I'm not aware of, or it's
just being overseen?

Vlada

Vladimir Savic wrote:
> Here we go again... Improved patch!
> 
> Still I need to figure out how to create new devices from lscp file
> (similar to what importing .rg files does).
> 
> Feature request:
> Bank manager sorting isn't that great now. Bank 10 doesn't come up after
> Bank 1 in real world. Bank 2 does!
> 
> 
> Vlada
>

2009/11/3 D. Michael McIntyre <michael.mcintyre@...>:
>
> Incidentally, while we are on the topic of audio features and audio projects,
> have you tried the new project packager I rewrote from scratch?  The .rgp
> format *is* a more or less workable thing, I think.  The new packager is not a
> clone of the original, but rather 100% compatible with old files, using all
> new code and an all new thought process for handling everything.  Now that
> it's integrated real code instead of some tacked on script, it may be worth
> thinking about more ways to integrate it into audio-related plans.
>

Looks like it is creating an archive, with any possible content?
Or does wavpack support *.wav only,  not mp3,flac,.. ?
A good idea, to pack the audio files with the rg-file into such package.
*.rgp could be used as default format for files containing audio or
other content (cover-art,..)
I don't know how wavpack compares to say bzip2 or so.


-- 
E.R.