#apertus IRC Channel Logs

good morning

comradekingu: your suggests for article changes are much appreciated but generally I opted for a more story-teller style of writing in contrast to your to-the-point short way of putting facts on the table: me: "We have reached a major milestone: The hardware designs for the AXIOM Beta are complete!", you: "A major milestone is reached, completion of hardware designs for the AXIOM Beta!"

best team-talk video so far :)

se6astian, comradekingu: maybe add as a separate language? (english-nostory)

ha, I don't think it's that

milling, fabrication, camera output, etc

ahoi all..

nice tt. But i guess there will still be some open questions till all backers will be contributing in phase 1 (or at least: the most of them). Maybe we could open a thread in the lab or something to collect and answer them - so we'll get as much people as possible on the phase 1 step .. (We may not forget that we invited them to spent 350 bucks on the development of an working prototype - there will be a lot of concerns before they

but i am not the "taking it all serious customer" at all..

for example: "do we get rid of the defect/ or wrong working columns on the right sensor side? (might be some kind of *dirt on the surface) - we all remember how long it take a big australian company to get some clean sensors into their 4k cinema camera and finally ship them - and how much their customers became upset just about this further delay..

and not worry too much about the currently heavy noise even under well lit conditions ..

Thanks for your efforts!!

my only crit with the recent test footage is there's still quite a few over exposed shots

PhilCee: AFAIR BM had physical dirt compromise thei sensor in the manufacturing process, we have digital artifacts that are most likely caused by a software issue that drives the sensor or processes the data coming from it

intracube: true, especially the bursts are a bitch to focus and expose properly - at the time we created them we did not have live hdmi

so it was shooting, downloading, developing, looking

se6astian: eep

light meter, expose for highlights :)

problem was also that we shot macro and had no idea what we actually had in view when focus is off :)

seb - thats something to make a point: the "wrong" columns are no hardware problem - something we can fix in software .. and so on. I guess there will ba still a lot of questions till people check in with another grand..

got2go.. i'll have a look at the logs later on..

hi Bertl

intracube: I'm sadly never had the chance to shoot movies on film but learned to use a external light meter at university. Bought one than and love lighting, powering the cam up and being ready to go.

hey guys, do you know how I would go about joining in to help out on the beta project?

glad to hear :)

I was hoping to help out with generating IP for the FPGA

my background is as a Systems Architect

well, for now we have been unsing VHDL

personally I consider it the "better" language compared with Verilog, but we don't have a problem with either

about two and a half years ago, we started hacking on the FPGA side, and back then, I checked out both HDL dialects and went with the IMHO nicer one (although less popular :)

Is there a running list of IP blocks that you guys are hoping to create?

probably the best start is to get familiar with what we have now and figure out what makes sense to tackle

that makes sense. is there a git repository or anything like that?

we have a git repository, but it is not (yet) up to date, here is the most recent code:

note: this is a port from the firmware we had for the AXIOM Alpha (with various adjustments) to the Microzed/Beta

yes, either use the .xdc files for pin assignment or check with the schematics

all the schematics are available online, if you can't find something or need something in a different format (e.g. pdf) just let me know

if you want to start hacking on it right away, I'll check in the latest version and you can use that

note: we are using Vivado (web license)

and everything can be built from the command line

(doesn't mean that you can't use the gui)

ok cool. I'll probably bundle some things into a makefile. Usually makes life easier that way IMO

yeah. I think I just missed the prompt. was going for James as the nickname

yep. will be setting up Pidgin

completely agree

yep. so where can I find the git repository?

Try reading it as a story. It lacks the realism of a story told verbally, and its far removed from anything that reads casually. I found it very hard to understand at all

Instructions shouldnt be a story, which is another point i fell off

ok. that makes sense

we haven't used git much yet, but I'd say we have to figure this out in the near future

ok. my recommendation would be for the "core team" to all be added to that repository directly and each change be done on a branch.

makes sense

I've also been working on a side project that is supposed to make open source hardware sharing a little easier

makeables.info if you were interested in checking it out

should have git as a backend in another year

thanks. alpha should be functional in a month

of course

so, are you "expecting" an Early Beta soon?

not sure what you mean by that question

I just signed up for preorder. It'd be nice to get some hardware at some point soon, but there isn't a rush on that.

Although if you guys need help with mechanical drawings or anything like that, I could help out there as well.

hello hello

works for me. I doubt that there is a central location for work needed? Just so that way I can pick off one item at a time

we are using phabricator for coordination

https://lab.apertus.org/

but note that we haven't added many software tasks yet, because the focus was on getting the hardware ready

what software are you guys using for the skeleton? (aka the mechanical drawings. I noticed KiCAD for the pcb side of things)

onshape.com seems pretty cool for that kind of thing

Guest2304: while we still plan to migrate to KiCad, we have been using Eagle for now, but despite the fact that it isn't open source software, it is not a vendor lockin

Eagle has a "free" (as in beer) version which can be used to do simple stuff and view complex stuff

interesting. curious how git would handle merges on those files then

KiCad has dramatically improved over the last year or two since CERN got interested and working on it

so I hope we will soon find the time an leisure to migrate

however, it still is the best opensource mechanical cad program I know of

excellent! welcome to the team! :)

note: I'll read up on anything you direct at me (either by prepending my nick or as private chat), it might take some time, but you'll get an answer

ok. that works for me. I probably won't be needing an immediate answer anyways

ok. sounds good.

yep, IRC channel is #apertus @ irc.freenode.net

looking forward to it

excellent

off for now ... bbl

irieger: yep, same here. I've never had the chance to shoot on film

http://www.hitfix.com/motion-captured/what-one-bad-screening-of-the-hateful-eight-means-for-the-future-of-film