|
|
|
03-21-2012, 08:08 AM
|
#321
|
Human being with feelings
Join Date: Mar 2012
Posts: 1
|
Quote:
Originally Posted by VVV
Off course I use multicolors! ...
|
Just wondering what theme you had going on there, black background on the fx windows looks nice
|
|
|
03-21-2012, 10:24 AM
|
#322
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by UnderwaterSunlight
the track "pf-arpoh-beat" is very fascinating. which synth have you used ?
|
that's one of Michael Cavallo's (free) presets on a single instance of the awesome Zebra 2 synth. the Zebra 2 arp was a big inspiration for arp!0.
Quote:
Originally Posted by UnderwaterSunlight
however, i can't get your tracks at "bangzero.tumblr.com" to play - all i get is an error message when i click the play icon.
|
so do i. thanks for reporting that. i'll look in to it. in the meanwhile, you can play/download the tracks using the little "mp3" link.
ps- fixed the play errors
Last edited by bang; 03-21-2012 at 02:47 PM.
Reason: note fix; add links & credit
|
|
|
03-22-2012, 10:49 AM
|
#323
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
arp!0 - v0.78beta - 22 mar 2012 - little things release
hello all! new release. this primarily fixes some flawed logic for the step back in time step types. it also add alt/option-right-click to delete a step and control/command-right-click to insert a step. and it changes the icon for the step operation type from reverse-?: to !: for easier documentation.
enjoy! /dan
|
|
|
03-25-2012, 12:02 PM
|
#324
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
un-step?
hello folks! i am looking for input on arp!0 terminology. i think we need a new term for the step sequence. trying to document how the steps of the step sequence affect the steps of the input note sequence is just too ambiguous. :^) so, any ideas or preferences for a new word instead of "step"? a quick trip to the thesaurus turns up these possibilities:
pattern sequence
motif sequence
form sequence
schema sequence
motion sequence
shape sequence
design sequence
system sequence
i suppose "form sequence" is my favorite of the moment. but that's not a very strong preference. what says the group mind?
enjoy! /dan
|
|
|
03-25-2012, 01:34 PM
|
#325
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
more "step" alternatives:
progression sequence
program sequence
flow sequence
arrangement sequence
progression has something of the right feel to it.
just sort of thinking in public here. so no worries, but any input is welcome.
enjoy! /dan
|
|
|
03-26-2012, 01:15 AM
|
#326
|
Human being with feelings
Join Date: May 2006
Posts: 143
|
Quote:
Originally Posted by bang
if you mean + & - 12, for a total of 24, then no, that's the current limit. how specifically would you use more than that? would it be more arp or sequencer like? there would be some tricky gui issues to increase the transpose range without making things huge or unwieldy. i've thought about it but haven't come up with any great ideas so far.
enjoy! /dan
|
I´m thinking more like a sequenser. 2 octavs is good but sometimes you want to accent a note 2.5 octavs up or more. Esp when doing crazy porta stuff och percussive accents, or both at the same time.
This is so good already, but this was one thing I missed.
/Per
|
|
|
03-26-2012, 01:16 AM
|
#327
|
Human being with feelings
Join Date: Mar 2009
Posts: 243
|
wow, dan, you really are a philosopher.
any of these terms which you might choose sounds fine.
"motif" reminds me of a certain keyboard by yamaha which has an arp too, but i think the arpbangzero is more advanced.
looking forward to the actual release.
b t w, i got your arp working in cubase studio 5. however, i need always to properly expand the gui window manually as this appears small whenever i launch cubase.
|
|
|
03-26-2012, 01:18 AM
|
#328
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by amenbrother
I´m thinking more like a sequenser. 2 octavs is good but sometimes you want to accent a note 2.5 octavs up or more. Esp when doing crazy porta stuff och percussive accents, or both at the same time.
This is so good already, but this was one thing I missed.
|
check out the settings pane in the latest version. i added a couple of options that support up to 4 octaves. they can make the trans grid kind of big, but keep it simple.
enjoy! /dan
|
|
|
03-26-2012, 01:21 AM
|
#329
|
Human being with feelings
Join Date: May 2006
Posts: 143
|
Quote:
Originally Posted by bang
wow. new release. this is quite something i think. or at least my poor, addled brain is telling me so. something about the incremental effort to add features increasing in non-linear ways as the code size grows. anywho...
so, big change is new step types. emphasis on big. here's a bit of screen:
i did update the documentation for this. but i think that needs work. a lot of work maybe. or application notes. or tutorials. or something. there is a "quick" overview below. but i dunno. i'm not sure my words are working very well just now. the executive summary is that the first two rows jump around in the input notes by position. the 3rd row recalls notes from the recent history, which is quite different. the 4th row does random notes and other (very) odd stuff. and the 5th row are "meta" steps which can be added to other step types for special behaviors, including skipping note output. i'll be working on better documentation for this. question are very welcome, and might help a lot.
other than all that, this release also adds the option of increasing the range of the transposition sequence up to 4 octaves. i went with the simplest way of doing this, so it just adds rows to the transp grid, making the height of the gui somewhat large. see the settings page for the relevant options.
i also moved the slider grids around so that the related accent and offset slider grids are one above another. this makes it easier to see when they are in sync or not. and i tweaked the variant program change logic. and i fixed a couple of pretty nasty bugs.
and there we have it. major changes. so i won't be surprised if there are some glitches. feedback please. big tia! and...
enjoy! /dan
____
step types overview:
the first two rows basically let us select notes based on their position in the input sequence. the input note sequence comes from the current input notes, the sort type, any active sort transform, the order type, and the replicant octaves. within that note sequence, the first two rows of sort type jump forward or back by 1, 2, or 3 steps, or jump to the first or last step. the important bit here is that the jumps are based on position. this lets us make various note patterns based on relative positions in the input note sequence.
the 3rd row takes a different approach and selects notes based on the recent history of output notes. these step types select notes from the last 4 generated by arp!0. this is a very useful alternative to selecting notes by their position in the input sequence. but it's a bit hard to describe exactly how this temporal alternative is useful except by examples. that's coming rsn.
the 4th row has a number of special step types. the diamond step type reverses the direction in which the input note sequence is processed. for the bidirectional orders, this just toggles the current direction. for the unidirectional up and down orders, this step type will actually change the current order from up to down and down to up. note that this reverse step will generate a repeat of the previous note, much like the "sticky" up-down and down-up orders do. we can avoid this repeated not using the contract metastep described below.
the next two step types select random notes. the "?" step just plays a random note from anywhere in the input sequence. the "?><" type randomly choose either the next or previous note from the input sequence.
the last type, step operation, is sort of a can of worms i'm afraid. in its simplest form it just jumps back in the step sequence to some earlier step. this allows us to have a set of prefix steps that generate initial seed notes followed by a looping set of steps based on those seed notes. this is essential to create certain kinds of arp patterns. but on top of that "simple" form, i implemented "meta" step operations which make it possible to randomly select various subsets of the entire step sequence. how this works is very hard to describe clearly however. which makes me question how useful it is. i'll work on the docs for that when it's not so late in the day.
the 5th row contains "meta" step types: modifiers which can be added to any of the "normal" types. the first is subtract, or "-", which just inhibits note output for a step.
the next type is contract, or "'", which combines a step with the following step. contracted steps change the input note sequence just as if they occurred normally. but the contracted step outputs no notes, takes no time, and is immediately followed by the next step sequence step. this is extremely useful for making steps which modify a previous step without repeating it. this is another feature that needs examples. rsn!
next is resortx, or "~". this simply triggers an update for any current sort transform, which is useful to update random steps in the transform.
finally we have the section meta type, or ":". this just marks a step as the start of a section, which is then referenced by the step operator type.
_____
release notes:
- finish work on new step types. see updated documentation for details.
- add options to expand transpose range/gui: range can be 24/36/48 semitones. add transpose base option: transpositions can start at -24/-12/0 semitones.
- change positions of slidergrids to align related accent & offset seqs.
- change variant program change logic to support > 8 variants; reset seq positions and don't save changes to previous variant now selected by enabling program changes prior to variant program change; add next & previous variant and play/pause pc's.
- bugfix: bogus unidirectional offset logic
- bugfix: truncated sortx length logic
|
Wicked!
Thanx a lot!
|
|
|
03-26-2012, 01:25 AM
|
#330
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by UnderwaterSunlight
wow, dan, you really are a philosopher.
|
practical philosophy is one of my vices, i confess. :^)
Quote:
Originally Posted by UnderwaterSunlight
any of these terms which you might choose sounds fine.
|
for the moment i am going with "dir sequence" for "directions". this is less a matter of philosophy than clarity in the documentation. terminology matters, imo. and the confusion between the "steps" sequence and steps generally was really bad.
Quote:
Originally Posted by UnderwaterSunlight
b t w, i got your arp working in cubase studio 5. however, i need always to properly expand the gui window manually as this appears small whenever i launch cubase.
|
don't know what might be going on there, and don't have cubase to check it out i'm afraid. i try to request a window that's wide enough and extra high. do other Jesusonic plugins open larger?
|
|
|
03-26-2012, 01:39 AM
|
#331
|
Human being with feelings
Join Date: Mar 2009
Posts: 243
|
i tested reacomp from the reaplugs series. it also comes up with its gui too small.
|
|
|
03-26-2012, 01:42 AM
|
#332
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by UnderwaterSunlight
i tested reacomp from the reaplugs series. it also comes up with its gui too small.
|
thanks for checking that out. there also seems to be a problem on the mac with the Js gui size settings. i'll try to do an issue report on that at some point.
|
|
|
03-26-2012, 02:06 AM
|
#333
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
arp!0 - v0.79beta - 26 mar 2012 - terminology matters release
hello all! another new release. changed the names of the step/transp sequences to dir, for directions, and trans. fixed the logic for the updown/downup orders to work better with the new dir sequence types. tweaked the example multi-color schemes and added a new one. a few other things listed in the release notes below.
i also improved the docs for the dir sequence types. in particular, there are a few examples of how the contract meta direction works. contract can be *very* useful. i'm still intending to do some app notes for the more obscure directions. i'll copy the new dir docs below fwiw. questions quite welcome.
enjoy! /dan
Code:
dir: directions which modify the play order. the dir types are:
> - next step: plays next note in sequence based on note sort, sort
transform, and order. this is the "normal" next note.
>| - last step: plays the last note in the input note sequence.
>2 - 2nd next step: plays the 2nd note ahead in the input note sequence.
>3 - 3rd next step: plays the 3rd note ahead in the input note sequence.
< - previous step: plays the previous note in the input note sequence.
|< - first step: plays the first note in the input note sequence.
<2 - 2nd previous step: plays the 2nd previous note in the input note
sequence.
<3 - 3rd previous step: plays the 3rd previous note in the input note
sequence.
= - same step: repeats the immediately previous note
<= - back one step in time: replays the note which was played just before
the previous note. this is based on the history of notes arp!0 has
played, and can be different from previous notes in the input note
sequence when the normal sequence order has been changed by special
steps like first/last/random/etc.
<=2 - back 2 steps in time: replays the 2nd note prior to the last.
<=3 - back 3 steps in time: replays the 3rd note prior to the last.
<> - reverse: alternates between up and down unidirectional orders.
changes the current play order for bidirectional orders
(up-down/updown/down-up/downup). by default, repeats the previous
note in sequence, which gives the effect of the "sticky" up-down and
down-up orders. add the contract meta to avoid this duplicate
note and give the effect of the "bouncy" updown/downup orders.
? - random step: plays a random step in the input note sequence.
?>< - randomly next or previous step: randomly does either next step or
previous step.
!: - dir operation: this is a special dir step type that modifies the
order of the dir sequence itself. can of worms. see description
of the section meta below.
meta directions are optional behaviors which can be added to the normal
dir types. when a meta dir is selected in the dir dropdown menu it will
be added or removed from whatever basic step type is already selected for
that dir step. the meta dir types are:
- - subtract meta: suppresses note output for a step.
' - contract meta: combines a dir step with the following dir step.
contracted dir steps change the input note sequence just as if they
occurred normally. but the contracted dir outputs no notes, takes
no time, and is immediately followed by the next dir sequence step.
contracted dir steps provide a way to specify a step relative to
another step. for example:
|<' > - specifies the 2nd note in the input sequence: "|<'" is a
contracted "first step" dir step. it selects the first
note in the input sequence, but otherwise does nothing
because it is contracted. the following ">" dir step then
generates the next note after that, which is the 2nd note.
>2' >3 - specifies the 5th note ahead in the input sequence. ">2'"
selects the 2nd note ahead, but does not play it because it
is contracted. ">3" plays the 3rd note after that, which
is 5 notes ahead.
? <=' > - generates random notes interleaved with sequential notes
every other step. "?" selects a random note from the
input sequence. "<='" selects the whatever note was
output before that random note, but generates no output
because it is contracted. ">" then generates the next
note after that in the input sequence.
~ - resortx meta: triggers an update for any active sort transform before
the step.
: - section meta: marks a step for special dir sequence operations which
are triggered by dir operation steps. dir operation steps will have
different effects when combined with dir meta steps. when a dir
operation step occurs, the normal dir sequence order is changed as
follows:
!: - normal: rewind the dir sequence to the closest previous step with
a section meta. this is useful to restart the dir sequence from
some point after the first step. it enables an initial, one time
set of prefix dir steps followed by a different set of repeating dir
steps.
~!: - "!:" + resortx meta: seeks forward in the dir sequence randomly
to one of the following steps marked with the section meta.
!:- - "!:" + subtract meta: terminates a set of randomly selected
section metas. the "~!:" dir operation will not seek forward past
this step, and the "!:'" dir operation seeks to the step following
this one.
!:' - "!:" + contract meta: seeks forward in the dir sequence to the
step after the next "!:-" dir operation.
:!: - "!:" + section meta: seeks back to the first dir step.
release notes:
- tweak multi colorschemes in global settings file
- fix dropdown buttongrid color bug
- add alt/option-click [arp!0] for reload settings
- add control/command-click [arp!0] for toggle global options
- fix updown/downup order logic to handle dir:first/last/prev better which
prevents some dir seqs that stick at high/low octave boundaries
- changed step sequence name to dir, for directions. changed transp seq
name to trans.
- added program change base+29 for restoring saved play positions for all
sequences. renumbered some of the previous variant program changes to
make room.
- allow contract and resortx metas on same step.
|
|
|
03-26-2012, 02:12 AM
|
#334
|
Human being with feelings
Join Date: Jan 2007
Location: mcr:uk
Posts: 3,889
|
Thanks Dan! I think you're a strong contender for best JS ever.
|
|
|
03-26-2012, 02:19 AM
|
#335
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by UnderwaterSunlight
i tested reacomp from the reaplugs series. it also comes up with its gui too small.
|
on second thought, that's odder still. reacomp is a standalone vst, not a Jesusonic plugin. seems like it really should be able to show up at the right size. i'm less surprised that ReaJS doesn't size correctly. does the Liteon/vumetergfx size wrong UnderwaterSunlight?
|
|
|
03-26-2012, 02:33 AM
|
#336
|
Human being with feelings
Join Date: May 2006
Location: Surrey, UK
Posts: 19,677
|
^^^
In energyXT, the ReaComp VST opens with the correct size. reaJS opens with a standard size and generally has to be resized manually for the loaded JS FX.
vumetergfx needs resizing vertically.
Also, is "control sequence" a suitable term?
__________________
DarkStar ... interesting, if true. . . . Inspired by ...
|
|
|
03-26-2012, 02:37 AM
|
#337
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by IXix
Thanks Dan! I think you're a strong contender for best JS ever.
|
very nice of you to say so IXix. thanks.
|
|
|
03-26-2012, 03:04 AM
|
#338
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by DarkStar
^^^
In energyXT, the ReaComp VST opens with the correct size. reaJS opens with a standard size and generally has to be resized manually for the loaded JS FX.
vumetergfx needs resizing vertically.
|
so it seems arp!0 is not alone. i'll put this on my "short list" of desirable Js fixes. maybe when the OSC dust settles Js could get some developer love. :^)
Quote:
Originally Posted by DarkStar
Also, is "control sequence" a suitable term?
|
quite suitable. do you think it is much better than "directions sequence"? that sequence is sort of a map of how to traverse the input note sequence. "directions" appealed to me because it suggests ways of moving between steps.
|
|
|
03-26-2012, 12:39 PM
|
#339
|
Human being with feelings
Join Date: Mar 2009
Posts: 243
|
concerning reacomp standalone vst: to be more precise concerning my previous statements:
reacomp standalone's gui is only crippled in cubase 5 64bit as it must be bridged therein. in cubase 5 32bit its gui is all right.
|
|
|
03-30-2012, 08:53 PM
|
#340
|
Human being with feelings
Join Date: Aug 2011
Location: Brasil
Posts: 10
|
Excellent arpeggiator, but I think that some functions could be simplified or together as the reFX Nexus. Congratulations!! Thank you.
See the animation, maybe you will inspire.
https://lh4.googleusercontent.com/-1...s800/nexus.gif
|
|
|
03-30-2012, 09:44 PM
|
#341
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by Plauto
Excellent arpeggiator, but I think that some functions could be simplified or together as the reFX Nexus. [...]See the animation, maybe you will inspire.
|
the animation is tantalizing. looks quite clever. some of what seems to be happening in the animiation wouldn't work well in arp!0 because arp!0's sequences can be different lengths. other things look cool, but might not be functionally better than the current ui. some of it might be quite nice, but just too hard to implement in Js. it's hard to tell from such a quick animation. i would need some explaination of exactly what is going on before it could be very inspiring. or a manual, which doesn't seem easy to download.
have you used the Nexus arp enough to clarify any of this Plauto? what would really help is a breakdown of specific features of the Nexus arp ui that you think work better than arp!0's.
enjoy! /dan
|
|
|
03-30-2012, 10:13 PM
|
#342
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
ps- guess i will also say here that i am trying to wind down arp!0 development now to get something ready for a 1.0 "release". i have one last feature on my not so short list that i am working on now: more flexible tempos/sync. once that is done i hope to do a thorough test cycle and get the documentation up to date and edited for clarity. then it feels like i need some time putting arp!0 to use to get some perspective on what might come next. arp!0 does *way* more than i ever imagined it would back when i started this a few months ago. i'd like to see what i can do with the odd thing it has turned out to be. always open to input of course. any *critical* missing pieces or usability problems folks? enjoy! /dan
Last edited by bang; 03-30-2012 at 11:41 PM.
Reason: <awk
|
|
|
03-30-2012, 11:31 PM
|
#343
|
Human being with feelings
Join Date: Aug 2011
Location: Brasil
Posts: 10
|
There must be someone else who use the Nexus, especially one that has better communication in English, I can try to explain, but as I'm using an online translator, things get complicated. The market is starved for good arpeggiators, there is some, but none works with excellence as the Nexus, is fantastic, you have taken the first step with arp! 0, your ideas are great, but you should also think of the practicality of use. See the attached assembly on how the arp! 0 could function in a simple way, considering the operation mode of the Nexus arpeggiator.
|
|
|
04-03-2012, 09:47 PM
|
#344
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by Plauto
See the attached assembly on how the arp! 0 could function in a simple way, considering the operation mode of the Nexus arpeggiator.
|
thanks for the mockup Plauto. it does help me understand what's going on in the Nexus arp. if i have it right, it is superimposing equivalents to arp!0's length, gate and trans seqs and a 4th seq in a single space. and length is represented using wider columns. this is quite clever, especially when fitting a powerful arp into a small space as part of a larger ui. and the use of width to represent length is a good visual cue to what length does. altogether it looks quite nicely done. but i think there are some tradeoffs. while superimposing 4 sequences keeps things close together, it also makes the click targets smaller and somewhat ambiguous. and changing some values requires click and drag. because the same 4 sequences in arp!0 have separate spaces, the click targets can be larger and you can change any dropped down value with a single click. for working on one sequence at a time i think arp!0's approach has some definite advantages. and as i said earlier, because arp!0's sequences can have different sizes, using width to represent step length won't work. a current long step can be in different columns for different seqs. finally, sorting out what clicks do what in several superimposed sequences would be substantially harder to do in Jesusonic than the current approach. to some extent, arp!0's ui reflects the limits of the Js graphics api. it is, i hope, a creative and useable ui built from a somewhat basic set of tools. while the exact approach of the Nexus arp doesn't seem right for arp!0, it is certainly full of good ideas. thanks very much for introducing it to me. enjoy! /dan
Last edited by bang; 04-03-2012 at 09:54 PM.
|
|
|
04-04-2012, 12:58 AM
|
#345
|
Human being with feelings
Join Date: Jan 2007
Location: mcr:uk
Posts: 3,889
|
Hey Bang, I think the size limit just got bumped .
|
|
|
04-04-2012, 01:26 AM
|
#346
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by IXix
Hey Bang, I think the size limit just got bumped .
|
it *did*! it *did*! reaper422pre2! woot! :^) also fixes for midi bus handling and too much code in parens!
which means in the short term that i will bump the max variants to 12 in the upcoming release. and we get a new midi bus setting which makes multiple arp!0 instances for one track workable. and i think it means i can get rid of the "horrible hack" i used to work around the parens bug. but that will require folks to update to at least Reaper 4.22. will that be a problem anyone?
not sure what else it means right now. i *really* want to get something called "1.0" out the door and take a break from coding for a while. (and do some other paying coding rsn i think.) i've thought about adding another couple of optional midi controller sequences. i'm reasonably happy with note probabilities as an option for one of the control sequences, so i don't have any immediate plans to add a dedicated note probability sequence. personally, i'd like to see some grander scheme of per sequence probabilities, particularly for the dir sequence. but those ideas need to percolate quite a bit yet. so while these Js fixes open the door to new settings and ui, i want to get the current arp!0 house in order before i go through it. or something. :^)
thoughts anyone?
enjoy! /dan
|
|
|
04-04-2012, 06:37 AM
|
#347
|
Human being with feelings
Join Date: Jan 2011
Posts: 1,296
|
Quote:
Originally Posted by bang
will that be a problem anyone?
|
I'm just about always on the latest pre, so no!
__________________
I am a universal adaptor.
|
|
|
04-04-2012, 09:53 AM
|
#348
|
Human being with feelings
Join Date: Dec 2008
Posts: 2,111
|
Hi Bang, Thanks for this amazing arp!
I have some trouble getting arp!0 to sync to host. When I start playback in Reaper beginning from start of measure, sometimes arp!0 does not start from the beginning of the step sequence. Why is that? When this happens it seems to be difficult to resync arp!0 back to correct "phase".
Sync is also lost when playback is looped in Reaper. Any idea how to prevent that?
jnif
|
|
|
04-04-2012, 10:14 AM
|
#349
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
hi jnif! welcome to arp!0-land!
arp!0 remembers the play positions for each sequence as of the last time they were edited or saved in a preset. if you reset all play positions to 1 by shift-control-clicking on any first step arp!0 should start there whenever host playback starts. (shift-command-click on macs.) you can manually recall saved play positions by right-clicking on the current variant button. this is because right-clicking variants generally resets sequence play positions. it may be easier to see what's happening here if you do this while arp!0 is paused. pause + right-clicking the current variant shows the playback positions that will be restored whenever host playback starts.
if i've misunderstood and this is not your issue please clarify.
arp!0 does not currently restore play positions when playback loops. this is so a playing arp continues seamlessly across the loop. perhaps there should be an option for this? and maybe there should be an option to restore playback positions on pause as well? playback positions are sort of a hidden setting in arp!0. i'm not entirely happy with that. ideas anyone?
enjoy! /dan
Quote:
Originally Posted by jnif
When I start playback in Reaper beginning from start of measure, sometimes arp!0 does not start from the beginning of the step sequence.[...]Sync is also lost when playback is looped in Reaper.
|
Last edited by bang; 04-04-2012 at 10:17 AM.
Reason: <quote
|
|
|
04-04-2012, 10:16 AM
|
#350
|
Human being with feelings
Join Date: Jan 2007
Location: mcr:uk
Posts: 3,889
|
Quote:
Originally Posted by bang
will that be a problem anyone?
|
Not me. I'm on the official release as soon as it hits the shelves and often the latest prerelease if something in the changelog catches my eye.
As for features/changes etc., the current state is a little over my head now so I'll just trust that you'll continue to make a superb arp and I'll catch up with it eventually.
|
|
|
04-04-2012, 10:33 AM
|
#351
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by IXix
As for features/changes etc., the current state is a little over my head now so I'll just trust that you'll continue to make a superb arp and I'll catch up with it eventually.
|
me too, actually. i feel a little like Dr. Frankenstein. :^)
|
|
|
04-04-2012, 11:59 AM
|
#352
|
Human being with feelings
Join Date: Dec 2008
Posts: 2,111
|
Quote:
Originally Posted by bang
arp!0 remembers the play positions for each sequence as of the last time they were edited or saved in a preset. if you reset all play positions to 1 by shift-control-clicking on any first step arp!0 should start there whenever host playback starts. (shift-command-click on macs.) you can manually recall saved play positions by right-clicking on the current variant button. this is because right-clicking variants generally resets sequence play positions. it may be easier to see what's happening here if you do this while arp!0 is paused. pause + right-clicking the current variant shows the playback positions that will be restored whenever host playback starts.
|
Thanks, those instructions help a lot.
Still the play position gets out of sync sometimes even when I think I have not changed it or saved presets. Now I'm able to reset it back to start with shift-ctrl-click.
Is it possible that auto-save could mess up the play position? For example when playback is stopped the play position usually does not stop at the first step. Then if auto-save happens in the background it could save the play position to the incorrect position where it was left when playback stopped. I don't know if this kind of auto-save problem is really happening, maybe the problem is something completely different and I'm doing something wrong. The play position just seems to get to incorrect position quite randomly.
Quote:
Originally Posted by bang
arp!0 does not currently restore play positions when playback loops. this is so a playing arp continues seamlessly across the loop.
|
I think this is OK behaviour. But there seems to be problems in some cases even when loop length and arp sequence lengths are identical. For example if I have two long MIDI notes (a two note pad chord). Then I playback a loop in the middle of that chord so that those two notes are sent to arp!0. In this case the first loop round is different than the subsequent loop iterations. It sounds like the order of the two notes changes in the end of the first loop round, but still the order is not changed in the "notes" row in the bottom of arp!0.
jnif
|
|
|
04-04-2012, 01:12 PM
|
#353
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by jnif
Is it possible that auto-save could mess up the play position?[...]The play position just seems to get to incorrect position quite randomly.
|
very astute jnif! i think that's exactly what is happening. i've noticed Reaper seems to invoke the @serialize code to save presets more often than i expected. but i hadn't made the connection to "randomly" saved position. i will remove the logic to save seq positions on save for the next release, coming r.s.n.
Quote:
Originally Posted by jnif
I think this is OK behaviour. But there seems to be problems in some cases even when loop length and arp sequence lengths are identical. For example if I have two long MIDI notes (a two note pad chord). Then I playback a loop in the middle of that chord so that those two notes are sent to arp!0. In this case the first loop round is different than the subsequent loop iterations. It sounds like the order of the two notes changes in the end of the first loop round, but still the order is not changed in the "notes" row in the bottom of arp!0.
|
is the number of sequence steps odd and the number of notes even, or vise versa? does this happen only the first time through? does your loop in the middle of the sus'd notes start on a beat boundary? there is some tricky business here because Reaper is sending noteoff and noteons when the loop cycles, but the noteoffs/ons don't seem to happen at exactly the "right" times if my fuzzy memory is right. you could try turning off the clear notes on host seek option in the settings pane. and, what behavior are you hoping for?
enjoy! /dan
|
|
|
04-04-2012, 01:31 PM
|
#354
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by jnif
In this case the first loop round is different than the subsequent loop iterations.
|
looking at this a bit more, i am seeing that when you initially start a loop in the middle of sus'd notes it picks up the first note on the first beat. subsequent loopbacks after that don't get the first note on the beat. i'll look into this. but as i said, Reaper may not be delivering the noteoffs/ons to arp!0 so that it is possible to get it just right. i worked pretty hard to get this to work when starting playback. so if it's not working on loopback it might just not work. we'll see... enjoy! /dan
|
|
|
04-04-2012, 09:48 PM
|
#355
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
arp!0 - v0.80beta - final feature creature release - 4 apr 2012
hello all! new release! this primarily adds the ability to specify the tick time as either synchronized or absolute. and the old sync'd fractions can now be scaled. perfect for Reichian phase music and wind chime emulations! :^) and more variants and a midi_bus setting as mentioned above. you will need 4.22pre2 or later for these, or any windows Reaper for more variants. also a few tweaks, including the fix for "random" resets of saved seq positions.
the tick time setting is more powerful/complex in this release. i will append the relevent bit of documentation below. mainly you will see a scale slider below the tick (was sync) fractions. if you don't touch this arp!0 operates as before. you can also right-click the "tick" label to use an unsynchronized absolute time for the tick. there are still fractions in the dropdown, but these only set the range of the slider. i'm quite interested in how well this scheme works for folks. so if you're inclinded feedback is welcome.
one more note concerning the recent Js bugfixes: i doubt the "too much code in parens" fix will make it into a ReaJS update very soon. alas, that is the main limiting factor for many potential gui changes. since i really want to support ReaJS, this means there is still a damper on future gui enhancements to some extent.
i'm off on a road trip for a few days. will have the dev computer along, but time will be somewhat limited. hope this release works well for folks.
enjoy! /dan
release notes:
- hilight edited step when showing dropdown
- limit output range of midi note numbers
- scaled, absolute or synchronized tick times
- midi bus setting
- bump max variants to 12
- remove save seq play positions when preset is saved
tick docs:
Code:
tick: sets the time interval between arp steps according to host tempo or
absolute time. tick has two modes: synchronized or absolute, which are
selected on the setting pane. or right-click the "tick" label to toggle
between these modes. in sync mode, the tick time is relative to the host
tempo, and displayed as a fraction of a whole note. in this mode arp!0
syncs to exact beats when the host is playing or recording. click the
sync fraction to show a dropdown menu of fractions and a scale slider.
click any fraction to select it. the scale slider allows sync'd ticks
that are not exact fractions. it shows a scaling factor from 0.75x to
2.0x, with a midpoint line at 1x. text at the left end of the slider
shows the current scale factor, or "exact" if scaling is not in effect. it
also shows the tick time in parenthesis. click in the slider to set a
scale factor. right-click a fraction to disable scaling. the sync
fraction on the tick button will have a "+" or "-" suffix if scaled
greater or less than the exact fraction. in absolute mode the tick time
is displayed as a decimal number of seconds, and the tick label will have
a "~" suffix. click the number to show a slider and a grid of fractions.
text at the left end of the slider shows the tick time in seconds. click
the slider to select a tick interval. the fractions select the range of
the slider relative to the current host tempo, again from 0.75x to 2.0x of
the fraction of a whole note selected. click these fractions to change
the range of the slider, but not change the current tick time.
right-click a fraction to change the slider range and select the 1x value
on the slider as a tick time. shift-click the tick button to for a
high-resolution slider with a range of +/- 10% of the current value.
|
|
|
04-04-2012, 10:22 PM
|
#356
|
Human being with feelings
Join Date: Jan 2011
Posts: 1,296
|
Mr bang, you are going to have to make some stellar documentation for this thing (illustrated, preferably, with bright colours, and few words), because it's starting to get pretty complex, to my mind.
Your latest posts seem to have all been in Greek.
__________________
I am a universal adaptor.
|
|
|
04-04-2012, 10:34 PM
|
#357
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by copacetic
Mr bang, you are going to have to make some stellar documentation for this thing (illustrated, preferably, with bright colours, and few words), because it's starting to get pretty complex, to my mind. Your latest posts seem to have all been in Greek.
|
yeah. yeah. i know. dir types and the tick options did get a bit out of hand. but hopefully all the complex power user stuff is optional. and while the quick reference is very brief, i think if you sat down in front of arp!0 and read through it it would make more sense. i've tried to be clear and to the point anyway. pictures and tutorial videos would be better. maybe someday. i have thought about doing a few screencasts. i bet that's harder than it seems. :^)
questions always welcome! enjoy! /dan
ps- thought i'd got rid of all the Greek letters a while back. darn!
|
|
|
04-04-2012, 11:05 PM
|
#358
|
Human being with feelings
Join Date: Jul 2006
Posts: 626
|
Quote:
Originally Posted by copacetic
[...]it's starting to get pretty complex, to my mind.
|
one more thing: i am ok with powerful things being somewhat complex to use. but it is very important to me that the basics are very simple and easy. so, have the recent power-user bits made the simple things more complex for you copacetic? anyone? big tia! /dan
|
|
|
04-05-2012, 02:09 AM
|
#359
|
Human being with feelings
Join Date: Jan 2011
Posts: 1,296
|
Quote:
Originally Posted by bang
one more thing: i am ok with powerful things being somewhat complex to use. but it is very important to me that the basics are very simple and easy. so, have the recent power-user bits made the simple things more complex for you copacetic? anyone? big tia! /dan
|
I haven't actually been using the latest few, as my music PC is in pieces, with the room it's in being painted, when I get connected again, I will have a look, certainly.
__________________
I am a universal adaptor.
|
|
|
04-05-2012, 05:27 AM
|
#360
|
Human being with feelings
Join Date: Mar 2012
Location: Italy
Posts: 132
|
omg it's awesome o,O
thanks so much for it!
hoping for a guide and for ppl sharing presets :P
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 03:42 AM.
|