Processing Forum

NURBS looks weird in 3D DXF exported plane

[0 Replies]
- 15-Jun-2013 04:14 AM
- Forum: Programming Questions
Hi guys, I'm trying to make something that should be simple, but it's driving me crazy.

I'm using the code below to generate a 3D plane, it's basically a list that contain random height values, and then applies them to a fixed grid.

It actually works. My problem comes when I import this into Cinema4D and try to apply NURBS to get a softer plane; it goes crazy.

I tried OPENGL and P2D, as well as getting the DXF and exporting it to another format (OBJ, 3DS, VRML, DAE...) before applying the NURBS... but I get always the same two results:

a) Or the plane is made of independent polygons, so it NURBS every polygon independently, so you get something similar to a plane full of bezier drops.

b) the plane is made of strips, so it NURBS the strip along one axis, but the connection between strips (the other axis) is not done, so you get kind of holes plus sharp angles between strips.

I don't think is a problem of the librar (so I'm publishing on the general section) but a problem in how the plane is constructed.

Am I missing something?

I also tried placing everything between a beginShape/endShape expecting to get one whole object instead of a group of them, but it also doesn't affect.
2. beginShape();
3. for (int i=0; i<waveMap.length-1; i++) {
4. beginShape(QUAD_STRIP);
5. for (int j=0; j<waveMap[i].length-1; j++) {
6. y = waveMap[i][j];
7. vertex(x, y, z);
8. y = waveMap[i+1][j];
9. vertex(x, y, z+spaceZ);
10. y = waveMap[i][j+1];
11. vertex(x+spaceX, y, z);
12. y = waveMap[i+1][j+1];
13. vertex(x+spaceX, y, z+spaceZ);
14. x+=spaceX;
15. }
16. endShape();
17. z+=spaceZ;
18. x=0;
19. }
20. endShape();
Some insight would be appreciated

mouseDragged() not working if CONTROL key is hold

[2 Replies]
- 10-May-2013 04:01 AM
- Forum: Programming Questions
Hi, I was assigning some drag behaviors depending on which key you are pressing, and just found that if you hold CONTROL the whole function is not working... like the drag is internally not detected, here some easy code:
2. void setup() {
3. size(500, 500);
4. }
6. void mouseDragged() {
7. println(frameCount);
8. }
10. void draw() {
11. background(0);
12. }
You can try to hold any key and drag the mouse, and it will print to terminal the framecount, but if you hold CONTROL it will print nothing.

Any way to solve this? I actually would like to use CONTROL while dragging...

strokeWeight() and stroke() not working on PDF creation

[2 Replies]
- 28-Apr-2013 10:05 AM
- Forum: Core Library Questions
Just a quick issue about PDF creation.

If you run the code below you will get 2 PDF files, one which is actually what you see on screen (lines on different weight and color) and another one which is not (all the lines in black a 1px weight).

Any idea how to get the PGraphics to export weight and color of the strokes?

