Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #37707 > unrolled thread

Looking for a MIDI file parser acknowledging how broken javascript become.

Back to article view | Back to comp.lang.javascript

Contents

  Looking for a MIDI file parser acknowledging how broken javascript become. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-11-07 22:18 -0800
    Re: Looking for a MIDI file parser acknowledging how broken javascript become. "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2019-11-08 04:11 -0800
    Re: Looking for a MIDI file parser acknowledging how broken javascript become. Arno Welzel <usenet@arnowelzel.de> - 2019-11-12 12:08 +0100
      Re: Looking for a MIDI file parser acknowledging how broken javascript become. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-11-12 10:21 -0800
      Re: Looking for a MIDI file parser acknowledging how broken javascript become. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-11-12 21:48 -0800
        Re: Looking for a MIDI file parser acknowledging how broken javascript become. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-11-13 03:55 -0800
          Re: Looking for a MIDI file parser acknowledging how broken javascript become. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-11-13 03:56 -0800
        Re: Looking for a MIDI file parser acknowledging how broken javascript become. Arno Welzel <usenet@arnowelzel.de> - 2019-11-14 08:19 +0100
          Re: Looking for a MIDI file parser acknowledging how broken javascript become. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-11-14 01:35 -0800
      Re: Looking for a MIDI file parser acknowledging how broken javascript become. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-11-12 23:56 -0800
        Re: Looking for a MIDI file parser acknowledging how broken javascript become. Jonas Thörnvall <jonas.thornvall@gmail.com> - 2019-11-13 00:00 -0800

#37707 — Looking for a MIDI file parser acknowledging how broken javascript become.

It is a sad story of human stupidity.
Basicly a midifile is messages there is timed messages and data messages.
The idiots building their parsers using fig lingo. It is fucking tedious implementing parsers, but when the endresult coming out of parser is harder to use then make a parser of ones own, one wonder a bit of the state of matter.

How fucking hard can it be to store the messages as strings in an array?
The hard part is reading out the fucking files.

Not fucking get them into an array of messages.
Each message is simple to parse, no but the fucking monkeys must create objects for this and that, so now i have to make a parser that not made for monkeys playing with figo lingo....

[toc] | [next] | [standalone]

#37720

On Friday, November 8, 2019 at 12:19:02 AM UTC-6, Jonas Thörnvall wrote:
> It is a sad story of human stupidity.
> Basicly a midifile is messages there is timed messages and data messages.
> The idiots building their parsers using fig lingo. It is fucking tedious implementing parsers, but when the endresult coming out of parser is harder to use then make a parser of ones own, one wonder a bit of the state of matter.
> 
> How fucking hard can it be to store the messages as strings in an array?
> The hard part is reading out the fucking files.
> 
> Not fucking get them into an array of messages.
> Each message is simple to parse, no but the fucking monkeys must create objects for this and that, so now i have to make a parser that not made for monkeys playing with figo lingo....

Can you state this in the form of a question?

[toc] | [prev] | [next] | [standalone]

#37755

On 08.11.19 07:18, Jonas Thörnvall wrote:

> It is a sad story of human stupidity. Basicly a midifile is messages
> there is timed messages and data messages. The idiots building their
> parsers using fig lingo. It is fucking tedious implementing parsers,
> but when the endresult coming out of parser is harder to use then
> make a parser of ones own, one wonder a bit of the state of matter.
> 
> How fucking hard can it be to store the messages as strings in an
> array? The hard part is reading out the fucking files.

Keep in mind that MIDI was introduced more than 35 years ago in August
1982. At that time computers (including those in synthesizers) where not
that powerful and did not have a lot of memory - we talk about
kilobytes, not megabytes.

Also see:

<https://www.csie.ntu.edu.tw/~r92092/ref/midi/>
<http://www.somascape.org/midi/tech/mfile.html>

> Not fucking get them into an array of messages. Each message is
> simple to parse, no but the fucking monkeys must create objects for
> this and that, so now i have to make a parser that not made for
> monkeys playing with figo lingo....
What "objects" are you talking about? Is your rant about
<https://www.npmjs.com/package/midi-parser-js>?

Then go ahead and write your own parser.


-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#37772

