webcam stepsequencer

[artificial]

Hello guys, once again!

I think I have found a solution for my webcam stepsequencer.

The problem is that at the moment only one captured zone is converted to the stepsequencer...

After some hours of patching now, I'm feeling a bit dizzy now, so I just wanted to ask, whether if someone has an idea, how it could be done that the stepsequencer is able to convert more captured zones at the same time?!?!

You can download the patchfile here:
http://www.sensomusic.com/forums/uploads.php

cheers guys!

artificial

[nay-seven]

strange , your patch seems empty..(1Ko )

[artificial]

oops... sorry, I'm going to upload it again....

[artificial]

Okay, I changed the URL in the first post, so you need to download it directly from the uploader, because this way, the downloaded file has 119kb (so, it should work now)!

cheers

[nay-seven]

thanks , work this way
cool project , i think you need an array guru on this subject ( 23fx , martingnasse....call for you... )

what about on hardware side..?

[artificial]

The last weekends I did some brainstorming and I think I found a nice solution, which should be kinda cheap too. The problem is that I'm only at home on weekends, so I'm going to build it this weekend, my ideas so far:

I want to create this box:

top: wood; 40*30cm
sides: two sides glass; two sides wood; height: 40 cm; below you will find more information
bottom: wood

The top:
On the top there should be the grid (holes drilled through the wood). I consider making it 40*30cm, because this would be the same proportions (4:3) as the webcam picture (for example: 640*480).

The sides:
I choose 2 sides as glass and 2 as wood, because I need some light in the box, because the underside must not be completely black (if possible it should be grey). Otherwise it will not be able to detect the filled holes, which should create black blurs. Well, I think two picture frames would be perfect for the sides, and kinda cheap.

The bottom
The bottom should also be wooden with notches for the sides to make it more stable.

What do you think of it?

[nay-seven]

That 's seems great !

i just suggest you ( i talk by experience ) to built first a paperboard version
this way you can test safely before wood/glass version .

And other thought: what about a little electric light inside the box in place of glass, this way you don't depend of external light..?

[martignasse]

Hi artificial,

Interesting project you have here

I'll try to see if i can help, but unfortunately, i have no webcam to experiment with

Anyway, i'll have a look at your patch.

[23fx23]

testing with paper board is a nice suggestion, let us know your progress!

[artificial]

That 's seems great !

i just suggest you ( i talk by experience ) to built first a paperboard version
this way you can test safely before wood/glass version .

And other thought: what about a little electric light inside the box in place of glass, this way you don't depend of external light..?

Hehe, yeah I already tested it (ot of a fast-built paperboard box) with a puredata patch and this way, I got the basis for my measures... but yeah, i should do another test with Usines' detection patch (just to be sure, if everything would work this way).

I also thought of an internal electric light... I'm going to think about it again... but maybe combining this ideas would be the best?

Hi artificial,

Interesting project you have here

I'll try to see if i can help, but unfortunately, i have no webcam to experiment with

Anyway, i'll have a look at your patch.

This would be great if you could check my patch, because I have the feeling that it is not that efficient! You have to know that I'm still kinda new to patching!

Thanks for your effort, guys!

cheers

[martignasse]

The problem is that at the moment only one captured zone is converted to the stepsequencer...
...whether if someone has an idea, how it could be done that the stepsequencer is able to convert more captured zones at the same time?!?!

Ok, i think i see the problem.

What you try to do in your patch is to apply the same math computing flow for each X and Y array members of detected zone, right ?

Unfortunately, it's impossible (or very, very difficult) to achieve that by patch
Script is the way to go, as you'll can use a for loop to do the job

Hope it help

[artificial]

oh... i see...so, this means that I have to script the whole maths? Could be a competition as I'm completely new to Usines script, but I trying to learn it!

thanks for your help!

[artificial]

Hello again!

I have tried to create a script for the maths now.

The main idea was that it should check if there is a detection in the horizontal grid (lines) and if there is a detection in the vertical columns (steps). So I divided the picture in this grid.

