Jump to content

pscottm

Members
  • Posts

    158
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by pscottm

  1. unshifted >> and << controls were mentioned a few posts back. they dont work unshifted. in my opinion, this is an advantage for anyone who uses the record button unshifted and would like to keep PFL unshifted at tbe same time. ie, boom in one hand, record/stop/pfl w the other.
  2. thanks jack, i guess i came to the same conclusion. i'm sure i'll figure out a way to work w this. all transport schemes aside, seems odd that there isn't a folder browser window of some sort to make it easier to double check things that have already been recorded.
  3. i'm getting the hang of mine too. so far my experience has been in parallel w bernie's. i'm impressed w the sound and overall layout but still figuring things out too. for instance.. i like having the transport controls 'unshifted' for one-handed record/stop control, and appreciate the fact that PFL remains 'on top' while recording 'unshifted', but i cant seem to operate the >> and << transport controls when unshifted. am i missing something?
  4. i have a couple of these and love them. very well made and durable. http://www.rivbike.com/product-p/basssl.htm
  5. i'll see if i can get ed to chime in on this.. he wrote all the code for jumpstart and i'm not sure how much architectural info he wants to give away.
  6. hi nick, i worked w ed to develop Jumpstart LTC and just wanted to let you know that the app does not rely on iphone time or any other network time to derive its code. as a result, the TC from iphone running jumpstart is surprisingly accurate and can run for several hours before dropping a frame. So you really can walk from device to device to load TC without having to worry about frame-accuracy issues.
  7. yes you are correct! I didn't know this til now but the G3 line input pin is different than G2 line input. So the BNC-to-mini cable i made for taking TC from camera and sending to line input of G2 goes nowhere when connected to a G3.. but the square wave is so hell-bent it makes it thru anyway, just too weak for using w the wrong cable. that explains it. thanks!
  8. i have used TC w my 552 for auto-load situations and can offer a few observations. yes the 552 needs a healthy TC level to be read so i would be wary of sending a giant square wave down a multicore snake w the audio. as for wireless TC hop, the sennheiser g2 works great. the g3 does not work at all, it doesn't have enough signal to push the TC w enough level for the 552 to read it. i'm sure the g3 units are fine for other uses but for TC i find the g3's line driver is just too weak.
  9. i just did a shoot w a sony 900 and preferred the zax Rx's outputs set to mic level and 900 cam XLRs also set to mic level.
  10. the short (12") stereo mini-to-mini i got from radioshack works fine.
  11. it's not a slate, it's not a clock. it's a simple way to load timecode start-time and user bits into a TC device. like setting TC on a zaxcom zfr100 to time-of-day. i plug the phone into the zax TC input w a short mini-to-mini cable, hit 'start' on the phone. the zax jams automatically, unplug the phone and get to work as usual. then usually jam the slate from the recorder. i think it's a great app for this purpose, which if i'm not mistaken, is all it's really designed for.
  12. indeed, it clarifies things considerably.. thank you, john, for taking the time. -scott
  13. much of this discussion relates to FCP setup problems.. what about avid? i'm working on a 5d shoot for the first time soon and i'm confused about which TC and sample rate to use. the camera shoots 30, the editor told me the avid will run at 29.97, so which should i use? i'll be using a smart slate.. and since avid can interpret TC from a video clip's audio, i'm also considering sending TC to the 5d's audio input via g2. would this be more advantageous than scratch audio? regarding TC and sample rate, my first guess would be to roll TC at 30, record @ 48,048 and force-stamp the files @ 48. but then i think maybe 29.97/48 would be better. i'm hoping to do a test with the camera but the chances are iffy.. any thoughts or insight on which way to go? many thanks. -scott
×
×
  • Create New...