Man everything has been very quiet lately.
Is everyone recovering from the New Year?
-S
Crickets?
That's true for me, for sure. I'm nervous about doing anything interesting here until the new version drops. Part of that is the secrecy -- it is impossible to know what the changes will be.
Still wouldn't you think things would be forward compatible?
I was thinking I was in some sort of paradox and was cutoff from the Usine world...hahah
I kept looking at the forum and everyone was so silent...
So regardless, lets talk about what you want to do with Usine in the New Year?
-S
I was thinking I was in some sort of paradox and was cutoff from the Usine world...hahah
I kept looking at the forum and everyone was so silent...
So regardless, lets talk about what you want to do with Usine in the New Year?
-S
"Every act of creation is first an act of destruction." -Picasso
I would like to announce that I am working on a Holly-Chord, which is essentially Midi-Harmony III.
Instead of Hard-coded arrays of only 5 harmonies, I built a file-based chord-by-key.
This allows a simple text file, as well as dynamic update to make custom harmonies and chords.
Currently a close friend of mine is updating a chord offset list and it will contain a "Huge" amount of chords including inversions.
Already 100+ different variations and chord-types.
-S
Instead of Hard-coded arrays of only 5 harmonies, I built a file-based chord-by-key.
This allows a simple text file, as well as dynamic update to make custom harmonies and chords.
Currently a close friend of mine is updating a chord offset list and it will contain a "Huge" amount of chords including inversions.
Already 100+ different variations and chord-types.
-S
"Every act of creation is first an act of destruction." -Picasso
Would be nice if we come together, I would hate to have people doing redundant works when we could all work together and build the ultimate add-ons to compliment! 
-S
-S
"Every act of creation is first an act of destruction." -Picasso
Most definitely 23fx23!
Currently you can specify a chord per note for each of the 12 notes... that translates up and down the entire keyboard, (ex. Set Cadd9 to C note, all C notes will be add9).
I am looking for alternate methods like inversion modifier keys.
CodeFN42 Chordit is a relatively similar method of what I want to add as well.
So say you are hitting a C and you want to play 5 different inversions of a Cminor chord you can use the corresponding modifier to play the inversions as well which adds a lot of dynamics.
Anyone have any good method of preventing stuck notes? I was thinking about building a buffer that records and will send note off after a specific time if not seen, anyone else have any good methods?
-S
Currently you can specify a chord per note for each of the 12 notes... that translates up and down the entire keyboard, (ex. Set Cadd9 to C note, all C notes will be add9).
I am looking for alternate methods like inversion modifier keys.
CodeFN42 Chordit is a relatively similar method of what I want to add as well.
So say you are hitting a C and you want to play 5 different inversions of a Cminor chord you can use the corresponding modifier to play the inversions as well which adds a lot of dynamics.
Anyone have any good method of preventing stuck notes? I was thinking about building a buffer that records and will send note off after a specific time if not seen, anyone else have any good methods?
-S
"Every act of creation is first an act of destruction." -Picasso
Regarding stuck notes, does your patch send note offs on its own? Ie,are the stuck notes always happening? Or is it only sometimes? It seems like you could just propagate the note off of the 'controlling' note to all the notes of the chord?
Regarding worrying about compatability, frankly I am a bit worried. But more so is the uncertainty of what is changing, what the new stuff will be, where my ideas will fit into the new Hh, etc. For instance I have an idea for a launchpad kind of interface using elastique player. But who knows? Maybe senso already added one.
I know the team is very small, and making promises is dangerous (no rewire, after all the mentions, for instance). I just feel like I've been waiting a year for the major update. In the meanwhile I've bitten the bullet on other DAWs which are simply faster to work in. I miss Hh features all the time. But I can just start cooking without dreaming up new patches or wondering if this or that is "just around the corner".
Regarding worrying about compatability, frankly I am a bit worried. But more so is the uncertainty of what is changing, what the new stuff will be, where my ideas will fit into the new Hh, etc. For instance I have an idea for a launchpad kind of interface using elastique player. But who knows? Maybe senso already added one.
I know the team is very small, and making promises is dangerous (no rewire, after all the mentions, for instance). I just feel like I've been waiting a year for the major update. In the meanwhile I've bitten the bullet on other DAWs which are simply faster to work in. I miss Hh features all the time. But I can just start cooking without dreaming up new patches or wondering if this or that is "just around the corner".
Sephult -
Are you running the latest version? There was a serious bug causing stuck notes addressed in .009
Before .009 came out, I avoided stuck notes by eliminating all "Midi in" and "send to usine", replacing them with using the a midi bus instead.
Shawn
Are you running the latest version? There was a serious bug causing stuck notes addressed in .009
Before .009 came out, I avoided stuck notes by eliminating all "Midi in" and "send to usine", replacing them with using the a midi bus instead.
Shawn
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Yeah I am using the latest version.
shawnb, what type of midi messages you have problems with? I had the every-once-in-awhile stuck notes but not a whole lot before .009.
Has me curious
It happens only once in awhile too, pretty infrequent but I want to put some handling in.
I have not troubleshot this yet, but will take a monitor to it the further I get, from my ears it sounds like only a single note of a chord etc that I can tell. I am thinking about creating a secondary script that's sole purpose is for matching note-off to note-on with some sort of gating feature I believe. This way if a note doesn't see a note-off past a threshold time it will send one out just for the note.
-S
shawnb, what type of midi messages you have problems with? I had the every-once-in-awhile stuck notes but not a whole lot before .009.
Has me curious
It happens only once in awhile too, pretty infrequent but I want to put some handling in.
I have not troubleshot this yet, but will take a monitor to it the further I get, from my ears it sounds like only a single note of a chord etc that I can tell. I am thinking about creating a secondary script that's sole purpose is for matching note-off to note-on with some sort of gating feature I believe. This way if a note doesn't see a note-off past a threshold time it will send one out just for the note.
-S
"Every act of creation is first an act of destruction." -Picasso
Sephult -
Mostly note, clock & wheel messages - high volume. I went into detail in this thread:
http://www.sensomusic.com/forums/viewto ... 188#p30188
This was fixed in .009.
I still use the MIDI bus method, however, because it allows me to discretely route MIDI device input. "Send to Usine"/"Midi Input" loses port (device) references. Replacing them with "SendMidiBus"/"GetMidiBus" resolves that issue; however, you may lose some HH functionality (I think you lose MIDI Learn & clock sync).
Now, where I want HH MIDI value-add (such as Learn, sync) I use "Send to Usine".
I also route all MIDI to discrete ports using "SendMidiBus"/"GetMidiBus", creating a unique bus per input device.
In one instance, I have it sent to both (SendMidiBus and SendToUsine), & have had no issues.
(Just in case you/others aren't aware, if you click on your devices either in the Devices pane or in your rack, a little patchlet opens up that routes your device data. This is where I make these changes.)
Shawn
Mostly note, clock & wheel messages - high volume. I went into detail in this thread:
http://www.sensomusic.com/forums/viewto ... 188#p30188
This was fixed in .009.
I still use the MIDI bus method, however, because it allows me to discretely route MIDI device input. "Send to Usine"/"Midi Input" loses port (device) references. Replacing them with "SendMidiBus"/"GetMidiBus" resolves that issue; however, you may lose some HH functionality (I think you lose MIDI Learn & clock sync).
Now, where I want HH MIDI value-add (such as Learn, sync) I use "Send to Usine".
I also route all MIDI to discrete ports using "SendMidiBus"/"GetMidiBus", creating a unique bus per input device.
In one instance, I have it sent to both (SendMidiBus and SendToUsine), & have had no issues.
(Just in case you/others aren't aware, if you click on your devices either in the Devices pane or in your rack, a little patchlet opens up that routes your device data. This is where I make these changes.)
Shawn
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Actually yes, I think I remember that post...at one time I did have some flooding issues as well and think I jumped in the discussion.
"Every act of creation is first an act of destruction." -Picasso
I should add ----
I've run into stuck/dropped notes in many other circumstances, outside of HH. It is usually a matter of a MIDI buffer being overrun. Before a code fix, I would review all driver settings for your devices & buffer settings for any software you are using (VSTs/DAWs). I would also consider experimenting with HH's performance settings (threads & buffer size).
Shawn
I've run into stuck/dropped notes in many other circumstances, outside of HH. It is usually a matter of a MIDI buffer being overrun. Before a code fix, I would review all driver settings for your devices & buffer settings for any software you are using (VSTs/DAWs). I would also consider experimenting with HH's performance settings (threads & buffer size).
Shawn
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Who is online
Users browsing this forum: No registered users and 127 guests