CK_Modules (SE) VST/FX now Freeware

[magicmusic]

Midi Transpose is a 'live' feature since it is MIDI i.e. the transposition is not saved in the patch, so, of course if you reload the song the default transposition is Zero. Only when a MIDI transpose note is played will the transpose change.

Yes, but when switch Midi Transpose Channel to off and in Hold Mode, the transposition is not set to 0. But ok, i see when i switch to release mode, then transposition is set to 0 without reload song.

Can you please tell, if it is hard to add the feature that the program change messages are delay to beat, or end of sequence. Look in this video at 3:10, for what this feature is usefull too. It is a video from Karma.



here the scene switch(is the name here for pattern change), can be set that the pattern is play to end and only at end of pattern the pattern and trigger notes(for transpose) change. in this video you can see, that he press a key to play a fill. and then during the fill is play, he press the key to play another sequence but the drum fill is play until end, and only if drum fill end new pattern is play.

I really dont understand wy Hardware synthesizer mostly have this feature.

when the pattern is lets say 10000 cycles long, and a program change message or Note for trigger come into the VST at 95000. the notes and program change at midi clock 95000 can change in event time if option is on. Or is this not possible with VST ?

the formula is as this.
((event time of note/pattern length)+1)*pattern length.
its integer calculation
95000/10000 =9
9+1=10
10*10000=100000.
So the time of the event should be modify or old event delete and a new create with time 100000

but its also ok, if it can set to delay to next bar, or next 2 bars.
maybe can create a Midi VST for this. But I think many are happy if you add this feature in the seq and arp with an option switch. because its possible to make music without pressing keys in correct timing

[C.Kerry]

Can you please tell, if it is hard to add the feature that the program change messages are delay to beat, or end of sequence. Look in this video at 3:10, for what this feature is usefull too. It is a video from Karma.
I really dont understand wy Hardware synthesizer mostly have this feature.

I guess the reason why H/W keyboards with sequencers have that feature is because they are used to play Live.
Whereas VSTs are mostly used in sequencers with pre-recorded music - so you can set your program changes to the correct point.

If other people request this feature then I will take a look at it, but so far you are the only one. PatternArp has been my best seller before and not one customer has mentioned it.

The other issue is that adding any new GUI controls will most probably make old presets incompatible, which is something I really don't want to do.

But as I said, if several people request it here then I will look into it, see if it can be added and preset compatible.

[BlackWinny]

If other people request this feature then I will take a look at it, but so far you are the only one. PatternArp has been my best seller before and not one customer has mentioned it.

I didn't know Pattern Arp before this thread. But look what Fluffy and me we wrote about Poly Step Seq a few weeks before...
http://www.kvraudio.com/forum/viewtopic ... 0#p5860450
               
As Pattern Arp is built on the same concept (in logic treatments and in the graphical aspects), all I wrote in that post for the Step Sequencer apply to Pattern Arp.

[BlackWinny]

And I think that magicmusic's request is really interesting, yes. If it's simple enough to not upset the code.

[C.Kerry]

If other people request this feature then I will take a look at it, but so far you are the only one. PatternArp has been my best seller before and not one customer has mentioned it.

I didn't know Pattern Arp before this thread. But look what Fluffy and me we wrote about Poly Step Seq a few weeks before...
http://www.kvraudio.com/forum/viewtopic ... 0#p5860450
As Pattern Arp is built on the same concept (in logic treatments and in the graphical aspects), all I wrote in that post for the Step Sequencer apply to Pattern Arp.

From that thread I see you said PolyStepSeq GUI was a 'model' of what others should base their designs on, right? If so, thanks for that

So, do you want the same layout but only bigger/wider? - that is something I could do.
The original design was based on the typical 1366x768 laptop monitor resolution, providing plenty of space to still allow access the Host controls/tracks etc. - that is how I prefer to work.

If enough people request changes then i will seriously consider making those types of changes.
Anything that alters the GUI Size/Layout is fine, no problem.
Adding new features/GUI Controls can muck things up in SE for Preset compatibility, and I have to respect/consider the people that bought them previously.

This applies to the 'Delay Preset Change' feature - I agree it sounds like a great idea and i'm sure i have some modules that already delay Preset Changes for smooth Program Changes - If enough people want it, then i will put in the time to explore that possibility.

[BlackWinny]

For people who as me have eyesight impairments, a GUI just a little bigger would be very nice.

Say, based on a 1600 pixels width of screen, which has become the standard now since 2011. Mathematically it doesn't make much difference compared to a 1366 px based screen, but visually it changes everything in the readability.

