Even a genius needs help once in a while, "but they seldom get any"

[Jonas Thörnvall]

I am pretty clueless how about how ***they*** program midi those programmers, but i built a track sequenser and now i realise that the thingys stored at the tracks need to be sorted on time basis. So it seem that track is mostly an editing feature?

Thingys are read using timebasis. Since track zero not used i was thinking downmixing the channels to it.

Can some of the more anal geniuses show me howto todo it in an elegant way. Or are you to buissy pondering over linguistic and semantic excersizes?

I suspect i have to do it ***yet again*** myself.
Well evidently track isn't of any use in the downmix.
I have started to ponder if track really necessary, but it seem like a good idea to have when building an event editor. Also this allow instrument changes on same channel and even changing outmodule even when in track.

That the midi API have omni listening on midiports is clear, i do not know if it can have multiple outports open.

track[m] ={
outport:[],
portname : [],
midichannel:[],
program:[],
time:[],
data0:[],
data1:[],
data2:[]
};

[Jonas Thörnvall]

It is an event sort, that needs to be done.

[Christoph M. Becker]

On 09.01.2018 at 15:48, Jonas Thörnvall wrote:

> Can some of the more anal geniuses show me howto todo it in an elegant way.

That is not supposed to work. Get well soon! :)

*plonk*

--
Christoph M. Becker

[Jonas Thörnvall]

I cure myself with a colorful interface and by taking pity on the poor semantic fanatcis.

https://www.facebook.com/photo.php?fbid=1512548872148264&set=a.288020821267748.63002.100001794973974&type=3&theater

[Jonas Thörnvall]

Well i cheat a bit doing interface first, you can't set how many bars to record yet although the metronome to calculate it is there "although" not playing yet, but you can record and set program channel and outputports on a track.

It get a little weird try to play the tracks though first it play track one and then rest of the events stacks in a single stroke, because they are before the event already played.

So i have to downmix, "sort it out so to say"

[Jonas Thörnvall]

Den tisdag 9 januari 2018 kl. 16:04:13 UTC+1 skrev Christoph M. Becker:

Flattering doesn't work i thought you guys took honor in being precise and on the mark?
Maybe i was a bit sloppy i meant anal retentive that is a good quality to have as a programmer "if it comes with some intellect" LoL

[Chris M. Thomasson]

https://youtu.be/kEBW8A3bw-Q

;^)

[Jonas Thörnvall]

Well maybe a good idea but i fear a modplayer is a much more complex ***thingy*** then something that deals with pure midisignals. You need a sound generator and god knows what to quirk out sounds, because it ain't just pure samples and midi in mods? They bend and pitch samples, then it would be better to go for a real sampler. I once invented ***the*** algorithm for none shortened/elongated piched sampleplayback i ***stretched*** the samples.

Well i just interpolated the bits in between in an rather ugly manner.
Kind of a bitwig you know.

[Jonas Thörnvall]

It was almost 20 years ago, and my memory is a bit rusty but basicly i used nykvist theorem to resample into the different keys i think it was the standard procedure and then i took the new pitched sample compared it with the ground keylength and got a ratio lets say 3,4 times shorter then i copied each bit using some statistic overlay 3,4 and pushed between.

And the strange thing? It worked, try it yourself. Well a single note, i don't remember which was the base note used by early sampler and pcm sounds. Do not sound perfect, but if you record/sample a tone in each octave it sounds good, those days 32MB ram, so the bitwig of samples became a memory issue. But i think they solved it by reading the sampled notes directly from disc realtime but it must caused a small latency?

Today i think you could do the resampling of a single sample into all notes and hold them within memory, even using javascript "because of the ton of memory" in modern computers. It will take a couple of seconds max to do the realtime key resampling?

Well i think Javascript is amazing in many ways, but you have started to lock up things into blip blop semantics, that is basicly unreadable without a manual.

I still trying to findout how the fuck to get the ports "promise" to load before the interface. If you would not be so fucking anal about the semantics it would be a no brainer. Now i have to reload the thing to get an error free load of the midi ports. I mean how can one put complexity in syntax of such a thing as the thing to wait for another task first to be done, before you start next?

Yeah i get that i must wait for the fucking ports to be ready before the interface can try load the values from them. But i don't get how fucking waiting for an answer of a task can be so fucking complex that i am clueless about how to check if the ports loaded, before i try to call the values within them.

How is it possible to fuck up things so bad?

[Jonas Thörnvall]

Apparently javascript have gone from having a rather straightforward syntax, into the world of mystery. I thought javascript and script languages was created to get away from awkvard convoluted syntax.

And now the "idiot industry" slowly take over the project, and move it into the land of obscurity, it is rather sad that it moved towards that one have memorise stringed together piece of semantic nonsense bullshit, to be usable.
I think there must be more people then i that have noticed it.

https://stackoverflow.com/questions/27759593/how-do-i-wait-for-a-promise-to-finish-before-returning-the-variable-of-a-functio

[Jonas Thörnvall]

https://daveceddia.com/waiting-for-promises-in-a-loop/

[Jonas Thörnvall]

https://github.com/petkaantonov/bluebird/issues/31

[Jonas Thörnvall]

How can i make sure that main() is executed after success?
I just can't figure that out.

if (navigator.requestMIDIAccess) {
navigator.requestMIDIAccess()
.then(success, failure);
}

function failure () {
console.error('No access to your midi devices.'+ + msg )
}

function success (midi) {
mid=midi;
inputs = midi.inputs.values();
outputs = midi.outputs.values();
// inputs outputs are Iterators
for (output = outputs.next(); output && !output.done; output = outputs.next()) {
var deviceOut = output.value.name;
console.log(deviceOut);
var optout = document.createElement("option");
optout.text = deviceOut;
document.getElementById("out_portsel").add(optout);
}

for (input = inputs.next(); input && !input.done; input = inputs.next()) {
var deviceIn = input.value.name;
var optin = document.createElement("option");
optin.text = deviceIn;
document.getElementById("in_portsel").add(optin);
// each time there is a midi message call the onMIDIMessage function
input.value.onmidimessage = onMIDIMessage;
}
}

function main(){
Rstarttime=performance.now();
document.getElementById("out_portsel").selectedIndex = outportindex;
makeTrack();
setTrack();
listTrackData();
changeProgram();
}

[Y A]

Seems like JSON. That should not be hard to solve.