Hallo, shreeswifty hat gesagt: // shreeswifty wrote:

I recently recall a mention of mtof.txt

mtof.txt is a simple list of frequencies, where each line corresponds to the midi frequency.

You can brew your own with this patch snippet:

[127( | [until] | [i 0]X[+ 1] <- counter | [mtof] | [add $1( | [textfile]

Ciao

Frank Barknecht _ ______footils.org__

Hallo, Tim Blechmann hat gesagt: // Tim Blechmann wrote:

...

...

I recently recall a mention of mtof.txt

mtof.txt is a simple list of frequencies, where each line corresponds to the midi frequency.

|mtof(~)| is completely hardcoded, so it's not possible to change the behaviour ...

I didn't intend to imply that.

I just described a way to recreate the mtof.txt as it was included in the docs of earlier Pd versions as an array source in a midi example patch.

mtof.txt just contained a mapping of midi notes (as line numbers) to frequency values as a source file to be read into an array. This array then can be used in e.g. [tabread] to emulate [mtof]. Of course with [mtof] this usage is redundant. However of course you can [tabdread] other mappings which you write on your own. But then you don't need mtof.txt

This probably is the reason, why mtof.txt isn't included in current Pd versions, AFAIK.

Ciao

Frank Barknecht _ ______footils.org__

Hey there,

I reported this memory leak problem on Linux about a year or two ago.

Add considering I have an installation that uses pix_image under linux up for 250 days without a reboot. I suppose this could be a new problem that was resolved under linux some time ago. I remember Johannes replied to my report, but I can't remember anything else about what happened, Only Etienne reminded me!

Ben

Hi

We will look into those problems. Thanks for the report.

For another approach, try loading images with pix_movie/film and just re-trigger the first frame over and over. Also, consider making the multiple image sequences into a single moving using QTPro or similar application and stepping through the frames. This method is probably the fastest way to get images to the screen and also will allow for mixing images and movies using the various pix_ objects.

cgc

On Oct 27, 2004, at 9:50 PM, Etienne Desautels wrote:

...

Hi all,

I did for an interactive video installation a pd-GEM patch, a kind of video sequencer. I'm on mac os 10.3.5 with pd 0.37 and GEM 0.90. I use pix_image to load images on a rectangle and I have 2 problems with it.

First, pix_image have a system to keep each loaded image in the computer memory for using it later if you reload the _exact_ same image. But if you load a lot, say hundreds, of images, that will use a lot of memory. I'd like to know if there's a way to avoid this, a way to release this memory ?

Secondly, I think there's a bug in pix_image (and pix_multiimage also). It's suppose to use the data image in the cache if you reload the _exact_ same image, but it doesn't seem to work. That make my first problem even worst because each time you reload the same image, gem will put it another time in memory, so the memory will grow indefinitely. I did the test with pix_image and pix_multiimage and on 2 different computers (powerbook 667 with an ATI and a dual G4 1GHz with an nVidia). Each time I reload the same image, I can see the memory usage of pd growing. The only way to release the memory is to quit pd. It's not an acceptable solution for me because my installation is running all day long and at some point PD hang because there's no more memory and swap.

You could try it by using the help patch of pix_image and keep reloading the same image and watching the memory usage of pd in top.

Thank you for your help.

Etienne

---

GEM-dev mailing list GEM-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/gem-dev

-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support.

---

GEM-dev mailing list GEM-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/gem-dev

On Oct 28, 2004, at 2:00 PM, Etienne Desautels wrote:

Hi Chris,

Thanks for your answer.

I just replace my pix_image object with pix_film and it works. I also send it a RGB colorspace message at loading time, this way PNGs are showing fine. Without the RGB message, JPGs are showing fine but not PNGs. Do you have any ideas why it works with JPGs and not PNGs?

Quicktime will convert YUV to RGB automagically, but not the other way around. pix_film defaults to YUV because it is the proper color-space for video and also quite a bit faster than RGB. PNG images are RGB with lossless compression, while JPEG are YUV with lossy compression applied.

cgc

On Oct 28, 2004, at 10:14 PM, Etienne Desautels wrote:

I would like to adjust the settings of the webcam (color balance, brightness, etc.) but when I send a dialog message to pix_video, the normal QT dialog open and then pd freeze. I have to hit ^-C to quit pd. Do you have any ideas on this ?

The dialog window is a failed experiment at this point. It does work if the application is a standard 'Mac app' with the expected event loop handling code, but Pd doesn't fall into that category. We have gotten the gemwin to work like a regular window and also functioning mouse events, but nothing else. I also have not had success with using Pd messages to change the parameters or video device used by Quicktime. I have not worked on the code in a while, but it's on the todo list.

cgc