http://rapidshare.com/files/239394039/X ... 0.wkp.html
or add ons/other
edit: arf bug when chg color, later..
Statistics: Posted by 23fx23 — 01 Jun 2009, 00:02
]]>
http://rapidshare.com/files/238968827/XYcolorseq_V3.wkp
now it works as we want regarding enabling, disabling, and I implemented XY: X contols gate and saturation, Y controls Lum and
velocity, think it can be powerfull in live situations.
edit: but wait tomorow , new version cpu optimized, instead of 16x times sames process only one dispaching, got 0,5 cpu here now for 16XY that's quite cool, still little bug to fix...
Statistics: Posted by 23fx23 — 30 May 2009, 19:53
]]>
edit yep after a night thingz are more clear
found the solution, will uploader a bit later.Statistics: Posted by 23fx23 — 30 May 2009, 04:21
]]>
]]>
]]>
that's what rock here, you decide what you want and there is 99 percent chances you can create it with usine, and it often gives you an idea how you could go even beyond what you initially had in mind.....
go for it you won't regret it!
Statistics: Posted by 23fx23 — 29 May 2009, 09:34
]]>
Guru doesn't quite work how I described - with Guru, you have to drag the level all the way down to disable which gets really annoying (maybe there's another way of disabling it in guru. I'll have to look in the manual.) The behaviour I was trying to describe , which I consider an improvement, was to disable on the release after non-dragging only when the bit was previously enabled. This seems to me a best of both worlds approach where you can quickly enable and disable just as you would normally but you then have the possibility of adjusting levels.
Statistics: Posted by dullard — 29 May 2009, 05:08
]]>
http://www.sensomusic.com/forums/upload ... es%20B.pat
is the guru behavior like that concerning enabling (actually you have to move a bit up or down to set a velocity for the swich to stay enabled..)
Statistics: Posted by 23fx23 — 29 May 2009, 02:47
]]>
I would do a slightly different implementation where a square would be turned off only if a press is *released* without dragging. This way, it makes it easier to fiddle with changes in the velocity.
yup would be better, thought about it during the night and a simpler wire shematic to be able to position it anywhere on screen. if you're patient enough, im actually implementing this idea on a bigger setup that should allow 32 fast access sequencers, or 512 sw with caption and customizable color sets..with this would add kind of 512 "fader" fonctionality, or 1024 if doing it for X and Y... (in fact any pannel could act as an XY, great)
.played a bit where velocity to cutoff and that's funny... as I know it will take a bit time, I ll try to correct this one this evening and repost.
cool if you make C, ah new coders
Statistics: Posted by 23fx23 — 28 May 2009, 10:45
]]>
- metronome on track 2
- run 2 hours without any trouble
can you try this procedure? or try to send me you workspace by mail contact@sensomusic.com
@23fx23: your are just a killer!
Statistics: Posted by senso — 28 May 2009, 09:50
]]>
I would do a slightly different implementation where a square would be turned off only if a press is *released* without dragging. This way, it makes it easier to fiddle with changes in the velocity.
Statistics: Posted by dullard — 28 May 2009, 03:56
]]>
Statistics: Posted by nay-seven — 27 May 2009, 23:23
]]>
http://www.sensomusic.com/forums/upload ... uencer.pat
just basic example, only red values, a color version is possible but would take too much cpu. note that is it take 0,5 to 1 percent cpu wich is already far too much for a simple sequencer, and should be positioned around middle of the screen (didn't implement offset compensation yet) but if you wanna test it must be working and usable...
Statistics: Posted by 23fx23 — 27 May 2009, 22:49
]]>
2) The problem of adjusting the volume with vertical bars is that with, for example, 10 different samples being triggered, you run out of vertical space.
Statistics: Posted by dullard — 27 May 2009, 21:41
]]>
1) the pb has normally been fixed in the 4.21b: small drift sync issue. on my system(s) seems to be perfect.
I have also corrected a small trouble on loop marker of the sequencer :
- sometime the first not is not played
- sometime the first note is played twice.
next release 4.21c
2) instead the switch-sequenced module you can use a 'normal' step-sequenced module and adjust the volume vertically like in the Reaktor way?
PS: please try to report issues and bugs by mail it heps to archive.
Statistics: Posted by senso — 27 May 2009, 11:26
]]>
but be sure it will be possible in usine.
edit: error thanks you illuminated me:
it is already possible (so often hehe)
as there is the mouse object, when a panel is pressed, if the mouse moves while pressed it analyses Y or X deviation to affect velocities. ive got a subpach that can change either color/lum/sat so this seems pretty doable...at least in pach version...
I had let down this idea for a while but now i think i need to implement it, gonna try to create such pach..
(cause this also would allow for example to enable a send effect and set send values, tweak ccs ect with a single pannel, would be quite powefull if also labelled..)
Statistics: Posted by 23fx23 — 27 May 2009, 03:07
]]>
I cannot get FXexpansion Guru to stay in sync with usine. I don't know whether it is an issue with guru or usine but I haven't had problems using other hosts. I'm new to usine so I may be missing something with synchronising with the master tempo. When left running for 10 minutes or so, they are completely out with each other.
This brings me to the second part of this post. I wouldn't use Guru if I could replicate it's features with usine. I'm not yet a pro user so I can't dissect the drum pattern patch but I assume it's built with a few buttons in the interface builder. It would be nice to have a way of changing the velocities of the drum hits. What I propose is (similar to how Guru does it) a tap turns the button on and a drag on the button up or down affects a value associated with that button which changes the colour fade of the button ie a bright red button would go through shades of pink toward white as the value associated with it, used for velocity in this case, is lowered. The behaviour of the button would be: in the off state, a press would turn it on at 100% of the value. While being pressed, a drag would change the value up or down. In the on state, a release of a press which hadn't had a drag would turn the button off.
Cheers for reading!
Statistics: Posted by dullard — 27 May 2009, 01:06
]]>