QuickTime TeXML Export Hangs

I'm using QT Pro for Windows version 7.7.4 and I have a MOV file that contains a text track with a textual timecode at each frame.
If I export the text track to TeXML and the movie is longer than two minutes the export hangs.
Is there are a workaround or fix for this?
Thanks

Opening the XML file with QuickTime appears to have a limit too before it hangs.

Similar Messages

Using Quicktime's "Export for Web" feature in iWeb?

Greetings,
Does anyone know if this is possible within iWeb, that is, to use movies created using Quicktime's "Export to Web" feature, which really seems to deliver superior movie quality?
Much appreciated,
DaveB

Thanks, good stuff, though I'm still having a small problem with this. I'm getting a gray line around the top and left of my movie and the right side of the player is getting cut off. When I try to make the width larger, it just moves the gray line further to the left.
Any ideas?
http://www.brianderr.com/brianderr/copythis3.html
*This is the script that I added to the html snippet in iWeb.* I changed the height to 505px because it was cutting off the bottom of the player at 496.
<iframe src="http://idisk.me.com/brianderr/Public/KANYE%20PT%201/kanye1.html"
style="width:720px; height:505px";
scrolling="no">
</iframe>
*This is the script from my read me file that I kept:*
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<title>QuickTime Pro - Export for Web - KANYE PT 1</title>
<script src="http://www.apple.com/library/quicktime/scripts/ac_quicktime.js" language="JavaScript" type="text/javascript"></script>
<script src="http://www.apple.com/library/quicktime/scripts/qtp_library.js" language="JavaScript" type="text/javascript"></script>
<link href="http://www.apple.com/library/quicktime/stylesheets/qtp_library.css" rel="StyleSheet" type="text/css" />
</head>
<body><script type="text/javascript">
</script>
<noscript></body>
</html>

Exports hangs in stored procedures

hi i am running oracle 8.1.7 on solaris 8 when i am doing the export the export goes fine but when its reaching exporting stored procedures last after the integrity constraints the export is hanging and giving error
last terminated with unsuccessfully,what may be the reason only for the stored procdures failing in export.How to fix this
wiht regards
ramys

hi there is
no errors comming from the export logs.The export hangs and for long time and i have to cancel the export session
and giving export terminated unsuccesfully,how to fix it
with regards
ramya

Aperture 3: multiple export hangs while generating thumbnails?

Sigh. I was almost ready to write a blog post claiming that while AP3 has its share of bugs, it's not the unusable mess some have painted it to be. This morning I'm no so sure anymore. I think this is stellar update with tons of potential. When it works it screams on my machine and the new features are amazing. But guys, i need the basics to work.
Here's what I've just sent t via the feedback form:
I've been trying to export 29 pictures in web format for the past 40 minutes. I've had to force-quit AP three times and restart my machine twice. Aperture starts exporting at a normal pace but then completely hangs on a "generating thumbnails" process. At this point it becomes impossible to either cancel the task or quit Aperture normally. It also kicks my iMac's fan into overdrive - something that NEVER happens.
This is not good.
Other problems:
- random crashes while using brushes.
- second display doesn't follow "blank" command and keeps reverting to "alternate" even when the menu says Blank.
This is a great version of Aperture with a lot of potential. These bugs are killing me though.
I've just rebuilt the database. If it's still not working I'm going to remove plugins and see if it helps.
Anyone else having problems with this?

Absolutely has to be a bug. This isn't a setting or configuration problem. It might even be a Snow Leopard problem. I had the same problems with A2.1.4 on SL as I do with version A3.0.1. Export hangs seem to happen on images that came from my A2 library that was imported into A3 but originally adjusted in A2. These images were imported from scanned TIFF files. If the adjustment mechanism was flawed in prior Aperture versions then Apple needs to create and distribute a utility that converts these images into something that A3 can use.
I will have to revert to A2 running on Leopard until Apple can get this fixed. If I cannot export, there is no point in running the software. On this discussion thread, we are just trying to fly by flapping our arms.

QuickTime not playing QuickTime when exported?

Hi,
I just exported a movie for iPhone from QuickTime using Export for web. I get a question mark.
I'm using QuickTime Pro Version 7.6.2 (518) and OS X 10.5.7
I also get the question mark when publishing movies with iWeb so I'm assuming it's the same problem.
What can I do to fix this and ensure that others can see these movies?
thanks,
Dave

