DMGAudio Compassion (Launched)

[Tscho]

I'd like to see an option to put the Limiter before the Compressor in Compassion (I think someone else suggested this already, but I can't find the post). I know the standard chain order is different. But taming the spikes before hand often helps the compressor to work smooth with more relaxed settings.

This option would add more flexibility and avoid the need of using two instances of Compassion.

Johannes

[DaveGamble]

To me there's only one issue left that's quite annoying.
When I choose a mod I see the proper name in the preset field, but when I close and re-open COMPassion the field always says "None".
This happens too when you click "Save" in COMPassion or when you load a project.
I noticed it doesn't happen with presets... is this intentional?

also, when i load a mod, and then change the view settings of the main window, the name of the mod changes to "none"

any progress on this Dave??

Sorry to come in so late, yes this is actually intentional.
Mods act to "change" a bunch of parameters, like adding a coat of paint. But you can still tweak, and it won't affect the Mod (unless you explicitly go through the "export Mod" procedure).
So I've never really thought that retaining the contents of that box was especially useful.

It doesn't happen with presets because you're actually modifying the preset when you make changes.

Now, I can change this (i.e. save the name) if there's a good argument for it (I can see it might be helpful to serve as a reminder of the last Mod you applied... but since nothing stops you applying dozens of mods to build a finished result, how useful really is that?)

Do let me know,

Dave.

[DaveGamble]

I'd like to see an option to put the Limiter before the Compressor in Compassion (I think someone else suggested this already, but I can't find the post). I know the standard chain order is different. But taming the spikes before hand often helps the compressor to work smooth with more relaxed settings.

This option would add more flexibility and avoid the need of using two instances of Compassion.

Johannes

I like it. Will add in due course!

Dave.

[DaveGamble]

Compassion v1.04 is out now!

Changes:
- Fixed OSX 10.4 support
- Fixed crash in wavelab
- Fix AU resize
- Fix bug whereby LP-split settings were not recalled correctly.
- Enable RTAS Automation
- Dezipper control changes.
- Added menu to allow tabbing between advanced pages (click page-name)
- Fixed Opto-mod HPF frequency
- Added ProTools metering support

Enjoy!

Dave.

[Funkybot's Evil Twin]

Dave, are you still kicking around the idea of making a "lite" version of Compassion? That's something I'd be highly interested in.

[Tscho]

I'd like to see an option to put the Limiter before the Compressor in Compassion (I think someone else suggested this already, but I can't find the post). I know the standard chain order is different. But taming the spikes before hand often helps the compressor to work smooth with more relaxed settings.

This option would add more flexibility and avoid the need of using two instances of Compassion.

Johannes

I like it. Will add in due course!

Dave.

Great!

And Thanks for the Advance-Pages-Menu. A real time saver!

Johannes, eagerly waiting for the next update

[Dr.Gunjah]

To me there's only one issue left that's quite annoying.
When I choose a mod I see the proper name in the preset field, but when I close and re-open COMPassion the field always says "None".
This happens too when you click "Save" in COMPassion or when you load a project.
I noticed it doesn't happen with presets... is this intentional?

also, when i load a mod, and then change the view settings of the main window, the name of the mod changes to "none"

any progress on this Dave??

Sorry to come in so late, yes this is actually intentional.
Mods act to "change" a bunch of parameters, like adding a coat of paint. But you can still tweak, and it won't affect the Mod (unless you explicitly go through the "export Mod" procedure).
So I've never really thought that retaining the contents of that box was especially useful.

It doesn't happen with presets because you're actually modifying the preset when you make changes.

Now, I can change this (i.e. save the name) if there's a good argument for it (I can see it might be helpful to serve as a reminder of the last Mod you applied... but since nothing stops you applying dozens of mods to build a finished result, how useful really is that?)

Do let me know,

Dave.

Hey Dave,

as for me, I don't care about this anymore, because I still don't get the benefits of using mods.
1. If I use a mod straight after loading compassion, I could have just used a preset instead.
2. If I tweak some parameters and then want to load a mod it's gambling(no pun intended ) because I can not see which parameters are affected by the mod and chances are good I loose my recent tweaks.
When I use undo, it doesn't undo the whole mod, but every parameter change individual, which makes it neither ergonomic nor safe to load a mod.

Cheers,
Doc

[LeVzi]

I have a bug with Compassion, but it's something I cannot make happen on demand.

Basically I load it into a slot and the GUI doesn't open, and Cubase hangs. Thing is, it's so erratic as to when it actually happens.

Thing is, in this project, it's all over the place, I've used it loads with no issues at all. But now, it is refusing to work, every time I try to insert it, it crashes Cubase.

I'm using the brand new version of Compassion, but had the same issue with the previous version, and Cubase 6.0.3.