Den tisdag 12 november 2019 kl. 12:08:47 UTC+1 skrev Arno Welzel:
> On 08.11.19 07:18, Jonas Thörnvall wrote:
> 
> > It is a sad story of human stupidity. Basicly a midifile is messages
> > there is timed messages and data messages. The idiots building their
> > parsers using fig lingo. It is fucking tedious implementing parsers,
> > but when the endresult coming out of parser is harder to use then
> > make a parser of ones own, one wonder a bit of the state of matter.
> > 
> > How fucking hard can it be to store the messages as strings in an
> > array? The hard part is reading out the fucking files.
> 
> Keep in mind that MIDI was introduced more than 35 years ago in August
> 1982. At that time computers (including those in synthesizers) where not
> that powerful and did not have a lot of memory - we talk about
> kilobytes, not megabytes.


Well i am fully aware how awkward it is to read out a midifile, i was hoping to avoid write the script myself. I may have done midi parsing once or twice but the last time was certainly more then 20 years ago.

I simply was hoping to find code i could read and understand, but i simply can't.

> Also see:
> 
> <https://www.csie.ntu.edu.tw/~r92092/ref/midi/>
> <http://www.somascape.org/midi/tech/mfile.html>
> 
> > Not fucking get them into an array of messages. Each message is
> > simple to parse, no but the fucking monkeys must create objects for
> > this and that, so now i have to make a parser that not made for
> > monkeys playing with figo lingo....
> What "objects" are you talking about? Is your rant about
> <https://www.npmjs.com/package/midi-parser-js>?
> 
> Then go ahead and write your own parser.

Most probably will do that, i don't feel keen on it.

> 
> 
> -- 
> Arno Welzel
> https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#37892

Den tisdag 12 november 2019 kl. 12:08:47 UTC+1 skrev Arno Welzel:
> On 08.11.19 07:18, Jonas Thörnvall wrote:
> 
> > It is a sad story of human stupidity. Basicly a midifile is messages
> > there is timed messages and data messages. The idiots building their
> > parsers using fig lingo. It is fucking tedious implementing parsers,
> > but when the endresult coming out of parser is harder to use then
> > make a parser of ones own, one wonder a bit of the state of matter.
> > 
> > How fucking hard can it be to store the messages as strings in an
> > array? The hard part is reading out the fucking files.
> 
> Keep in mind that MIDI was introduced more than 35 years ago in August
> 1982. At that time computers (including those in synthesizers) where not
> that powerful and did not have a lot of memory - we talk about
> kilobytes, not megabytes.
> 
> Also see:
> 
> <https://www.csie.ntu.edu.tw/~r92092/ref/midi/>
> <http://www.somascape.org/midi/tech/mfile.html>
> 
> > Not fucking get them into an array of messages. Each message is
> > simple to parse, no but the fucking monkeys must create objects for
> > this and that, so now i have to make a parser that not made for
> > monkeys playing with figo lingo....
> What "objects" are you talking about? Is your rant about
> <https://www.npmjs.com/package/midi-parser-js>?
> 
> Then go ahead and write your own parser.
> 
> 
> -- 
> Arno Welzel
> https://arnowelzel.de

Can i ask you Arno is there a simple way to get the objects, stringify them over into an array, or will that require as much work as actaully writing a parser? 

I have find two object oriented midiparsers, but i am simply not the man to read over the even information into an array. I think the actual conversion of delta-time to the absolute time my script use will be no problem, i will figure out in an hour or to.

But how many rows of code will be needed to stringify the event objects, is it two lines, 10, 100 or 1000? I can't even estimate how hard it will be?

I am not sure what is meant by using json in your project, is it just an include src or do it need installation? I want my project simple client side script, so nothing beyond a simple include src should be needed.

It seem most of the parser i found need json, all so what do i need to do?

https://www.npmjs.com/package/midi-parser-js
https://github.com/Tonejs/Midi
https://github.com/nfroidure/midifile
https://github.com/colxi/midi-parser-js
https://github.com/chrisguttandin/midi-json-parser

The tone.js one i at least can see and understand what it do output someone was smart enough making an example below and it seem to run out of box when downloaded just the index, but what is the format objects or is it just formatted text? 

Well I probably could use that text mass and parse it to suit my needs.
I downloaded the indexfile, and it seem to run so i guess i only need to include same src's into my script. When i include this code should comment the use in my include src file or is it ok to just include the src tag?

I guess the disadvantage is if he should remove the code from server, so i guess most people download the necessary files and make a relative path, but then the server somehow must run Json or?

https://tonejs.github.io/Midi/

 

[toc] | [prev] | [next] | [standalone]

#37895

