64 bit Quicktime

Attempting to load Quicken on WIN 7 64 bit machine. Message, "load 64 bit version".
Where is the 64 bit version? No distinction is made in the download choices. I did attempt to download the version for WIN 7.

Hmmmm. Just doublechecking ... are you getting this when you download the installer, or after the install when you try to open QuickTime?
If the latter, it might be worth trying to run the program in XP 32-bit compatibility mode. Essentially, follow the instructions in the following document *in reverse* (your QuickTime program will be in \Program Files (x86)\ rather than in \Program Files\ though) and select XP 32 bit mode (if you get that as an option):
[Error -2096 message when opening QuickTime for Windows in Compatibility Mode|http://support.apple.com/kb/TS1875]
(I fear we're just going to get the 2096 error, but it seems worth a crack, just in case.)

Similar Messages

Is there a 64 bit Quicktime Pro for Windows?

I just purchased a 64 bit vista machine for video editing and I'm looking for a 64 bit version of quicktime pro. I've installed quicktime on this machine and notice that it runs as a 32 bit process. I want to take full advantage of my hardware, and therefore want a version of QT Pro that is made for the 64 bit architecture. There is no information on apple's website that I could find about this. Does anyone in the community know if apple has made such a version of QT Pro???
Thanks!

I believe the libraries for QuickTime (QTKit) are indeed 64 bit. However, 64 bit under OSX is very different from 64 bit under Windows. There are a few good websites that can help explain the difference, here's one that is fairly straightforward.
http://arstechnica.com/articles/culture/microsoft-learn-from-apple-II.ars/3

Limitations of Quicktime files (.mov and h.264) in Windows 64-bit.

It was recently brought to my attention (yes, I'm late to the party) that any file that requires the Apple Quicktime process for playback (decoding) is severely limiting my otherwise powerful system. The Quicktime process is a 32-bit process, which limits your editing functionality to 4GB of RAM—even if you have 32GB or more installed!
I'm starting this new thread because the thread on which this was brought to my attention wasn't directly related to these issues.
A few of my questions: Why do so many cameras create .MOV or .MP4 files that require QuickTime components? 64-bit QuickTime X has aparently been available on the Mac for quite a while, yet I presume they won't allow anyone else to develop a 64-bit codec for Windows, so why hasn't someone sued Apple for monopoly, anti-trust, conflict-of-interest, etc? And most importantly, in a world where DSLRs and off-board ProRes recorders abound, are Windows users really stuck with no option but to transcode the footage before heavy use in Premiere? The Atomos recorders provide the option of using DNxHD, however, if I understand correctly, that codec still requires Quicktime (I've not tested this bit). Is there a matrix available that shows camera / recorded format / requires quicktime / 8- or 10-bit / 4:2:0 or 4:2:2, etc?
To my fellow Windows 64-bit editors, how do you keep your sanity when editing "natively" in Premiere .MOV, .MP4, ProRes or DNxHD with the 4GB RAM limitation? And what camera / off-board recorder do you prefer to avoid both a long transcoding session AND get right to work with native 64-bit codecs?
Thanks in advance!
=== Systems ===
Desktop              |   Laptop
i7-2600K             |   i7-3630qm
GTX460 (1GB)   |   GTX670mx (3GB)
         Windows 7 64-bit
         16GB RAM

strypesinpost wrote:
...Have you read this yet?
http://blogs.adobe.com/VideoRoad/2012/12/premiere-pro-and-quicktime-an d-nikon-oh-my.html
Just now. Yet, it seems to contradict my own findings. The article says: "In the case of Canon DSLR files, there’s something in the file header. Premiere Pro can recognize that the clips came from a Canon camera, and bypass QuickTime. This enables Premiere Pro to have smooth playback of DSLR files..."
The test I conducted was between files from a Canon 7D in their original format vs. an AVI file I transcoded from those originals using GoPro Studio (formerly Cineform). I load up a project and timeline with the original 7D files and then scrub the heck out of the timeline, back and forth. I have Task Manager open in order to monitor my RAM usage. I simply could not get past roughly 4GB. Once I deleted all the original .MOV files from the project, retaining only the transcoded .AVIs, the project cut like butter. The harder I scrubbed the timeline, the higher my RAM usage soared until it gradually, and gracefully came close to maxing out. Lol. Is there a better test I should run?
The other test I ran was a project where I took a single talking head clip of approximately 5 minutes in length. Nothing too taxing for the hard drive, and something that *should* be easy enough to play completely from RAM, once it played through once or twice. I cut this clip and staggered a few tracks on top of eachother. No effects, no transparency. The cumulative effect was a cuts-only edit, but on the timeline my tracks looked like stairs, etc (perhaps the stairs weren't necessary). The primary goal here was to watch how the system performed with a simple cuts-only project where Peremiere was repeatedly asked to access the same file from random locations in the file.   The .AVI version of this project, again, played flawlessly. The .MOV version played even worse than I was expecting, since cuts-only 7D footage is usually not SO hard on the system (even if it is limited to 4GB RAM). The .MOV project couldn't keep up. Period. As soon as the file needed to "jump back" on itself, the refresh rate became intolerable.
So is the 7D an exception to the rule stated in that article? It definitely seems to be limited to 4GB of RAM! If it isn't, why am I seeing this?
Also, is it possible that the footage from the 7D may not *REQUIRE* Quicktime to decode, but since Quicktime is found on my system, the 7D files default to using it anyway?
I've not tested my GoPro footage so thoroughly, but I believe it's limited in the same way. After a transcode to AVI in GoPro Studio, even 2.7K footage plays slick as a whistle. Not so when I don't transcode.
Further thoughts?

64-bit version of Quicktime for Windows

I'm running 64-bit version of Windows 7 via bootcamp. I'm running 64-bit version of Microsoft Office 2010. I have the latest version of Quicktime installed 7.7.3 something. I can play the file on the desktop no problem, but when I try to insert the file into Powerpoint or play a file that I inserted previously into Powerpoint on a different system, it says either Quicktime unavailable or you need a 64-bit version of Quicktime in order to insert the file.
So, exactly where is a 64-bit version of Quicktime for Windows because apparently the one on the Apple website for Windows is not 64-bit. Everyone keeps saying download the 64-bit version of Quicktime. Great, tell me where it is. There is no option for 64-bit on the website. It doesn't even say it is 64-bit. It just says its compatible with Windows 7. Powerpoint 2010 64-bit MUST have a 64-bit version of Quicktime in order to insert or play any Quicktime file. The OS doesn't give a rats @ss one way or the other.
The file I previously inserted was playing on a system that apparently had a 32-bit version of Powerpoint installed. That machine defaults to VLC player on the desktop. It has no issues with the file. It's the Quicktime Player mismatch on my machine that is giving me grief. If I knew Office was going to be a PITA if I installed the 64-bit version I would have stuck with the 32-bit version.
Ideas? Where is the 64-bit version? How do you tell it is 64-bit? How do you force the installer to make sure it ONLY installs a 64-bit version of it?

If Microsoft merely off their own decided that only a 64-bit version of QuickTime was going to be supported by them and did not both checking such a beast existed then this is perfectly believable behavior on the part of Microsoft and they should roast in **** for it.
If Apple led Microsoft to believe that a 64-bit version of QuickTime was going to be released like a 64-bit version of iTunes for Windows has been released but then backed out then this is equally believeable behaviour on the part of Apple and then equally the guilty parties at Apple should roast in ****.
It should be noted that the 64-bit version of iTunes is able to play videos via the 32-bit version of QuickTime. This suggests Microsoft programmers are weak with the force. This would tend to support my theory that Microsoft despite being the biggest software company in the world are better at making hardware than software.
Moving on to trying to be more constructive…
Clearly as things stand using the existing and only official version of QuickTime for Windows which is 32-bit only is not going to work in 64-bit Office. It might therefore be worth looking at trying the following.
Uninstall completely Apple's 32-bit QuickTime for Windows (if installed currently)
Install QuickTime Alternative - see http://www.free-codecs.com/download/QuickTime_Alternative.htm
I have no idea if QuickTime Alternative is 64-bit, I have no idea if it will work in 64-bit Office even if it is 64-bit. However it does work in Internet Explorer for Windows, it is free and therefore will cost you nothing to try. If it does not work you can then always uninstall it.
As another even more abtruse solution, you could try loading your PowerPoint file in to the free iWorks i.e. KeyNote via a free iCloud account. It will allow importing PowerPoint files and will even work in Internet Explorer.

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!

In what way is iTunes for 64-bit windows 64-bit?

I keep finding conflicting info on this topic. There appears to be a version of iTunes for 64-bit Windows, but task manager shows itunes.exe as being 32-bit.
In what way is this installer 64-bit? Does it install 64-bit drivers for iOS devices and iTunes, but the program is still 32-bit?

The itunes.exe process itself is 32-bit (on a 64-bit install). Most of the iTunes program files are also 32-bit.
The miniplayer is 64-bit, and there are 64-bit plugins for Outlook. (You'll see those items in the iTunes folder in your "Program files" rather than in the iTunes folder in your "Program files (x86)".)
The GEAR drivers itunes uses for burning will be the 64-bit versions on a 64-bit system.
The iPod service will be 64-bit on a 64-bit system.
Apple Mobile Device Support is 64-bit (so you'll have the 64-bit Apple Mobile Device Service, and usbaapl64.sys and netaapl64.sys rather than usbaapl.sys and netaapl.sys, on the 64-bit system.)
Some of the bonjour componentry on the 64-bit install will be 64-bit.
Most everything else is 32-bit (QuickTime, Apple Software Update, Apple Application Support).
(Apologies for inaccuracies ... it's been a wee while since I checked the noir-household 64-bit Vista box for locations. The precise details of what is 32-bit and 64-bit can change between versions. For example, one of the big changes between the itunes 8.x 64-bit versions and the itunes 9.x 64-bit versions was the iPod Service going 64-bit.)

Quicktime Pro 7 on Snow Leopard displays black with uncompressed Quicktime

Hi, I have searched these discussions but with no luck so far. Any help will be greatly appreciated but I have the feeling there may be no solution to my problem. Perhaps the new 64 Bit Quicktime 7 is missing the codecs I need.
For more than five years I have been exporting uncompressed Quicktimes from an online workstation (Autodesk Flame) to my G5 to make small quicktimes to email clients to see work in progress, or to make file sequences for upload and also to make DVDs fro client presentations outside my online suite. I would export an uncompressed Quicktimes of, (for instance), a 30" TV Commercials (of around 1GB) from my online workstation fro my Mac to deal with. This week I changed my five year old G5 for a Snow Leopard Mac Mini. My Quicktime 7 Pro license transferred fine, but it seems to me Quicktime 7 is working quite differently and iDVD also. When I open an uncompressed quicktime created from my online workstation the video is Black , but I can hear the audio. It still allows me to make a small H264 quicktime but I can't export file sequences correctly. The frames created are black. iDVD also creates black DVDs but with sound. BTW I have the same problem if I export an uncompressed AVI from Flame.
I thought it might be hardware limitation of the Mac-mini, but some simple tests indicate that's not the case. From my online machine I can export an uncompressed Targa file sequence of the Commercial and an uncompressed wav sound file instead of an uncompressed Quicktime. I can then use Quicktime 7 to put them together make an uncompresses quicktime from the Targa sequences combined with audio and it displays the video fine and I can do whatever I want with it, but it takes time to create. This uncompressed quicktime file is around the same size 1GB as the uncompressed movie file that I am trying to get Quicktime 7 to display, that I normally export from Flame. (And BTW the Mac Mini renders quicktimes nearly three times faster than my 2004 G5 and can play back the 1GB uncompressesd file it made with hardly a glitch, The G5 would choke if i tried to play an uncompressed movie).
This kind of uncompressed Quicktime that I can make from Targa files using Quicktime 7 Pro seem to be exactly the same as the uncompressed Quicktimes my Autodesk Flame exports. In the properties window the video codec is "None, 720 x 576 Millions+" in both cases, and it is of course a .mov. So why the difference? My big problem is that the uncompressed quicktimes exported from Flame are not able to be handled as well by my Mac as before. I know I can export file sequences with a separate audio files and put them together in Quicktime but when I am working on a commercial I might want to do this 20 times a day. Exporting an uncompressed file with audio is much less hassle. I would just drop it in iDVD and make a DVD or get Quicktime to re-encode it for email. My Post Production clients pay me to work on the online workstation and I don't want to spend extra time on my Mac-mini. I was hoping to spend less....
I hope I have been clear enough explaining my problem. Thanks very much for any tips.
Regards,
Harold

Hi there,
I can confirm that this seems to be a bug in Quicktime where it tries to multiply the alpha channel against the contents of your movie file.
I had a bunch of Apple Animation quicktimes that are suddenly playing back as all black. I opened one of these movies in Shake and noticed that it had an all black alpha channel. So, as an experiment, I added an ellipse as an alpha channel (making sure it was not pre-multiplied against the image) and wrote this movie out as an Apple Animation. Sure enough, quicktime would now play back an image where the contents were only visible inside the the ellipse. I.e. it is multiplying the image by the alpha channel.
So, the issue is that quicktime multiplies the alpha channel against the contents of the movie.
The workaround is to re-encode your movies with solid white alpha channels (I have been unable to write out an Apple Animation movie without any alpha channel at all). Most likely you don't care what is in your alpha channel (the Apple Animation codec seems to add it whether you actively request it or not), but if you do, then I don't know how to get around this problem.
Also... what a pain. I don't really relish re-encoding all of my quicktimes. I will also file a bug (or piggy back on the one already filed). Hopefully we can get this fixed soon.

AVI / Quicktime export not working correctly

Hi there,
I just started using CS4, my first simple task already failed. Imoprt / export a video, no editing no rending. This works fine in CS2, the exported video looks exactly like the imported one. Here i have a strange shift in colors (especially red). It looks a little bit like a "glowing".
Card: AJA 2K (4.2.1)
CS4 Premiere (4.2.1)
I have the following sequence:
Uncompressed
1080psf23,976
Video sources in the timeline
10 Bit
Quicktime
AJA v210
1080psf
23,976
Export:
10 Bit
Quicktime / AVI
AJA v210
1080p
23,976
I tried:
YUV
CGR
SMPTE
I don't know how to make this work?
Thanks in advance*

HA!
That's a great one to play at Parties!!
BTW - that's a great way to do one-offs of sections you want to send out. HOWEVER - a problem there too - if you have a CLIP selected, FCP won't know if you are exporting that cut or the in/out point. Make sure everything is DE-selected. You'll notice a color shift in the timeline indicating the IN/OUT area when you are good to go.
Glad you fixed, now GET BACK TO WORK!
CaptM

Firewire video in 64 bit mode - is this still a problem?

I've been holding off on upgrading from Logic 8 to 9 for a myriad of reasons, but the biggest head-scratcher for me is that you can't run Firewire video (or Digital Cinema Desktop, for that matter) in 64 bit mode.
Does anyone know if this issues still exist in 9.1.2/9.1.3?
Makes it very tough to score to picture when you can't see the picture...

This ONLY effects the 64-bit mode! And because Mac OS X doesn't offer this in 64-bit QuickTime, this problem still exists. But if you use Logic 9 in 32-bit mode, just like Logic 8, it will work fine.

Exported Quicktime Won't Open

Hi,
I exported a couple of uncompressed 10-bit Quicktimes from an FCP 6.0.2 sequence (running QT 7.4.1). They open and play fine on my computer, but not on my client's PC. I burned them to data DVD's, the client dragged them to their hard drive, and tried opening in the latest version of QT for Windows. They get the recognition error, "not a file that QT understands." I don't really get where this could have gone wrong. Any ideas?

QT can handle a remarkable number of codecs, which obviously play well on your natively QT based Mac machine with FCP installed and not on a PC.
QT is a FAR more complex wrapper then AVI (usually installed by default on PCs).
QT files can contain multiple video and audio tracks while AVI cannot.
Uncompressed 10 bit may not indeed run on an average PC but maybe one PC that have installed Premiere Pro 3.0 might....
That could be a lead.
G.

ITunes 7.0.1.8 experiences - Here's what got fixed for me...

After news of the iTunes 7.0.1.8 update broke out today, I downloaded it and have used it for a little while.
I'd thought I'd share my experiences so far, but please take note that I did not do any CD burning/importing tests, nor do I own an iPod to sync content to or a 5.1 set of speakers to play songs with. I have heard that this update dramatically fixes the slow recognition and sync times for iPods and that there is better speaker recognition for surround sound systems, but I can't personally confirm this.
My current audio settings in QuickTime are at 48kHz, 16-bit, QuickTime Music Synthesizer. Safe Mode is disabled. These have been my withstanding settings since iTunes 6. To my knowledge, all sound drivers and video drivers are up to date. Hardware acceleration is at full, and DirectX is also up to date.
Some problems I noticed in iTunes 7.0.0.10, in no order - and whether they've been fixed or not in iTunes 7.0.1.8:
Problem: Cover Flow view was slow to respond and had album art rendering issues. I didn't get the diagonal lines, but it definitely bogged down my system. Most likely a memory leak.
With 7.0.1.8: Partially fixed. CPU usage doesn't skyrocket as much, but the flow animations still stutter and album art rendering still lags. Once the art is loaded into RAM, however, Cover Flow is as smooth as ever and does not max out at 100% CPU for me.
Problem: Download manager was unresponsive. iTunes would crawl when playing a song and downloading something, as menu commands, pausing/unpausing, etc. was delayed by up to a minute. CPU usage at 100%.
With 7.0.1.8: Mostly fixed.The download manager is now noticably speedier, and is responsive to user inputs with pausing downloads, scrubbing songs, etc. However, CPU usage is still at 95%-100% when a download is running.
Problem: Gapless playback caused distortion.
With 7.0.1.8: Fixed. Gapless playback now works correctly and seamlessly, without causing distortion in the first or last few seconds of a song or delaying playback.
Problem: Audio playback became distorted and skipped when running any other applications, such as a web browser.
With 7.0.1.8: Partially Fixed - Your results may vary. Audio no longer messes up horribly anymore -- even when the voume is less than 100% -- which is great. However, small skipping is still apparent when browsing in Firefox or even in the iTunes Store. This happens sporatically, however, as I'm browsing now and there is no studdering, though minutes ago browsing caused some skips. CPU usage spikes to 100% momentarily when this occurs. Nonetheless, it is still a MAJOR improvement from before, and now I believe that skipping exists due to my only having 256MB RAM in this PC. Your results may vary.
Problem: Newly downloaded album art did not actually get embedded into the music file, and iTunes didn't find album artwork for tracks that were in the iTunes store.
With 7.0.1.8: Not fixed. Downloaded album art from iTunes 7 is not embedded into the actual file, and needs to be copy-pasted back in the Artwork tab of the "Get Info" window. One non-related fix, though, is that album art can now be manually added in the album viewer on the bottom left of the window for multiple tracks at once. For downloading artwork (I did not set this as 'automatic' in my iTunes preferences but did it manually), I recommend matching the store listing 100% with track numbers, capitalizations, etc. and making sure the ID3 tags of MP3 files are v2.2 or higher.
Problem: At random times, checkboxes did not actually check or uncheck when clicked on; this was especially true in the Podcast library. Only a manual right-click menu selection would check or uncheck an item.
With 7.0.1.8: Fixed. No more checkboxing issues so far.
Problem: Visualizer size setting in Preferences -> Advanced tab (Small, Medium, Large) did not actually take effect.
With 7.0.1.8: Not fixed. The visualizer still plays in the "large" setting, no matter what the setting is; I believe this is a bug. In addition to this, when in Cover Flow view and changing to the visualizer, Cover Flow leaves an intrusive snapshot on top of the visualizer, which isn't fixed until switching out of the visualizer and changing back to the list or album view.
Problem: Video playback stuttered when viewing on-screen controls, and the controls didn't appear when the mouse was over the video and iTunes was in mini player mode or minimized. Clicking on the video at that point stopped playback and closed the video window.
With 7.0.1.8: Not fixed. While video playback is snappier in iTunes 7 in general, this little oversight hasn't been touched yet. I also believe part of it is because of a lack of RAM on my computer, but would've liked to see more smooth playback like what was found in the last revision of iTunes 6, in addition to the added controls.
Problem: Adding ratings from within the library is a little hit-or-miss; I have to click on a certain edge of the star to select it.
With 7.0.1.8: Not fixed. I have to click pretty firmly on the ratings column in my iTunes library, or just do it manually by right-clicking or doing it in the Get Info window.
I think that covers most of what I personally found in the previous version of iTunes 7. I didn't previously have the importing problem or settings fail to save (sans the visualizer), however. (Feel free to add to this thread with your experiences if you'd like.)
Dell Dimension 2400 Windows XP Intel Celeron 2.59GHz, 256MB RAM

UPDATE/EDIT FROM PREVIOUS POST:
Ok. The new 7.0.18 does repair the volume slider audio issue. HOWEVER, Simply installing the new update (at least for me) did **NOT** fix the problem. After posting my previous post, I tried to remove Quicktime and iTunes completely and try reinstalling.
It turns out that when I uninstalled Quicktime from Add/Remove Programs, it didn't remove all the Quicktime files and it was not reinstalling Quicktime afterwards!!
I only noticed when I downloaded the standalone version of Quicktime and tried running it and it said a "newer version" was on my computer, though it did not show up on my Add/Remove Programs file listing.
So I looked in the usual places and found that I had a Quicktime folder remaining in the Program Files folder and one in the C:\Windows\system32 folder. I also had to manually remove the following files from the C:\Windows\system32 folder:
Quicktime.qts, QuickTimeMusicalInstruments.qtx, the Quicktime.Resources folder, QuicktimeVR.qtx and the QuickTimeVR.Resources folder.
The main problem is that iTunes didn't let me know there was an issue with the QuickTime installation. It just wouldn't run iTunes. There should have been a notification.
Anyway, after all this, I reinstalled iTunes fresh and checked the volume slider and LO' And Behold! The volume slider issue was repaired.
However, there is a LOT of skipping occurring that never happened before. Not sure what's up with that. CPU usage stays low and then I get a few skips per minute...UNACCEPTABLE!!! That didn't happen before and that issue will still need to be fixed. Until then, back to WinAmp. Thx a LOT Apple...you *#^@ing hosers!

No Sound for Videos in iTunes 10.6 - Help!

Hi,
All of a sudden, in iTunes for Windows, whenever I play videos, I get no sound/audio. The video plays fine, but no sound.
Previously, everything played fine in iTunes, video and audio.
Here is what I am using:
iTunes 10.6 for Windows 64-bit
Windows 7 Ultimate 64-bit
Quicktime 7.7.1
What is strange, is that audio files (songs and audio podcasts) play fine in iTunes. But when I switch to ANY video file (music video, movie or video podcast) the video portion plays fine, but no audio.
I've tried playing the same videos in Quicktime (standalone), and all is well.
I'm also able to play the same video files in Windows Media Player with no issues.
In addition, all of the videos have great sound in my iPod, iPhone, and iPad.
The problem is solely with playback within the iTunes Program.
Any thoughts on what settings I should check, or what other tips I should try?
Much appreciated!
N~

Hi,
I have the same problem exactly.
Everything worked and I had sound while playing movies on the Itunes player and on the phone and suddenly it stopped.
Now I can only play the video but with no audio and on the phone is the same.
I have already re installed itunes and quik time and still it doesn't help.
It making me go crazy.
I do have sound while playing songs or videos from the internet, but not a downloaded videos or videos from my PC.
Could you help me with it???

ITunes 7.0.2.16 - It hasn't fixed my playback issue(s). Your experiences?

A little recap of my iTunes 7 story:
-I went from iTunes 6.0.5 to iTunes 7.0.0.70 ("updated my library," analyzed gapless playback and indexed my album art) and got video slowdown (100% CPU) and horrible playback stuttering as the main issues, amongst others.
-Upgrading to iTunes 7.0.1.8 lowered the system resources a bit, but audio still skipped (though no longer distorted) and the playback bar never finished in playlists with repeat/shuffle turned off--the last song in a playlist would play, but iTunes won't end it once it reaches -0:00 remaining. iTunes also sometimes stopped playing back music entirely, staying put at 0:00 and requiring a reboot.
Here's my deal with iTunes 7.0.2.16 so far:
While installing iTunes 7.0.2.16, it wiped out and re-installed QuickTime 7.1.3 (just like the iTunes 7.0.1.8 installer did) as well as break all my QT + iTunes shortcuts.
Upon opening iTunes and clicking "Agree," it updated my library again in the same way it updated with the first-time launch of iTunes 7.0.0.70. Took quite a while to finish, and I thought the application hung for a couple of moments.
After a few minutes of usage alongside Firefox and other applications, I can say that in my case, the new version of iTunes has NOT fixed my playback-skipping issues and video playback slowdown that I first encountered with iTunes 7.0.0.70, but a few UI bugs are done with:
-Party Shuffle works as intended now.
-The 0:00 issue with tracks not finishing has disappeared. FINALLY!
-Cover Flow no longer refreshes artwork in its pane when playing a new song in that view.
-Checkboxes seem to work again in the Podcast library.
Minor bugs left besides playback performance: The visualizer only plays back in large size, no matter what size is chosen in Preferences. There's still a graphical glitch with the menu bar when stopping an enhanced podcast, and double-clicking an album cover not in focus in Cover Flow causes the animation to start from the beginning.
How's iTunes 7.0.2.16 for the rest of you? I might have to try that 48kHz/16-bit QuickTime tweaking again and see if it brings any luck.

A small update from my first post here since this topic's getting bumped - here's my temporary workaround with playback in iTunes 7.0.2.16, and it's worked:
Upon opening iTunes, play a track and don't let it stop. Just, whatever you do, keep some form of audio playing at all times (music/podcast/audiobook) without pausing or stopping it. Then, go about your regular multi-tasking routine and it shouldn't skip. Again, iTunes should always be playing something; don't let a playlist finish without "repeat all" turned on, for example.
If you need to turn off the music for a moment, just mute the volume in iTunes (drag the volume slider all the way to the left).
I find this to be the only workable solution for me until the next iTunes revision comes out - playback has been perfect about 100% of the time. Hope it works for you! Lemme know if it does.

"...an Output Module failed" error screen...

Greetings AE Peeps!!
Long time - no see - been stupid busy. My Studio has just ponied up and upgraded our 5 Edit Stations to AE CS5. I personally am a huge advocate of not upgrading software while in the middle of a project, but this was out of my control. I am having a lot of crashing (app just quits for no reason while scrubbing) and other weirdness...like today. I am rendering a 3 minute piece in ProRes 4:2:2 (1280x720p) to my RAID (no special plug-ins or anything) and I get the following error at the very end of every render:
After Effects Error: Rendering error while writing to file (insert my RAID path here). An output module failed. The file may be damaged or corrupted (-1610153464)
I have never in 11 years got a "failed Output Module error". Can anyone speak to this and tell me how to get rid of it short of reinstalling AE?
Grazie! Ciao!
Joey

First, make sure that you've installed the After Effects CS5 (10.0.1) update.
Regarding the output module failure: It may be that this is because you have an output module created in a previous version of After Effects that refers to a codec or set of settings that isn't working in After Effects CS5. The best thing to do is to remove the output modules from the render items and then rebuild them in After Effects CS5. That may sound tedious, but you only need to do it once, and then you can save output module templates that you know work with After Effects CS5.
As Mylenium suggested, there are some challenges associated with the fact that there is no 64-bit QuickTime, so we had to create our own 32-bit-to-64-bit QuickTime conversion layer (QT32 Server). QuickTime does work with After Effects CS5, but there are some hiccups in some cases on first use.
If this doesn't help, answer back and we'll help you through.
Oh, this might be useful, too:
http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

CS5 Error with Animation Output

Running CS5 on a Mac 10.6.4
Every time I render, it gives the following error message:
An output module failed. The file may be damaged or corrupted. (-1610153464)
I've tested the files on a different machine and they open and render out fine.
I did some searches and for some it was the dreaded Optical Flares plugin from Video CoPilot causing this same problem.
I'm having these issues and I don't have any plugins installed.
Re-Installed everything 3 times, trashed preferences, removed plugins from the Application support and still no luck.
The only thing that works for me is outputting to a PNG or JPEG sequence.
If I try to render using the Animation preset, It gives the error message.
I also have been getting a weird "MooV" error message when I try to import certain types of quicktime files. Not all just a few random ones.
All of this leads me to believe it may be an issue with 32 bit Quicktime.
Any suggests on how I can get the Animation preset working again?
Thanks.
It gives an error message

Sure, I had the exact problem posted at the top of this thread. Spent two days reading all the posts regarding anything that had to do with this Output Module error. I finally came upon a post of someone who was having a similar issue as I with the hang at start up. However, the post was replied to by a guy who said "Repeat the hang with only AE running, then go to the Activity Monitor and select the QT32 Server process. Then press the "Sample Process" button at the top of the window...It looks like both of you are having a similar problem with a third party AVI codec. Please remove or uninstall any third party AVI codecs such as DivX, XVid, etc. from your system and try AE again."
"You can also temporarily disable these components by closing any QT related apps and then dragging components out of the Library/QuickTime folder on your boot drive. If that works, try adding them back one by one until it fails again. That is the problem codec."
So I removed AviImporter.component from Library/Quicktime on the boot drive and these two problems were solved.
Here is the link to the post where I found this info.
http://forums.adobe.com/thread/634237?start=0&tstart=0

64 bit Quicktime

Similar Messages

Maybe you are looking for