LFO everything 1.6 ....... faster, simpler, cleaner !

stringtapper · Post by **stringtapper** » Sat Jan 15, 2011 12:25 am

julienb wrote:the price has changed a bit.
but the support is so powerful/reactive & nice...

Er, yeah except that you never answered my question in this very thread.

julienb · Post by **julienb** » Sat Jan 15, 2011 7:02 am

You probably have some visual and audio bugs.

stringtapper · Post by **stringtapper** » Sat Jan 15, 2011 6:32 pm

julienb wrote:You probably have some visual and audio bugs.

What? I was asking a serious question about your device. There are some developers who have released M4L devices in which they have taken steps to make sure the insides of the patch are not viewable (or at least not easily viewable), and I was asking if you had done something similar.

Your answer:

julienb wrote:what do you mean?
nothing can really be closed on that way ...

…contains a question (that I answered in my next post) and your second sentence doesn't make any sense in English.

I am being totally serious here. I just want to know if I will be able to get inside your patch to learn from it before I buy it.

julienb · Post by **julienb** » Sat Jan 15, 2011 6:43 pm

stringtapper wrote:
julienb wrote:You probably have some visual and audio bugs.
What? I was asking a serious question about your device. There are some developers who have released M4L devices in which they have taken steps to make sure the insides of the patch are not viewable (or at least not easily viewable), and I was asking if you had done something similar.

Your answer:

julienb wrote:what do you mean?
nothing can really be closed on that way ...
…contains a question (that I answered in my next post) and your second sentence doesn't make any sense in English.

I am being totally serious here. I just want to know if I will be able to get inside your patch to learn from it before I buy it.

hello, no problem with you stringtapper.
a jealous/complexed guy just wrote a message and removed it and I answered to him.

btw, there are not really ways to lock down your patches.
some workaround, yes. But I think this is a bit strange to lock them down.
my business isn't only to sell this device (fortunately) and I guess some people copied/torrented it.
I cannot blame them. they are just contributing to my celebrity

so feel free to ask more questions on julien@designthemedia.com

stringtapper · Post by **stringtapper** » Sat Jan 15, 2011 7:44 pm

julienb wrote:hello, no problem with you stringtapper.
a jealous/complexed guy just wrote a message and removed it and I answered to him.

btw, there are not really ways to lock down your patches.
some workaround, yes. But I think this is a bit strange to lock them down.
my business isn't only to sell this device (fortunately) and I guess some people copied/torrented it.
I cannot blame them. they are just contributing to my celebrity

so feel free to ask more questions on julien@designthemedia.com

Sorry about the confusion julienb.

Good to hear that you would not lock your patch down. It's an important distinction for me. If I'm going to buy a patch I'm buying it to see how it works as much (or more) than to use its actual function.

Thanks.

julienb · Post by **julienb** » Sat Jan 15, 2011 7:47 pm

stringtapper wrote:
julienb wrote:hello, no problem with you stringtapper.
a jealous/complexed guy just wrote a message and removed it and I answered to him.

btw, there are not really ways to lock down your patches.
some workaround, yes. But I think this is a bit strange to lock them down.
my business isn't only to sell this device (fortunately) and I guess some people copied/torrented it.
I cannot blame them. they are just contributing to my celebrity

so feel free to ask more questions on julien@designthemedia.com
Sorry about the confusion julienb.

Good to hear that you would not lock your patch down. It's an important distinction for me. If I'm going to buy a patch I'm buying it to see how it works as much (or more) than to use its actual function.

Thanks.

as I told, excepted if you use some externals, it is impossible to lock them.

julienb · Post by **julienb** » Sat Jan 15, 2011 7:49 pm

http://vimeo.com/18657462 is the last video of the last version 1.5 ... release on next monday!

custom waveforms are now available (no, not now ... on next monday!)

stringtapper · Post by **stringtapper** » Sat Jan 15, 2011 7:51 pm

Well if you look at the Puremagnetik M4L devices they have released, they have gone to great lengths to hide the insides. Transparent objects and patch cords, all objects stacked upon each other, [thispatcher] routines that make the patch close when you try to open it in editing mode, etc. I spent some time pulling one of them apart but got bored before I ever got into the real workings of the patch.

julienb · Post by **julienb** » Sat Jan 15, 2011 7:57 pm

stringtapper wrote:Well if you look at the Puremagnetik M4L devices they have released, they have gone to great lengths to hide the insides. Transparent objects and patch cords, all objects stacked upon each other, [thispatcher] routines that make the patch close when you try to open it in editing mode, etc. I spent some time pulling one of them apart but got bored before I ever got into the real workings of the patch.

it is a workaround, indeed.
but we can dig it

opening them as texte, we can correct all the patch inspector visible values... of course.

julienb · Post by **julienb** » Wed Jan 19, 2011 1:54 pm

http://designthemedia.com/products/abletonlive

now with drawable waveforms ! ! !

