02:21 | rton | left the channel | |
02:30 | Bertl_oO | off for another quick nap ...
| |
02:30 | Bertl_oO | changed nick to: Bertl_zZ
| |
03:13 | seaman | left the channel | |
03:31 | supragya | joined the channel | |
03:33 | slikdigit | left the channel | |
05:45 | supragya | left the channel | |
06:15 | hof[m]1 | left the channel | |
06:16 | hof[m]1 | joined the channel | |
06:21 | Bertl_zZ | changed nick to: Bertl_oO
| |
06:21 | Bertl_oO | morning folks!
| |
08:18 | se6astian|away | changed nick to: se6astian
| |
09:02 | rton | joined the channel | |
09:04 | se6astian | changed nick to: se6astian|away
| |
10:03 | se6astian|away | changed nick to: se6astian
| |
11:42 | indraneel | joined the channel | |
11:45 | indraneel | left the channel | |
12:17 | ArunM | joined the channel | |
12:23 | ArunM | left the channel | |
13:23 | seaman | joined the channel | |
13:36 | se6astian | changed nick to: se6astian|away
| |
13:37 | aombk3 | left the channel | |
15:43 | comradekingu | So i told this environmental agency about the apertus merits in terms of ethical production and sourcing. However, the current landing page says nothing about that, so it can't be featured. Is this information displayed anywhere?
| |
16:04 | BAndiT1983|away | changed nick to: BAndiT1983
| |
16:07 | BAndiT1983 | comradekingu -> https://www.apertus.org/opensource -> "Professional Manufacturing"
| |
16:14 | comradekingu | BAndiT1983: That doesnt actually pin down anything
| |
16:15 | BAndiT1983 | "what we care about" does it for me
| |
16:16 | comradekingu | It is just intent
| |
16:16 | comradekingu | It doesnt say anything about conflict materials, regulations, contracts, programs, nothing
| |
16:17 | comradekingu | Apple "cares" about this stuff too
| |
16:17 | comradekingu | It just strikes me as unprofessional
| |
16:19 | BAndiT1983 | ?
| |
16:21 | comradekingu | https://www.apertus.org/opensource to say it as honestly as possible, is just not cutting mustard
| |
16:39 | supragya | joined the channel | |
16:39 | supragya | hi BAndiT1983
| |
16:44 | BAndiT1983 | hi supragya
| |
16:44 | BAndiT1983 | how is it going?
| |
16:45 | supragya | quite good!
| |
16:45 | supragya | have you read the long email?
| |
16:45 | BAndiT1983 | of course
| |
16:46 | BAndiT1983 | monitoring IRC, lab and my mails through the day
| |
16:48 | supragya | okay.. you had a few question?
| |
16:49 | supragya | regarding MXF
| |
16:49 | BAndiT1983 | it was mostly about MXF-like structure, still not totally sure that we can accomplish whole processing in the camera
| |
16:49 | supragya | camera doesn't really need to make those inside... given the document
| |
16:49 | BAndiT1983 | wrote already yesterday about separate data files (video and meta data) or a stream with embedded meta data
| |
16:50 | BAndiT1983 | just want to ensure some things, as the discussions turn always to advanced formats, but the focus should be on the required data
| |
16:50 | BAndiT1983 | no problem here with converting in post, to reduce the strain on the camera
| |
16:51 | supragya | I PM'ed you a link
| |
16:51 | supragya | can you have a document open aside...
| |
16:51 | BAndiT1983 | i know the specs, at least to some level
| |
16:51 | BAndiT1983 | opened it
| |
16:53 | supragya | MXF should not be hard.. given it is jst a KLV format storage
| |
16:54 | supragya | if we can get the raw12 out
| |
16:54 | BAndiT1983 | it doesn't answer my point, what we should get from the camera and in which format
| |
16:54 | supragya | as stream maybe... then a constant Length can be appended with appropriate key before flushing to disk
| |
16:55 | BAndiT1983 | there are many formats out there, but first we need the data as some package which comes from the camera
| |
16:55 | supragya | A good way of doing is more of MLV way, have to say this
| |
16:56 | supragya | (initial metadata)-(data)-(data)-(mode change meta)-(data)-(data) etc
| |
16:56 | BAndiT1983 | MLV was developed for such cases, as some parts of canon EOS are unknown and others are processed by their camera MCU
| |
16:56 | supragya | in anycase... I would recomment this data not to be kept as is... and should be converted to anything like XDNG before it hits post
| |
16:57 | supragya | *CDNG
| |
16:57 | BAndiT1983 | there are a lot of things which can be calculated from meta data and image data, so we should grab as more as possible for later processing
| |
16:57 | BAndiT1983 | of course it will be converted, but first we need the data in some format which allows hi-speed output
| |
16:57 | supragya | [as more as possible for later processing] -> this was one of the issues
| |
16:57 | supragya | since a GPS module would make sense for example
| |
16:57 | supragya | but MLV does not have that
| |
16:57 | BAndiT1983 | that's why my example was focussed on ARRIRAW, we need something similar, they also use frame server for preview, if i remember correctly
| |
16:58 | BAndiT1983 | why do you care about GPS currently?
| |
16:58 | supragya | my issue is that then we would have to make new blocks for this
| |
16:58 | BAndiT1983 | we could embed custom tags or re-use existing ones
| |
16:58 | BAndiT1983 | and what is the problem with that? if we convert it afterwards in right format for CDNG or MXF etc., then there is not much issue
| |
16:59 | supragya | [why do you care about GPS] -> more of other things... such as lens info (which is currently under discussion in MLV)
| |
16:59 | BAndiT1983 | the question is, if we just write such things into some extra file or not
| |
16:59 | supragya | [and what is the problem with that? if we convert it afterwards in right format for CDNG or MXF etc., then there is not much issue] -> just wanted to know if this was on table, or we were to ship MLV directly to post
| |
16:59 | BAndiT1983 | maybe it's too much to embed it everytime, so we can use json for example and then merge
| |
17:00 | BAndiT1983 | i would go for conversion, because current hardware would struggle a bit with advanced stuff
| |
17:00 | supragya | [so we can use json for example and then merge] _. a custom header in MLV to hold JSON?
| |
17:00 | BAndiT1983 | afterwards we can re-use the modules on the camera
| |
17:01 | BAndiT1983 | and if we don't use MLV, but just a stream with frame markers?
| |
17:01 | supragya | a good direction to look into
| |
17:01 | BAndiT1983 | hope that g3gg0 will come online today, as he is the primary mentor ;)
| |
17:01 | supragya | but doesn't that lead to whole plethora of new problem why we create specs like MLV in first place?
| |
17:02 | supragya | take for example stereoscopic data
| |
17:02 | BAndiT1983 | stereoscopic data would include 2 streams or one with alternating sensor data
| |
17:03 | supragya | alternating sensor data _> s1,s2,s1,s2 (as this)?
| |
17:04 | BAndiT1983 | yep
| |
17:04 | supragya | a simplistic model such as this... would have to always be extended for new requirements... let's say if we export darkframes for meta
| |
17:05 | BAndiT1983 | i would go with XMP file, which would be merged with video stream later to MXF, CDNG etc.
| |
17:05 | supragya | that would mean we have two channels for output?
| |
17:05 | supragya | one for data, other for things other than data?
| |
17:05 | BAndiT1983 | yep, fast one for video data and slower one for meta
| |
17:06 | BAndiT1983 | just ideas, as direct output would be nice, but also requires a lot of testing in-camera
| |
17:07 | supragya | then data+marker is good thing
| |
17:07 | supragya | on fast lane
| |
17:07 | supragya | maybe we can throw in a serial number between the data (such as an int or long)
| |
17:08 | supragya | this would allow to sync packets between the two comm channels
| |
17:08 | BAndiT1983 | some sort of id is necessary, also as some sort of hash in case of failure
| |
17:09 | supragya | the two channels as in :[https://trello.com/c/aX7KJihl/24-the-planned-usb3-recording-pathway] ?
| |
17:09 | BAndiT1983 | yep
| |
17:10 | BAndiT1983 | unordered frames maybe, so the output doesn't lag
| |
17:10 | supragya | [unordered frames maybe] -> serial numbers just for that too
| |
17:11 | supragya | these serial numbers can be quite cyclic, however should be distinguishable
| |
17:11 | BAndiT1983 | that's the idea
| |
17:11 | BAndiT1983 | or you can read the order out of the XMP meta data
| |
17:12 | BAndiT1983 | i suppose, that this one should be ordered, but frame data sorted afterwards in post
| |
17:12 | BAndiT1983 | preview with frame server would also be possible, don't see any issues there too
| |
17:12 | supragya | [read the order out of the XMP meta data] -> how are you imagining this?
| |
17:13 | BAndiT1983 | data is written in the right order of frames, with id/hash, frames get same id, but related to them
| |
17:13 | BAndiT1983 | XMP data would be ordered, so entry one would correspond to frame 1, which could be frame 3 in the stream
| |
17:14 | supragya | and mapping operation be done based on hash or ID?
| |
17:14 | BAndiT1983 | yes
| |
17:15 | BAndiT1983 | don't think, that they will be off by far in the stream, also it's not the final word, that any disorder would be there, just throwing some considerations from MLV format
| |
17:15 | supragya | in scene we are looking at... why is MLV there?
| |
17:16 | supragya | isn't (data/id stream) + (XMF) the idea now?
| |
17:17 | supragya | does MLV comes up in the fast lane in this model? or XMF?
| |
17:19 | BAndiT1983 | XMP can be transferred over ethernet, as it can be written more slowly, and MLV was just an example for frame disorder
| |
17:20 | BAndiT1983 | video data -> fast output, meta data/XMP -> slower output
| |
17:22 | supragya | ARRI foramt specification are available? I would like to look at it
| |
17:22 | supragya | ARRI metadata white paper?
| |
17:22 | BAndiT1983 | don't think so
| |
17:23 | BAndiT1983 | ArriRaw is a raw codec similar to CinemaDNG that contains unaltered Bayer sensor information, the data stream from the camera can be recorded via T-link with certified recorders like those from Codex Digital or Cineflow.
| |
17:24 | supragya | the format is proprietary?
| |
17:24 | supragya | ah yes, you said it was
| |
17:24 | BAndiT1983 | file:///C:/Users/Andi/Downloads/ARRI_Metadata_White_Paper_ALEXA_SXT_SUP1.0_ALEXA_Mini_AMIRA_SUP4.0_ALEXA65_SUP1.1.pdf
| |
17:24 | BAndiT1983 | ah sorry, wrong link
| |
17:25 | supragya | :) XD
| |
17:25 | BAndiT1983 | http://www.arri.com/?eID=registration&file_uid=17128
| |
17:25 | supragya | I would fly to get hold of your computer now BAndiT1983 ? :) [file:///C:/Users/Andi...]?
| |
17:26 | supragya | that is the white paper
| |
17:26 | BAndiT1983 | don't know if there is open info or just an overview
| |
17:29 | supragya | more of an overview... list of tags as such..
| |
17:29 | supragya | not the way they record it...
| |
17:34 | BAndiT1983 | but maybe some ideas for required meta data
| |
17:34 | BAndiT1983 | but wiki mentions some tool which can read the tags from ARRIRAW
| |
17:41 | supragya | [ some ideas for required meta data] -> as in what has to be collected?
| |
17:41 | BAndiT1983 | yes
| |
17:42 | supragya | tiff tags give quite extensive view on that...
| |
17:45 | supragya | CDNG what has to be collected: pg24, how MXF is (FWIW): pg14, still would look into ARRIRAW, but basic tags would be more or less the same
| |
17:46 | supragya | Changes occur in maybe color data representation etc... only (which is not the metadata in focus now)
| |
17:46 | BAndiT1983 | ARRIRAW seems to be proprietary, other google links sugest that too
| |
17:47 | BAndiT1983 | *suggest
| |
17:48 | supragya | Image Orientation _> maybe this: Bertl once told me that data could be mirrored
| |
17:49 | supragya | The sensor can mirror the image vertically. This may lead to rearrangement of rows (first row becoming the last row and so on). However, this does not change the column order inside the rows
| |
17:51 | BAndiT1983 | any advantage or purpose?
| |
17:51 | supragya | no. It just does... maybe Bertl_oO may explain this more
| |
17:51 | supragya | Moreover, some way to encode if it was an electronic shutter or physical shutter (so we have both in camera)?
| |
17:52 | BAndiT1983 | to be honest, haven'T dived that deep into that area
| |
17:53 | supragya | maybe also, ways to encode external systems: remote shutter / WiFi module / Flash system
| |
17:55 | BAndiT1983 | that's the gsoc task ;)
| |
17:56 | supragya | :) in any case... an extensibel XMF should do fine in that case
| |
17:56 | supragya | *extensible
| |
17:57 | supragya | BAndiT1983: can we three have a meeting on Sunday... ?
| |
17:58 | BAndiT1983 | think so, at which time, as on saturday here is the night of museums, so will be out till late at night
| |
17:58 | supragya | I am home... please decide a time that suits you
| |
17:59 | BAndiT1983 | anything after 12
| |
18:00 | supragya | [anything after 12] -> timezone +1 UTC?
| |
18:01 | BAndiT1983 | yep, berlin time
| |
18:01 | BAndiT1983 | ah, it's utc +2
| |
18:03 | supragya | How about Sun, May 6, 2018 [18:00 UTC +2 Berlin] / [21:30 UTC +5:30 India] ?
| |
18:04 | BAndiT1983 | if it's not too late for you, then ok
| |
18:05 | supragya | Good time for everyone, I can push back if you want to enjoy your evening
| |
18:06 | BAndiT1983 | no need to, as it's usual time when i do some stuff for apertus on sunday
| |
18:06 | supragya | I feel it is okay for everyone then!
| |
18:06 | supragya | I will inform g3gg0
| |
18:08 | BAndiT1983 | very good
| |
18:13 | supragya | i would be off for now.. have a great day
| |
18:16 | BAndiT1983 | ok, see you, you too
| |
18:18 | supragya | left the channel | |
18:37 | seaman | left the channel | |
19:39 | illwieckz | left the channel | |
19:40 | illwieckz | joined the channel | |
19:50 | seaman | joined the channel | |
20:38 | Bertl_oO | off to bed now ... have a good one!
| |
20:38 | Bertl_oO | changed nick to: Bertl_zZ
| |
20:54 | g3gg0 | joined the channel | |
20:54 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
20:54 | g3gg0 | hi
| |
20:55 | se6astian|away | changed nick to: se6astian
| |
22:18 | intrac | left the channel | |
22:24 | BAndiT1983|away | changed nick to: BAndiT1983
| |
22:34 | RexOrCine|away | changed nick to: RexOrCine
| |
23:27 | se6astian | changed nick to: se6astian|away
| |
23:43 | BAndiT1983 | changed nick to: BAndiT1983|away
|