Jump to content

Bouke

Members
  • Content Count

    234
  • Joined

  • Last visited

  • Days Won

    4

About Bouke

  • Rank
    Hero Member

Profile Information

  • Location
    Netherlands
  • About
    I'm a developer of software tools, both ''off the shelf' as custom work.
  • Interested in Sound for Picture
    Not Applicable

Recent Profile Visitors

2,043 profile views
  1. It should be possible, and perhaps a good time to finally build a Linux box and toy around. What is the screen resolution you want to use? Touchscreen? First things first, did any of you test it already? (The latest version, I forgot to put an 'about' in the menu, but if you see the option 16/24 bits, it's current.) If it does not sound good, what's the point? (Do test with / without the meters turn on, the meters work in between the chunks, in theory, that could introduce ticks every 10 msec.)
  2. Hi Daniel, Yep! If you have time, please toy with it and let me know your findings!
  3. If this thread is revisited in another 5 years, I've made a small simple (lossless, what goes in goes out) audio delay that can delay up to 10 seconds, in steps of 10 msecs. (Using any soundcard present.) It's free, and even brings it's own VU / Peak meters. Mac only at the moment, but I'll make a Win version when my Win box is powered up again. Download AudioDelay here
  4. Just for fun I started to code a delay. (Well, that's done, now making an interface...) Any source in / any device out, adjustable delay as long as you want. It' quite easy to make, just store chunks of sound in a buffer, and read from that buffer. Only drawback, if you change the delay, it will skip parts of sound without any dissolve, in chunks of 1/100 of a second. No clue how that will sound yet. And yes, you need a computer with sound card, but it hardly will take resources, since it does not do anything except eating a tiny bit of memory to store the sound.
  5. Can't you post a 10 sec vid of a funny puking cat? That would be WAY more interesting.
  6. I know, wrong group, but nevertheless... I'm currently working on a video recorder for a MoCap studio, but perhaps it could be handy for you guys as well. At the moment it can: Record video from up to 8 Blackmagick devices (A cheap BM Mini Recorder is good enough for rock 'n roll.) Take sound from another device and marry it to the video on the fly. (So no need for SDI audio embedders.) Take LTC from another device or UDP for accurate TC. Apply some effects (currently flip / rotate as I work for MoCap, but I could add LUT's or alike.) Record in 'any' codec
  7. Have never worked with it, but since it's able to run Python, my code 'should' run on it. But why the hassle? Get a tablet running Win10 and run this: LTC reader It can act like a smart slate (Play clap sound and freeze display.)
  8. For Mp4 / Mov, only the start frame is written as 'tc', as a frame number. The rest is calculated based on the frame rate. (And yes, you can specify a different framerate for the TC if you like, but it 'should' not be an issue, it's just math...) You don't know me, but I'm a coder, not a sound guy. (I used to be a video editor, but have seen little off speed files.)
  9. Ah, my bad. I've overlooked this: But then the solution seems simple enough, set the cams to regular 29,97, and have post interpret as 23,976 (read, 1:1 frame relation.), as RunAndGun mentioned. Any half decent NLE can do this. Or am I still missing something? Having said this, if you can manage to put 23.976 LTC on an audio track, my LTC_convert can probably set 'correct' TC's on the files. (And if not, send me testclips and I'll make it work...)
  10. I totally don't get this. This is NOT shooting slomo with an off speed, this is a speed change in post with a 1:1 frame relation. (And yes, that results in a 'slomo', since the frame duration is stretched, but I consider this 'pull down', as 29,97 is NOT an 'off' speed.) Are both set to drop / non drop alike? If not, that's your problem. Then, depending on how smart Post is, how is the new TC calculation done? If they are in sync in 29,97, they also should be in 23,976
  11. Hi all, Since some (well, a lot) of you are responsible for Timecode: QT change has had a major update. It is no longer dependent on QuickTime being installed, and 64 bits (big sur / Catalina compatible.) And it now works also on Mp4 and BRAW files. Beside that, I've recently added an option to offload cards and set TC based on system time, but with a non-drop option. This was done per feature request from Top Gear USA. The logic behind it: They shoot 23,976, but have a couple of drones with no TC nor sound input. Thus the sound guy jams all cams, and the drones get thei
  12. Whom's? If you mean my software, you have to be a tad more specific, as I can't mind read over this distance. Bouke
  13. Hi Nick, If you toy with LiveLog, keep in mind that it was intended to log with minimum effort, hence the customizable comments / shortcuts. I've used the previous version myself for logging just markers / comments in very long lectures, where I was busy controlling and switching 2 cams / powerpoint, so not much time for writing notes. (I had to post myself, and did not want to go trough the whole shebang again.) But that was with a Avid Marker TXT files. Now the same client is going to record the lectures themselves (the local university), and I've build a lot of stuff in to accomm
  14. Speaking of, have a look at this: https://www.videotoolshed.com/product/livelog/ (I did not (yet) build in a 'sound report' option, but that would be a breeze.) And that reminds me, did you ever toy with the video slave mode of my LTC reader?
×
×
  • Create New...