Binary Counter

Reply to Binary Counter on Sun, 21 May 2017 01:16:57 GMT

Fauveboy — Sun, 21 May 2017 01:16:57 GMT

Im using a binary counter which prints results like so... The numbers occur from user input. I was planning on using objects like select or condition objects to specify a binary numberto assign it to a job... but they don't recognise values that the console shows? Is there any way around this?
Many thanks

Reply to Binary Counter on Sun, 21 May 2017 05:14:12 GMT

LiamG — Sun, 21 May 2017 05:14:12 GMT

The message box is creating a symbol rather than a float. If you don't mind using externals, you could do this:

[symbol $1$2$3(
l
[symbol2list] (from zexy)

Reply to Binary Counter on Sun, 21 May 2017 06:59:47 GMT

Balwyn — Sun, 21 May 2017 06:59:47 GMT

you could prefix the binary symbol with an non-numeric symbol eg. bin$1$2$3$4(, then use [rout.e bin1100 bin1101 bin1110 bin1111].
I notice you are using [gate] as a [spigot] and you have four [sel] instead of [sel 12 13 14 15].
Is the binary representation the actual output? or does it need to converted to decimal
This may offer some help
4bit.pd

Reply to Binary Counter on Sun, 21 May 2017 10:18:12 GMT

whale-av — Sun, 21 May 2017 10:18:12 GMT

@Fauveboy Hello....... Have you tried this.......modified.... better....logic age4.zip
You just put the [action xy] module in a job, and it gives the state, and bangs the job again for the previous button if you release the last....
David.

Reply to Binary Counter on Sun, 21 May 2017 10:36:00 GMT

Fauveboy — Sun, 21 May 2017 10:36:00 GMT

Yes thank you very much, im still incorporating into the design i have to use it functionally...does it mean rather than sustaining a job when you release the last button then previous xy is retriggered ?

Reply to Binary Counter on Sun, 21 May 2017 10:58:43 GMT

Fauveboy — Sun, 21 May 2017 10:58:43 GMT

logic4 is more appropriate for the instrument control for the binary counter I was aiming for something more minimal...because Im pushing in these values by hand if I press 1111 in those moments that my fingers are out of time route reads this and might send 0001 0011 ect is there a way to press the values but avoid these nuances ?

Reply to Binary Counter on Sun, 21 May 2017 11:02:53 GMT

Fauveboy — Sun, 21 May 2017 11:02:53 GMT

the only button i intended to press here was 1111 but these are the print results

Reply to Binary Counter on Sun, 21 May 2017 11:28:53 GMT

Fauveboy — Sun, 21 May 2017 11:28:53 GMT

why would print show these results to the equal to condition? however banging a normal message it seems to return true for without a problem ?

Reply to Binary Counter on Sun, 21 May 2017 20:32:56 GMT

whale-av — Sun, 21 May 2017 20:32:56 GMT

@Fauveboy Post above........ No method, because in joining the floats in a message the result has become a symbol......... and logical operators don't know what to do with a symbol.
You need to add them up.........
(((It will be easier to use [expr].......!!!!)))..... to do the adding.

Sorry to have butted in on this thread!!!
Post 2 before......
In versions 3 & 4 the last job that is still active (true) is re-triggered on a button release. That is what you were looking for a while ago (ageing), but it does not have to be so........

Just delete the matrix of [xytog3]'s......... as that is the part re-sending the "last" value (held button).
Lots of other stuff becomes irrelevant as well......... logic6.zip
David.

Reply to Binary Counter on Sun, 21 May 2017 16:19:53 GMT

Fauveboy — Sun, 21 May 2017 16:19:53 GMT

okay yes I see....and with the binary is there no way to maintain the combo of 0000 the benefit was going to be with just four buttons you can have 16 combinations and so more score to control other parameters with less?

Reply to Binary Counter on Sun, 21 May 2017 18:14:05 GMT

ingox — Sun, 21 May 2017 18:14:05 GMT

@Fauveboy You can also keep it decimal, like this: expr-button-test.pd

Reply to Binary Counter on Sun, 21 May 2017 17:56:52 GMT

ingox — Sun, 21 May 2017 17:56:52 GMT

On a more general note: With your button grid, i would take another approach:

Each button would have a unique button id, derived from x and y.
In a table, each button id is assigned to a section number and a section id. This can be done with [coll].
If a button is pressed, the button id is calculated from x and y and is send to the [coll] to look up the section number and the section id.
The section id and the button value (0 or 1) are routed to the section in the pd code where they should be processed
Do stuff

This way you can make different layouts for the grid, send each button to the section where it should do anything and don`t have to worry about x and y or rows and columns in each section anymore.

Reply to Binary Counter on Mon, 22 May 2017 15:12:24 GMT

ingox — Mon, 22 May 2017 15:12:24 GMT

This should already work for your grid (at least for the last 4 buttons): grid-layout-test.pd

Reply to Binary Counter on Sun, 21 May 2017 19:55:26 GMT

Fauveboy — Sun, 21 May 2017 19:55:26 GMT

Thank you this works really well....and regard the coll is it always written by had or can you process numbers into it? It would be cool to save a configuration to then up load...

Reply to Binary Counter on Sun, 21 May 2017 20:06:43 GMT

ingox — Sun, 21 May 2017 20:06:43 GMT

@Fauveboy yes, you can write it by hand, with pd messages and save and load the contents to a textfile. So you can even make your layouts with a text editor or with libre office calc + text editor.

A little bit of work each time, but most flexible.

Reply to Binary Counter on Mon, 22 May 2017 15:07:03 GMT

ingox — Mon, 22 May 2017 15:07:03 GMT

With this little trainer you can write the layout directly from the grid: grid-trainer.pd

Reply to Binary Counter on Mon, 22 May 2017 12:00:35 GMT

Fauveboy — Mon, 22 May 2017 12:00:35 GMT

I typed the numbers out in a text file and copy and pasted into the coll, it asks to save changes however when I click yes and open it back up again theres no data in there?

Reply to Binary Counter on Mon, 22 May 2017 13:32:51 GMT

Jona — Mon, 22 May 2017 13:32:51 GMT

you need a message "write coll.txt" for saving. and "read coll.txt. when you open again. or you call the patch "coll coll.txt". instead of coll.txt you can use any name, you just need to save it as a txt file. or just use 1 as an argument then its saved in the patch.

Reply to Binary Counter on Mon, 22 May 2017 14:35:13 GMT

Fauveboy — Mon, 22 May 2017 14:35:13 GMT

so i have a textedit file in the same directory called untitled.rtf but im getting error messages from the console when I press the message read. And im not yet getting a result with the write message?

Reply to Binary Counter on Mon, 22 May 2017 14:37:47 GMT

ingox — Mon, 22 May 2017 14:37:47 GMT

@Fauveboy maybe because rtf is not text. its rich text, which is bad.

Reply to Binary Counter on Mon, 22 May 2017 23:31:53 GMT

Fauveboy — Mon, 22 May 2017 23:31:53 GMT

brill! got it

Reply to Binary Counter on Thu, 25 May 2017 11:33:59 GMT

Fauveboy — Thu, 25 May 2017 11:33:59 GMT

Problem with the binary design.....I im using th binary Base -2 column to represent the four toggles Im using to count... graph to illustrate. currently im using "combination that equals the decimal Base - 10 no. 1 or 2 for oct+ and oct - , on a chromatic keyboard. I then need to use "3" to trigger an LFO which is a combination, of the combination that make 1 & 2. however it means that when i want to get to the LFO trigger i jumps through the jobs of 1 & 2 change the octave im on when i need a bit of tremelo... this area of the patch is receiving the 1 and 2 to change the octave ....

Reply to Binary Counter on Thu, 01 Jun 2017 18:30:28 GMT

Fauveboy — Thu, 01 Jun 2017 18:30:28 GMT

im using the binery counter to select different values on the ADSR but when i select 2 for some reason it doesnt change the values in the number box after 3?

Reply to Binary Counter on Sat, 03 Jun 2017 07:51:08 GMT

Balwyn — Sat, 03 Jun 2017 07:51:08 GMT

You should use [sel 2 3] in place of [== 2] and [== 3] and replace the toggles with gui bangs to visualise the result.
Logic operators and gui objects like toggle will output bangs for both states.
And the order the wires were connected determines the order of operation.
Use [trigger] if the order is important [trigger] fires right to left eg. [t b f] if a float is sent to the inlet, that float is passed to the right outlet and then a bang is sent to the left outlet.