<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 20, 2018 at 8:24 AM, Chris Caudle <span dir="ltr"><<a href="mailto:chris@chriscaudle.org" target="_blank">chris@chriscaudle.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On Wed, April 11, 2018 8:21 am, Chris Caudle wrote:<br>
> And the app is set at 29.97fps? I'm still confused about why ffmpeg is<br>
> flagging the video file as 29.89fps.<br>
<br>
</span>I found a useful program called mediainfo available in the Fedora<br>
repositories.<br>
Original project seems to be here:<br>
<a href="https://mediaarea.net/en/MediaInfo" rel="noreferrer" target="_blank">https://mediaarea.net/en/<wbr>MediaInfo</a><br>
<br>
CLI and GUI versions available.<br>
The report from mediainfo for the phone video contains this info on frame<br>
rate:<br>
<br>
Frame rate mode : Variable<br>
Frame rate : 29.892 FPS<br>
Minimum frame rate : 16.411 FPS<br>
Maximum frame rate : 30.344 FPS<br>
<br></blockquote><div><br></div><div>I am going to check that program out as its clearer on what's going compared to what I doing now, thanks for the tip. <br><br>I've delayed my response because I have been doing
some bash script hacking with ltcdump that I almost have working. Hours
turned into days :-) . Its not that big of a script and I will have
more to say on that soon. <br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I'm not sure how variable frame rate works in h264 encode/decode,<br>
presumably it has to be converted to a consistent frame rate for playback,<br>
but I'm not sure.<br>
Perhaps that is confusing the video file import, I have only ever worked<br>
with video files with constant frame rate.<br></blockquote><div><br><br>The phone problem with Ardour was indeed because it was a variable rate issue. I was able to fix it with this command. And then Ardour was fine with it. <br><br>HandBrakeCLI -i ../motox_in_file.mp4 --cfr -r 29.97 -o fixedmoto.mp4<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I know you said you were purchasing some kind of small video camera, I<br>
have not compared prices lately but it might be useful to see what older<br>
SLR cameras with video capability are selling for on the used market. <br>
1920x1080 is only around 2M pixels, maybe there are a lot of 2M - 6M pixel<br>
cameras getting sold cheaply because all the photo people want the new 20M<br>
pixel hotness. DSLR also has the advantage you can switch out for better<br>
or at least more appropriate lenses at some point if you want (telephoto,<br>
wide angle, different aperture capability, etc.). I guess verify that the<br>
files from a DSLR work like you need first, my wife's SLR doesn't do video<br>
so I can't check with that model.<br>
<span class="gmail-HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>So I was able to get the Q8 working with Ardour too. The Tentacle Sync LTC generator also works fine and I'm really happy with it. <br><br></div><div>TBH I think phone cameras are "good enough" for this project, but it requires a usb interface and while the Irig DUO works ok I just like the Q8 workflow more. The camera on the Q8 is nothing special but the audio is fantastic. To be clear my priority is good audio and then whatever video that comes with it is ok for me. <br></div><div><br></div><div>My main problem finding a camera is something with good audio via XLR inputs. Audio only recording is a nice plus. The Q8 right now is $350 and I couldn't find anything else with XLR inputs under $1000. The main issue with the Q8 right now is that its from 2015 and I expect a new model soon. Even still I am probably going to buy a second one. <br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-HOEnZb"><font color="#888888">
-- <br>
Chris Caudle<br>
</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
______________________________<wbr>_________________<br>
Ardour-Users mailing list<br>
<a href="mailto:ardour-users@lists.ardour.org">ardour-users@lists.ardour.org</a><br>
To unsubscribe or change your mailing preferences please visit:<br>
<a href="http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org" rel="noreferrer" target="_blank">http://lists.ardour.org/<wbr>listinfo.cgi/ardour-users-<wbr>ardour.org</a><br>
</div></div></blockquote></div><br></div><div class="gmail_extra">So about these scripts I am writing ...<br><br></div><div class="gmail_extra">I can sync both cameras fine individually. Ardour and Xajdeo only supports one video at at time. Best I can tell the typical workflow using Ardour for multiple cameras, has a video software editing step in between recording and Ardour. <br><br>However I googled and I couldn't find a Linux based UI that can read LTC - besides XJadeo but for multiple videos that's not the right tool? I installed a couple things and couldn't figure out how to read ltc. There must be something people use for multiple cameras that contain ltc though, any hints appreciated. <br><br></div><div class="gmail_extra">In the meantime I thought it would be relatively easy to segment the videos via ffmpeg and then pipe that into ltcdump. Using bash (or any language) for timestamps parsing is tricky though so I'm debugging that now. Soon I'll either get stuck or show what I have working. <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Kind regards, <br></div><div class="gmail_extra">Robert<br></div></div>