I'm working on a generative graphics app, and part of my screen is the interface, so I would prefer to use PGraphics to export just the right area and avoid the PDF being bigger (xy size/format) than the necessary... in the example I'm just avoiding the right half of the screen, but the idea is that way I can also scale the output to the desired PDF size (so I don't need a huge screen if I want the output to be an A1 for instance)
2. import processing.opengl.*;
3. import processing.pdf.*;
5. void setup() {
6. size(500, 500, OPENGL);
7. background(255);
8. PGraphics pdf;
9. pdf = createGraphics(250, 500, PDF, "wrong.pdf");
10. pdf.beginDraw();
11. beginRaw(PDF, "right.pdf");
13. for (int i=1; i<25; i++) {
14. strokeWeight(i);
15. stroke(10*i);
16. line(10, 10*i*2, width/2-10, 10*i*2);
17. pdf.line(10, 10*i*2, width/2-10, 10*i*2);
18. }
20. // Switch off the exporter
21. pdf.dispose();
22. pdf.endDraw();
24. endRaw();
25. }
Any ideas on how to solve this, or achieve it in other way, will be much appreciated.

Minim .get() never gets two times the same result when you run again the analysis

[4 Replies]
- 13-Apr-2013 12:39 AM
- Forum: Core Library Questions
I don`t know exactly what track.left.get(i) and track.right.get(i) are doing, but what I'm sure is that they don't always get the same result when you run the application multiple times.

Actually, if you get a short sound clip (just a few seconds) and let it loop printing the values to the terminal it will show a sequence that you could easily recognize, but actually it's not the same thing every time; sometimes there is a visual pattern (if you make a quick graphic out of the values) although the values doesn't match exactly, but at some level is pseudo-random stuff.

I was trying to generate an image from a sound file, but if gathering the data is not accurate from the beginning (run two times the sketch an get the same output) it actually doesn't work as a visualization tool, is more kind of 'sound based generation'.

Somebody has some ideas how to solve this?

Not playing the file at the same time you are analysing it helps a bit (in terms of repeatability). I also was playing with the buffer size but it doesn't help much.

Finally the best approach I found, was to run the analysis a few times and make an average, so you clean out a bit the 'random noise'... but of course this is a workaround, nothing to build upon.

As I see it, you should be able to get the data from a sound file as well as you get it from a text file.

Would be nice to hear if somebody got better results with repeatability in audio analysis with this or other library for Processing.

ControlP5 inaccurate RangeSlider output

[3 Replies]
- 11-Apr-2013 10:38 AM
- Forum: Contributed Library Questions
Hi,

I've been the whole day struggling with some weird numbers in my application, and after checking absolutely everything I finally found that the problem was not in my calculations, but in how the RangeSlider from ControlP5 was actually showing them... the good thing is that I actually cleaned the code.

I'm attaching a sample code, just a simplified version of the library example, adding three range sliders.

The issue shows when trying to set the value in the slider (you can hide decimals, but actually that they explains a lot)

This is the results you get if you run the code below:

Slider from 0-40000 set as 100-35000 shows 0.00-34947.36

Slider from 0-4000 set as 100-3500 shows 94.73-3494.73

Slider from 0-400 set as 100-350 shows 100.00-349.47

It seems clearly a problem in how is internally dealing with the decimals.

The only way you get the precise result you are asking, is if your slider is from 0-100. Anything bigger than that will be adjusted sliding the decimal period (multiplying by 10, 100, 1000… etc) resulting in an every time more inaccurate output.

I tried to send the values as floats, but it actually doesn't change anything.

I can imagine a workaround using sliders under 100 and then scaling them myself to the right value (avoiding the float issue)... but as you can imagine that would be quite nasty in terms of keeping the code as simple as it needs.

Do you have any simpler solution for this? Otherwise I just prefer to remove the GUI.

I'd much appreciate the help.

//// EXAMPLE CODE TO SHOW THE ISSUE
import controlP5.*;

ControlP5 cp5;

Range rangeL;

Range rangeS;

Range range;

void setup() {

size(700, 400);

cp5 = new ControlP5(this);

rangeL = cp5.addRange("Range 10K")

   //.setDecimalPrecision(0)

       .setPosition(50, 50)

         .setSize(400, 10)

             .setRange(0, 40000)

               .setRangeValues(100, 35000)

                   ;

rangeS = cp5.addRange("Range K")

   //.setDecimalPrecision(0)

       .setPosition(50, 100)

         .setSize(400, 10)

             .setRange(0, 4000)

               .setRangeValues(100, 3500)

                   ;

range = cp5.addRange("Range")

   //.setDecimalPrecision(0)

       .setPosition(50, 150)

         .setSize(400, 10)

             .setRange(0, 400)

               .setRangeValues(100, 350)

                   ;

}

void draw() {

background(0);

}

Activity Trend