SupaTrigga REQUESTS and BUGS thread

[putte]

.... Bug!:

for the first time i now tried using it under osX 10.2.6 and Logic 6.1
(i fist converted the Supatrigga with angus´ vst-au adapter)

It loads up, but doesnt do anything to the audio.
Bram ... am i the first who tried it to use as a vst-au?

putte

[jackbatterypack]

I got the same Cubase 5.1 error with Supatrigger. When i click either play (or open the plugin while the track is playing) cubase just closes up and drops back to the desktop (Windows XP in my case) - this happens in tracks when other plugins are used

when i use it alone (as the only plugin - sometimes it works, sometimes it just mutes the channel i'm processing..)

cubase 5.1 r1, windows xp. athlon xp2000

[Kim Lajoie]

Beat me up because I just skimmed over the whole thread....

It's cool, but doesn't seem to work properly at tempos above 130BPM. It seems to generate a bar-long loop and repeat it for several bars before generating another loop. Doesn't seem to do this at slower tempos.

WinXP, CubaseVST5.1

Downloaded SupTrigger yesterday.

Forever,




Kim.

[Bram]

hey guys,

thx for all the feedback...
my exams finished friday and i'm enjoying the _splendid_ weather a bit...
expect some more feedback from me on all the questions/problems!

seems like cubase 5.1 is gonna be a bitch.


- bram

[putte]

my exams finished friday and i'm enjoying the _splendid_ weather a bit

are you crazy?! ... you mean ... outside world and all that stuff? ... real sun and air and all these things? ...

nono, congrats bram to your exams! Enjoy time over there ....

putte

[Kim Lajoie]

seems like cubase 5.1 is gonna be a bitch.

Don't beat yourself up about it - I'm upgrading to SX in a few days.

Of course, there might be others too....

Forever,




Kim.

[skybax]

It's cool, but doesn't seem to work properly at tempos above 130BPM. It seems to generate a bar-long loop and repeat it for several bars before generating another loop. Doesn't seem to do this at slower tempos.

I have the same problem in Muzys! I haven't tried at a slower tempo though ...
I thought it was a "feature"
Maybe if this is fixed, I'll start using it

[Mr. Slater's Parrot]

Bram, from another thread ...
james & others:
I created a 'bugs and feature requests' thread over at the smartelectronix forum... Please post bug's (errrmm, and feature requests! ) there...
When I'm back from my few-days-away-from-pc I'll go over that thread and see what I can do about all the problems...

Thanks, Bram.

Here's my test: add an instance of Groove Agent as a VSTi and an instance of SupaTrigga as an insert effect. Then press Play on Groove Agent to generate some audio (looped). I've tried the same thing with a drum loop instead of Groove Agent, as well.

The results:
o In standalone Chainer, SupaTrigga seems to work just fine.
o In EnergyXT inside of Chainer, SupaTrigga seems to work just fine.
o In Orion, SupaTrigga seems to work just fine.
And yet:
o In Muzys, SupaTrigga only outputs the dry signal until I play around with a bunch of controls on the Muzys insert box and/or on the SupaTrigga UI. After some seemingly random amount of twiddling of knobs, SupaTrigga kicks in and seems to work just fine, thereafter.
o In standalone Console, only the dry signal from Groove Agent is heard.
o In Sonar, only the dry signal from Groove Agent is heard. This is the case using the Cakewalk/Fxpansion wrapper and using the DirectiXer wrapper.
o Using Chainer as a wrapped VSTi inside of Sonar with Groove Agent and SupaTrigga loaded, only the dry signal from Groove Agent is heard.
o Using EnergyXT as a wrapped VSTi inside of Sonar with Groove Agent and SupaTrigga loaded, only the dry signal from Groove Agent is heard.

I don't understand what is different between Standalone-Chainer & Orion, which work, and all the other combinations that don't work.

Any help would be most appreciated as I'm very excited by SupaTrigga and its amazing potential.

Thanks,

James

[Ned Bouhalassa]

Hey James, thanks for the great tip of combining Groove Agent and SuppaTrigga!

[Mr. Slater's Parrot]

You're welcome!

Some of the Groove Agent styles sound really cool with SupaTrigga. For example, using Chainer, I loaded Groove Agent and set it to "New Orleans Funk". Then I added one instance of SupaTrigga and panned it far left and turned up the slices to 8 or 16. Then I added another instance of SupaTrigga with its settings tweaked slightly and panned far right with 8 or 16 slices. Then I let some of the dry Groove Agent signal come through the middle. Wow, a funky beat with wild percussion thrown in!

SupaTrigga has *amazing* potential!

James

[Bram]

James, thanks a lot for that... You'd be a heck of a nice beta-tester!
some insights into how supatrigga works and it will make a lot more sense:

basicaly Supatrigga needs 'extensive' VST time info: supatrigga needs to know EXACTLY where in the measure we are and this information isn't provided by all the hosts.

Right now I made it so that if the information that is needed isn't present, supatrigga just outputs the DRY signal. I'm going to change this in the new version: when the needed info isn't present, I'll send out short bleeps or something.
That way it's easier to find the hosts that just don't give the info the triggah needs.

Anyway, this leads us to a few interesting conclusions, or guesses right now:
* au->VST adaptor from fxpansion doesn't generate timinginfo yet, it's up to angus to add that (I know it's possible, go bitch to angus, hehehe, hi angus! )
* none of the cakewalk products nor DX->VST adapter from fxpansion generate the right info (hehehe, hi again angus )
* non-realtime hosts such as wavelab most likely won't work
* some hosts mess up the timing-info, my money is on Cubase 5.1 sending supatrigga bogus information, which I might not be catching like I should!
* as timing-info is probably the most 'advanced' (and quite crappy) feature of VST most other wrappers could get us into trouble.

I haven't got the souce code, nor a compiler handy right now, so, it'll be a while

James / putte: interested in joining the smartelectronix betatesters team?

More info/.. later

cheers,

- bram

[Mr. Slater's Parrot]

Hi Bram,

That explains things a lot and sounds like it accounts for the results I'm seeing. I'll try to contact support for some of the hosts and wrapper vendors to see if better timing data can be added.

I would be happy to help beta test -- you've create a really awesome effect!

James

[Mr. Slater's Parrot]

I contacted Kirill, the developer of the DirectiXer VST/VSTi-to-DX/DXi wrapper. He said that Sonar/DX only sends timing data to DXi instruments, not to DX effects. He suggested that I wrap SupaTrigga as an instrument -- this is just a setting in DirectiXer -- instead of wrapping it as an effect. And ... it works!!! ... using DirectiXer, at least. I'm getting crashes when doing the same thing with the Cakewalk/Fxpansion wrapper.

It also works fine when using Chainer DXi -- wrapped with DirectiXer -- as an effect in Sonar.

Thanks Bram and Kirill!



James

[Bram]

hey james, that's good news!!
i'll talk to angus about the problem when I meet w/him next week...

- bram

[cold c]

Supatrigga is crashing cubase here too. Cubase 5.1, winxp. Sometimes it has no effect whatsoever, sometimes it works, sometimes it crashes cubase with the standard "a serious problem has occurred..." error message. Very nice when it works though.