On Wed, Mar 25, 2009 at 6:32 PM, alex stone <compos...@gmail.com> wrote:
>
>
> On Wed, Mar 25, 2009 at 6:21 PM, Chris Cannam <
> can...@all-day-breakfast.com> wrote:
>
>> On Wed, Mar 25, 2009 at 2:51 PM, alex stone <compos...@gmail.com> wrote:
>> > Going forward, i think Julie also has it right with an inbuilt synth for
>> > those who want to plug and play.
>>
>> Right, it would certainly be nice to have a synth (perhaps a plugin
>> setup) available out of the box. That's a somewhat bigger problem
>> though, and I'm not sure it would be so nice to be forced to solve
>> that one as well before the next release.
>>
>> Well, perhaps it would. But let's assume not, for now.
>>
>> In the meantime it would be good to improve the situation with MIDI
>> connections for everyone, and I don't think it's all that reasonable
>> to make it impossible to get any sound out of Rosegarden on first run
>> without going to the MIDI device manager dialog. That seems like sort
>> of a reductio ad absurdam of the current situation ("it's effectively
>> impossible, so let's simplify it by making it actually impossible").
>> It should _at least_ be possible to select an output in the main
>> window, and if you do have a perfectly good synth already running,
>> Rosegarden should use that.
>>
>> But that doesn't have to have any bearing on the question of how well
>> Rosegarden remembers your carefully configured composition settings
>> when you reload a composition. I suppose what I'm suggesting is that
>> we separate "what we do when you first run with an empty composition"
>> from "what you do when loading your own composition" (or even "when
>> loading your own saved studio").
>>
>> Incidentally, don't forget that even re-connecting your saved
>> connections from your composition is not an exact science. Just
>> because the same synths are running now as were running then, doesn't
>> mean they'll have the same client numbers or that we'll necessarily be
>> able to distinguish between them by name. Though we can do a lot
>> better than we do now (by not mixing up random other auto-connections
>> with restored ones).
>>
>>
>> Chris
>>
>
> Yes, i guess what i'm saying is, get the other connections out of the
> picture, unless specifically called for by the user. Surely that gives us a
> better chance of repeating a connection profile for a saved project, or
> indeed the default studio(s).
>
> Even first time users will become 2nd time users, etc, and like any app,
> they'll find they're way around RG, read the fine manual, and explore
> options. The first time user's experience is important, but so is continuity
> for regular users.
>
>
> Alex
>
> --
> Parchment Studios (It started as a joke...)
>
That should be "their" way around.........
Unforgivable.
--
Parchment Studios (It started as a joke...)
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
