eXT 2.5.4 and Reaper 3.75(its not shown in reaper),XP SP3,Athlon XPToneCarver wrote:Nope, no requirement for SSE2. What host, operating system and CPU are you running?tomtoo wrote:Does it need sse2 , fails to open for me.
Greetings
Thomas
.
It's probably a bit much to give each rover or striker tile its own duration but the next version (or maybe the version after the next version) will have a duration jitter control that will give some probability-based variation to the note durations. I could see maybe having something like a duration tilt (just thinking out loud here...) that makes the note length for high notes longer (or shorter) than low notes, similarly to how the note probability tilt works. Interesting, deserves some thought.SaganTech wrote:Now I have a suggestion that would make a significant improvement to this plug-in and would be fairly easy to implement. If each note/wallhit or each rover had its own duration. It would make this plug produce more varied and less "wind-chime" like results.
The next version won't have full midi learn but it is likely to have some midi mapping in there via user-editable text file that describes the midi assignments. Using a text file description is not as convenient as midi-learn but it is a good step in the right direction for having full midi-learn someday.ecamburn wrote:midi learn on this, at least things like rows, cols, and wall controls would be unreal.
so when you sayToneCarver wrote:Also, there is no restriction on the scales being defined in ascending order. They can be descending, zig-zag, whatever.
does that mean "high notes" according to highest frequency notes (midi note numbers) in the scale file, or "high notes" according to highest numbered notes (note 1, note 2, etc.) in the scale file?ToneCarver wrote:I could see maybe having something like a duration tilt (just thinking out loud here...) that makes the note length for high notes longer (or shorter) than low notes, similarly to how the note probability tilt works.
nova3 reports over 64 parameters , to the host , for automation ...ecamburn wrote:midi learn on this, at least things like rows, cols, and wall controls would be unreal.
thanks for the tip normal. assigning knobs as we speak...normal wrote:nova3 reports over 64 parameters , to the host , for automation ... including those you mention ...
Good question. My natural inclination is to use the midi note numbers to define which notes are the "high notes" relative to the other notes. This is how the note probability tilt identifies the low and high notes. It makes it easier to adapt to scale transpositions and keeps it independent from the scale rotation. However, I had not considered using the positions in the scale definition files for defining what notes are high and low. Interesting perspective. Can you give me an example of what sort of behavior you are thinking about?terriandralph wrote:I want to make sure I understand the concept correctly...
You mentioned earlier that
so when you sayToneCarver wrote:Also, there is no restriction on the scales being defined in ascending order. They can be descending, zig-zag, whatever.
does that mean "high notes" according to highest frequency notes (midi note numbers) in the scale file, or "high notes" according to highest numbered notes (note 1, note 2, etc.) in the scale file?ToneCarver wrote:I could see maybe having something like a duration tilt (just thinking out loud here...) that makes the note length for high notes longer (or shorter) than low notes, similarly to how the note probability tilt works.
I hope its the latter.
Thanks. I did not do anything explicit to require SSE2 but there may be some default settings that assume SSE2 so I'll look into disabling those and include a non-sse build in the next release if possible.tomtoo wrote:eXT 2.5.4 and Reaper 3.75(its not shown in reaper),XP SP3,Athlon XPToneCarver wrote:Nope, no requirement for SSE2. What host, operating system and CPU are you running?tomtoo wrote:Does it need sse2 , fails to open for me.
Greetings
Thomas
That would be nice !ToneCarver wrote: Thanks. I did not do anything explicit to require SSE2 but there may be some default settings that assume SSE2 so I'll look into disabling those and include a non-sse build in the next release if possible.
Perhaps the end result will not occur as anticipated, but my main concern is that if midi note numbers are used to define which notes are "high notes", the use of the duration tilt would result in the notes of a bass line tending to be of shorter duration and the notes in the upper parts tending to be of longer duration (or vice versa) and make the note durations in the parts too predictable. I just thought that defining which notes are "high notes" using the positions in the scale definition files could accomplish two different tasks; if the higher midi numbers correlate with the higher positions in the scale definitions files, then the effect you initially intended for the duration tilt would occur, but if I wanted to be able to mix the durations between all of the parts for variety's sake, defining which notes are "high notes" using the higher positions in the scale definition files would accomplish this task (since I can assign both high and low midi note numbers at higher positions in the scale definition file).ToneCarver wrote:Good question. My natural inclination is to use the midi note numbers to define which notes are the "high notes" relative to the other notes. This is how the note probability tilt identifies the low and high notes. It makes it easier to adapt to scale transpositions and keeps it independent from the scale rotation. However, I had not considered using the positions in the scale definition files for defining what notes are high and low. Interesting perspective. Can you give me an example of what sort of behavior you are thinking about?terriandralph wrote:I want to make sure I understand the concept correctly...
You mentioned earlier that
so when you sayToneCarver wrote:Also, there is no restriction on the scales being defined in ascending order. They can be descending, zig-zag, whatever.
does that mean "high notes" according to highest frequency notes (midi note numbers) in the scale file, or "high notes" according to highest numbered notes (note 1, note 2, etc.) in the scale file?ToneCarver wrote:I could see maybe having something like a duration tilt (just thinking out loud here...) that makes the note length for high notes longer (or shorter) than low notes, similarly to how the note probability tilt works.
I hope its the latter.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026
