Re: [SIP-devel] new interf_demo + pbs
Advanced image processing toolbox for Scilab on Unix/Linux/Mac OS
Status: Beta
Brought to you by:
ricardofabbri
From: DRUEL J. <joc...@li...> - 2003-07-01 09:40:26
|
Hi Riccardo, I hope your exams were all right. I send you a new version of the gui: Le Mardi 1 Juillet 2003 00:47, vous avez écrit : > On Sat, 21 Jun 2003, DRUEL Jocelyn wrote: > > 2) 2 functions to take pictures from a video camera using xawtv. We use a > > cheap miroPCTV for this (about 50$). This works on linux only of course. > > Cool. I suggest that you check if the xawtv command is available > before calling it. But this is not very important. > Good idea. I did a message if we're under windows but I don't know how to test the existence of xawtv from within scilab. There was a syntax error in the function snap1: 2 , instead of 1 in the name=xgetfile... This is now corrected. > > 3) modifications to use gray_imread: > > I replaced many gray_imread by gray_imread/2555 because I had problems > > with displaying or tracing profiles. I don't exactly know why. > > This is due to the fact that you read your .jpg images, which are > pseudo-color (indexed). What you probably did before imread was to use > the index of the image, which points to 256 different colors in the > colormap. The colors in the colormap goes from 0 to 65535, so you must > divide by __257__ to get the 0-255 range (65535 / 257 == 255). > ok, I changed my division factor from 255 to 257 > > The gray_imread function is much much slower than imread when I read > > grayscale pictures. A test on my box gave: 2.4 and 0.26 (estimated by > > timer()). That's a pb for me (specially as I read several images to make > > some calculations). > > gray_imread (because of im2gray) is really very slow, I haven't > noticed that before. I optimized im2gray to eliminate a for loop (see > attachment). gray_imread is much faster now. In scilab any loop over > an image is prohibitive :-((. It is ok just for "thumbnail-sized" > images, when we need to prototype an algorithm. > > I could implement im2gray in C, but the trick I done in gray_imread > saved me some development time. But if it is still slow, please tell me. > The speed is now all right for me. I have a pb with the mogrify function: I tested b=mogrify(image, '-draw circle 100,100 150,150') the answer is: non conforming drawing primitive definition I saw that "draw" is the only options which requires a string. Is it the problem ? Well, if you have a solution, maybe you could add it in the examples of the help page. Best regards Jocelyn -- Powered by Linux |