2CAudio B2: Full Body. Maximum Attitude.

[BachRules]

B2 is running fine for me in Reaper Win8 64 bit.

The B2 demo?

[BachRules]

As for your question, we don't generally have other reports about issues with Reaper so it seems it could be an install issue. Could you redownload, unzip using your OS's built-in unzip tool -- NOT a third party unzip tool, if on OSX, try manually setting permissions to the 2CAudio folder as deceived here:

http://2caudio.com/support/faq#_installation

...then rerun the installer. Does the issue persist?

Are you using mono tracks? Does is issue happen on stereo tracks?

Anyone else have any issues at all with Reaper? Anything?

(PS: it is now appoximately 7AM on a Sunday now as I write this... probably that is a step or two above "unresponsive"?)

Now you're asking me to do unpaid work for you, and that's not polite or pleasant of you either. I don't work for free. Find someone who does, hire people to help you test, or ignore this issue and see what that does for your business.

[Echoes in the Attic]

As for your question, we don't generally have other reports about issues with Reaper so it seems it could be an install issue. Could you redownload, unzip using your OS's built-in unzip tool -- NOT a third party unzip tool, if on OSX, try manually setting permissions to the 2CAudio folder as deceived here:

http://2caudio.com/support/faq#_installation

...then rerun the installer. Does the issue persist?

Are you using mono tracks? Does is issue happen on stereo tracks?

Anyone else have any issues at all with Reaper? Anything?

(PS: it is now appoximately 7AM on a Sunday now as I write this... probably that is a step or two above "unresponsive"?)

Now you're asking me to do unpaid work for you, and that's not polite or pleasant of you either. I don't work for free. Find someone who does, hire people to help you test, or ignore this issue and see what that does for your business.

This is how support works. They give steps for you to try and narrow down the issue. Are you expecting him to come to your house to figure out what the problem is on your system?

[aMUSEd]

After I deleted the demo and re-installed, if I put B2 on a track, loaded a track, took B2 offline, and brought it back online, the preset was gone and all B2 settings back to square-one.

It sounds like that might be a demo limitation not a bug:

========================================================
2C-B2 Demo Version Limitations
========================================================

1) Only 44.1 and 48 kHz sample rates are supported

2) No parameters info is published to the Host software. So plug-in state will not be saved in the host software project

3) No external parameters control is supported. So no parameter automation and no control surfaces support

4) Presets can be saved but cannot be loaded (only factory preset can be loaded)

5) One session time is limited to 30 minutes. you need to re-load the plug-in to continue evaluation

6) No multiple instances allowed. You can run only one instance of plug-in in your host software

7) The total in-use plug-in evaluation time is limited to 40 hours

NO AUDIO DROP-OUTS, NO NOISE MIXED. PURE AUDIOPHILE DELIGHT.

[BachRules]

This is how support works. They give steps for you to try and narrow down the issue. Are you expecting him to come to your house to figure out what the problem is on your system?

It works better when the customer has already handed his money over, can't get it back, and is desperate.

I'm done with charity work for software developers. I helped Cakewalk debug Sonar while Sonar fanboys attacked me left and right for my blasphemy of reporting a bug in Sonar. I helped EWQL debug Spaces while EWQL fanboys attacked me for similar blasphemy. Last week I helped a different company, and they actually paid me for the hours I worked for them, and that is how it should work; and that's not in the future between 2CAudio and me, so 2CAudio are on their own on this one.

[elxsound]

After I deleted the demo and re-installed, if I put B2 on a track, loaded a track, took B2 offline, and brought it back online, the preset was gone and all B2 settings back to square-one.

It sounds like that might be a demo limitation not a bug:

========================================================
2C-B2 Demo Version Limitations
========================================================

1) Only 44.1 and 48 kHz sample rates are supported

2) No parameters info is published to the Host software. So plug-in state will not be saved in the host software project

3) No external parameters control is supported. So no parameter automation and no control surfaces support

4) Presets can be saved but cannot be loaded (only factory preset can be loaded)

5) One session time is limited to 30 minutes. you need to re-load the plug-in to continue evaluation

6) No multiple instances allowed. You can run only one instance of plug-in in your host software

7) The total in-use plug-in evaluation time is limited to 40 hours

NO AUDIO DROP-OUTS, NO NOISE MIXED. PURE AUDIOPHILE DELIGHT.

Wow. I think devs deserve metals for putting up with the types of nonsense they have to when providing support.

Why would someone create a solid project using a demo of a plugin without at least reading the restrictions of the demo?

AND...

Then lash out at the developer because they didn't bother to read the restrictions of the demo.

[BachRules]

It sounds like that might be a demo limitation not a bug:... 2) No parameters info is published to the Host software. So plug-in state will not be saved in the host software project...

I agree that accounts for the parameter resets; thanks for pointing that out. However, it doesn't begin to account for why I couldn't remove this effect from my track without it crashing Reaper.

