KVR Audio

droopy6 · Post by **droopy6** » Mon Aug 13, 2012 10:02 pm

I tried the Geist Demo and I can't figure out why the REX slices
are always quantized to 1/16.
Geist resolution is up to 1/64, so why there is no choice about that ?

A lot of REX files cannot be played properly at 1/16, the groove is entirely
trashed.

twolegstoneworks · Post by **twolegstoneworks** » Tue Aug 14, 2012 8:10 am

How did you load the REX-file? Did you set the "slice" option in the file-window before loading the file?

droopy6 · Post by **droopy6** » Fri Aug 17, 2012 8:24 am

metal wrote:How did you load the REX-file? Did you set the "slice" option in the file-window before loading the file?

yup.
but that's not the point. the point is the pattern, on top of the slicer.
it seems the pattern created by geist is always at 1/16.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Fri Aug 17, 2012 8:26 am

[DELETED]

droopy6 · Post by **droopy6** » Fri Aug 17, 2012 8:29 am

nope.
it is very strange...

twolegstoneworks · Post by **twolegstoneworks** » Fri Aug 17, 2012 8:58 am

droopy6 wrote:
metal wrote:How did you load the REX-file? Did you set the "slice" option in the file-window before loading the file?
yup.
but that's not the point. the point is the pattern, on top of the slicer.
it seems the pattern created by geist is always at 1/16.

Ahh, now I see what you mean. Yes, it does actually seem like the quantize is always set at 1/16 for patterns - regardless whether you chop your loop into 1/32 or 1/64..only the pattern length changes.. Maybe it's hardwired to 1/16 for some reason? Worth reporting to FXpansion surely.

djsubject · Post by **djsubject** » Fri Aug 17, 2012 11:38 am

uncheck the "Q" button in geist & the rex should load un-quantised

will check later & report as a bug if it dose not!

Subz

droopy6 · Post by **droopy6** » Fri Aug 17, 2012 2:13 pm

As far as I know, The Q button is only here for MIDI input. checked or not, the pattern extracted from the REX file is ALWAYS quantized to 1/16
that's too bad

kingtubby · Post by **kingtubby** » Fri Aug 17, 2012 2:42 pm

It does apply the appropriate shift to the slices. You can see it in the pattern window, with the multi-graph view selected.

droopy6 · Post by **droopy6** » Fri Aug 17, 2012 6:55 pm

It does apply the appropriate shift to the slices

may be, but the grid, is always with 1/16 resolution. The point is
to work at 1/64 to respect the groove of the loop.

djsubject · Post by **djsubject** » Sat Aug 18, 2012 6:21 pm

droopy6 wrote:
It does apply the appropriate shift to the slices
may be, but the grid, is always with 1/16 resolution. The point is
to work at 1/64 to respect the groove of the loop.

Ahhhh, i see what you mean now!

Subz

droopy6 · Post by **droopy6** » Sat Aug 18, 2012 7:17 pm

I now the idea behind geist is to remix loops, so the primary goal is not to replay a REX loop perfectly. but, when you know geist can go up to 1/64, I can't figure out why they limit the grid to 1/16 in the slicer...
It does not make sense.

Amberience · Post by **Amberience** » Mon Aug 20, 2012 11:41 am

So... if I can get this straight...

You've set the pattern steps to 1/64th... and do the REX load operation *after* ??

That's not really how Geist is designed to work. However slicing a rex file to a pattern, the rex file should playback *exactly* as it is - without any timing differences. If you turn on use layers, and load it in... it should match the loop exactly.

When you do this, the pattern will look like its sliced to 16ths. But if you open up the graphs, you'll see the shift lane is calculated to make the slices playback exactly when they should, in relation to the file.

droopy6 · Post by **droopy6** » Mon Aug 20, 2012 5:10 pm

You've set the pattern steps to 1/64th... and do the REX load operation *after* ??

no. forget this. if you do that, the rex slicer go back to 1/16, that's all.

so, I didn't notice the Shift feature. that's cool. but even there is some shift, the loop is damaged.
try "Exit Only Beat" in "Beat Bandit" library for instance.

so, it seems that the slicer is buggy, inserting bad shift values.
or simply, even with shifting, 1/16 is not enough to play with accuracy this loop.

stikygum · Post by **stikygum** » Mon Aug 20, 2012 9:19 pm

I would go ask in the Fxpansion forum or email support. It seems very odd that all REX are imported as 1/16ths.

What's wrong with Geist REX Import ?