Den onsdag 13 november 2019 kl. 06:48:16 UTC+1 skrev Jonas Thörnvall:
> Den tisdag 12 november 2019 kl. 12:08:47 UTC+1 skrev Arno Welzel:
> > On 08.11.19 07:18, Jonas Thörnvall wrote:
> > 
> > > It is a sad story of human stupidity. Basicly a midifile is messages
> > > there is timed messages and data messages. The idiots building their
> > > parsers using fig lingo. It is fucking tedious implementing parsers,
> > > but when the endresult coming out of parser is harder to use then
> > > make a parser of ones own, one wonder a bit of the state of matter.
> > > 
> > > How fucking hard can it be to store the messages as strings in an
> > > array? The hard part is reading out the fucking files.
> > 
> > Keep in mind that MIDI was introduced more than 35 years ago in August
> > 1982. At that time computers (including those in synthesizers) where not
> > that powerful and did not have a lot of memory - we talk about
> > kilobytes, not megabytes.
> > 
> > Also see:
> > 
> > <https://www.csie.ntu.edu.tw/~r92092/ref/midi/>
> > <http://www.somascape.org/midi/tech/mfile.html>
> > 
> > > Not fucking get them into an array of messages. Each message is
> > > simple to parse, no but the fucking monkeys must create objects for
> > > this and that, so now i have to make a parser that not made for
> > > monkeys playing with figo lingo....
> > What "objects" are you talking about? Is your rant about
> > <https://www.npmjs.com/package/midi-parser-js>?
> > 
> > Then go ahead and write your own parser.
> > 
> > 
> > -- 
> > Arno Welzel
> > https://arnowelzel.de
> 
> Can i ask you Arno is there a simple way to get the objects, stringify them over into an array, or will that require as much work as actaully writing a parser? 
> 
> I have find two object oriented midiparsers, but i am simply not the man to read over the even information into an array. I think the actual conversion of delta-time to the absolute time my script use will be no problem, i will figure out in an hour or to.
> 
> But how many rows of code will be needed to stringify the event objects, is it two lines, 10, 100 or 1000? I can't even estimate how hard it will be?
> 
> I am not sure what is meant by using json in your project, is it just an include src or do it need installation? I want my project simple client side script, so nothing beyond a simple include src should be needed.
> 
> It seem most of the parser i found need json, all so what do i need to do?
> 
> https://www.npmjs.com/package/midi-parser-js
> https://github.com/Tonejs/Midi
> https://github.com/nfroidure/midifile
> https://github.com/colxi/midi-parser-js
> https://github.com/chrisguttandin/midi-json-parser
> 
> The tone.js one i at least can see and understand what it do output someone was smart enough making an example below and it seem to run out of box when downloaded just the index, but what is the format objects or is it just formatted text? 
> 
> Well I probably could use that text mass and parse it to suit my needs.
> I downloaded the indexfile, and it seem to run so i guess i only need to include same src's into my script. When i include this code should comment the use in my include src file or is it ok to just include the src tag?
> 
> I guess the disadvantage is if he should remove the code from server, so i guess most people download the necessary files and make a relative path, but then the server somehow must run Json or?
> 
> https://tonejs.github.io/Midi/

Could it be that he do not use midichannels and instead just change patch?

[toc] | [prev] | [next] | [standalone]

#37896

