SDK - compiling the delivered sln file Visual Studio
Hi @ all,
we run into big issues while trying to compile the vsbuilt which was located in the the GEM/build directory
we couldn't get the built to run, maybe someone out there had the same problems. Surfing the internet didn't give any results. One more thing to mention, within the readme file i find following:
this is the project-file to build Gem using Microsoft's VisualStudio 7
DEPRECATION WARNING
this MSVC-Project is deprecated and has not been used for a long time.
do not expect it to work out of the box.
these files have been moved here in an attempt to cleanup the project
originally these files have been located in <Gem>/src/ instead of
<Gem>/build/win-vs7, so all the paths in the project-file might be wrong
either fix the project-files or copy them over to the src/ directory
i don't do it, as i don't have a VC7 anymore (it is outdated anyhow)
It would be great if someone could give any information about that.
thank you.
MIDI weird issues with arduino + PD (not pduino)
Greetings! I have some weird MIDI issues I was wondering if anyone here have any idea about what migth be the cause of, and perhaps could offer some pointers towards a potential cure to!
I am working on a project that involves the need to get midi messages from arduino to my sound card. This project involves doing stuff in water, so we have allready gotten a wireless MIDI transmitter that works perfrectly. The trouble, however, seem to be in Pure Data for all I can understand. I am using an arduino decimilla, with a regular flex sensor as control. And the problem is:
When PD receives MIDI data from the arduino , it all seems good in the beginning, the response is quick, and all is well. However, after running only a short time, not more than a few minutes max, the MIDI messages seem to get delayed, so when i move the flex sensor, it takes a while before the changes registeres in PD. What is even weirder is that in addition to this, there seem to be like a double flow of delayed messages, where at first the "original" message comes along, and then short after, a duplicate message comes along too. So when say I bend my flex sensor, at first, the midi goes from 127 to 60, and then after a short while, jumps back to 127 and ramps back to 60 again. Sometimes they even seem to compete and garble eachother at the same time, with values jumping all over the place. I find the irregularity of the whole troublesome affair really frustrating. I am still a noob with arduinou so even though I do not believe the problem lies in the arduino, I cannot be sure. The reason I believe it is in PD is beacause all i have to do is shut down PD and start it up again, and it works nice.. a few minutes. And needless to say, in a live setting, you don't want to go up and restart PD all the time, especially since I will be submerged in a pool during the performance.. (have allways used Pduino before the few times I've used it with PD, but that is not an option this time)
I am working in Windows XP with a Edirol UA-25 sound card btw.
The arduino code i'm using to produce MIDI was borrowed from this program;
http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1165833586/0#2
Anyone had similar problems with MIDI in PD? I know the warning says "MIDI is dangerous in PD" but... I have used CC messages before with no problem at all. This is so weird...
Any clever suggestions would be hugely appreciated.
Call for projects - make art 2009 - what the fork?!
_
_ _ ____ _ _ ||
| | | | ||_ | | || | |
| || | | || | | ||| | |_____
| | || | | | ____ | | | | |
| | | | | | | | | | || | |_
|| || || || || || ||
|| ____ _______ _________
|| || | | | | _
| || | | ||| | | || ||
from | __ | | _ | | |
7 to 13 | | | | | | ||__ ||
DECEMBER 09 || || || |_| ||
MAKE ART 2009 - What The Fork?!
distributed and open practices in FLOSS art
--
CALL FOR PROJECTS
--
make art is an international festival dedicated to the integration of
Free/Libre/Open Source Software (FLOSS) in digital art.
The fourth edition of make art -- What The Fork?! distributed and open
practices in FLOSS art - will take place in Poitiers (FR), from the 7th
to the 13th of December 2009.
make art offers performances, presentations, workshops and an
exhibition, focused on the encounter between digital art and free
software.
We're currently seeking new, innovative FLOSS works and projects: music
and audiovisual performances, presentations, software demos, and
installations.
This year make art focuses on distributed and open practices in FLOSS
art. 'What the fork?!' is about decentralisation. Forking is the new
black. Forking, copying the source code of a project and continuing
work on the copy instead of the original, used to have a bad reputation.
It would split a project and its developer community in pieces, leading
to different, often incompatible, projects. Wasted effort, rivalry and
developer fights were all associated concepts. This is history. Forking
a project with the intention to compete with it is another story, but
the freedom to fork enables quick implementation of features and
customization, bypassing acquiring committer status, bugfix or feature
request protocol, working in a distributed way, together with others but
not necessarily towards one goal, working from one source,
cross-fertilising, inspiring, copying, patching, improving,
experimenting, changing direction, and merging. This practice is boosted
by decentralised software development tools, such as Darcs, Mercurial
and Git. It's not about quick hacks, but about creating room to
experiment, letting go of the one working copy and creating a
multiplicity of ideas.
Deadline : 15th of July 2009.
For more details, please visit http://makeart.goto10.org/call
--
:*
Control analog sensor data in PD?
damn godinpants, that was exactly what i needed!! damn i'm excited now, its starting to work out! i also divided the soundfiler info by 100 and multiplied it to the signal before the [pack 0 100]. that made sure it worked for the full sound file instead of just 0-44100.
i have two sensors. one sensor is the scratcher: the soundfile is played fast/slow depending on how fast i move an object closer to the sensor. I dont know if that makes sense. is it possible to have the other sensor slow down the speed of the playback??
for instance, i have a 10 second file. i made the vertical slider range from 20-100 because that's the range the signal is clearest. if i move my hand slowly closer to the sensor, the 10 second sound file plays forward. i want the other sensor to "zoom" into the vertical slider and make, for instance, the 20-30 range the range that the 1st-scratcher-sensor is working with. if my left hand is using the 2nd "zoom" sensor, and my right hand is using the 1st "scratcher" sensor, my left hand will pinpoint a section of the sound file that i want my right hand, the scratcher, to play back and forth.
Whats the best way to do that? (sorry for the long detailed messages, i just try to make sure you guys understand my situation)
Random numbers, timers, projections
Hey everyone.
You'll have to excuse me 'cause I don't have a clue about PD, but need to use it for one of my current projects.
Basically, I want to project some text from my computer onto a blank canvas. I want to use a pressure sensor to detect when a user is sitting down. Once it knows someone is sitting down, I want the text to change.
From here on, I want the text to change after a given amount of time... say... 30 seconds for now?
When it gets to the last slide of text, I want it to do nothing other than display this line of text, until the user places their hand over an LDR. When the user's hand is placed over the LDR, the light will be reduced to a certain level. Once this level is reached, I want PD to time for 15 seconds, and at the end of the 15 seconds, illuminate any random combination of light bulbs and set off a rumble pack beneath where they have put their hand. If the user removes their hand before the 15 seconds is up, I do not want any of the light bulbs to illuminate, and I do not want the rumble pack to go off.
[When certain bulbs are illuminated, I want certain lines of text to be projected.
Say bulbs 1 and 2 are illuminated, but 3, 4 and 5 are not. I would like text to be projected that says "Bulbs 1 and 2 are illuminated. Bulbs 3, 4 and 5 are not". Or say Bulbs 1, 3 and 5 are illuminated, I want text to be projected that says "Bulbs 1, 3 and 5 are illuminated. Bulbs 2 and 4 are not."]
If the user stands up at any point in time, removing pressure from the pressure sensor, I want the initial line of text to be displayed on screen again, and everything to start over.
Sorry if this sounds very complex, please let me know if you can help out at all.
Edit ::
If it makes it any easier, you could ignore the bit that I've put in the square brackets. Instead of this, I would just like one more screen of text to be projected when any combination of the bulbs are illuminated.
Control analog sensor data in PD?
Hi! There is so much documentation online, but i still cant seem to figure this out:
I have a sharp gp2d120 sensor hooked up to my arduino. The arduino has firmata 2.0 installed so that it can communicate to PD (using pduino). I am getting a steady stream of voltage data from the sensor (as you can see from the the 4th analog pin in the screenshot). I'm trying to figure out how i can turn this data into something i can work with. Or maybe i need to learn how to work with it. Ultimately i want to control the frequency of a sound file based on the voltage output of the sensor (which is relative to the proximity of an object to the sensor).
So how can i convert this analog data into something i can work with (some data type that i can [delay] and that i can output to [dac~]? Do i need to use [mtof] to convert it to frequency? Do i need to turn it into a MIDI device somehow? [ctlin]? [tabread4]? These are just some objects that have come up after i searched for solutions, but i don't know how to execute it all.
side note: is it possible to set the sample rate of arduino in PD? the sensor works best with 10ms intervals between each sample.
Sending message from pd to flash
I have been trying to send data that i collected from a external sensor in pd to a flash application which will in turn trigger animations and sound based on the data collected from the sensor. I have so far been able to get data from the external sensor onto pd, build up connection between pd and flash using the flosc that i downloaded. I was able to send messages from flash with flocs file to pd and pd is able to receive it. but i have been having problems with sending message from pd to flash... i dunno if the prob lies with pd not able to connect to the port where my flash is at or whether is it flash was unable to receive the msg from pd ...
is there anyone who has a workable example that is able to send message from pd to flash ? I heard pple talk about flashserver but looking at the website they only mention connecting to max/msp ... so is there a possiblity to connect pd with flashserver ?
this is my first project using pd ... so i still have alot of doubt in using the software... please give me guidance and examples to help me through ...
i have a screenshot of the patch that i edited to fit my project ... please tell me what is wrong with my patch ... thanks
How to organize hard disk space for older projects compatibility
Thanks you guys for reply.
For sure the advice from Obiwannabe is important because at least for the early period of its life, an abstraction or a self made external can be deeply modified.
But, actually I like to make better and better my abstractions, for example in a dsp or synth by adding some new switch, slider, parameter....
Abstractions may contain obscure errors.
Therefore, sometimes I have to change the library folder, and this increases the performance of new projects. On the contrary the old ones are broken.
If you use relative paths referring to your abstractions/externals, then by make copies of used files in a separated project folder, you fix all the compatibility problems because you don't change more those files unless you want.
Of course you have not to copy the audio files that can be stored in a well defined folder out of the project folder.
When you want upgrade an old project with new abstractions/externals you can copy them from the pd-development-folder and easier fix the compatibility problems.
This method helps you also when you want share a project like this with someone else because it gathers all the dependences.
Think for example of a recording project, a live performance, a course lesson where you have to show something that perfect works...then after some months you have to do the same thing but now your develop-environment is changed.
How to organize hard disk space for older projects compatibility
Good question and ideas Enrico.
I started by realising quickly that abstractions were a potential problem after getting burned early. For the first year I used Pd I never used an abstraction, always sub-patches.
I think this is good advice for beginners, to spend at least 3 or 4 months only using sub-patches. It keeps everything in one file and makes projects easy to manage.
Later I developed discipline to manage projects with abstractions. By prefixing abstractions with a simple 2 or 3 character to show where it belongs. So most of the abstractions in the drum synth folder were called [drm-snare32~] etc.
Later I learned that certain ones were finished, familiar and ready to move into a globally visible folder. At that time I remove the prefix so [drm-snare32~] would become the definitive [snare32~]
and then I did search and replace in most the files.
I know I can never change the abstractions in my library folder so all the permissions might as well be set to read-only.
Aside from that, I follow normal project folder discipline and have a separate folder for every project with all the resources in there. Rarely ever do I refer to objects in another project, always copy them to make a fresh start (and add prefixes to show where they belong).
Still get broken projects from time to time, but they're easier to fix now.
How to organize hard disk space for older projects compatibility
Hello to everybody,
I would discuss with you about some good philosophy for organize PD patches in order to have the most number of projects ready to work in a given time.
I have an intensive work on PD for digital music creation and development. For me is usual spend a lot of time when I re-open an old working project and find it doesn't work now, because in the meanwhile I have optimized some self made abstraction or external.
If you use the same abstractions/externals in more than a patch (I hope;-), often is necessary and useful make them better to improve your current projects, but the old project architectures now are probably out of order... THIS IS A BIG PROBLEM FOR ME.
yesterday I found out a trick, perhaps many of you know it or have a better method.
Is possible to refer to your patches from any part of your hard disk by writing a path on the actual object you create inside PD e.g.:
C:/pd/synth/myabstraction [example of absolute path]
../synth/myabstraction [example of relative path]
So if you want to use the object delay you have in your computer, then make a new object and write on it [C:/pd/dsp/delay] if this is the path.
MY METHOD is this:
I have a folder named "pd" and subfolders named synth, dsp, external etc... I refer from every new project I do.
---> this is my environment for development
Every time I start a new project I save it inside this folder and I refer to the abstraction/externals I use by writing RELATIVE paths on the new objects.
When the project is finishes (ok, works is enough I simply save a pd folder CLONE in another part of my hard disk and I name it with the project name.
In this way I continue to develop the "pd" folder, make new projects, BUT the old ones are well separated and... EVERY TIME WORKING for me.
what do you think about?
Have good pd projects !
Enrico