FCPX "Retime to fit" bug

Hello.
I noticed a bug in new feature called "Replace and retime to fit". In my case I have some images on timeline with simple crossfade transition between them. If I want to replace one of images, I drug new one from Event library to timeline, drop it on old image and choose "Replace and retime to fit" option from pop-up menu. As expected, new image replaces old one and streches in/out to be exactly same duration as old one. But this scenario happens only if I have no transitions. If I have transition, strange things hapens: new image doesnt stretch (and its duration seems to be default FCPX duration for images), "in" transition moves on place of "out" transition and timeline become messed up, because new image's duration change move all other clips and brake all timings.
Now I have to put markers on audio line in places where transitions borders are, then do retime to fit, then manually move transitions to their places according to markers. Its a little bit annoing and spends a lot of time.
Do you have same bug? Or any ideas why its happening and how to fix it?
Thanks!

The more I investigate the worse it gets. Here are a few further observations:
When used locally my test page behaves as previously described except that I am now aware that Mozilla browsers print
the first page cropped as intended but fail to acknowledge the existence of anything cropped from the right. Internet
Explorer 5.2 is the only browser of mine which always behaves correctly in this respect in that it will print all four
pages if instructed to do so.
The online behaviour of iCab 4.2.0 is even more bizarre and undesirable than its local behaviour. It only prints a small
fraction of the page. So far my tests indicate that Safari, Camino, Firefox 3 and Internet Explorer 5.2 behave in the same way online as they do locally.
I have not printed every combination of pages - I have relied upon Preview to show what will be printed - however
the 20 prints I have done indicate that this method of testing is satisfactory.
I am using OS X 10.5.5 on a G4. In general all browser settings are similar - 100%, no headers/footers, minimum borders
etc - iCab margins are all set to 12pt (without this setting the combination of iCab and my LaserWriter 16/600 lose an
indeterminate amount of data around the edges.
I have now mounted a demonstration page at: http://links.open.ac.uk/browser/test/
The files can be downloaded for local testing from: http://links.open.ac.uk/browser/test/test.zip

Similar Messages

FRAME FITTING BUG? Indesign CC

I think this has been covered before for Indesign CS 6. (Re: Indesign CS6 Frame Fitting Options bug?)
I have this same bug in CC. We have recently moved from 5.5 to CC and it's causing a major issue. I do comic strip and multiple place comic strip pages into full page frames that have been set via frame fitting to being centred. Except it won't centre the images. See the CS 6 discussion above for more specifics.
Is there a work around yet for CC or is is still broken since CS6?! It's costing me money as i cannot go back to cs 5.5.

Hi, Pickory!
(Or Richard – whatever you prefer)
That was easy. You left your traces in the copyright statement of the script at Kerntiff ;-)
//DESCRIPTION: After place, V1.0.1.
//(c) 2013 Richard Bines kerntiff.co.uk
And posted about the function ourAfterPlace(e){} here:
Re: Indesign CS6 Frame Fitting Options bug?
After tracing all app.eventListeners with a for in loop, I could tell the jsxbin part of the script was using that function:
//RESULTS:
name
label
eventType    afterPlace
handler
function ourAfterPlace() {
    [compiled code]
id    6
isValid    true
parent    [object Application]
index    1
properties    [object Object]
isValid    true
Uwe

FCPX undo / auto save bugs + RAM Hog - Possible Fix?

Hi there FCPX users,
I have a 8-core 2010 Mac Pro with 16GB Ram and the stock GPU running Lion 10.7.2
I have been using FCPX since day dot, and have been overall very pleased with its super fast work flow and realtime capabilities.
I have completed over 100 3-4min edits with average project size of 50GB, and a bunch of wedding edits with approx 150-200GB project sizes. The issues I had with 10.0.0 - 10.0.1 were mainly FCPX quitting unexpectedly.
And now on 10.0.2 I have expereinced the well known auto save / greyed out undo bug. I have gone through all the steps via apple care which included:
Trashing the Prefs, repair permissions, check drive space / correct format, new user account and clean install of lion / Final Cut X.
I am still experiencing this issue. So yesterday I purchased another 16GB Ram totaling now to 32GB Ram, and I monitor the RAM usage via "Free Memory".
I Noticed that if my RAM is running low, I "free Memory" without quitting FCPX and continue to work as normal, and so far I have not yet experienced the issue again.
Dont know if this is a temporary fix, but it has worked for an hour long edit (approx 6-7 hrs without restaeting FCPX).
Also, I have noticed FCPX will eat up 16-20GB RAM quite easliy.
Not sure if this problem is related to RAM...
My 2 cents.

You have to really be conscious when you start a new project and how and where you manage your footage.
No one has complained more than I have about FCPX's quirky behaviors and it can be frustrating. I have worked with FCPX since day one, even tried to get a refund but couldn't. After using it for a while now, it is very easy to get used to how fast some elements are in editing and reviewing a lot a footage. But several things you have to make sure of that will keep the rendering speed up and less crashing happening.
First make sure that you can see how much space you have on your drives by right clicking in the main window of you screen and make the necessary clicks form the drop down menu. Make sure any drives you have been doing projects with lately are hooked up and do a secure empty trash. Its cool to see how much space you regain. 2) make sure that FCPX, Motion and Compressor (if you have those are installed on your boot drive).
3) Create a FCPX Projects folder on an external (FW800) with at least 75% of its drive space available if you do not have secondary drive installed in your computer. (Its very important to note that any drive you use for any aspect of editing should never be more 75% full, especially your boot drive.) This is where FCPX will log all of its operating files for all of your projects.
4) Either copy all of the other FCPX files from your main hard drive and paste then into the new folder you created. Then delete all of those files, as well as any Motion files too! (Do the same as you did for FCPX in the previous step)
5) If you need to move all of your music files to another drive as well. If its iTunes, you will have to tell iTunes where to look for the new files and it will populate accordingly. This will free up a tremendous amount of space. Make sure to delete them form the main drive.
6) Remove any junk programs form the boot drive (main) or move them to another drive if possible.
7) Now do another secure empty trash and watch your drive space return.
8) Now open up FCPX and make sure you only create projects on your new drive by clicking on that drive in the project window. Any older projects you can simply pull them to the other drive and you will be prompted on how to duplicate that project and all its files to that drive. Delete the other ones.
9) Only capture footage to you external drives. Save it there until you need it.
10) Create all new projects on the secondary drive and pull any footage you are working with on that drive as well. By keeping it all off the Boot drive FCPX will run much smoother and faster, especially if you have at least 16g of Ram, which I recommend.
So to re-cap:
1. Keep your boot drive lean. Delete anything you can move to another drive. Do not set up events and or projects to it...never!!!
2 Use you secondary drive for your project files and the video you are working with in your events.
3. Store raw footage on a FW800 drive ready to move to your secondary drive.
4. Use secure empty trash after all editing sessions when you are certain of your trash contents.
Doing these things have greatly increased much more consistently faster render times and much fewer crashes.
iMac 27 - 3.5gh - 16GB Ram - Quad i7 - 250SSD/1TBesata - External FW800 Drives
Good Luck