Den onsdag 13 november 2019 kl. 12:55:30 UTC+1 skrev Jonas Thörnvall:
> Den onsdag 13 november 2019 kl. 06:48:16 UTC+1 skrev Jonas Thörnvall:
> > Den tisdag 12 november 2019 kl. 12:08:47 UTC+1 skrev Arno Welzel:
> > > On 08.11.19 07:18, Jonas Thörnvall wrote:
> > > 
> > > > It is a sad story of human stupidity. Basicly a midifile is messages
> > > > there is timed messages and data messages. The idiots building their
> > > > parsers using fig lingo. It is fucking tedious implementing parsers,
> > > > but when the endresult coming out of parser is harder to use then
> > > > make a parser of ones own, one wonder a bit of the state of matter.
> > > > 
> > > > How fucking hard can it be to store the messages as strings in an
> > > > array? The hard part is reading out the fucking files.
> > > 
> > > Keep in mind that MIDI was introduced more than 35 years ago in August
> > > 1982. At that time computers (including those in synthesizers) where not
> > > that powerful and did not have a lot of memory - we talk about
> > > kilobytes, not megabytes.
> > > 
> > > Also see:
> > > 
> > > <https://www.csie.ntu.edu.tw/~r92092/ref/midi/>
> > > <http://www.somascape.org/midi/tech/mfile.html>
> > > 
> > > > Not fucking get them into an array of messages. Each message is
> > > > simple to parse, no but the fucking monkeys must create objects for
> > > > this and that, so now i have to make a parser that not made for
> > > > monkeys playing with figo lingo....
> > > What "objects" are you talking about? Is your rant about
> > > <https://www.npmjs.com/package/midi-parser-js>?
> > > 
> > > Then go ahead and write your own parser.
> > > 
> > > 
> > > -- 
> > > Arno Welzel
> > > https://arnowelzel.de
> > 
> > Can i ask you Arno is there a simple way to get the objects, stringify them over into an array, or will that require as much work as actaully writing a parser? 
> > 
> > I have find two object oriented midiparsers, but i am simply not the man to read over the even information into an array. I think the actual conversion of delta-time to the absolute time my script use will be no problem, i will figure out in an hour or to.
> > 
> > But how many rows of code will be needed to stringify the event objects, is it two lines, 10, 100 or 1000? I can't even estimate how hard it will be?
> > 
> > I am not sure what is meant by using json in your project, is it just an include src or do it need installation? I want my project simple client side script, so nothing beyond a simple include src should be needed.
> > 
> > It seem most of the parser i found need json, all so what do i need to do?
> > 
> > https://www.npmjs.com/package/midi-parser-js
> > https://github.com/Tonejs/Midi
> > https://github.com/nfroidure/midifile
> > https://github.com/colxi/midi-parser-js
> > https://github.com/chrisguttandin/midi-json-parser
> > 
> > The tone.js one i at least can see and understand what it do output someone was smart enough making an example below and it seem to run out of box when downloaded just the index, but what is the format objects or is it just formatted text? 
> > 
> > Well I probably could use that text mass and parse it to suit my needs.
> > I downloaded the indexfile, and it seem to run so i guess i only need to include same src's into my script. When i include this code should comment the use in my include src file or is it ok to just include the src tag?
> > 
> > I guess the disadvantage is if he should remove the code from server, so i guess most people download the necessary files and make a relative path, but then the server somehow must run Json or?
> > 
> > https://tonejs.github.io/Midi/
> 
> Could it be that he do not use midichannels and instead just change patch?

Then i canät use his parser quite sad it is the only one i understand.

[toc] | [prev] | [next] | [standalone]

#37904

Jonas Thörnvall:

> Den tisdag 12 november 2019 kl. 12:08:47 UTC+1 skrev Arno Welzel:
>> On 08.11.19 07:18, Jonas Thörnvall wrote:
>>
>>> It is a sad story of human stupidity. Basicly a midifile is messages
>>> there is timed messages and data messages. The idiots building their
>>> parsers using fig lingo. It is fucking tedious implementing parsers,
>>> but when the endresult coming out of parser is harder to use then
>>> make a parser of ones own, one wonder a bit of the state of matter.
>>>
>>> How fucking hard can it be to store the messages as strings in an
>>> array? The hard part is reading out the fucking files.
>>
>> Keep in mind that MIDI was introduced more than 35 years ago in August
>> 1982. At that time computers (including those in synthesizers) where not
>> that powerful and did not have a lot of memory - we talk about
>> kilobytes, not megabytes.
>>
>> Also see:
>>
>> <https://www.csie.ntu.edu.tw/~r92092/ref/midi/>
>> <http://www.somascape.org/midi/tech/mfile.html>
>>
>>> Not fucking get them into an array of messages. Each message is
>>> simple to parse, no but the fucking monkeys must create objects for
>>> this and that, so now i have to make a parser that not made for
>>> monkeys playing with figo lingo....
>> What "objects" are you talking about? Is your rant about
>> <https://www.npmjs.com/package/midi-parser-js>?
>>
>> Then go ahead and write your own parser.
>>
>>
>> -- 
>> Arno Welzel
>> https://arnowelzel.de
> 
> Can i ask you Arno is there a simple way to get the objects, stringify them over into an array, or will that require as much work as actaully writing a parser? 
> 
> I have find two object oriented midiparsers, but i am simply not the man to read over the even information into an array. I think the actual conversion of delta-time to the absolute time my script use will be no problem, i will figure out in an hour or to.
> 
> But how many rows of code will be needed to stringify the event objects, is it two lines, 10, 100 or 1000? I can't even estimate how hard it will be?
> 
> I am not sure what is meant by using json in your project, is it just an include src or do it need installation? I want my project simple client side script, so nothing beyond a simple include src should be needed.
> 
> It seem most of the parser i found need json, all so what do i need to do?
> 
> https://www.npmjs.com/package/midi-parser-js
> https://github.com/Tonejs/Midi
> https://github.com/nfroidure/midifile
> https://github.com/colxi/midi-parser-js
> https://github.com/chrisguttandin/midi-json-parser

