47 thoughts on “LFO Everything In Ableton Live”

  11. It gets even worse.. The guy is a *certified* Ableton trainer and behaves in a way which I can only describe as being uber-arrogant. Instead of explaining himself in an adult manner all he's been doing so far is (*trying*) ridicule the comments and questions people asked him.

    NOT a very good sight, and IMO this may very well impact the quality (again) which an Ableton certification was meant to represent.

    I say 'again' because last year I already started to notice that although people were Ableton certified they still made mistakes which I'd qualify as amateurish. Even blogged about that:
    http://blog.synthfan.info/2010/10/22/certified-do…

    A very strange development indeed.

  12. It gets even worse.. The guy is a *certified* Ableton trainer and behaves in a way which I can only describe as being uber-arrogant. Instead of explaining himself in an adult manner all he's been doing so far is (*trying*) ridicule the comments and questions people asked him.

    NOT a very good sight, and IMO this may very well impact the quality (again) which an Ableton certification was meant to represent.

    I say 'again' because last year I already started to notice that although people were Ableton certified they still made mistakes which I'd qualify as amateurish. Even blogged about that:
    http://blog.synthfan.info/2010/10/22/certified-do…

    A very strange development indeed.

  13. It gets even worse.. The guy is a *certified* Ableton trainer and behaves in a way which I can only describe as being uber-arrogant. Instead of explaining himself in an adult manner all he's been doing so far is (*trying*) ridicule the comments and questions people asked him.

    NOT a very good sight, and IMO this may very well impact the quality (again) which an Ableton certification was meant to represent.

    I say 'again' because last year I already started to notice that although people were Ableton certified they still made mistakes which I'd qualify as amateurish. Even blogged about that:
    http://blog.synthfan.info/2010/10/22/certified-do…

    A very strange development indeed.

  14. It gets even worse.. The guy is a *certified* Ableton trainer and behaves in a way which I can only describe as being uber-arrogant. Instead of explaining himself in an adult manner all he's been doing so far is (*trying*) ridicule the comments and questions people asked him.

    NOT a very good sight, and IMO this may very well impact the quality (again) which an Ableton certification was meant to represent.

    I say 'again' because last year I already started to notice that although people were Ableton certified they still made mistakes which I'd qualify as amateurish. Even blogged about that:
    http://blog.synthfan.info/2010/10/22/certified-do…

    A very strange development indeed.

  15. It gets even worse.. The guy is a *certified* Ableton trainer and behaves in a way which I can only describe as being uber-arrogant. Instead of explaining himself in an adult manner all he's been doing so far is (*trying*) ridicule the comments and questions people asked him.

    NOT a very good sight, and IMO this may very well impact the quality (again) which an Ableton certification was meant to represent.

    I say 'again' because last year I already started to notice that although people were Ableton certified they still made mistakes which I'd qualify as amateurish. Even blogged about that:
    http://blog.synthfan.info/2010/10/22/certified-do…

    A very strange development indeed.

  16. It gets even worse.. The guy is a *certified* Ableton trainer and behaves in a way which I can only describe as being uber-arrogant. Instead of explaining himself in an adult manner all he's been doing so far is (*trying*) ridicule the comments and questions people asked him.

    NOT a very good sight, and IMO this may very well impact the quality (again) which an Ableton certification was meant to represent.

    I say 'again' because last year I already started to notice that although people were Ableton certified they still made mistakes which I'd qualify as amateurish. Even blogged about that:
    http://blog.synthfan.info/2010/10/22/certified-do…

    A very strange development indeed.

  17. People seem to be raging on the forums, but I don't see why this is considered "stealing". The older one and this new one are both LFOs but they seem different enough. Why can't two people make similar devices without one being considered a thief?If you built a compressor, does it mean that no one else has the right make one of their own?

    So he charges $8 for his, and the older one is free. Us as consumers have the right to decide which product to choose from. That's all.

    Also, the fact that he's a certified Ableton trainer has got NOTHING to do with this.

  18. I consider it stealing because the original author provided his patch with the restriction that it was not meant to be used in a commercial manner.

    Taking (easily identifiable) parts out of that first patch, placing them in yours and then selling the entire critter as if it was your own is in my opinion plain out stealing; you're creating profit for yourself while using other people's efforts.

  31. It was considered stealing because It wasn't a matter of similar devices, he copy and pasted a module directly out of Device LFO @ http://www.maxforlive.com/library/device.php?id=3… which had a non-commericial cc license. I think the Ableton trainer status came up because he denied it even though the evidence was very clear and verified by many people. Instead of ultimately admitting he stole the code and dragging it on for days it appears he finally removed the code and re-wrote that module in javascript.

  32. It was considered stealing because It wasn't a matter of similar devices, he copy and pasted a module directly out of Device LFO @ http://www.maxforlive.com/library/device.php?id=3… which had a non-commericial cc license. I think the Ableton trainer status came up because he denied it even though the evidence was very clear and verified by many people. Instead of ultimately admitting he stole the code and dragging it on for days it appears he finally removed the code and re-wrote that module in javascript.

  33. It was considered stealing because It wasn't a matter of similar devices, he copy and pasted a module directly out of Device LFO @ http://www.maxforlive.com/library/device.php?id=3… which had a non-commericial cc license. I think the Ableton trainer status came up because he denied it even though the evidence was very clear and verified by many people. Instead of ultimately admitting he stole the code and dragging it on for days it appears he finally removed the code and re-wrote that module in javascript.

  34. It was considered stealing because It wasn't a matter of similar devices, he copy and pasted a module directly out of Device LFO @ http://www.maxforlive.com/library/device.php?id=3… which had a non-commericial cc license. I think the Ableton trainer status came up because he denied it even though the evidence was very clear and verified by many people. Instead of ultimately admitting he stole the code and dragging it on for days it appears he finally removed the code and re-wrote that module in javascript.

  35. It was considered stealing because It wasn't a matter of similar devices, he copy and pasted a module directly out of Device LFO @ http://www.maxforlive.com/library/device.php?id=3… which had a non-commericial cc license. I think the Ableton trainer status came up because he denied it even though the evidence was very clear and verified by many people. Instead of ultimately admitting he stole the code and dragging it on for days it appears he finally removed the code and re-wrote that module in javascript.

  36. It was considered stealing because It wasn't a matter of similar devices, he copy and pasted a module directly out of Device LFO @ http://www.maxforlive.com/library/device.php?id=3… which had a non-commericial cc license. I think the Ableton trainer status came up because he denied it even though the evidence was very clear and verified by many people. Instead of ultimately admitting he stole the code and dragging it on for days it appears he finally removed the code and re-wrote that module in javascript.

  38. I just replied to your post with a comment on your blog. It's quite unfair of you to make such broad sweeping statements about the whole certification system based on your experiences with one or two people, especially on such minor details like what people call something or how they navigate around the program. Mistakes like this don't instantly make someone a complete phony. And you are simply wrong in your assertion that trainers don't have to be up to date. Most of the trainers have come on board since Live 8, and Live 9 is not out yet, so it has not been an issue yet, but I can assure you it is part of the certification agreement that trainers be tested for being up to date.
    Now for the record I am not commenting on Julien's situation. Even Nico from Ableton replied in that thread so I have to assume that there was some truth in it, but I personally don't know. I am commenting on the fact that you made it about all certified trainers which is pretty excessive.

  39. Trolls like you will always need a witch to hunt. Where is you pamphlet on your blog "certified doesn't mean qualified" ? shame on you to bash an entire profession based on 10 mn of your sad life on a forum about an insignificant incident… How pathetic it is from a guy who admits using warez and give a bullet point receipe on how to bypass Native Instrument maschine protection! screw you synthfan

  40. Using warez? No; using *information* I acquired through warez channels.

    I bought and paid for my Maschine plain and simple. And was outrageous when I discovered that their software DVD did not work on my modern computer. I got in a frenzy when I eventually managed to *make* it work by using "warez tactics" and ended up with the whole installation kaboodle (easily copied, shared and distributed if you'd want to) after performing the update.

    That got worse when I eventually got feedback from NI themselves; their solution was *exactly* the same as what warezers did: providing me the entire DVD image.

    And no: I don't bash an entire profession; I only address those people who feel special enough to proclaim themselves as being "experts" yet 5 minutes later allow themselves to make mistakes which one would expect from an amateur. Nothing more, nothing less.

  41. I replied to you this evening as well.

    Unfair when people start their tutorial proclaiming to be "Ableton experts" and end up making mistakes (not one; several) which one would address to newbies ?

    Live 9 isn't out yet. But Max for Live, Amp and other updates which separate 8.2.1 from 8.0 are.

    I do *not* go about all certified trainers. I do go about those who start to announce themselves as experts and then… Sorry you seem to feel addressed here, but I can't say if that's appropriate or not.

  42. yeah right lol, "using information acquired through warez channels" I ear you on Ableton forum using big words like "I'm disgusted" "outraged" about a guy using someone else's block of code in his 8$ commercial patch (what a big deal – pathetic) yet here you are, hypocrite "using information aquired through warez channels".

    What I found disgusting is people like you who find a pervert pleasure, putting more oil on the fire and seeing people like julienb being crucified on a public place for what is a minor mistake. But please tell us what else do you do on your warez channels?

  43. Hypocrite? It seems you didn't read my blog very well.. I'm merely saying that in certain specific situations warez aren't as evil as being proclaimed. In my particular case; I bought something over the Internet, I have 7 days *determined by law* to cancel a purchase if I'm not satisfied but due to NI's DVD failure it would have taken me 2 – 3 weeks before I was even able to give Maschine a testdrive, with thanks for NI's support for being utterly slow.

    And yes; I get disgusted when people take code from others and then sell it as if it was their own. You can now blame someone who outed his frustrations, but that is also ignoring the fact that would julienb has come straight right from the start none of this would have happened. All I did was respond to visual evidence (the code snippets) provided by stringtapper.

    As to bittorrent; I help share Debian, Ubuntu and several other projects on Sourceforge.org.

  44. man you won't fool anyone about your "warez practices".

    "Disgusted", "what a sad way to start the new year" "outraged" these are your words when confronted to a guy that borrowed 50 lines of code of a Max patch!! My grip with you and a couple of other troll on Ableton forums is that this is all you need to howl with the pack, using big words and ready to tear apart a poor guys that made an honest mistake he didn't really know how to deal with.

    Have a bit of perspective you bloodthirst idiots, you just have to turn on your TV or open a newspaper and you'll get real reasons to get disgusted and outraged.

  45. @Rascala: So you’re criticizing synthfan about warez and then downplaying Julien Bayle’s blatant stealing of *licensed* code and selling it as his own? You’re talking out of both sides of your mouth. The fact is what Julien did is bad, certainly not the worst thing in the world (do we really need to compare his actions to current global affairs to keep things in perspective?), but the reason he’s been criticized so much is because of his response as much as anything. The guy never owned up to what he did! How do you trust someone who is that dishonest? How do you do business with them? I had a right to point out his dishonesty because I bought his device. And I didn’t do it to demonize him or even to hurt his business. I did it in the hopes that he would finally be honest about it. As it stands now his own response to the situation has affected his credibility more than any words anyone could throw at him.

  46. After the original author made it quite clear that he did not want his code to be used like this all julienb had to do was to simply apologize and work it out.

    Instead he started denying the issue, ignored questions and even tried to ridicule the people who were simply asking why he did it. And when stringtapper showed the code which proved beyond any doubt that he had indeed copied this stuff it did indeed disgust me to no end.

    Honest mistakes deserve an honest apology. If you don't even realize this simple fact of real life you have much bigger issues to worry about.

Leave a Reply

Your email address will not be published. Required fields are marked *