QuickTime 64 bit

Hi i wonder if an QuickTime 64 bit version will arrive in future
Rendering large iPhone .MOV Video projects
the the applications run out of memory
Ihave 64 GB installed but as it is to day QuickTime only supports what a 32bit application can allocate
Filming with iPhone 6 mounted on a gimbal for iphone
allow you to make Videos like a PRO
but larger projects the applications run out of memory and the application hangs
So please be a kind Apple and make us a QuickTime 64 bit version
for OS X ,Windows and Linux as well
Thank You

Addressd Apple in a feedback formula on http://www.apple.com/feedback/quicktime.html
Thank you for your feedback on the QuickTime.
We cannot respond to you personally, but please know that your message has been received and will be reviewed by the QuickTime Team. If we need to follow up with you on your ideas for improving the QuickTime, we will contact you directly.
We appreciate your assistance in making the QuickTime better.
QuickTime Team
Apple
PS Snow leopard was tha last 32 bit OS X
To day it is the Old 32 bit applications which impede the effectiveness
OT: even Windows are using .mp4 in the latest
Windows Movie Maker
Version 2012 (Build 16.4.3528.0331)

Similar Messages

Quicktime 64-bit Windows 7 won't play AIF files?

I have an answering service collecting my phone calls after hours that provides me with a recording of messages delivered in a .aif file format. Having downloaded the latest version of Quicktime 7.6.6 I was hopeful that I would now be able to listen to those files using a Windows 7 64-bit O/S. Sadly such is not the case, I still have to load a 32-bit Windows XP mode environment to listen, (not clearly I might add, very choppy and clipped) to my messages.
When will Apple be getting this issue fixed???

If QuickTime is set to play avi files in System Preferences, then the avi might not be one that QuickTime can play. There are several proprietary avi codecs. You might try VLC player or some other player that can play all the different kinds of avi codecs.

ITunes is 64-bit. QuickTime is 32-bit. Why?

I downloaded iTunes for Windows 7, 64-bit. My understanding is that QuickTime is integrated with iTunes. When I go to Control Panel, one of the items is QuickTime (32-bit). Why isn’t it 64-bit?

Are you sure that iTunes 9 was seen as a 64-bit process? I don't remember ever seeing any of the iTunes versions being seen as 64-bit processes.
Some processes like iPodService are running as 64-bit processes.

On Windows 7, Itunes 64-bit is playing all videos with a green overlay