They do not *need* JSON, these parsers *create* JSON, because JSON *is*
the format to store data for JavaScript.

JSON = JavaScript Object Notation

And don't get confused by "Object" - JSON just represent serialized data
which is called "objects" since the data can be accessed using property
names.

[...]
> I guess the disadvantage is if he should remove the code from server, so i guess most people download the necessary files and make a relative path, but then the server somehow must run Json or?
> 
> https://tonejs.github.io/Midi/

No, you just download the stuff, integrate it in your own code and
that's it. There is no need for a server.

Did you ever use a JavaScript library from others? It seems you don't
have any experience at all with this.

-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#37905

Den torsdag 14 november 2019 kl. 08:20:04 UTC+1 skrev Arno Welzel:
> Jonas Thörnvall:
> 
> > Den tisdag 12 november 2019 kl. 12:08:47 UTC+1 skrev Arno Welzel:
> >> On 08.11.19 07:18, Jonas Thörnvall wrote:
> >>
> >>> It is a sad story of human stupidity. Basicly a midifile is messages
> >>> there is timed messages and data messages. The idiots building their
> >>> parsers using fig lingo. It is fucking tedious implementing parsers,
> >>> but when the endresult coming out of parser is harder to use then
> >>> make a parser of ones own, one wonder a bit of the state of matter.
> >>>
> >>> How fucking hard can it be to store the messages as strings in an
> >>> array? The hard part is reading out the fucking files.
> >>
> >> Keep in mind that MIDI was introduced more than 35 years ago in August
> >> 1982. At that time computers (including those in synthesizers) where not
> >> that powerful and did not have a lot of memory - we talk about
> >> kilobytes, not megabytes.
> >>
> >> Also see:
> >>
> >> <https://www.csie.ntu.edu.tw/~r92092/ref/midi/>
> >> <http://www.somascape.org/midi/tech/mfile.html>
> >>
> >>> Not fucking get them into an array of messages. Each message is
> >>> simple to parse, no but the fucking monkeys must create objects for
> >>> this and that, so now i have to make a parser that not made for
> >>> monkeys playing with figo lingo....
> >> What "objects" are you talking about? Is your rant about
> >> <https://www.npmjs.com/package/midi-parser-js>?
> >>
> >> Then go ahead and write your own parser.
> >>
> >>
> >> -- 
> >> Arno Welzel
> >> https://arnowelzel.de
> > 
> > Can i ask you Arno is there a simple way to get the objects, stringify them over into an array, or will that require as much work as actaully writing a parser? 
> > 
> > I have find two object oriented midiparsers, but i am simply not the man to read over the even information into an array. I think the actual conversion of delta-time to the absolute time my script use will be no problem, i will figure out in an hour or to.
> > 
> > But how many rows of code will be needed to stringify the event objects, is it two lines, 10, 100 or 1000? I can't even estimate how hard it will be?
> > 
> > I am not sure what is meant by using json in your project, is it just an include src or do it need installation? I want my project simple client side script, so nothing beyond a simple include src should be needed.
> > 
> > It seem most of the parser i found need json, all so what do i need to do?
> > 
> > https://www.npmjs.com/package/midi-parser-js
> > https://github.com/Tonejs/Midi
> > https://github.com/nfroidure/midifile
> > https://github.com/colxi/midi-parser-js
> > https://github.com/chrisguttandin/midi-json-parser
> 
> They do not *need* JSON, these parsers *create* JSON, because JSON *is*
> the format to store data for JavaScript.
> 
> JSON = JavaScript Object Notation
> 
> And don't get confused by "Object" - JSON just represent serialized data
> which is called "objects" since the data can be accessed using property
> names.
> 
> [...]
> > I guess the disadvantage is if he should remove the code from server, so i guess most people download the necessary files and make a relative path, but then the server somehow must run Json or?
> > 
> > https://tonejs.github.io/Midi/
> 
> No, you just download the stuff, integrate it in your own code and
> that's it. There is no need for a server.
> 
> Did you ever use a JavaScript library from others? It seems you don't
> have any experience at all with this.
> 
> -- 
> Arno Welzel
> https://arnowelzel.de