EDIT : Does seem to be in a loop now, I cannot insert it anywhere in this project. Yet I can insert EQuality ok.

The only change (I know of) that i've made to the default is that the GUI opens in full, as you couldnt change to advanced mode in Sound Forge.


EDIT2 : I just set Compassion's default to simple view and it is now loading and opening fine in the project, it seems when you set it's default state to open in advanced mode it doesnt like that. Only problem now is, I cannot use it in Sound Forge in the advanced state Any ideas ? ty

EDIT3 : It's just started crashing Cubase again, lol all I did was add some more audio channels. And if I try and open the GUI of a previously loaded instance, it still crashes it.

[bezusheist]

i love it

[DaveGamble]

I have a bug with Compassion, but it's something I cannot make happen on demand.

I'm using the brand new version of Compassion, but had the same issue with the previous version, and Cubase 6.0.3.

So the bug was also in 1.03?
Are you running 32bit or 64bit?
Is this with the VST or VST3 version?
When you say hang, does Cubase lock up (and require a force-quit) or does it crash and exit?

Changing default GUI size is unlikely to be causing the issue in this case... sounds like something else is around.
Can you send me a crash log?

Cheers!

Dave.

[LeVzi]

I have a bug with Compassion, but it's something I cannot make happen on demand.

I'm using the brand new version of Compassion, but had the same issue with the previous version, and Cubase 6.0.3.

So the bug was also in 1.03?
Are you running 32bit or 64bit?
Is this with the VST or VST3 version?
When you say hang, does Cubase lock up (and require a force-quit) or does it crash and exit?

Changing default GUI size is unlikely to be causing the issue in this case... sounds like something else is around.
Can you send me a crash log?

Cheers!

Dave.

Yes m8, was also in 1.03.

I'm running the 64bit version, and it occurs in the VST or VST3.

It hangs up and I need to kill it in task manager. If I am playing audio when I try to add COMPassion, the audio carries on, uneffected. It's almost like an offscreen prompt has come up.

No problem sending a crash log, where do I find it ?

[Amon1973]

It should be in My Documents/Steinberg/CrashDumps. But then you have to find the line about COMPassion, as every crash is added to the same .txt document. So the list could be pretty long

[fgimian]

I have a bug with Compassion, but it's something I cannot make happen on demand.

Basically I load it into a slot and the GUI doesn't open, and Cubase hangs. Thing is, it's so erratic as to when it actually happens.

Thing is, in this project, it's all over the place, I've used it loads with no issues at all. But now, it is refusing to work, every time I try to insert it, it crashes Cubase.

I'm using the brand new version of Compassion, but had the same issue with the previous version, and Cubase 6.0.3.

EDIT : Does seem to be in a loop now, I cannot insert it anywhere in this project. Yet I can insert EQuality ok.

The only change (I know of) that i've made to the default is that the GUI opens in full, as you couldnt change to advanced mode in Sound Forge.


EDIT2 : I just set Compassion's default to simple view and it is now loading and opening fine in the project, it seems when you set it's default state to open in advanced mode it doesnt like that. Only problem now is, I cannot use it in Sound Forge in the advanced state Any ideas ? ty

EDIT3 : It's just started crashing Cubase again, lol all I did was add some more audio channels. And if I try and open the GUI of a previously loaded instance, it still crashes it.

May I suggest that you are perhaps running out of memory on your project? I'm quite sure it's a known symptom for Cubase to show blank interfaces .etc when no memory is left although I haven't ever gotten into that situation myself and I suppose it is even less likely in Cubase x64.

Perhaps try unloading 1 - 2 heavy VSTis (especially sample based ones) and try insert the plugin again?

How many instances of Compassion do you have running in the project? I'll try to repro here too.

Cheers

[Amon1973]

May I suggest that you are perhaps running out of memory on your project? I'm quite sure it's a known symptom for Cubase to show blank interfaces .etc when no memory is left although I haven't ever gotten into that situation myself and I suppose it is even less likely in Cubase x64.

Perhaps try unloading 1 - 2 heavy VSTis (especially sample based ones) and try insert the plugin again?

How many instances of Compassion do you have running in the project? I'll try to repro here too.

Cheers

I think that's unlikely. I had a similar issue with Stillwell plugins (Bombardier, MajorTOM, EventHorizon+, CMX demo). It happened just at the beginning of a project - I think I had something like 20 plug-ins loaded in the whole project... having C6 on Win7 x64 with 12GB the issue must reside somewhere else, as I had no resources-hungry VSTi.

Weird fact is, after re-installing the plugs a couple times, I reported to Scott... and the issue simply disappeared after a couple days, I'm no longer able to reproduce it

[LeVzi]

Dave,

I'll send you an email with it all m8. Not sure what's causing it tbh, can't be RAM, i've got 8 gig of it ! lol