Hello all.
I had some free time, so I made a simple clip-mixing tool with effects using PD and PDP/PiDiP. Actually, it was a patch I built for a performance last week, this is just the "pretty" version. It's something I had to do anyway. :-)
It's nothing you can't do yourself in about an hour, but I figured sharing is nice.
Requires PDP, PiDiP, playlist, PD 0.37.4.
Questions, bug reports, bug fixes or any feedback most welcome.
Anyway, enjoy!
.thomas
Hi Thomas,
I've tried quickly a couple of things with your mixing-tool.
The thing which doesn't work for me is the pd chromakey. I get something like this: invalid command name ".x47bb60.c"
To solve your metro problem, i attached a qt_example which makes it possible to change the metro while playing with trigger/float/bang.
Graph on parent is always funny, but it makes it a little bit easier if you use a canvas as a background. When saving/closing the file, you have to adjust the window to the size that you want for graph on parent, which is the 'size' which appears on your flake.01 window. But it's always a bit 'tricky' to do it precise.
The hradio works fine if it isn't placed on top on another object in the final window.
Hope this will help a bit.
Ciao,
Sara
Thomas Sivertsen wrote:
Hello all.
I had some free time, so I made a simple clip-mixing tool with effects using PD and PDP/PiDiP. Actually, it was a patch I built for a performance last week, this is just the "pretty" version. It's something I had to do anyway. :-)
It's nothing you can't do yourself in about an hour, but I figured sharing is nice.
Requires PDP, PiDiP, playlist, PD 0.37.4.
Questions, bug reports, bug fixes or any feedback most welcome.
Anyway, enjoy!
.thomas
#N canvas 335 336 458 308 10; #X obj 146 151 pdp_qt; #X obj 69 97 metro 40; #X floatatom 90 19 5 0 0 0 - - -; #X obj 23 60 bng 15 250 50 0 empty empty empty 0 -6 0 8 -139201 -1 -1; #X msg 70 73 stop; #X obj 90 44 t b f; #X obj 212 49 openpanel; #X msg 212 74 open $1; #X msg 212 21 bang; #X msg 212 123 stop; #X msg 212 99 play; #X obj 146 205 pdp_glx; #X connect 0 0 11 0; #X connect 1 0 0 0; #X connect 2 0 5 0; #X connect 3 0 1 0; #X connect 4 0 1 0; #X connect 4 0 9 0; #X connect 5 0 3 0; #X connect 5 1 1 1; #X connect 6 0 7 0; #X connect 7 0 0 0; #X connect 8 0 6 0; #X connect 9 0 0 0; #X connect 10 0 0 0;
Hallo Sara,
how is it?
sara kolster hat gesagt: // sara kolster wrote:
The hradio works fine if it isn't placed on top on another object in the final window.
Unfortunatly at least I still get the same behaviour in the simplyfied example I posted earlier, even if I include a cnv below the hradio.
Ciao
Frank Barknecht _ ______footils.org__
Hey Frank,
I'm ok here in the Baltics. Almost at the end of the Baltic tour ;)
You're right, if I save, close and re-open the patch, the hradio-object is being moved. [by itself?]
Ciao, Sara
Frank Barknecht wrote:
Hallo Sara,
how is it?
sara kolster hat gesagt: // sara kolster wrote:
The hradio works fine if it isn't placed on top on another object in the final window.
Unfortunatly at least I still get the same behaviour in the simplyfied example I posted earlier, even if I include a cnv below the hradio.
Ciao
sara kolster wrote:
Hi Thomas,
hello
I've tried quickly a couple of things with your mixing-tool.
The thing which doesn't work for me is the pd chromakey. I get something like this: invalid command name ".x47bb60.c"
Ah yep. It has some weirdness. At least it's not a stack overflow or slow-down (that I noticed...). Will fix. Wasn't tested for anything but bluescreen, and it's way too simple (need to figure out about alphas).
To solve your metro problem, i attached a qt_example which makes it possible to change the metro while playing with trigger/float/bang.
Yes! I forgot the thing about banging the metro on each incrementation! Thank you! But, I wanted to do something with the absolute frame-numbers because that will be more flexible in the end. I have an idea about an fps as a motion-blur-threshold. Simple, but works since processing is free in pdp, at least for my use so far. :-)
Graph on parent is always funny, but it makes it a little bit easier if you use a canvas as a background
Aha. That was one of the things I wanted to afterwards. Looks like it'll be black & yellow, then.
When saving/closing the file, you have to adjust the window to the size that you want for graph on parent, which is the 'size' which appears on your flake.01 window. But it's always a bit 'tricky' to do it precise.
Oh. That is not so simple when it keeps reseting shit left and right, top and bottom, not to mention hogs the scale units and has an artistic idea about the placement of my sliders and toggles. The whole thing about sacrificing goats and stuff isn't really necessary. Still, i guess it takes more than 4-5 hours practice and a trackpad to make it easy. :-/
Anyway, I didn't read the docs well enough or experiment enough before opening my big mouth. Will practice. :-)
The hradio works fine if it isn't placed on top on another object in the final window.
Well, not for me. Will investigate. I tried it in subpatches, there it works ok. Better approach for some things, anyway.
Hope this will help a bit.
Thank you! The docs for graph-on-parent very much welcome!
Tomorrow my stack-overflowing almost-pure-pd step-sequencer will get some more attention along with the other stuff.
Flake, indeed.
.thanks
Hallo, Thomas Sivertsen hat gesagt: // Thomas Sivertsen wrote:
I tried it in subpatches, there it works ok. Better approach for some things, anyway.
You probably meant to say "abstractions". Subpatches are the [pd] thingies, abstractions are seperate files. This is a very important difference to remember, because it will have further consequences like handling of $0-localized variable which are seen outside subpatches, but hidden outside abstractions and also argument passing: subpatches don't have their own $1,... arguments, abstractions do.
Ciao
Frank Barknecht _ ______footils.org__
-
Frank Barknecht -
sara kolster -
Thomas Sivertsen