Odd Clipping
I'm noticing some pronounced clipping when trying to play some of my songs in iTunes. There's no clipping when I try playing the same files in Audacity or WMP, so I think the actual file is fine; iTunes is just causing playback issues. With other songs I don't notice clipping and I can't imagine why. Does anyone know how I can correct this? I have (I think) the latest version, iTunes 8.0.1.11.
In iTunes Help: "If the song doesn't sound right when you play it, you may need to change your QuickTime settings. Choose Start > Control Panel. Then double-click QuickTime and click the Audio tab. Click "Select Audio Playback and Recording Devices" and choose a different device. If the song still doesn't sound right, try turning off the iTunes Sound Enhancer in the Playback pane of iTunes preferences."
Similar Messages
-
Uploading stills giving odd clip length for time laps.
I'm putting together a timelapse movie with about 6K stills. I have them gathered in groups of 600. They're all about 4 megs. I'm taking them into a sequence at 24 fps. Why is my clip coming in at about 6 sec's? Then another group of 600 stills coming in at .04 sec's??? Driving me crazy. I'm a photographer and total nubile in Premiere, so, go ahead and laugh but please let me know what the hell's going on.
OP said "They're all about 4 megs"
Does the latest PProCC still have problems with using "many" large pictures?
To the OP (Original Poster) if Jim answers "yes" to my question, read below... if he says "no" just ignore this
Some of this is from the Premiere Elements forum, but the idea of sizing pictures is the same for PPro or Encore
Pictures that are "overly" large may cause video editing problems
Photo Scaling for Video http://forums.adobe.com/thread/450798
-HiRes Pictures to DVD http://forums.adobe.com/thread/1187937?tstart=0
-PPro Crash http://forums.adobe.com/thread/879967 -
Project renames sequence and all clips in the sequence when a clip is added
My project is renaming my sequences and the clips in those sequences whenever I add a clip. For example, I have a sequence called "dance section 2", which contains 20 some-odd clips with various names. When I add a clip named "drop from above", the name of the sequence is changed to "drop from above", and the name of every other clip in the sequence is also changed to "drop from above" (video, audio, stills, everything). When I add a clip named "spins", all the names are changed to "spins".
The name of the sequence is changed in both the timeline and the browser, but the names of the other clips are changed only in the timeline. In the browser, they keep their old names. The exception to this is the last clip added before the name changer. For example, if I add "drop from above" to the sequence, and then add "spins", the clip named "drop from above" is renamed "spins" in the browser as well as in the timeline, but the other clips are renamed only in the timeline.
The clips in the sequence also keep their original content - so the sequence looks the same as it did before, but all the names of the clips are changed.
This is only happening in one project. All of my other projects are working fine.
I've tried restarting and deleting preferences. I've also looked at the autosave vault for the project. The backup projects saved after a certain time all behave the same way, and the projects before that time all behave normally. I can't imagine what would have caused this, though, since I've been working on this project all day and nothing's happened to my computer or hard drive or anything.
Also, there are no freeze frames at the beginnings of my sequences (I read another thread with a somewhat similar issue and getting rid of freeze frames seemed to help that person).
I'm in FCP 7.0 on a Macbook Pro.
Thanks in advance for your help!Welcome to the discussions...
I've had this happen. My guess is that it's related to round-tripping to/from Color, but I can't be sure. IMHO, the sequence is corrupted. I just dealt with it for a while, then rebuilt it by making changes from an earlier version.
Sorry I don't have a better solution, but at least you know you're not alone.
Patrick -
Clipping sound in a song i purchased
i'm hearing this odd clipping noise, sort of like a pop kind of, in a song on an album i recently purchased. it's like a split second after a high hat sound (drums). itunes support resent me the download but the noise is still there. i've had a couple people listen to it just to make sure i wasn't going crazy and everyone seems to hear it. i can't imagine it's in the actual recording (but maybe?), however i haven't had a problem with either downloads. basically i'm just wondering if there's something i may not be thinking of that could be causing it, if anyone has any advice on that? i'm hearing it on my computer as well as my phone.
i may be making too much of it, it just seems a little too noticeable for it to be there and is distracting. any suggestions are appreciated. thank you.i can't imagine it's in the actual recording (but maybe?),
Seconyers,
It could be a defect in the original mastering, but is more likely to be an audio artifact that crept in as a consequence of the encoding process.
Your main choices are to live with it or insist on a refund on grounds of being defective. If you want to experiment for a couple of bucks, you can buy the same song from another online music store that sells in a different format (MP3 or one of the lossless formats). -
Two different clip settings on one timeline
Hello All,
I am combining clips shot with two different cameras on one timeline.
For best quality results of the image, what sequence settings and then export choice should I use? It is a 4 min film that I would like to export as QT or MPEG-4 movie file.
In FCP, both clips look crisp and sharp. I tried various export formats in compressor, but the output always returns the clips from camera 2 de-interlaced (the edges of objects are not smooth but zygzagy).
Clip settings from camera 1:
frame size: 1920 x 1080
video rate: 23.98 and some in 29.97
compressor: Apple ProRes 422
Pixel Aspect ratio: square
Field dominance: None and some have Upper (Odd)
Clip settings from camera 2:
Frame size: 720 X 480
Video Rate: 29.97
Compressor: DV/DVC PRO- NTSC
Pixel Aspect: NTSC- CCIR60
Field dominance: Lower (Even)
Thank you for any suggestions,
Izabelahazel - if you're making a DVD, then you're going to be using NTSC SD settings - so that's the "send to" compressor - and in compressor you will choose a DVD format, etc.
But if you are creating a digital file to play from a laptop to a projector, I am suggesting you set your frame size to the most common pixel width of most projectors; 1024 x 576 precisely so you do not have to make any adjustments on the projector. You are basically running VGA out (or DVI) into the PC input of the projector and running a quicktime or wmv file and the projector will not have to re-map the image. All of my editing takes place on a mac, and quicktime is my fav but in the corporate world I often have to produce PC friendly files that they take and project with conference type LCD projectors. I do it all the time - this is a good way to go if you are in a similar position.
On larger scale productions, we stay mac based and use high-end projectors and switchers, etc. But when you are handing your edits off to normal corporate meeting attendees they often try to embed them into powerpoint or at least run them in windows media players. If this is the case for you, then I am saying create custom frame of 1024 x 576 if your content is 16:9. -
Can see artwork in navigator but no on artboard, why??
when i open a particular file i can see the artwork in the navigator but not on the artboard.. (in CS4). If i hover over the artboard i can see the outlines of the art but can't seem to be able to view the whole artboard to see the entire file... what am i doing wrong? thanks!
what does the layer palette say to the matter? Can you select the items there and have them show up persistently? Surely something with an odd clipping mask or knockout group somewhere. Also, check of course the View settings in the menu. maybe you have inadvertently toggled something for worse.
Mylenium -
What are the "rules" regarding render files?
OK...one PO-ed user here, wondering *** is going on...
I've always said that FCP is about as weak as an early version of Media 100 when it comes to render files. You can search my posts (not that you'd want to...), and find that I've been complaining about every system I regularly work on losing render files like a 6 year old loses mittens.
However, it's hit the fan, thus this post. I work on a half-hour tv show. Let me mention that we shoot and edit in XDCAM EX 1080i60; this is notable as yes, I know, rendering in long-GOP codecs is slow. Oh, I know it...
Anyway, this past Tuesday I dilligently rendered my composite sequence, and the broadcast output sequence, and then exported the broadcast sequence for feed. All was well.
Today, I opened up the project so I could make final archives and web exports of the individual segments...and guess what? Gee, Wally, the entire sequence was, you guessed it, unrendered. Where did those pesky render files go? Well, I figured I'd try something I never try, and that was to reconnect them. Hopeless, right?
As it turns out, yes, hopeless...because when I navigated to the Render Files folder, there was a grand total of 11 render files for this particular project. Now, I don't change my System Settings at all...I like where things go, I have my media volumes set up, everything should be hunky-dory, no?
So to get to the heart of the matter...what process is tossing render files? Why are they disappearing from my hard drive?
I have folders from projects from 2 months ago that have some render files in them, but I don't have the render files my system (supposedly) created on Tuesday!
Anyone got any ideas?Hey, Shane, as soon as I saw you posted I began to get deja vu all over again, as we had a discussion about losing render files which, yes, caused me to stop nesting...for the most part. So yes, here we again have evidence that the "nesting behavior" coding team took off early the day they were supposed to be bug-fixing...but i digress.
I nest only when necessary...generally, we edit "packages" (your acts) and then I get em, do whatever audio and color correction time allows, and copy and past them into my complete program sequence.
However, when all is well, good, revised and approved, I "edit" that complete 22:10 sequence into my "BS" sequence (you might guess, Broadcast Safe), which has the bars n tone requested by the broadcast mothership, and where I apply a light Broadcast Safe filter and a touch of compression to the audio. So I guess my only question here it...are you suggesting that I just splat-A my edited sequence and apply the filters to the gazillion-odd clips individually? -
Premiere Pro CC 2014 - Bug Report
Just thought I'd report on a ton of bugs that hit me after using CC 2014 on a project though I have no idea what is causing any of them except most likely the underlying Mercury and/or Lumetri Deep Color Engines.
The BIGGEST ISSUE was FLICKERING, most of the other bugs happened in trying to find a way around it. Seemed to experience these problems on two different computers.
Computer 1: Windows 7, Geforce 670 (from memory)
Computer 2: Windows 8, Geforce 750M
Workflow: 3 minute HD music video edited in PP mainly using multicam, direct link grade in Speed Grade utilising the new master clip and clip grade, effects (Red Giant's Universal's diffuse glow, glimmer and Knoll Light Factory, plus RGB curves) and overlays then applied in Premiere with a couple of shots sent to AE for object removal.
Bugs:
Applying perhaps a range of effects seem to results in the image flickering (tried rendering it in software, CUDA and OpenCL engines) and oddly enough only in the second half even though the clips where at same location, same take, same effects and lighting. Often removing the Universal diffuse glow or glimmer effect seem to remove the flicker though the odd clip that didn't have it applied would also randomly flicker so seems like the render engine is freaking out.
At one stage the export resulted in white flashes and even effects not being applied and randomly appearing on/off.
Another time on export the effects were applied but the footage disappeared entirely
Anti-flicker under the motions tab would not remember/display it's value upon loading, displaying 0.00
Anti-flicker on export if perhaps adjusted again after loading the project produced pure RED image on export
Sending a clip to After Effect from Premiere often would not render in Premiere (would produce error, blank or crash) so I had to render proxies in After Effects for it to come across into Premiere. Never had to do this in the previous version of CC.
Overlaying footage and using Screen resulted in a darker image on one clip, maybe something to do with Lumetri applied to a master or independent clip and the order in which effects are being calculated.
Premiere crashed often, usually if it was struggling to display image and then you tried to follow up with commands, move the timeline position or save for instance
Premiere if it didn't crash occasionally it would have laggy play back, and this was just trying to play a single DNxHD clip with no effects applied in a native timeline.
If you need any more information to help fix these bugs let me know and I'll attempt to deliver.Adobe, I can't believe you're so out of touch on this issue that you are telling people to try removing curves effect. At this point I'm beginning to think that you are deliberately misleading people to downplay this issue. We have told you multiple times that we are a studio with 5 editing stations, all different configurations and graphics cards, and have experienced the issue on several projects and varying levels. This is a MAJOR bug that is crippling business everywhere, that you can read about on several forums, and you are still tell people to 'try removing curves'. For simple edits that don't use many effects, no problems (which is why there are not more complaints because must people do simple edits). As soon as you pile on colorgrading and effects the flickering starts.
For the rest of you folks trying to get through this, don't waste your time like we did trying to self diagnose the problem removing/changing effects and trying different combos. It will go away one minute, only to randomly return the next. The ONLY true solution we have found is to go back to CC pre 2014. For those of you in mid-project, that means rendering out your work now, maybe without effects if you have to, and start over.
Don't waste your time trying 'removing curves' like Adobe has suggested. -
Crash on quit when switching resolutions.
In case there are others out there needing to switch resolutions and have a full screen app running on the desktop with OS X 10.8 and Director 12.
I thought I would share this experience and offer a way of fixing it.
If you use BuddyAPI to change the screen resolution of your project and set the "Full Screen" option in the build settings for your projector. The projector will crash when you use the halt command.
This only happens on OS X 10.8 and you projector is built with Director 12. Director 11 will not have this problem. But as we all know custom fonts will not display properly on OS X 10.7 and 10.8 when the projector is built with Director 10, 11 or 11.5.
By the way it is also important not to use the older baSetDisplay as there will be color palette problems if you have used any art that have reduced palettes.
Rather use baSetMultiDisplay, it works like a charm.
if (the platform contains "Windows") then
isOK = baSetMultiDisplay( "primary", 800 , 600 , 32 , 60 , "temp" , 2 )
else
isOK = baSetMultiDisplay( "primary", 800 , 600 , 32 , 75 , "temp" , 2 )
end if
The fix for the crash is also with the help of BuddyAPI.
If you not set the projector options to "Full Screen" when you reset the monitor's resolution the menu bar will remain, so use BuddyAPI's baHideTaskBar(2) to get rid of it. Now it no longer crashes on Quit.
Hope this can save someone some grief.
Cheers!
Update:
I forgot to mention that now you will the menu bar will appear at the top of the window. To make it dissapear add the following code to your StartMovie script or at the end of your BuddyAPI resolution switch call:
baHideTaskBar(2)
P.S. The reason for the crash however is squarely in Adobe's court as you can see by the crash log below.
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000009eb435c
VM Regions Near 0x9eb435c:
MALLOC_LARGE (freed) 00000000092bb000-00000000093fb000 [ 1280K] rw-/rwx SM=PRV
-->
VM_ALLOCATE 000000000b9f9000-000000000b9fd000 [ 16K] rw-/rwx SM=PRV
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x9764b258 fixupSelectorsInMethodList + 27
1 libobjc.A.dylib 0x976419f4 _class_getMethodNoSuper_nolock + 107
2 libobjc.A.dylib 0x976413d1 lookUpMethod + 235
3 libobjc.A.dylib 0x976412e1 _class_lookupMethodAndLoadCache3 + 47
4 libobjc.A.dylib 0x97640ac1 objc_msgSend + 81
5 com.apple.HIToolbox 0x93d949bb _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
6 com.apple.HIToolbox 0x93c1c394 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
7 com.apple.HIToolbox 0x93c1b780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
8 com.apple.HIToolbox 0x93c1b5ca SendEventToEventTargetWithOptions + 94
9 com.apple.HIToolbox 0x93dd6204 SendMenuPopulate(MenuData*, OpaqueEventTargetRef*, unsigned long, double, unsigned long, OpaqueEventRef*, unsigned char*) + 370
10 com.apple.HIToolbox 0x93def1fd PopulateMenu(MenuData*, unsigned long) + 92
11 com.apple.HIToolbox 0x93dedd93 FindItemByCommand(MenuData*, unsigned long, unsigned char, unsigned long*, MenuData**, unsigned short*) + 47
12 com.apple.HIToolbox 0x93dedf85 FindItemByCommand(MenuData*, unsigned long, unsigned char, unsigned long*, MenuData**, unsigned short*) + 545
13 com.apple.HIToolbox 0x93dedf85 FindItemByCommand(MenuData*, unsigned long, unsigned char, unsigned long*, MenuData**, unsigned short*) + 545
14 com.apple.HIToolbox 0x93dedc1f _GetIndMenuItemWithCommandIDWithOptions(MenuData*, unsigned long, unsigned long, unsigned char, MenuData**, unsigned short*) + 110
15 com.apple.HIToolbox 0x93c6b761 GetIndMenuItemWithCommandID + 99
16 com.apple.HIToolbox 0x93ecc757 InvalidateLiveMenu() + 82
17 com.apple.HIToolbox 0x93ecc8de RemoveWindowFromWindowMenu(WindowData*) + 58
18 com.apple.HIToolbox 0x93c33634 _ShowHideWindows + 816
19 com.apple.HIToolbox 0x93c332ff ShowHide + 44
20 com.apple.HIToolbox 0x93c0d1ac WindowData::Destruct() + 160
21 com.apple.HIToolbox 0x93c21ad8 HIObject::__Deallocate(void const*) + 34
22 com.apple.CoreFoundation 0x96e545d9 CFRelease + 873
23 com.apple.HIToolbox 0x93c21934 HIObject::Release() + 20
24 com.apple.HIToolbox 0x93eb85e6 DisposeWindow + 29
25 com.adobe.director_12_0.IMLLib.framework 0x0063a1a4 imWindowDispose + 247
26 com.adobe.director_12_0.IMLLib.framework 0x0063a257 0x600000 + 238167
27 com.adobe.director_12_0.IMLLib.framework 0x0061eb8d imShutDown + 100
28 com.adobe.director_12_0.ProjLib.framework 0x000aadfd 0xa7000 + 15869
29 com.adobe.director_12_0.ProjLib.framework 0x000a9bae ProjectorMain + 1165
30 D&D2_stub_SP_v1_2 0x00002d5f 0x1000 + 7519
31 D&D2_stub_SP_v1_2 0x00001d29 0x1000 + 3369
32 D&D2_stub_SP_v1_2 0x00001c58 0x1000 + 3160Thank you everyone for your comments and help. We had to push the release back two weeks for many reasons, some of them this issue.
But I thought my solution would be good to know for people. For the record I was attempting to edit at 4k with imported RED files converted to optimized media. What I didn't realize is that some of those clips were actually shot at 5 or 6k. I think that was one problem in and of itself, so I converted my projects to 1080p. Still got memory errors though.
So I think what solved the issue was when I flushed the cache by moving it outside the library. I think FCP had crashed while doing background renders from choking on some of the odd clips. I believe that corrupted some of the cache system, and wasn't fixed even when regenerating the cache files.
So I went to project settings and set the project cache to be outside of my project file in a folder I created. When doing so you are prompted to decide whether or not to move your current cache. I didn't, and this forced it to re-reender all those clips (but not the original optimized or proxy media). This seemed to clear up every problem I was having with Final Cut Running Out of Memory problems. I bet it was the cache, but could have been related to the mixed resolutions.
So I thought this might helpful to others searching this forum, and thanks again for everyone's help! -
Crash on quit due to background processes
Please help, I have a deadline soon. FCPx is crashing every time I quit. It hangs on stopping background processes when I can not see that there are any, and I have them turned off.
I have done a safe boot, wiped preference, and even created a completely new user on the mac. Nothing helps. Any suggestions would be greatly appreciated.Thank you everyone for your comments and help. We had to push the release back two weeks for many reasons, some of them this issue.
But I thought my solution would be good to know for people. For the record I was attempting to edit at 4k with imported RED files converted to optimized media. What I didn't realize is that some of those clips were actually shot at 5 or 6k. I think that was one problem in and of itself, so I converted my projects to 1080p. Still got memory errors though.
So I think what solved the issue was when I flushed the cache by moving it outside the library. I think FCP had crashed while doing background renders from choking on some of the odd clips. I believe that corrupted some of the cache system, and wasn't fixed even when regenerating the cache files.
So I went to project settings and set the project cache to be outside of my project file in a folder I created. When doing so you are prompted to decide whether or not to move your current cache. I didn't, and this forced it to re-reender all those clips (but not the original optimized or proxy media). This seemed to clear up every problem I was having with Final Cut Running Out of Memory problems. I bet it was the cache, but could have been related to the mixed resolutions.
So I thought this might helpful to others searching this forum, and thanks again for everyone's help! -
Help Needed With "Extend Marker" Function Not Working
I have several Clips and used the "DV Start/Stop Detect" function to find the time code breaks, which seems to work well. I've now got a clip full of Segment markers.
The problem arises when I try to use Extent Markers "Option + `" to make subclips. When I put the play head on a subsequent marker, the Marker/Extend function is grayed out.
Extending a marker that I have created using the M key works perfectly.
Why can I not use the Extend function on Segment Markers?
Any help on this is greatly appreciated. I have 30 odd clips that I need to set up segments for, and doing it manually will add hours to my workload.
Thanks
Gary
Dual G5 2.5 GHz Dual Core, 2.5 GB RAM, 500 GB HDD Mac OS X (10.4.3) Final Cut Studio FCP 5.0.4Thanks for the reply.
I am completely aware of items 1 through 3, and never Extend markers in the Timeline. Only the Viewer.
To perform an Extend Marker and avoid headaches, load the captured clip - the one with the video icon in the Browser - into the Viewer. Then, as you scrub along in the Viewer, Option-` as needed.
That is precisely what I am doing.
To Extend the marker I first double click the clip to load the entire clip into the Viewer, where all the Section markers are displayed. I then check Mark>Markers>Extend and the function is grayed out. However, if I move the playhead one frame prior to the Section marker, the previous Section marker extends to the frame prior to the new play head position.
If I do this with manually entered markers (using the M key, creating Marker 1, 2, 3.... in sequence on the Viewer timeline), then the Previous marker is extended to the frame immediately prior the the current play head position - i.e. from Marker 1 to Marker 2. I do not have to move off the Marker 2 position to be able to extend Marker 1.
Also, simply selecting all your Markers and either dragging them to another bin (or pressing Command-U) does not produce the needed subclips?
Of this I am also aware. I find the Command-U process just confuses the issue, creating more clips to manage (others may disagree). I prefer to simply drag the "Subclips" directly from the Main clip into a Timeline.
Because you're doing all this to get subclips, right? Or wrong?
If I understand your reply correctly, I think you misunderstood my problem. I have been using subclips for several years, and find them VERY useful, especially with multi-camera shoots. So, I am quite familiar with creating and extending markers.
I just started experimenting with the Detect feature and find it works quit well (most of the time). My problem is that the Segment markers created by the Detect process, do not perform the same as manually place markers, as far as the Extend marker function is concerned, anyway.
BTW - By using the TC display in my Panasonic PV-GS400 Camera, and sending the FCP video via Firewire to the camera, the camera displays the TC on the captured clip, which I then rename the marker to for TC reference. As long as the Date/Time on the cameras are properly synced, syncing clips in the Timeline is a breeze!!
Anyway, to clarify, my process is as follows:
1. Capture a clip.
2. Display the clip in the Viewer
3. Select "DV Start/Stop Detect" and watch as the section markers appear in the Viewer.
4. In Viewer, place play head on the first Section marker
5. Press the M key to Edit Marker.
6. Change the Name of the marker to the timecode of the Marker now displayed in the Camcorder window.
7. Use Shift-Down Arrow to move to the next Section Marker
8. Press Option+` to Extend the previous marker - which does not work and is grayed out in the Mark>Markers>Extend menu.
9. Back to step 5.
This process works perfectly with manually created markers. Because the Extend works if I move the play head one frame prior to the current Section marker, this tells me there is something "special" about the Section marker that disables the Extend function, unlike a manually created marker.
BTW - If I delete the Section marker, and create a manual marker at the same frame, the Extend marker function works again. Again, indicating that Section markers are different somehow from manual Markers.
Hopefully, this wordy explanation of my process clarifies my problem.
Aside: The clips are supplied to me by a customer on a 500GB FW800 drive. FCP5 was used to capture the clips from the original Tapes (which I do not have access to). I am the editor for the project.
Thanks again for the reply. It is greatly appreciated. If there is any other info that I have missed that will help figure this out, please let me know and I will post a response a quickly as possible.
Gary -
Exporting problems on final cut X with mavericks
I am trying to export a 94 minute project thru share to a master file & it hands at preparing media. Threw away preferences, don't see any yellow triangles n any clips. Any way to get this to work? I have a 2 x 2.8 GHz Quad-Core Intel Xeon and I'm working with Mavericks.
ThanxMy mother often had occasion to tell me that I had just started the job instead of talking about it so much I'd already be done. I suggest doing anything BUT what I advised if you have a faster, more likely solution but again, in my limited experience when there are no yellow triangles and no obvious cause for a problem, there is a whacked clip. If, for instance, you can look over the clips sizes you may find one that is a totally non-standard size. Or perhaps one is done with some odd container that is causing an issue. You may be able to pick out the odd clip or it may be a third party transition or effect. Or something entirely unrelated to my suggestion. All I can add is that you might want to look at the specs of your clips...perhaps copy the entire timeline and work on a copy of it...toss out any third party effects or transition or whatever and see if it might be them. That approach can make a person crazy which is why I suggested just exporting half the timeline. It's really quite effecient if you can't make educated guesses as to what might be causing the problem. I'm assuming you've trashed prefs.
-
Pink screen when exported mpg is played
when I populate my timeline with video clips and audio and effects, it seems like the render bar is only over the effects and the odd clip, so when I export my project and try to play it the whole screen is a pink color except the effects and the clips that have the render bar over them, it doesn't matter wether the bar is red or green. I haven't had this problem before, what could I be doing wrong?
Thanks for the reply, I am a newbie to video editting and don't really understand how it works, but I shoot the video on my Sony HDR-SR1 camera and upload the clips (.m2ts files) to my computer, then I import the files into PPro and drag the clips into the timeline, then I unlink the file to separate the audio from the video, so I can record my own voice track, when I have the clips, audio and effects the way I want them I export to a MPEG2 format and the Preset is Custom, and I change the size from 1440 x 1080 to 720 x 540 (my attempt to reduce file size), when the export is done I play the mpg file with Windows Media Player and the audio plays fine but parts of the video is completely pink, I went back to the project file and noticed the clips that didn't have the render line (red) were the parts that were pink and the clips and effects that had the red render line over them played fine.
My computer is an Intel Quad Core 3.00 GHz, with 8.00 GB or RAM, running Windows Vista 64-bit.
I hope this helps,
Mike -
soundtrack pro ( universal) has start to behave strangely it's crash almost everytime that I quit the application.
Any idea?Thank you everyone for your comments and help. We had to push the release back two weeks for many reasons, some of them this issue.
But I thought my solution would be good to know for people. For the record I was attempting to edit at 4k with imported RED files converted to optimized media. What I didn't realize is that some of those clips were actually shot at 5 or 6k. I think that was one problem in and of itself, so I converted my projects to 1080p. Still got memory errors though.
So I think what solved the issue was when I flushed the cache by moving it outside the library. I think FCP had crashed while doing background renders from choking on some of the odd clips. I believe that corrupted some of the cache system, and wasn't fixed even when regenerating the cache files.
So I went to project settings and set the project cache to be outside of my project file in a folder I created. When doing so you are prompted to decide whether or not to move your current cache. I didn't, and this forced it to re-reender all those clips (but not the original optimized or proxy media). This seemed to clear up every problem I was having with Final Cut Running Out of Memory problems. I bet it was the cache, but could have been related to the mixed resolutions.
So I thought this might helpful to others searching this forum, and thanks again for everyone's help! -
Hi
I'm trying to use transform_world to take on world, scale it and translate it and copy it into the output
It seems that just scaling it and copying it works, and just translating it and copying it works, but trying do do both results in some really odd clipping/masking problem. The example code below should scale by a factor of 100 and then translate by 2 pixels in the x direction (unless I've messed up my matrix multiplication, but I don't think I have). As far as I can tell, both the scaling and the translation are working as they should, but in addition the copied image is cropped on the left. The attached images show the results if I use values of xtranslate of 2 and 2.5 pixels. In this case the world that is being copied from contains white noise, and that copied to is just a purple background. The crop amount seems to be (1-xtranslate)*scale, so is 100 for xtranslate of 2 and 150 for xtranslate of 2.5.
Does anyone have any idea of what is going on?
PF_CompositeMode mode;
mode.opacity=255;
mode.opacitySu=32768;
mode.rgb_only=false;
mode.xfer=PF_Xfer_IN_FRONT;
PF_FloatMatrix mat;
double ratio=(double)in_data->downsample_x.num/(double)in_data->downsample_x.den;
double scale=100.0*ratio;
double xtranslate=2.5*ratio;
mat.mat[0][0]=scale;
mat.mat[0][1]=0.0;
mat.mat[0][2]=0.0;
mat.mat[1][0]=0.0;
mat.mat[1][1]=scale;
mat.mat[1][2]=0.0;
mat.mat[2][0]=xtranslate*scale;
mat.mat[2][1]=0.0;
mat.mat[2][2]=scale;
PF_Rect dest;
dest.bottom=in_data->height;
dest.left=0;
dest.right=in_data->width;
dest.top=0;
int quality=PF_Quality_LO;
err=suites.WorldTransformSuite1()->transform_world(NULL,quality,0,PF_Field_FRAME,&ni.pixelworld,&mode,NULL,&mat,1,true,&dest,output);
links to examples
http://www.flickr.com/photos/78717189@N00/9437292828/
http://www.flickr.com/photos/78717189@N00/9434514543/oh my... it seems to not exist in the ccu sample in CS5 and up.
here's the code from the CS3 SDK:
static void
CCU_ConcatMatrix (
const PF_FloatMatrix *src_matrixP,
PF_FloatMatrix *dst_matrixP)
PF_FloatMatrix tmp;
PF_FpLong tempF = 0;
for (register A_long iL = 0; iL < 3; iL++) {
for (register A_long jL = 0; jL < 3; jL++) {
tempF = dst_matrixP->mat[iL][0] * src_matrixP->mat[0][jL] +
dst_matrixP->mat[iL][1] * src_matrixP->mat[1][jL] +
dst_matrixP->mat[iL][2] * src_matrixP->mat[2][jL];
tmp.mat[iL][jL] = tempF;
*dst_matrixP = tmp;
void
CCU_SetIdentityMatrix (
PF_FloatMatrix *matrixP)
matrixP->mat[0][0] =
matrixP->mat[1][1] =
matrixP->mat[2][2] = 1;
matrixP->mat[0][1] =
matrixP->mat[0][2] =
matrixP->mat[1][0] =
matrixP->mat[1][2] =
matrixP->mat[2][0] =
matrixP->mat[2][1] = 0;
PF_Err
CCU_ScaleMatrix (
PF_FloatMatrix *mP,
PF_FpLong scaleX,
PF_FpLong scaleY,
PF_FpLong aboutX,
PF_FpLong aboutY )
PF_Err err = PF_Err_NONE;
PF_FloatMatrix scale;
if (scaleX != 1.0 || scaleY != 1.0)
scale.mat[0][0] = scaleX;
scale.mat[0][1] = 0;
scale.mat[0][2] = 0;
scale.mat[1][0] = 0;
scale.mat[1][1] = scaleY;
scale.mat[1][2] = 0;
scale.mat[2][0] = (1.0 - scaleX) * (aboutX);
scale.mat[2][1] = (1.0 - scaleY) * (aboutY);
scale.mat[2][2] = 1;
CCU_ConcatMatrix(&scale, mP);
return err;
PF_Err
CCU_RotateMatrixPlus (
PF_FloatMatrix *matrixP,
PF_InData *in_data,
PF_FpLong degreesF,
PF_FpLong aboutXF,
PF_FpLong aboutYF)
AEGP_SuiteHandler suites(in_data->pica_basicP);
PF_Err err = PF_Err_NONE;
PF_FloatMatrix rotate;
PF_FpLong radiansF = 0,
sF = 0,
cF = 0;
if (degreesF){
radiansF = PF_RAD_PER_DEGREE * degreesF;
sF = suites.ANSICallbacksSuite1()->sin(radiansF);
cF = suites.ANSICallbacksSuite1()->cos(radiansF);
rotate.mat[0][0] = cF;
rotate.mat[0][1] = sF;
rotate.mat[0][2] = 0;
rotate.mat[1][0] = -sF;
rotate.mat[1][1] = cF;
rotate.mat[1][2] = 0;
rotate.mat[2][0] = (aboutXF * (1.0 - cF) + aboutYF * sF);
rotate.mat[2][1] = (aboutYF * (1.0 - cF) - aboutXF * sF);
rotate.mat[2][2] = 1;
CCU_ConcatMatrix(&rotate, matrixP);
return err;
void
CCU_TransformFixPoints (
const PF_FloatMatrix *matrixP,
A_long countL,
PF_FixedPoint *pointsFiAP)
PF_Fixed iL = 0;
PF_FixedPoint currentFiPt = {0,0};
PF_FpLong dF = 0;
for (iL = 0; iL < countL; iL++)
currentFiPt = pointsFiAP[iL];
dF = currentFiPt.x * matrixP->mat[0][0] +
currentFiPt.y * matrixP->mat[1][0] +
65536.0 *
matrixP->mat[2][0];
pointsFiAP[iL].x = static_cast<PF_Fixed>(ROUND_DBL2LONG(dF));
dF = currentFiPt.x * matrixP->mat[0][1] +
currentFiPt.y *
matrixP->mat[1][1] +
65536.0 *
matrixP->mat[2][1];
pointsFiAP[iL].y = static_cast<PF_Fixed>(ROUND_DBL2LONG(dF));
static void
TransformOval(
PF_InData *in_data,
PF_EventExtra *extra,
PF_FixedRect *fx_frame,
PF_Point *transformedPtP)
AEGP_SuiteHandler suites(in_data->pica_basicP);
PF_FixedPoint centerFiPt = {0,0};
PF_FloatMatrix mat;
PF_FpLong angleF = 0,
dxF = 0,
dyF = 0,
x_radF = 0,
y_radF = 0;
PF_FixedPoint copy_pts[OVAL_PTS];
centerFiPt.x = (fx_frame->left + fx_frame->right) / 2;;
centerFiPt.y = (fx_frame->top + fx_frame->bottom) / 2;
dxF = FIX_2_FLOAT(fx_frame->right - fx_frame->left);
dyF = 0;
angleF = suites.ANSICallbacksSuite1()->atan2(dyF, dxF);
angleF /= PF_RAD_PER_DEGREE;
x_radF = suites.ANSICallbacksSuite1()->sqrt(dxF * dxF + dyF * dyF) / 2.0;
dxF = 0;
dyF = FIX_2_FLOAT(fx_frame->bottom - fx_frame->top);
y_radF = suites.ANSICallbacksSuite1()->sqrt(dxF * dxF + dyF * dyF) / 2.0;
CCU_SetIdentityMatrix(&mat);
CCU_ScaleMatrix(&mat,
x_radF,
y_radF,
0,
0);
CCU_RotateMatrixPlus( &mat,
in_data,
angleF,
0,
0);
for (A_short iS = 0; iS < OVAL_PTS; iS++) {
copy_pts[iS].x = std_oval[iS].x;
copy_pts[iS].y = std_oval[iS].y;
CCU_TransformFixPoints( &mat,
OVAL_PTS,
copy_pts);
for (A_short jS = 0; jS < OVAL_PTS; jS++) {
copy_pts[jS].x += centerFiPt.x;
copy_pts[jS].y += centerFiPt.y;
for (A_short kS = 0; kS < OVAL_PTS; kS++) {
extra->cbs.layer_to_comp( extra->cbs.refcon,
extra->contextH,
in_data->current_time,
in_data->time_scale,
(PF_FixedPoint *)&(copy_pts[kS]));
extra->cbs.source_to_frame( extra->cbs.refcon,
extra->contextH,
(PF_FixedPoint*)&(copy_pts[kS]));
for (A_short qS = 0; qS < OVAL_PTS; qS++) {
transformedPtP[qS].h = FIX2INT_ROUND(copy_pts[qS].x);
transformedPtP[qS].v = FIX2INT_ROUND(copy_pts[qS].y);
Maybe you are looking for
-
B(lack)SOD after install windows 7 on iMac late 2009?
I know it's been covered a million times, and I have read the forum and support pages and tried everything imaginable, but I still get a plain black screen after I install windows 7 on my late 2009 iMac 27" macos 10.8.5. I know this is because the di
-
I just added a new Skype number for Wisconsin, and now I wish to cancel my old Skype number with a Cincinnati area code. How do I do that? I followed the instructions, but there is no "cancel Skype number" option under my old Cincinnati Skype number.
-
Some java object assignment problem
Hi, here is some code --- class point int x; getx(){ return x; setx(int x) this.x = x; class Immutable { private point p; getp(){ return p; setp(point p) this.p = p; Immutable nn = new Immutable(); i have to assign p.x=-5; without touching setp() met
-
External speakers - audio out not working
I have these old Creative speakers with a subwoofer that I often use with my macpro laptop. I just bought a 4K Mac Pro tower, and on the back, I see two similar jacks, one of them with a little speaker icon, which I assume, means thats where I should
-
Arranging groups of photos in aperture 2.1 browser
Hi, I'm having trouble reordering groups of photos. According to the getting started manual (page 75) you can select a group of photos in the aperture browser, and drag them within the browser to change the order of the photos. Doing that with indivi