|
|||||||||
|
Thread Tools | Search this Thread |
March 4th, 2010, 03:27 PM | #1 |
Regular Crew
Join Date: Nov 2007
Location: Colorado Springs, CO
Posts: 65
|
more notes on nanoFlash beta 1.5.31 / XDR beta 1.5.25
Hi,
Here is a summary of what we've found regarding beta 1.5.31 : a couple of the features, new features in particular, have some small hang-ups we are addressing: 1) Crank function (Video->Crank) : we've got a bug in there which prevents importing of cranked MXF footage, 50 Mbit and above, from being imported or properly displayed into most Pc based NLE's. This will be fixed for the subsequent beta release. 2) Video-> Record PSF>Progressive : If you are recording 720p, do not turn on this setting. We've got a bug there (in the beta release only) which throws off the 720p recording if Record PSF>Progressive is on. Also being fixed. In 1080p or 1080i this setting works fine without any problem in beta release. 3) System->Trigger->Emb/LTC Timecode Trigger: as discussed in another thread, in the beta release we only trigger if the increasing timecode is greater than last recorded timecode, to minimize unexpected recordings from playing back SxS cards from the camera, etc. In the next release, this will be a separate menu option. Timecode trigger will always trigger with increasing timecode. We are adding the trigger "TC > Last TC" option which will only trigger if the increasing timecode is greater than last recorded timecode. 4) Standard def MXF files: in the beta release, audio channel 1 is hacked up for our SD MXF files (only). This is being fixed. Also we still lack compatibility with Sony XDCAM Optical equipment in standard def. We are chasing this down as well. 5) Playback of Quicktime files (from nanoFlash) can have slight pixelation (in beta release only) . From a computer there is no problem with the video, only when playing from nanoFlash. Also being addressed. Don't have a specific release date for the next beta but we're getting closer. Additionally, let me add a few points to consider when using the crank mode, as it can be a little tricky: Crank [ ] [Recorded Frame Rate] [Crank Frame Rate] Allows frame rate overcrank / undercrank to provide slow motion / fast motion effects. The recorded format corresponds to the incoming video format – for example, if 720p60 is the incoming format, and recorded rate is set to 24, the recorded format will be 720p24. In this example, if the crank rate is set to 60 then this provides a 2.5x slow motion effect. Recorded Rate (1st crank setting): 24, 25, 30, 50, or 60. ***Can not exceed incoming video frame rate ***. Crank Rate(2nd crank setting): Frames per second to preserve from the incoming video: 1 to 60. *** Can not exceed incoming video frame rate ***. > Crank is I-Frame only recording, and the audio is not for use in this mode, only video. > In Crank mode, incoming 720p60 can only be used with 60, 30, or 24 recorded rates (and 1080p30 with 30 or 24 recorded rates) . > Incoming 720p50 can only be used with 50 or 25 recorded rates (and 1080p25 with 25 only). > Press right or left arrows during record to dynamically adjust crank rate. > The bit rate of cranked recording is based on the incoming video frame rate. For example, a 720p60 incoming signal @ 280 Mbit will allocate the 280 Mbit across every 60 frames, regardless of the Record Rate / Crank Rate settings. ( Note that this is constrasted with other modes such as pulldown removal. In pulldown removal, @ 280 Mbit, a 720p60 (or 1080i60) signal is brought to 24 frames per second, and the 280 Mbits are allocated across the 24 frames per second. ) > 720p24 / 25 / 30 can not be played out of the nanoFlash at this time. > Do not use Crank mode in combination with Pre-Record Buffer (System->PreBuffer), Time-Lapse, 720p60->30/50->25 (coming in next beta, cuts 720p frame rate in half by throwing out every other frame), or 3:2 Pulldown Removal. Tommy Schell |
| ||||||
|
|