sure thing. I've posted these galleries in 2 places and neither are working for me:
http://gallery.me.com/timaging#100060
http://web.me.com/timaging/DaveLisaPix/CapeCod2009.html
second one doesn't work in Firefox at all, so I'm just considering the first link for now. Scroll down and you will see a few movies in there.
Dave

QuickTime - Save Export Settings - script help needed

Currently I am using Panther 10.3.9 - with QT PRO 7.02 - ( I do not want to
upgrade to Tiger at this time unfortunately)...
* MY GOAL: to be able to save export preferences in QuickTime pro.
Since QuickTime does not seem to be able to save export presets... I
downloaded the the script collection from
From: Scriptable Applications: Quicktime Player
Location: http://www.apple.com/applescript/quicktime/
and created export settings and tried ....
Save Export Settings.scpt
... but the file that got saved will not open in QT PRO - OSX and wants to
open something from old os9....
what do I do?

= = = (see scripts below)
* here is my basic workflow ...
- load a QuickTime movie
- adjust the QuickTime movie export settings
- save a test copy ( validating the settings)
- run the "save export settings.scpt" with name "set1test"
Then
- open and run the "Export QuickTime movie.scpt" with the name " test movie"
- run the new test movie - and when I check info - it does NOT reflect the desired settings...
= = =
One issue is - this line...
export movie 1 to new_file as QuickTime movie using settings "set1test"
... It doesn't seem to care what the settings file name is - and if I change that name to a nonexistent name - it still exports the movie without an error.... Therefore it leads me to believe that it's not using it to begin with....
- another issue is that the settings file "set1test" says it is the kind = "QuickTime settings document" - however it has a blank icon in the Finder - and there does not seem to be any way to open the file with QuickTime 7.02 - and it can to open something classic mode when I double click on it.
= = = the Save settings script...
tell application "QuickTime Player"
activate
try
if not (exists movie 1) then error "No movies are open."
stop every movie
set the target_file to choose file name with prompt "name & location for the QT settings file:"
save export settings movie 1 for QuickTime movie to target_file with replacing
end try
end tell
=== the Export QuickTime movie.scpt
tell application "QuickTime Player"
activate
try
if not (exists movie 1) then error "No movies are open."
stop every movie
set the movie_name to "mytest.mov"
if (can export movie 1 as QuickTime movie) is true then
set the new_file to ¬
choose file name with prompt "Enter a name:" default name movie_name
export movie 1 to new_file as QuickTime movie using settings "set1test"
end if
end try
end tell

Scheduled export hangs very often

