[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] Windows audio driver

From: alex stone
Subject: Re: [Denemo-devel] Windows audio driver
Date: Sun, 13 Dec 2009 13:10:30 +0000

Richard,  i see where you're going with this.

The user creates an "industrial grade" preference list of devices and
ports at a global level.
At project level, the user then picks and chooses which ports he
wishes to use per staff, and saves that project. The next time the
project is open it remembers which ports it wants and only uses those,
but at global level, all ports are "running" and available at all
times Denemo is open.

This is not a usual case in my experience (most daws require the user
to create and destroy ports per project), but  keeping an open mind, i
think i like your approach better. It would seem simpler to have all
ports running, and just cherry pick from that at the user's leisure.
The user can setup a global "template" of devices and ports, and
within reason, leave it alone after that, removing at least one layer
of donkey work. For fairly static orchestral setups, using a sampler,
like linuxsampler, where a global template is likely to be used
anyway, it would be fairly quick to add a staff, and assign a port,
with the instrument already loaded and ready to roll.

So you get my vote.
A smart idea, not only structurally, but from a workflow
administrative perspective as well.

Good thinking.


On Sun, Dec 13, 2009 at 12:31 PM, Richard Shann
<address@hidden> wrote:
> On Sun, 2009-12-13 at 09:53 +0000, alex stone wrote:
>> When i open denemo with an existing file (i.e. $ denemo
>> /home/alex/test1.denemo), the previously named and saved ports with
>> the project are renamed back to default
> there is no such thing as a denemo "project". The ports and devices are
> set up in preferences, which means that they belong to the user, not to
> any piece of music. Specifically they are not saved in a .denemo file.
> I think I detect a serious design flaw here - I looked back over the
> emails a couple of days ago to try and understand what you guys are
> trying to do with this stuff. The idea seemed to be that a set of
> "devices" and "ports" would be created by the user in his preferences.
> Then when the user created a piece of music he would associate a staff
> with some of the names he uses.
> These properties of a staff are (or should be) saved with the .denemo
> file.
> What you would like to happen if on loading a .denemo file a staff has a
> reference to a (device/port) that is not in the current prefs I don't
> know. And what jack calls are associated with a given set of prefs and
> when they should be made I don't know. And what jack calls are
> associated with any device/port thingy attached to a staff I don't know.
> Richard



reply via email to

[Prev in Thread] Current Thread [Next in Thread]