If line 1 is detected and step 1 is detected, it should send the value 1 to an output (called for example l1s1)... if not, it should send the value "0"... in this case i have to create a dedicated output to every cell in the grid (because I thought of a 16 step sequencer with 6 lines, this should be 96 outputs)... and this outputs are then connected to the values of 6 stepmidi modules (for every line I need one module)... Am I totally wrong, or could the detection work like this, as it should be possible to detect various zones at the same time?

Anyway, I've tried to create a simple demo script. It should only detect the cell in line 1 and step 1 (bottom left !!!)... but unfortunately it does not work yet...

Code: Select all

//////////////////////////
// 
/////////////////////////
// parameters declaration

var inputx : tParameter;
var inputy : tParameter;
var l1s1 : tParameter;
var x : single;
var y : single;

// initialisation : create parameters
procedure init;
begin

inputx := CreateParam ('x',ptArray);
SetIsOutput(inputx,false);

inputy := CreateParam ('y',ptArray);
SetIsOutput(inputy,false);

l1s1 := CreateParam ('line 1 step 1', ptDataFader);
SetIsInput(l1s1,false);

end;

// Global variables

var linecount : byte;
var stepcount : byte;
var step1 : byte;
var step2 : byte; 
var step3 : byte; 
var step4 : byte; 
var step5 : byte;
var step6 : byte; 
var step7 : byte; 
var step8 : byte; 
var step9 : byte;
var step10 : byte; 
var step11 : byte; 
var step12 : byte; 
var step13 : byte;
var step14 : byte; 
var step15 : byte; 
var step16 : byte;

var line1 : byte;
var line2 : byte; 
var line3 : byte; 
var line4 : byte; 
var line5 : byte;
var line6 : byte;

//////////////////////////////
// main proc
//////////////////////////////

Procedure Process;
begin


for stepcount := 0 to 15 do
	begin 
                x := GetDataArrayValue(inputx, stepcount);

      		if &#40;x > 0&#41; AND &#40;x <= 0.0625&#41; then
			begin
				step1 &#58;= 1;
			end
		else
			begin
				step1 &#58;= 0;
			end;
	
	end;

for linecount&#58;= 0 to 5 do
	begin
                y &#58;= GetDataArrayValue&#40;inputy, linecount&#41;;

      		if &#40;y > 0&#41; AND &#40;y <= 0.1666&#41; then
			begin
				line1 &#58;= 1;
			end
		else
			begin
				line1 &#58;= 0;
			end;
        end;

if &#40;line1 = 1&#41; AND &#40;step1 = 1&#41; then
	begin
		SetValue&#40;l1s1, 1&#41;;
	end
else
	begin
		SetValue&#40;l1s1, 0&#41;;
	end;

end;

Sorry, if my script is total nonsense, but despite some simple php-scripts, I'm kinda new to scripting, so please don't flame me!

Thanks in advance!

[martignasse]

wow artificial,

great start with script, it's almost running with your first try

You just forgot to ad an IF (stepcount = 0) and an IF (linecount = 0) statment to isolate your step1 and line1 treatement

like that :

Code: Select all

//////////////////////////
// 
/////////////////////////
// parameters declaration

var inputx : tParameter;
var inputy : tParameter;
var l1s1 : tParameter;
var x : single;
var y : single;

// initialisation : create parameters
procedure init;
begin

inputx := CreateParam ('x',ptArray);
SetIsOutput(inputx,false);

inputy := CreateParam ('y',ptArray);
SetIsOutput(inputy,false);

l1s1 := CreateParam ('line 1 step 1', ptDataFader);
SetIsInput(l1s1,false);

end;

// Global variables

var linecount : byte;
var stepcount : byte;
var step1 : byte;
var step2 : byte; 
var step3 : byte; 
var step4 : byte; 
var step5 : byte;
var step6 : byte; 
var step7 : byte; 
var step8 : byte; 
var step9 : byte;
var step10 : byte; 
var step11 : byte; 
var step12 : byte; 
var step13 : byte;
var step14 : byte; 
var step15 : byte; 
var step16 : byte;

