Vortex VSTi - Multi Timbral Groove Machine Beta

[Janusz Grzybek]

Hi Andy,

Thank you for fast developing of Vortex .

I've some loose ideas for new potential features of Vortex:

What do you think about adding tooltips to Vortex? It could be very useful for Vortex's users, because:
* GUI has a lot of small buttons without labels and it could be uncomfortable, especially for new users. Of course, Vortex has good (not finished yet) manual, but constant switching between DAW and PDF reader could be irritating.
* Adding tooltips with coordinates (note pitch, step number) to cells in sequencer grid can really speed up and facilitate editing of sequences, because user needn't count steps or notes. Optionally it could be implemented as small box (in GUI) with displayed coordinates for currently edited cell, but this solution requires some space in limited space of plug-in interface.
Seems to me that you use Synthedit for developing. I don't know Synthedit, but I think this tool support adding tooltips.

Midi files support:
* Export to Midi. Some users already asked about this. I think this is good idea. Saved presets (fxp) contains all sequences, multisequences, synth settings, etc. while exported Midi file contains only selected or currently edited sequence e.g. C, C#, D, etc.
* Import from Midi files. Some synths already supports import from external files to their arpeggiators/step sequencers. What do you think about implementing this same solution? However, I don't know how Vortex should support import from polyphonic Midi files to monophonic sequences.
I think combination of export and import features, could be useful for using Vortex sequences in Midi tracks (in DAWs)and vice versa, but also interesting solution for internal exchange data between Vortex presets. For example I would like use some sequence e.g. C# from one preset in other preset. In this case I export this separated sequence from preset, and next import to my edited presets. With this solution I don't need replace all sequences or manually copy sequence.

BTW:
I'd like update my PDF document about Vortex setup in Studio One, because your synth engine support multiout, while configuring it in Studio One is also tricky . I'll send it to you in next days.

Best,
Janusz

[Astralp]

Hi Janusz

No problem, I'm hoping to get v1 finished this week, now the sample system is coded it should start moving along fairly quickly

I have on my dev list to add a display, probably overlayed over the sequence. It did initially have the same one as arp which shows what you just clicked, but it did take a lot of space, and got in the way of the more compact design. So yes at some point there will be a display overlay.

I do use Synthedit, it's a great DEV environment, although I mostly tend to code my own modules, for instance the main sequence display/rows etc.. are a single peice of code, as is the main Vortex Engine, Ammonite, and TerraNova I'm not a fan of popup tooltips, I think an overlay will look much better

Yes the midi import/export is on the list, though not for v1, there are a few tricky aspects to it as you mentioned, usually once I start playing things fall into place.

Have you tried the drums yet?

I'm just working on the additional CC mixer page at the moment.

[Janusz Grzybek]

I think an overlay will look much better

I agree with this

Yes the midi import/export is on the list, though not for v1, there are a few tricky aspects to it as you mentioned, usually once I start playing things fall into place.

Yes... it could generate lot of issues , but by the other hand it combined with sequencer will be powerful thing.

Have you tried the drums yet?

Yes, I tried. Of course this is not Battery or Superior Drummers , but kits sound good. Generally, step sequencer + drums is very good solution. However, with randomize feature it could give very weird results .

Janusz

[Astralp]

Well the full drum sample complement in the released version is huge, the kits have lots of variety compared to the two, 64 kits are laid out the same and the last 64 have the same 1st octave format, but the second octave has instrument stabs and various other good things. Lat night I was just changing kits with the test synth pattern and it was sounding great, it's like having Black magic built in I'll make some more kits once the release is out.

I've almost finished the CC Page which has a 12 x 8 row of knobs so that 8 CCs can be controlled for each channel, this allows access to the onboard CCs so you can override the 'rompler' settings such as filter decay etc... Adds quite a bit of power to the onboard sound engine, plus they can alternatively be used to control external gear.

[MarkSA]

Hi Andy,

The Multisequence on/off button seems to be fixed.

Vortex is coming along nicely .The drums make a difference. The test patches work good. Nice sounds.

Regarding Asio4all/ I use these asio drivers and sometimes they cause me a few problems. They sometimes uninstall themselves

I think the manual needs updating with all of these features.

[Astralp]

Great

I'm leaving the manual until last simply because all of the screen grabs can go out of date with just simple changes and it's lots of time creating them etc... In the meantime feel free to ask any questions

Yes asio4all does that with my laptop, it works the first time, but as soon as I open it up again it's non functional until a reboot, I ended up getting a usb soundcard with asio for when I'm working on the lappy.

I'm pleased to get the drums finished, it was one of those jobs which could have taken a lot longer. I was dreading it, but it actually went very smoothly. Still needs some optimization but I'm more concerned with stability at this stage

[musikmachine]

Mark - This one is fixed in the next version, thanks

