Author Topic: Pre-recording for the raw_rec module?  (Read 8282 times)

bouncyball

  • Member
  • ***
  • Posts: 153
Re: Pre-recording for the raw_rec module?
« Reply #50 on: March 27, 2017, 06:30:40 PM »
@g3gg0: :D

vstrglv

  • Member
  • ***
  • Posts: 126
Re: Pre-recording for the raw_rec module?
« Reply #51 on: March 29, 2017, 07:51:59 PM »
mvl_lite.mo from magiclantern-crop3x.2017Mar21.5D3113 supports 10 and 12bit, but mvl_lite.mo from Exp. Latest Build (2017-03-27 23:39) not. Why? 5D3 1.1.3
Canon 5D3

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 9711
  • 5D Mark Free
Re: Pre-recording for the raw_rec module?
« Reply #52 on: March 29, 2017, 09:01:43 PM »
Because the 10- and 12-bit recording is not yet in mainline.

Feedback is mixed, and I don't use it in practice, so I could not judge whether it's OK to merge it or not in this state. Sorry.

vstrglv

  • Member
  • ***
  • Posts: 126
Re: Pre-recording for the raw_rec module?
« Reply #53 on: March 29, 2017, 10:10:26 PM »
Thank you alex. It's a pitty, because 10 and 12bit reduce bit rate threshold for CF card.
 If i load mvl_rec.mo and mvl_lite.mo from Exp. Latest Build (2017-03-27 23:39) and activate mvl_rec there is  sound recording now. 
Canon 5D3

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 9711
  • 5D Mark Free
Re: Pre-recording for the raw_rec module?
« Reply #54 on: March 29, 2017, 10:34:13 PM »
The two modules are not meant to be loaded together (as any symbols exported by both will conflict somehow, but the linker doesn't warn about it and I don't really know how it's handled). I should probably enforce this somehow.

The mlv_lite module from the crop_rec branch also has the H.264 proxy included, and it's faking mlv_snd status in order to show the audio meters (since you can use the H.264 stream for audio). This is the source of conflict.

The conflict with mlv_snd is an obvious one, but I bet there are more.

Not sure what's the best way to fix, as this method (exporting symbols and letting the linker figure it out) allows some communication between modules, but it has its limits.

dfort

  • Hero Member
  • *****
  • Posts: 1548
Re: Pre-recording for the raw_rec module?
« Reply #55 on: April 09, 2017, 07:28:14 AM »
I've been playing around with rec-trigger. There's a special mlv_lite module in the Experiments download page that should work on all platforms. If you configure it a certain way you can shoot single frames which is great for timelapse and animation. The way to do it is by setting the Pre-record to OFF and the Rec trigger to Half-shut:pre only.



An issue I had was that the counter shows time in minutes, seconds and tenths of seconds: MM:SS.1/10sec. so with a standard frame per second video rate you need to take a few exposures before the counter advances.



I tried changing the display so it uses a timecode like, MM:SS.FF. I thought it was pretty cool so I submitted a pull request before testing all the possible variations of the Pre-record options. a1ex found all sorts of problems with my code so I started going further and further down the rabbit hole, changing variable names and adding menu items until I got something that might be useful. It is still quite experimental so I stuck it in the Advanced menu.



As you can see I left the time display that was adapted from the ffmpeg time unit syntax as the default and added the option to display the counter in Timecode format or in Frames. This probably isn't SMPTE approved timecode because it is based on the record frame rate instead of the playback frame rate but it does advance every time a frame is saved and it displays pretty much the same minutes and seconds as the ffmpeg version.

If the camera is set for NTSC 30fps (actually 29.976 more or less) the frame counter goes from 00 to 29 then it advances the seconds counter. Likewise at 25fps it goes from 00 to 24 and at 24fps it goes from 00 to 23, just like timecode. This should help for those cases when you are shooting one-frame-at-a-time and need to be more accurate than 1/10sec.



If anyone wants to try it out I put a test build of the mlv_lite module which should work on all platforms in my bitbucket download area. Look for magiclantern-mlv_lite-rec-trigger-experiment.

Feel free to post comments on the pull request:

https://bitbucket.org/hudson/magic-lantern/pull-requests/823/display-counter-in-timecode-format-mm-ssff/diff

EOSM.202 EOSM.203 700D.115 5D3.*

DeafEyeJedi

  • Hero Member
  • *****
  • Posts: 2833
  • 5D3 / M1 / 7D / 70D / SL1
Re: Pre-recording for the raw_rec module?
« Reply #56 on: April 09, 2017, 08:45:14 AM »
Thanks for this much antcipated Timecode implementation, @dfort and I guess I wasn't supposed to try this together with an Non-CPU lens info experimental build (2017-04-04) because I am getting this message below running on 5D3.123 and not sure if this is to be expected?



Perhaps I should try w Nightlies instead?
5D3.113 • 5D3.123 • EOSM.203 • 7D.203 • 70D.112 • 100D.101

dfort

  • Hero Member
  • *****
  • Posts: 1548
Re: Pre-recording for the raw_rec module?
« Reply #57 on: April 09, 2017, 07:05:02 PM »
Interesting find @DeafEyeJedi. I only tried it with a nightly build.

Best to look at one experiment at a time.
EOSM.202 EOSM.203 700D.115 5D3.*

 

courtesy