var line1 : byte;
var line2 : byte; 
var line3 : byte; 
var line4 : byte; 
var line5 : byte;
var line6 : byte;

//////////////////////////////
// main proc
//////////////////////////////

Procedure Process;
begin


for stepcount := 0 to 15 do
    begin 
        x := GetDataArrayValue(inputx, stepcount);

        // added this
        if (stepcount =0) then begin 
            if &#40;x > 0&#41; AND &#40;x <= 0.0625&#41; then begin
                step1 &#58;= 1;
            end
            else begin
                step1 &#58;= 0;
            end;
        end; // and this
    end;

for linecount&#58;= 0 to 5 do
    begin
        y &#58;= GetDataArrayValue&#40;inputy, linecount&#41;;

        // added this
        if &#40;linecount =0&#41; then begin 
            if &#40;y > 0&#41; AND &#40;y <= 0.1666&#41; then begin
                line1 &#58;= 1;
            end
            else begin
                line1 &#58;= 0;
            end;
        end; // and this
    end;

if &#40;line1 = 1&#41; AND &#40;step1 = 1&#41; then
    begin
        SetValue&#40;l1s1, 1&#41;;
    end
else
    begin
        SetValue&#40;l1s1, 0&#41;;
    end;

end;

otherwise, the rest of the set loop and line loop reset your step1 and line1 to 0.

That said, i suggest you another strategy, to reduce CPU usage and to be more modular.

For now, you say, i have 16 step, i have 6 line, let see if coordinate provided are corresponding to one of those.
In any case, like you said, you'll have to inspect each possibility (so 96 test), plus you make a double loop.

I just propose you the opposite :

