Carlo Capocasa wrote:
One drawback: Sequence lengths cannot be
arbitrary, 1,2,4,8,16,32 or 64 bars. If this is a showstopper I would
recommend writing to the author (or starting a campaign for people to
write to the author) and ask for that.
Am i the only person who can set arbitrary sequence lengths in Seq24?
From 1 bar to 16 bars and then 32 and 64 bars.
For me it is in the drop down dialog next to the time signature selection.
This is running ubuntu edgy eft. and pretty sure it has been there the
entire time i have used the program.
Just my thoughts,
Chris
On 11/29/06, Cesare Marilungo <cesare(a)poeticstudios.com> wrote:
Cesare Marilungo wrote:
carmen wrote:
Puredata's strong point is not sequencing and notation,
sure but then neither is it the forte of linux audio software in
general. for sequencing i definitely dig Pd+Tk a lot more than eithe
seq24 or Dino, since youve got full access to the data for further
massaging/accessing in unconventional ways without being bound to a
clicky-clicky GTK workflow.. and arent bound to MIDI-enforced notions
of what is a track, what is a folder of tracks, what is a region, etc..
http://replic.net/~ix/pr/seq.png for note/part editing,
http://replic.net/~ix/pr/lg.gif for streaming control-data. just grab
/extensions/gui/ix/{mat,lg}.wid and [widget]..plug the xlets into
PDContainer, Pool, or the storage of your choice and get
editing...using del, metro, pipe, or what have you for playback..
Carmen, where is the [widget] external?
Can you provide some more instructions to install these awesome stuff?
Is there some documentation to extend or write my own widgets?
Thanks in advance,
c.
Ok. I've found [widget] in the miXed/toxy and installed everything
inside it. Pd should be started with -lib widget, right? Anything else
is needed? And how should I use your files?
c.
> so what
> I need is an application that I can send midi notes and controller
> data
> through, which will remember them and pass them on to Puredata
>
for this i like rradical-style figure-8 abstraction to timestamp
events and shuttle them onto storage - you can alligator-clip them
anywhere in a patch, instead of having to keep track of midiout's and
range remapping into/out-of midi and the subsequent resolution loss..
cheers,
c
--
http://www.cesaremarilungo.com