720p 59.94/60 to SD

Hiya,
I've got a couple QTs encoded with DVCPro HD 720960 codecs. The timebase is 59.94 i believe.
Anyhow, i'm building out a SD QT for web/dvd and the HD content is looking worse than the SD stuff.
What is a good setting to convert this media to SD?
cheers

When converting from DVCPRO HD 720/60p to 10bit SD... Will I need to make any adjustments to the frame size as the aspect is different. (Crop, Letterbox??)

Similar Messages

  • [SOLVED] Can't play H.264 (720P) on Mplayer

    The title says it all.
    This is the output of mplayer (using umplayer/smplayer)
    /usr/bin/mplayer2 -noquiet -v -nofs -nomouseinput -vc coreserve, -lavdopts skiploopfilter=all -sub-fuzziness 1 -identify -slave -vo gl:yuv=2:force-pbo -ao alsa -nokeepaspect -framedrop -dr -double -input nodefault-bindings:conf=/dev/null -nostop-xscreensaver -wid 35651627 -monitorpixelaspect 1 -noass -subfont-autoscale 3 -subfont-text-scale 2.5 -subcp enca:es:ISO-8859-9 -subpos 100 -volume 16 -cache 2048 -osdlevel 0 -idx -vf-add yadif=1 -vf-add pp -autoq 6 -vf-add screenshot -noslices -channels 2 -af scaletempo -softvol -softvol-max 110 -aspect 4:3 /files/Video/Movies/Mean.Girls.2004.BluRay.720p.H264.mp4
    MPlayer SVN-r36285-4.8.0 (C) 2000-2013 MPlayer Team
    CPU vendor name: GenuineIntel max cpuid level: 13
    CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (Family: 6, Model: 58, Stepping: 9)
    extended cpuid-level: 8
    extended cache-info: 16801856
    Detected cache-line size is 64 bytes
    CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNowExt: 0 SSE: 1 SSE2: 1 SSE3: 1 SSSE3: 1 SSE4: 1 SSE4.2: 1 AVX: 1
    Compiled with runtime CPU detection.
    get_path('codecs.conf') -> '/home/axelectrik/.mplayer/codecs.conf'
    Reading optional codecs config file /home/axelectrik/.mplayer/codecs.conf: No such file or directory
    Reading optional codecs config file /etc/mplayer/codecs.conf: 205 audio & 424 video codecs
    init_freetype
    Using MMX (with tiny bit MMX2) Optimized OnScreenDisplay
    get_path('fonts') -> '/home/axelectrik/.mplayer/fonts'
    Configuration: --prefix=/usr --enable-runtime-cpudetection --disable-gui --disable-arts --disable-liblzo --disable-speex --disable-openal --disable-libdv --disable-musepack --disable-esd --disable-mga --disable-ass-internal --disable-cdparanoia --enable-xvmc --enable-radio --enable-radio-capture --language=all --confdir=/etc/mplayer
    CommandLine: '-noquiet' '-v' '-nofs' '-nomouseinput' '-vc' 'coreserve,' '-lavdopts' 'skiploopfilter=all' '-sub-fuzziness' '1' '-identify' '-slave' '-vo' 'gl:yuv=2:force-pbo' '-ao' 'alsa' '-nokeepaspect' '-framedrop' '-dr' '-double' '-input' 'nodefault-bindings:conf=/dev/null' '-nostop-xscreensaver' '-wid' '35651627' '-monitorpixelaspect' '1' '-noass' '-subfont-autoscale' '3' '-subfont-text-scale' '2.5' '-subcp' 'enca:es:ISO-8859-9' '-subpos' '100' '-volume' '16' '-cache' '2048' '-osdlevel' '0' '-idx' '-vf-add' 'yadif=1' '-vf-add' 'pp' '-autoq' '6' '-vf-add' 'screenshot' '-noslices' '-channels' '2' '-af' 'scaletempo' '-softvol' '-softvol-max' '110' '-aspect' '4:3' '' '/files/Video/Movies/Mean.Girls.2004.BluRay.720p.H264.mp4'
    Using nanosleep() timing
    Terminal type `unknown' is not defined.
    Parsing input config file /dev/null
    Input config file /dev/null parsed: 0 binds
    Setting up LIRC support...
    mplayer: could not connect to socket
    mplayer: No such file or directory
    Failed to open LIRC support. You will not be able to use your remote control.
    get_path('.conf') -> '/home/axelectrik/.mplayer/.conf'
    Playing .
    get_path('sub/') -> '/home/axelectrik/.mplayer/sub/'
    File not found: ''
    Failed to open .
    get_path('Mean.Girls.2004.BluRay.720p.H264.mp4.conf') -> '/home/axelectrik/.mplayer/Mean.Girls.2004.BluRay.720p.H264.mp4.conf'
    Playing /files/Video/Movies/Mean.Girls.2004.BluRay.720p.H264.mp4.
    get_path('sub/') -> '/home/axelectrik/.mplayer/sub/'
    [file] File size is 875863037 bytes
    STREAM: [file] /files/Video/Movies/Mean.Girls.2004.BluRay.720p.H264.mp4
    STREAM: Description: File
    STREAM: Author: Albeu
    STREAM: Comment: based on the code from ??? (probably Arpi)
    CACHE_PRE_INIT: 0 [0] 0 pre:419430 eof:0
    Cache fill: 0.00% (0 bytes)
    libavformat version 55.7.100 (internal)
    Configuration: --enable-gpl --enable-postproc
    LAVF_check: QuickTime / MOV
    libavformat file format detected.
    [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f4745215900]ISO: File Type Major Brand: M4A
    [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f4745215900]File position before avformat_find_stream_info() is 875863037
    [h264 @ 0x7f4745223040]no picture
    [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f4745215900]All info found
    [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f4745215900]File position after avformat_find_stream_info() is 2773137
    ==> Found audio stream: 0
    ID_AUDIO_ID=0
    ======= WAVE Format =======
    Format Tag: 20557 (0x504D)
    Channels: 2
    Samplerate: 48000
    avg byte/sec: 8069
    Block align: 1
    bits/sample: 16
    cbSize: 5
    Unknown extra header dump: [11] [90] [56] [e5] [0]
    ==========================================================================
    [lavf] stream 0: audio (aac), -aid 0, -alang und
    ==> Found video stream: 1
    ID_VIDEO_ID=0
    ======= VIDEO Format ======
    biSize 201
    biWidth 1280
    biHeight 720
    biPlanes 1
    biBitCount 24
    biCompression 875967048='H264'
    biSizeImage 2764800
    Unknown extra header dump: [1] [64] [0] [29] [fe] [e1] [0] [18] [67] [64] [0] [29] [ac] [d9] [80] [50] [5] [bb] [1] [10] [0] [19] [74] [f0] [4] [c4] [b4] [8] [f1] [83] [19] [a0] [1] [0] [7e] [68] [e9] [7b] [cf] [8] [47] [10] [a3] [84] [44] [85] [6] [d] [5] [10] [61] [8] [8] [82] [2] [14] [28] [14] [85] [41] [50] [50] [2a] [4] [68] [8] [4] [41] [a2] [88] [51] [6] [9c] [20] [63] [85] [21] [a8] [50] [90] [c0] [81] [23] [6] [46] [82] [40] [a0] [54] [16] [41] [63] [15] [31] [48] [4e] [29] [a6] [85] [15] [59] [11] [51] [a] [c8] [63] [cd] [3c] [c9] [90] [c7] [2a] [21] [84] [44] [9c] [40] [c1] [2] [46] [84] [2] [10] [88] [50] [60] [d0] [c4] [3d] [88] [91] [a4] [ad] [24] [da] [4a] [da] [49] [36] [c8] [91] [25] [6c] [84] [21] [a] [52] [98] [84] [94] [a6] [21] [a] [51] [6] [9c] [60] [81] [21] [8] [4b]
    ===========================
    [lavf] stream 1: video (h264), -vid 0
    LAVF: 1 audio and 1 video streams found
    LAVF: build 3606372
    VIDEO: [H264] 1280x720 24bpp 23.976 fps 1175.4 kbps (143.5 kbyte/s)
    [V] filefmt:44 fourcc:0x34363248 size:1280x720 fps:23.976 ftime:=0.0417
    Clip info:
    major_brand: M4A
    ID_CLIP_INFO_NAME0=major_brand
    ID_CLIP_INFO_VALUE0=M4A
    minor_version: 0
    ID_CLIP_INFO_NAME1=minor_version
    ID_CLIP_INFO_VALUE1=0
    compatible_brands: isomavc1M4A mp42
    ID_CLIP_INFO_NAME2=compatible_brands
    ID_CLIP_INFO_VALUE2=isomavc1M4A mp42
    creation_time: 2012-04-17 19:31:49
    ID_CLIP_INFO_NAME3=creation_time
    ID_CLIP_INFO_VALUE3=2012-04-17 19:31:49
    ID_CLIP_INFO_N=4
    Load subtitles in /files/Video/Movies/
    get_path('sub/') -> '/home/axelectrik/.mplayer/sub/'
    [file] File size is 127642 bytes
    STREAM: [file] /files/Video/Movies/Mean.Girls.2004.BluRay.720p.H264.eng.srt
    STREAM: Description: File
    STREAM: Author: Albeu
    STREAM: Comment: based on the code from ??? (probably Arpi)
    SUB: Detected subtitle file format: subviewer
    ENCA supported languages: be bg cs et hr hu lt lv pl ru sk sl uk zh __
    ENCA detection failed: fallback to ISO-8859-9
    SUB: opened iconv descriptor.
    SUB: closed iconv descriptor.
    SUB: Read 1642 subtitles, 0 bad line(s).
    ID_FILE_SUB_ID=0
    ID_FILE_SUB_FILENAME=/files/Video/Movies/Mean.Girls.2004.BluRay.720p.H264.eng.srt
    SUB: Added subtitle file (1): /files/Video/Movies/Mean.Girls.2004.BluRay.720p.H264.eng.srt
    ID_FILENAME=/files/Video/Movies/Mean.Girls.2004.BluRay.720p.H264.mp4
    ID_DEMUXER=lavfpref
    ID_VIDEO_FORMAT=H264
    ID_VIDEO_BITRATE=1175392
    ID_VIDEO_WIDTH=1280
    ID_VIDEO_HEIGHT=720
    ID_VIDEO_FPS=23.976
    ID_VIDEO_ASPECT=1.7778
    ID_START_TIME=0.08
    ID_LENGTH=5633.11
    ID_SEEKABLE=1
    ID_CHAPTERS=0
    Could not find a UTF-8 locale, some keys will not be handled.
    X11 opening display: :0.0
    vo: X11 color mask: FFFFFF (R:FF0000 G:FF00 B:FF)
    vo: X11 running at 1366x768 with depth 24 and 32 bpp (":0.0" => local display)
    [x11] Current fstype setting doesn't honour any X atoms
    [gl] using extended formats. Use -vo gl:nomanyfmts if playback fails.
    [gl] Using 0 as slice height (0 means image height).
    Opening video filter: [screenshot]
    Opening video filter: [pp]
    [screenshot] query(Planar YV12) -> 3
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=0, chromMode=0
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=2, chromMode=0
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=3, chromMode=0
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=3, chromMode=2
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=3, chromMode=3
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=7, chromMode=3
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=7, chromMode=7
    Opening video filter: [yadif=1]
    Opening video filter: [hqdn3d]
    Opening video filter: [pp=de]
    [hqdn3d] query(Planar YV12) -> 3
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=0, chromMode=0
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=2, chromMode=0
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=3, chromMode=0
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=3, chromMode=2
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=3, chromMode=3
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=7, chromMode=3
    pp: de
    pp: de::de
    pp: hb::hb
    pp: option: a
    pp: vb::vb
    pp: option: a
    pp: dr::dr
    pp: option: a
    pp: lumMode=7, chromMode=7
    ==========================================================================
    Forced video codec: coreserve
    Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
    libavcodec version 55.12.100 (internal)
    Configuration: --enable-gpl --enable-postproc
    INFO: libavcodec init OK!
    Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
    ==========================================================================
    ID_VIDEO_CODEC=ffh264
    [PP] Using external postprocessing filter, max q = 6.
    AutoQ: setting quality to 6.
    Audio: no sound
    Freeing 0 unused audio chunks.
    Starting playback...
    [ffmpeg] aspect_ratio: 0.000000
    [ffmpeg] aspect_ratio: 0.000000
    [h264 @ 0x7f4745223040]no picture
    ds_fill_buffer: EOF reached (stream: video)
    [ffmpeg] aspect_ratio: 1.777778
    VDec: vo config request - 1280 x 720 (preferred colorspace: Planar YV12)
    [PP] Using external postprocessing filter, max q = 6.
    Trying filter chain: pp hqdn3d yadif pp screenshot vo
    VDec: using Planar YV12 as output csp (no 0)
    Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
    ID_VIDEO_ASPECT=1.3333
    VO Config (1280x720->1280x960,flags=4,'MPlayer',0x32315659)
    REQ: flags=0x6CB7 req=0x0
    REQ: flags=0x6CB7 req=0x0
    REQ: flags=0x6CB7 req=0x0
    REQ: flags=0x64B7 req=0x0
    SwScaler: reducing / aligning filtersize 1 -> 4
    SwScaler: reducing / aligning filtersize 1 -> 4
    SwScaler: reducing / aligning filtersize 5 -> 4
    SwScaler: reducing / aligning filtersize 5 -> 4
    [swscaler @ 0x7f4745232a00]BICUBIC scaler, from yuv420p to rgb24 using MMXEXT
    [swscaler @ 0x7f4745232a00]1280x720 -> 1280x960
    [swscaler @ 0x7f4745232a00]lum srcW=1280 srcH=720 dstW=1280 dstH=960 xInc=65536 yInc=49152
    [swscaler @ 0x7f4745232a00]chr srcW=640 srcH=360 dstW=640 dstH=960 xInc=65536 yInc=24576
    REQ: flags=0x64B7 req=0x0
    VO: [gl] 1280x720 => 1280x960 Planar YV12 [zoom]
    VO: Description: OpenGL
    VO: Author: Reimar Doeffinger <[email protected]>
    [gl] GLX chose visual with ID 0x97
    X11 error: BadMatch (invalid parameter attributes)
    Type: 0, display: 0x7f4746d59fa0, resourceid: 5000001, serial: 2f
    Error code: 8, request code: 2, minor code: 0
    [gl] Settings after autodetection: ati-hack = 0, force-pbo = 1, rectangle = 0, yuv = 2, ycbcr = 0
    [gl] Creating 2048x1024 texture...
    [gl] Resize: 1078x606
    *** [pp] Exporting mp_image_t, 1280x720x12bpp YUV planar, 1382400 bytes
    *** [hqdn3d] Allocating mp_image_t, 1280x720x12bpp YUV planar, 1382400 bytes
    [postproc @ 0x7f4745210ae0]using npp filters 0x7/0x7
    *** [yadif] Allocating mp_image_t, 1280x720x12bpp YUV planar, 1382400 bytes
    ds_fill_buffer: EOF reached (stream: video)
    ds_fill_buffer: EOF reached (stream: video)
    ds_fill_buffer: EOF reached (stream: video)
    ds_fill_buffer: EOF reached (stream: video)
    ds_fill_buffer: EOF reached (stream: video)
    ds_fill_buffer: EOF reached (stream: video)
    ds_fill_buffer: EOF reached (stream: video)
    ds_fill_buffer: EOF reached (stream: video)
    EOF code: 1
    Uninit video: ffmpeg
    Drawn 0 frames, 0 using DR, DR refused 0
    vo: uninit ...
    Exiting... (End of file)
    ID_EXIT=EOF
    It works fine with VLC using the codec avc1 , so the fix might be to use coreavc codec with mplayer, unfortunately mplayer-coreavc-svn from AUR does not compile :S
    Thank you
    Last edited by axelectrik (2013-06-09 22:00:22)

    It actually worked!
    Can't see what was the problem with mplayer but now it plays perfectly
    Thank you!

  • Can't import HDV 720p from my Sony HDR HC1 camcorder to my FCP 5.0.1 help

    I have footage that was shot on a contractors JVC HDV camera at 720p. I play it in my Sony HDR HC1 and i can view it and it plays awesome. It even recognizes its 720p. But i try to import it into Final Cut Pro on my IMac G5 or powerbook G4 17inch and it can play the camera but not capture footage. I have FCP version 5.0.1 How can i get this video into my editing software ive tried it on imovie as well and cant import video but i can control the camera. Please help.
    Do i need to buy the updated FCP i noticed doing some research there is a FCP 5.1 now that i heard nothing about?
    Thanks for the help in advance.
    powerbook g4 17inch, powerbook G4 12inch, imac G5   Mac OS X (10.4.7)  

    Get a hold of the JVC camera the footage was shot with. When FCP 5.1.2 is released (this month), you'll actually be able to capture the footage directly... problem is that the JVC recording is short GOP, and FCP currently only supports LONG GOP... You will need to upgrade to capture the footage directly, or buy this: http://www.lumierehd.com But in any event, you'll need the JVC camera to capture it's recordings, now or in the future.
    JVC's iteration of HDV isn't the same as Sony's... that's the problem. PLUS FCP doesn't support any recordings of the JVC format except 1080i60 as of now. 5.1.2 will change that I believe. IBC was where this new update was announced I think, and you'll need to "cross grade" your FCP 5.0.x version to FCP 5.1. to get this update down the line... Yeah, I don't like the situation either, but there it is... Canon's HDV and JVC's HDV are very similar FWIW...
    Jerry

  • MacBook Pro mid-2010 15-inch Supports Monitor at 720p but not 1080p

    Hello all,
    Systems Specs:
    MacBook Pro (15-inch, Mid 2010)
    Processor: 2.53 GHz Intel Core i5
    Memory: 4 GB 1067 MHz DDR3
    Startup Disk: Macintosh HD
    Graphics: NVIDIA GeForce GT 330M 256 MB
    I am attempting to connect my MBP to a new Asus VE278Q, 27inch 1920x1080. I use a mini-display port to HDMI monoprice cable. I can connect at 720p and the display looks fine. When I switch to 1080p the monitor flickers and turns to snow within a few seconds. My parents' 2013 MBP, using the same cable, can connect to the monitor and display perfectly.
    The technical specs for a mid-2010 MBP say that it can support  "up to 2560 by 1600 pixels on an external display." It should be able to support this monitor easily. I have also tried to connect it to a Sony 1080p TV, where it registered as black screen.
    Does anyone have any idea what is going on? Is there something wrong with my graphics card?

    Hi stan,
    Read about it here:
    http://support.apple.com/kb/TS4088

  • Bad Picture Quality On SD Channels With HDMI And Panasonic VIERA 720p LCD HDTV

    I just bought a new Panasonic VIERA 32" 16:9 8ms 720p LCD HDTV TC-L32X1 for my in-laws when they finally had Verizon FIOS brought into their neighborhood last month.
    Install was by the Verizon tech using the HDMI cable I also had shipped to them.
    The HD channels quality is excellent, but the SD quality is smeared -- almost looks like an impressionist painting.
    It is not the TV -- the TV menus are crystal clear, as are the HD channels.
    And, it is not just the broadcast HD -- the DVR box menus are also smeared when viewing as SD channel, as is the guide and the pop up channel info.
    We've tried all the settings on the TV -- Zoom, 4:3, etc.
    The other TV (an older CRT) actually has better SD quality than the Panasonic.
    My research indicates we're not the only ones on FIOS with this problem. Someone suggested using the component hookup rather than HDMI?
    Other say that IMG 1.7 is supposed to solve the problem, that the SD quality was fine before IMG 1.6.
    Any suggestions, solutions, or updates?
    The picture is virtually unwatchable.
    Thank you!

    Here's a particularly relevant post if you don't want to wade through all the above links:
    (http://forums.verizon.com/t5/FiOS-TV-Technical-Assistance/bad-pq-on-std-def-channels/m-p/10917#M5540) -- second to last.
    "Re: bad pq on std.def. channels
    01-06-2009 03:55 PM
    Joe01880 - Being a new customer as of last October, I have never seen anything other than IMG 1.6.  My understanding from other posts is that before IMG 1.6, the SD PQ on an HD box was just fine.  I'm not sure what the complaints/gripes/begs were for IMG 1.6 but it seems to me that, if Verizon knows what changes were made, it should be straightforward to determine which changes caused a deterioration of the PQ.  I think it's been at least 6 months since the first complaints of poor PQ, so I don't really see how anyone can claim that Verizon is in danger of "rushing" an update to address this problem.  I also don't think that a forum topic, no matter how much it complains or gripes, will cause Verizon to rush.  I am much more worried that during a large portion of my 2 year contract that the issue won't be addressed at all, so I'm happy to add my voice to those complaining."

  • I am trying to connect my laptop to my TV. The computer flashes blue after I plug the cable in but the TV says there is no signal. I have a Mac Book Pro 2009 and a Samsung 32" Class (31.5" Diag.) 450 Series 720p LCD HDTV (2010 model)

    Hello,
    I am trying to connect my laptop to my TV. The computer flashes blue after I plug the cable in but the TV says there is no signal.
    I have a Mac Book Pro 2009 and a Samsung 32" Class (31.5" Diag.) 450 Series 720p LCD HDTV (2010 model).
    I am using a mini display port to VGA adapter. I have sucessfully hooked up boh devices but it stopped working after a handful of times. I was wondering if there is anything I can do to fix the problem or is my cable broken?

    Some things you can try.
    Startup Issues - Resolve
    Startup Issues - Resolve (2)

  • How to smooth text when using 720p HDTV as monitor?

    I know I'm not using the best choice for a Monitor, but want to tweak it the best I can.
    Sony Bravia BX 320, 720P TV as my monitor
    New Mac Mini bought yesterday
    1080P Display Setting in Mini's display profiles
    720P ibid
    Connected via HDMI
    Have tried tweaking around with different Mac Display profiles and color calibrations. Above look the best as far as resolution and picture when sitting far away from screen.
    Closer I get to screen, the more pixelated and crappy the text looks, which is really bad
    What are the tweakablle settings, both in the monitor and computer I would want to play with to smooth the text out as best as is possible given my monitor choice?
    What would be a better "TV" choice to use as a monitor for my Mini? I only run a Roku and OTA HDTV into the TV tuner.
    Is there a choice that looks good in both TV and Mini monitoring applications?
    Thanks so much.

    I have never used any of this, I have never needed to use it. I just know that the information is around and has been useful to others.
    I also saved this tutoial that I found once. Perhaps it can help you;
    SwitchResX Tutorial
    0. All of this is easier to do if you have a portable Mac, since you can configure the external display while viewing everything on the built-in display. You can do it with only the external display (your big TV, that is), but it's tedious.
    1. Get the proper cable to connect your Mac to the display (VGI, DVI, or DVI->HDMI, depending on your display's inputs; if you're using a portable Mac with only mini-DVI you'll need the adapter *and* a cable).
    2. Connect the display and turn on the Mac. Launch the SwitchResX Control application (if all you're doing is setting up a custom configuration, you don't need the preference pane and thus don't need APE either).
    3. In the SwitchResX Control application, select the display you want to configure in the "Settings of:" menu (if it isn't selected already) and click the "Display" tab. Then click the "Export DDC" button and select a location to save the file.
    4. Using the text editor of your choice (TextEdit works, or you may have a preference for something else) open that file you just exported. You should see at least one Monitor Description Block (mine has two, labeled Descriptor #0 and Descriptor #1). This should give you a starting point. Mine looks like this:
    Code:
        Descriptor #0 is Timing definition:
        Mode = 1920 x 540 @  60Hz
            H. Active...............1920 pixels
            H. Blanking.............280 pixels
            V. Active...............540 lines
            V. Blanking.............22 lines
            HSync Offset............88 pixels
            HSync Pulse Width.......44 pixels
            VSync Offset............2 lines
            VSync Pulse Width.......5 lines
            Pixel Clock.............74.25MHz
            Horizontal freq.........33.75kHz
            Vertical freq...........60.05Hz
            H Image Size............16mm
            V Image Size............9mm
            H Border................0 pixels
            V Border................0 lines
                Interlaced
                Sync: Digital separate with
                    * Positive vertical polarity
                    * Positive horizontal polarity
    Note that the Mode is described as 1920 x 540 @ 60Hz, interlaced. It's actually 1920 x 1080, interlaced. I'm not sure why the vertical resolution is half what it should be there, but that's an important detail to note. If yours looks like it's half what it should be, you'll have to double it below. Use your common sense here.
    The next step depends on what problem you need to solve. If you have a picture and you just need to adjust its position and/or size, you have the easier task and these instructions can help you. If you don't have a picture at all, the values provided by your display are invalid, and you'll have to do some research to find valid values (I can't help you find them). Search and/or ask on this forum, and also try Google.
    5. Click on the "Custom" tab in the SwitchResX Control app. Click the "+" button to create a new resolution. Select "Custom" in the menu at the top (as opposed to "Scaled"). Start by entering the values in the Monitor Description Block you exported and opened in a text editor. The thing to realize as you get started is that all the numbers interact with each other, and as you change one value the application will recalculate the others if they're affected by the change. At a given resolution, the number of horizontal pixels and the number of vertical lines in each box always have to add to the same totals, and you can get those values by adding the "Active" and "Blanking" values in the Monitor Timing Block. To stick with my display, the horizontal pixel values must add up to 2200 (1920 (H. Active) + 280 (H. Blanking)), and the vertical line values must add up to 1124 (2 * (540 (V. Active) + 22 (V. Blanking))). The horizontal and vertical scan rates are calculated using those total values and the pixel clock value.
    This is a very important concept to understand. With a constant pixel clock value and constant totals of Active + Blanking in both axes, the scan rates should also remain constant. If you have changed your active, porch, or sync width values and the scan rates don't add up, you won't get any picture. To use my display as an example again:
    Code:
    Pixel Clock 74.25 Mhz, Interlaced
                Horizontal      Vertical
    Active:     1920 pixels     1080 lines
    Frt. porch: 88 pixels       4 lines
    Sync width: 44 pixels       10 lines
    Back porch: 148 pixels      30 lines
    Scan rate:  33.75 kHz       60.05 Hz
    Note that 1920 + 88 + 44 + 148 = 2200, and 1080 + 4 + 10 + 30 = 1124.
    6a. Adjust the values to fit your display (heh). This is the trial-and-error portion of the task, and is also slightly counterintuitive. You can get an idea of the adjustments you need to make if you use DisplayConfigX to display an "Image Size Test" (in the "Test Screen" tab). It'd make life easier if that were built into SwitchResX, but anyway:
    If you need to shrink the visible area, decrease the Active value and increase the front or back porch values by the same amount. If you need to increase it, do the opposite. It helps to work incrementally (say, by multiples of 8) and save and test your work as you go along. Note that you may not actually need to restart the computer: I found that I could just unplug the HDMI cable from the back of my display and plug it back in, and the new settings would take effect. Remember to click "OK" (and not "Cancel") in the Timing Parameters window, then "Apply" in the main window, before you do this, or before you reboot. Otherwise your changes will be lost.
    The porch values are counterintuitive. The horizontal "front porch" is the right edge of the screen (not the left as you might expect); the vertical "front porch" is the bottom edge of the screen. To move the image to the right, decrease the horizontal front porch and increase the horizontal back porch; to move it to the left increase the front porch and decrease the back porch. To move the image up, increase the vertical front porch and decrease the back porch, to move it down, decrease the front porch and increase the back porch. Again, it helps to save and restart or disconnect/reconnect the display to test these adjustments. The "Quick change" buttons in the bottom right-hand corner of the Timing Parameters window will adjust the porches for you, but note that in older versions the buttons were reversed (down means up and left means right, if you catch my drift). That's been fixed in version 3.7.6, apparently.
    Also, remember as you adjust porch values that you shouldn't ever need to change the sync width.
    6b. You know how I said you might not need to restart the computer? That's not actually 100% true for some displays. When I boot my computer with the display connected, the image is shifted to one side. If I subsequently change resolutions in software or disconnect and reconnect the display, the image will shift back. I got around this problem by first coming up with a configuration that was properly aligned after such a switch. After I had that I rebooted and estimated how far the image was shifted to one side. I then adjusted the porch values, saved, rebooted, and tested again. I now have two configurations, one for "fresh boot" that's adjusted for that sideways shift, and one I can use if I've changed the resolution for some reason. After all that, my default settings are now:
    Code:
    Pixel Clock 74.25 Mhz, Interlaced
                Horizontal      Vertical
    Active:     1834 pixels     1024 lines
    Frt. porch: 120 pixels      40 lines
    Sync width: 44 pixels       10 lines
    Back porch: 202 pixels      50 lines
    Scan rate:  33.75 kHz       60.05 Hz
    Again, 1834 + 120 + 44 + 202 = 2200, and 1024 + 40 + 10 + 50 = 1124. The Pixel Clock and both scan rates are the same as I found in the DDC.
    Note also that if you have the same sideways shift problem, your two resolutions can't be identical (the system won't know which one to select). I made mine different by two pixels of horizontal resolution, which turns out to be rounded off in practice anyway (so one's 1832 x 1024, and the other's 1834 x 1024, with porch values adjusted accordingly, but they both look the same).
    At this point you should be able to align your desktop to your display by iterating through these steps, applying your changes, and either disconnecting and reconnecting the display or rebooting.
    7. If ever you go horribly wrong and go from having a misaligned picture to having no picture at all, you'll have to delete the override installed by SwitchResX. Boot the computer into Safe Mode, launch the SwitchResX Control app again, and click the "Factory settings" button, then the "Apply" button, and reboot.
    And as a preemptive strike: no, I probably don't own your display and don't know the numbers for it offhand, and my consulting rate is $45/hr (really!). 
    Copyright Fedward. All rights reserved, all wrongs reversed.

  • Choosing between 720p and 1080p on Mini connected to Sony HDTV (1920x1080)

    I have a late 2009 Mac Mini and a SONY HDTV and had no difficulties at all in hooking them up. I just connected the Mini Display Port to DVI connector which ships with the MAC Mini to a Belkin DVI to HDMI cable (also available from Apple Store) and connected the HDMI to my TV. I switched on the TV, selected the correct HDMI input, then switched on the Mac Mini and could see the picture immediately. I was missing the menu bar at the top so went to SYSTEM PREFERENCES and then DISPLAYS and the OPTIONS tab, and unselected OVERSCAN, and that gave me a perfect picture (slightly smaller than full screen but perfectly adequate as far as I'm concerned).
    By default my resoluton was set at 1080p (presumably the Mac detected that the native resolution of my TV is 1080p). The DISPLAYS box shows a number of resolution with a little TV screen icon beside them, as if suggesting those resolutions for use with the Sony. It shows 480i, 480p, 720p, 1080i and 1080p. There are also lots of others without TV icons beside them.
    The only problem I found is that 1080p made it quite difficult to read text on my screen, even though it's not very far away from the sofa. My eyesight is very good but I couldn't read the screen comfortably when surfing the net or even when changing settings etc. I swiiched, therefore, to 720p and this produces a very comfortable size of text for using the MAC.
    My question is whether it really makes such a big difference whether one chooses 720p or 1080p, as I really can't see much difference for playback of video from Hulu or other streaming websites. Even when I played a DVD movie from the Mac Mini superdrive, the difference in quality was hard to detect. I guess if I tried viewing Full 1080p HD material, there would be some difference, but how much of such material is available on the net anyway? I take it that switching between 720p and 1080p wouldn't cause any harm, if I chose to do so occasionally for watching any Full HD movies that I rip?
    Look forward to hearing views!

    Hi- I also picked up a mini a week ago, and have it hooked up to my Sony HDTV via HDMI, just as you. The same thing happened the first time I connected the mini to my tv- with overscan on, the top and bottom of the screen were cut off.
    The solution is to pick up your Sony remote, go to the onscreen menus, and make sure that 'full pixels' option is selected. When you do, the screen will be absolutely perfectly aligned.
    I mention this because while in overscan mode, I find that the Sony makes an absolutely beautiful screen, and text is quite easy to read, albeit a bit small.

  • Dv2630ea connected to tv , screen open tv shows 720p hd , closed it shows 1080i hd

    i dont really know the difference between 720p hd and 1080i hd however the 1080i hd is a lot smaller on my tv screen with a black border around it.
    is there anyway to get it to full screen on my telly?

    OK...That looks like a case of image scaling issue...
    On Nvidia Graphic card that can be custom by going to Nvidia Control Panel - > Video & Television - > Resize HDTV Desktop.
    Under 'When the desktop is displayed on my HDTV' select 'Resize HDTV Desktop' and click Resize Desktop. Check below Screenshot...
    Now on click Resize Desktop you will get below screen... Now move the slider on right and bottom of nvidia logo up-down or left-right till the 4 corner arrows line up to the screen edge...
    Note: above screenshot from latest nvidia driver. May change on older one...
    Although I am an HP employee, I am speaking for myself and not for HP.
    Make it easier for other people to find solutions, by marking my answer with 'Accept as Solution', if it solves your problem.
    Click on the BLUE KUDOS button on the left to say "Thanks"

  • How can I download both 720p and 1080p versions of TV shows and movies?

    I have iTunes set to download the 1080p versions of movies and TV shows, but I still have a 2nd generation Apple TV that can only show 720p. How can I setup iTunes to download both HD versions? It also seems that when I have iTunes in the Cloud turned on, it doesn't allow me to redownload any of my HD content again.
    I also need the 720p version because of the older versions of the iPod I still have.

    I ended up getting the proper response from iTunes Support. I forgot to share it with everyone else. Here is how you download both versions of the videos:
    iTunes only lets you download one version of a video at a time. As a work around, I would like you to try the following:
    - Download the 1080p version of the video first
    - Then remove the 1080p version of the video from your iTunes library and save it somewhere else on your computer.
    - Now that you have removed the 1080p version go to the iTunes > Preferences > Store
    - Change the HD version "when downloading HD videos, prefer."  to  720p
    - Go to purchase page, the 720p version should download.

  • Are you seeing a colour shift in 720p and 1080p h.264 slideshow exports?

    When I export video from Lightroom 3 (or 3.2), I see that 720p and 1080p output can be very different in colour from other resolutions. It's as if my display profile were being ignored when playing back those particular resolutions.
    Playback client: Apple's QuickTime Player X on Mac OS X 10.6.4. If I use VLC or QuickTime Player 7, colour is consistent across all export resolutions but is consistently wrong compared with the original photographs. (Again, it's as if the ICC display profile is being ignored.)
    Display profile: my display is profiled and the profile is an ICC v4 file but I can reproduce the issue with some v2 profiles, as well.
    AVC vs h.264
    One oddity (that might be a peculiarity of QuickTime Player) is that when I view the 720p and 1080p movies, and ask for information about codecs (command-i), QuickTime Player X tells me that these two movies use AVC encoding. For all the other sizes, it says claims h.264. My understanding is that these two are effectively the same thing; on the other hand, it's curious that the two sizes showing different colour from the rest are identified differently. And QuickTime Player 7 claims AVC for all resolutions and always gets the colour wrong.
    Is this just a QuickTime Player X bug? It gets colour right for all resolutions except 720p and 1080p, and provides a clue by saying the movie uses the AVC codec? Or is this an encoding issue?
    Other sizes are fine
    Exporting and playing back any other h.264 movie size, from 320 pixels right up to 960 pixels, provides perfectly acceptable colour in QuickTime Player X .There's a slight shift compared with the originals but nothing dramatic, and it's consistent across different sizes.
    Any thoughts? Can you reproduce the problem?
    I've tested this on a bunch of different Macs but they're all running 10.6.4.  Can anyone see this problem? Would anyone like to test on Windows and report back? The results seem to vary wildly depending on your display profile and how far it is from a canned profile so if you really want to be sure of seeing the differences, switch your display to "Wide Gamut RGB" for the playback test, then compare the 720p/1080p files with the rest, including the sRGB reference.
    Would anyone like to tell me I'm being a complete idiot and overlooking something blindingly obvious? I won't be upset.
    I was just about to post a note on the blog but thought I'd better post something here first. I'll probably ask readers to provide feedback here rather than on the site. I get the feeling that this issue won't be a big deal for most people.
    Some examples for download
    I have a zipped collection of single-image slideshows generated by Lightroom at each available resolution, together with a 960-pixel JPEG (sRGB) of that same image to act as a reference. You can download it here (5.9MB). For the moment, you'll probably have to ignore the URL that you see in the slideshows and in the Read Me file—it points to the blog post that I was preparing but which I haven't yet published. I'll do that next so anyone reading the blog will come here and post.
    Thanks in advance, and apologies if I'm being dumb about something.
    Update
    I've added a 720x480 file that shows the same problem and updated the URLs shown in the movies and the Read Me file.
    Message was edited by: Bahi Para

    Bahi,
    just to illustrate what mess this is, I tested for you on Leopard (10.5) and Snow Leopard (10.6) using the same wide gamut monitor. Here are two screenshots from that experiment. I converted the screenshots from my display profile to sRGB to show you what I see and scaled down 50% (this is a 30" behemoth). First Leopard.
    You see they are all the same, but different from the sRGB export you provided. The GB sticker is too blue and the tint on the car is wrong. I doubt anybody but a photographer would notice though.
    Next is Snow Leopard:
    Here the 320 pixel, the 480 pixel and the 960 pixel image are different from the 720 pixel, the 720p and the 1080p ones. Neither is strictly correct as they are all different from the sRGB display. This is consistent with their being no real color management, just gamma corrections and color space transforms (video is usually not stored as RGB but as YUV, necessitating a transform for display). Annoying, but not much you can do about it.
    Just doing some quick googling I came across many mentions of issues such as this. It clearly is just a big mess.

  • Does Frontrow/Quicktime upscale to 720p on TV?

    I have just bought a 42" TV.
    It has great reviews - but is apparently lacking in it's ability to de-interlace and upscale. So give it a good HD signal, it will provide a good HD picture.
    As I understand it - my mac will be sending a 720p signal (via DVI) anyway, so the strength or weakness of my TV will make no difference.
    Does Frontrow automatically upscale my source video? I've read somewhere that the video card might upscale automatically (I'm using a GeForce 8600M GT, on my MBP 2.2)
    I know Quicktime automatically de-interlaces. Are there any settings I need to change for upscaling?
    Is watching via VLC going to look better than Frontrow does? (I've read VLC upscales really well).
    Basically what do I do to get the best picture from rental movies and TV shows from my Mac? (pity we can't rent HD on a Mac!)

    you need to put the movie into itunes and it also needs to be in an appletv supported format.
    if the movie is 720p and is in appletv format, then yes it will stream as 720p to the appletv.

  • [Solved] After watching several youtube html5 720p videos, Firefox (version 33) display or screen turns black and aero transparency in windows 7 turns opaque.

    Hello ! I just want to share something familiar with that black display or screen occurs for some people. When I watch youtube videos, I used to watch them in html5 720p videos (not flash videos, https://www.youtube.com/html5 ). I upgraded firefox to version 33. No black display when I used it. Randomly and after watching several html5 videos on youtube, aero transparency in my windows 7 turns opaque and firefox display goes all black. Firefox doesn't respond at any command. I need to kill his process in task manager in order to close it. When I open firefox again, normal display goes. To relaunch aero transparency in windows 7, I need to restart the service whose name is, I think, "Desktop Window Manager Session Manager". I use windows 7 in french and the service name is "Gestionnaire de sessions de Gestionnaire de fenetrage".
    To solve this, I upgraded my graphic driver but this didn't work. I tried to put "layers.offmainthreadcomposition.enabled" to false in "about:config" menu. No random black display but some html elements turned black for some seconds or definitely when firefox rendered web pages. I tried to uncheck "Use hardware acceleration when available" in options menu. No random black display but html5 720p videos didn't play smoothly.
    Then, I chose to watch youtube 720p videos again with flash player and no random black display and html5 720p videos played normally.
    Here are my graphic acceleration infos :
    Date du pilote 7-2-2014
    Description de la carte NVIDIA GeForce GTS 360M
    DirectWrite activé false (6.2.9200.16492)
    Fenêtres avec accélération graphique 1/1 Direct3D 11 (OMTC)
    GPU #2 active false
    ID du périphérique 0x0cb1
    ID du vendeur 0x10de
    Pilotes de la carte nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
    RAM de la carte 1024
    Rendu WebGL Google Inc. -- ANGLE (NVIDIA GeForce GTS 360M Direct3D9Ex vs_3_0 ps_3_0)
    Version du pilote 9.18.13.4052
    windowLayerManagerRemote true
    AzureCanvasBackend skia
    AzureContentBackend cairo
    AzureFallbackCanvasBackend cairo
    AzureSkiaAccelerated 0
    I hope this will be useful to solve this problem in future versions or to someone.

    This is happening to me too, I don't know if this is an Adobe Flash Player 11.5's bug or it's just my computer. All my browsers, chrome, IE9, Fox, doesn't even load anime videos. I tried reinstalling 11.5 many times, it have no effect but I use IE9 64-bit to run the videos that couldn't run. I waited 25 min for a JW player to load an episode of anime and I'm sick of it.

  • Mixed Media: 720p 60 + DVCPRO 50

    Hi all,
    I've searched the forums looking to answer this question, and may have actually found the answer more than once but have now thoroughly confused myself into a corner, so I thought I should just post.
    What would be the best method to work with 720p60 HD footage and DVCPRO 50 footage in the same timeline?
    All media has already been captured; recapturing with a hardware/deck/camera-based downconvert is no longer an option. Final output is to an SD DVD, in both NTSC and PAL (for which I'll be using Natress' Standards Conversion).
    I've been able to work with both formats in a variety of timelines, including Uncompressed 10-bit, DVCPRO 50 and so on, with each yielding slightly different results (letting FCP handle the rendering required). I'll be slowing down and reversing some clips, doing some desaturating, color correction, and adding grain here and there, so different combinations look better and worse depending on the sequence preset and the format of a particular clip, but none is consistently good for both formats.
    I'm assuming the correct way to approach this is to standardize the formats between the two sources -- in this case I'm figuring the best option is to downconvert the HD to a friendly SD (like DVCPRO 50, for example).
    Based on one of Shane Ross' posts I tried Media Manager, but I was given a warning that the frame rates didn't match and that I could either abort or preserve the framerate of the source (720p). Is the only other option a time- and drive space- costly conversion via Compressor?*
    *Um, yeah, important note: I've already done a bunch of editing on this project, naively (perhaps) believing that I could go about downconverting later on, but I did this thinking that Media Manager could easily convert and replace or create a new project with the downconverted media.
    Any advice would be extremely appreciated.
    Did I mention my deadline is in two days?
    2x2 GHz G5, 4GB RAM; 1.67 GHz 15" PB G4, 2GB RAM   Mac OS X (10.4.7)   SATA RAID; G-RAID (x3)

    Hey Pat, thanks -- your post gets to the heart of my troubles. (Shane's does too, in the sense of technical specifics, e.g. please forgive any slightly misstated specs in what follows...)
    The 16mm footage, which was originally 24 frames per second, was transferred to DVCPRO 50 (interlaced NTSC, 720x480, 29.97) before being captured (and it looks great). The few bits of DV were actually shot PAL (progressive) before being transfered to DV NTSC (interlaced), prior to capture (I had no say here, this is how I received the material -- which, by the way, looked pretty nasty).
    The HD footage was shot 720p 60, which I'm understanding means 960x720, 'p' for 'progressive' and 60 frames per second. That last part has confused the heck out of me -- I know it's possible to shoot faster than NTSC's run of the mill 30fps (okay, 29.97), but for some reason I thought this was an unusual circumstance (as if it needed a special camera or tape stock or whatever). I also understand the potential benefits when it comes to shooting a higher frame rate, like if you're planning on doing speed changes (especially slow-mo), but am I wrong to think that 60fps is unusual?
    Let me clarify a little. I know 29.97 is standard NTSC video, but according to the info within FCP (and in my bins), 720p 60 means 60 frames per second, not fields per second (which would indeed be 30 frames per second, or 29.97). If, however, the format was called '60i' this would mean that it was indeed 60 (or 59.98) fields per second, giving us 30 (or 29.97) frames per second. Please let me know if I've got this right.
    Assuming that's correct, then the 720p 60 is never going to play nicely with the DVCPRO 50. Even if I take the clips that I want to slow down and change their speed in a native timeline (720p 60), those rendered files still won't look good back in the DVCPRO 50 timeline (progressive vs. interlaced, 59.98 fps vs. 29.97 fps). It would seem to me that the best way to deal with this is to take the 720p 60 footage, make the speed changes in a native timeline (BTW, which way: using the speed controls within FCP, or Twixtor, or some kind of Cinema Tools conversion taking advantage of the 60fps?), and then output or convert this clips somehow before placing them back into the non-native DVCPRO 50 timeline. Make sense?
    My original hope was that the frame rate would be a minor concern, rendered nicely in the DVCPRO 50 timeline, and I was optimistic by how easily they seemed to mix together prior to making any speed changes. This hope was further dashed by the different results yielded by some of the film effects, like adding grain (which I now have a solution for: make all of my speed changes, finalize my edit, output a final version, then import that movie for applying additional effects, which will no longer vary according to the source footage specs, such as frame size and frame rate). I know it'll wind up being more complicated than this (for example, if I've got a cross dissolve between a 720p 60 clip and a 16mm clip (transferred to DVCPRO 50), applying a 24p film effect to the HD footage must be done independently (since the 16mm clip already has a 24p look to it), output (or rendered?), a then dropped back into the edit before outputting for final effects, such as adding grain).
    Phew. Sorry if I've overstated anything, I just want to be clear. Answering any of my questions above would be a huge help... and yes, my time is running out. No pressure.
    Maybe I can help things along by restating my questions (simply):
    1. What is the best way to apply speed changes, including reversals, to 720p 60 footage?
    2. What is the best way to insert speed-altered 720p 60 clips into a DVCPRO 50 timeline?
    3. What is the best way to apply a 24p frame rate effect (courtesy of Nattress' Film Effects) to this mix of 720p 60 and DV? (None of the DVCPRO 50 requires this filter because it was all originally 16mm film, which already appears to be 24p)
    Thank you for your help so far, and thanks in advance!
    P.S. - Sorry, another thought just occured to me. Say my cut is locked, couldn't I also opt to output the edited 720p 60 clips I'm using from a native 720p 60 timeline, then convert these clips using Compressor and re-import them into my project?
    I've read elsewhere that Compressor's format conversions are pretty spiffy, if time-consuming, but I'd only need to do this to a handful of relatively short shots. This way I could import the clips as DVCPRO 50 NTSC (interlaced, 29.97, 720x480), then apply other effects to all of the clips (like 24p, grain, etc.)...

  • I wrongly imported DVCPRO 50 files into a 720p HD sequence

    Hi,
    I wrongly imported clips originally shot in DVCPRO 50 PAL files into my default 720p HD sequence into a 720p HD sequence and when I discovered that I started a DVCPRO 50 sequence and imported the clips from the HD seq but they all look a bit out of focus and they had to be resized, and the text looks a bit out of focus too.
    How can I keep my edits but continue to work in the a seq set to the native format of the footage and make the clips look right?

    http://discussions.apple.com/thread.jspa?threadID=2682382&tstart=0

  • DVCPRO HD 720P Capture File  Pixel Dimensions, etc.

    I'm crossing over from Final Cut 7 where I've been using AJA LHi card to capture DVCPRO HD 720P 59.94 tape from the Panasonic 1400 deck successfully for years. In Premiere I've adjusted all the capture settings and sequence settings to conform to DVCPRO HD 720P 59.94:
    -Pixel format: MC DVCPRO HD 720P 60
    -Capture format: AJA Mov Capture
    -Video format:  720P 59.94
    BUT....
    -My Premiere capture tests look not only slightly horizontally stretched, but  cropped about 30 pixels only on the right of the full raster frame in both Premiere and in playback in Final Cut 7.  This is true for the clip as it plays on the timeline as well.
    -When I launch the clip in QT player it has the same cropping problems but is playing as 960x720, not defaulting to 1280x720 as normal 16:9. Final Cut captured clips play in QT as default 1280x720. So the file as captured in Premiere is missing a tag that tells QT how to resize it. I'm in QT 10.4 by the way.
    -I've imported captures from Final Cut into Premiere and they look fine.
    -The Premiere captured clip in the bin shows as 960x720 which is correct for DVCPHD, but in parenthesis shows (1.3333) which I've never seen anywhere before.
    -The folks at AJA think this is a Premiere issue not a capture card issue, and I tend to agree.
    Any suggestions?
    Thank you
    Steve
    Mac Pro Tower Quad Core
    OS 10.10.2

    I'm wondering if what the original camera may have embedded into the file is jumbled in with the 1400 and "crashing into" what both FCP and PrPro expect to 'see'. From the above grab, PrPro is thinking that this is just a P2 format Panny camera, shooting "standard" P2 stuff. Which this clearly is not.
    At this point ... wondering is say Kevin-Monahan could jump in here & provide some assistance? At least, he'd know who to talk with about this. So might shooternz ... he's been around this sort of thing for many years.
    Neil

Maybe you are looking for