dBlue / Illformed Glitch 2 is OUT !

[core]

Great to see this legend updated

[3ee]

And to be honest I've tried Effectrix - but was unable to find the fun I had with Glitch. But it's personal of course - some will like Effectrix better, some Glitch.

exactly!
I even had a chance to buy Effectrix for $30 for a day... no fun!

Anyway, really excited to see Glitch2, can't wait to have a play!

[dejaru]

Looks fantastic and it's just great fun to play with.
Been missing this on my mac.
Another one for the shoppinglist

[U-o]

It's great. I'll wait for better price.

[3ee]

It's great. I'll wait for better price.

Me too. 50euro+vat seems expensive to me although it might seem like a fair price.

Just had a quick play.

Although the overall feel of the effect is charming and workflow is smooth and nag-free so far, I still have some "complaints".

1st of all, a tiny error, nothing serious.
The gates time clock timings are misplaced. i.e. 1/16 is actually 1/8 and so on...


-filters have the same old harshy sound, I assumed they would been updated (the code)
-dist section sound quality is unacceptable IMO, although I like every of them algos present atm... it aliases like hell, main cause probably for the overall harshy sound.
-Retrigger - "decay" parameter is a nice addition, but I'm missing the slice "length" one.

-not so important, but naggy appearance when twisting a knob, the mouse cursor "teleport-repeats" itself when reaching the end-zone of the parameter. This doesn't affect the actual action tho...
no mouse wheel support?

...anyway, Glitch2 is fun and overall a good plug IMO!

[Ah_Dziz]

I played with the demo some last night and overall I like it. I do miss some of the features which were removed from the old version though. The slicer module is completely gone and the stutter module was far more flexible in previous incarnations. I did also get some pretty mild bugs while playing around. Some modules were changing their parameters on their own when switching scenes.also the parameter tips stopped working after a couple of minutes. It was having some sync issues too but playing with the quantize setting seemed to fix. I'm curious if it has midi learn also. Gonna buy it either way. Just waiting to hear if I will get a discount for owning the old payware version.

[SoulTrain]

I have two studio computers - one is MAC with a 64 bit host and the other one is a PC with a 32bit DAW. Is it possible to use the plug-in on both computers?

[dblue]

Is it possible to use the plug-in on both computers?

Yep.

[dblue]

I can't find it in the kvr database yet. What type of copyprotection does this use?

It uses the "I trust you not to be an asshole" protection scheme. You download your personally licensed copy from the members area of my website, then you install it on any computers that you own. Simple as that.

[Compyfox]

To reask the question from a page earlier, what is the copy protection scheme?



I also took Glitch2 for a spin. And while I do like the capability to now use several FX modules at once within one pattern, I really, really, really miss the capability to trigger indificual notes by MIDI.

This is a major turnoff in v2.


Another thing that I can confirm, is the misplacement of certain things. Like the modules changing their own parameters, the quantizing modes are off. And most drastically... the "MIDI keys" range form C-0 to G-10, but in Cubase C-0 is actuall C-2. So it's two octaves off!


And the demo thing with "no scene recalling on reload" is a bit annoying. I kind of expected a "doesn't save" feature after reading the info text. But not this. Pity - this is essential with tests on my end recently.


Else, Glitch seems to save their "random settings" in so called "seeds" to recall what it initially created on random. Interesting idea indeed.



So yeah...
I guess for the time being, I stay with v1.3.x while it's still working.
For a v2, I'd love to see the following FR's, on top of bugfixes:
- more FX modules
- triggering these modules at will with MIDI notes (and therefore reducing the patterns/scenes down to 24, or two octaves)
- maybe smaller divisions (16) - but this is highly experimental. 8 divisions are fine



Else, no issues currently in Cubase 7. But the missing individual MIDI module trigger feature is something that really holds me back.

[dblue]

To reask the question from a page earlier, what is the copy protection scheme?

See my reply above.

I really, really, really miss the capability to trigger indificual notes by MIDI.

Create several scenes, each one with only a single effect filling the entire sequencer, and then trigger these with MIDI notes to change effects on the fly. Isn't this pretty much the exact same thing? To be fair, Glitch 1 never had any real MIDI triggering in this regard, it was simply a hack. Seems you found the hack quite useful, though

Like the modules changing their own parameters

Parameters are linked to scenes, so every scene has its own unique parameter settings. When you change scenes, you change parameters. If you don't want this, then copy/paste your parameters from one scene to the next to keep it consistent.

the quantizing modes are off

How so? Quantizing live MIDI input is of course always a huge pain in the ass. If you press a key after the beat has started, then it's pretty difficult for me to do anything useful with that, except to quantize it to the next upcoming beat. So it can help to play your notes slightly ahead of time so they quantize to the next beat or whatever. If you sequence stuff manually in your DAW instead, then it's best to simply turn quantize off. Anyway, if you think something really fishy is going on, then explain it a bit more and I'll try to look into it.

the "MIDI keys" range form C-0 to G-10, but in Cubase C-0 is actuall C-2. So it's two octaves off!

Each scene is simply mapped from MIDI note #0 to MIDI note #127. Each DAW represents this 0-127 range in a slightly different way. Some start at C-0, some start at C-1, others at C-2, etc. It's really just a display issue, though, not a technical issue. If it really bothers you, then hopefully Cubase lets you set some kind of octave shift to put it back into the correct range.

- more FX modules

I have several more planned, and will continue to add new stuff in the coming weeks/months.

- triggering these modules at will with MIDI notes

This is definitely a very interesting concept, and would of course be more flexible than my scene-based workaround above. I'll certainly see what I can do here

- maybe smaller divisions (16)

I'll explore this as well. I chose a max of 8 beats and 8 divisions simply because it comfortably fits on the screen without any clumsy scrolling or zooming mechanics. There's no technical reason why it can't be higher, if I come up with an elegant way to easily navigate larger/denser patterns. Otherwise, you are clicking on blocks that are like 2 or 3 pixels wide


Anyway, thanks for your detailed feedback!

[dblue]

the parameter tips stopped working after a couple of minutes.

Which operating system and DAW do you use, and which exact version of Glitch was it?

[maniacoli]

nice effectrix clone, loved the first glitch though

[lalo]

Hi all,
i'm a dbGlitch user since a lot of time.
i've just bought ver. 2 right away.
Wonderful work !!

A couple of ( old ) feature request since the old times

1. Automatable VST Parameter for Mutate, Randomize and Seed buttons ( the global ones and the individual fx ones and the sequence ones)

2. Global Filter ( the same that we have in individual FX

3. I use Glitch mostly in live gig situations. I use to play soft synths and let them pass through Glitch. I need midi notes for playing so would be great to have an alternative way of triggering patterns and individual fx ( a VST automatable parameter would be the way to go )

4. Separate outputs for individual FX ( i.e. a main mix LR and then individual fx outs for sound spatialization and send the different fx to different mixing bus)

5. More FX

[Ah_Dziz]

the parameter tips stopped working after a couple of minutes.

Which operating system and DAW do you use, and which exact version of Glitch was it?

cubase 5 32 bit latest build, vista 64 bit professional. 32 bit vst version of the plugin. I don't have the exact version number of glitch in front of me.

Also, did you see the thing in my post above where modules were changing from their previous parameters when changing scenes? I know that each scene has it's own set of parameters now which is awesome but specifically the tape stop module was changing it's slowdown time and speedup times in one scene as I switched back to it. The values were not consistent and it only did it the first time I switched away and then back. After I get my registered copy I'll try and see if I can come up with a reproducible way to do this.