PlanetZ forums - scopeusers.com

Hi All,

DAS reverb family is growing up : here comes DAS GRIESVERB...

We are very proud to introduce the last one of the DAS reverb processor range : DAS GRIESVERB , an amazing powerfull Stereo Reverb Processor (Two Engines) that is completing the original bundle :

DAS Giesverb is included in the DAS REVERB BUNDLE .

It is free for all that already owns the Reverb bundle
(Just download here : http://www.digitalaudiosoft.com/plugins ... %20Bundle/ )

You can buy THE REVERB BUNDLE here : http://www.digitalaudiosoft.com/order.html

ENJOY ...

... DAS PLUGINS AND MAKE GOOD MUSIC

cheerz
olive

um... wtf does the name mean ?! I'm not that good at french... (and the reverb surface isn't gris exactly)

-greetings, markus-

Hi Olive!

Thanks for this "Autumn Special"! Can't wait to try it out. The filters appear to be different. Do we need to get new keys for this device?


Cheers,

T

Sweet!! can't wait to try it out

Merci beaucoup!!!!

merci beaucoup

GRIESVERB sounds better than your fabulous RMX160 !

Thanks Olive!! It is very kind of you to supply the DAS Griesverb with the the already fabulous Reverb bundle.

One request:-
a great feature of the DAS Griesverb is the feedback you can get when using the various sliders - bringing up the sliders to increase the feedback and then bringing them back down again to reduce the feedback in time with the music. It would be great to be able to make use of this and record these slider movements as midi controller data in a sequencer. Would it be possible to add midi inputs to the DAS Griesverb (as you have already done with the RMX160A and D_Verb reverbs)? Midi input on the REV 224 would be great aswell

I know you can get passed the problem of no midi input on devices by either inserting them into a mixer's insert or fx sends, or using a device like the AuxRack which has a midi input. But then the midi control assignments are not stored with the project for devices inserted into a mixer's insert or fx sends, or AuxRack.

HI hesno ...


About midi in DAS plugz :

As you already saw some have and the most recent don't ...

In fact, is is an advice from Sonic Core not to put the midi functions in the "basic" plugz as they can be midified later (as you wrote ...)

About automation of these plugz, they are fully XTC supported ... so that if you work in xtc, all parameters and automations will be stored and played back ,

if you are not in xtc mode, you will have to insert these plugz in some additional devices such as channel mixer ...

But then the midi control assignments are not stored with the project for devices inserted into a mixer's insert or fx sends, or AuxRack.

i am not sure of that !!! can you (or any one else confirm ?) did you try to save the midi assignement ?

Any way THX A LOT FOR SUPPORT AND FEEDBACK ...

And always ... Enjoy DAS plugz and make good music ...

cheers
olive

[quote="sonolive"]

In fact, is is an advice from Sonic Core not to put the midi functions in the "basic" plugz as they can be midified later (as you wrote ...)


Interesting does that mean that scope 5 is undergoing some midi/automation changes, I hope so.

sonolive wrote:
In fact, is is an advice from Sonic Core not to put the midi functions in the "basic" plugz as they can be midified later (as you wrote ...)

Sonic Core's advice makes me mad!! Let me make myself clear - my query is based on recording midi controller data to a sequencer to control devices and not using midi controller data as a performance tool. I understand that these can be very different uses of midi controller data and, as such, users of midi controller data as a performance tool will often have different requirements to those who use midi controller data to control devices by recording and playing back midi controller data from a sequencer:-

a)Users of midi controller data as a performance tool will usually have midi controllers with lots of knobs/sliders and a standard midi controller setup for each device. They would just load their device and then load a midi controller assignment preset for that device from the "MIDI Controler" folder. There maybe various presets they have created for the various midi controllers that they use.

b)Users recording midi controller data to a sequencer to control devices will usually have midi controllers with fewer knobs/sliders and won't always have standard midi controller setups for each device.


If you are using a sequencer to control a device with midi data and the device has no midi input so has to be inserted into a mixer's insert or fx sends, or AuxRack you have to:-

1)Save midi controller assignments in the "MIDI Controler" folder. Do this for all devices where it is needed.
2)Save your project as normal.
3)Load the midi controller assignments you saved in the "MIDI Controler" folder. Do this for all devices where it is needed.

You could, as I previously mentioned, create midi controller assignment presets in the "MIDI Controler" folder and then load them everytime you load a project where you use midi controllers to control a device that has no midi inputs. But you would need to do this for every such device in your project that you have used midi controllers to control and that has no midi inputs.

Midi learn is fantastic. It's great to be able to just click on a paramater that you want to control on a device and then twiddle your controller to assign it. If you want to use the midi learn function on a device with no midi input then you will have to save your midi controller assignments as a preset in the "MIDI Controler" folder and then reload this midi controller preset after reloading the project.

Why do Sonic Core advise "not to put the midi functions in the "basic" plugz as they can be midified later"? I would really like to ask a member of Sonic Core to explain their reasoning behind this? It really seems as though Sonic Core do not appreciate the fact that users not ony use midi controller data as a performance tool. Or am I the only person who records midi controller data to their sequencer to control devices? Surely adding midi functions to a plugin is not a complicated issue (please forgive me if am wrong on this Olive!) . Adding midi inputs to a device means no need for an AuxRack or limiting a device's use to a mixer's insert or fx sends. Plus adding midi inputs to a device means instant recall of all your midi controller settings for that device when reloading it in a project rather than having to save and reload your midi controller assignments for that device.

I do have a SonicCore SCOPE SDK LICENSE AND NONDISCLOSURE AGREEMNENT form to fill in and send off so that I can (hopefully ) add midi inputs to devices where I need them. But it would be far easier (signifcantly so for non SonicCore SCOPE SDK LICENSE holders) if midi inputs were just included in the first place.

Please developers - add midi inputs on all devices.

I feel I might be hijacking this thread with my last post . So, if anyone is interested and would like to respond, please check out the "Please developers - add midi inputs on all devices" thread on the Problem Solving forum at http://www.planetz.com/forums/viewtopic.php?f=1&t=26190 .

Presets would be welcome.Thank U.