QT Pro exported file is a faded white single frame

I have a file that I am trying to resize to a more internet friendly size for iWeb (it would be nice if iWeb automatically did this). However the resulting file is a white frame from about the middle of the movie. I have tried various setting but they are all pretty much the same. The audio is ok.
I'm going from a Mov to a Mov with H.264 using the default settings for Broadband - High.
One thing I did note was that the progress bar was slow to 50% then fast to 75% then finished suddenly.
The movie can be seen on this screenshot with the original behind it.
Dual 2GHz PowerMac G5 (plus 15" G4 PowerBook) Mac OS X (10.4.8) 2.5 GB DDR SDRAM, 2x160GB SATA, 23" Cinema HD Display

I'm going from a Mov to a Mov with H.264 using the default settings for Broadband - High.Sounds as if you are using one of the automatic "share" settings here. Might be nice to know the specific workflow used since some H.264 profiles can do strange things when attempting to get complex graphics/scenes all the way down to a specified video data limitation at a specific display size. In this case, it sounds as if it may have created a "freeze frame" for a portion of your clip. Have seen this happen when compression demands exceed the feasible "per pixel/per frame" ratio for the profile, dimensions, and content in use. You might try manual settings to find an acceptable "happy point" for you specifc needs. Hard to make even educated guesses without concrete starting specifications and some idea as to your target goals.

Similar Messages

Self Contained Final Cut Pro Export Files unreadable in New Final Cut Pro 7

Has anyone come across this? I was using Final Cut Pro 5, created a self contained file of a current project 1.9GB in size. Uploaded the new version of Final Cut Pro 7 and upgraded to Snow Leopard, and now it tells me that this is unrecognizable as a movie file. Quicktime or Final Cut Will not open this file. I'm puzzled.

VideoJunkie88 wrote:
Has anyone come across this? I was using Final Cut Pro 5, created a self contained file of a current project 1.9GB in size. Uploaded the new version of Final Cut Pro 7 and upgraded to Snow Leopard, and now it tells me that this is unrecognizable as a movie file. Quicktime or Final Cut Will not open this file. I'm puzzled.
Hi VideoJunkie
I have not come across this. However, my previous FCP 6 Self-Contained Exported ProRes 422 standard (not HQ) files which are actually 1440 x 1080 will only playback in the new QT version 10 using that aspect ratio (whatever the actual screen ratio is at 1440 x 1080, I'm not sure, but the video width is squashed together... I suppose it has something to do with showing it in square pixels versus rectangle... or do I have that turned around. I'm not sure, I have always been confused about the ProRes 1440 x 1080 format, all I know is it plays back properly in 1920 x 1080 when I transcode it for DVD or ATV, iPhone etc..). In any case, you need QT player 7 (standard or pro version) to display these files at the intended aspect ratio of 1920 x 1080. The old QT Pro player version 7 will let you change this in the properties window, but the QT 7 standard player will not let you (those options are grayed out) and the new QT X player doesn't even show these options (i.e totally unavailable).
Also, these previous files will play just fine (for me anyway) in FCP version 7. If you having a different issue where they will not play at all, then I'm not sure how to help you, but I just wanted you to be aware that my old self-contained files from FCP 6 do work (for me anyway) in the new FCP7 under Snow Leopard.
(ADDED) I must ask, what codec were your previous exported self-contained QT movies? Do you have this codec on the commuter your trying to play your old master self-contained exports on?
Ron
Message was edited by: videocrafter

Good day! On the ultrabook Asus (System Settings: WIN 8.1 64-bit, Core I5-3317U CPU @ 1.70 Ghz, Memory 4 Gb), set Adobe Acrobat XI Pro 11.0.09 When you convert to any format via SaveAs in WORD, EXCEL, or via the Export file in ... throws the error "Un

Good day!
On the ultrabook Asus (System Settings: WIN 8.1 64-bit, Core I5-3317U CPU @ 1.70 Ghz, Memory 4 Gb), set Adobe Acrobat XI Pro 11.0.09
When you convert to any format via SaveAs in WORD, EXCEL, or via the Export file in ... throws the error "Unable to process the document in the module Save As. File not created"

Hi,
Was it working fine for you before?
Is it with some specific documents?
Are you able to convert the word/excel files to pdf?
Regards,
Rave

Good day!   On the ultrabook Asus (System Settings: WIN 8.1 64-bit, Core I5-3317U CPU @ 1.70 Ghz, Memory 4 Gb), set Adobe Acrobat XI Pro 11.0.09 When you convert to any format via SaveAs in WORD, EXCEL, or via the Export file in ... throws the error "Una

Good day!
On the ultrabook Asus (System Settings: WIN 8.1 64-bit, Core I5-3317U CPU @ 1.70 Ghz, Memory 4 Gb), set Adobe Acrobat XI Pro 11.0.09
When you convert to any format via SaveAs in WORD, EXCEL, or via the Export file in ... throws the error "Unable to process the document in the module Save As. File not created"

This happens with any file .
Send a file with the screen errors and system data . Also send a couple of files PDF.
Translates only txt format.
Acrobat установлен: C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\Acrobat.exe
    Версия: 11.0.9.29
Дата создания: 2014/09/12
    Время создания: 13:43:46
Браузер по умолчанию:
Версия BIOS: _ASUS_ - 1072009
Версия ОС: 6.2.9200
Всего виртуальной памяти: 4194176 KB
Всего физической памяти: 4077252 KB
Графическая плата: Intel(R) HD Graphics 4000
    Версия: 10.18.10.3412
    Отметить: Не поддерживается
Доступная виртуальная память: 3638168 KB
Доступная физическая память: 1689940 KB
Имя пользователя: Vazgen
Имя системы: VAZGENTAICHI
Монитор:
    Название: Intel(R) HD Graphics 4000
    Разрешение: 1920 x 1080 x 60
    Бит на пиксел: 32
Название ОС: Microsoft Windows Vista
Папка Windows: C:\WINDOWS
Папка для временных файлов: C:\Users\Vazgen\AppData\Local\Temp\
Почтовая программа по умолчанию: Microsoft Outlook
    mapi32.dll
    Версия: 1.0.2536.0 (winblue_rtm.130821-1623)
Производитель ОС: Microsoft Corporation
Процессор: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~1696 Mhz
Сведения о Windows:
   Планшетный ПК: Да
   Начальная версия: Нет
   Media Center Edition: Нет
   Медленный компьютер: Нет
Сведения о сеансе:
   Тип загрузки: Обычный
   Завершение работы: Нет
   Сеть: Доступно
   Внутри Citrix: Нет
   Внутри VMWare: Нет
   Удаленный сеанс: Нет
   Удаленное управление: Нет
   Использование JAWS: Нет
   Использование Windows-Eyes: Нет
   Использование NVDA: Нет
Сведения об Acrobat:
   Изолирование программной среды: Отключить
   Связанная программа для чтения: Нет
   Multi-Reader с поддержкой Desktop: Отключить
Сведения об отображении:
   Ширина экрана: 1920
   Высота экрана: 1080
   Число мониторов: 2
   Число кнопок мыши: 2
   Мышь с колесом прокрутки: Нет
   С маркером Windows: Нет
   Двухбайтовая кодировка: Нет
   С редактором метода ввода: Да
   В программе для чтения с экрана: Нет
Сведения об учетной записи:
   Права пользователя: Администратор
   Управление учетной записью пользователя: Ограниченное
   Целостность процесса: Не определено
   Тип профиля: Отсутствует
Установленные приложения:
   Версия Office: Office 2013 32-bit
Файл подкачки: 4194303 KB
Часовой пояс: Московское время (зима)
Язык: Русский (Россия)
C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\Accessibility.api
    Версия: 11.0.9.29
Дата создания: 2014/09/12
    Время создания: 13:44:20
C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\Annots.api
    Версия: 11.0.9.29
Дата создания: 2014/09/12
    Время создания: 13:44:22
C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\IA32.api
    Версия: 11.0.9.29
Дата создания: 2014/09/12
    Время создания: 13:44:18
C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\PaperCapture.api
    Версия: 11.0.9.29
Дата создания: 2014/09/12
    Время создания: 13:43:36
C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\SaveAsRTF.api
    Версия: 11.0.9.29
Дата создания: 2014/09/12
    Время создания: 13:44:20
C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\SendMail.api
    Версия: 11.0.9.29
Дата создания: 2014/09/12
    Время создания: 13:44:20
C:\Program Files (x86)\Adobe\Acrobat 11.0\Acrobat\plug_ins\Updater.api
    Версия: 11.0.9.29
Дата создания: 2014/09/12
    Время создания: 13:44:22

My MacBook Pro won't go beyond a white screen, after I pushed the restart button. How can I get it to a login? I have routinely backed it up, but don't know how to bring that up, nor if I have a boot file on that external disk. Help!

My MacBook Pro won't go beyond a white screen, after I pushed the restart button. How can I get it to a login? I have routinely backed it up, but don't know how to bring that up, nor if I have a boot file on that external disk. Help!

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Export Quicktime movie in FCP comes out as a Final Cut Pro Movie File

Does anyone know why when I Export Quicktime movie in FCP it comes out as a Final Cut Pro Movie File? I can still play it in Quicktime and it's possible to set the Quicktime Player as the default software, but it still says in my finder window that it is a Final Cut Pro Movie File.
Does anyone know if there are any settings for the clip to come out as a Quicktime Movie instead? Thank you!

+Jim Cookman :+
+"The studio apps "brand" their exports. Actually kind of useful...+
In the words of the venerable Forest Gump, "Useful is as useful does" ... or something like that.
I actually use similar "icon" techniques in other areas of my workflow. But most of the time I just modify the file title for quick ID - I also use dashes & underscores to get things to stand out and stay at the top of lists etc.
But QT is my Go-To App for quick media reference and I have it set up to play almost all types off media when double clicked. I started doing it years ago when iTunes opened up every time I wanted to check a few seconds of an mp3 file.
I guess the best solution would have been for Apple to leave the "export FinalCut movie" option intact and simply add in an "export Quicktime movie" option as well. Or maybe add another drop down option for the tagging (branding).
At least we would have been able to make the workflow choices in-the-box rather than doing it with the OS.
Andy Neil,
I think using the OS is the better option rather than re-compressing your movie just so you can double click into QT.
best
g
Message was edited by: Goldfish

Premiere Pro CS6 - video noise in the exported file

Hi everyone,
Im trying to make the transition from FCP7 to Premiere Pro CS6. I edited my first project with Premiere Pro and exported the sequence. However I noticed that the exported file had more video noise than the original clips.
The material is shot by Canon 5D Mark III and edited natively in the Premiere's timeline. Then they are exported to ProRes 422. After noticing the noise I exported the sequence as "match the sequence settings" and it created the .mpeg file. Same thing, there was noise. I then tried another other formats of that same clip and transcoded the Mark III footage to Xdcam EX 1080p before sending to premiere. Same thing, no matter what I did.
The only way i got the exported file to look the same as original file, was to convert the files before sending to ProRes 422, then edit those files in Premiere in the sequence thats settings are XDCAM EX 1080p and then to export it to ProRes422.
Do you have any thoughts for this. The noise I'm talking about is not a huge amount of noise but definitely noticeable if you look the FULL-HD material.
I really hope there is some setting I missed. Im using Mac pro 2009 and Macbook pro 2011.
Thanks
Thomas
mac

Hi Thomas
Try exporting by enabling "Render at maximum depth" and " Use maximum render quality" in the export dialogue window.

Export a Final Cut Pro XML file problem about translation issue

When I export the final cut pro xml file, there is always translation issue like that 'Transition <....> not translated, Cross Dissolve used instead.'
Most of the transition type can cause the translation issues except the wipe and cross dissolve.
Is there any body knowing the reason? Is that OK?
By the way , I am using the trial version of cs5

Hey Ani_,
I've been working with Adobe products for a long time and typically when you come across an error that has anything to do with a XML file export problem its due to things such as effects you may have added in, color corrections, cross fades or any type of video transitions between clips. Remember your work flow should be
Import your footage into Premiere Pro
Name your clips (helps find things later on)
Place clips on time line in the order you wish (ONLY MAKE CUTS don't add anything, transitions color effects nothing)
Then once your clips are all placed on the timeline in your correct order you then EXPORT> Final Cut Pro XML
Now you can bring this into other programs for color grading or whatever else your going to do. You will notice you have no errors on the export.
Once your done doing what your doing to the clips in another program (for example: Divinci Resolve color grading) you can then export them back to your main project then add your effects and transitions.

Attempting to export file at 2880x1440, but premier pro changes it to 2048x1024

Hi all,
attempting to export file at 2880x1440, but premier pro changes it to 2048x1024.
I first noticed this issue when trying to change the frame rate of a file using twixtor, but now this is
a recurring problem.
Using a Mac Pro, with adobe premier pro cc.
Thanks in advance,
Best
Erfan

Okay, thanks Jeff, that makes sense.
I have now attempted this however I can't find the option for 5.2, also it is the frame size that I can't alter, I can however export at 60fps @ 2048x1024 and the final file plays fine.
Again I really appriciate you taking the time,
thanks,
Erfan

Audio problems when exporting files from Premiere Pro CS5

I try to post in English.
I have audio problems in Premiere Pro CS5 when exporting a film.
I cut an interview. The sound seems not to be synchronized when exporting a file. It doesn´t matter what file format I export. On cutting points the sound is different to the sound I hear in premiere. In premiere the audio sounds very good but in exported file I hear cracks on cutting points.
When I reimport the audio file an put it in the timeline the synch point is correct but the interview differs about 2 frames to the original audio in premiere.
The material was filmed on Sony ex3. The files are XDCam HD. I have updated the production suite.
Thanks for answers
Frieder

Also, make sure that you check the box marked "Export Audio" if you want a MP4 extension.

Exporting files from Final Cut Pro in Snow Leopard

I am using Final Cut Studio 2. I recently upgraded to Snow Leopard. Before the upgrade when I would export files from Final Cut the dialog box would automatically go to the last used folder location. Now, each time it goes to the system hard drive. Is there a way to fix this?
Thanks

Fix what?
Just choose the correct folder to which to export.

Premiere Pro CC inserting single frame into exported files

I have never had this issue before today.
A project I have been compiling off and on for several months was exported using AME via PPCC.
In previous exports this issue did not come up at all.
Here is the problem:
The rendered videos (using Apple ProRes 422 HQ, QT H.264, and MPEG2 DVD) have a single frame insert between two stills in a montage.
The previous render it appeared on a different photo a few seconds later in the program, like this:
Again, these are single frame artifacts not found in the timeline in PPCC. They only appear as "flash frames" in the exported video.
Anybody else seeing this? Is there a solution?
Thanks
Jeremy Praegitzer
Adobe Premiere Pro CS5/CS6 Certified Associate
TV Department Manager - Love A Child, Inc.

Hi Jeremy,
Thanks for posting on Adobe forums,
Please provide us details of your systems:
What is the OS and version ?
What is the Graphics Card installed on the system ?
How much Ram do you have ?
Do you use any external Hard Drive ?
and if you are using GPU Acceleration on Open CL, You can these issue on Export.
Please switch GPU acceleration on Software only mode, (if using cuda enabled card then Cuda )
Regards,
Sandeep

HT1338 how to export files to an external hard drive connected to my macbook pro?

i am unable to export files from my mac onto an extrernal hard drive. as i check the permissions of the hard drive, it says, read only!! kindly help me with this!

You can use a blank CD or DVD instead of your friend's hard drive.
Or you may be able to copy the files over the network. Is your friend's PC in the same location as your Mac, on the same wifi network (or wired network)? Connect the hard drive to the PC, then turn on file sharing on your Mac.
To turn on file sharing:
Open System Preferences
Click "Sharing"
Put a checkmark next to "File Sharing"
Click "Options…"
Put a checkmark next to "Share files and folders using SMB (Windows)"
Put a checkmark next to your user account, enter your password
Click "done"
Your Mac should now appear in the Windows "network", and you can use your friends laptop to browse the Mac files and copy over anything you need.

Soundtrack Pro Export Window unavailable

Just got soundtrack pro and am having trouble exporting files. The file/export option is unavailable (faded out) and I have no idea how to make it available. thanks

Nope. its just a single aiff file that I want to export as an mp3. I did try making a quick recording in a multitrack window, and was able to export that. I just can't export a single audio file.

Error messages during XML import of Project Pro 2010 files

Hi folks,
I'm trying to diagnose a couple of sick Project Pro 2010 files loaded from Project Server by saving them locally as XML files and then reimporting (not connected to the server during import). The anomalous behavior exhibited by both files
is that one takes 15 minutes to load from the server, while another takes over 20 minutes. These are not typical load times for this server. In both cases, Project consumes about 25% of the CPU during the load process. There's little network I/O
while this goes on, and when externally linked schedules are loaded to the cache, they load very quickly. Other than the long load times, the schedules appear to be behave normally, except for some very odd print preview behaviors in one of the schedules
that I asked about in a different thread (among other things, the default print preview start date is 17 years after the default finish date, and the finish date is about 11 years before the schedule actually starts).
The questions I'm asking here are about errors I see when I try to import the files exported as XML, and whether they might provide any clues as to what's causing the load time issues.
When attempting to import one of the files saved as XML, a pop-up appears that says, "The actual finish date is before some of the previously entered timephased actual work values. If you continue with this operation, Project will truncate
some of the previously entered timephased actual work values. To continue, click OK..."
When attempting to import the other file saved as XML, I get a series of pop-ups identifying a series of tasks that say, "The timephased edit will cause 'Develop Requirements Review Meeting Mi...' to start before 'Conduct Requirements Review"
finishes. As a result the task link cannot be honored. You can: () Continue. Keep the timephased edit and ignore the link. () Cancel. Ignore the timephased edit. (OK/Cancel/Help)".
Interestingly, both files contain external Project Server predecessor / successor links. In the case of the first file, the XML import just appears to strip those out. In the case of the second file, I get a long series of pop-ups (with
some buggy text inserts) in pairs. The first message in the pair is typically "An import error occurred. The element <PredecessorLink> in the <Task> element with <UID>=611 has invalid data. Verify that the file
name and path are correct, and then try again. (OK)", where the indicated UID varies. The second pop-up in the pair appears to have a buggy text constructor and looks like this, with "[stet]" indicating the apparent buggy text inserts,
"An import error occurred. The element [stet] Verify that the file name and path are correct, and then try again. [stet] in the 309 element with <UID>=7 has invalid data. [stet] ^4 (OK)"
In the second pop-up of the pair, the "xyz element" varies, but the "<UID>=7" reference and "^4" are consistent. In the XML, UID 7 appears to refer to a calendar, a task which includes a number
of entries similar to:
<TimephasedData>
<Type>24</Type>
<UID>7</UID>
<Start>2014-10-03T08:00:00</Start>
<Finish>2014-10-04T08:00:00</Finish>
<Unit>2</Unit>
<Value>PT8H0M0S</Value>
</TimephasedData>
... and to an assignment:
<Assignment>
<UID>7</UID>
<TaskUID>10</TaskUID>
<ResourceUID>-65535</ResourceUID>
<PercentWorkComplete>100</PercentWorkComplete>
which includes blocks like:
<TimephasedData>
<Type>2</Type>
<UID>7</UID>
<Start>2014-10-17T08:00:00</Start>
<Finish>2014-10-17T17:00:00</Finish>
<Unit>2</Unit>
<Value>PT8H0M0S</Value>
</TimephasedData>
Eventually, the second file also does load with no external file links indicated.
Again, I'm just looking for anything that might be a clue to the long Project Server load times.
Thanks in advance,
LP

Slow performance can come from a number of different things. Without knowing more detailed information about your setup or workflow, it's difficult to accurately troubleshoot.
-What kind of Mac are you using?
-What is your source format?
-Where is your source footage located?

QT Pro exported file is a faded white single frame

Similar Messages

Maybe you are looking for