lekernel changed the topic of #milkymist to: Milkymist One, Migen, Milkymist SoC & Flickernoise :: Logs: http://en.qi-hardware.com/mmlogs :: Something to do? https://github.com/milkymist/bugs/issues
antgreen has joined #milkymist
cladamw has joined #milkymist
Jia has joined #milkymist
bkero has joined #milkymist
xiangfu has joined #milkymist
<hypermodern> Wolfspraul have there ever been feedback loops between more than one milkymist1?
<wolfspraul> I don't think so
<hypermodern> where the synthesis is feed into the other via camera or through the internet?
<wolfspraul> well there are technical boundaries too
<wolfspraul> currently m1 cannot sample vga video-in
<wolfspraul> and it cannot stream video over ethernet either
<hypermodern> what if it came in through the camera?
<wolfspraul> sure, over the composite signal it could
<hypermodern> so that would be analog right?
<hypermodern> so repitition effects will show up?
<wolfspraul> analog, yes
<hypermodern> Awesome!
<hypermodern> I'm looking for Moiré patterns
<wolfspraul> not sure how good those 'repetition effects' will actually look like
<wolfspraul> sure - try!
<hypermodern> Well no-one has ever tried them
<hypermodern> :-D
<hypermodern> or video feedback with scan lines
<hypermodern> which would continually degrade to some state
<hypermodern> this could be really interesting
<hypermodern> I'm thinking about a show this summer with the qi speakers and laoban speakers
<hypermodern> and I think that a MM1 loop will be interesting of the theme of the show.... based on "Re-" meaning re use etc...
<hypermodern> or re-cycle etc.
<wolfspraul> good
<hypermodern> this moiré effect could be layered on top of the video synthesis either by refresh rates being subtly out of synk
<hypermodern> Potentially making the people who move through the room become part of the degradation of their own image
<hypermodern> plus we could use the dmx controllers to flash the room
<hypermodern> to "reset" if video output gets stuck into black
<hypermodern> Potentially stroboscopic light would influence the effect as well.
<wpwrak> hmm, i wonder what effect the fairly low resolution of the composite video input would have on this
<wpwrak> but it could go either way - good or bad :)
<wolfspraul> yes, agree
<hypermodern> I'm thinking good
<wolfspraul> but the ideas can and should be tried now
<hypermodern> just cause I like analog video degradation
<hypermodern> !
<hypermodern> OK, I'm drafting up a proposal, and I have the floor plans, and will make a mockup in the next few days, this is a very helpful conversation, Wolfspraul
<hypermodern> thank you.
<hypermodern> What is the refresh rate on MM1
<hypermodern> 60fps?
<wolfspraul> no no
<wolfspraul> I don't think so
<wolfspraul> maybe 24fps?
<hypermodern> OK.
<hypermodern> as long as it's over 12!
<wolfspraul> it is
<hypermodern> that's where images flow
<wolfspraul> though in 1024x768 it goes down to 4 or so :-)
<wolfspraul> I think
<wolfspraul> but since it operates at 640x480, you get your >12
<hypermodern> what's the default then to get 24?
<hypermodern> OK
<hypermodern> gotcha
<wolfspraul> it's just about performance here and there
<hypermodern> 240x480 gives 24 fps?
<wolfspraul> Sebastien works intensively on this stuff, we try to up the performance
<wolfspraul> 640x480
<wolfspraul> I *think* it was 24fps, but not 100% sure now
<hypermodern> OK no problem
<wolfspraul> the bottleneck is memory bandwidth
<wpwrak> i also think it's 24 ... checking ...
<sb0> 640x480 @24fps works, yes
<wolfspraul> at some point I think somewhat soon (?) we plan to switch to a new version of the SoC with faster memory
<wolfspraul> but let's say that will be another month or two out, I think
<hypermodern> Cool thank sb0
<hypermodern> and is there any limit on how long a jpeg image can be held i.e. is there any risk of "burn in" like a plasma tv?
<sb0> probably more, I'm back from the US only on May 13th, and the schedule is already quite packed
<sb0> I won't have time to write much code
<wolfspraul> sure, but it's moving, and in the meantime we try to improve the environment and platform elsewhere. one by one...
<sb0> then we need the old cores ported, at least the important ones
<sb0> and dataflow synthesis in migen to rewrite the hw acceleration properly
<wolfspraul> yep
<wolfspraul> as long as migen is not aborted, it doesn't really matter whether it takes another month or two somewhere, since we have so many other good short targets that can make a difference to users today
<wpwrak> hypermodern: depends entirely on your display technology. i can't imagine any way in which a static/repetitive image could upset the M1 itself
<hypermodern> OK.
<hypermodern> that's what I fugured
<hypermodern> I knew it can effect certain display types, but I figured not the chip itself
<hypermodern> thank you for the clarification
<hypermodern> Is there any vector support for .svg?
<hypermodern> or only png and .jpg?
<wolfspraul> on the m1? no svg
<wpwrak> only pixels, no direct support for vector. there's some vector drawing for the audio signal, but i doubt you could use that for much
<hypermodern> OK
<wpwrak> wolfspraul: we may need migen to verify the M1r4 boards, though
<hypermodern> would it be enough to just have a series of lines rendered via vector and a second set rendered over the top off by a few degrees?
<hypermodern> similar to the images of lines I sent you?
<wpwrak> hypermodern: i'm not sure you have enough control over lines to do such things. also, lines are drawn by software, so that's quite slow.
<hypermodern> Slow is fine
<hypermodern> slow may actually be better wpwrak.
<wpwrak> hmm :)
<hypermodern> trying to render something like this http://en.wikipedia.org/wiki/Moir%C3%A9_pattern
<hypermodern> with math see the calculations of parallel patterns.
<hypermodern> slow will give time for the eyes to perceptually burn in
<hypermodern> contributing to the movement
<hypermodern> even though the image is static!
<hypermodern> So what I'm wondering is if MM1 can render static lines at maybe 4 fps (or slower is fine)
<wpwrak> you may have more luck with precomputed images. you could still combine them with the video in image.
bkero1 has joined #milkymist
<hypermodern> great idea,from two channels right?
<hypermodern> so if you had two transparent png that would work?
<wpwrak> you may want to change the code for that, instead of trying to make the existing system do that
<hypermodern> The problem is I don't know how to code
<hypermodern> I know how to make images though...
<hypermodern> :-D
<wpwrak> transparency is actually alpha-blending. so you get a merged image. but yes, you have two image channels there to play with
<wpwrak> ah, without coding skills, this may be difficult :) alas, the M1 code probably isn't even a particularly good place to get started. it's quite clean, though. but sometimes a bit complex.
bkero1 has joined #milkymist
<hypermodern> and I have an idea of a looping static image installation
<hypermodern> which is a video synthesizer not making video digitally
<hypermodern> but through loopback degradation and moiré patterns
<hypermodern> so the actual hardware drives the visual effects and the *perception* and subsequent retinal fatigue of the viewer makes it move
<hypermodern> Thank you for the input wpwrak
bkero1 has joined #milkymist
<wpwrak> no problem. hope it's useful :)
<hypermodern> so to make sure I understand what you're saying I'd like to go through it
<wpwrak> you probably just have to experiment a bit to get a feeling for what works and what doesn't
<hypermodern> in channel 1 I put 180 degree vertical series of lines
<wpwrak> for pattern generation, i'd suggest trying to make some PNGs
<hypermodern> and in channel 2 I put a 175 degree diagnal
<hypermodern> they both have transparent backgrounds
<hypermodern> and then I can make a single image using the alpha blend correct?
<wpwrak> you can have a large set of images and pick each channel from that set. so you can have dynamic effects - or just a collection for trial and error
<hypermodern> I see, do you by chance know what the max memory is for images that ar 1024x768?
<hypermodern> maybe something like 40?
<wpwrak> i'm not sure if transparency in images is used by M1. but since the blending is additive, black means that the respective image doesn't add anything
<hypermodern> Ah, good tip. thank you.
<wpwrak> the rendering only runs at 640x480
<hypermodern> Ok
<hypermodern> how many images at that res?
<hypermodern> Roughly speakin
<wpwrak> and i think the effective resolution for images is only around 300x216. but i don't know where that limit comes from
<hypermodern> no problem...I just need to know how many roughly can be store in the mm1 memory
<hypermodern> to be mixed
<wpwrak> not sure ... maybe around 100
<hypermodern> Perfect
<hypermodern> Thank you.
<wpwrak> i only went to ~30 ;-)
<hypermodern> OK...this gives me a lot more perspective. Thank you wpwrak and wolfspraul
<hypermodern> I'll be back with a better understanding once I draw/write out my goals for the installation
<wolfspraul> thanks a lot!
<hypermodern> You're welcome ;)
<wolfspraul> with m1 I think what you need to expect is that you want to try a lot of things (assuming you have that motivation)
rejon has joined #milkymist
<wolfspraul> and in many of those cases, you run into 'missing' features
<wolfspraul> eventually you hit the bottom, and are 100% aware of what m1 can do
<wolfspraul> from then on it goes UPWARDS! :-)
<hypermodern> Well at this point it's all on paper
<wolfspraul> because the thing is actually very cool, but it takes time to get out of the hundreds of perceptions set by other computers
<hypermodern> so I am trying to figure out the parameters of what the tool *can't* do and then I get my freedom
<wolfspraul> oh it's great, you are doing exactly the right stuff with m1
<hypermodern> that's always true with any tool
<wolfspraul> yes
<wolfspraul> good
rejon has joined #milkymist
isa has joined #milkymist
cladamw has joined #milkymist
xiangfu has joined #milkymist
cladamw_ has joined #milkymist
voidcoder has joined #milkymist
mumptai has joined #milkymist
hypermodern has joined #milkymist
voidcoder has joined #milkymist
<GitHub27> [board-m1] adamwang pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/78ef08946f92a24032c5ff89f2d7e01adc1aca4e
<GitHub27> [board-m1/master] added Field for 'P/N' to part number and 'Smt' to record if DNP, correct connections. - Adam Wang
Martoni has joined #milkymist
elldekaa has joined #milkymist
azonenberg has joined #milkymist
<GitHub194> [board-m1] xiangfu pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/8e020ee2313bcf77a7d8df99364429a534f58282
<GitHub194> [board-m1/master] remove common.lib. use the KiCAD default device.lib - Xiangfu
<GitHub119> [board-m1] xiangfu pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/d310ea06f35d28997824d4d2557184d6e44dc9d7
<GitHub119> [board-m1/master] add m1-cache.lib to .gitignore - Xiangfu
<xiangfu> wpwrak, Hi
<xiangfu> why you add './' to the 'components.pro' Library?
<GitHub3> [board-m1] xiangfu pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/05fae055de763a3bb56d3b1eba9cd7e093c2c067
<GitHub3> [board-m1/master] Revert "remove common.lib. use the KiCAD default device.lib" - Xiangfu
rejon has joined #milkymist
<GitHub189> [board-m1] xiangfu pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/9b6bf67f86265e2add950452bd051849639acde6
<GitHub189> [board-m1/master] MISC: add LED matrix - Xiangfu
whitequark has joined #milkymist
jiri__ has joined #milkymist
<GitHub183> [board-m1] adamwang pushed 2 new commits to master: https://github.com/milkymist/board-m1/compare/9b6bf67...038fea1
<GitHub183> [board-m1/master] added external USB ports A/B - Adam Wang
<GitHub183> [board-m1/master] Merge branch 'master' of github.com:milkymist/board-m1 - Adam Wang
cladamw has joined #milkymist
<GitHub26> [board-m1] adamwang pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/35af0750795e6cf4ca31b305d84d5c231611f8a9
<GitHub26> [board-m1/master] added external USB ports C/D - Adam Wang
voidcoder has joined #milkymist
<GitHub43> [board-m1] adamwang pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/430b1c9b168452c91b8b40cd5a9ecc6346aad530
<GitHub43> [board-m1/master] added internal USB ports E/F - Adam Wang
voidcoder has joined #milkymist
sh4rm4 has joined #milkymist
rejon has joined #milkymist
mumptai has joined #milkymist
voidcoder has joined #milkymist
azonenberg has joined #milkymist
elldekaa has joined #milkymist
voidcoder has joined #milkymist
antgreen has joined #milkymist
jimmythehorn has joined #milkymist
Fallenou_ has joined #milkymist