continuous note on a particular VVID. The sequencer only reuses a VVID once
it has ended any previous notes on that VVID. The sequencer can allocate a
This is the current issue at hand - just because the sequencer has ended a
VVID with a voice-off, doesn't mean the voice is off. It just
On Tue, Jan 07, 2003 at 03:21:22 +0100, David Olofson wrote:
Problem is step 1. If the voice allocator looks at velocity, it
won't work, since that information is not available when you do
the allocation. Likewise for setting up waveforms with velocity
maps and the like.
But in the
On Mon, Jan 06, 2003 at 11:17:07 +0100, David Olofson wrote:
These instantiation parameters are in fact just control events, and
they relate to whatever voice is assigned to the provided VVID.
The issue here is this: Where does control data go when there is no
voice assigned to the VVID?
ZynAddSubFX is a open-source software synthesizer for
Linux.
It is available at :
http://zynaddsubfx.sourceforge.net
or
http://sourceforge.net/projects/zynaddsubfx
news:
1.0.4 - It is possible to load Scala (.scl and .kbm)
files
- Added mapping from note number to scale degree
is
On Tuesday 07 January 2003 04.24, Tim Hockin wrote:
Two problems solved! (Well, almost... Still need temporary space
for the parameters, unless voice allocation is
non-conditional.)
I think if you get an allocate voice event, you MUST get a voice on
event.
Why? Isn't a voice on event
On Tuesday 07 January 2003 09.15, Tim Hockin wrote:
continuous note on a particular VVID. The sequencer only reuses a
VVID once it has ended any previous notes on that VVID. The
sequencer can allocate a
This is the current issue at hand - just because the sequencer has
ended a VVID with a
On Tuesday 07 January 2003 10.23, Steve Harris wrote:
On Mon, Jan 06, 2003 at 11:17:07 +0100, David Olofson wrote:
These instantiation parameters are in fact just control events,
and they relate to whatever voice is assigned to the provided
VVID.
The issue here is this: Where does
On Tue, Jan 07, 2003 at 01:41:43 +0100, David Olofson wrote:
Yeah, byt you may not want control values to be latched except when a
note is actually triggered (be it explicitly, or as a result of a
contro change). Also, this voice.set_voice_map() may have significant
cost, and it seems like
On Tuesday 07 January 2003 15.03, Steve Harris wrote:
[...]
It's just that there's a *big* difference between latching
control values when starting a note and being able to morph
while the note is played... I think it makes a lot of sense to
allow synths to do it either way.
I'm not
On Tue, Jan 07, 2003 at 03:38:05 +0100, David Olofson wrote:
It might seem handy to allow synths to explicitly say that some
controls *must* be rewritten at the instant of a VOICE_ON, but I
don't think it's useful (it's useless for continous velocity
instruments, at least) enough to
On Tuesday 07 January 2003 17.10, Steve Harris wrote:
[...]
OK... I was thinking that the initial mention of the VVID would
cause it creation (be that implicit or explict, though I prefer
explit I think), thereafter control changes would be applied the
the instantiated voice (or the NULL voice
ONe great thing about this scheme is that it encourages people not to
think of certain, arbitary parameters as instantiation parameters, withc
are special in some way, 'cos there not.
The way I've seen velocity-mapped samplers is not to change the sample later
- you get the sample that maps to
unsuscribe
I browsed the Kernel Source and there is only one mark_inode_dirty in
pipe_write (in fs/pipe.c). So we know where it is hanging...
And in __mark_inode_dirty (in fs/inode.c) there is one
spin_lock(inode_lock)
call, and I guess that is where the whole thing is hanging. So something
is
So I run that in a terminal and after playing around with a bunch of
jack apps got the machine to lockup... and then, after a little bit,
suddenly, it came back to life! (you could see that the monitor had
changed the priority of the hogs to SCHED_OTHER).
So I guess that somehow jack has a hard
So I run that in a terminal and after playing around with a bunch of
jack apps got the machine to lockup... and then, after a little bit,
suddenly, it came back to life! (you could see that the monitor had
changed the priority of the hogs to SCHED_OTHER).
So I guess that somehow jack has a
what do you want to know?
Ahem, everything? :-) ;-) :-)
recompile with DEBUG_ENABLED defined at the top of engine.c and then
if necessary client.c as well.
this will produce reams of output, but will provide you with the next
hint. problem: the output will affect scheduling, which might make
I made a post a while back defining all the XAP terminology to date. Read
it if you haven't - it is useful :)
I was hoping something of this sort existed. It would be very helpful if you
could put the list of XAP terminology on the webpage. It would help keep
everybody on the same page when
unsuscribe
19 matches
Mail list logo
