Hi All,
To find out if xeq, the sequencer package created by Krzysztof Czaja in 2006, is worth fixing, documenting and making a reliable deken package, I am looking for someone knowledgeable of and interested in sequencers.
Xeq is a sequencer suite inspired by the [qlist] object, but extended by several useful features, only very rudimentary described. At least it supports midi files, searching for note sequences in its dictionaries, and maybe even some sort of programming to control sequence parsing.
At the moment, xeq compiles but because of the very limited documentation; an outdated paper and a few poorly documented patches its usage range is unknown.
To some extend I can fix bugs when it is clear what the proper behaviour is, but my knowledge of advanced sequencer usage is too limited to find out how it should work. This also limits my capability to create useful help-patches. So I am seeking help from someone with more than average knowledge of sequencers.
I am aware that software can be too complicated to be useful, so at one point the conclusion could be that xeq is not worth the effort to document and debug it. But so far the framework looks well structured, and some of the charted functionality is working very well.
For testing the source is available at https://github.com/electrickery/pd-xeq/tree/experimentalReconstruction, but I can provide a deken like zip with an executable and available documentation for all the usual platforms. No stabilility is guaranteed, but it sure it will be 'interesting' (if you like sequencers ;-).
Fred Jan
I wonder, was this ever on extended or used by anyone here? Curious to hear more about its features.
we got a couple of sequencers on the list but recently joão was complaining about their limitations. Is it multitrack?
a powerful sequencer is always helpful and welcome... (perhaps recycle it into a new object under a new name if it turns out to be too crazy)
cheers
2016-10-21 18:30 GMT-02:00 Fred Jan Kraan fjkraan@xs4all.nl:
Hi All,
To find out if xeq, the sequencer package created by Krzysztof Czaja in 2006, is worth fixing, documenting and making a reliable deken package, I am looking for someone knowledgeable of and interested in sequencers.
Xeq is a sequencer suite inspired by the [qlist] object, but extended by several useful features, only very rudimentary described. At least it supports midi files, searching for note sequences in its dictionaries, and maybe even some sort of programming to control sequence parsing.
At the moment, xeq compiles but because of the very limited documentation; an outdated paper and a few poorly documented patches its usage range is unknown.
To some extend I can fix bugs when it is clear what the proper behaviour is, but my knowledge of advanced sequencer usage is too limited to find out how it should work. This also limits my capability to create useful help-patches. So I am seeking help from someone with more than average knowledge of sequencers.
I am aware that software can be too complicated to be useful, so at one point the conclusion could be that xeq is not worth the effort to document and debug it. But so far the framework looks well structured, and some of the charted functionality is working very well.
For testing the source is available at https://github.com/electricker y/pd-xeq/tree/experimentalReconstruction, but I can provide a deken like zip with an executable and available documentation for all the usual platforms. No stabilility is guaranteed, but it sure it will be 'interesting' (if you like sequencers ;-).
Fred Jan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/li stinfo/pd-list
- Fred Jan Kraan fjkraan@xs4all.nl [2016-10-21 22:31]:
Hi All,
To find out if xeq, the sequencer package created by Krzysztof Czaja in 2006, is worth fixing, documenting and making a reliable deken package, I am looking for someone knowledgeable of and interested in sequencers.
Thank you for looking into this!
Xeq is a sequencer suite inspired by the [qlist] object, but extended by several useful features, only very rudimentary described. At least it supports midi files, searching for note sequences in its dictionaries, and maybe even some sort of programming to control sequence parsing.
You are most likely aware of this material, but Krzysztof gave a talk about it at the first Pd Convention in Graz 2004 http://puredata.info/community/conventions/convention04/lectures/tk_czaja/
P
hmm, it's got nothing to do with midi, right? oh...
2016-10-21 19:28 GMT-02:00 Peter P. peterparker@fastmail.com:
- Fred Jan Kraan fjkraan@xs4all.nl [2016-10-21 22:31]:
Hi All,
To find out if xeq, the sequencer package created by Krzysztof Czaja in 2006, is worth fixing, documenting and making a reliable deken package,
I am
looking for someone knowledgeable of and interested in sequencers.
Thank you for looking into this!
Xeq is a sequencer suite inspired by the [qlist] object, but extended by several useful features, only very rudimentary described. At least it supports midi files, searching for note sequences in its dictionaries,
and
maybe even some sort of programming to control sequence parsing.
You are most likely aware of this material, but Krzysztof gave a talk about it at the first Pd Convention in Graz 2004 http://puredata.info/community/conventions/convention04/lectures/tk_czaja/
P
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
hmm, it's got nothing to do with midi, right? oh...
haha, it looks like there's plenty of midi in there =). if i'm reading it correctly, it looks like it functions sort of like arrays? you bind a sequence to some global symbol and access it by passing that symbol.
I'd be interested in more sequencer options for pd so it'd be nice to have xeq or something like xeq available. i suppose i'm going off-track a little, but it'd be nice to have something supercolliderish with TempoClocks and Patterns where it's really easy to loop sequences, randomize specific bits of a sequence, etc. and have that all bound to a global transport (or two). A lot of the times I end up making my own hacky transport with metro and sends and receives for beginnings of bars, beats, etc and even then it's not the easiest to do say, quintuples when I've got my global metro going in 16ths...
I suppose xeq could potentially be revived with [text] compat since that seems to be the successor to [qlist]? it seems like [text] solves a lot of the issues xeq had with qlist, like global binding allowing multiple objects to traverse a text file...
Derek
Derek Kwan www.derekxkwan.com
On 22-10-16 06:11, Derek Kwan wrote:
hmm, it's got nothing to do with midi, right? oh...
haha, it looks like there's plenty of midi in there =). if i'm reading it correctly, it looks like it functions sort of like arrays? you bind a sequence to some global symbol and access it by passing that symbol.
This approach allows multiple clients ("friends" in xeq-speak) read a single server ("host") sequence.
I'd be interested in more sequencer options for pd so it'd be nice to have xeq or something like xeq available. i suppose i'm going off-track a little, but it'd be nice to have something supercolliderish with TempoClocks and Patterns where it's really easy to loop sequences,
It has tempo options and functions to find sequence patterns, but the proper patches to demonstrate are lacking...
randomize specific bits of a sequence, etc. and have that all bound to a global transport (or two). A lot of the times I end up making my own hacky transport with metro and sends and receives for beginnings of bars, beats, etc and even then it's not the easiest to do say, quintuples when I've got my global metro going in 16ths...
I suppose xeq could potentially be revived with [text] compat since that seems to be the successor to [qlist]? it seems like [text] solves a lot of the issues xeq had with qlist, like global binding allowing multiple objects to traverse a text file...
Xeq evolved from the original [qlist] format to something more powerful. But how powerful hes to be determined... At least it reads, plays and writes multi-track mid files. That part I happened to get working.
Derek
Greetings,
Fred Jan
On Sat, Oct 22, 2016 at 10:07:40AM +0200, Fred Jan Kraan wrote:
On 22-10-16 06:11, Derek Kwan wrote:
hmm, it's got nothing to do with midi, right? oh...
haha, it looks like there's plenty of midi in there =). if i'm reading it correctly, it looks like it functions sort of like arrays? you bind a sequence to some global symbol and access it by passing that symbol.
This approach allows multiple clients ("friends" in xeq-speak) read a single server ("host") sequence.
This very directly inspired my design for the "array" and "text" objects :)
Miller
On 10/22/2016 06:11 AM, Derek Kwan wrote:
haha, it looks like there's plenty of midi in there =). if i'm reading it correctly, it looks like it functions sort of like arrays? you bind a sequence to some global symbol and access it by passing that symbol.
almost: [array] functions sort of like [xeq].
iirc¹, miller was quite impressed by krzysztof's ideas to manage data in [xeq].
gfmasdr IOhannes
¹ of course i could equally well be totally mistaken.
m Freitag, 21. Oktober 2016, 22:30:40 CEST schrieb Fred Jan Kraan:
Hi All,
To find out if xeq, the sequencer package created by Krzysztof Czaja in 2006, is worth fixing, documenting and making a reliable deken package, I am looking for someone knowledgeable of and interested in sequencers.
I use xeq since, hmmm 2003 for my "Autoklavierspieler" [1] and preferred it to seq for the more flexible structure, playing in parallel und variable speed, positioning within midifiles and and accuracy and dont know any more why else. Using it in many installations now playing for years, especially the speaking piano pieces.
The problem was compile errors since 5 years made me to use my own version of the source, but not clean enough to release.
So I would be very pleased if you dekenize xeq.
mfg winfried
[1] http://algo.mur.at/projects/autoklavierspieler
Xeq is a sequencer suite inspired by the [qlist] object, but extended by several useful features, only very rudimentary described. At least it supports midi files, searching for note sequences in its dictionaries, and maybe even some sort of programming to control sequence parsing.
At the moment, xeq compiles but because of the very limited documentation; an outdated paper and a few poorly documented patches its usage range is unknown.
To some extend I can fix bugs when it is clear what the proper behaviour is, but my knowledge of advanced sequencer usage is too limited to find out how it should work. This also limits my capability to create useful help-patches. So I am seeking help from someone with more than average knowledge of sequencers.
I am aware that software can be too complicated to be useful, so at one point the conclusion could be that xeq is not worth the effort to document and debug it. But so far the framework looks well structured, and some of the charted functionality is working very well.
For testing the source is available at https://github.com/electrickery/pd-xeq/tree/experimentalReconstruction, but I can provide a deken like zip with an executable and available documentation for all the usual platforms. No stabilility is guaranteed, but it sure it will be 'interesting' (if you like sequencers ;-).
Fred Jan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 22-10-16 10:46, Winfried Ritsch wrote:
m Freitag, 21. Oktober 2016, 22:30:40 CEST schrieb Fred Jan Kraan:
Hi All,
To find out if xeq, the sequencer package created by Krzysztof Czaja in 2006, is worth fixing, documenting and making a reliable deken package, I am looking for someone knowledgeable of and interested in sequencers.
I use xeq since, hmmm 2003 for my "Autoklavierspieler" [1] and preferred it to seq for the more flexible structure, playing in parallel und variable speed, positioning within midifiles and and accuracy and dont know any more why else. Using it in many installations now playing for years, especially the speaking piano pieces.
The problem was compile errors since 5 years made me to use my own version of the source, but not clean enough to release.
So I would be very pleased if you dekenize xeq.
If you happen to have some not-to-complicated patches which demonstrate features of xeq, those would be welcome. Xeq works remarkable well, but some of the objects can crash with certain argument values. Checks can and should be added, but then you have to know 'valid' ranges. For me, dekenizing means including help-patches demonstrating at least some of the functionality of each object.
mfg winfried
Greetings,
Fred Jan
[1] http://algo.mur.at/projects/autoklavierspieler
Xeq is a sequencer suite inspired by the [qlist] object, but extended by several useful features, only very rudimentary described. At least it supports midi files, searching for note sequences in its dictionaries, and maybe even some sort of programming to control sequence parsing.
At the moment, xeq compiles but because of the very limited documentation; an outdated paper and a few poorly documented patches its usage range is unknown.
To some extend I can fix bugs when it is clear what the proper behaviour is, but my knowledge of advanced sequencer usage is too limited to find out how it should work. This also limits my capability to create useful help-patches. So I am seeking help from someone with more than average knowledge of sequencers.
I am aware that software can be too complicated to be useful, so at one point the conclusion could be that xeq is not worth the effort to document and debug it. But so far the framework looks well structured, and some of the charted functionality is working very well.
For testing the source is available at https://github.com/electrickery/pd-xeq/tree/experimentalReconstruction, but I can provide a deken like zip with an executable and available documentation for all the usual platforms. No stabilility is guaranteed, but it sure it will be 'interesting' (if you like sequencers ;-).
Fred Jan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Hi Fred Jan,What features do you find in the xeq library which couldn't be sustainably implemented with abstractions? -Jonathan
From: Fred Jan Kraan <fjkraan@xs4all.nl>
To: "pd-list@lists.iem.at" pd-list@lists.iem.at Sent: Friday, October 21, 2016 4:30 PM Subject: [PD] Request for help investigating the xeq sequencer package
Hi All,
To find out if xeq, the sequencer package created by Krzysztof Czaja in 2006, is worth fixing, documenting and making a reliable deken package, I am looking for someone knowledgeable of and interested in sequencers.
Xeq is a sequencer suite inspired by the [qlist] object, but extended by several useful features, only very rudimentary described. At least it supports midi files, searching for note sequences in its dictionaries, and maybe even some sort of programming to control sequence parsing.
At the moment, xeq compiles but because of the very limited documentation; an outdated paper and a few poorly documented patches its usage range is unknown.
To some extend I can fix bugs when it is clear what the proper behaviour is, but my knowledge of advanced sequencer usage is too limited to find out how it should work. This also limits my capability to create useful help-patches. So I am seeking help from someone with more than average knowledge of sequencers.
I am aware that software can be too complicated to be useful, so at one point the conclusion could be that xeq is not worth the effort to document and debug it. But so far the framework looks well structured, and some of the charted functionality is working very well.
For testing the source is available at https://github.com/electrickery/pd-xeq/tree/experimentalReconstruction, but I can provide a deken like zip with an executable and available documentation for all the usual platforms. No stabilility is guaranteed, but it sure it will be 'interesting' (if you like sequencers ;-).
Fred Jan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 22-10-16 23:55, Jonathan Wilkes wrote:
Hi Fred Jan, What features do you find in the xeq library which couldn't be sustainably implemented with abstractions?
What features it contains is to be found out. For a great part, they probably could be implemented as abstractions. The Context (v2) implementation by Liam Goodacre proves this is possible.
At the existing documentation is outdated and incomplete, and so is the list of features. Looking at the code gives only hints of features. You have to know about sequencer usage to interpret these hints correctly.
-Jonathan
Fred Jan
*From:* Fred Jan Kraan fjkraan@xs4all.nl *To:* "pd-list@lists.iem.at" pd-list@lists.iem.at *Sent:* Friday, October 21, 2016 4:30 PM *Subject:* [PD] Request for help investigating the xeq sequencer package
Hi All,
To find out if xeq, the sequencer package created by Krzysztof Czaja in 2006, is worth fixing, documenting and making a reliable deken package, I am looking for someone knowledgeable of and interested in sequencers.
Xeq is a sequencer suite inspired by the [qlist] object, but extended by several useful features, only very rudimentary described. At least it supports midi files, searching for note sequences in its dictionaries, and maybe even some sort of programming to control sequence parsing.
At the moment, xeq compiles but because of the very limited documentation; an outdated paper and a few poorly documented patches its usage range is unknown.
To some extend I can fix bugs when it is clear what the proper behaviour is, but my knowledge of advanced sequencer usage is too limited to find out how it should work. This also limits my capability to create useful help-patches. So I am seeking help from someone with more than average knowledge of sequencers.
I am aware that software can be too complicated to be useful, so at one point the conclusion could be that xeq is not worth the effort to document and debug it. But so far the framework looks well structured, and some of the charted functionality is working very well.
For testing the source is available at https://github.com/electrickery/pd-xeq/tree/experimentalReconstruction, https://github.com/electrickery/pd-xeq/tree/experimentalReconstruction, but I can provide a deken like zip with an executable and available documentation for all the usual platforms. No stabilility is guaranteed, but it sure it will be 'interesting' (if you like sequencers ;-).
Fred Jan
Pd-list@lists.iem.at mailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Alexandre Torres Porres -
Derek Kwan -
Fred Jan Kraan -
IOhannes m zmölnig -
Jonathan Wilkes -
Miller Puckette -
Peter P. -
Winfried Ritsch