Back to Square One

Unfortunately, the visit to my university's IT department was fruitless. If anything, the situation is MORE confused than it was before. No one was able to puzzle out the problem with getting Silo running on the school's server, so it looks like this entire path may be a bust. I've sent one last e-mail to the developer of Silo, but I'm reasonably sure the problem is with the apache configuration of the school's server.

My meeting with my advisor today was spent brainstorming some new possible paths for the chat logging part of the grant. It looks like there are two equally viable paths we could take: one more complicated, but somewhat quicker in transferring data, and one that is actually quite simple, but contains many possible slow down points. Before Thursday I'll be diving deeper into LSL in an attempt to get chat data formatted as a URL to be sent to a PHP email form. With any extra time, I'll also be looking into applescripting.

My video tracking patch is more bogged down than ever. It's so bad that I'm only getting one voice out of my poly~ object. I've decided that I'm going to use two separate Max patches for the video tracking portion of the project. I'll be splitting my current patch up into two parts, the Jitter part and the MSP part. One patch will run in Max itself while the other will be in Max Runtime, and the two patches can communicate through netsend and netreceive. I'm hoping that, as others have experienced, my dual-core processor will be more efficiently used by splitting it up in this way. Depending on how much time the LSL scripting takes me, though, these changes may not be implemented for a few more days.

- M