Custom fit bug?

First off, I really like being able to add bookmarks. This feature should really be in Adobe Reader too.
I just tried DE and when setting custom fit to 100%, then resizing the window, the custom fit popup still shows the pdf as being 100%, even though the pdf clearly is not.
Is there any way to lock the zoom at 100% ?
Thanks

No, there is no way to lock it. It is an interesting idea, but might lead to some curious UI issues. We will log this idea for consideration. Thanks for the suggestion!

How does FCPX handle audio?

Still working on getting audio exported to an AAF, and having problem doing this. So I need help understanding how FCPX is handling my audio.
When it's on the timeline, is it being conformed to the frame rate of the video?
When audio is exported, does FCPX force it to conform to the video frame rate in the project settings, audio properties, or both? Or does it allow the audio to export at whatever rate the original media is at?
I export an XML from FCPX, then open that with X2Pro and it makes an AAF file, but a report tells me that "Conform rates are not supported. The Conform rate at 01:04:49.23 has been ignored." So when I go to that timecode, all I see is video at 24p and a detached audio piece at 23.98. Why are these different? How would I fix?

FINALLY! Thank you God, this issue is resolved. Here's what I learned and had to do in case anyone else may be wrestling with this issue.
Apparently, FCPX handles audio like this:
• Adjusts varying frame rates to match the project property, e.g. if you drop footage that is 24, 30, and 60 all on a 24p timeline, FCPX makes them fit into 24p, it does not tell you or show you this, it just does it automatically
• It may handle detached audio a little differently. For instance, I had a 24p timeline, and there were 39 detached audio clips that were 23.98 because they were not attached to any video, so I had to reimport and sync, see the workaround below.
The X2Pro, program to convert FCPXML to AAF, spits out a report showing where all the conform errors were, 39 total, but still required calculating where exactly it was because it didn't identify precisely by frames. Once the offending detached audio clip was located, I then Expanded the Audio Components to see both the original and synchronized audio. Next I had to go find the external audio that had been synced, then do a replace edit on the old synchronized clip. This made the audio's video frame rate 24 and took away the conform errors! Then I had to sync up the new detached audio clip manually with the video clips above it.
Also, to get out to an AAF with X2Pro, it does not support retiming, so I had to strip out 22 instances of retiming.
Whew, glad that's all over! Hopefully this AAF will be pristine for my audio post supervisor to bring into ProTools!
Thank you all for your help and input along the way!