On Windows 7, Itunes 64-bit is playing all videos with a green overlay. You can see the video, but it's all green-scale (like grey-scale, only green). I've tried setting the Quicktime Direct3D options per Apple knowledge base articles, but to no avail... Windows 7 is all up to date, and I have the latest video drivers installed.
The videos play perfectly in Quicktime (32-bit; I guess there isn't a 64-bit Quicktime?).
Here's a screenshot:
I'd love to get this fixed; it's really baffling and annoying.

I had the same problem and surfed around the internet like a maniac. Finally, after several re-openings and re-installs of iTunes, I tried to log on to my account through the "Genius" - which I could. After that I have not had any problems to go to the Store!
Hope it works for you too!

Output the same size as the cropped video - to Quicktime

I have cropoped and resized my video and want to export it to quicktime the same as the cropped size.
I have tried to follow the instructions at this link, using the Crop button. I followed the instructions: "To crop the image interactively, drag the sides or corner handles of the crop box around the source image."
http://help.adobe.com/en_US/PremierePro/4.0/WS877FE27E-DDE6-4c35-9158-D1E1F5DEEEF2.html
However, I don't see the "Change Output Size to automatically set the frame height and frame width of the output to the height and width of the cropped frame". Using CS4 and exporting to quicktime 32 bit export.
So instead of doing the crop it is exporting it at 1440 x 1080.
Is it possible to crop and export to Quicktime?
Thanks
Rowby

To further explain --
THe crop setting in the Export Setting dialog box gives me two drop down options:
Scale to fit
Black Borders
"Change Output Size" is greyed out -- even though I have the image cropped in the Export Settings "Source" tab.
Exporting to Quicktime/Animation/32 bit
And in the Export Settings Video settings the width remains at the source's 1440, 1080. The "Constrain width and height" button is unchecked. Aspect is set for D1/DV NTSC Widescreen 16.9.....
Rowby

Error message in Quicktime

After saving a movie to the computer I can play it with media player without a problem, but if I try to open it in Quicktime I get an error
message 2048 couldn't open file because it is not a file that Quicktime understands. I have PE 11 on a Dell, Windows 7, Windows
quicktime 32 bit.

Richard,
One thing to remember is that MPEG is but a wrapper, and can contain a lot of different CODEC's, just like AVI (fewer variables than AVI, but still a lot of them). It could well be that yours uses a CODEC, that is not installed on the system, or is one that QT Player just cannot use.
Usually, when QT Player encounters a wrapper, that it can play, but when the CODEC is just not installed, it will offer to take you to a page on Apple's Web site, where there are several CODEC's, and player enhancements - some free, but some for sale. OTOH, if it's a CODEC, that QT Player cannot play, it usually just yields a message to that effect. It will not usually throw an error message, such as you got.
Now, it appears that you used the MPEG-2 DVD wrapper & CODEC. Is that correct? That is about as "plain vanilla," as an MPEG-2 gets, and it would surprise me, that QT Player could not handle that. However, there are a couple of variables, that might cause an issue. By the DVD-specs., the Bit-Rate (total for both the Audio and Video Streams combined), cannot be over 10 MB/s. As the Audio Bit-Rate is not factored into many encoder's settings (it's really pretty small), most will choose about 8 MB/s, for the max. Bit-Rate for the Video, allowing some headroom for the Audio. Some DVD hardware players will choke if the Bit-Rate is much above 7.5 MB/s for the Video, though they are spec'ed. to handle that 10 MB/s total Bit-Rate.
As a test, I would choose MOV, with the Animation CODEC. This will be very, very close to Uncompressed, and WILL create a large file. However, that should be about as easy for QT Player to handle, as it gets. Remember, this is but a test. If QT Player pops up an error message with that file, then it is something with your installation of QT Player, or something on your computer, that is interferring with QT Player. Please report on that test. If your Timeline's Duration is long, maybe limit this test to just part of it, with the WAB (Work Area Bar), so it does not take too long to Export/Share that file for testing.
Good luck,
Hunt

Quicktime issues on Maverick?

I have Quicktime on my 10.9.5 2011 Macbook Pro - yet I keep getting notifications that I need to install Quicktime. Then when I go to the website, Apple says "QuickTime is built into Mac OS X." Never ending circle. I'm on Chrome - Quicktime IS enabled under plugins... I use quicktime all the time ... I first noticed this when I tried to watch apple trailers... couldn't do it. I *CAN watch apple trailers on Safari with n

MichelleEulene wrote:
I have [1] Quicktime on my 10.9.5 2011 Macbook Pro - yet I keep [2] getting notifications that I need to install Quicktime. Then when I go to the website, Apple says "QuickTime is built into Mac OS X." Never ending circle. [3] I'm on Chrome - Quicktime IS enabled under plugins... I use quicktime all the time ... I first noticed this when I [4] tried to watch apple trailers... couldn't do it. I *CAN watch apple trailers on Safari with n
QT X version #?
WHAT is giving you the "notifications" ?? OS X Software Update?
Chrome - what version? If latest update, you do NOT have QT enabled - see > QuickTime 64-bit Chrome Plugin
No plug-in in Chrome - Safari has not disclosed what its plans are for HTML5 specification standard
ÇÇÇ

Debayering and quicktime encoding

Hello,
I'm using netbeans 5.x under ubuntu 8.04 with J2SE, JDK 1.6.
I have built an application that pilots a digital camera. I now have to transfer images from the camera to the pc, so I create a socket and get the datas into an array, no problem on this side.
The thing is, I now have to first debayer those raw datas, and then to encode the frames into a 10 bit uncompressed quicktime file.
Is there someone who has already worked on something like this in Java ? Everywhere I look it seems the jmf can't handle it.
Any help would be much appreciated.
Thank you,
Dan.

Hi,
No one can confirm that it's not possible to encode quicktime 10 bits uncompressed from raw datas (RGB pixels) with the jmf ?
Thank you,
Dan.

