Needed to do today:
- Need to ‘bang’ through a single number without it constantly updating.
- Send messages from Flash to Max.
- Playback from collisions in Flash.
To start with the Beta that had been the focus of our efforts had ‘broken’ as certain tweaking had meant that a few files had been edited for the worse.
After much painstaking research into how to only bang through a number once, the help of Stewart was enlisted and he helped us understand the logical way to do it, then we helped him understand why that wasn’t possible in Max. So together we overcame the ’single number bang’ issue and the project was then able to progress. (See 1 Below.)
Thankfully sending of information from Flash to Max didn’t appear to be a difficult one but the reference was less than comprehensive. The problem was not sending the information as we could ‘print’ the information in the Max window to confirm that information was transmitting, it was getting that information into the patcher window and then doing something with it.
It was the [remote] function that was needed and when turned on allowed a receive object reference in the Flash actionscript to receive a message. Further problems arose when Flash tried to send the ball number on collision as you can just insert the variable so 10 different functions needed to be created to send each number when called. (See 2 Above)
This linked to the playback patcher in Max, which was straight forward linking to the already existing playback setup.
Here is a video of the RC1 in operation in its proposed display space.
See also: http://www.youtube.com/watch?v=SZ7EiZLmqIM
I have finally solved the problem of the ‘bang’ going off continuously in the MaxMSP window (and consequentially making everything else after it go off continuously) by asking for help.
I posted a question on the Cycling 74 forum in the hope that somebody may have had a similar problem or someone might share their insights. What actually happened was that less than an hour after posting I got the answer… and it made me feel like such a n00b.
I asked the following:
“I am having a problem using a sound analyser with Max.
The aim is when a number box goes above a certain value (say 25) then ‘bang’ once and only once until the number goes above 25 again.
The problem is that the number box is constantly updating (from the sound analyser) and when it changes number but remains above 25 it triggers another ‘bang’. So due to updating continuously it is ‘banging’ continuously. I need it to stop after the first ‘bang’.
This is for my final project this year and is supposed to be displayed at our broadcast event on Thurday.
Any help would be greatly appreciated.
Thanks“
The response was this:
“Hi.
Try this:
———-begin_max5_patcher———- 396.3ocwT0zbBCBD8L4WACmsN.ZzZOzC9WnyzKcb5PRnJcR.m.
YpsN9eu.ILVa8iXp0dYIr6xx681vtNBfRTq3ZD7N3SP.XcD.3c4b.
Z1CPErUo4LsOMjrpHgWh5UG5EkznEevcglzG23cIyjtPHm+bIO
0TWbBFaCCGMxYi8eSF2GCm0bDQlu5pjWuYbn31qRHy4F+ES1
5TUYBdoeAGRVgGGnoBi1TxYEvG4kL3CLoFNUkmEpa84MuujW
iMjPZP8fnDlbNBNykzlnHmoWKEkjJiQIQmj9jI25Vn3fce7O9L3
O4PTp6bQxeyhh.FL7UdJfz7bHoqscB022GN7X88A6k2z+v9tW
jrM9KpPcOjF2YcBScKCNpNQOCchbwdebIkHkjWK8cTkF4Uo33
ioRj+s+l94SOO9P4B42G054ny+tZnVUUlFJayHQ3VVlw0FgjYD
1QNaygtSNKDYYbe3fdVHxVprcxFHbf9YaQDoEHJ9phH63CH
4DHhrSNWCDgaAhtdZDsEHZvu.Q1Mah9z6gIOd
———–end_max5_patcher———–
Ciao“
After some googling and download of the trial version of Max 5, I opened the file and discovered it worked.
This is what it looks like in a patcher window in Max 5.
The answer is a small yet surprisingly powerful object called [onebang] which only allows one ‘bang’ if it meets the requirements of the object above, in this case ’sel 1′.
Below is an image from Max 4.6 which I am using for the project.
1: The [onebang] object in action.
2: Selection for playing back the sounds – simply select a number and ‘bang’, this will be linked up to flash to pull the sounds out and play them when an object collides with another.
