shaun

I'm currently working on a project making a sort of live twitter wall in jitter.

Basically I started off building the patch with already existing java externals like "searchtweet". I found that making URL requests with searchtweet caused a massive drop in the framrate for a few seconds..

To overcome the issue I've begun building my own external in C (for windows using the "twitcurl" library..) After a week of screaming at visual studio I finally managed to throw a little external together that does what need. EXCEPT...

is this something to do with how max handles web requests? Should i look into changing my object to work in the low priority thread?

I can upload the external if anyone wants a look.. (it is definitely not finished and you may need to install the "twitcurl" library for it to work..)

Basically I started off building the patch with already existing java externals like "searchtweet". I found that  making URL requests with searchtweet caused a massive drop in the framrate for a few seconds..

To overcome the issue I've begun building my own external in C (for windows using the "twitcurl" library..) After a week of screaming at visual studio I finally managed to throw a little external together that does what  need. EXCEPT...

I can upload the external if anyone wants a look.. (it is definitely not finished and you may need to install the "twitcurl" library for it to work..)


url-requests-effecting-frame-rates-from-qmetro

without knowing the specifics, my advice is to separate your video processing from your web processing, launch each patch in a separate instance of Max 7, and pass data using udpsend / udpreceive

if on Mac, I use the following command in the terminal to open a unique instance of Max: open -a /Applications/Max.app/ -nF

if on Mac, I use the following command in the terminal to open a unique instance of Max:  open -a /Applications/Max.app/ -nF


Depends on how often your sending a bang to your twitter object.

A patch I did with live twitter feeds(and searchtweet) and opengl had this problem as well, I solved it by severely reducing the amount of bangs the object received.

I just used counter and set it to 500 to get a bang when the max count was reached.

Depends on how often your sending a bang to your twitter object.
A patch I did with live twitter feeds(and searchtweet)  and opengl  had this problem as well, I solved it by severely reducing the amount of bangs the object received.
I just used counter and set it to 500 to get a bang when the max count was reached.


I'm not actually sending any bangs, just a message containing the search string..

Even a single message to my object causes the qmetro to almost freeze for a second, even with no actual jitter or open gl objects present, just the metro into an fps gui..

I like the idea of a separate patch to handle web requests.. I'll try it later.. thanks

URL requests effecting frame rates from qmetro..