Saturday, 2014-01-25

drobillafalktx: You using -Wcast-align too?00:02
falktxnot sure now00:02
drobillaAs I write down how atoms are by definition 64-bit aligned, knowing that my code is totally not -Wcast-align clean by any measure, I wonder how actually true that is :)00:02
drobillaThe NASA JPL coding guidelines are a good source for insane compiler warnings and code quality measures, by the way.00:03
falktxnope, no cast-align00:03
falktxbut I'll add it  now00:03
drobilla(LV2 iiiiiiinnnnnn spaaaaaaaaaaaacccccccceeeeeeeee)00:03
falktxI want to use '-Wsign-conversion' but Qt clashes with this00:04
drobillaGtk2 violates a few I use too, the strict prototypes ones IIRC.00:06
drobillaThose only apply to C though.00:06
drobilla(Great for ensuring that every function that can be static is static in C though)00:07
falktxwhat about "-ansi -pedantic" ?00:07
falktxthat's usually fun...00:07
drobillaMost of my C++ is C++0x these days, but I do use pedantic00:07
drobillahttp://pastebin.com/vFTePKRe00:08
drobillaI keep two levels, ultra-strict is for "stuff I look and and would like to be clean for, but aren't"00:09
drobillaI skip through errors in emacs, so any warning really gets in the way, strict is day-to-day dev flags.00:09
*** falktx has quit IRC00:31
*** falktx has joined #lv200:53
*** HarryHaaren has quit IRC01:02
drobillaOutput ports with a variably sized type MUST be initialised by the host before every run() to an atom:Chunk with size set to the available space. The plugin reads this size to know how much space is available for writing. In all cases, the plugin MUST write a complete atom (including header) to outputs. However, to be robust, hosts SHOULD initialise output ports to a safe sentinel (e.g. the null Atom) before01:03
drobillacalling run().01:03
drobillaOops.  This is a contradiction.01:03
drobillaNot sure what the best rule here is.  I'd be tempted to say hosts must set the type to 0 and initialize the size, but this may conflict with future use of the reserved type 0 (with non-zero size) for references.01:08
drobilla<characteristicShortNameGripe>InputPort and OutputPort were kind of silly when Inlet and Outlet are there for the taking01:19
*** HarryHaaren has joined #lv201:22
drobillaMaybe it's best left undefined for now, then.  i.e. the only thing plugins can depend on is that the size indicates the amount of space available for writing01:24
*** Gethiox4 has quit IRC01:32
drobillafalktx: Speaking of warning flags, LV2 itself is inherently not const-correct thanks to our friend connect_port()01:33
drobilla(Also known as The Thing We Did Totally Wrong)01:33
falktxheh, forgot about that one01:34
drobillaWe really should have left room for extensibility in LV2_Descriptor01:35
drobilla(extension_data can do it, of course)01:35
drobillaAnchakor: My solution to RDF wankery knee-jerk was to talk about the mechanics completely without referring to specific type at all, so it's all bits and bytes until section 302:14
drobillaThen type hierarchy, which is mostly numbers anyway.  No Turtle until at least page 302:15
drobilla1. Introduction 2. Mechanics 3. Semantics (4-* ?).  I think this works well.  Saying "Semantics" might be a red flag, but it's just such a tidy split :)02:16
drobillargareus: Deadline for paper-submissions: January 27th, 2014 (23:59 HAST)02:45
rgareusdrobilla: sounds about right.02:46
drobillargareus: ... Hawaiian-Aleutian Standard Time?  Am I missing something? :)02:46
rgareusdrobilla: that's correct. we're on Hawaiian time02:46
drobillaOkay then.02:46
rgareusdrobilla: it gives pretty much everyone a good extra day, and it allows Frank to lazily close submission after breakfast in europe.02:47
drobillaheh02:47
rgareus(though it's a pretty safe bet that there'll be a deadline extenstion.)02:48
rgareusextension, even.02:48
drobillaI didn't hear that.02:48
rgareusbut you can submit and update (until submission really closes)02:48
drobilla4:59 a.m. EST, so basically, "before sleep time" for me02:48
falktxrgareus: who is going to read the papers btw?02:51
falktxI really didn't want to "waste" too much time on it02:51
falktxI mean, right now I see the paper more like a formality02:52
rgareusfalktx: a peer review comittee will read it. at least 2 independent persons per paper02:52
falktxnot something that really needs to be perfect02:52
falktxrgareus: can submissions get rejected? if so, why? and how many usually do?02:55
falktx(sorry for all the questions, I'm a very curious person)02:55
rgareusfalktx: yes, there's a fixed number of presentation slots.02:56
rgareusfalktx: and the rejection rate depends on the number of submissions.  the highest so far was about 50% when LAC was at stanford.02:56
rgareusfalktx: last year I think rejection rate was 10-20%02:56
rgareusfalktx: Frank Neumman (AudioFranky on IRC) is chair of the review committe02:57
rgareusfalktx: he knows this stuff.02:57
rgareusfalktx: I only learn most of this over beers at the conference. -- scientific ethics demand from me that I don't peek :)02:58
rgareus(which I could do as root)02:58
falktxhmm, I need to speak to him then02:58
falktxsee if I can persuade him...02:59
rgareusfalktx: well, the review is done by independent peers, but most of which are just the usual LAU/LAD crowd.03:00
rgareusfalktx: eg. http://lac.linuxaudio.org/2012/ has a "Review committee" list for said year03:00
rgareusfalktx: unless you write complete BS, I dare say there's a high chance of being accepted one way or another.03:02
drobillafalktx: I wouldn't extrapolate too much from my worries, in a conference like this 'show and tell' papers about projects don't really need to adhere to some lofty standard03:02
falktxI have the topics for the paper in place, just need to write the content now03:04
drobillaI'm a Computer Scientist describing some lofty ideas that are a bit to left field for this crowd, and am basically trained to try really hard to make them bulletproof because it's my job, and in the sort of conferences usual in my field, aggressive rejection definitely happens.03:04
drobillae.g. the conference I submitted my last failure to had a 15% acceptance rate03:04
drobillaI'm only really woried about people like Fons who I'm pretty sure personally hate me :)03:05
rgareusThe two main idea ideas behind LAC papers: (A) written documentation is always good   and  (B) provide creditablity03:06
drobillaYeah, this process is really making me realize I've been fucking up by not doing it every year, because then I'd at least have publications to show for this absurdly massive amount of work I've done.03:06
rgareusdrobilla: you are free to submit the paper blinded for review.03:06
drobillargareus: Yeah, big mystery there :)03:07
rgareusdrobilla: I was just going to say that03:07
rgareusdrobilla: that's why we stopped bothering.03:07
drobillaI'm sure it's fine.  I'm sort of wired to assume everyone hates me.03:08
rgareusthere's a very strong correlation  author <> topic in linuxaudio03:08
drobilla(and this stuff in particular)03:09
drobillargareus: speaking of creditability, shame your lightning talk on GL UIs isn't in the proceeding.  How should I cite that?03:14
drobillaFancy UIs in general are a good use case for needing a real protocol, should be mentioned.03:14
rgareusdrobilla: mmh. I don't know.   I was drafted for a speaker that could not come and jumped in for this lightning talk with 4 hours preparation!03:14
drobillaheh03:15
rgareusdrobilla: there's no real publication.03:15
drobillaJust asking in case you have a .bib entry hanging around03:15
*** NickSB2 has joined #lv203:16
rgareusdrobilla: I suppose  http://lac.linuxaudio.org/2013/program/83   will work as reference03:16
drobillaEven the W3C stuff doesn't really publish, my bibliography is ultra questionable from a scholarly standpoint, but such is tech in the trenches03:16
rgareustitle: openGL UIs for LV2 plugins ; year: 2013 ;  <URL>03:17
rgareus'tech in the trenches' hell yeah!03:19
drobillaYeah, I like "in the trenches".  Usually contrasted against either completely out of touch theory types, or Enterprisey™ wankers :)03:20
rgareusthe vast majority of RFCs do not have any bib. or just a few references03:20
drobillaYeah.  Unfortunately bibtex styles are all over the place, I usually end up just ramming stuff in there wherever to make the output look sensible.03:22
drobilla(Not a huge fan of ACL style)03:22
*** falktx_ has joined #lv203:30
*** falktx has quit IRC03:33
*** HarryHaaren has quit IRC03:35
* drobilla decides that citing LISP is a stretch03:35
drobillahttp://www.cs.uni.edu/~wallingf/blog-images/people/john-mccarthy.jpg03:36
* drobilla wants a poster of this so bad03:37
rgareusLOL03:39
*** falktx_ has quit IRC07:21
*** edogawa has joined #lv207:32
*** Gethiox has joined #lv209:54
*** timbyr has quit IRC10:22
*** timbyr has joined #lv210:24
*** shanipribadi has joined #lv213:12
*** falktx has joined #lv213:13
*** NickSB2 has quit IRC14:23
*** Gethiox2 has joined #lv215:15
*** Gethiox has quit IRC15:15
falktxand now I realized I had even more bad lv2 time types15:29
falktxtime:beat is a double, I had it as long15:29
falktxhttp://lv2plug.in/ns/ext/time/#beat15:29
falktxerrrrr :(15:29
*** falktx has quit IRC15:57
*** falktx has joined #lv216:05
*** rncbc|AFK has quit IRC16:08
*** rncbc has joined #lv216:18
* drobilla wonders if a C atom validator is possible17:04
drobillafalktx: i.e. your host was sending that to plugins?  (when receiving you really should check anyway)17:04
falktxyes, sorry17:05
falktxnot sure how I made that, I copied some from jalv. is it possible that jalv has it wrong too?17:05
drobillaI need to flesh out those docs.17:06
drobillaI don't think jalv even sends beat.17:06
drobilla(beat != barBeat)17:06
falktxyep17:07
drobillaMostly derived from jack transport, but beat stuff became float to make ticks go away17:08
falktxI kinda want ticks though17:10
drobillaWhy?17:15
falktxBBT = bar beat ticks, what's wrong with ticks?17:16
drobillaTicks means choosing some ppqn.  It seems objectively better to send a massively higher resolution float you can easily convert to a tick if you want17:16
drobillaYou can consider it ticks with PPQN somewhere around 3 billion :)17:19
wrljust multiply the fractional part by some arbitrary ppqn to get ticks17:20
falktxI'm just following the jack design17:21
falktxit's easier when porting software17:21
drobillaPerhaps.  The mishmash of things that start from both 1 and 0 in jack transport is silly IMO17:26
drobillaOh well.  "Easier" by one division.  You'll live :P17:26
*** rncbc has quit IRC18:12
*** mlpug has joined #lv218:17
*** mlpug has quit IRC19:48
*** mlpug has joined #lv219:54
*** edogawa is now known as CarlosSantana20:02
*** CarlosSantana is now known as edogawa20:03
*** mlpug has quit IRC20:18
*** NickSB2 has joined #lv221:33
*** kaspar_e has joined #lv221:34
* drobilla desperately tried to cram code into these 40 character columns21:57
drobillatries*21:57
*** ssj72 has quit IRC22:04
*** ssj72 has joined #lv223:14
*** edogawa has quit IRC23:35

Generated by irclog2html.py 2.13.0 by Marius Gedminas - find it at mg.pov.lt!