KSS player with per-channel spectrum analyser online

페이지 2/3
1 | | 3

By niek

Expert (109)

niek의 아바타

29-03-2021, 19:49

Btw, this is here now.

By ren

Paragon (1883)

ren의 아바타

29-03-2021, 22:38

More broken than working?

By ren

Paragon (1883)

ren의 아바타

31-03-2021, 10:52

I def. like the per-channel stuff, and the note display btw (could e.g. be logged to MIDI as well that way Smile)

You hacked that into the C sources yourself right?

If my C skills weren't seriously lacking I would e.g. have a PSG<>SCC vol. balance slider on my player already, instead of the 3 webNEZ PSG options. One day perhaps.. Wink

I'm (still) dissatisfied with libkss's PSG. NEZplug sound much better in that regard IMO (though not sure how realistic it is; there's a pretty big difference between the 2 MSX PSG types there).

By niek

Expert (109)

niek의 아바타

31-03-2021, 15:53

Hmm, yes it's amazingly bad all of a sudden, last time I tested it worked fine. :O Might have something to do with the browser version...?

The per channel export stuff is in libkss, okaxaki implemented it when I requested it. Smile I managed to get it working partly myself as well before that I remember, but that was a huge hack. My C skills are lacking as well. Wink

The notes are calculated with the pitch in Javascript, search for pitch in the msxplay-bundle.js. I remember I didn't like it yet, when having vibrato it'll change all the time, I guess that can be improved with some tricks.

By niek

Expert (109)

niek의 아바타

31-03-2021, 16:05

Edge seems to work a bit better then Chrome, at least playback starts all the time...

This is my 100th message on msx.org. Running Naked in a Field of Flowers

By aoineko

Master (167)

aoineko의 아바타

31-03-2021, 22:53

niek wrote:

Edge seems to work a bit better then Chrome, at least playback starts all the time...

Edge is not know to respect the W3C standards and norms.
It is therefore preferable to refer to Chrome and Firefox to determine the functioning of a site.

By gdx

Enlighted (4808)

gdx의 아바타

01-04-2021, 01:50

Chrome doesn't manage memory properly. Especially on Mac.

By niek

Expert (109)

niek의 아바타

01-04-2021, 19:47

Well, Edge is based on the Blink engine these days, which has been created for Chrome, so that's the same. And I agree about the memory management thing, but I guess it's my own fault in this case, the site is just an experiment. I noticed it's also very bad on Edge. However I got it stable when reopening the site a few times, no idea why... some timing issue I guess.

@Ren, some info about the per channel export here.

By niek

Expert (109)

niek의 아바타

01-04-2021, 19:54

Have you seen this other experiment btw? Would be nice if this had a spectrum analyser...

Just include the one line of Javascript and all zip files with vgm files in there will be detected, downloaded, extracted in memory and offered in a overlay player.

By ren

Paragon (1883)

ren의 아바타

02-04-2021, 10:59

Ha, yes, thx, I remember those GitHub issues/requests Smile

I'll def. look into that some time. Next to visualization, note recognition, I think it's pretty nice to be able to change volume levels per channel, and e.g. being able to save that to a preset.

Yes, I'm, aware of vgmplay-js as well Smile
I also read (parts of) that forum thread @ vgmrips.net where vampirefrog mentioned they will be using libvgm as JS replayer. Since libvgm is pretty much finished now, and already powering the latest vgmplay, I figure they'll come up with their Emscripten version soonish?

Anyway, you did your vgmplay-js yourself from the (now) legacy source code right, I figure shouldn't be too hard to figure out how to build it myself, but really would need to find some time to sit down with that. (My player *does* still need a core to support .vgm Smile)

mmontag/chip-player-js seems interesting as well (to learn from perhaps as well).

페이지 2/3
1 | | 3