But in fact, to talk specifically of Poly Step Seq and Pattern Arp, the cells of their matrices of squares (the main matrix of each plugin) are (for me) at the good size as they are currently, and therefore there is no real need to enlarge them. The problem is more about the matrix of numbers at the right side. The numbers of this matrix are a bit too small. It is this matrix which could be enlarged (in height as well as in width) just a little bit, very few, just enough to gain one or two sizes for the numbers which are in the cells. The same for the buttons "-12"... "+12". And the same for the labels "Start", "Steps", "Pat", "Mode", "MIDI", ""Root", etc. on both GUI's.

In the Pattern Arp, all the LCD displays at the bottom could be also a few pixels wider... just enough to increase a bit (of one "step" in the scale of sizes) the size of the characters inside them and above them.

At the top left of the main matrix, the pointer system of coordinates could gain in readability too, by the same increase of the size of the characters, by just one or two sizes, very few in fact, but that "very few" in all these elements would certainly make a huge differences for us, the visually impaired persons.

And, at last, it would be very nice if the matrix of the right side of both GUI was much darker, or even in black background (with the same white letters, no change for their white color) to increase at the maximum the contrast... and the same for the background of the elements which recall LCD displays at the bottom of the GUI's.

I think that for the total it would need not more than around 15% (certainly much less than 20%) of widening for the total GUI of both, knowing that their main matrix itself doesn't need any modification of its width.


All that doesn't seem a lot of work, I think, but it would lead for the two GUI's to a much much much more readable GUI, with very very few modifications in fact, I'm pretty sure.

I really love these two GUIs. In my opinion yes, they are a model of what should be done by all the developers!

May I make you another little suggestion? At the bottom left of each of the two main matrices you could add four little square buttons (the same size as the current buttons "-12"... "+12", not bigger), a red, a bright blue, a bright green, and a bright yellow. The user chooses one of these four colors... which will become the color of the "activated cells" in the matrix. I think that the selection could be saved in the subdirectory which contains the SEP and SEM modules... Maybe I say an idioty, it's just a final suggestion.

But for the moment, I say a great, great, great thank you for all these excellent tools!

[fluffy_little_something]

I am not sure, but I always thought there is a little terminology inconsistency in the sequencer. The term step refers to a let's call it note slot in the sequencer's main window, but in the playlist step seems to refer to a string of sequences. I don't know which meaning is implied by the term step sequencer, though

But really, since his stuff is free now, I think we should not bug him too much

[BlackWinny]

I'm not sure either, but (maybe I say an heresy, my version of what I understand in that is very humble) if I recall correctly an ARP follows imperatively the rules of the harmony in the succession of steps in the times, and a step-sequencer is much more generalist, allowing to make a succession of what you want in the notes... and not only in the notes, but also in any MIDI parameters related to filters, envelopes, etc. even without necessary change of notes.

[fluffy_little_something]

In terms of design the only thing I might suggest is making the horizontal note lines light and dark like the keys of the keyboard, Currently they are all the same shade of gray which makes it necessary to look to the left edge for the keyboard. When reducing the cells in height, that can be quite a challenge for the eyes.
Or at least a second keyboard at the right edge of the sequencer would help as one could move with the eyes to the keyboard that is closer to the note.

Speaking of that, I think in this context it would make sense to simplify the keyboard by making each key exactly one line wide and full-length, unlike with the shorter black keys and wider white keys now.

[C.Kerry]

Speaking of that, I think in this context it would make sense to simplify the keyboard by making each key exactly one line wide and full-length, unlike with the shorter black keys and wider white keys now.

In the StepSequencer all the rows are the same height, so they are exactly one key.
Making the Black notes full length just doesn't look right, it doesn't look like a keyboard then, which makes it harder to match things up.

As for the term 'Step' it is simply that, don't try to link them together.
There are 2 different Sequencers in PatternArp and PolyStepSeq. A NOTE Sequencer and a PATTERN Sequencer. Each has a number of Steps that can be programmed in them.

The Sequencer's Steps are triggered by the Host Clock to play the Notes.
The Playlist has Steps in a table/list t control which Pattern to play; Step#X play Pattern #Y and Repeat it #Z times - then goto the next Step in the list.
I don't know what other terminology would be more appropriate.

[magicmusic]

Can you please tell, if it is hard to add the feature that the program change messages are delay to beat, or end of sequence. Look in this video at 3:10, for what this feature is usefull too. It is a video from Karma.
I really dont understand wy Hardware synthesizer mostly have this feature.

I guess the reason why H/W keyboards with sequencers have that feature is because they are used to play Live.
Whereas VSTs are mostly used in sequencers with pre-recorded music - so you can set your program changes to the correct point.

If other people request this feature then I will take a look at it, but so far you are the only one. PatternArp has been my best seller before and not one customer has mentioned it.

