Effectrix Scratch Feature Help

[robindean]

Hi all.

I'm trying to become as familiar with Effectrix as possible and need to know primarily about how the terms work for it's scratch interface.

Basically, I need visual analogies for what fwd spin, fwd slope, bwd spin, bwd slope represents. In toying with these, I'm having difficulties getting the sound I'm after. So, I figure by asking all of you I can make up for it by thinking about what the hands are "physically" doing in conjunction with these terms.

Also, How does the "size" really work in conjunction (in each effect) compared to the "beat size" setting in the top left (1/32, 1/16, 1/8, etc)?

Effectrix doesn't have a manual?

[Sugar Bytes]

Hi,

just click on the Effectrix logo to open tha about screen.
In there you find the link to he manual.
The manual can be found in the Effectrix program folder.

Size: length of the audiosnippet that is gonna be scratched.
Fwd Spin: Forward speed
Bwd Spin: backward speed.
Slope: acceleration curve.

Try the vinyl effect (STOP mode off). Its easier to use and works without looping the audio signal.

best
Rico

[robindean]

Thanks for the tip!

The manual helps LOL.

Um ... I might have found a bug, though.

On my computer, using Cubase (see my signature for hardware/software details), when I manually change the FWD Speed in scratch to anything above zero, it immediately jumps to an extremely high speed.

What I mean is that, if I set the FWD speed below zero, it sounds interesting and normal for manipulation ... but above zero it instantly becomes so fast that there's no room for finessing the feel. It's as if there's no gradient to the knob above zero.

I'm pretty sure there's a bug in there.

[robindean]

My mistake (I'm still learning). I set the scratch size very small so any fwd change was drastic.

My question still stands though.

I'm interested in creating cool and rhythmically accurate scratch tracks. Simply using the "vinyl" feature isn't "real" enough. The actual physics of a hand in motion and when the record is released are both quite important to me.

Let's say I have a song at 97 bpm (Cubase).

How do I attain 16th not scratches that sound realistic?

You know a simple "wiki-wiki-wiki-wiki" in 16th notes at 97 bpm.

Inherently, I'd prefer that you "teach me how to fish" by explaining a decent way to gather the involved calculations.

[robindean]

Brand new user. Spent $129. No new responses or tutorial regarding my interest in this feature. Hmmm ...

[Sugar Bytes]

Hi robindean,

did you try the presets: Drunken Dj, Good One and intensive ?
These presets basically have a classic wiki-wiki sound.
This should give you a good starting point.
Note that the overall speed depends on the size and the fwd/bwd parameter.
Because fwd/bwd basically describe how fast the record is pushed.
In the middle position (0%) the movement speed is the normal playspeed.
Anything above will increase the movment speed. Note that you can fine adjust the parameter with shift+click. Very important are the slope parameters because they control the acceleration of the movement. The neutral setting (0%) means there is no acceleration, which is quite unnatural. Try around with them to get a realistic scratch sound.

Hope this helps,
Robert

[robindean]

For your next release, it might help us if we can set the size / duration to a fixed note length based on the host sync. Then, the fwd / bwd speed could be set to adjust pitch / speed and THEN ... WHEN WE SET SLOPE ... have Effectrix automatically calculate the difference within the boundaries we've set.

Basically, after all is said and done, slope should be limited to and automatically calculated for within the boundaries of the rhythmic value

A visual blueprint (parabolic line chart) might help.

Is there any way for me to try and hack into this and provide development?

[Sugar Bytes]

For your next release, it might help us if we can set the size / duration to a fixed note length based on the host sync.?

yes and no, at least there should be an additional way to have also unsynced timing.

Then, the fwd / bwd speed could be set to adjust pitch
?

Well that's the problem, a change in pitch is also a change in time.
(Unless we do some additional timestretch/pitchshift)

Basically, after all is said and done, slope should be limited to and automatically calculated for within the boundaries of the rhythmic value
?

Of course i can also imagine some kind of automatic calculation to fit certain movements into a certain time context.

A visual blueprint (parabolic line chart) might help.

Is there any way for me to try and hack into this and provide development?

Ideas and improvments are always welcome. Please open up an 'improvment Request thread', so that other users (and we), can participate and discuss your ideas.

Best,
Robert