-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added information on the event type 'Square', and the new save/load feature
- Loading branch information
1 parent
73f2b76
commit 4bdcdee
Showing
1 changed file
with
21 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,20 +24,34 @@ MIDI - First install the free Loopbe1 software and make sure it is running. Next | |
|
||
|
||
Event types: | ||
|
||
Gather - occurs when all visible balls are close enough together | ||
|
||
Ungather - occurs when balls are no longer gathered | ||
Location - uses the average location of all balls and translates it into a midi CC(slider). | ||
Works both vertically(locationv) and horizontally(locationh) | ||
Speed - uses the longest distance between any 2 visible balls and converts it into a midi CC(slider), the effect | ||
this has is that bigger, slower, juggling can be used to slow down music and smaller, faster juggling can be used | ||
to speed it up. | ||
|
||
Location - uses the average location of all balls and translates it into a midi CC(slider). | ||
Works both vertically(locationv) and horizontally(locationh) | ||
Speed - uses the longest distance between any 2 visible balls and converts it into a midi CC(slider), | ||
the effect this has is that bigger, slower, juggling can be used to slow down music and smaller, | ||
faster juggling can be used to speed it up. | ||
|
||
Peak - if a ball is seen above a certain point then its horizontal location is transalted into a midi note. | ||
|
||
Square - occurs when a ball has been seen in the square for a certain amount of time(user defined), so long | ||
as enough time has passed since that square has been triggered. The format for indicating these times are as follows: | ||
Square#,midi,min time between triggers, required time ball must remain in square to trigger | ||
EX: Square0,0.5n,0,0 - can be thrown square and will continue to send signals the whole time in the square | ||
EX: Square0,0.5n,500,0 - can be thrown through square and only send 1 signal | ||
EX: Square0,0.5n,500,600 - can be held in a square to cause trigger, but throwing through the square wont cause a trigger | ||
|
||
|
||
Notes: | ||
-The current tracking system relies on glowing juggling balls and a dark room, the code looks for the largest | ||
white objects it sees and assigns a tracker to the 3 largest. The avereage of these trackers positions averaged | ||
over time is shown as well. | ||
white objects it sees and assigns a tracker to the 3 largest. The avereage of these trackers positions averaged | ||
over time is shown as well. | ||
-The syntax in the main textfield must be exactly right or it might crash. | ||
-saving/loading will store all event types currently in the scrolled text in a text file(*saveName.txt), it also saves the | ||
positions of any squares currently on the camera in another text file (*saveName*+sqr.txt) | ||
|
||
Any questions or help setting it up or anything: [email protected] |