evilsoup

Thanks @Randal'Thor. @Axelrod -- it looks like that meta post does answer the problem here -- leave the existing answers where they are, so long as they're not calling religious texts or other sacred stories 'fiction'. (Unless I'm missing something, which I might be as it's half past midnight where I am. Night night.)

Both to clarify and to see what the current usage

Also, that meta post is nearly five years old and seems to me to be primarily about preventing trolling from obnoxious atheists. I'm not really sure that it's entirely relevant to this case... or might be worthwhile putting up a new question on meta?

@Axelrod -- well, in that case the religion-based answers would be incorrect... But I believe the standard policy on stackexchange sites is for incorrect answers to be dealt with via votes rather than moderation tools.

To fit in with the spirit of the rule, it would make sense to change the wording of the question from 'Where in fiction entailing magic...' to something like 'What's the earliest known story involving magic or the supernatural...' (assuming such a change would accurately reflect the OP's intention).

... It seems pretty clear that the whole point of a ban on having questions or answers about religious texts is the potential to cause deliberate offence (i.e. by mighty internet atheists). That's clearly not the spirit of the question or any of the answers in this case. To state that a frequently-used element of fiction has antecedents in religious texts does not imply anything about said religious texts.

@Marco I think you are correct, yes; if you'd care to claim the bounty, please feel free to expand that into an answer with a little more explanation.

(the actual documents I'm working on are essentially novels)

so I use that because it's the first thing I've found WRT pandoc's creation of PDFs

@Marco I have basically no knowledge of LaTeX

this question would be off-topic on latex.SE (I think), but given that I think a proper answer would involve LaTeX, I thought I'd post it here, for some LaTeX gurus to have a look at...

hello all

This question should be migrated to SuperUser, I think:askubuntu.com/q/271975/112879

oh whoops, sorry I assumed it was a general-use room :P

man, all this good stuff is going to get lost in the general chat, I should have opened up a separate room for this conversation

well, I'm due to compile it myself (for opus & drawtext support) anyway, so if you want I can test it out later today/some time tomorrow

you should file it on the ffmpeg bug tracker

actually, that sounds like a potential bug

hmm

heh

actually, the timestamps are saying that you answered first

lol probably

thank you for the feedback on my stuff, too :)

ace

maybe put in something along the lines of 'this information was originally taken from the HandBrake wiki, but has since been deleted from there'

so I say, just go for it

I don't think that strictly applies to the information in the wiki; but on the other hand I seriously doubt that anyone is going to go after you or me or the FFmpeg wiki for copying over a deleted guide from there freely-available wiki,

well, HandBrake itself is GPL

that is annoying

but better safe than sorry, you know?

I mean, I'm sure they wouldn't mind, since both HandBrake and FFmpeg are FOSS projects

copyright doesn't end just because the text is deleted from the internet

well I guess it depends what the handbrake wiki's policy is

hmm

the only thing for the crf info: if you copied it from wikipedia, I believe that you have to cite them as the creator

groovy

it's all good, count the pennies & the pounds count themselves :)

maybe migrate that crf stuff over to the x264 encoding guide on the ffmpeg wiki, since it's x264-centric

well I'm glad that those are relatively minor corrections, and I will definitely incorporate that stuff into the next version

here you go; I don't think it has any information you don't have, but if you have any criticisms of it they'd be nice to hear :)

with x264, you probably should mention the presets, since they're just as important in controlling file size as the crf

oh actually, there's one more thing

your table is a nice summary of the information, though

but before I consider it ready for the ffmpeg wiki

mostly just as a staging point, so I can push out the information somewhere people can see

I have an empty blog set up, just for this post (and a few other|)

I've actually been working on a blog post (to later be incorporated into the ffmpeg wiki, when I think it's up to scratch) that covers very similar ground to your table. I'll put up the WIP and give you a link, there may be something in there that you can use.

Apart from that, the only omission on the list is the new Opus encoder; but that's very new, and I haven't got to play with it yet, so I'm not entirely sure how it's supposed to work

Unfortunately, AFAICT, AC3 doesn't have a VBR mode, so it may not fit properly there

Also, if you're going to mention MPEG2, you should also probably add in AC3 audio - which is commonly used on DVDs alongside MPEG2 - as the most common use-case for MPEG2 in ffmpeg is probably creating DVD-compliant VOB files.