#apertus IRC Channel Logs

(As in what would an ideal protocol / hardware combo offer?)

(or what is it you're looking for?)

Bandwidth

we also want 12bit (maximum on the CMV12k)

At 300fps?

it can do up to 150FPS at 12bit IIRC

the highest sensor rate is at 10bit with 300FPS, IIRC

without any framing, encoding or checksums

In your estimation, all protocol checks in, your ceiling would be around where?

18-19?

Yikers.

so around 24Gigabit on wire

yes, quad SDI should work, dual 12G SDI also

I don't think it is realistic to make a movie with 150/300 FPS

(Not quite a standard ala AC wireless)

I think they have settled more or less

3G-SDI

So really, at that data thruput, it is all onboard for the foreseeable future. Striped or otherwise.

Is there a time code library out there? (For actual time code audio, not the numbers.)

troy_s: do you know google? https://github.com/x42/libltc

you have to decide if you are talking about raw out or video out

good morning

morning folks!

hi!

i mean like this: do 1 for example for 3 hdmi connection

I think that is already planned

how's it going?

nice to hear! well i have a few days off from work so i thought i say hi to u guys and have a look what's trending in here =)

Hi Bertl

I expect my goto camera todo atleast 120fps

your comments are appreciated :-)

PRN: what I meant is, for high speed photography 150/300 FPS is usually way too slow and for making "a normal movie" the data you get when you film everything at 150 FPS is probably not worth the efford, as you would have a lot of post processing to get to sane shutter times

hehe, yeah even tarsem singh wont do the whole film at 300 lol....peace

by the way. is there someone who already startet a design for the heatplate to sensor to peltier thingyding?

so we want copper i guess? would it make sense to pipe/lead the heat to the bottom of the camera? the idea is to connect it directly to the bottom plate that holds the rods or mounting plate. basicly in the space betweteen the camera and the tripod

copper or aluminum, depending on how important weight is

so you are working at least against convection

so we get the possibility to connect the peltier at the bottom and the top?

depends on the enclosure I guess

while looking at this.. https://www.apertus.org/sites/default/files/Pcbstack02-V3.jpg

pcb wise our contact area for the heatplate would be below the image sensor holder board through a hole? or directly on top/infront of the sensor?

so maybe best of both worlds to both sides of the camera. i like the 2 sided idea cause it gives more freedom. if your not going to use a peltier you still have the option to put a heatsink on top, sides or bottom depending on which direction we go with the heat transfer.

o/

nice, what's the size/resolution of the LCD display?

in the 3d model it's an image plane with a 640x480 texture

hmf, and I've only -just- noticed that the menu items don't line up with the buttons

best would be pixel accurate fonts and symbols without any smoothing

Bertl: couldn't all the text and icons be pre-rendered?

Bertl: if you've ever seen winamp skins

Bertl: what program, software will generate the GUI?

*googles even

Bertl: yep

Bertl: custom C library or existing?

http://fortawesome.github.io/Font-Awesome/

I doubt we will have a web browser running on the remote control :)

it wouldn't even have to do any alpha blending if done carefully

note that a display buffer for 640x480 (assuming an RGB display) already consumes about 400kbyte memory :)

why so limited?

well, of course we can add memory and flash, etc, but I don't see that this would make sense for such a limited interface

the character set for the display: https://lh5.googleusercontent.com/-DggV4DaimnY/VH5NxcM1fXI/AAAAAAAAA84/Ic0nuyO-n7k/w250-h299-no/apertus_control_characterset_4bit.png

hmm, I missed out a : from the characters

the big one behind the 9 works too =)

nevermind i tried to be funny ^^

Bertl: IMO it's important to make the interface look as modern as possible

the large timecode characters would look really bad

Bertl: another question if you've got time; does the 512kB include the frame-buffer or is it separate?