dBlue / Illformed Glitch 2 is OUT !

[Endor-8o8]

Cool to see an effetrixologic update for this great toy, but the price is too high imo, will wait for a better offer...

[robogone]

It uses the "I trust you not to be an asshole" protection scheme.

Awesome! I'll probably get round to picking it up sometime.

[highkoo]

Great to see this legend updated

+1
Effectrix is the copy-cat. Always was.
Anyone around pre-05 knows that...

[manducator]

It uses the "I trust you not to be an asshole" protection scheme.

Awesome! I'll probably get round to picking it up sometime.

definitely +1

[metalifuxx]

Great to see this legend updated

+1
Effectrix is the copy-cat. Always was.
Anyone around pre-05 knows that...

+2

[highkoo]

And to be fair, Effectrix added the sequencer-style gui, which dblue is (smartly) using here.
Good stuff all around, anyway.

[Compyfox]

nice effectrix clone, loved the first glitch though

It was pretty much mentioned to death in here already...
Glitch came out in '05, Effectrix took the idea further and was released in '08. So Glitch is among the oldest of these kind of FSU effects.

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?

Sorry, not the same. I can only trigger "one" FX module this way, or several combined. But I can not mix and match unless I create tons of presets for all kinds of purposes. That would mean 8^8 = 16777216 combinations that I also need to remember.

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

Yes, it was limited to one master and one slave effect, but it was darn useful.
Maybe create a "pure module trigger" mode, and one "sequencer" mode. Switchable with a button on top right of the GUI or something like that. What do you think?

How so? Quantizing live MIDI input is of course always a huge pain in the ass....

They are wrong labeled.

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. ... If it really bothers you, then hopefully Cubase lets you set some kind of octave shift to put it back into the correct range.

It's irritating, and no, Cubase can't change anything about it.

Then again, the labeling in Cubase is like the labeling on 99% of available MIDI hardware or master keyboards.

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

Definitely looking forward to that.
Like I said, create a button on the GUI that switches Glitch2 from Arranger to Module Trigger mode, and fuse your plugin as if Effectrix/Artillery is one plugin.

Best of both worlds, you can't go wrong there. Especially considering the updates you're planning.

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

I gave you some hints. You do the coding.



Divisions are not that important. It's fine as it is.

Anyway, thanks for your detailed feedback!

Thanks for letting me use a demo version.

[mholloway]

the demo of Glitch 2 is completely unusable for me -- anybody else having this problem? opening the plugin window results in a blank white box appearing. The GUI appears elsewhere on the screen, but cannot be interfaced with, and disappears once you click anything.

I'm running 64 bit, Ableton Live 9, iMac OSX mountain lion.

edit: the AU seems to work fine, the VST has the above problems.

-M

[fgimian]

OMG!!!! I'm buying this for sure, just as soon as I check that it is stable in Logic Pro 64-bit

The price is extremely reasonable and dblue deserves the credit. It was almost a crime that v1 was given away for free! I have compared Effectrix to Glitch on multiple occasional and it doesn't come even close.

Now that I'm on Mac, the news of AAR 64-bit and this have made me so ecstatic!! If only LennarDigital would release Sylenth1 64-bit AU, I would be in heaven

Really love the new interface too, looks brilliant!

[dblue]

anybody else having this problem?

I'm aware of the problem and it's going to be fixed very soon. Hopefully later this week.

[cryophonik]

I don't suppose an AAX version is planned, is it?

[dblue]

I don't suppose an AAX version is planned, is it?

Nope.

I'm probably just out of the loop, but I've barely even heard of AAX plugins before. I had to Google it just now to remind myself and figure out what the heck you were even referring to.

Sorry!

[mholloway]

I'm aware of the problem and it's going to be fixed very soon. Hopefully later this week.

Cool, though since the AU works fine my initial comment of "totally unusable" is quite untrue This is a killer plugin, will be buying shortly!

-M

[wasi]

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. ... If it really bothers you, then hopefully Cubase lets you set some kind of octave shift to put it back into the correct range.

It's irritating, and no, Cubase can't change anything about it.

Then again, the labeling in Cubase is like the labeling on 99% of available MIDI hardware or master keyboards.

It is irritating, but it's nothing that can be changed in-app. If you used it in renoise, C-0 would be midi note 0.

I ran into this with Geist, which hard-codes different elements to different midi note numbers, but then names them "C2" etc., but "C2" is something else in every host I use. Here's what I found:

http://cote.cc/blog/logic-studio-9-midi-note-numbers

The MIDI specification, as defined by the ISO (International Oraganization for Standardization), tells us that middle C is MIDI note number 60. All other notes are relative to this one. Therefore, MIDI note number 69 is the A above middle C (us used for 440Hz tuning). However, the specifications does not say which one is middle C (C1. It turns out that various manufacturers place this middle C at different octaves. It usually is C3, C4 or C5.

So Cubase obviously places middle C at C3 (C-2 is midi note 0). Renoise uses C5 (so C0 is midi note 0), IIRC Ableton Live uses C4 (so C-1 is midi note 0).

The nice thing about using C5 is that ther's no negative octaves, i.e. no C-2 or C-1, which overall I find less confusing. Many write C2 as C-2, forgetting that in a DAW that assumes middle C as C3, you need to be able to write C-2 and C2.

Nothing to be done. There's no midi spec for middle C.

[fgimian]

Just bought my copy, well done with getting this out there!! Love the new interface

A tiny suggestion from me: Can you please add the version number in the members area so that I can easily check that I'm up to date?

Thanks heaps!!