New emulation

I'll give you a hint

Think I'll call it Bottom.
Looks like it controls live, reason, traktor

I think i would call it base. If so way to go. Beacuase a livid script master loves shove it. http://www.aumhaa.com/wp/

Dude you are on a roll, arent ya?

includes proper velocity , not sure about the aftertouch pressure yet though

Bottom.PNG

Softcore wrote:Dude you are on a roll, arent ya?

i need to get out more, though

i used some of your ideas with the faders, i.e. the text object as a mask for the multiball, within a container. thanks for that.

I 've lost count of all the times, something I found on someone else's template gave me ideas or inspired me for something of my own!

Oh cool, i am currently thinking about getting one and this might help me on my decision.

Can't wait for this since Livid has a pretty cool codec for Reason. Do you know how big in terms of size this is going to be?

Hi
I have done some work on emulations some of the Livid stuff . .
Not quite finished but could maybe tidy them up a bit if you are interested . . .

IMG_0476.pngIMG_0477.png

Have also looked at doing OHM, Controlr etc . .

Yes please, i would like to test the Base to extend their codec for Reason and if i succeed i will most likely even buy one.

Looking good.
Do you know if it work ok in reason ? I can't test mine , it should really , same with flstudio , the latest version of that has
Scripts for livid stuff
Which one shall we do next? Maschine? ..... Tried it can't get close

Maschine would be awsome i have and love it couldnt replace real thing. But would nice to at least control plugin. you would have to probably make a whole program in max msp to do conversions because maschine works with hid and not midi. THough i would say since you did base cntrlr would be cool. It's got some good max for live patches for step sequencing.

Didn't know about the hid , that's the next few days spoken for , yep maschine is the dogs b.......x

The template works pretty straight away with Reason and the Livid Codec. Especially the coloring of the pads works perfectly. The only thing i did notice during my short test, was that the mapping of the buttons for Kong are partly shifted eg the pad in the low left corner of the yellow 4x4 grid doesn't trigger the corresponding pad in Kong (it doesnt trigger anything) but the same pad in the blue 4x4 grid triggers pad 16 in Kong. Could be a problem with the codec though.
The other templates seem to work though.

I dont understand the velocity and aftertouch and wasnt able to make that work.

Odd about the left bottom pad , actually thinking about it it could be the root note selector or scale , it's not abundantly clear where you are ,with just the 2 character display scale , as a double check the LCD message on the setup page will confirm both scale and root. I believe there is an auto scale that changes from drum map to major depending what device is in focus,
The velocity and aftertouch sliders are best set to the level stated I n the text .5 and .6
That bits still a work in progress

So you've got something reasonable? Maybe we should do a little exchange? Would need to do a bit more work on mine though . . .
Hadn't really looked at Aftertouch, but I got a velocity system going that seems reasonable though no tone a lot of testing, few bugs to iron out etc
And a bit of the other behind the scenes stuff - still a few things I'm not sure of how they are supposed to be done to match the hardware
The dual light switches don't quite react the way I think they should but then they aren't being sent what should be sent . . .

Yep it sounds as though it's fairly reasonable.
I didn't bother with the 2 LEDs on the switches . Just scripted pad colours instead , also I think the graduated LEDs on the sliders act slightly different from the hardware. In that the top 2 are visible , well that's what it looks like in all the videos anyway.
The velocity and aftertouch are really still work in progress
I'll send you the template,


Electrofux...... I checked the template regarding the pad ,all is ok, I had a look at the codec and that seems to be ok too,

going to test it again and have a deeper look. Maybe one of my codecs was somehow interfering. Was just a short test.

I made a longer test and the Kong template problem didnt come up again and this time velocity worked in a way. But honestly i would rather like to set it to a fixed value because it is hard to control when it is emulated.

I tend to agree about the velocity , I'm not too keen on it in any app to be honest . It don't feel right.
I'm going to replace it with my velocity module which is fixed, random, ranged, what ever . And I might incorporate it into the module , best of both worlds.

You can make the velocity fixed by moving the sensitivity slider