Maybe a bug + a (related) suggestion

[dullard]

It's taken ages of searching before I discovered usine by accident and it looks exactly what I'm after - finally something that caters for live performance. Many thanks to senso for a fantastic bit of kit...

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!

[23fx23]

hey i had exactly the same idea!!!!
in fact im trying to build this actually, i got quasi all needed to build it, exept the pb is that it needs an object that can have a mouse down , a xy mouse position, and color input at the same time, wich doesnt exist actually ..would be cool to implement color in in image object, or XY in panels...

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..)

[senso]

welcome into the Usine community!

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.

[dullard]

1) I'll move this over to email. They still aren't cooperating with each other using 4.21b.

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.

[23fx23]

hi dullard, Ive made a little pach that works like you describe:

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...

[nay-seven]

creative one , 23fx alias ColorMaster...!!.........

[dullard]

wow 23fx23 thats very cool, if a little too heavy on the cpu for my creaky old computer. I think I may have a shot at duplicating this in c++ once I have the money to go pro even tho my c++ skills are somewhat rusty...

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.

[senso]

@Dullard: tested and tested again on the 4.21b:
- Guru on track 1
- 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!

[23fx23]

thanks glad you like it, note I made a weird wire shem, got a better in mind now.

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

[23fx23]

here is a new pach with this behaviour not sure ive chosen the best tech but seems to work:
added 3 colors choice Red, Green or Blue, and a pointer that make note reached blink white, better relative mode and range multiplier. (still better to be around center however, we can't go up outside the screen hehe)

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..)

[dullard]

Nice one! I'm desperate to go pro... should be soon
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.

[23fx23]

so, the pach b is workin as you were thinking? this is a good idea, im thinking also of having a setting on X that could be another CC/parameter linked to hue or Saturation, or hue shift maybe better.to control ie lengh/gate time and velocity via one press, drag XY on a single cell.
don't worry, usine idea is relatively quicklearnt (on other side infinites way to explore take infinite time...) even if im not considering myself as a pro in all possibilities of usine,start to well catch it's philosophy now, but still every day amazed by what it is capable of.
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!

[23fx23]

edit: sorry re read, yes so you also think it should be better first behaviour concerning enabling, . actually the pach b worsk by checking if velocity has been changed of a certain range to disable or not on release, but not cool for quick enabling without setting velocity otherwise cells are not set on ,mmmneed to find another way...mm seems related to time pressed then... or maybe other solutions, ideas?

[dullard]

I think that if it has been pressed and it that press was to enable a previously disabled bit then it shouldn't disable on release whether or not it has been dragged. It should only disable it after not dragging if the bit was previously enabled. Not related to time pressed.

[23fx23]

exactly, i see it very well in terms of results, and tried to pach it tonight couldn't find the way, better sleep and think... there is a tricky thing to do, that 's the "if after not draging" i have pb to visualize/converts in terms of patch, what aproach to use ,, ..arf will find anyway..

edit yep after a night thingz are more clear found the solution, will uploader a bit later.

[23fx23]

yop dullard made a new version:

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...

[23fx23]

ok this final one seems much better ,optimised and quite well working:

http://rapidshare.com/files/239394039/X ... 0.wkp.html


or add ons/other
edit: arf bug when chg color, later..