ChanServ changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, and CD theory of operation are also on-topic. Channel logs: https://freenode.irclog.whitequark.org/~h~yamahasynths
Stilett0 has quit [Quit: leaving]
Stilett0 has joined ##yamahasynths
l_oliveira has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
_whitelogger has joined ##yamahasynths
_whitelogger has joined ##yamahasynths
_whitelogger has joined ##yamahasynths
_whitelogger has joined ##yamahasynths
_whitelogger has joined ##yamahasynths
nukeykt has joined ##yamahasynths
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
_whitelogger has joined ##yamahasynths
futarisIRCcloud has joined ##yamahasynths
cr1901_modern1 has joined ##yamahasynths
cr1901_modern has quit [Ping timeout: 255 seconds]
l_oliveira has joined ##yamahasynths
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<Sarayan>
SWP = Standard Wave Processor
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
andlabs has joined ##yamahasynths
cr1901_modern1 has quit [Quit: Leaving.]
cr1901_modern has joined ##yamahasynths
<Lord_Nightmare>
upd7759 is an adpcm playback chip, but its a bit interesting internally as it has its own microsequencer thing on die, which isn't dumped yet. its been decapped, but the ROM is probably implant
<Lord_Nightmare>
this microsequencer is probably what explains the somewhat inconsistent 'request for new data' behavior when the chip runs in slave mode
<Lord_Nightmare>
maybe having to do with the exact number of bytes needed to keep some sort of fifo(?) full? I don't know for sure, charles macdonadl did some tests on it
<Lord_Nightmare>
*macdonald
nukeykt has quit [Quit: Page closed]
<Sarayan>
Hi whitequark, managed to sync groupxiv with latest leaflet?
<whitequark>
Sarayan: not yet but i have an opening so i think i'll look into it now
<Sarayan>
wq: way cool
<whitequark>
Sarayan: updated
<Sarayan>
yay, so that means I can replace leaflet with groupxiv?
<whitequark>
i think so
<whitequark>
btw i also added a feature that allows you to zoom further than 1:1
<Sarayan>
ok, trying to understand how to use it :-)
<whitequark>
Sarayan: the idea is you put a small json file next to your tiles
<Lord_Nightmare>
if that's the issue can't you apply a configurable integer offset for the x and y image indices?
<whitequark>
Lord_Nightmare: no, has nothing to do with tile files
<Lord_Nightmare>
and treat x and y image indices (this is for the source images) as always signed
<Lord_Nightmare>
ah ok
<Lord_Nightmare>
i was wrong in my guess
<whitequark>
Sarayan: ok, yeah, it's setMapBounds
<whitequark>
i can just disable that
<whitequark>
Sarayan: to help me debug these issues, can you add a header to og.kervella.org?
<whitequark>
Access-Control-Allow-Origin: *
<whitequark>
this will let me point my local instance of groupxiv to your tiles
<Lord_Nightmare>
whitequark: can you make it an option in the json to disable the 'lock viewport to upper left corner of image' thing?
<Lord_Nightmare>
if only dig needs it, then it can be disabled elsewhere
<Sarayan>
wq: should be there now
<whitequark>
Sarayan: pull
<Sarayan>
ok
<Sarayan>
better than raw leaflet: the tile zoom level is better chosen
<Sarayan>
worse: it has both layers active initially, that's slower to load
<Sarayan>
worse: the margin is big
<whitequark>
Sarayan: fixed both layers issue
<Sarayan>
equivalent: it doesn't "scale the zoom" between the layers
<Sarayan>
that one is an annoying problem, since the die shot and the schematic are aligned
<whitequark>
Sarayan: "scale the zoom">
<whitequark>
?
<Sarayan>
if you switch between the two layers, you see they're not at the same size
<Sarayan>
because the original images are not the same size either
<Sarayan>
(schematic is 5x larger, and 5 is not a power of two)
<Sarayan>
but they're designed to be aligned
<whitequark>
hmm
<Sarayan>
interesting, under chromium zoom 2 is exactly the window size
<whitequark>
not on my machine
<Sarayan>
that's thw web for you
<Sarayan>
not a real problem though
<Wohali>
cr1901_modern: fyi i'd like to do the social media thing on May 1 to announce the rest of these boards. Right now it's looking like I'll have 50 unclaimed PCBs :( Unless people really rush to pay for their preorders Mon or Tues. Can you help?
<whitequark>
Sarayan: yeah the alignment is a serious problem
<whitequark>
actually i have an idea...
<whitequark>
Sarayan: set tileSize for the die shot to 768
<whitequark>
of course, this way only the schematic will be pixel perfect
<whitequark>
but since there is a factor of 1.5 you cannot make both pixel perfect anyway
<whitequark>
it is possible to make leaflet load more images and then downscale, but it is slow enough as it is
<Sarayan>
you mean the downscale it not done by the browser?
<whitequark>
Sarayan: there are 2 options
<whitequark>
either make it load the tile of die at smaller zoom level and stretch it
<whitequark>
or, make it load 4 times the tile of die at higher zoom level and shrink it
<whitequark>
the 1st option is faster
<Sarayan>
I mean, as soon as the zoom level is dependant on the window size, you can't be pixel perfect can you?