Hi friends,
I've scheduled export running on DB server-Windows. I've created a batch file with export commands for about 5 databases and scheduled the job to run this batch file every night around 9 pm.
But, the export hangs quite often atleast 1-2 night a week with this message and when I come in the morning I had to hit enter for it to proceed:
batch file: (I've replaced the username,pwd etc in the below cmd, cannot provide on the forums...)
exp system/pwd@db1 file=exp_db1_full.dmp log=exp_db1_full.log full=y buffer=400000
exp username/pwd@db2 file=db2_user.dmp log=db2_user.log buffer=400000
exp system/pwd@db3 file=exp_db3_full.dmp log=exp_db3_full.log full=y buffer=400000
exp username/pwd@db4 file=db4_user.dmp log=db4_user.log buffer=300000
exp username/pwd@db5 file=db5_user.dmp log=db5_user.log buffer=300000
D:\>exp username/pwd@db4 file=db4_user.dmp log=db4_user.log buffer=300000
Export: Release 10.2.0.3.0 - Production on Wed Jan 13 21:17:36 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Release 10.2.0.3.0 - 64bit Production
EXP-00028: failed to open dbname_user.dmp for write
Export file: EXPDAT.DMP >It hangs mostly for db3,db4 or db5 exports.. Not consistent either. Just stops with this command. Please give me your suggestions...
Thanks a lot

It could be a couple of issues:
1. The file you gave it may be maxing out size wise and since there is no other file to use, exp builds the default file
expdat.dmp and prompts the user to make sure it is ok to use that file. To get around this, you could add a second
filename to the exp commands. If this happens for more than one job, you are overwriting the expdat.dmp file from the
previous job.
2. If for some reason it can't open that file, it would prompt for the expdat.dmp file.
So, by hitting <cr> when prompted, your exp job will write to the expdat.dmp file. It would be interesting to look at the size of the expdat.dmp file and the size of the file you thought the export was going to write to.
Dean

Datapump export hangs

Hi Gurus in the house,
I am using putty to access my database server, and I am trying to export the full database into a directory I created. The problem is that the export hangs at a particular place. My oracle version is 10.2 and I have used both system and a regular user (with exp_full_databse privilege) to do the export several times. The job runs but hangs at the same place and I have a deadline approaching to get export done on this machine and 2 other ones with same problem.
What can i do in this situation? Thanks folks and happy thanksgiving in advance.
BJ

You will be able to run the datapump import with trace option to see what is happenning. If it is running now, you can also use <ctrl>+c, run "status" command, it will show you what it is doing currently.

Strange quicktime codec export behavior

I was trying to make a movie from an image sequence using "export quicktime movie" today and had some odd results. The goal was to get the best quality for the least file size, and I needed alot of compression, so I tried many combinations of codecs and quality settings. The first oddity, was that the file size of the movie using "least" quality was higher than that of "low" quality for several codecs, including H264, MPEG and Sorensen 3. The second oddity was that if I scaled the movie during the export, I got a file that was the same size as the unscaled movie. If I scaled first in another program (ImageJ) and then made the movie, it was smaller than the unscaled. Comments?
BTW- the winner was Sorensen-3-low

Not sure what you mean. The codec used and quality setting have dramatic effects on the final file size. Just try rendering a movie with different quality settings and you will see the difference. I have done this many times and know it is true. I just never went to "least" before.
Some codecs have independent controls to restrict the data rates and set "quality" (i.e., reiteration of certain processes) while In others, the data rate may be incorporated into the "quality" control. The Apple Animation codec, for instance will increase the video data rate in proportion with increases in the "quality" setting but H.264 has independent/active control settings for each.
In more concrete terms, think of the data rate as the speed of a traveling car, the duration of your clip as the time a car travels, and the file size as the total distance traveled by the car. It is easy to see that a car traveling 100 mph for 4 hours covers a total distance of 400 miles while a car traveling at 50 mph only covers 200 miles. In a similar manner a clip having a total average data rate of 4.0 Mbps is twice as large as the same clip having a total average data rate of only 2.0 Mbps. Thus, if you really want to compare the differences in your file storage sizes, compare their their total average data rates and not their quality settings.
I scaled the movie from about 600x400 to 400x200.
Still not sure if you are referring to a change in the display dimensions or a change to the encoding matrix. This is important since it affects how different devices/applications deal with the content. Any clip can be re-scaled independent of the the encoded resolution. I.e., you can simple grab the lower right-hand corner of a QT player and drag it to change the clip's display dimensions. (Alternatively, you can change the properties window using QT 7 Pro). However, this action does not change the "encoded" resolution of the clip even if the scale change is saved in the file. On the other hand, if you exported or transcoded the modified file to video compression formats not having a "standardized" encode data matrix (e.g., like NTSC MPEG-2 or DV content has), then both the default scale and encode matrix are changed.
In the first case, where a file is simple rescaled, QT 7 would open with the display defaulted to the "Current Size" dimensions stored in the file and, if converted to a different video compression format, it would use the "Current Size" to set the target dimensions for the conversion. QT X, on the other hand, would not. It would ignore the "Current Size" setting and use the encoded dimensions for a "save" conversion.
To complicate matters, some conversion processes are device aware and may additionally restrict export/conversion dimensions. For instance, let's say I have a 640x360 file encoded at 29.97/30 fps. If I scale it to 1280x720 and then export the resulting file to the QT TV preset, I will end up with 960x540 encoded/display file. But, If I do the same thing to a 640x360 23.976 fps file, I would end up with a 1280x720 encoded/display file.
BTW: you do realize you are changing the 3:2 aspect ratio of the 600x400 file to 2:1 in the 400x200 file. (Or are we also taking about "cropping" as part of your work flow?)
In one case, I scaled the original data with ImageJ and then used the reduced size image sequence in Quicktime to export a movie... If I scaled first in another program (ImageJ) and then made the movie, it was smaller than the unscaled.
This is what I would normally expect in QT 7 Pro if the "scaled" clip has a changed "Current Size."
The second oddity was that if I scaled the movie during the export, I got a file that was the same size as the unscaled movie... In the other, I imported the full sized images sequence into Quicktime and set the smaller size with the size dialog during movie export.
You would have to provide more detailed information regarding your work flow here -- i.e., specific QT Player and/or target compressor and size settings if both options were available in your work flow.

Quicktime only exports audio in Lion

I have just upgraded to Lion and I can no longer get Quicktime to export video. When I select Export>Format>480p (for example) only the audio will export. What's goign on? Is there a fix for this?

What version are you using?
I was using QT 7 Pro version 7.6.6 as indicated by the ability to select different video compression formats as stated above.
As far as I know, there is only one QuickTime version available for OS X Lion, Version 10.1. It is the program that came with the new OS X Lion.
If you had QT 7 Pro installed on your Snow Leopard system at the time it was upgraded to Lion, then it would still be there after the upgrade. In addition, users can install the QT 7 Player to Lion after upgrading and key it for QT 7 Pro use if they so desire.
I was capable of exporting video and sound in Snow Leopard. Here is the flow process: In OS X Lion, open a .mov file. Go to File then Export. At the bottom of the dialog box it says Format. You can choose 480p, 720p, 1080p, then a line, then iPod..., Ipad..., Mac & PC, then a line, then Audio Only. These are the presets.
You still should be able to do so. I just ran four additional tests using four of the QT X "presets" at random. All successfully created an H.264/AAC file with playing video.
I'm not sure you are using the same version of QuickTime or the same OS if you do not see these things. At any rate, no matter the selection I choose, the only output I receive is an audio file. I think there is a bug in the new QuickTime.
I wasn't. That is why I asked which you were using so I could try and duplicate your work flow. Since I have no problem converting files, it does not sound like a bug—rather a bad software install or a conflict between the QT Player X and some third-party app you have installed on your system which I don't. However, you still have not indicated what video compression format was used in the source file. WMV for instance would be playback compatible if you had the free Flip4Mac player codec component installed but not conversion compatible without paying a minimum of $29 for the WMV "import" codec.

FCP quicktime "iphone "export diff then quicktime "export for iphone web"??

so what i dont get, is when i export out of quicktime using "export for web" and i choose the "iphone" 900 kbit option, i get 480X270 beautiful true widescreen clips. But when I export using quicktime conversion in final cut pro 6 and i choose" iphone"....i get 480X360. Why does this happen? I want true widescreen, just like everything i get from itunes.....not this 360 size (which i know is the phones screen res, but who cares)?

Alistair
Earlybird is exporting H264 ... the Key Frames setting is determining the GOP length. This value should really be determined based on the complexity of the video, to my understanding, the actual frame rate has no bearing on it. If you have very complex fast moving content then a low Key Frame rate is advisable to ensure good image quality (although it will adversely affect the filesize) whereas if you have slow moving or static content (like an interview subject) then a higher Key Frame rate will still produce a good image but at a smaler filesize. The default of 24 should be pretty much fine as a catchall starting point.
Earlybird
Corrupted render files (and render references) can be a pain because FCP will use those files and references in place of the original media when building the export. And so it should as it does't want to waste time re-rendering sections that are apparently already rendered. Unfortuantely, as noted, if the render file has gone bad and/or starts referencing the wrong media then you'll get these wierd flashes of completely unexpeced and unwanted footage showing up where it shouldn't be. When you trash those files then QT / FCP will just go back and re-reference the original media ... so it's usually a worthwhile step to take just in case thats the problem. The worse case scenario is that it only that doesn't work and you spend some time unecessarily re-rendering.
As to why these files go bad? That I don't know. Why do Preferences get corrupted? That I don't know either but it definitely happens :-(
Cheers
Andy

I get hangs using plug-ins (NIK), and can't export (hangs/crashes). Anyone experiencing this?

Updated Aperture today (3.4.3) running 10.8.2. Now I get hangs using plug-ins (NIK), and can't export (hangs/crashes). Anyone experiencing this?

Andrew,
In general, I've found the Nik plug-ins to be the least problematic of all that I use. Unfortunately you haven't provided enough information so that help can be focused on your problem. So here are some of the standard steps to take.
1. Make sure you are running Nik's latest versions. There were earlier ones that didn't work properly with ML.
2. Which plug-ings are the problem?
3. Have you tried the repair/rebuild option on your Aperture database? Often what appears to be problems with a 3rd party item actually stem from some sort of fault in the database.
4. If you're really stuck do the following steps: A. Delete the Nik plug-ings. B. Repair/rebuild the database. C. Download Nik's latest versions. D. Reinstall. E. Test.
This is a generic problem solving approach that fixes many things. Also, you should examine if it is a particularly type of file or set of photos or something specific in the images you are working on. A corrupt image, for example, can produce really weird things on occasion.
Hopefully some of this is useful. If not, more detail is needed.
Robert

Where have the Quicktime advanced export settings gone in Keynote 6.3?

Where have the Quicktime advanced export settings gone in Keynote 6.3?
In previous versions, it was possible to select numerous options and setting to export a high quality Quicktime video.

The new version 6 and the previous version 5 can both be installed, many users use both to utilise the different features. If you had the previous version installed and have not deleted it is located in iWorks in the Applications folder. If you don't have the previous version it is available from Ebay.

Why does quicktime only export audio

Why does Quicktime only export audio when exporting .mov files? I used to do it all the time with this same version. Now it doesn't work. I see a lot of other posts asking the same question and no answers.

Why does Quicktime only export audio when exporting .mov files? I used to do it all the time with this same version. Now it doesn't work. I see a lot of other posts asking the same question and no answers.
MOV files are audio and/or video content wrapped in an MOV file container. The first step in solving your problem would be to determine what codec components were used to create the source files and then determine if they are still supported by you current system configutation and/or conversion work flow.

FCP quicktime conversion export problem

issue exporting still image instead of video
FCP quicktime conversion export problem
within the last 2 weeks i have exported from FCP studio 7.0.3 as quicktime conversion, the settings are:
export as QuickTime Conversion:
> Options> quality> set to Best>
Standard Video Compression Settings
Compression Type: H.264
Motion:
Frame Rate: Current fps
Key Frames: Every 24 frames
check Frame Reordering
Compressor:
Quality: Best
Encodeing: Best (Multi-pass)
Data Rate:
Automatic
Filter… none
Size>
Dimensions:
NTSC 720x486 16:9
>ok
Sound: (don't change anything)
Format: Integer (Little Endian)
Sample rate: 48.000kHz
Sample size: 16-bit
Channels: (L R)
>Export
the results i get a odd. - the video exports fine, except for the beginning titles, instead a still frame image from somewhere else in the video occupies that intro, until the first transition- in this case- dip to white, then the rest of the video is fine. the portion of the beginning that does not show are composed of: livetype text credits in V2 - in which i have done a manual opacity fade up and down - so the livetype text fades in, over matte color solid in V1. in the exported video -i do not see any of this, all i see is a seemingly random still from somewhere else in the video. i can however hear the audio as it is supposed be.
cant figure out why this is happening. anybody know?
i think the livetype files are 1920 x 1080.
my FCP sequence is 720 p
this has only recently started happening and doesn't seem to be consistent.
im wondering if it has to do with the live type files, or the white solid?…
or the conversion settings above?

Alistair
Earlybird is exporting H264 ... the Key Frames setting is determining the GOP length. This value should really be determined based on the complexity of the video, to my understanding, the actual frame rate has no bearing on it. If you have very complex fast moving content then a low Key Frame rate is advisable to ensure good image quality (although it will adversely affect the filesize) whereas if you have slow moving or static content (like an interview subject) then a higher Key Frame rate will still produce a good image but at a smaler filesize. The default of 24 should be pretty much fine as a catchall starting point.
Earlybird
Corrupted render files (and render references) can be a pain because FCP will use those files and references in place of the original media when building the export. And so it should as it does't want to waste time re-rendering sections that are apparently already rendered. Unfortuantely, as noted, if the render file has gone bad and/or starts referencing the wrong media then you'll get these wierd flashes of completely unexpeced and unwanted footage showing up where it shouldn't be. When you trash those files then QT / FCP will just go back and re-reference the original media ... so it's usually a worthwhile step to take just in case thats the problem. The worse case scenario is that it only that doesn't work and you spend some time unecessarily re-rendering.
As to why these files go bad? That I don't know. Why do Preferences get corrupted? That I don't know either but it definitely happens :-(
Cheers
Andy

QuickTime TeXML Export Hangs

Similar Messages

Maybe you are looking for