<wolfspraul>
wpwrak: I forwarded you the faderfox reply
<wolfspraul>
he is one of the vast majoriy who always hits reply, not reply-all...
<wolfspraul>
just a heads up - Jon is still traveling, but in London his m1 (rc2 with l3/l19 fixes) froze on him several times
<wolfspraul>
he thinks it may be related to using the mouse
<wolfspraul>
so he's in the GUI, moving around with the mouse -> freeze
<wolfspraul>
first time I hear this, will keep an eye on it
<wolfspraul>
reboot fixed it, so it was not a big problem, but slightly embarassing with m1 hooked up to a big screen...
<wolfspraul>
rejon: I just mentioned your m1 hangs, maybe cause by mouse movement...
<wolfspraul>
if you have any additional feelings about this (as to the cause), please post...
<wolfspraul>
wpwrak: ok so mathias (faderfox) also suggested the LC2 and especially LD2
<wolfspraul>
I can somehow see how the LD2 could make sense
<wolfspraul>
it's very simple, but all endless encoders so it could work well with m1
<wolfspraul>
plus it works now (midi), unlike lv3 which first needs midi-usb support
<wolfspraul>
does the LD2 interest you at all?
<wolfspraul>
we could ask him to send a LV3 to Sebastien, and LD2 to you? I can also imagine buying some for myself/Jon/Xiangfu/others
<wolfspraul>
somehow I think the LD2 will give us quicker results at the beginning, until Sebastien has added usb-midi support (I don't think anybody else can add that quickly, so either Sebastien or no usb-midi for now)
<wolfspraul>
mathias has discounted another 2nd gen model to 99 EUR, though it's the LX2 which doesn't make much sense for m1 imho
<wolfspraul>
maybe he can give us a better price on the LD2 as well, if we order a few... (in addition to the m1 swap program which I will definitely do because it gets an m1 into the hands of someone in this industry, which is a must for us)
<wpwrak>
(FN 2.0 GUI) well, i already suggested a touch screen/tablet. and yes, i had virtual sliders and knobs in mind :) i still think that would be a very nice complement for more physical controls (or even a replacement for some people)
<wpwrak>
(gui) the patch would then simply define which set of controls it needs and the GUI would set up a suitable virtual layout. of course, one could combine this with a learn mode where you tap the virtual control, actuate the physical control (MIDI or such), and the physical control gets assigned
<lekernel>
yeah, that and also replace the equation editor
<lekernel>
actually maybe even the complete MD process :) as a superset of the current process
<lekernel>
there are a lot of hardcoded things which can be made more configurable
<wpwrak>
wolfspraul: (faderfox) thanks ! hmm, so doesn't like to make LV3. grmbl.
<wpwrak>
(rejon's freeze) maybe another variant of the MIDI freeze ? i wouldn't be terribly surprised if that wasn't limited to just midi
<wpwrak>
yeah. that was easy. killed it :-)
<lekernel>
?
<lekernel>
you fixed the midi bug?
<stekern>
lekernel: apart from looking insanely cool, is the reactable really providing an enhanced user experience compared to more conventional methods?
<wpwrak>
wolfspraul: (usb-midi) i think by the time we have the devices, sebastien will probably have implemented the support :) i think he once said the protocol didn't look too ugly
<lekernel>
well, if you could edit M1 patches with such an interface, it could motivate people to make some
<lekernel>
it doesn't have to be a touch surface btw, a 1st version could work with mouse (and be compatible with the current hardware)
<wpwrak>
(fied) no, it's still at large :-( but i was able to hang my M1 with the mouse, much like i did with midi
<lekernel>
ah?
<lekernel>
how did you do? moving it a lot?
<lekernel>
it never happened to me
<lekernel>
MIDI and mouse use very similar code ...
<lekernel>
so yes, it would make sense that the mouse can cause a crash as well
<lekernel>
maybe RTEMS doesn't like posting a message into a queue from an ISR?
<wpwrak>
i started rendering, created a "busy" scene (not sure if scene complexity actually matters), then jerked the mouse around a bit. i accidently hit the mouse button, so it went back to the GUI, and hung right there
<wpwrak>
hmmm
<wpwrak>
interrupt synchronization issues would explain a lot
<stekern>
yes, connecting together "boxes" with functionality would probably be more user friendly
<wpwrak>
(cooler gui) first, i'd clean up the language. as a i said, the whole thing is a bit of an insult to the whole IT profession :) we can still maintain compatibility with the old syntax
<lekernel>
he, say that to the milkdrop guys :p
<wpwrak>
yes yes, i know you're not to blame for that ;-)
<wpwrak>
for creating effects, i think just having a ton of controls can be very useful for the creative process
<wpwrak>
wolfspraul: sebastien suggested a joysticks because several variables are truly 2D vectors. e.g., points of reference (center of rotation, center of expansion) or shift vectors
<wpwrak>
i haven't use the pad as a true 2D control yet, just to control a pair of unrelated parameters
<wpwrak>
but i plan to do so. there are currently two obstacles: one is the hang, which gets in the way quickly. the second one it the small number of MIDI variables. i need to look into enlarging this set. maybe doubling or quadrupling it.
<wpwrak>
not sure if this is easy or hard. probably not too bad. gui will get a bit crowded.
<lekernel>
use pages, like on the DMX desk?
<wpwrak>
ah, note to self: i should test gui changes in 640x480.
<wpwrak>
yes, that's an option. may be the only choice in the end anyway
<wolfspraul>
wpwrak: ok, let's hope my connection doesn't break all the time
<wolfspraul>
so yes, it seems the LV3 is something he wants to phase out already
<wolfspraul>
after just barely having added it
<wolfspraul>
also it's not in his 10-minute intro video of 3rd gen controllers
<wolfspraul>
only the other 5 are
<wolfspraul>
I will confirm this in my next mail
<wolfspraul>
what do you think about the LD2 he pointed to?
<wolfspraul>
his naming is a mess. it looks like the FX3 is the closest 3rd gen equivalent to the LD2? :-)
<wpwrak>
yes, his naming is very messy. you need a dictionary :)
<wpwrak>
lemme check the LD2 ...
<wolfspraul>
I have a number of questions/replies already on his last mail, the only thing I need to know from you is what you think about the LD2, and which one in general you would be happy to receive as an early Christmas gift
<lekernel>
wpwrak, I wouldn't be surprised if some bug in the RTEMS port to LM32 messed up the use of queues with interrupts
<wolfspraul>
is there any software for an android or ipad tablet that would turn it into a midi controller?
<lekernel>
the LM32 port (initially made by a Finnish company) is "nothing serious" and no one really cares
<wolfspraul>
I think we should just be practical and pick the fastest and cheapest way *now* to get more value out of m1, for ourselves first, then our customers
<wolfspraul>
that's why I'm a little drastic and would even prefer the LD2 right now, because I can plug it in and make it work fast, without usb-midi support
<wpwrak>
the LD2 is just rotary encoders (with push function). that may be a bit limiting.
<wpwrak>
i'd still want the LV3, if only to have as diverse set of controls as possible to experiment with
<wolfspraul>
once we have usb-midi, the LV3 is great for experiments but it sounds like it will be phased out, joysticks causing too much trouble for him
<wolfspraul>
wpwrak: yes, but he says they have great precision and are endless
<wpwrak>
(usb-midi) as i said, it's not really a problem if you have a PC
<wolfspraul>
but the lv3 doesn't work today, can we really be that optimistic that usb-midi won't turn into a many-months endeavor?
<wolfspraul>
ah ok, sorry I forgot that
<wolfspraul>
well then
<wolfspraul>
lv3 your way?
<lekernel>
wolfspraul, send me that LV3 and i'll get it to work (natively)
<wpwrak>
(usb-miid) it works for me. now. very day ;-)
<wolfspraul>
ok ok
<wolfspraul>
lv3
<wolfspraul>
to Sebastien & Werner :-)
<wolfspraul>
and we get him an M1 in exchange, I really love that idea
<wpwrak>
everybody loves LV3, except for his daddy :)
<wpwrak>
a migration path from joysticks could be a touch pad
<wolfspraul>
wpwrak: why do you think endless rotary encoders with push are limiting?
<wpwrak>
there would only be space for one pad, as opposed to two joysticks, though (well, in theory you could have two really tiny pads, but i think that would be too crowded)
<wolfspraul>
they have push, replacing the need for keys, at least initially, unless the keys are velocity, pressure or displacement sensitive (will ask about that too)
<wpwrak>
first, they're not 2D, so you'd have to coordinate two rotary movement. also, you'd use both hands for a 2D control instead of just one
<wolfspraul>
and same for the faders I would think, only that you cannot so quickly go to either extreme maybe
<wolfspraul>
yes, compared to x/y you need two, agree
<wolfspraul>
that's indeed bad
<wpwrak>
i'm less sure about faster vs. pot vs. encoder
<wpwrak>
faster and pot have fixed stops, which can be an advantage, a disadvantage, or both at the same time
<wolfspraul>
yes
<wpwrak>
e.g., if you have well-defined semantics for the endpoints (such as no movement at 0), then it's nice if you can find that point easily, instead of having to "search" for it
<wolfspraul>
so basically you say we know so little about the exact usage on m1, for now we just want to have all variants to find the optimum use for them?
<wpwrak>
of course, if what you're controlling is endless in nature, such as the angle in a color wheel, a pot/fader would be limiting
<wpwrak>
also, pots/faders/joysticks retain their physical configuration when software changes. e.g., if you load a new patch, that may be a conflict
<wpwrak>
though it may be possible to avoid most problems there simply by being careful with what variable you assign to what control
<wpwrak>
(know little) yes, that's basically it
<wpwrak>
and it goes beyond this - we probably also want to give customers a lot of freedom there
<wpwrak>
so it's good if we have a device we can recommend. of course, there's the small problem that he wants to retire it. maybe we need to find out more about why exactly the joystick is such a pain for him
<wolfspraul>
he wrote it
<wpwrak>
gluing ...
<wolfspraul>
expensive/lots of work/glue/moq 1000
<wpwrak>
bah, who's afraid of MOQ ? ;-)
<wolfspraul>
but sure he is flexible
<wolfspraul>
I'm not so worried about that eol right now
<wolfspraul>
he has over 100 in stock/production, is flexible, we on the other hand have nothing but plans right now
<wolfspraul>
so we can focus on what is best to make our side work well asap, and then we will always find a controller
<wpwrak>
i'd at least like to try the joystick. see if they feel good and make sense. that will help with figuring out what to do next, e.g., joystick, pad, or abandon 2D and just combine 1D controls
<wpwrak>
yes, i guess if we're in shape to empty his current stock, the MOQ will not be his biggest problem ;-)
<wpwrak>
another thing that may be worth looking into are pressure/velocity-sensitive buttons
<wpwrak>
i could see a use for injecting images
<wolfspraul>
I will ask in my next round/reply
<wpwrak>
i played a bit with this: connect the camera, assign video_a to a button, toss snapshots into the effect
<wpwrak>
i'm having a bit of trouble with total brightness control.  and the nature of how patches are processed means that i can control the intensity of the snapshot with the duration of the button press
<wpwrak>
but it may be useful to have a faster way to control the brightness. also, there may be others effects where you want to make something go "boom", where a pressure sensitive button could be nice.
<wpwrak>
needs experimenting. an alternative could be pot/fader/encoder plus button
<wpwrak>
of course, again, this takes two hands :)
<wpwrak>
for my demo videos, i used a lot of control inputs on four variables: zoom/blur, rotation speed, wave amplitude (audio sensitivity), and offset from the center
<wpwrak>
that's about as much as you can do with both hands
<wpwrak>
i put all the color controls on the nanoKONTROL2, and they're much slower to access. of course, the color mix is propagated slowly anyway, and the color change rate is something i feel doesn't need adjusting a lot. most of the time, i just keep it at "fast", to get a busy image
<wolfspraul>
wpwrak: and what types of controls worked best for those?
<wolfspraul>
sounds like they could all be encoders, no? zoom/blue, rotation speed, wave amplitude, offset from center
<wpwrak>
maybe with improved color control, the color section would become more important. but i'll need to work on the math there, to get a useful "compression" of the color space. my current modulation of the original path in 3D space is pretty crude and makes it hard to get predictable results.
<wpwrak>
i have them all on faders for now
<wpwrak>
ah, i mean the color controls
<wpwrak>
for the rest, i have amplitude on a pot, offset on a big fader, blur and rotation on the pad
<wpwrak>
the use of the pad for these isn't driven by them wanting a pad but more my the pad being there :)
<wpwrak>
s/my/by/
<wpwrak>
so i need to play a bit more with sending them to other controls. hence the "learn" mode :)
<wpwrak>
what's nice about the pad is that it's very fast. this is particularly interesting for rotation. there i can "wiggle" the arms of a star pattern by rolling my finger. or make pulsed rotation by holding one point and tapping another
<wpwrak>
joysticks may be inferior in that regard. but let's see.
<wpwrak>
afk for a bit
<wpwrak>
back
<wpwrak>
just found another little MIDI quirk. "running status". that's when a midi message reuses the status byte of the last one. luckily, none of my equipment seems to generate this sort of stuff. anyway, will be easy to support
<stekern>
that is pretty commonly used
<wpwrak>
ah, good to know
<wpwrak>
midi is full of little surprises :)
<stekern>
yeah, it's one of those bw optimizations, I've learned about that one the hard way :)
<wpwrak>
i like how they hid it at the end of the protocol description, as far as possible from other things at the same layer :)
<wpwrak>
stekern: do you know if there's anything on linux that generates such sequences ?
<stekern>
can't remember if rosegarden did, or if it was some of my equipment that did
<wpwrak>
is there a decent midi sniffer ? i've tried kmidimon, but it always hangs after a few messages :-(
<kristianpaul>
epson emp 1765
<stekern>
I think I just used an oscilloscope ;)
<wpwrak>
grmph. does it always have to be the hard way ? :(
<kristianpaul>
thats the video projector dint allowme to demo M1 in pasto :(
<wolfspraul>
kristianpaul: excellent, thanks a lot!
<kristianpaul>
And btw i may demo M1 and nanonote in Ecuador in mid feb
<wolfspraul>
daredevil
<wolfspraul>
:-)
<lekernel>
those VGA problems are incredibly pesky
<kristianpaul>
indeed
<wpwrak>
interesting. the emp-1765 is unknown to google. what kind of device is this ? portable, home cinema, big screen, ... ?
<lekernel>
with another projector I had the issue that it detected 640x480 as 1280x1024 and only displayed a zoomed part of the picture
<lekernel>
I wonder what causes that
<lekernel>
maybe using 25MHz instead of 25.175MHz as pixel clock?
<wpwrak>
maybe some pulses the wrong length ? you'd think they could count the hsyncs between vsync, though
<wolfspraul>
one guy I met asked me whether m1 supports 'resolution detection'
<wolfspraul>
I don't know vga well enough - what 'resolution detection' is even possible?
<lekernel>
yes, with DDC
<lekernel>
the hardware supports it, it's even part of the test routine
<lekernel>
FN does not
<wolfspraul>
can m1 detect what resolution the other side wants/supports? or can the other side detect m1's resolution?
<lekernel>
M1 can detect
<lekernel>
if someone writes the right software
<kristianpaul>
wpwrak: big screen i guess, it was used to project like 6m from wall
<wolfspraul>
wait, who can detect what?
<wolfspraul>
(in vga)
<wolfspraul>
m1 can detect what the other side wants/supports? or the other way round? or both?
<lekernel>
the M1 can probe the connected devices for resolutions it supports
<lekernel>
then it output a signal in some of these resolutions, and the device will display it
<wolfspraul>
also unusual/special resolutions, say 640x200 ? (random example)
<lekernel>
with proper software support, which doesn't exist today, yes
<wolfspraul>
ok good
<wolfspraul>
he said that led walls often have unusual resolutions... (that's where the question came from)
<lekernel>
LED walls are often DMX... also possible, also lacks software
<wolfspraul>
his last event had a led wall with a 13:2 aspect ratio
<wolfspraul>
you mean all pixels of the entire wall are controlled by dmx?
<lekernel>
yes
<wolfspraul>
wow
<wolfspraul>
interesting
<wolfspraul>
is dmx fast enough for that?
<lekernel>
usually you have several DMX connectors for that
<lekernel>
so using the single DMX connector on the M1 will limit the resolution
<wolfspraul>
ok
<lekernel>
however it shouldn't be too hard to add up to 12 DMX outputs on the M1 using the expansion connector
<wolfspraul>
:-)
<lekernel>
the hardware is trivial, but it will - again - need copious amounts of software supports
<wolfspraul>
thanks for helping me understand the vga resolution detection situation, that's helpful
<wolfspraul>
oh sure, one by one
<wpwrak>
my wish would be more USB ports. a lot more :) usb-midi may already add 1-2 devices.
<kristianpaul>
some: fedback from a guy wich work in visual arts and assisted to christopher adam sharism talk
<wpwrak>
s/assisted/attended/ :)
<kristianpaul>
ah yes yes...
<kristianpaul>
ok:
<kristianpaul>
he mention the lack of a video mixer
<kristianpaul>
using a simple slider to mix two video inputs
<wpwrak>
ah, he wants more inputs
<kristianpaul>
is expensive and dont allow live coding
<wpwrak>
i think the mixer is kinda there
<kristianpaul>
all the expensive vj statations have video mixer
<kristianpaul>
also the effects still not impresive at all
<wolfspraul>
that is good feedback. how can we bind him a little more into the milkymist community?
<lekernel>
kristianpaul, did they use the camera? what patch did they show?
<wolfspraul>
always point to the twitter account, maybe this channel
<wpwrak>
for really good effects, i think we need better controls and also image support. that way, other design tools can be used to draw images and they can then be mixed into the patch
<kristianpaul>
wolfspraul: i already did point him to the channel and prefer stay where he is afaik
<wolfspraul>
sure, perfect
<kristianpaul>
he just know i own a M1 and wanted to share the comments
<wolfspraul>
let's bring people together
<wolfspraul>
yes, perfect!
<kristianpaul>
lekernel: i think he want to use two cameras at the same time
<wolfspraul>
we want to hear it, even if we heard it before etc. we need to bring those people together
<kristianpaul>
or two video sources perhaps?
<lekernel>
kristianpaul, but did they use the camera during the demo? and what patches did they show?
<wpwrak>
i'm not sure yet how good the current mixing features of M1 are. just made my first experiment with video on yesterday, in a bit of a hurry (to impress some girls ;-)
<wolfspraul>
one thing you can always reply today is that for sure, m1 is *different* from everything else
<lekernel>
I'm asking about the source of the "effects not impressive"
<wolfspraul>
the entire architecture
<kristianpaul>
lekernel: dont know
<wolfspraul>
that difference alone should justify (to some people at least) to give it the benefit of the doubt today and follow where it's going, with whatever level of commitment
<wpwrak>
lekernel: probably the usual: M1 running without sensitivity tuning - "screensaver mode"
<wolfspraul>
from that difference, I believe over time it will have features that people really love and will not find with the other solutions. but right now I'd have a hard time pointing to these features myself.
<wolfspraul>
kristianpaul: just saying this in general, I think people will be willing to listen and follow, m1 is something new :-)
<wpwrak>
lekernel: i'm actually beginning to like the built-in microphone because it provides a setup-free audio input. that helps to bring at least some life into the patches.
<kristianpaul>
wolfspraul: sure sure, he knows that, i told him about M1, he saw it working at labsurlab for the dorkbot transmition and now from this christopher adam and made the comments
<kristianpaul>
of course i asked to reply this here, he said is OKAY
<kristianpaul>
he is aware of copyleft hw, just when something dont seems to work for him, he just said it :)
<lekernel>
video mixer is so boring... but everyone's asking for that
<lekernel>
phew
<kristianpaul>
well i just telling what _people_ _want_ :-)
<wolfspraul>
kristianpaul: another thing to keep in mind, whenever you talk to someone who already has VJing experience, is that they will naturally compare it to the stuff they already know
<kristianpaul>
yes
<wolfspraul>
it may be worth pointing that out even to them
<wolfspraul>
we do not in any way want to claim that m1 can 'beat' all these other vj setups and software
<wolfspraul>
that's also why we must be open about potential feature shortcomings
<lekernel>
kristianpaul, for the last weeks I have not been complaining about people who are on this channel, I've been complaining about people who are _not_ here
<kristianpaul>
;)
<wolfspraul>
not that someone feels cheated or so once they find out the 640x480 resolution, for example
<wolfspraul>
so we clarify that
<wolfspraul>
but then we say - m1 is DIFFERENT
<kristianpaul>
i havent heard complaing about resolution yet
<wolfspraul>
some people have patience and energy to follow things that are different, and some don't
<wolfspraul>
sure I just tell you how I think we can convert some people
<wolfspraul>
when they start comparing to their existing solutions, the end result is already clear
<wolfspraul>
it will be: don't switch
<wolfspraul>
we don't want people to switch from resolume/modul8 etc on a notebook to m1
<wolfspraul>
instead, it's a new/different tool
<wolfspraul>
VERY DIFFERENT
<wolfspraul>
:-)
<wolfspraul>
either they appreciate that difference, or m1 is not for them, at least today
<wpwrak>
oh. by the way, how difficult would it be to support RGB in, i.e., use all three video connectors ? is this just a question of setting the right registers in the codec or would there be more ?
<wolfspraul>
see my point?
<kristianpaul>
no wait, he dint own a VJ stuff, but he already saw working some of then, i guesss prety similar situation if he already owned one
<lekernel>
wpwrak, in theory, just write a couple of adv7181 regs
<wolfspraul>
highlight the difference of m1, the fact that it's entirely new and different
<wolfspraul>
because I think it's true
<wolfspraul>
we compare features to a notebook/software solution, but in reality it's a completely different architecture
<wpwrak>
kewl. we should make that work at some point in time, if only because the presence of these three connectors strongly suggests you can use split RGB. and maybe it'll also help with video in quality.
<wpwrak>
wolfspraul: i'd emphasize the interactivity aspect. after all, people also buy gaming consoles :)
<kristianpaul>
anyway, i still asking people buy a new a very different M1 :-)
<wolfspraul>
interactivity yes, but you are a little ahead in your use of controllers :-)
<wolfspraul>
but of course, I agree
<kristianpaul>
lekernel: if got your message right, you mean this people out there should join the channel so we can convert him ;) ?
<kristianpaul>
i already realized midi is way to avoid get a boring M1 :-)
<kristianpaul>
wpwrak: had you already tried midi over osc?
<wpwrak>
kristianpaul: no, i haven't touched OSC so far. i picked the conservative approach and went all-MIDI
<wpwrak>
so yes, maybe you could also do USB-MIDI -> PC -> MIDO-to-OSC -> Ethernet -> M1
<lekernel>
yes, that should work
<wpwrak>
and save USD 5-15 for the USB-MIDI dongle :)
<wpwrak>
what would be a program (on linux) that implements such a transport ?
<wpwrak>
okay, how do i use OSC on the M1 ? i.e., how do i make things received end up in one of the oscN variables ?
<wpwrak>
or is this somethign that doesn't work yet ?
<wpwrak>
ah .. midi-over-osc ought to end up in the midi subsystem. good
<wpwrak>
grmbl. probably easier to write my own forwarder ...
<wpwrak>
does anyone have an example of a working oscsend ... /midi command ? i'm getting a little bit of reactions, but things are a tad weird
<lekernel>
oscsend /midi m ...
<wpwrak>
i'm trying things like  oscsend m1 4444 /midi m b0010200
<wpwrak>
what happens is that every once in a while. "Latest active controller" shows 1 (1)
<wpwrak>
leeet's debug this then ...
<lekernel>
packet losses? OSC is based on UDP
<lekernel>
try connecting the M1 directly to the computer
<kristianpaul>
he said potencial is no bad, and people ask about live coding because thing fpga can do on that
<kristianpaul>
so, last qute from him "pero ver que deviene en un screensaver es unpoco triste para tanto harware power :)"
<kristianpaul>
what i understand as hardware been really powerfull but underdeveloped?
<wpwrak>
oh ;-)
<wpwrak>
naw, the problem is elsewhere :)
<lekernel>
more bugs? phew
<lekernel>
this is sooo painful
<lekernel>
and it works for me, as always
<wpwrak>
are you using OSC for midi messages ?
<lekernel>
yes, I tested it
<wpwrak>
so how would you send a controller message, like a  b0 01 02  sequence ?
<wpwrak>
oscsend m1 4444 /midi m b0010200 ?
<wpwrak>
or maybe 00b00120 ?
<lekernel>
something like that... but that's something I did one year ago
<lekernel>
and no one touched it since then
<wpwrak>
okay
<wpwrak>
i think i figured out what's wrong. but it depends a bit on how oscsend is really supposed to work
<wpwrak>
ah yes, 00b00102 is right
<wpwrak>
good. then it's a one-line fix :)
<wpwrak>
now, let's test it ...
<wpwrak>
perfect
<lekernel>
ah, no bug this time :)
<wpwrak>
oh yes, a bug ;-)
<wpwrak>
i guess you were cleaning up some code and made a typo
<wpwrak>
contrOSC doesn't see to want to do what we need. (uses some special-purpose identifiers) hmm. seems funny that there wouldn't be a tool for simple MIDI->OSC forwarding
<wpwrak>
well, let's hack one ...
<lekernel>
ah, yes probably
<lekernel>
thanks for fixing
<wpwrak>
np. i like an easy one from time to time :)
<mumptai>
moin
<GitHub78>
[flickernoise] sbourdeauducq pushed 1 new commit to master: http://git.io/8NxJWw
<GitHub78>
[flickernoise/master] input.c: an OSC-MIDI message contains a complete command - process accordingly - Werner Almesberger
<GitHub22>
[flickernoise] sbourdeauducq pushed 1 new commit to stable_1.0: http://git.io/oJP2Fg
<GitHub22>
[flickernoise/stable_1.0] input.c: an OSC-MIDI message contains a complete command - process accordingly - Werner Almesberger
<lekernel>
hi mumptai
<mumptai>
needs some coffee
<kristianpaul>
wolfspraul and lekernel: there is  sdram on the LX9 board, 64Mb LPDDR
<wpwrak>
oddly enough, i can't hang the M1 with MIDI-over-OSC
<lekernel>
if my "message queue from ISR broken" theory is right, it can make sense
<wpwrak>
yes, it's a good theory
<wpwrak>
that would explain all the weirdness i'm seeing, plus it would explain why this kind of problem exists in such fundamental functionality
<wpwrak>
but before i try to pry apart that code, the hangover from yesterday needs a bit more subduing :)
<sh4rm4>
as if that single file had been deleted in the meantime... 00012 works
<sh4rm4>
nm, it works with another browser. seems i hit a random bug in chrome
<kristianpaul>
is okay here
<wpwrak>
lekernel: hmm, i rather start with a basis i know a bit. else it's very easy to end up chasing ghosts. but i'm looking at diffs between CVS and our tree (from the SDK) now
<wpwrak>
interesting detail: the rb trees are used in files that have "scheduler" in their names (and nowhere else). so maybe this is actually what causes the infamous lag.