[5534] copy protection violation? thanks for that

[CarlSeleborg]

Dear friends,

Although I agree that it is hardly acceptable to see such a message box
when you've bought Live, it happens from time to time that the crowd
shoots the messenger a little too promptly.

As you know, plug-ins are pieces of code loaded into the host's memory
space and executed there. If the plug-in crashes, it really looks like
the host crashed. Live 7 used to try to continue running, at the risk
of using corrupt data. Live 8 got a little more defensive about that:
we feel it's better to crash early than to corrupt your Live Sets.

In this case, the messenger has a wrong diagnostic: the Warmverb plug-in
probably does crash, which gets caught by Live as a copy-protection violation,
perhaps because the plug-in does things to memory that it should
not be doing.

Here's my suggestion: if you see this message even without any plug-in in
your Sets, then it's definitely Live's fault. In the meantime, we will
investigate further to see why this particular message pops up.

And for what it's worth: always contact [email protected] in such cases,
they can help you.

Thanks for reading, and keep on rocking.

Carl

[Zerobae]

i should add that meanwhile ableton support has been informed and christian kleine was very supportive in trying to find what's wrong here. when i started this thread, nothing lead me to believe that a (particular) plug-in had to to with it – the message popped up without anything loaded (when starting live), but only, as i discovered later by accident, if a live set containing warmverb had been saved before.
currently i cannot reproduce this behavior anymore, which is only partly encouraging as i don't know what exactly will trigger it to return, so it could happen anytime.
what i can say is it has never happened as long as i didn't save sets containing warmverb, so it looks very much like the plug-in's fault and i apologize if my op has led others to jump to conclusions.

[b0unce]

so it looks very much like the plug-in's fault

Realllllly ?
So, warmverb is also causing (similar) misbehaviour in other hosts ?

[dom]

bounce, please.
your statement is technically irrelevant.

dom

[b0unce]

?
seems logically relevant to me...there's two variables in this quandary, host & plugin.

Also, I don't think it's cool to flippantly shift the blame on the devs of Warmverb....when clearly, their plugin may be operating perfectly with other hosts.

Is my question really THAT out of place ?

[dom]

Is my question really THAT out of place ?

Yepp, it is. Plugin handling can and copy protection handling is pretty different between different hosts, even if there's a VST standard, which actually contains a lot of grey areas.

That's why your comment is only heating up the discussion without any further value.
And at least in technical discussion i would like to prevent that.
That's ok with you, right?

with love,
Dom

[b0unce]

Is my question really THAT out of place ?

Yepp, it is. Plugin handling can and copy protection handling is pretty different between different hosts, even if there's a VST standard, which actually contains a lot of grey areas.

Well, I disagree. I think it's perfectly fine.
As you say - there are differences in copy protection handling from host to host, it's not far-fetched to consider Live 8.x's copy protection handling is at fault - and not, as you and your colleague seem to be alluding, warmverb's fault. To ask whether warmverb is causing (similar) misbehaviour on other hosts is a basic diagnostic query, the answer would go some way in isolating the problem (plugin or host?)
that should certainly be asked in this thread, considering the allusions. If that puts a fire under your arse, then I apologise...but really, it's not intended to be a question for heating a technical discussion up.
It seems so logical to me, I find it weird you object to it - despite your given reason.


Besides all that, I have bona fide experience with an older ableton live copy protection bug. Which was never resolved in any bugfix/update for that version of Live. As you know.

Regards

[dom]

Well, I disagree. I think it's perfectly fine.

Again, i respect what you personally think, and what kind of assumptions it leads you to - but it is really of no technical relevance here.

So, please, with sugar on top stop: as there's a bug number assigned to the subject now, stop contributing to this thread if you can't add practical experiences to this very problem. Because that's what we would like to collect here.

You know i always fight for freedom of speech.
If you feel like discussing your own theories you come up with because you don't trust the ableton development and support, just start another thread for it.

Thanks,
Dom

[john doe by choice]

In this case, the messenger has a wrong diagnostic: the Warmverb plug-in
probably does crash, which gets caught by Live as a copy-protection violation,
perhaps because the plug-in does things to memory that it should
not be doing.

That is what they are saying, bonce - Carl is saying that it is not a copy-protection issue, but that the error code being displayed is wrong, which happens, since people program this software, and people aren't perfect, unlike you. Funny, both Ableton and the op say that it appears to be an issue with Warmverb, and yet you still have to blame Ableton. What else do you expect with you upgrade fees - Henke to come over and make you dinner once a week? Dom standing by your toilet to wipe your ass for you?

You bitch about pace on a non-pace related forum (take it to the forums for the software companies that use pace already, ffs), you tell everyone here to go to hell, you have nothing to offer except being an ass with a thesaurus, and now you are taking advantage of the forum's non-censorship policy by talking shit to the guy who can effectively out you and ban you (something that is long overdue, I believe).