FCPX Crashes On Open- Render File Problem

Hello-
Right now I cannot open FCPX. I've been working on a 15 minute project with a moderate amount of effects.
Tried to edit today, and after opening, quits after trying to render.
Ran Pro Maintinance Tools which generated this crash report:
Effects Rendering
This crash appears to have occurred while trying to render effects on a clip. Possible causes for this include corrupt or unsupported media, a bad filter, a graphics card issue or too many filters applied to a single clip.
Suggested Actions
Use Corrupt Clip Finder to check for corrupt media.
If you are editing with long GOP media (H.264, HDV, MPEG-2, XDCAM, WMV, etc), consider letting Final Cut Pro X transcode them to ProRes for better performance.
Consolidate filters where possible. For instance, if you have multiple color corrections on a single clip, try to achieve the same colors with just one filter.
Remove third party filters from clips, or use Plugin Manager to disable them completely.
Make sure you are running the latest version of OS X.
Relevant Line
0 com.apple.Flexo 0x0000000100cbe2ce -[FFEffectStack(Retiming) retimed] + 30
I've deleted every render file.
I've deleted every thumbnail file.
I've trashed all preference files and caches.
Deactivated all filters within FX Factory.
No corrupt files found in Events or Projects folders.
I've uninstalled, and reinstalled FCPX 10.0.4
I've updated the OS to 10.7.4
My external LaCie Rugged has only two folders on it, Events and Projects. The entire drive is for one project.
Nothing. Crashes on open.
I'm completely out of ideas. Anyone who can help me solve this will have a slave for life...or certainly my deep gratitude.
Thank you.

This line from the Pro Maintainence Tools crash report seems to suggest it's crashing when it tries to render a "retiming" effect:
0 com.apple.Flexo 0x0000000100cc12ce -[FFEffectStack(Retiming) retimed] + 30
But I don't have any third party retiming effects applied, which means it might be crashing with the native FCPX retiming trying to render.
How could I possibly get at a built in effect to disable it? I have many clips retimed on this project.

[svn:fx-4.x] 14123: Two additions/corrections to 14076.

Revision: 14123
Revision: 14123
Author:   [email protected]
Date:     2010-02-11 09:37:26 -0800 (Thu, 11 Feb 2010)
Log Message:
Two additions/corrections to 14076. Add key mappings for layoutDirection="rtl" for spark list components. Correct type of keyCode variable so it is an uint rather than an int to match event.keyCode.
BitmapImage has a hard-coded layout direction="ltr".
QE notes: For layoutDirection="rtl" need to test LEFT, RIGHT, UP and DOWN keys.
Doc notes: None
Bugs: SDK-25330
Reviewed By: Hans
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-25330
Modified Paths:
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/containers/Accordion.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/ButtonBar.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/CalendarLayout.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/ColorPicker.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/Menu.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/MenuBar.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/RadioButton.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/Tree.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/colorPickerClasses/Sw atchPanel.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/listClasses/TileBase. as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/controls/sliderClasses/SliderT humb.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/core/Container.as
    flex/sdk/branches/4.x/frameworks/projects/framework/src/mx/core/UIComponent.as
    flex/sdk/branches/4.x/frameworks/projects/spark/src/spark/components/List.as
    flex/sdk/branches/4.x/frameworks/projects/spark/src/spark/components/RadioButton.as
    flex/sdk/branches/4.x/frameworks/projects/spark/src/spark/components/supportClasses/Butto nBarBase.as
    flex/sdk/branches/4.x/frameworks/projects/spark/src/spark/components/supportClasses/DropD ownListBase.as
    flex/sdk/branches/4.x/frameworks/projects/spark/src/spark/components/supportClasses/Slide rBase.as
    flex/sdk/branches/4.x/frameworks/projects/spark/src/spark/primitives/BitmapImage.as