TJ - I still can't reproduce any of these problems unfortunately, it does seem to be something to do with your specific system, which makes fixing trickier. I find it strange that different asio drivers could make a difference to the plugin itself, and I'm completely perplexed as to how it could affect the lights! Very strange.. I've just tried asio4all on my system and it didn't make any difference as far as I could tell, although I don't find asio4all very stable in general with my soundcard.

Which driver did you use in cantabile? Again it works well in cantabile here..

Paint mode is added to the FR list.

Yes the gate time is short, the way it is built it has to be a 64th note and so you must use Release time to lengthen the notes. It is tricky to implement note length when you have multiple tempos running from a single clock. I do plan to look into other ways to add it when I look into swing.

Back to your issues, I think we will have to do some dedicated debugging in a few days time to try and figure out what is going on via log files.

Is ARP functioning correctly in all respects in FL?

Is anybody else using FL and having these issues?

In cantabile i used the ak1 asio driver. In Live things were working well unti l i tried tried mukltimode, initially triggering C was fine but once i triggered C# the sequence became stuck. Tried changing preset in Vortex and Trilian to no avail.

I'll try the new beta anyway, see if i can reproduce. I can't see a release time option or do you mean assign a CC to increase release length on the steps that aren't tied? Latch extended gives the notes a similar length which is most useful for recording, but what about something like the pulse length in Arp?

[Astralp]

The next version, which is less than an hour away adds the CC page for control over any 8 CCs per channel, so release can be one of those.

I think the last beta should work correctly, I think you are experiencing one of the midi bugs I fixed. Hope so anyhow!

It's complicated to explain, but due to the way Vortex is built, pulse length can't happen the way it did in the past and so the maximum size it can be is a 64th as the clock is always running at 64ths. The only way it could be achieved would be to process the midi afterwards, but this is tricky and I envisage it will be a big job in terms of getting it right. It will happen at some point and the bonus over the pulse clock length would be that notes could be longer than the pulse percentage, meaning that they could overlap which could be interesting. It would be the equivalent of a midi Note off delay I suppose Hmmm that's made me think it might be interesting to implement a midi delay now...

[MarkSA]

I have a question regarding Multisequence. Read the manual, but I couldn't work out where/when exactly do you use it. Ie, when you are playing/triggering the step Seq? I tried that and it threw things out of wack sometimes. MS button on while using the step seq.

The MS button when on stops the step seq.

Sometimes it cause to play notes even after I have untriggered them . Had to use all notes off.

[Astralp]

The idea is that you set up your sequences using single sequence mode and then if you wish you can use multi-sequence mode as way of playing patterns back. You can assign a group of sequences to a single midi key, and re-adjust the tuning and also apply a scale filter which will force notes to rescale to the selected pattern. Multi-Sequence mode is an alternative to Sequence mode, they are designed to be used exclusively, you shouldn't switch between them when performing. The reason that all notes switch off and retrigger is to avoid hanging notes. (I thought I'd dealt with that one, but perhaps not!)

The Multi-Sequencer uses Octaves C2 & C3 for the triggers, you will see the relevant key light up on the MS display when it is active.

The Octaves above C3 allow retuning the entire output in real-time of playing sequences (much like using channel 16).

The MS has had less development time spent on it than other areas so far, I will be adding more after release thus the tiny area it currently takes up on it's page

[Astralp]

Beta 10 is up!

* CC Page - 8 knobs for channels 1-12, select a CC for each row and it will send CCs to either internal or external;
* The row for the channel must be enabled
* If the internal Synth is enabled on the mixer page, the relevant colun will affect the internal synth.
* If the internal synth is disabled and the Mixer Knobs are enabled, the strip will send to the external midi channel. I'm wondering if it's overkill to have 2 Ons actually, maybe just the strip being enabled would be enough to decide whether it sends or not?
* The CCs have been named for the internal synth parameters for easy reference, obviously those names don't reflect external devices.

Haven't got around to adding the lights yet, that will be in the next release.

[Astralp]

Oh, for the time being stay away from the sample related CC values, especially when in drum mode, they could cause a crash until I've put some safeguards in place.

[musikmachine]

Really starting to take shape now Andy, the drums when run through the fx sound great.

The new synth patches are very usable as well. Multisequence is where it's at. I think Vortex'll be an awesome percussion module if you can modulate the drum samples pitch and also have steps on the same lane. I'll have a proper play tomorrow as it's late now but i have encountered few issues so far with beta 9.

Cheers.

[Astralp]

Thanks TJ, wait until you have all the kits, get a drum loop going then CTRL click on the program Change Box and get a random kit, instant gratification

Many more synth patches to come too as soon as I get the chance..

On a side note, Jens sent me a log of maschine sending out note On messages when the A, B, C D etc.. buttons are pressed, can you check to see if yours is doing the same?

If you don't have a midi logger you get hold of midi-ox from here:

http://www.midiox.com/

It would be worth checking to see what messages it's sending to see if there's any possible issues there, and if there are any unusual messages I'd appreciate the log file

[Janusz Grzybek]

I found build 11 in beta folder. What's new in this build?

Janusz