so a midifile can be played forwards backwards with dynamic tempo.
If not, then maybe a message sequencer, e.g. a "text" object, otherwise I'll probably have to write one myself...
and yes, I know it's not as trivial as it sounds, especially the midifile player.
I would be grateful for any advice.
mfg winfried
how about a patch that reads the midifile and stores the data, which you then play as you wish? for an instalation I'm working on, I prepared a patch that reads a midifile with +50K events, puts them into a data structures "score", and then the info can be used for playback. It's not "one object", but it does what you wish.
so a midifile can be played forwards backwards with dynamic tempo.
If not, then maybe a message sequencer, e.g. a "text" object, otherwise I'll probably have to write one myself...
and yes, I know it's not as trivial as it sounds, especially the midifile player.
I would be grateful for any advice.
mfg winfried
Am Donnerstag, 8. August 2024, 20:00:15 CEST schrieb João Pais:
how about a patch that reads the midifile and stores the data, which you then play as you wish? for an instalation I'm working on, I prepared a patch that reads a midifile with +50K events, puts them into a data structures "score", and then the info can be used for playback. It's not "one object", but it does what you wish.
Thanks, using data structures is a nice idea. Somehow once (15+ years ago) used them but where slow doing tracing objects, but maybe the new implementation is more usable.
The problem is how to handle noteon/off in reverse, there should be different modes. So mabe I store it in reverse order in another text.
mfg winfried
so a midifile can be played forwards backwards with dynamic tempo.
If not, then maybe a message sequencer, e.g. a "text" object, otherwise I'll probably have to write one myself...
and yes, I know it's not as trivial as it sounds, especially the midifile player.
I would be grateful for any advice.
mfg winfried
Pd-list - pd-list@lists.iem.at https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/364V2QKCJZ C56BCCUZEG35CFIBMSDR4S/
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
how about a patch that reads the midifile and stores the data, which you then play as you wish? for an instalation I'm working on, I prepared a patch that reads a midifile with +50K events, puts them into a data structures "score", and then the info can be used for playback. It's not "one object", but it does what you wish.
Thanks, using data structures is a nice idea. Somehow once (15+ years ago) used them but where slow doing tracing objects, but maybe the new implementation is more usable.
The problem is how to handle noteon/off in reverse, there should be different modes. So mabe I store it in reverse order in another text.
which new implementation? :)
I'm not sure if I know of any changes in the drawing, but I might be wrong. anyway this only affects the result if a) you need to see the structs (if you don't, there is no lag) and b) even if you need to see them, you might notice something only when opening the canvas for the first time, afterwards is no issue. My patches usually have a reading point marker for live visualisation as well, and doesn't affect the performace.
Making 2 score versions (forward + backward) might be the best idea as well - it's not that hard to do a forward-playing patch, but since [pointer] doesn't have a "previous" method, it would need lots of creative thinking and calculations to make that happen (although surely possible). Using "next" in a reversed score makes it much simpler.
Here is a picture of a small section of my canvas, for reference.
Joao
mfg winfried
so a midifile can be played forwards backwards with dynamic tempo.
If not, then maybe a message sequencer, e.g. a "text" object, otherwise I'll probably have to write one myself...
and yes, I know it's not as trivial as it sounds, especially the midifile player.
I would be grateful for any advice.
Thanks for the info,
The piano roll score looks nice, is this a library object, where can I find this.
Tracing data also backwards would be a solution, have to look. Midifiles for ensemble mecanique have up to 1 million notes, so effiiency might be an issue.
mfg winfried
Am Freitag, 9. August 2024, 12:52:37 CEST schrieb João Pais:
how about a patch that reads the midifile and stores the data, which you then play as you wish? for an instalation I'm working on, I prepared a patch that reads a midifile with +50K events, puts them into a data structures "score", and then the info can be used for playback. It's not "one object", but it does what you wish.
Thanks, using data structures is a nice idea. Somehow once (15+ years ago) used them but where slow doing tracing objects, but maybe the new implementation is more usable.
The problem is how to handle noteon/off in reverse, there should be different modes. So mabe I store it in reverse order in another text.
which new implementation? :)
I'm not sure if I know of any changes in the drawing, but I might be wrong. anyway this only affects the result if a) you need to see the structs (if you don't, there is no lag) and b) even if you need to see them, you might notice something only when opening the canvas for the first time, afterwards is no issue. My patches usually have a reading point marker for live visualisation as well, and doesn't affect the performace.
Making 2 score versions (forward + backward) might be the best idea as well - it's not that hard to do a forward-playing patch, but since [pointer] doesn't have a "previous" method, it would need lots of creative thinking and calculations to make that happen (although surely possible). Using "next" in a reversed score makes it much simpler.
Here is a picture of a small section of my canvas, for reference.
Joao
mfg winfried
so a midifile can be played forwards backwards with dynamic tempo.
If not, then maybe a message sequencer, e.g. a "text" object, otherwise I'll probably have to write one myself...
and yes, I know it's not as trivial as it sounds, especially the midifile player.
I would be grateful for any advice.
Thanks for the info,
The piano roll score looks nice, is this a library object, where can I find this.
Those are the scalars done with data structures - so, in a way, each is an object.
Tracing data also backwards would be a solution, have to look. Midifiles for ensemble mecanique have up to 1 million notes, so effiiency might be an issue.
if you want to display them, that will surely lag at least when opening the canvas. My patch has 36K scalars, I haven't opened it for a while but I think it took at least one minute to open - but after that, no more issues, also not when scrolling through it.
If you don't need a graphical display, then data structures can still be used eficiently without scalars - or [text], or [coll], etc.
Joao
Hello,
Le 9 août 2024 à 21:42, Winfried Ritsch ritsch@iem.at a écrit :
Tracing data also backwards would be a solution, have to look. Midifiles for ensemble mecanique have up to 1 million notes, so effiiency might be an issue.
PureData's datastructure is using pointers to store memory addresses, this should be the fastest method you can get with PureData. There is no need to slow it down by drawing data on a canvas.
Reverse playing is not really friend with MIDI note on and note off concept, that would be replaced by note length and a timing method in the player struct.
Anyway, with actual computers we can render a midi file to audio in seconds and scratch it with usual methods.
pat'
Am 10. August 2024 09:45:56 MESZ schrieb Patko nytkophilus colet.patrice@gmail.com:
Anyway, with actual computers we can render a midi file to audio in seconds and scratch it with usual methods.
Well, this works as long as you are rendering your midi data with a soft synth.
Afaik, wini wants to control a hardware piano http://algo.mur.at/projects/autoklavierspieler
mfg.sfg.jfd IOhannes
Thanks for all the input.
Since there is no ready to use object/project, I will do one an report back if done and evaluated.
mfg winfried
Am Samstag, 10. August 2024, 10:52:36 CEST schrieb IOhannes m zmölnig:
Am 10. August 2024 09:45:56 MESZ schrieb Patko nytkophilus
Anyway, with actual computers we can render a midi file to audio in seconds and scratch it with usual methods.
Well, this works as long as you are rendering your midi data with a soft synth.
Afaik, wini wants to control a hardware piano http://algo.mur.at/projects/autoklavierspieler
mfg.sfg.jfd IOhannes
Pd-list - pd-list@lists.iem.at https://lists.iem.at/hyperkitty/list/pd-list@lists.iem.at/message/V77ZVI4UGU TJAP7SGVUTF2PHDSTYIJWM/
To unsubscribe send an email to pd-list-leave@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.iem.at/
-
IOhannes m zmölnig -
João Pais -
Patko nytkophilus -
Winfried Ritsch