If anything, all Dom needs is to look through a few pages of this:

http://forum.ableton.com/search.php?aut ... 6&sr=posts

To see that you are really no good for this forum, and that you only desire to cause dissent. I can understand dissent for the sake of humanity against a heavy handed dictatorship or military presence (try reading Paulo Freire), but what you do is simply protest for the sake of protest, and serves no purpose.

To back up the op's current sentiments, I have also had experiences with plugins that crashed Live - once removed, everything went back to normal...it was a bit of a process, finding which one was the culprit, but it worked.

[b0unce]

Well, I disagree. I think it's perfectly fine.

Again, i respect what you personally think, and what kind of assumptions it leads you to - but it is really of no technical relevance here.

So, please, with sugar on top stop: as there's a bug number assigned to the subject now, stop contributing to this thread if you can't add practical experiences to this very problem. Because that's what we would like to collect here.

You know i always fight for freedom of speech.
If you feel like discussing your own theories you come up with because you don't trust the ableton development and support, just start another thread for it.

Thanks,
Dom

Hehe, ok...freedom of speech is nice. I mean, I'm grateful to be given the liberty to speculate whether Shannon Doherty sleeps with terrorist aliens or not. Truly I am. But, if the price here for that freedom is forgoing the right to speculate on who's at fault when Ableton is crashing....I'd rather give up the trivial BS. Keep fighting the good fight though,

Anyways, there's nothing to add to this line of chatter...I asked my question, which is all I wanted to ask and still the answer is of interest to me.





@Mongo by choice, is that quote supposed to make my question invalid or something ?
The abes gave you a friend or foe button...or list, or something along those lines, anyways - it was designed for you so please use it.

[john doe by choice]

The abes gave you a friend or foe button...or list, or something along those lines, anyways - it was designed for you so please use it.

That doesn't mean a whole lot coming from you, since your obvious foe is this whole forum (for proof, see this: http://forum.ableton.com/search.php?aut ... 6&sr=posts ), and you keep coming back...that would make you a hypocrite, wouldn't it? At least until you stop posting.

[b0unce]

If you really want the drama, start another thread and I'll browbeat you there instead.
Respect your Dom's wishes and keep the heat out of this thread, or maybe you're the hypocrite ?
(btw - you're rhetorical question is flawed, if it even bothered me to begin with... it would make me a masochist - not a hypocrite. I'm neither)

[john doe by choice]

If you really want the drama, start another thread and I'll browbeat you there instead.
Respect your Dom's wishes and keep the heat out of this thread, or maybe you're the hypocrite ?
(btw - you're rhetorical question is flawed, if it even bothered me to begin with... it would make me a masochist - not a hypocrite. I'm neither)

I'm not making bullshit comments about technical aspects of Live, which is what he asked you to stop, if you go back and read his posts again.

Also, suggesting to someone to use the foe feature of the forums (a feature that, if I am correct, removes from the users sight posts made by people they have selected to be a foe), but not using said feature, makes you a hypocrite, since, as I said, you treat the whole forum as your foe; you don't like anyone here, you don't offer anything positive or useful, you don't treat anyone with any amount of respect at any time, and you bitch about things that have nothing to do with this forum. By suggesting to someone to use the "foe" feature, but not applying that suggestion to yourself, your suggestion qualifies as hypocrisy, and if you're going to play some english-major, argument-is-flawed crap, at least figure out the difference between "your" and "you're" so you can have the upper ground you so valiantly love to insult people from.

But wait, if you used the foe feature on everyone here you didn't like, this forum would appear to be empty to you, and you'd have no reason to come here and be an asshole, a behavior that is obviously one you choose, according to your user post history.

Seriously, Dom should just out you already, it's the least you deserve with your terrible post history - if you're going to be an ass, at least do it from a real profile. As it is, none of your posts have any balls or weight behind them, you're just another internet troll, with nothing substantial to give.

[Tone Deft]

john doe by choice - what was your old login name? I didn't catch when you switched. no matter, just curious.

[john doe by choice]

john doe by choice - what was your old login name? I didn't catch when you switched. no matter, just curious.

I act the same on my other profile as I do on this one, and actually use it way less...also, I don't post under that profile because it has a direct connection to a myspace profile I have which has been stalked on by some dumbass just because I got the url first, which is fucking lame, and I wouldn't put it past this person to stalk me here, either.

Anyway, I'm not trolling from this profile, which is the point - bounce's profile is made for being an ass, just like when smutek got caught busting your balls from his troll profile, only bounce is a little more subtle than that. If I were trolling, I would expect to be outed, but I'm not 100% prick to everyone all the time, just as you're not, even if we can both be pricks sometimes. bounce, however, is full-on hard-on all of the time, an approach which is on a different level entirely.