05:11 | Bertl_oO | off to bed now ... have a good one everyone!
| |
05:11 | Bertl_oO | changed nick to: Bertl_zZ
| |
07:27 | se6astian | good day
| |
11:48 | Bertl_zZ | changed nick to: Bertl
| |
11:48 | Bertl | morning folks!
| |
15:40 | vup | Bertl: can it ever happen that you need to combine a B frame with a A frame one higher?
| |
15:40 | vup | for the sample footage se6astian uploaded some time ago for anuejn this seems to work better tm
| |
15:47 | Bertl | yes, if for some reason the exposure gets synced to the B frame, then you need to do that
| |
16:16 | anuejn | ouch that is bad :(
| |
16:19 | Bertl | it should be easy to prevent this from userspace before starting a recording though
| |
16:19 | Bertl | i.e. stop live acquisition, wait for odd frame, resume live acquisition
| |
16:20 | Bertl | (probably three or four bash lines ;)
| |
16:26 | se6astian | sounds like a good addition to the startup script
| |
16:31 | Bertl | maybe
| |
16:31 | Bertl | off for now ... bbl
| |
16:31 | Bertl | changed nick to: Bertl_oO
| |
17:31 | anuejn | hm... I guess we dont really mean the same thing
| |
17:31 | anuejn | what we are experiencing cant be detected automatically in a trivial way?
| |
17:32 | anuejn | it can be distinguished by looking at the results though but thats tedious?
| |
19:21 | se6astian | have you observed that actually happening so far?
| |
19:27 | anuejn | i guess?
| |
19:27 | anuejn | your sample footage looks better if we decode it "wrong"
| |
19:31 | Bertl_oO | anuejn: we are likely talking about the same issue
| |
19:31 | Bertl_oO | the problem here is the sequencer
| |
19:33 | Bertl_oO | the sequencer doesn't care wheter we have an A or B frame, it simply syncs to a frame change
| |
19:33 | Bertl_oO | if that happens to be a B->A transition, then everything is fine and you will get A and B frame from the same exposure
| |
19:37 | se6astian | interesting!
| |
19:38 | se6astian | so how could this be tested/verified?
| |
19:39 | se6astian | the 4 line bash script you suggested would run on the beta?
| |
20:01 | Bertl_oO | yes, and it would read out the frame counter register
| |
20:02 | Bertl_oO | wait for the right moment and then enable the acquisition
| |
21:11 | se6astian | that is fil_reg 15 ?
| |
21:16 | se6astian | and accessing the frame counter register can be done like in https://github.com/apertus-open-source-cinema/axiom-firmware/blob/main/software/scripts/axiom_raw_mark.sh I assume?
| |
21:51 | Bertl_oO | capture is turned on/off via the button overrides in capture reg 15, yes
| |
21:51 | Bertl_oO | the frame counter is in the hdmi generator register block
| |
21:53 | Bertl_oO | axiom_raw_mark does not access the frame counter, it just configures static overlay entries
|