No never.

[toc] | [prev] | [next] | [standalone]

#37893

Den tisdag 12 november 2019 kl. 12:08:47 UTC+1 skrev Arno Welzel:
> On 08.11.19 07:18, Jonas Thörnvall wrote:
> 
> > It is a sad story of human stupidity. Basicly a midifile is messages
> > there is timed messages and data messages. The idiots building their
> > parsers using fig lingo. It is fucking tedious implementing parsers,
> > but when the endresult coming out of parser is harder to use then
> > make a parser of ones own, one wonder a bit of the state of matter.
> > 
> > How fucking hard can it be to store the messages as strings in an
> > array? The hard part is reading out the fucking files.
> 
> Keep in mind that MIDI was introduced more than 35 years ago in August
> 1982. At that time computers (including those in synthesizers) where not
> that powerful and did not have a lot of memory - we talk about
> kilobytes, not megabytes.
> 
> Also see:
> 
> <https://www.csie.ntu.edu.tw/~r92092/ref/midi/>
> <http://www.somascape.org/midi/tech/mfile.html>
> 
> > Not fucking get them into an array of messages. Each message is
> > simple to parse, no but the fucking monkeys must create objects for
> > this and that, so now i have to make a parser that not made for
> > monkeys playing with figo lingo....
> What "objects" are you talking about? Is your rant about
> <https://www.npmjs.com/package/midi-parser-js>?
> 
> Then go ahead and write your own parser.
> 
> 
> -- 
> Arno Welzel
> https://arnowelzel.de

I need some help though i see when i look at it, the notes and instruments, where is the channel information?

Normally?? the instrument channel is the first byte in a message ranging 192-207. At least that is how i change the instrument on a midichannel on my hardware.

And the notemessage first byte, lets use both ON 144-159  and OFF 128-143 "they use duration here instead of "OFF" works fine with me".

But i can't see these messages for channel in the textoutput where do they hide?

https://tonejs.github.io/Midi/

[toc] | [prev] | [next] | [standalone]

#37894

Den onsdag 13 november 2019 kl. 08:56:34 UTC+1 skrev Jonas Thörnvall:
> Den tisdag 12 november 2019 kl. 12:08:47 UTC+1 skrev Arno Welzel:
> > On 08.11.19 07:18, Jonas Thörnvall wrote:
> > 
> > > It is a sad story of human stupidity. Basicly a midifile is messages
> > > there is timed messages and data messages. The idiots building their
> > > parsers using fig lingo. It is fucking tedious implementing parsers,
> > > but when the endresult coming out of parser is harder to use then
> > > make a parser of ones own, one wonder a bit of the state of matter.
> > > 
> > > How fucking hard can it be to store the messages as strings in an
> > > array? The hard part is reading out the fucking files.
> > 
> > Keep in mind that MIDI was introduced more than 35 years ago in August
> > 1982. At that time computers (including those in synthesizers) where not
> > that powerful and did not have a lot of memory - we talk about
> > kilobytes, not megabytes.
> > 
> > Also see:
> > 
> > <https://www.csie.ntu.edu.tw/~r92092/ref/midi/>
> > <http://www.somascape.org/midi/tech/mfile.html>
> > 
> > > Not fucking get them into an array of messages. Each message is
> > > simple to parse, no but the fucking monkeys must create objects for
> > > this and that, so now i have to make a parser that not made for
> > > monkeys playing with figo lingo....
> > What "objects" are you talking about? Is your rant about
> > <https://www.npmjs.com/package/midi-parser-js>?
> > 
> > Then go ahead and write your own parser.
> > 
> > 
> > -- 
> > Arno Welzel
> > https://arnowelzel.de
> 
> I need some help though i see when i look at it, the notes and instruments, where is the channel information?
> 
> Normally?? the instrument channel is the first byte in a message ranging 192-207. At least that is how i change the instrument on a midichannel on my hardware.
> 
> And the notemessage first byte, lets use both ON 144-159  and OFF 128-143 "they use duration here instead of "OFF" works fine with me".
> 
> But i can't see these messages for channel in the textoutput where do they hide?
> 
> https://tonejs.github.io/Midi/

Well maybe i got a file using only one channel nah that can't be i see drums as instrument.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web