Need help to figure out why AE is taking 20 to 30 hours to render 5 minutes of Virtual studio

While I have been doing video editing for years, I am new to After Effects....Still, I went through the tutorials and Lynda.com, and I think I know my way around it well enough so that my renders should be working far more effectively than they are.
The big problem is the duration it is taking to have After Effects render a virtual Studio clip, whether I just use a 20 second clip of my reporter with a video playing behind them in an LCD tv set, or if I try to run a full 5 minute version of the entire show....Friday night I tried to run the full 5 minute version of one of , and it took over 36 hours!!! I am not getting any real help from Blue FX...either the support they offer is really for people that have been using After Effects for many years, and they can't imagine the issues I am having..or, maybe they feel that my issues are more After Effects issue than template issues.
When I first bought the template a month ago, the PC I had been editing with for years was not powerful enough by most accounts I have read, about what is useful for AE....So I put together a new PC, this one with 32 gigs of ram, an Nvidea 760 video card with 2 gigs of RAM, 8 hard drives and tons of fans for 24 hour operation.
Some of the things I don't know..... How long "should" one of these 3D virtual studios take to render, where you have already stripped out the greenscreen and are feeding the reporter video in with alpha channel on a quicktime 32 bit animation codec video....and have a 1080p hi res video playing in the TV behind the reporter--in the virtual studio...and you have all the 3 D renders and shadows and effects of the studio template being rendered? Do people really wait 24 to 30 hours for a 5 minute long finished rendering?
To give you an idea of the studio template and what my computer is having to process, here is a sample we did, no script, just trying to see how this would produce.....and this one I did in 25 second and 10 second chunks/renders, assembling later in Premiere,....still, the rendering was close to 20 hours.
Beyond the Beach - YouTube
If any one can suggest what might be going on wrong, that is taking so long, I'd appreciate it. One are I wonder about is whether something needs to be collapsed--I read that some elements need to be collapsed prior to rendering--but how would I know which?

Rendering composites has always been slow. It is much faster than it used to be. MP rendering still does not work for all situations. Temporal effects and MANY, let me repeat that MANY codecs do not respond well if at all to MP rendering so you should turn that off unless you know for sure your comp and your codec work with MP rendering. I seldom if ever use MP rendering for anything that is not rendered to an image sequence. It is not uncommon for my complex composites to take 2 or 3 minutes a frame. I have had many that take longer. Simple projects, on the other hand, can render as fast as 2 or 3 frames a second. It all depends on the project. That's the way compositing goes.
Compositing is almost always faster than 3D rendering. I had a 3D project last week that took 25 hours to render 100 frames. You just have to plan for it early in the project.
Here's what my usual workflow is:
Avoid Ray-traced rendering unless there is no other way to achieve the design (I also minimize the ray traced paths in 3D apps because it is very slow)
Pre-render and replace footage elements that I am going to re-use. For example, if I pull a key and I'm going to need to use that key for 5 or 10 layers to pull off a convincing composite I'll pre-render the keyed footage to a lossless production codec and replace the keyed layer in the comp with the rendered file
Render and replace all Warp Stabilized footage with a suitable DI (lossless digital intermediate)
Use the Adobe Media Encoder render all deliverables, including production proofs and production masters, usually directly from an AE project file, then start or switch to another AE project and continue working while the AME is chugging away
Render Image Sequences whenever possible in the production pipeline because it's easier to make changes to frame 200 through 220 when the client wants a change in less than a second of a 30 minute project.
NEVER try and edit a movie in AE. AE is for sequences or shots, your NLE is for editing
I have not sat around twiddling my thumbs waiting for AE's render cue to churn out a project in years. The only time I wait for anything is for ram previews. I also have some workflow suggestions for that.
Just as cell animators do, run motion tests with the most basic of your project's elements. By that I mean set Comp Resolution to automatic, set the Zoom factor to 50 or 25% and check how the motion works before you add any effects that are going to slow things down. If you have already added effects you can temporarily turn them off in the Timeline view
Check only critical frames or a few critical frames that are in transition (moving) at full resolution because RAM previews at full resolution are short and slow to render and you don't have time to mess around
If you have long sections to ram preview to verify timing follow rule 1 but modify the ram preview settings to use only every other or every fourth frame
THE MOST IMPORTANT RULE: Remember that video moves and that you cannot judge the final quality of a video by nit picking a single frame. You must watch playback in real time on the playback device that will be used to see if your scene is working.
Last rule, if you have gone over the same few frames of a sequence trying to fix something about it for more than 10 minutes, step away from that project and do something else for at least 20 minutes. You'll be amazed how good it looks when you get back to it
I have one more suggestion for a new AE user. Actually, this is for anyone that works at a computer for a living. Never sit staring at the screen and pounding at the keyboard for more than one hour without standing up and walking at least around the room for 5 minutes to let your head clear and get the blood circulating. You'll be happier, more creative, and have better health and posture.