julienb · Post by **julienb** » Wed Jan 19, 2011 10:20 pm

OMG, Peter did it: http://createdigitalmusic.com/2011/01/g ... everything

mr.ergonomics · Post by **mr.ergonomics** » Thu Jan 20, 2011 3:38 pm

I don't know if you have another development thread, but two small ideas.

1.
wish:
make the big "on/off" button midi midi/macro mappable too.

why:
when you want to control the parameter with controller you have to turn the LFO off to get control again.
you can do it at the moment just by turning the whole device off, but the on/off button is a way better visual indicator.

2.
faster tempo synced rates for the LFO (4n seems to be the fastest at the moment) 1/8,1/16 and 1/32 would be nice too.

thanks for this device, I really like it. for production I record the automation directly in arrange view and turn the LFO off after that. that way lives history stays clean too. this is a good workflow for me.

emajcher · Post by **emajcher** » Fri Jan 21, 2011 5:21 am

LFO everything steals code for the bpatcher module for persisting track/device/parameters with a live set lifted from my Midi LFO which I posted on maxforlive.com under a non-commercial license @ http://www.maxforlive.com/library/device.php?id=354 way back in July.

The creative commons license explicitly states:

"This license lets others remix, tweak, and build upon your work non-commercially, and although their new works must also acknowledge you and be non-commercial, they don’t have to license their derivative works on the same terms."

The bpatcher is identical, down to the module positions, font I use and the name of every single parameter based on the naming conventions I use when I develop M4L patches. Asking for permission would have been the proper approach before you renamed the object and started to sell it with your patch; designing a LFO that controls Live was academic (which can be seen from the number of LFO's on maxforlive.com), the hard part was persisting the parameters with the live set in a reliable fashion. I am not a big fan of selling m4l patches, especially where you are lifting code specifically from a device that is marked as non-commericial only.

Lux Libra · Post by **Lux Libra** » Fri Jan 21, 2011 7:41 am

julienb · Post by **julienb** » Fri Jan 21, 2011 7:52 am

emajcher wrote:LFO everything steals code for the bpatcher module for persisting track/device/parameters with a live set lifted from my Midi LFO which I posted on maxforlive.com under a non-commercial license @ http://www.maxforlive.com/library/device.php?id=354 way back in July.

The creative commons license explicitly states:

"This license lets others remix, tweak, and build upon your work non-commercially, and although their new works must also acknowledge you and be non-commercial, they don’t have to license their derivative works on the same terms."

The bpatcher is identical, down to the module positions, font I use and the name of every single parameter based on the naming conventions I use when I develop M4L patches. Asking for permission would have been the proper approach before you renamed the object and started to sell it with your patch; designing a LFO that controls Live was academic (which can be seen from the number of LFO's on maxforlive.com), the hard part was persisting the parameters with the live set in a reliable fashion. I am not a big fan of selling m4l patches, especially where you are lifting code specifically from a device that is marked as non-commericial only.

in order to design a circle, you have to ... draw a circle.
circle cannot be protected in any manners because it is too much elementary.
I won't justify the fact I didn't "steal" anything, it is obvious I didn't.
I have no problem with this kind of (a bit jealous) comment.
I'm just a bit sad to read it.
But I can understand your opinion about the fact it already existed LFO, free etc.

I'm making A LOT for communities (arduino, midibox, and others too), I'm also selling things because I'm not a student "living with only fresh air" or just an hobbyist.

BTW, emajcher, I understand your angriness.
A LOT of people copied schematics + firmware of my protodeck controller (and I know well a company who probably sold several things)
But was it a "copy"? or only me saying "they copied MY stuff" ?
MY protodeck controller probably inspired several persons, company. and finally, I'm just proud of this (even if it wasn't inspiring and me egocentric thought I inspired people with my ideas etc)

BTW², don't think your modules were unique ; they really aren't (too)

LFO everything 1.6 ....... faster, simpler, cleaner !

Re: LFO everything 1.2 (NeW version ! ! ! !)

Re: LFO everything 1.2 (NeW version ! ! ! !)

Re: LFO everything 1.2 (NeW version ! ! ! !)

Re: LFO everything 1.2 (NeW version ! ! ! !)

Re: LFO everything 1.2 (NeW version ! ! ! !)

Re: LFO everything 1.2 (NeW version ! ! ! !)

Re: LFO everything 1.2 (NeW version ! ! ! !)

Re: LFO everything 1.2 (NeW version ! ! ! !)

Re: LFO everything 1.2 (NeW version ! ! ! !)

Re: LFO everything 1.5 (draw your waveforms !!)

Re: LFO everything 1.2 (NeW version ! ! ! !)

Re: LFO everything 1.5 (NeW version ! ! ! !)

Re: LFO everything 1.5 (NeW version ! ! ! !)

Re: LFO everything 1.5 (NeW version ! ! ! !)

Re: LFO everything 1.5 (NeW version ! ! ! !)