[Roger Maus]

I think I made up my mind: just now I realized that a i7-4770_ and a Xeon E3-1245v3 is practically the same. So I’ll take the latter one, since it is quite cheaper!

Do you think an extra GTX 750 is worth the money? How about using the built-in GPU of the processor and spending the money on some extra SSD or extra RAM instead?

[Roger Maus]

Thanks for your elaborate response. Just realized you are building a similar system right now: https://forums.creativecow.net/thread/2/1049743

Regarding PCpartpicker: we have a similar thing here in Germany. At geizhals.de you can do the same thing with your “wishlist”.

Thanks for calling the build a “solid machine”. This is all I wanted. (Optical drive will be SATA-BD LG Electronics BH16NS40.)

I think I will stick with the Barracuda 7200.14 2TB. WD Black are just a bit faster, which is not worth the extra bucks. Same about Hyrid HDDs. To keep it cheaper, I will at a bigger SSD (for project footage) and further 16GB of RAM later on.

I have a some spare 120GB SSDs (old Samsung 840 & OCZ Vertex2). Still wondering how to distribute all the files!?
Maybe 250GB Samsung EVO for OS & programs, 120GB SSD for Cache, HDD for footage & export, further 120GB SSD…. for what!? It’s simply to small, since there’s only about 90 “real” GB usable.
(Media/footage is normally ~200GB, Export files ~100GB.)

[Roger Maus]

Hi Liam, thanks for your reply!

Yes, I will replace th RAM for Crucial Ballistix Sport DIMM Kit 16GB which I wanted to take in the first place anyway.

I know that the PSU only delivers what is needed, but 700 Watt PSU simply use to be more expensive than 400 Watt PSU, you see?

Thanks for your response. I’ll replace the GTX 650 for a 750. No need for 2GB VRAM, right?

And I will save some money by taking a even cheaper board, e.g. ASRock H87 Pro4.

Nice to hear the boxed cooler will be enough!

I am thinking about changing the disk setup: no EVO 250, but cheaper SSDs, but more of them!
120GB Crucial M500 – for OS, programs, media cache
480GB Crucial M500 – for media/footage, project files (I doubt the GB are sufficient!)
2TB Seagate – for export, archive, backups

You think the CPU is the bottleneck?

[Roger Maus]

Overshoot works perfectly fine. But if anyone else wants to stick to the “old” bounce expression, this is the way:
amp = .1;
freq = 1.5;
decay = 2.0;

n = 0;
if (numKeys > 0){
n = nearestKey(time).index;
if (key(n).time > time){
n--;
}}
if (n == 0){ t = 0;
}else{
t = time - key(n).time;
}
if (n > 0 && t < 2){ //----INCREASE LATTER VALUE IF CUT OFF----//
v = velocityAtTime(key(n).time - thisComp.frameDuration/10);
value + v*amp*Math.sin(freq*t*2*Math.PI)/Math.exp(decay*t);
}else{value;
}

[Roger Maus]

Hi there,

sorry for picking over these bones, but
what could be the reason if the bouncing aborts – like in my case?

I applied the expression to the position property.
amp = 0.1
freq = 1.0
decay = 2.2

[Roger Maus]

Sorry for warming this up again, but how can I get rid of the following error:
Bad method arguments: one argument to mul() must be a scalar
This is the faulty expression (on a 3D layer):
x = wiggle(.5,150,3);
y = wiggle(.5,50,2);
z = wiggle(.1,5,2)*wiggle(.1,5,2)*wiggle(.1,5,2); //faulty line
[x[0], y[1], z[2]]
Is the solution to convert a vector to a scalar?

[Roger Maus]

x = Math.pow(wiggle(1,10,3)[0]-value[0],3)+value[0];
y = Math.pow(wiggle(1,10,3)[1]-value[1],3)+value[1];
z = Math.pow(wiggle(.5,5,.2)[2]-value[2],3)+value[2];
[x, y, z]
Can’t exactly tell why, but it works!

[Roger Maus]

Can somebody please help me getting this into 3D?

All the before mentioned code works perfectly for a single value, but I can’s manage to apply it to the position property of a 3D layer.

(Can’t tell exactly, but in the end it was always an error either due to div by zero or “mul() needs a scalar”)

[Roger Maus]

Sorry for the late reply. It works perfectly – all three variations.

[Roger Maus]

Thanks for your response! Holding a value is not what I wanted, but increasing the octaves is something I will use more often now.
Until now I achieved this by combining two different wiggles, like:
wiggle(.5,100)+wiggle(3,5)-value

Sorry that I did not make clear what I want to achieve. I will give it another try.

This is a normal, default wiggle:

This is a wiggle that I’d like to get (NB: different scale):

See? Values more extreme, but rarer. Values are most of the time around zero, but amplitudes are more “severe”.