u-he

snigelx · Post by **snigelx** » Thu Jun 05, 2014 3:48 pm

hakey wrote:The current manual says:
As in all other u-he synthesizers, key follow pivots around E3

Whatever he meant by this exact wording, I am not certain but isn't the behavior the same in ACE? Hmm... I didn't notice a difference in the way it has affected Cutoff. I mean, if I set KF to full then it tracks the keyboard...in a positive modulation from the lowest octave to the highest

snigelx · Post by **snigelx** » Thu Jun 05, 2014 3:51 pm

delete

pdxindy · Post by **pdxindy** » Thu Jun 05, 2014 5:00 pm

More Bazille - recorded in a cliff dwelling out in the high desert of New Mexico

http://draigathar.org/sounds/B41.mp3

snigelx · Post by **snigelx** » Thu Jun 05, 2014 5:06 pm

pdxindy wrote:More Bazille - recorded in a cliff dwelling out in the high desert of New Mexico

http://draigathar.org/sounds/B41.mp3

you nailed the sound of inebriated coyotes on jaw harp...and peyote!

nBeat · Post by **nBeat** » Thu Jun 05, 2014 7:55 pm

About KeyF1(2) and pivot note:

It's like a seesaw.

Does it make sense?

Howard · Post by **Howard** » Thu Jun 05, 2014 10:10 pm

RE Key Follow: I meant to check today. Forgot

Tom Drinkwater · Post by **Tom Drinkwater** » Fri Jun 06, 2014 10:01 pm

justin3am wrote:Urs had mentioned in the past that if the sequencer rate is modulatable, it can go out of sync even when modulation is not applied. I seem to remember this beeing the case with Zebra's MSEGs. I think it has to do with whether the sequencer is following the host's song position or if it is run by an internal clock (which it would have to be, to support modulation). Correct me if I'm wrong.

I always thought that a clock input would be a elegant solution. The sequencer would normally run based on the song position but if you connect a signal to the clock input, it would then ignore the song position with the understanding that the sequence could eventually run out of sync. Admittedly, my understanding of this stuff is very basic.

can someone explain why modulating the divide value that already exists is not a good way of doing this?

the speed would then be modulatable, but when the seq is set to sync it would also be affected by any tempo changes in the host session. sounds ideal to me.... and when it isn't set to sync there isn't a problem anyway.

pdxindy · Post by **pdxindy** » Fri Jun 06, 2014 10:15 pm

Tom Drinkwater wrote:
justin3am wrote:Urs had mentioned in the past that if the sequencer rate is modulatable, it can go out of sync even when modulation is not applied. I seem to remember this beeing the case with Zebra's MSEGs. I think it has to do with whether the sequencer is following the host's song position or if it is run by an internal clock (which it would have to be, to support modulation). Correct me if I'm wrong.

I always thought that a clock input would be a elegant solution. The sequencer would normally run based on the song position but if you connect a signal to the clock input, it would then ignore the song position with the understanding that the sequence could eventually run out of sync. Admittedly, my understanding of this stuff is very basic.
can someone explain why modulating the divide value that already exists is not a good way of doing this?

the speed would then be modulatable, but when the seq is set to sync it would also be affected by any tempo changes in the host session. sounds ideal to me.... and when it isn't set to sync there isn't a problem anyway.

ideal yes... but that does not mean the math pencils out in the practical sense... currently, without modulation, try holding a note down that is using the sequencer and record it in sync... then look at the waveform and you will see it goes out of sync with your daw timeline fairly quickly.

snigelx · Post by **snigelx** » Fri Jun 06, 2014 10:56 pm

The way I view keyfollow is like a rubberband placed around a central note... as the tracking is increased then the "rubberband" is stretched both ways away from the central note... in the case of cutoff tracking, then the value of cutoff is distributed between the lowest and highest MIDI note depending on the current keyfollow setting...so yes I do actually see what is meant by pivot. This is the way I have understood it at least.. It makes sense for me. And depending on manufacturer the cutoff values may be distributed at certain preconfigured intervals like quarter tone..semitone.. etc depending on keyfollow/tracking setting

AndreasD · Post by **AndreasD** » Fri Jun 06, 2014 11:26 pm

Bug in v2370:
Attached patch.
Look what the sequencer is doing with the first 4 LEDs. That's not normal.
To get to this behaviour i assigned CV2 modulation to Gain of Filter3. Set this to None and the sequencer is back to normal

Tom Drinkwater · Post by **Tom Drinkwater** » Sat Jun 07, 2014 12:05 am

pdxindy wrote:
ideal yes... but that does not mean the math pencils out in the practical sense... currently, without modulation, try holding a note down that is using the sequencer and record it in sync... then look at the waveform and you will see it goes out of sync with your daw timeline fairly quickly.

um no I don't see that, it seems to stay in sync fine. when the seq is set to sync, it stays in sync, as far as I can see, over a 2 minute period I don't see any drift...

how far out over what time scale are you talking about? am I looking for the wrong thing?

snigelx · Post by **snigelx** » Sat Jun 07, 2014 11:04 am

Thank you thank you thank you for Alt-draw... This is...nice

ols · Post by **ols** » Mon Jun 09, 2014 12:02 pm

Yes, it is done with Bazille and a convolution reverb ...
Can be improved a lot !

http://algosyn.com/music/synth/bazille/PipeOrgan1.mp3
http://algosyn.com/music/synth/bazille/PipeOrgan1.h2p

Enjoy !

Olivier

Tom Drinkwater · Post by **Tom Drinkwater** » Mon Jun 09, 2014 2:19 pm

a really great feature for bazille would be a mute function. I initially thought a per module mute, but then I thought, better still, what about double click or modifier-of-yr-choice-click on an output (or input) to mute it, then the cable from it would turn grey. no extra GUI items needed then.

it would be really helpful when working out what is doing what without disconnecting or losing settings.

a signal input to the scope to monitor from any output would also be great!

abstractcats · Post by **abstractcats** » Mon Jun 09, 2014 6:15 pm

Offcial a Bezille owner

u-he

KVR Audio

Bazille Public Beta (updated to 2370)