[elxsound]

This is how support works. They give steps for you to try and narrow down the issue. Are you expecting him to come to your house to figure out what the problem is on your system?

It works better when the customer has already handed his money over, can't get it back, and is a desperate.

I'm done with charity work for software developers. I helped Cakewalk debug Sonar while Sonar fanboys attacked me left and right for my blasphemy of reporting a bug in Sonar. I helped EWQL debug Spaces while EWQL fanboys attacked me for similar blasphemy. Last week I helped a different company, and they actually paid me for the hours I worked for them, and that is how it should work; and that's not in the future between 2CAudio and me, so 2CAudio are on their own on this one.

I hate to break it to you, but if you're getting attacked this much, there's a chance you've done something wrong.

In this case, it seems you've spotted a demo restriction you were ignorant of because you didn't read the limitations. Not a bug, but a demo limitation.

For the record I use B2 in Reaper among several hosts without a problems. It works as advertised and It recalls presets (because it's the full version, not a demo).

[BachRules]

I think devs deserve metals for putting up with the types of nonsense they have to when providing support.

Why would someone create a solid project using a demo of a plugin without at least reading the restrictions of the demo?

AND...

Then lash out at the developer because they didn't bother to read the restrictions of the demo.

Cool. If I get back into commercial development and I produce some crap, I'll market it to you since you'd make a useful fanboy.

[elxsound]

It sounds like that might be a demo limitation not a bug:... 2) No parameters info is published to the Host software. So plug-in state will not be saved in the host software project...

I agree that accounts for the parameter resets; thanks for pointing that out. However, it doesn't begin to account for why I couldn't remove this effect from my track without it crashing Reaper.

That would be a Reaper issue, not a 2CAudio issue.

Once you delete the plugin from your folder, the way Reaper recalls the plugin that no longer exists is independent of any other 3rd party plugin developer. So try your support request there.

[BachRules]

It sounds like that might be a demo limitation not a bug:... 2) No parameters info is published to the Host software. So plug-in state will not be saved in the host software project...

I agree that accounts for the parameter resets; thanks for pointing that out. However, it doesn't begin to account for why I couldn't remove this effect from my track without it crashing Reaper.

That would be a Reaper issue, not a 2CAudio issue.

Once you delete the plugin from your folder, the way Reaper recalls the plugin that no longer exists is independent of any other 3rd party plugin developer. So try your support request there.

Nonsense. No other plug-in crashes Reaper when you simply remove it from a track.

[elxsound]

I think devs deserve metals for putting up with the types of nonsense they have to when providing support.

Why would someone create a solid project using a demo of a plugin without at least reading the restrictions of the demo?

AND...

Then lash out at the developer because they didn't bother to read the restrictions of the demo.

Cool. If I get back into commercial development and I produce some crap, I'll market it to you since you'd make a useful fanboy.

I take you call many people fanboys. Mainly people who provide corrections to your mistakes.

Why not man-up, since it was your error.

[elxsound]

It sounds like that might be a demo limitation not a bug:... 2) No parameters info is published to the Host software. So plug-in state will not be saved in the host software project...

I agree that accounts for the parameter resets; thanks for pointing that out. However, it doesn't begin to account for why I couldn't remove this effect from my track without it crashing Reaper.

That would be a Reaper issue, not a 2CAudio issue.

Once you delete the plugin from your folder, the way Reaper recalls the plugin that no longer exists is independent of any other 3rd party plugin developer. So try your support request there.

Nonsense. No other plug-in crashes Reaper when you simply remove it from a track.

Have you deleted the plugin completely and any corresponding plugin dependent folders?

[BachRules]

I'm done with charity work for software developers. I helped Cakewalk debug Sonar while Sonar fanboys attacked me left and right for my blasphemy of reporting a bug in Sonar. I helped EWQL debug Spaces while EWQL fanboys attacked me for similar blasphemy. Last week I helped a different company, and they actually paid me for the hours I worked for them, and that is how it should work; and that's not in the future between 2CAudio and me, so 2CAudio are on their own on this one.

I hate to break it to you, but if you're getting attacked this much, there's a chance you've done something wrong.

There's also the fact that I did nothing wrong, all the bugs I reported were later acknowledged by the respective developers, and in the meantime their stupid fanboys did their thing.

[elxsound]

I hate to break it to you, but if you're getting attacked this much, there's a chance you've done something wrong.

There's also the chance that I did nothing wrong, all the bugs I reported were later acknowledged by the respective developers, and in the meantime their stupid fanboys did their thing.

Cool.

Let's take it at face value then. Back then, you were right and they were wrong. You were attacked by fanboys.

Now...

You made a mistake regarding the demo limitations and now you want to your reaper project to work without B2.

Right?

Have you deleted the plugin and any plugin dependent folders (presets, etc...)? Are you on Mac or PC?