699 karma · joined March 28, 2011
Realist, pragmatist, strong-willed, strong-minded. Sometimes taciturn, sometimes loquacious. FLOSS enthusiast but still using Windows. Alpine Linux advocator.
I'm not sure about papermail, i.e. whether it supports "format=flowed" or not. Perhaps the mail lacked it anyway.
Use gmane for your own sake and sanity: http://thread.gmane.org/gmane.comp.video.blender.devel/40386
About page gives good idea what it is and how it differs from Avisynth.
VapourSynth is an application for video manipulation. Or a plugin. Or a
library. It's hard to tell because it has a core library written in C++
and a Python module to allow video scripts to be created. It came to be
when I started thinking about alternative designs for Avisynth and most
of it was written over a 3 month period. The software has been heavily
inspired by Avisynth and aims to be a 21st century rewrite, taking
advantage of the advancements computers have made since the late 90s.
The main features compared to Avisynth are:
* Multithreaded - Frame level multithreading that scales well
* Generalized Colorspaces - New Colorspaces can be specified at runtime
* Per Frame Properties - Additional metadata can be attached to frames
* Python Based - The scripting part is implemented as a Python module
so you don't have to learn a special language
* Support for video with format changes - Some video just can't stick
to one format or frame size. VapourSynth can handle any kind of
change
* Compatible with a large number of already existing Avisynth plugins
Mind that it is still WIP. It's not complete Avisynth drop-in replacement, but it's close as possible, yet diverges whenever things can/should be done better. It's mostly ABI-compatible for Windows Avisynth plugins.
Don't be fooled by simplified mpv --help output. :)
Usage: mpv [options] [url|path/]filename
Basic options: (complete list in the man page)
--start=<time> seek to given (percent, seconds, or hh:mm:ss) position
--no-audio do not play sound
--no-video do not play video
--fs fullscreen playback
--sub=<file> specify subtitle file to use
--playlist=<file> specify playlist file
https://github.com/mpv-player/mpv/blob/master/DOCS/man/en/op...
In the past VLC used to display wrong colors or downgrade video quality for better performance, not sure how it is now (possibly a bit better).
Relevant: http://www.cccp-project.net/wiki/index.php?title=Media_Playe...
mpv is a free and open-source general-purpose video player. It is based on the MPlayer and mplayer2 projects which it greatly improves.
Changes from mplayers: https://github.com/mpv-player/mpv/blob/master/DOCS/man/en/ch...
Quoting JEEB's explanation from IRC:
> sounds like mplayer2, which used to be uau's patchset for mplayer. And then mpv was forked out of mplayer2 because uau wouldn't merge things from other developers
Lachs0r's Windows binaries: http://mpv.srsfckn.biz/
I encoded:
V ebg-rq guvf grkg whfg gb znxr lbh phevbhf.
V ebg-rq guvf g′瀀栀攀瘀戀栀昀⸀To be less off-topic: good job on making it, openness and finally shipping it.
[1] https://mediacru.sh/demo
[2] http://en.wikipedia.org/wiki/Love,_Chunibyo_%26_Other_DelusionsBug spotted. Setting avatar in the profile doesn't work.
EDIT 1: Apparently it started to work (even without doing logout and login again).
I noticed also that after editing the track title and saving it's not updated in the view - I have to refresh the page to be sure, whether the change actually did happen.
EDIT 2: Changing e-mails doesn't require mail confirmation. While it may seem as PITA for many, it's good in avoiding mistakes and spamming accounts you don't really possess.
EDIT 3: And information about changed mail came where? To mail address used during registration. :) It would be fine if I got it delivered to my new address too, but I haven't.
(And I do curse Microsoft for making IE 9 Vista+ only browser, which is quite likely explainable by use of some shiny new undocumented API, that wasn't available in XP and before. Microsoft and their browser tightly coupled with OS...)
tml xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:page="http://tjansen.de/minifiedPage" xmlns:i="http://tjansen.de/internal" xmlns="http://www.w3.org/1999/xhtml">
My wild guess it's targeting voice commanding, which I practically never use as voice recognition is still not reliable enough (and I'm not always comfortable with shouting at my phone in public).
Good job!
Now I remembered something! Some time later I tried contacting Rick van Rein, thinking that maybe he would be interested in a new version of the patch, or rather he could review it and I would learn something, but I never got the reply from him.
I hope my attempt isn't too embarassing, yet can be interesting for someone, so I just published my mail to Rick with the attached patch [3]. Feel free to show me how wrong I was in my poor "refinements" of the original patch! I would be more than happy (even though I'm not into kernel now at all) to get constructively bashed about it.
[1] http://rick.vanrein.org/linux/badram/
[2] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/bad_memory.txt
[3] https://gist.github.com/przemoc/5251104 Internal compiler error
A few years ago I was doing lot of Linux kernel builds. My desktop computer, which is Athlon 64 X2 4600+ and 2x GeIL PC2-6400 DDR2-800 C4 ULTRA DUAL CHANNEL (2x1GB each; 4GB total), was doing make -j6 (or -j8, don't remember now) of kernel one after another. After many many hours some builds started to failing with mentioned error. Let's say 1 of 4. I had to do it, so I was repeating make (automatically) till it succeeded, but later I fiddled with memtest86+. It was running day and night on all 10 tests (I believe that was test count back then) and something popped up finally (I wasn't checking it constantly) [1]. But you know what? When I switched to showing badram patterns later and the problem reappeared, it was red line without any pattern! I used to see some addresses and such whenever error was detected by memtest (or experience computer halt, etc.), but that time I had seen nothing - it was quite enigmatic. I've checked memtest sources and test 5 was filtered out from showing badram patterns as apparently not being reliable. I changed it (I've just found the changed sources on the disk and diffed it to the original release [2]), recompiled the memtest and run it again. I got badram patterns this time [3].
I needed BadRAM patterns to secure myself from being constantly hit by this memory problem, but I don't remember whether I used them in the end.
I still use this computer. No big compiles, no big problems, but sometimes I get the iffy feeling. :) I had a few BSODs since then and I believe they were caused by this memory problem. Haven't seen its manifestation for a long long time. Maybe my computer was simply overheated back then? Since then I'm much more into checksums than I used to be...
[1] http://i.imgur.com/RMhCOLM.jpg
[2] https://gist.github.com/przemoc/5250861
[3] http://i.imgur.com/jFHZkVA.jpgAnd regarding optimization. Language-defined integer type size is one thing and CPU register sizes used in calculations is different thing. It's not like having 32-bit int forces you (or compiler) to use 32-bit registers.
For every int we (i.e. programmers) should be aware of possible min and max values that can be stored in it. Thus we can easily use fixed-size ints everywhere, paying attention to signedness too of course. The problem is that there is high temptation of using int most of the time, because it's easier to write (it's shorter). For the same reason many C programs use int instead of unsigned short or uint16_t for instance. Well-defined int size is part of self-documenting code, as it shows mindfully applied constraints.
In practice, only when you're writing some loops with small number of iterations etc., you don't care whether your counter for instance is 24-bit integer or 48-bit, because 16-bit or maybe even 8-bit would be enough. In most other cases you care whether 64-bit value will fit into your value or not and whether it can be there at all. And if you care about memory you use smaller ints in your structures when bigger ones aren't needed.
So, to some extent, it is indeed not a big deal. But it still isn't "not an issue". We gain more than 2^31-1 elements in slices on 64-bit platforms, true, but it should be possible from the beginning, without need to redefine int on such platforms.
> Previous Go implementations made int and uint 32 bits on all systems.
> Among other things, this enables the allocation of slices with more than 2 billion elements on 64-bit platforms.
If they truly wanted to have platform-dependent int, then why 64-bit int on 64-bit platforms wasn't introduced from day 0? It's a valid question, because it would avoid this big (implementation) change at all.
> However, programs that contain implicit assumptions that int is only 32 bits may change behavior.
I can agree that this assumption is wrong, but why changing int implementation now?
> Due to the change of the int to 64 bits and some other changes, the arrangement of function arguments on the stack has changed in the gc tool chain. Functions written in assembly will need to be revised at least to adjust frame pointer offsets.
My main point is that variable-sized int implementation and usage gives more problems than we get profits in return, even more when previous and widely used 1.0 version, which 1.1 is going to be backward-compatible with, did it differently.
Again, I wouldn't comment if variable-sized int was in Go 1.0 implementation, but it wasn't.
http://theoldreader.com/feeds/import
"Thank you for uploading your OPML file. We will soon start importing your subscriptions, which might take up to several hours depending on the amount of feeds you have.
There are 22325 users in the import queue ahead of you."
It may take some time indeed... I have 114 subscriptions and some of them can be dead now, as I haven't used GR for quite some time.
IMO not old enough to be not supported, but YMMV.
1. I see it differently. I usually know/see some first approximation that could be easy to do (and fixed later when better solutions comes up), but I'm totally resisting to do what I perceive as inferior solution. My procrastination may be even about finding this better solution and the problem is that I am holding the progress at all just because I'm fiddling with getting something super right atm, which is rarely really needed (almost never). My performance is perceived by others as non-existent, because I'm paying attention to details that may not even really matter.
2. This one is the obvious one, but it's not the main procrastination problem. 10% at most. Well, until you're constantly working at night for instance (because of your procrastination) and you're becoming constantly tired through the day - then you're making being tired a sad routine. It's procrastination force feedback, but again, it's not the main reason for procrastination as I see it.
3. Starting doing real job is somewhat "scary", true, but it's often simply the effect of 1.
4. If you can postpone something, it's obviously not that important to you right now or you feel that there is enough time to do it a bit later (and you feel it will be a quick thing, which isn't always the case, many times also because of the perfection factor).
In the end, despite aiming for perfection, I often have to make cuts, go with worse (in my eyes) solution, because there is no time for "playing" and deadline is already behind me. This is the worst.
"You see, procrastinators tend to be people who have, for whatever reason, developed to perceive an unusually strong association between their performance and their value as a person. This makes failure or criticism disproportionately painful, which leads naturally to hesitancy when it comes to the prospect of doing anything that reflects their ability — which is pretty much everything."
First paragraph in the text that stuck me so deeply. And it's not like I fear criticism (https://news.ycombinator.com/item?id=5361495), but my urge for perfection is killing my performance and this in fact is indeed literally killing me.
I may reevaluate feed idea when I see intelligent reader that will show me early the most interesting stories from my subscriptions and will do it with a style. Reading must be a pleasure, not pain. Typographically web is a horrible place, there is so much that can and should be improved. Feeds should be your better (i.e. correctly) looking versions of the texts you can find on the web.
Google Reader Plus extension improved a bit comfort of using GR, thanks to multi-column view for instance, but it wasn't enough to keep me using GR.
But well, I may be wrong, and Maxis is simply no longer the company that it used to be.
Anyone willing to record screencast how OneTab fails at handling million tabs? :)
Ask HN: Open source commenting systems for static pages - alternatives to Juvia?