The other issue is that adding any new GUI controls will most probably make old presets incompatible, which is something I really don't want to do.

But as I said, if several people request it here then I will look into it, see if it can be added and preset compatible.

ah so, thats a Problem, that it is not possible to add new GUI values without compatibility loss. then only a own Midi VST that delay notes and program change to next beat is possible

That Hardware synths are use more for live is maybe the reason, because with VST you miss the feature. So on live can not replace. I use soundblaster z with ASIO. even if set low latency of 2 ms it delay 30ms or more when i output dolby pro logic over spdif to my surround receiver. Most surround receiver have no 6 analog inputs.

VST computer music have lots more problems with latency then hardware. so a trigger of sequence quantize help alot to get precise timing. I set my Asio buffer to 8 ms, because 4 or 2 give sometime crackle.

Sequencer all have input quantisation. also mulab. But this work not on live play. only the note in the editor is then later show. and when you play the sequence later in sequencer it sound diffrent as what you play. So wy not add this feature, also cheap keyboards have in a VST or sequencer ?. I guess when nobody want this feature, Hardware Synths dont have it. And maybe music sound less monotonous, because it is easy that the pattern of the sequencer can change to avoid that same sequence must play in whole song

when you search for "midi input quantize vst" there are more that want such a delay feature. and some guys tell it is not possible

http://www.kvraudio.com/forum/viewtopic.php?p=5293714

EDIT: If it is possible that the grid can be larger i like also. but the text is large enough for me in the step sequencer. but your synthesizer i think to small and its hard to read the next. But with Mux it is possible that a own GUI can build with only the importants knobs. move a knob in your VST and choose menu "drag last tweaked parameter". only i see in mux is, that it seem not possible to give a new name. but ck modules have usefull names. Sample tank not. it show for filter a name channl 1 usr 1

[C.Kerry]

All that doesn't seem a lot of work, I think, but it would lead for the two GUI's to a much much much more readable GUI, with very very few modifications in fact, I'm pretty sure.

Actually, it's much more work than you would imagine. I won't bore you with an explantion why
But I am sensitive to the issues you raise because I know the newer HD monitors' resolutions do have a negative impact on these and other GUIs.

[fluffy_little_something]

Speaking of that, I think in this context it would make sense to simplify the keyboard by making each key exactly one line wide and full-length, unlike with the shorter black keys and wider white keys now.

In the StepSequencer all the rows are the same height, so they are exactly one key.
Making the Black notes full length just doesn't look right, it doesn't look like a keyboard then, which makes it harder to match things up.

As for the term 'Step' it is simply that, don't try to link them together.
There are 2 different Sequencers in PatternArp and PolyStepSeq. A NOTE Sequencer and a PATTERN Sequencer. Each has a number of Steps that can be programmed in them.

The Sequencer's Steps are triggered by the Host Clock to play the Notes.
The Playlist has Steps in a table/list t control which Pattern to play; Step#X play Pattern #Y and Repeat it #Z times - then goto the next Step in the list.
I don't know what other terminology would be more appropriate.

Yes, I know what they mean in each section. but when I first used it, I didn't know anything about STEP sequencers, so it was a bit confusing.

Regarding the design, I did some painting in Paint At the center my changes, which I think would allow you to see which note you are editing right there, without looking at the keyboard.
https://app.box.com/s/qvohckttcvxgzn357age
Btw, my darker lines look irregular in terms of darkness, but I noticed that that is because the lines are actually not at all of the same height It is alternating x , x+1, x, x+1, x pixels and so on.

[BlackWinny]

All that doesn't seem a lot of work, I think, but it would lead for the two GUI's to a much much much more readable GUI, with very very few modifications in fact, I'm pretty sure.

Actually, it's much more work than you would imagine. I won't bore you with an explantion why
But I am sensitive to the issues you raise because I know the newer HD monitors' resolutions do have a negative impact on these and other GUIs.

Yes but don't worry, it's just suggestions.


But really I thank you to have very well understood our eyesight handicaps (here and for ME80 for example).


So many other developers leave these kinds of suggestions remain totally dead letters without even any kind answer for a single question of contrast between colors without the least change in the sizes, places...

[C.Kerry]

But really I thank you to have very well understood our eyesight handicaps (here and for ME80 for example).

So many other developers leave these kinds of suggestions remain totally dead letters without even any kind answer for a single question of contrast between colors without the least change in the sizes, places...

I've been working on a BIG PolyStepSeq GUI - this is the progress so far - the PlayList window hasn't been changed (code change) and two options still need enlarging.

PolyStepSeq_BIG_GUI_Work.png

All the Numbers etc. have been enlarged and I improved the contrast ratios.
Let me know your comments