Jump to content

nickreich

Members
  • Content count

    228
  • Joined

  • Last visited

About nickreich

  • Rank
    Hero Member
  • Birthday January 1

Profile Information

  • Location
    Australia
  • Interested in Sound for Picture
    Yes
  • About
    I do Sound For Picture and Location Recording - primarily for projects involving Theatre, Live Performance or Live Speaking events. Projects range from full-length films of Theatre and Opera shows, through to EPK/TVC shoots, Documentary and Streaming.

Recent Profile Visitors

1,767 profile views
  1. nickreich

    Sennheiser / Zax Lemo - Line Socket

    Thanks for that, I'll look it up.
  2. Has anyone sourced a Line Socket (to go on a cable rather than a panel) that mates with the Lemo connector used on mics wired for pro-series Sennheiser, Zaxcom, or Lectro SSM transmitters? Even Lemo's online tech support seem confused by which model matches the keyways etc. If you've found one that works, can you please share the model number? I need to make some adapters for mics wired for Senn Lemo, to plug into Lectrosonics PDRs. I can't swap or re-wire the mics. I've seen the Kortwitch solid-body adapters that Gotham sells, they work but the overall length of the plug plus adapter is a problem sticking out the top of the pack, so I'd prefer to make adapters with an inch of cable in between so they can fold back down the side of the TX. Thanks, nick
  3. nickreich

    Alexa Mini audio menu

    There's certainly a thing with old vs new versions of the Audio hardware board within an Arri Amira behaving differently, no matter what the firmware. Various menu items are greyed out on an Amira with the old board. I've never seen it mentioned, but maybe there are some differently-spec'd early-issue Minis out there, perhaps with different Lemo wiring. I DID see something recently on the Arri user forum about the Mini always recording 5 tracks of audio, with only two having program on them, presumed to be a hangover in shared firmware from the Amira, which can record 4 inputs plus 'voice notes' from a Bluetooth headset. I'd never heard of that before.
  4. nickreich

    Alexa Mini audio menu

    yes, that's what I meant - I don't believe there is a function in the Alexa Mini to merge or sum Left and Right inputs. There is no problem with pushing two channels of line level audio into the lemo connector - my usual music video-style workflow has guide audio on one channel and playback timecode on the other. Never had any complaints of crosstalk. Assuming the channels were separate going into the Alexa, I'm wondering if the issue has happened in Post or in transcoding before it got to Editorial?
  5. nickreich

    Alexa Mini audio menu

    I work with Minis quite frequently and I'm not aware of a menu setting that could do this (unless it's been added in. recent firmware update). The audio options in an Alexa Mini are quite basic, to say the least. I'm wondering if they were recording on the in-camera cfast card, or using an external recorder which might be the issue? Otherwise, was it a basic passive A-Box, or one of the little 2-channel active preamp boxes now available for the mini and quite popular with the Documentary folks? They might have track selection / mixing depending on the brand - pretty sure the Beachtek one does.
  6. nickreich

    Plug for Reaper

    wow - an echo from 2015! I do mainly recording of Concerts and Musical Theatre, both for Cast albums and filming for either full cinema 'streaming' or TV commercials and the like, and also a lot of Broadcast OBs for awards shows, where we record the rehearsals for finessing mixing before the live show. Because most live consoles at the larger end use MADI or similar in blocks of 64 channels, once the show tips over the 128 channel point into a third stage rack, they tend to fill the next one pretty quick with alternate mics, backups or whatever.
  7. nickreich

    MixPre 3 & RODE SmartLav+ not compatible really?

    so you have the SC3 adapter to convert the iPhone TRRS connector on the smartlav to a more typical TRS connector? The 3.5mm TRS connector on the side of the Mixpre 3 can be switched to 4 different uses. In the 'Input' menu in either Basic or Advanced mode, you can choose if it's in MIC mode (the one you want - provides plug-in power for the mic), LINE mode (for a stereo line level input) or CAMERA mode, for monitoring back from a camera but not recording it. The fourth use for the 3.5mm input is to get Timecode into the device. This is set in the same menu but only visible in Advanced mode. It's conceivable that setting might stick if you had it set then switched back to Basic mode, where it's not visible. Maybe check that out?
  8. nickreich

    Marry takes on 664

    yes, Video Toolshed BWF Sequencer. Will join non-contiguous takes and fill in the gaps with silence. Bouke wrote it for me to create single files from a half-day's shooting to hand off to Music staff. The timecode is still correct so they can give timecoded notes. It's here: https://www.videotoolshed.com/product/bwfsequencer/ Still in Beta, so it shuts down each time you do a set (demo restriction) but he can unlock it for you if you like it.
  9. nickreich

    Microdot on transmitter

    Sennheiser used these for years last century, on the 2012 transmitter (and possibly others). Using them heavily in Theatre applications, we found them to be quite reliable IF you added a small rubber O-ring around the connector for the male Microdot on the mic cable to tighten up against - otherwise they had a habit of coming loose, generating nasty pops in the audio. DPA (B&K at the time) supplied a little rubber gripper tool so you could get them tighter with your fingers, but we found the O-Ring to be a better solution. The DPA connector adapters from Microdot to other types have the same issue. I wouldn't go back to them on a TX by choice, though.
  10. nickreich

    time code tools, what to buy. (Ambient radio link)

    Hi Alidav, I think some of the systems being suggested above are too complicated for your needs. Basically, most users and manufacturers have moved away from directly transmitting Timecode over a radio link, as it is less reliable than having an accurate generator attached to each camera. You can get radio drop-outs. There are of course two ways timecode can be used on set - continuous timecode, often set to time-of-day, or "Rec Run" timecode, used less often nowdays, but only really for a single camera and a recorder, where the timecode starts and stops with the camera. For Continuous Timecode (or Time of Day) - which is what you'd need if there were two or more cameras anyway - all you really need at the basic level is two TC generator boxes for the camera, and use your Sound Devices 664 as the TC Master. Any of the currently available boxes will work fine - Tentacle Sync, Timecode Systems, Ambient's many products (including the Nano), and several other manufacturers. You simply jam-sync each box to the TC coming out of the 664, and put them on the cameras. Depending on the brand of the TC box, you might want to re-jam at lunchtime, or leave them to run all day. Ambient and Tentacle both have good videos showing this process. The tricky part is knowing how to set every brand of camera to lock to their TC box, and having the correct cables to link the two, but that's the same as using the TC radio link boxes you are used to. Some of the current boxes have a wireless network facility - this is different to the old TC radio links, as the wireless is used to simply jam-sync all the boxes (once or every few seconds, depending on manufacturer) - if the wireless drops out, there is no problem with the TC coming out of the boxes, and if one cameras jumps in a car and goes far away, it still gets TC. With those 'networked' devices, there's an advantage in having one of the boxes attached to your 664 as well, as it removes the need to jam one of the camera boxes to the 664 with a cable (which will then jam all the others over the 'network'). Please note that with the Ambient system, you do not require a 'Master Lockit' - even a Nano can be the 'network master' - the Master Lockit just gives you advanced control and Metadata functions you may not need for Documentary work. In the other, less likely case of using "Rec Run timecode" that starts and stops with the camera - some of the manufacturers still allow for this. Ambient for example, allow all their TC boxes to operate in "TRX mode", which to the user works in the same way as the old TC radio link boxes you have used. TC goes in to one box, and comes out of another one (or many) - and will start and stop as the source does. It is really using the wireless jamming network (they call C-Link) to start and stop the TC generators in each box - so it is still a bit more reliable than the old radio link system (which is why Ambient have discontinued them).
  11. nickreich

    Absolute UTC-based Timecode?

    I remember reading several articles about Ben Osmo's team on Mad Max Fury Road using several Ambient ACC501 Master Controllers with GPS Modules to jam their Lockits each day - as there were several shooting unit bases widely situated in the desert they started from each day, but may have ended up shooting the same action. I understood this to be a kind of GPS Time Of Day. The roll across midnight problem can be easily fixed with a standard 'time zone' offset. My concern with GNSS modules in individual TC Boxes is their ability to actually see a satellite signal in many shooting environments (ie: indoors) or getting desensitised by strong RF fields from other gear on the cameras like Video Transmitters and such. In a real on-set environment, even getting the time to take them outside to 'see a satellite' after power-up at the start of the day, before putting them on the cameras, can be a challenge.
  12. I do mainly large track-count recording (64 channels and over), mainly MADI through a variety of RME and DiGiGrid interfaces, and use Boom Recorder, Reaper and ProTools. Firstly as caleymw says, I've also heard that RME admit the UFX+ can only reach full track count reliably with the Thunderbolt connection, so try that first. I happily do 194 channels from a RME MADI FX card in a Thunderbolt chassis to a MacBook Pro a few years older than yours, recording to a single SSD for hours. I've been a Boom Recorder user since the early days, and have to say while it in theory can do 256 channels now, I haven't had reliable luck with it over about 40 channels and now call 32 channels my limit with it. I've tried working it through with Take Vos who wrote it, to no avail. Any more than 32 tracks, I use Reaper (as Pro Tools is limited to 32 chans of non-avid hardware). I've also tried Nuendo, Nuendo Live, Waves Tracks Live (which is just a skinned version of Ardour) and others, and Reaper is by far the most solid. I note you say "65 channels, 130 Files, 1 Folder" - why are you recording two files per track?
  13. Probably a bit OT here, but has anyone come across a Mac app that works with quicktime video files similar to the way Wave Agent creates sound reports from a folder of BWAVs? I'd like to dump a folder of h.264 Quicktime .mov files in it and end up with a list of the file names, and at least the timecode in and out points from the quicktime TC track - preferably in .csv format. Cheers, nick.
  14. nickreich

    Time code audio and video issue, any help appreciated

    So with the scientific/logging USB interface you are using, as with most more typical 'musician' USB interfaces, the interface's internal clock is the source of timing for the computer doing the recording. It has a proprietary sync system so you can link multiple units for multi-channel logging, but this does not seem at initial glance to be able to accept an industry-standard sync signal such as Wordclock, and as Bash notes - the available samplerates do not include those typically used in the film / music industries. This makes any suggestion of using wordclock / genlock between the camera and audio recorder impractical - although I'd contact Avisoft for comment. I note in their LTC tech note they warn of a possible DRIFT for the reasons I've outlined of somewhere in the vicinity of 300ms (0.3 sec) per 10 mins recording time - certainly in the ballpark of what I'd expect of decent camera and audio gear running un-sync'd (timecode or not). If the drift is greatly more than that, then Bash's suggestion that Premiere Pro is incorrectly assuming the audio is a particular samplerate, and playing it as such, may be a cause. However, my reading of your workflow description is that you are not actually importing the audio into the video editing software - you are simply using the timecode display on the video software to then go find a matching audio event to investigate, using the timecode display in the Avisoft playback application - rather than trying to play them in sync? Here's where another complication raises it's head. I assume that the Avisoft recorder software will happily play back audio through the computer's headphone socket without the recording interface attached. In that case, you need to know how the software handles it's timecode display on playback. Is is reading a recorded timecode track in real-time, or doing what most film-industry recorders do, and reading a start time stamp at the head of the file, then extrapolating based on the sample count from there. If it's the latter, the stability and accuracy of the timing 'clock' generated by the computer will always be different to that generated by the USB audio interface when plugged in. If you have the interface, and the software will play back with it connected, maybe try that, and see if there's a difference in the TC location of an easily-locatable event towards the end of a long recording. These scientific logging recorders are something most of us here don't come across. The KiPro Mini video recorder will be getting it's sync from the Camera via the SDI or HDMI signal carrying the pictures, so camera and KiPro can be considered as a single unit. If that camera happens to be a DSLR stills-type camera, don't expect much in the way of stability / accuracy from it's internal clock either.
  15. nickreich

    Time code audio and video issue, any help appreciated

    The Timecode coming into each device (video and audio) isn't actually labelling EACH frame - the device just looks at it at the exact moment a recording is started, reads the time data (in the format Hours:Minutes:Seconds:Frames, repeating as many times a second as suggested by the frame-rate you chose to use) and timestamps the file with that as it's start time. The vast majority of modern file-base recorders never look at the incoming timecode again during the recording of that take - whatever's playing them back just extrapolates from the start time. It's like the driver and conductor of a train both setting their watches to the station clock when they leave LA, then writing down their arrival time in NYC from their watches - the numbers will probably be different. Note that in the 'olden days' of linear recording media (ie Tape and actual Film), things were different - older texts can add to the confusion here. To give any more advice than we have already done would need more specific information about your setup - we know the KiPro Mini on the video side, but what specifically are you recording the sound on - and what editing software are you trying to combine them with?
×