Non-Progress

Well, it looks like things are at a standstill for the moment. Seems as though both the school's server and my advisor's web server have different issues with Silo that we can't solve ourselves. Zero Linden, the creator of Silo, has been a BIG help in getting us through most of our problems, but now it's all in the hands of the school's IT department. It looks like the problem with the school's server is that Silo requires access to the DELETE method to function properly, and that ability is likely disabled for very good reasons. Hopefully they'll be willing to let us poke through some of their heavy security so Silo can do what it needs to do.

My video tracking patch is still having bizzare CPU usage issues. Though the metro is driving most parts of the patch at 100ms, I'm hearing notes anywhere from once every 500ms to once per second. That is, of course, variable depending on how hard the CPU is working. Often times, I get an odd sort of galloping effect. The strange part is that this seems to happen no matter how much CPU is being used by the online community interface. This being a dual-core processor, I usually end up with Max/MSP using anywhere from 65-95%, depending on which interface I use. SL usually takes up no less than 95% (causing Max to use around 70%), while World of Warcraft uses only ~35% (causing Max to use ~85/90%). Notes seemed to come less often, if anything, running Warcraft, presumably because it is more populated and there are more people to track. One would think that with more CPU available to it, Max would take advantage and be able to process everything being asked of it. Rather, it seems to be restricting itself to just one core and scaling based on that. Perhaps the cv.jit objects don't support multithreading? I'm going to go ahead and build a polyphonic synthesizer to insert into the patch and see how the CPU behaves after that point. I suppose if that doesn't go well then I'll have to look into using two computers for this portion of the project.

- M