Property Changed:
    flex/sdk/branches/4.x/frameworks/

This line from the Pro Maintainence Tools crash report seems to suggest it's crashing when it tries to render a "retiming" effect:
0 com.apple.Flexo 0x0000000100cc12ce -[FFEffectStack(Retiming) retimed] + 30
But I don't have any third party retiming effects applied, which means it might be crashing with the native FCPX retiming trying to render.
How could I possibly get at a built in effect to disable it? I have many clips retimed on this project.

Library Backups No Longer Being Created in 10.1.2

No matter what I do, Library Backups are no longer being created in 10.1.2. This is happening on all 6 of my production Mac Pros and iMacs. I can change the location of the Library Backup folder, but nothing is ever created in the new location. It's as if FCPX no longer knows how to backup libraries.
Some background...
We are working with Libraries and Media files on our XSAN Volume.
OSX 10.9.3
FCPX 10.1.2
We did not notice the Backups were not being performed until one of our Libraries had an issue and we could not find a single Backup of the library.
What I have tried...
Move Libraries to Local System Volume - Still No Backups.
Change Library Backup Location - Still No Backups.
Toggle Library Backup Location to No Backups and then Back to Backups - Still No Backups.
Ensure Proper Permissions on Library Backup Folder - Still No Backups.
Trash FCPX Preferences - Still No Backups.
ReInstall FCPX - Still No Backups.
I am at a loss at what to do next. I can't even see the backup process happening in console, or any errors that might give me a clue as to why it's not working. Short of trying to reinstall Mac OS on one of my production macs, I see no other alternative. Considering I'm having this issue across our entire production system, I'm wondering if this is a very serious FCPX 10.1.2 bug.
Is anyone else having these issues????

Tom Wolsky wrote:
Definitely not working as advertised. I made a new library. Imported some stuff. Futzed around. No backup. Waited more than an hour. Made a new project and always immediately a backup appeared.
I've had pretty much the same results trying to sort out what is going on since the 10.1.2 update regards Library Backups.
I'm getting no backups with newly created Libraries like others, tried all sorts of juggling acts in the new settings arrangement trying to find a way in.
What I have so far discovered is that Libraries are not created until a Duplicate Project is created of the original Project for the Library, then it appears to do as expected.
Seems like a bug.
Hope other users can confirm this.
Al

How to make a title randomly 'jumping around', not 'flowing'?

I'd like to create my own 'watermark title'.
Idea: the ©k.schluter slightly rotates a bit and randomly (done), and 'jumps' randomly across the screen.
Apply a 'random generator' to the titles x/y position, makes it moving/flowing.
What I want is an instant move to a new, random position.
I miss a parameter - which one?
Even better would be:
that title isn't onscreen all time, just 'now&then, here&there'
thanks in advance!