Is Anyone Successfully Using DNxHR CODEC with CS6

Just downloaded the HR 4K CODEC today http://cdn.avid.com/Codecs/LE/2.6.0/CodecsLE_2.6.0_Win.zip
Trying to do a test export, but it hangs at 0%.
Anyone else try this yet?

tested it in premiere 8.2, seems to work ok, but was slow as it was using quicktime 32 bit. was able to export and re-import the video back into premiere and it read it ok. not sure why it wouldn't work in cs6, do you have the latest version of quicktime installed?

Nice forehead bruise, or Why won't 9.0.3 install?

Hello Applegangers. I have Windows XP as my OS, and a shiny new iPod which tells me I must be using version 9 of iTunes. Having had no problems with previous versions, I happily installed it... and it failed. And uninstalled, and it failed. I took the step of calling Apple customer no-service, and was told to run the application after launching IE (I use Firefox).
Now I've face-planted so many times I'm going to have to try a new hairstyle to cover the bruises.
I come here hopeful and full of certainty that someone can tell me the magic fix. To date, I have tried the following:
*Downloading from IE rather than Firefox
*Turning off firewall
*Running Windows Install Clean-Up Utility
*Updating Quicktime
*Unintall/reinstalling many, many times
*Maunally dumping all iTunes files and start over
*Praying to the gods of technology, even though I'm a technological atheist
*Rolling back to version 8 (won't work with Quicktime)
My bit of internet probing has shown me that at least there are many others in the same situation; nothing I've read so far as a "fix" has worked for me.

That coregraphics.dll is inside the install of AppleApplicationSupport.msi. I suspect the Apple Application Support somehow didn't install properly.
I've seen other posts where folks got it going by using WinRAR to extract the AppleApplicationSupport.msi from the iTunesSetup.exe, and run the AAS msi by itself:
1. Download iTunes setup exe
2. Open the exe with WinRAR and extract all contents to a new folder
3. Go into folder and run "AppleApplicationSupport.msi"
4. When windows says it can't find the folder, hit "browse" and select the folder you extracted the files to.
5. The installation window should now appear. Choose "Repair" option.

Stop or Redirect RTCP Multicast via SDP Files (Help!)

I've got a piece of hardware (Optibase MM400 encoder) that generates both an SDP file and a multicast RTP video stream. (I've configured it to omit the audio stream.) The SDP looks like this:
(Note: I've obscured some of the IPs with letters)
v=0
o=INGESTSERVERA7 723 75540417 IN IP4 AAA.BBB.239.243
s=MM-400
t=0 0
a=x-authentication:A989B14958B5089A940C1201
a=isma-compliance:1,1,1
a=mpeg4-iod: "data:application/mpeg4-iod;base64,AoILAE8BAQABAQOBJgABQIhkYXRhOmFwcGxpY2F0aW9uL21wZWc0LW9kLWF1O2Jhc2U2NCxBVWtCUndVZkEwTUE0QVFFT3lBUkFGQUFBQURhd0FBQTJzQUZMQUFBQWJBQkFBQUJzbFZWQUFBQnRRa0FBQUVCQUFBQklRQ080QUFnSXlBQWFBQkNnRWdBOVFXRURoUmpCZ0VEBA0BBQAAyAAAAAAAAAAABgkBAAAAAAAAAAADWQACQDZkYXRhOmFwcGxpY2F0aW9uL21wZWc0LWJpZnMtYXU7YmFzZTY0LHdCQVNZUVNJVUVVRlB3QT0EEgINAAAUAAAAAAAAAAAFAwAAQAYJAQAAAAAAAAAA"
m=video 11110 RTP/AVP 96
c=IN IP4 239.1.7.193/127
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=1; config=000001B001000001B25555000001B5090000010100000121008EE00020232000680042804800F505840E1463
a=mpeg4-esid:224
The problem is that both VLC and QuickTime spit out multicast packets in response to the streaming video--e.g. RTCP. (I'll explain why this is a problem in a followup message.)
I tried using the RTCP bandwidth specifiers (b=RR: and b=RS:) in both the session and media contexts, but it they didn't affect the RTCP packet rate (one every five seconds).
Here's how I used them in the session context:
v=0
o=INGESTSERVERA7 723 75540417 IN IP4 AAA.BBB.239.243
s=MM-400
b=RR:0
b=RS:0
t=0 0
a=x-authentication:A989B14958B5089A940C1201
a=isma-compliance:1,1,1
a=mpeg4-iod: "data:application/mpeg4-iod;base64,AoILAE8BAQABAQOBJgABQIhkYXRhOmFwcGxpY2F0aW9uL21wZWc0LW9kLWF1O2Jhc2U2NCxBVWtCUndVZkEwTUE0QVFFT3lBUkFGQUFBQURhd0FBQTJzQUZMQUFBQWJBQkFBQUJzbFZWQUFBQnRRa0FBQUVCQUFBQklRQ080QUFnSXlBQWFBQkNnRWdBOVFXRURoUmpCZ0VEBA0BBQAAyAAAAAAAAAAABgkBAAAAAAAAAAADWQACQDZkYXRhOmFwcGxpY2F0aW9uL21wZWc0LWJpZnMtYXU7YmFzZTY0LHdCQVNZUVNJVUVVRlB3QT0EEgINAAAUAAAAAAAAAAAFAwAAQAYJAQAAAAAAAAAA"
Here's how I used them in the media context:
m=video 11110 RTP/AVP 96
c=IN IP4 239.1.7.193/127
b=RR:0
b=RS:0
a=rtpmap:96 MP4V-ES/90000
a=fmtp:96 profile-level-id=1; config=000001B001000001B25555000001B5090000010100000121008EE00020232000680042804800F505840E1463
a=mpeg4-esid:224
I also tried it once with the "b=AS:" value set to the total size of the media stream.
Next, I tried to use the "a=rtcp:" attribute to redirect the packets to a different IP (unicast) and then just a different port.
Here's how I used it in the session context:
v=0
o=INGESTSERVERA7 723 75540417 IN IP4 AAA.BBB.239.243
s=MM-400
t=0 0
a=rtcp:11223 IN IP4 10.10.10.10
a=x-authentication:A989B14958B5089A940C1201
a=isma-compliance:1,1,1
a=mpeg4-iod: "data:application/mpeg4-iod;base64,AoILAE8BAQABAQOBJgABQIhkYXRhOmFwcGxpY2F0aW9uL21wZWc0LW9kLWF1O2Jhc2U2NCxBVWtCUndVZkEwTUE0QVFFT3lBUkFGQUFBQURhd0FBQTJzQUZMQUFBQWJBQkFBQUJzbFZWQUFBQnRRa0FBQUVCQUFBQklRQ080QUFnSXlBQWFBQkNnRWdBOVFXRURoUmpCZ0VEBA0BBQAAyAAAAAAAAAAABgkBAAAAAAAAAAADWQACQDZkYXRhOmFwcGxpY2F0aW9uL21wZWc0LWJpZnMtYXU7YmFzZTY0LHdCQVNZUVNJVUVVRlB3QT0EEgINAAAUAAAAAAAAAAAFAwAAQAYJAQAAAAAAAAAA"
...then just thet port...
a=rtcp:11223
This didn't affect the RTCP packets from VLC or QuickTime one bit, while changing the media port did have an effect--proving that the SDP files were being read.
On last thing I tried was the "a=rtcp:unicast reflection" attribute, hoping it would return traffic to a unicast address that I could blackhole.
Here's how I used it:
v=0
o=INGESTSERVERA7 723 75540417 IN IP4 AAA.BBB.239.243
s=MM-400
t=0 0
a=rtcp:a=rtcp:unicast reflection
a=rtcp:11223 IN IP4 10.10.10.10
a=x-authentication:A989B14958B5089A940C1201
a=isma-compliance:1,1,1
a=mpeg4-iod: "data:application/mpeg4-iod;base64,AoILAE8BAQABAQOBJgABQIhkYXRhOmFwcGxpY2F0aW9uL21wZWc0LW9kLWF1O2Jhc2U2NCxBVWtCUndVZkEwTUE0QVFFT3lBUkFGQUFBQURhd0FBQTJzQUZMQUFBQWJBQkFBQUJzbFZWQUFBQnRRa0FBQUVCQUFBQklRQ080QUFnSXlBQWFBQkNnRWdBOVFXRURoUmpCZ0VEBA0BBQAAyAAAAAAAAAAABgkBAAAAAAAAAAADWQACQDZkYXRhOmFwcGxpY2F0aW9uL21wZWc0LWJpZnMtYXU7YmFzZTY0LHdCQVNZUVNJVUVVRlB3QT0EEgINAAAUAAAAAAAAAAAFAwAAQAYJAQAAAAAAAAAA"
...and still, the VLC/QuickTime Player clients continued to spit out RTCP multicast traffic on the port (11111) following the media port (11110).
Anyone have any ideas what I'm doing wrong? Surely VLC and/or QuickTime has implemented a solution.
Note, this problem was identified in the QuickTime forums a few times, but never addressed:
* http://discussions.apple.com/thread.jspa?messageID=8020690&#8020690
* http://discussions.apple.com/thread.jspa?messageID=2543521&#2543521
* http://lists.apple.com/archives/streaming-server-dev/2003/Jul/msg00037.html
One last note: I successfully delivered the SDP file as a local file, a web file, and wrapped within a SAP multicast.. all with the same results.

For the purposes of completeness, and evidence that I've been digging for the answer, here's some overview and reference information.
Intro (skip if you know about RTCP and its downsides)
For people just running into this problem. VLC and QuickTime Player send out a multicast packet every 5 seconds in response to multicast RTP stream(s) identified via SDP files. These packets are "RTCP", which is sent by RTP clients to report on the quality of the streams from the client perspective.
The problem is, these packets can overwhelm a system with thousands of clients:
* All client packets have to be delivered to all other clients (huge complexity)
* Routers have to maintain giant lists of the multicast senders
* Many systems are only efficient for single-source multicast traffic (think satellites)
Note: As I understand it, the RTCP multicast packets are sent to all clients so that each client can throttle the overall RTCP bandwidth to reasonable levels. While this is clever solution, it doesn't reduce the number of multicast senders--just the frequency of their packets.
Possible Solutions
I've read through a lot of the SDP/RTP specs. It seems like the preferred (by the spec authors) solution is to redirect the RTCP traffic to a unicast location and then rebroadcast the RTCP traffic from the same single source.
This spec mentions the "rtcp-unicast" option:
Draft Spec: RTCP with Unicast Feedback (http://tools.ietf.org/html/draft-ietf-avt-rtcpssm-17)
This spec specifies means of directing RTCP traffic to specific ports/IPs (presumably unicast included):
RFC 3605: RTCP attribute in SDP (http://www.packetizer.com/rfc/rfc3605/)
Another potential solution (ideal in my case), is to pinch the bandwidth for RTCP traffic down to zero, effectively stopping all RTCP traffic from the clients.
This spec specifies the "b=AS:", "b=RS:", and "b=RR:" bandwidth modifiers:
RFC 3556: Session Description Protocol (SDP) Bandwidth Modifier (http://www.faqs.org/rfcs/rfc3556.html)
Other Specs
RFC 4566: SDP: Session Description Protocol (http://www.ietf.org/rfc/rfc4566)
* Replaced RFC 2327: SDP: Session Description Protocol (http://www.ietf.org/rfc/rfc4566)
RFC 3550: RTP: A Transport Protocol for Real-Time Applications (http://www.ietf.org/rfc/rfc3550.txt)
* Replaced RFC 1889: RTP: A Transport Protocol for Real-Time Applications (http://www.rfc-editor.org/rfc/rfc1889.txt)
RFC 3890: A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)
RFC 4585: Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)
RFC 1890: RTP Profile for Audio and Video Conferences with Minimal Control
Question: Which RFC(s) is QuickTime compliant with?

HD footage to a SD-DVD

I need help yet again (the story of my life). I filmed an amazing short in 720p and it's sitting fully edited on my "17 MacBook Pro. Now I'm trying to enter the film in some festivals, and they need a DVD copy of the short. I can render great looking quick time files, but when I try to burn them, they look really bad. When I use compressor, I’m always getting “video bandwidth too high” errors when I go to burn the mpeg2 to a DVD in DVD Studio Pro. I’m just wondering the exact steps/settings people are going through to get their HD footage from FCP to a SD DVD. Because I can’t seem to do anything right. Thanks a ton everybody. Hopefully I can get this figured out by before the festival deadlines is up.
-Daniel

An interesting topic. I would also like to try the most recent suggestion, using Animation codec set to NTSC 730 X 486. Where do I find that setting? I cannot find it in my Quicktime setting menu in FCP.
Recently, I edited a short HD documetary in FCP and then down converted it to DVDSP4 as a DV NTSC 48 kHZ Anamorphic Quicktime movie. Here are the steps that I followed. Any advice or feedback is appreciated.
Way #1
1. Project: 14 min. 45 sec.
2. Original project edited in HD in FCP (Original footage shot on Sony FX-1)
3. Down converted on G4 Powerbook 1.67 with setting at DV NTSC 48 kHZ Anamorphic. (I was told this setting gives more flexibility as a 16:9 wide screen image on computers and TV monitors.)
4. 6 bit rate / 7.9 rate max.
5. Two passes / Best
6. Closing credits with made in After Effects and then transferred directly to DVDSP4 in regular Quicktime lower bit rate and one pass. (I will redo at higher bit rate settings. Put the credits directly in SD in DVDSD4 and not in the HD Timeline on FCP because I had earlier problems when I down converted these graphics from HD on FCP to DVDSP4.)
7. No compressor or other items added to enhance video/audio quality. Should I use the Compressor? Any other items?
8.. Results: Satisfactory to Good
Way #2
1. Project: 14 min. 45 sec.
2. Original project edited in HD on FCP.
3. Used a G5 Quad with a Kona-2 graphic card installed. The Quicktime movie setting was on Kona-HDV 1080i60 (something like that). I ended up with a Kona-HD Quicktime movie. Then put the Kona-HD Quicktime file back into the FCP timeline and made a second Quicktime file in DV NTSC 48 kHZ Anamorphic from the FCP Quicktime settings. (Kona does not appear to have a NTSC Anamorphic setting.)
4. 6 bit rate / 7.9 rate max.
5. Two passes / Best
6. Same
7. Results: Good image / some lettering slightly blurred but probably acceptable.
Any advice on how I can make the DVD video image and audio better? Should I use the compressor? Other items?
I hope this reply contributed to the original question and image issues.
Powerbook G4 Mac OS X (10.4.6) Have access to G5 Quad, Presently use Powerbook G4 1.67

24p DV to HDCAM

Hi,
I have DVX-100 24pA NTSC DV footage in a 23.98 sequence. I want to uprez to HDCAM NTSC 23.98. The post house I'm working with recommends this workflow:
1. Within FCP, create a Quicktime 10 bit uncompressed 4:2:2 (23.98 progressive)
2. 10 bit Quicktime (23.98 progressive) transferred to Digibeta 29.97.
3. Digibeta feeds into Snell & Wilcox Ukon and converted to HDCAM 23.98 progressive.
I want to maintain optimal quality as my film will be showing in a large theater on HDCAM. The post house maintains that they do conversions like this all the time, and say I need a Digibeta in order for the HDCAM to run off of timecode. We're using the Snell & Wilcox Ukon as supposedly the hardware uprezzers are superior to software.
My questions are:
A. Is it necessary to convert to 29.97 Digibeta? By making a 23.98 sequence into 29.97 and then converting back to 23.98 seems like it might create pulldown issues and doesn't seem right.
B. Can the Snell & Wilcox Ukon, Teranex or other HD uprez boxes directly convert Quicktime 10 bit uncompressed 4:2:2 to HDCAM? I don't see the point of going to Digibeta just to run off of timecode.
It seems like there's the old Hollywood (expensive) way of doing this, and the DVX-FCP way that eliminates waste and high cost. Let me know if the workflow they recommend is the best option.
Thanks,
Alexander

Do you want it done right? OR done half-@$$ed? This isn't only the Hollywood way of doing it, but it is the best way of doing it.
Another way would be to simply copy and paste your clips into a 10-bit uncompressed or ProRes timeline, and render. This might pass for OK, but it is free.
Or you can use Compressor (also free) and have it take a few days or week to render this out. And the results will look good, but not as good.
Or you can invest in a Kona card and good sized RAID and output to digibeta, then recapture with the Kona 3 upconverting as you capture. This looks great...but not as good as the Wilcox or Terranex. Not free either.
Dude...you want to maintain optimal quality...and film festival and FILM BUYERS ESPECIALLY are quality critical. Don't let something distract them from your story. Do it right.
The post house knows what they are doing. They are paid to. Ask to see examples if you are wary.
Shane

Codec information in the info window or anywhere in Premiere Pro?

Hi all,
I'm very new to Adobe Premiere Pro so pardon the newly question. I of course come from the Final Cut Pro world.
So one of the things I didn't get was the level of information provided in the various info panels. I noticed that neither the file properties or info panels, display what kind of codec a particular video is when it's in the project. Lets say I had some XDCAM files and some ProRes files that i've imported, and I look at the info on the files either through right clicking and selecting properties or selecting the file and then going to the info panel, it doesn't ever display the actual codec in which the video is in. It usually says something like MPEG movie or Quicktime Movie, but it won't get more detailed like it's a "ProRes 422 file" or something like that.
Is there any place in Premiere where this information can be displayed? That's something that I did like about FCP, is it's transparent display of file attributes and how specific it gets down to what codec the file is encoded in, etc.
There's got to be a place in Premiere that has that info, no? Please advise.
Thanks!!

From what I understand, QT is now 64-bit native, so I'm not sure that would be the issue.
QuickTime X is 64-bit, but that's a completely different application and architecture than QuickTime 7, which is only 32-bit. Premiere Pro uses QuickTime 7 exclusively for QuickTime import/export support, since QuickTime X a) doesn't do everything QuickTime 7 does and b) is only available on the Mac.
Premiere Pro is not a QuickTime based application, the way that FCP 7 was (I think FCP X is a completely different animal, all the way). In many respects, QT is a bolt-on in Premiere Pro, but that's by necessity rather than by design. The QT32 Server application that Todd referenced is a result of this necessity; Apple didn't make it easy for other application authors to integrate QT into their applications, so Adobe had to do the next best thing. Not including QuickTime support of any sort in Premiere Pro CS5 and beyond, once the application went 64-bit, would have been an unacceptable end for many shops and editors who use QuickTime in their workflows. This comes at certain expenses, but there's only so much Adobe could do with the limitations of the QuickTime 32-bit architecture.
That said, Adobe has done a lot with many types of QuickTime files that completely circumvent the 32-bit QuickTime process, and allows Premiere Pro to natively and directly support certain MOV flavors. For example, Canon DSLR QuickTime MOVs are handled by Premiere Pro's MPEG importer (that's why they show up as MPEG Movie in Properties), as are DV/DVCPRO50/DVCPRO HD MOVs and JVC XDCAM EX MOVs. There are several other examples as well, but the end result is the same: you don't even need QuickTime 7 installed (on Windows or Mac) to import these files and they're always handled with a 64-bit importer. That's a pretty major workflow and performance enhancement, and I think goes a long way to suggest Adobe's commitment to handling as many media types natively and as robustly as possible.
Ultimately, I think that once Apple discontinues QuickTime 7, we'll be at a crossroads. Adobe appears to be trying to support as many different QuickTime codec flavors natively as they can, but that's a long list, and there are only so many that are viable to develop and maintain support of in the future. What that means for the formats and codecs you need for your workflows, I couldn't say, but definitely use that feature request form (when it works!) to add your voice to the conversation.

QuickTime 64 bit

Similar Messages

Maybe you are looking for