You can get the size of the array input (X or Y, they should be the same)
You make a loop with this number (ex: you have 4 coordinates, you loop 4 times)
inside the loop, for the current coordinate pair ( first, second...) you deduce his place in the sequencer (what the step corresponding to this X and what the line corresponding to this Y.

Like that, you just compute detected zones, and not the entire array of possibilities each times.

anyway, your first script is born, congrats

let me the time to make an example and post it...

[artificial]

Thanks for your help, martignasse!

I'm really happy that it was not too false. Oh, and that's great that you code another (and more cpu-friendly) script, because I already had the feeling, that it will be too cpu-intense... and so, by showing me another solution, I can learn more about it...!

I really appreciate your help!

[martignasse]

ok, seems like you are ready to go deeper in script land, good

in the script below, i implemented the strategy i told you.

just to mention :
- there is lots of potentials optimization, but it's not the subject for now.
- i commented a lot, to help you understand the underlying logic.
- i tried to show you some good script practice, even if i don't know all of them.
- look how we keep the script simple and easily expendable by choosing the array output.
- i used the script wiki page to remind myself some useful syntax
- has i can't use the video detect module (no webcan ) i used a kind of debug patch with array to simulate X and Y, can show you if you want.

So here we go

Code: Select all

//////////////////////////
// 
/////////////////////////
// parameters declaration

var inputx : tParameter;
var inputy : tParameter;
var arrayout: tParameter;
var x : single;
var y : single;


// Global variables
var zones : byte;
var i: byte;
var step : byte;
var line : byte;

// constant
// always good to have constant where we can ;-)
CONST SEQ_STEP_NB = 16;
CONST SEQ_LINE_NB = 6;

// initialisation : create parameters
procedure init;
begin

    inputx := CreateParam ('x',ptArray);
    SetIsOutput(inputx,false);

    inputy := CreateParam ('y',ptArray);
    SetIsOutput(inputy,false);

    // we choose an array because it save us to have loads of output outlet
    // we can extract individual info by patch, so it's ok
    arrayout := CreateParam ('arrayo ut', ptArray);
    SetIsInput( arrayout ,false);
    SetLength( arrayout , SEQ_STEP_NB * SEQ_LINE_NB );

end;

//////////////////////////////
// main proc
//////////////////////////////
Procedure Process;
begin

    // reset arrayoutput
    for i := 0 to SEQ_STEP_NB * SEQ_LINE_NB do begin
        SetDataArrayValue(arrayout, i, 0);
    end;

    // get the number of detected zone
    // could be inputy, as they should have the same size
    zones :=  GetLength(inputx);
   
    for i := 1 to zones do begin 
        // get the zone coordinate
        // i - 1 cause array index begin with 0
        x := GetDataArrayValue(inputx, i - 1);
        y := GetDataArrayValue(inputy, i - 1);

        // deduce step index (0 to SEQ_STEP_NB - 1) from x
        // again, SEQ_STEP_NB - 1 because we prepare variable to compute an array index
        // we use Trunc() to convert from single to integer or byte
        step := Trunc(x * (SEQ_STEP_NB - 1));
        
        // deduce line index (0 to SEQ_LINE_NB - 1) from y
        // again, SEQ_LINE_NB - 1 because we prepare variable to compute an array index
        // we use Trunc() to convert from single to integer or byte
        line := Trunc(y * (SEQ_LINE_NB - 1));

        // set the concerned cell to 1
        // we'll use the same ((line * SEQ_STEP_NB) + step) formula to extract  info from the array by patch
        // with a GetArrayValue module and this formula, we can spot an individual cell value
        SetDataArrayValue(arrayout, (line * SEQ_STEP_NB) + step, 1.0);
    end;
    
end;

next step is to make the patch to extract the output array info
but before that, just put an array display module on the output to see the result, and how X and Y influence it

bon appetite!

[artificial]

Wow! Thanks for this script!

I've tried to think it through, but I think now I'm a bit too tired to understand it completely... I guess I should print out the scripting manual too... haha!

But, now I have to try it out!!

Thank you so much!

cheers.

[martignasse]

hehe, take time...

and have fun

[artificial]

I'm going to have fun for sure!!

So, hopefully this weekend, I find the time to create the hardware...! If so, I'm going to post some pictures here, maybe someone else want to build such a sequencer...

[artificial]

okay, I have tested it out now, and in general it works great so far, there's only one thing: in the whole top line (line 6) there are no steps detected and also in the last column (16th step of each line) there are no cells detected... as I have still not completely understood the whole script I can't figure it out for myself... so, could you please help me once again?

Oh... by the way, for testing, you could also use a xy-pad!

cheers!

[senso]

a good news Usine V5.10 will contain a new Video Detection module much more efficient.
Take a look on
http://www.sensomusic.com/wiki/doku.php ... tection_dx

[martignasse]

okay, I have tested it out now, and in general it works great so far, there's only one thing: in the whole top line (line 6) there are no steps detected and also in the last column (16th step of each line) there are no cells detected... as I have still not completely understood the whole script I can't figure it out for myself... so, could you please help me once again?

Be, careful, as we use array to store step/line info, line number go from 0 to 5 (not 1 to 6) and step go from 0 to 15 (not 1 to 16)

So, in your patch, you could do something like that :

the module used is 'Extract sub array'.
We want the fourth line so the array begin at (line_index * SEQ_STEP_NB) + step_index = 3*16 + 0
and the length is 16.
has you see, we should use index, and not 'real' line or step number.

Oh... by the way, for testing, you could also use a xy-pad!

yep, but the XY pad hasn't array output

[artificial]

a good news Usine V5.10 will contain a new Video Detection module much more efficient.
Take a look on
http://www.sensomusic.com/wiki/doku.php ... tection_dx

Hey, that's great news!

I mean, I have not had a efficiency problem yet, but the more efficient it is, the better! hehe

So, when will V5.10 will be out??

We want the fourth line so the array begin at (line_index * SEQ_STEP_NB) + step_index = 3*16 + 0
and the length is 16.
has you see, we should use index, and not 'real' line or step number.

Ah... I see! Now, I think i got it! Thanks!

[senso]

The V5.10 will be out next week, I hope.

[artificial]

The V5.10 will be out next week, I hope.

Oh that's great!


The Webcam Step Sequencer already works, I have already tried it out with Tracktion 3 and FL Studio! There are still some detection anomalies, but they should not be a big problem.... just need some time for configuring!

Btw, I have changed my layout to 9 lines and we have already built the sequencer hardware... there are just a few thing, which I have to change/add:

I have to add an internal light source.

The top still needs to be painted.

Here are the first pics of the hardware!











cheers

[senso]

great job!!!
send us videos as soon as you can!

[martignasse]

wow, god job

what about the usine patch, have you got a functional one ?

...I have changed my layout to 9 lines...

Normally, just update SEQ_LINE_NB constant in the script and you should be ok

keep up the god work

[nay-seven]

great to see such a project growing !
any screenshot of Usine interface / video capture....?

[artificial]

Thanks for your feedback!

Well, I'm going to create a short demo video, but the problem is, that at the moment I don't have many dark marbles at home, which I could use...! But anyway, I'm trying to create something!

cheers

[artificial]

Oh.. I just have a small question: I want to delete the caption of the used switches... but everytime I open Usine, the switches' caption is "caption" again... how I can I delete the caption permanently? Btw, as I have to edit many switches, is there a way to group them together or something, to change their layout/caption/...?!?!

cheers guys!

[nay-seven]

have you try :
edit layout /uncheck show caption
but no group option for this right now..

about vidéo , a little advice : take you time..
good video quality , sound and practice to have a good result let you have more satisfaction and help Usine communication..

[martignasse]

Oh.. I just have a small question: I want to delete the caption of the used switches... but everytime I open Usine, the switches' caption is "caption" again... how I can I delete the caption permanently?

hmm, interesting problem.
The fact is : as your switch are outlet of a subpatch, usine rename them automatically to default if they are empty, the way to not display the caption is to set show caption to off in the edit layout, but don't put an empty caption or usine will reset it to default next time you load the workspace.

Btw, as I have to edit many switches, is there a way to group them together or something, to change their layout/caption/...?!?!

unfortunately, not for now you have to tweak them one by one.

...wait, there is a solution, but it's very tricky :
the wkp file is a text file, you can open it in a notepad.

search and replace : show caption=1 by show caption=0
the problem is to isolates your switch, they should have the line Tcaption=switch in the same bloc

be sure to try this on a duplicated wkp file, as you can completely corrupt it.

hope it help

[ethnix73]

Whaouuu!

Great project...Nearly Usine as a reactable.

[Clearscreen]

That's just awesome Artificial!!

[artificial]

Thanks for all the positive reactions, I'm really glad you like my project!

Btw, I'm going to create a demo video next weekend - when I'm at home again!

cheers!

[artificial]

well, I just wanted to inform you, that this project is NOT DEAD! I just have my final exams soon and so I'm a bit stressed at the moment... anyway, the video will come soon!

[martignasse]

cool, can't wait to see it in action

[23fx23]

same here can't wait to see!

[artificial]

hey guys!

here's a first promotional video, which I had to do for collegue...! I'm going to post a more "functional" video as soon as possible (final exams are coming in the next weeks, so it will take some time i guess!

http://www.youtube.com/watch?v=3NAn9fSdh8M

anyway, i hope you like this one!

cheers!

[23fx23]

awesome!! can't wait some more!

[nay-seven]

Really great one artificial !
good job !

[gurulogic]

This is !!!!!!!!!!

[artificial]

thanks for the feedback, guys! i'm really glad that you like the video! as I said before, another (more functional) video will come soon!

[bsork]

:D

[ethnix73]

Impressive!

[héliouk 6]

youpa!

[waolelaid]

real good work !!!

[artificial]

Sorry for being absent so long, but anyway, I uploaded the patch to the addons/groove makers section!

Have fun!

cheers.
artificial

[23fx23]

coool , gonna have a look at this awesome thing thanks