I would absolutely love to have conditionals. Also, more access to different kinds of data, like: the bounding boxes of text areas, groups, current states of emitters (all of these have dynamic bounding rectangles.) In the link behavior, a switched alternative to scale: a mathematical function... would be OUTSTANDING (as long as it can be relinked by "chain" in other behaviors. Shouldn't be too difficult to manage -- works just like a spreadsheet; one of the oldest formula applications on computers. I personally would rather see any conditional/language-like instructions implemented as JavaScript and NOT BASIC (or: !BASIC), or even as ActionScript (basically a specialized JavaScript) was implemented in LiveMotion (Adobe, ca: 2000-2003). I would like to have timers (setTimeout, setInvterval) that would not be interfered with by FCPX retiming and users stretching or collapsing effects in the storyline (an automatic Clip.stop() could be called at the end of the last visible frame in FCPX).
As for node-based apps, all we really need is a way to integrate Quartz Composer projects/modules into Motion -- with links into and out of the Quartz project. That would be pretty cool too.
There is, supposedly: FXPlug... but after 30+ years, I'm getting too old to learn another language (Objective C which looks just nasty to this old C programmer) and there is too little information (example code) online about developing plugins with it... at this time... for someone like me, that is. The last serious Mac Programming I did involved the "Toolbox" and "Quickdraw", and a 16/32-bit 68K Motorola microprocessor. By the time the G3's came out, I had pretty much moved over to web technologies (Java, JavaScript, PHP, etc.) Bottom line: I need more help than I can find and the people who are actually developing these things aren't sharing.

Any tricks to speed up export/share?

I have a two and a half minute video that is nothing but static title screens over audio, changing for each of five 30 second pieces of audio. I am exporting it so I can post it to YouTube (Share to YouTube), and it is going to take over an hour and a half on my Late 2009 MacBook. This is completely unacceptable. On previous, slower machines, I could export radio ad videos like this and upload them to YouTube in a fraction of this time.
What is it encoding? Geez.
Does anyone know any tricks for speeding up this process? I even tried setting it to the lowest resolution on share (it's just audio, so it doesn't really matter how "great" the title text looks)... Same thing.
Very frustrating, since I currently do not have home internet, and I have to bring my laptop down to a WiFi hotspot to do uploading.

For years, I have used Final Cut Express, importing DV, HDV, then most recently, AVCHD in to Apple Intermediate format for editing. I would export a reference .mov, and then convert that in Visual Hub for uploading. When Visual Hub dropped out, I just started using QuickTime. It was annoying, because you had to go in to the .mov and edit the aspect ratio to make 16x9 show up properly (fortunately, there was an Apple support doc on this, else I would have just assumed it was broken).
I love FCPX except for the bugs, and the speed. I am only a few weeks in to using it, and so far have used it for two TV ads. I am still trying to understand Proxy and Optimized. I have no internet access at home, currently, so the help files are not available (I had to print to PDF the online version for reference). I have been importing with Proxy, assuming it gives me something quicker/easier to edit, and on output, it would go back to the source AVCHD files and emit full resolution 1080. At least, I hope it works that way.
In my projects, as I move forward, I will be shooting only in 1080 and trying to output 1080 files for TV and for YouTube. This, alone, would take more time even if everything else is similar.
But geez, the time it takes to output a 30 second TV ad was just mind blowing :( I had a 3 minute video of a band playing a song, and it was taking almost two hours to export and post to YouTube!

Slow motion and frame rate and shutter speed

I have two cameras that record 60i and three that use 30p. Neither of the 60i cameras has a 30p option (one has a pf30). If I understand how FCPx handles this, if I drop both frame rates into a project, I get 30p out, correct? In effect de-interlacing the 60i footage to 30p. Is it best to import the 30p footage first to set that frame rate so that the 60i gets rendered to 30p?
We're producing a fishing DVD so good quality motion footage is important. This is an instructional DVD so I will be using some retiming to slow footage down to illustrate key points in the instruction.
I've read a lot of stuff on 1080i 60i vs. pf30 vs.30p vs. 24fps and benefits of using 720p vs. 1080i. Also looked at information on slow vs. fast shutter speeds.
So, the bottom line to get the best motion results for the DVD, I should be shooting at best bit rate possible, use 1080i 60i or 30p depending on the camera and let FCPx set everything to 30p. Correct?

For the 1080/60i media, it is best to have FCPX conform it to 30p (29.97p). [30p is a real timing: 30 exact frames per second, but it is not broadcast compliant. 29.97 is quite often simply referred to as 30, just for simplicity and/or laziness. The final decision for which to use rests with you. Also note, like "30 fps", 60 more often refers to 59.94 fps... for the same reasons.]
As for your target being DVD: DVD is always 480 lines whether it is anamorphic (16:9) or standard 4:3. If you would like to have "enhanced" slow motion, my recommendation would be to shoot in 720/60p (which is genuinely progressive "60" frames per second) and will give a slightly better edge on slow motion effects (retiming). That said, FCPX retiming is usually quite good no matter what the frame rate (frame blending recommended over optical flow [which tends to give a "morphing" effect when pushed too far].) 1280x720 frame size will give you plenty of downsampling resolution for DVD as well. [I *believe* that FCPX will use all of the 60fps available from the original video in retiming, even if the frame rate of the project is slower than the original media; so, 720/60p conformed to a 30p project and retimed to 50% will use every frame of the 60p slowed down by half... (somebody correct me if I'm wrong!)]
Best bitrate is also an important feature, but that is not due to the choice of format as much as that provided by the camera itself. Bitrates out of the camera may be relative to the frame size (they are in my consumer camcorders). A common consumer grade camcorder will top out at a bitrate (for 1080) somewhere between 17.5 and 22.5 Mbps, whereas an HD capable DSLR will usually top out at (easily) *twice* as much (45Mbps average from my Canon T4i) or more. Furthermore, the DVD standard imposes framerate restrictions (max is somewhere between 5 and 8Mbps -- the software that creates your DVDs will usually transcode for best bitrate, so not something you really need to bother with - just set the transcoder to best possible quality and provide it with the best quality video that's reasonable.) Whichever camera provides the highest bitrate should be your "main" camera.
As you may have discovered: another factor for a quality video regardless of camera is shutter speed. If you set the shutter speed too high (faster than twice the frame rate) then you will have "stuttering" issues (there will be "gaps" from still frame to still frame). Keep the shutter speed at the same or no more than twice the frame rate: e.g., for 1080/30p (target) the shutter speed should never be more than 1/60th of a second (I'll use 1/30th, 1/40th, or 1/50th usually). I haven't shot a lot of 720/60p, but I think I would still keep the shutter speed at between 1/60th and 1/120th exclusively [that is -- I wouldn't go as high as 1/120th or greater... but that's me... you should experiment for best results for you. If this creates exposure issues, then consider neutral density filters or circular polarizing filters to help bring scenes into exposure range (via aperture or iso or both.)
HTH
Good luck! Have a good shoot!

Recording with audio playback slowed down 65% what speed do I need to speed the video back up to to get it into real time?

Ive recorded a test video with audio/music playback slowed down 65% what speed do I need to speed the video back up to to get it into "real" time?
If I'd slowed the audio playback down 50% I would make the video 100% faster.
If I'd slowed the audio playback down 100% I would make the video 200% faster.
So its obviously somewhere inbetween speeding up by 100-200%
Sorry but its melting my brain today and I cant remember the calculation.
thanks

hey all
Thanks for the advise on this. I will explain a little more what am have/am intending to do.
I have used Audacity to slow the song down (Effect>Change Tempo)
Audacity will allow me slow the original song down by up to 99% (Or anything in-between up to 3 decimal places)
Unfortunately I am working to a time restraint of 12 minutes per clip (as my DSLR will only allow up to a 12 minute clip).
The song at normal speed is 4 minutes long.
Originally I slowed the audio down by 50% (Making the audio 8 minutes long), lip synced to it using a rasta blaster and recorded the video using my DSLR at 720p 50fps.
I then imported the video and audio I had been lip syncing to into FCPX.
I sped up the video by x2 (equivalent to speeding it up 200%)
Retime>Fast 2X
Layered the PROPER normal speed audio back over the top and all was fine.
Test video complete.
(You can ignore the 65% slowed down audio I mentioned earlier if you like, that was just an example of a slower than 50% audio test)
Firstly what I really want to do is to be able to slow the AUDIO down as much as possible (But still within the restraints of only being able to adjust FCPX retiming within a whole 1 percentage in the final video edit), but have the AUDIO of the song as near to/under 12 minutes as possible.
I will then re-record the video again to this new slowed down audio.
Secondly I will speed up the video from 12 minutes to 4 minutes.
Thirdly I will layer the correct 100% Normal AUDIO on top.
The FINISHED video should then look like everyone is wizzing around at high speed but the guitar playing/lyrics look like they are being played/sung at the normal speed.
Whatever happens (due to the constraints of FCPX) I need the calculations to work so that FCPX is retimed exactly to a whole 1% for the final video to sync up correctly.
So what I need to know in a nut shell is:-
What calculation do I use to work out the percentage to slow a 4 minute song down to a 12 minute song?
What calculation do I use to work out the percentage of how much I need to then speed the 12 minute video up to turn it back into a 4 minute video?
My mind is melting

Indesign Bug with Auto-Size and fitting in Anchored frames

Hi,
Steps to reproduce:
1. Create a text frame with 2 Anchored text frames with the same width.
2. Make the anchored frames Auto-Size --> Vertical only
3. insert text to the first frame, when type enter to the next line the frame become higher but the next frame remain in the same position. just after typing the first character in the second line the next frame adjust in the right position.
4. The same happen when pasting text that make the frame bigger.
5. The same happen without Auto-Size when fit frame to content.
Does anyone knows about it?
Any idea how to bypass?
Thanks

This is a user to user forum with "some" Adobe staff participation, report bugs at this link
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform for bugs or feature requests

Fit Frame to Content Bug in InDesign CC? Keyboard shortcut not working

Using InDesign CC 9.1 in Mountain Lion, recently installed and has been working fine except I noticed that the keyboard shortcut for Fit Frame to Content won't work, even though the other frame fitting shortcuts work. I searched this forum and elsewhere to see if there was any reported bug for this but came up with bubkis.
When using the contextual menu option or toolbar button for Fit Frame to Content I don't have any problem. I thought perhaps my own set of shortcuts had overridden this default shortcut somehow so I reverted to the default set without any luck. I quit and re-opened ID with the default shortcut set, no luck either.
In the Keyboard Shortcuts menu options, when I try to assign Opt-Cmd-C it does say it's already assigned to that function. I'm at a loss here to understand why this one particular function isn't working as a shortcut. Any ideas why? What can I do? Thanks.

It's working for me in InDesign CC on the same operating system.
Here's a couple ideas:
Make sure there's not a Mac OS X system shortcut already set to this shortcut. Go to System Preferences > Keyboard Shortcuts and check all the tabs for existing system shortcuts (I didn't find any but maybe you had set one). InDesign CC now gives preference to the system.
You could also try restoring your InDesign preferences.

FCPX Text Animation Bug

Hi Everyone!
I'm working through a 30+ minute video sequence showing photos and video clips of an event I attended recently. This is my first foray into FCP.
I've come across a rather weird text animation bug, where text is animated onto the screen incorrectly.
So what I've shown above is one typical text box I've added for narration, using the "Typewriter" effect. Of course, the text should render (appear) on screen one character at a time, but I have been getting a random number of characters at the end of the block that do not animate. The only way I have been able to get these blocks to animate correctly is to add enough spaces to the end of the text to force FCPX to rerender the block correctly.
At some point in the future, this bug resurfaces, and I have to delete the spaces, and re-add them, to get the block to render and animate correctly once again.
If I go and "share" the resulting sequence, the bug is rendered into the sequence.
Deleting the text block, and adding a new block, doesn't seem to help.
I have reported this as a bug to Apple.
It's not just the Typewriter text effect doing this. As far as I can see, it is every text effect bar the lower thirds (so far as I can see).
Any ideas on how to get around this? Does anyone else experience this bug?

I'm starting to pull my hair out on this one. My video is essentially ready for final rendering, but I've hit a snag re the rendering itself.
Check out this image I've just snapped:
http://www.becsta.com/pics/skitch/FCPvCompressor-20110918-225758.jpg
On the left is the Compressor 4 preview pane. Note that the text animations are screwed up, just like the screenshot at the start of this discussion.
On the right is the FCPX preview pane, showing that the rendering is complete and correct. All I did was select "Send to Compressor", and skipped the Compressor timeline up to review the same frame.
These text blocks are using the "Typewriter" effect.
So, what do I do to fix this once and for all?
Build it from scratch in Motion?
Any ideas?
/cue Princess Leia voice/ Help me Obi-Wan Kenobi, you're my only hope!

FCPX "Retime to fit" bug

Similar Messages

Maybe you are looking for