narcode / codeklavier Goto Github PK

Sorry- i cant get the Kaboom to happen. It doesnt register result 4...

I would like to see which shape Im in when i change trees. Now i see the new or selected tree, but not its shape.

The next shape function should also have a previous shape function.

THANKS CK MASTERMIND

2 versions crashed:

• text typer
• cklaculator

Make it possible to change the toggle key via the default setup ini

It would be great if the display could open on the secondary screen rather than the primary and take the appropriate dimensions. In performance, it is much better to keep the primary as the computer and only show the display.

Thanks

Divide conditional 2 in:

conditional 2: range > n

conditional 3: range < n

Dear CK Mastermind,

Here's an error that came up during my playing. It came up when i wasn't paying attention to the code and was more jamming, consequently making non-sensical 'equations'. It's difficult for me to reproduce but periodically stuff like this does happen so i think it's worth looking into. Of course we do this in Karlsruhe.

WIth many thanks from the ever grateful CK user and tester.
CKALc crash CKAR.pdf

Hey, I'm graphic designer and my aim is supporting open source projects and make my portfolio better. So, I can contribute on your project with making logo design. I am waiting your feedback! Have a nice day! :)
@narcode

Best Regards,
TJ Ulises
Visual Communication Designer

I propose to move to a clear git-repository structure. The master branch should be the one of the latest release of a stable version. A dev branch is where all the magic happens and we'll use feature branches whenever necessary. NVIE wrote a beautiful blog about a good workflow.

What happend to the development branch? I cannot submit a pull request. Or did I miss a big change?

Countdown for timer in the conditionals in terminal would be handy

When conditionals post it should look

Cn - Rn - Time to go - Loop time

At the moment we are using the very ugly:

currentdir = os.path.dirname(os.path.abspath(inspect.getfile(inspect.currentframe())))
parentdir = os.path.dirname(currentdir)
sys.path.insert(0,parentdir)

To fix the python search path. Perhaps we should move these inside the CodeKlavier folder.

Perhaps best after fixing issuer #40

Link to doc on google drive https://docs.google.com/document/d/1R8HLGy5L7mVDTv24spDOyfY-K6r1ocYNvORk_Kb_ucg/edit

Titles need to stay

The shift should say "wrong note" and then the shift. This should also be (eventually) replaced - perhaps with next result.

Sometimes chordal motifs are recognized when not really being played.

Include delta times in the function and analyze the cases where the motif is being recognized but its not.

Investigate why and compare to JS version and v0.1 (hello world). I noticed because of the fan noise and i hadn't noticed this before. Might have something to do with latest additions??

Perhaps when I map a mini -motif, the current value of that variable can be printed in post window?

Every time you start a CodeKlavier session, you have put in the midi-instrument and the settings and stuff. Let's use configparser for that!

Suggested workflow:

• starting CodeKlavier will ask you to give the filename for the configfile.
• leave blank to use the default
• add a 'configFileCreator' to write an appropriate configfile and save it

change createConfig to createConfigFile here and here

Dear CodeKlavier master,

Looking at the latest release, I realised there is no link to the corresponding SC directory. I think this is very useful otherwise it is difficult for users to come back to these versions.

With many thanks,

Your trusty mush brains CK user

The note counter isn't counting when switching to "hello world". I actually think we had already fixed this at one point but can't remember.

Conditional 3 doesn't handle results 1 and 2 properly. it just prints the "less than an 8ve. Nothing happens" even when the condition is met. This is only true for results 1 and 2 (stop snippets). The gongs work perfectly fine. Conditional 2 also works correctly.

yeah, make sure they are written good. @wooloogooloo can help???

1. All the hello world text is printing in the middle column of the 3 display. I think it's best when it doesn't print anything

2. When switching back and forth, the conditionals can go whack and I made it crash once but i think this is because i was trying to break it going back and forth. We can probably ignore this for now (see attached)
   

3. At one point Motippets stopped responding...I think it happens when I use the counter conditional- it crashes but not the other threads.
   

Create a masterscript that:

• waits for user input
• user can selection options:
  • quit
  • run any of the CodeKlavier works (at the moment: HelloWorld and Mottipets).

This is probably easiest to realise when #39 is done.

The tremello numbers keep printing even if there are no changes

Perhaps it's wise to put a limiter on the duration these stuks can grow to since I had a run when they went much longer than the designated finishing sample. I dont think however the gomb should kill the other mini- samples- but they should just be sure to not get too long

I THink it would be nice if the snippet2 could go to the earlier values for the variables

A few weird things that happened:

1. Whilst I was playing my prelude before launching snippet1, I somehow quit the process. It happened twice but I suppose it's possible I quit it accidentally myself in transitioning from terminal to atom.
2. The snippet1 won't restart after the conditional has been evaluated.
3. The tremolo's are over sensative and particular in L can give a value even when I've played it many notes apart.
4. The tremolo's played before the mapping of a minimotif already gives the value for that minimotif.

I think the snippet 1 should last much longer after the Gomb! Also, I miss the Huygens.end in this context. Would be cool if snippet 2 had a fade out. These are my current feelings about it. It's super elementary I know but I can't find the file to make these adjustments. Sorry

crash again although I got abit further... here's the error Press Control-C to exit.
Bye-Bye :(
Bye bye from CodeKlavier setup :(
Traceback (most recent call last):
File "motippets.py", line 154, in
tremoloHi.parse_midi(msg, 'tremoloHi')
File "/Users/Anne/codeklavier-python/CodeKlavier/motippets_classes.py", line 155, in parse_midi
[self._memory[2], self._memory[3]], 'hi',
IndexError: list index out of range
anne:motippets Anne$

Clean the quitting process. Now its 2 steps (at least in Presenter version)

Can you balance out the volume of the 2 snippets. Snippet 1 appears to be much louder than Snippet 2.

Are we ready for a new release and merge into the master branch? What is missing to make this happen?

The prototype motippets needs to be able to send the code from the LH ✋ to one screen/window and the RH ✋ to another one for the sake of clarity and readability in the code.

any ideas @borrob ?

The tremolo's played before the mapping of a minimotif already gives the value for that minimotif.

The readme from [hello world](codeklavier/hello world/README.md) has some old references. It refers to the 'rtp' version and the 'v4' version. Both files do not exist anymore.

Can't get it to start. When I give note for device ID everything crashes. It says it's line 144

File "motippets.py", line 144, in
if message[2] > 0 and message[0]:
IndexError: list index out of range

Hope it's an easy fix

Discussion conditional implementation Motippets.

1. Have a note clicker that when pianist has played 2000 notes, there is a bang and killl all to SC (like we did for Bilbao).

I think it would be nice to have volume control for snippet 1. Can we add an extra variable that controls the volume?

Dear CodeKlavier guru, will you move the delta time thresholds to the ini file? For quick adjustment

error Terminal Saved Output.pdf
attached the error

running ./codeklavier.py -c default.ini just exits. Perhaps we should print a message that the user pick a piece to play, or run interactively.

Frequent sever disconnecting leads to CKALC crash.
Terminal output attached
CKALC error.txt

Hey,
we discussed a different setup of the motifs in motippets so that it is possible to add variables and motifs in one place, rather than changing it in a bunch of places.

This is useful for the addition of new motifs for variables, conditionals, results etc.

This is not really a conditional. It's more like a self destruct button

codeklavier.py doesn't write a configfile
helloworld.py does let you select the port, but strands on the device_id

Functions are retailing the stack so anne cannot make free numbers.

GO GO Go Felipe!

Note: On Ckalc branch. The lambda calculus is fine, it's just a display issue.