2

[jorgo stefani]

@derilja: I am not using SD3 Standalone…

@Olle @Henrik: No, DAW and so the Hardware are not recognize the NEW state.

Same when u load another Kit from SD3-dropdown menue with new Macro states.

New Macro states are not reflected.

Only when u load from Preset/Bank – VSTi.fxb/fxp the states immediately updating.

A curiosity: If u record (in a DAW) the macromovements (as controllers)

Macro 2 / 3 /4… are recordable…

Macro 1 – not – maybe a part of the problem?

Reply To: SD3 as VST – some hard problems with Macro States not reflecting in the DAW version: 3.1.4
Operating system: Windows 10

• This post was modified 5 years, 7 months ago by jorgo stefani.

[jorgo stefani]

Hello Henrik.

First, thanks for the quick response. and one thing in advance

– I’m currently very happy with SD3 and do not want to sound disrespectful …

A: Henrik wrote: This can not be done since plugins (such as Superior Drummer 3) can not “tell” the DAW what to do.

– I think that’s not right. VSTs can and should communicate their (changed) parameter status to the DAW.

Otherwise, VSTSynths with bidirectional hardware controller – control would be unthinkable.

These are not commands to the DAW but only status information (e.g., CCs / Para 1-100) of the VSTi.

B: Henrik wrote: This can not be done either, but from a logical perspective! For example, say you have connected a knob to a volume knob in Superior Drummer 3, so that when you turn the macro knob both the volume and the pitch changes.
If you would change the volume control, and that would change the macro, that would be in turn so change the pitch control – which probably would not be intended!

– Yes, admittedly this is a bit more complicated as it would take into account different uses of the macros.

1. The Macro controls only one parameter (for example, a MixerFader)

– here bidirectional would be problem-free

2. The Macro controls several parameters

– Here should be a graphic hint (in the GUI / parameter block – Like Solo / Mute on the MixerTab above)

that there are several parameters and a clickable choice to change all or one from the nested parameters…

this is like an Off or temporarely Unlink – Button to disable the bidirectional parameter change.

This is may be considered as a constructive wish list :-))

Greetings…

Reply To: SD3 as VST – some hard problems with Macro States not reflecting in the DAW version: 3.1.4
Operating system: Windows 10

1

Thanked by: Henrik Ekblom

[jorgo stefani]

hi all.
here an update for the settings (Roland VH-11)…
HH-PedalControl
Openness6
Value: 5
Openness5
Value: 15
Openness4
Value: 32
Openness3
Value: 48
Openness2
Value: 62
Openness1
Value: 75
closed
Value: 85
Tight
If u cannot trigger the tight samples, check the incoming midi cc values (my are 0-90)
so i trigger between 90 and 85 the tight samples.

[jorgo stefani]

Nice..
but a ride on a cymbal position is not so “far away” like a bassdrum on top of a cymbal-stand :))
so as an idea: choice to change the generic icon back to the original one…

[jorgo stefani]

Hi Henrik.
If i replace a Cymbal with a Ride the Ride-Grafic is not the Original.
Its showing a grafic from a Roland-E-Cymbal (Black-Cymbal).
Is this a bug or its a visual for “not the correct place for a ride”? – this would be in conflict with ur state above:
“all positions can be replaced with any instrument”…
greetings

[jorgo stefani]

Thank you for hearing me…
Maybe the Screenshots and the Crashdump-file can help from my side…
One correction: Asio4all is working with SD3-Standalone but around 3times higher in latency as e.a. Cantabile

[jorgo stefani]

Hello Hendrik.
Wow – what a fast answer…
That would be great.
But – its not my “feeling” – look at the Screenshots (no image manipulation, 1:1 Screenshot, Standard 16/9 FullHD Monitor) :-))
I have read in another Topic that TT work on Fontscaling?
125% with free Fontscaling would absolutely perfect for FullHD Monitors / E-Drummer / Studios with unchangeable distances to the Monitor.
Do u have some infos about the ASIO-problems? – workaround? – e.g. write my Asio settings in a SD3Asio.ini or similar?
So long…
Greetings from Germany

[jorgo stefani]

For the “e-drum mode ” it would be nice if we can arrange the added instruments to new positions like SD2 to match the e-drum.
so we can “see” the instruments and not must learn for every Kit where are my – 2. Ride…
Greetings

[jorgo stefani]

Hello TT-Team.
I’m using the Focusrite Scarlett 18i8 interface.
Every time i want to open the “ASIO-Buffer Dialog” SD3 crash.
I´ve tried some other ASIO-Drivers (Realtek-ASIO, ASIO4ALL, Roland)
but still the same happens the “ASIO-Buffer Dialog” constantly crash SD3.
In this state the Standalone Version is not usable because the default high latency settings are not changeable.
Some facts:
I have a perfect configured and latency optimized system (i7-7700k….) and all (i mean ALL) runs flawless – except SD3 in the StandaloneVersion.
As VST the most is fine but…
due to the extra space i need for the host/sd3 window the upper scalings from sd3 dont fit my Monitor (16/9).
Example: SD3 at 150% on a 1920×1080 monitor with host. The complete Buttonbar is cutted.
Also in the StandaloneVersion the Buttonbar is cutted off.
Can i hope these issues will be soon fixed?

[jorgo stefani]

rrosin said
I use the VH-11 with a TD-15 module which is sending CC-values of 0..90 where SD3 expects values from 0..127 – so the HiHat is never recognized as “closed”.
You must adjust the CC curve in the MIDI mapping to fix this. It’s more a problem of the drum module than of SD3.
Here are my SD3 Settings for a VH-11HH that work near flawless (with proper setup in the module):
HH-PedalControl:
Openness5
Value: 5
Openness4
Value: 18
Openness3
Value: 37
Openness2
Value: 56
Openness1
Value: 75
Closed
Value: 85
Tight

[jorgo stefani]

…so – ~ 3 month later.
nothing happens
i am on bfd3 now.
also not a real-scalable interface but a clever and clear workflow and logic.
rest you continue on the laurels. any company that has done this is now bankrupt.
best wishes

[jorgo stefani]

…the manifest – workarounds dont work with *.dll – files. Superior Drummer is only a VST.dll
Best workaround (not a solution) for the moment is a second screen with 1024x768Px Resolution.
But…
– workaround for resolution
– workaround for e-drummer
– workaround for hh-settings
– workaround for inconsistent mapped packs
– workaround for default configs (save all in combined presets)
and im sure if i dive deeper in this BShit-ups, sry… i find many more ways to waste my time.
This is not a nice Programm – the workflow with it is a relapse into the 90´s.
Jumping from workaround to workaround….
bad bad bad
Solution: Toontrack – build a modern version and give us registered pained users a FREE-UPDATE.
Nothing other brings us (I know I’m not the only one) back…
Ciao

[jorgo stefani]

@Petrolu – How u do that in Cantabile Light? The CL Interface is Scaleable but the SD2 Interface stay in Scale.
P.S.: If u are a greek guy – “giasu” from germany :-))

@Toontrack – I am absolutely disappointed. I paid 250 euros and get a completely outdated software. The scalability has long been a required and necessary function of since her failed until now. The ease of use and clarity leaves something to be desired. So…
Never again … Toontrack. l switch to BFD3 (They have done their homework with V3) and wich you good luck in the further disregard of your users …

[Author]

Replies