David Eaks
Forum Replies Created
-
*EDIT- Sorry, this is a FCP7 question and I answered for FCPX.
You may have had many clips in the timeline selected, then double clicked the dip to color transition, which applies it to the ends of the selected clips.
Is command-T still set to the default, cross dissolve?
You can use the timeline index to select just the dip to color transitions to delete/replace them with your desired transition.
-
Select the clip, then in the inspector change the audio to dual mono. Then in your timeline right-click and choose show audio components. Now you have both channels playing on both sides and can alter each channel individually in the timeline.
-
I dont know those specific cable ties, I figure they are similar to these- https://www.riptie.com/Pages/esl.html
You can fold the fuzzy side in half under itself before wrapping it around the coiled cable. This way the tie doesn’t “hit itself” in the middle. If there’s still way too much of the hook side hanging off the end after wrapping, the tie is just plain too long for the cable.
I’m not really a fan of the “center mount” style ties in general but the rip-tie brand, heavy duty cable wraps, are by far my favorite. For the cables that are used almost daily for a significant portion of the year, anything less than the 10,000 release-cycle Rip-Tie isnt even worth the effort to mount on the cable.
I almost exclusively use the ties on this page, NOT to say other good cable ties aren’t available, I just like these-
https://www.riptie.com/Pages/cw.html
-
David Eaks
May 18, 2013 at 4:43 pm in reply to: Is doing heavy editing and rendering with a WD My Book II a bad idea?There are horror stories for every brand HDD, the thing is, they all suck and will fail. So have a backup system in place. I have personally had very good experience with Western Digital (primarily buying bare drive Caviar Blacks).
It looks like the drive you linked to uses the WD Green drives, which are “intellipower” and run somewhere between 5400 and 7200 rpm. Not usually recommended for video work, but I’m sure at the end of the day it will do the job.
-
Well, since it looks great on your computer I think the problem must be with Go Daddy’s recompression after you upload.
You could try making the transitions shorter, or longer, or remove them completely. Slightly increase the bit rate to get the file size even closer to 150MB. Try compression markers at the troublesome areas. Shorten the total length of the video to get the bitrate higher. Decrease the frame size in order to increase the bit rate.
Just some thoughts. Good luck!
-
A few questions. How long is the video? What is the frame size? What was the file size of the compressed version that you uploaded? Is the issue visible in the video file before uploading, or only after it is uploaded?
If the issue is present in your compressed file before uploading, you can try placing compression markers in Compressor. These will make compressor “focus” on those areas and make sure to do a good job.
You definitely want to use every bit of that tiny 150MB size limit.
-
On another note, do you even need to render your entire timeline? I leave auto render off and rarely render anything in the timeline anymore unless I really need to see a more complex effect playback in real time. I’ll even range-export small portions instead of rendering, then trash the file after viewing. Though my work is fairly light on things that need long renders.
At first I thought background rendering would be great, but its not truly in the background. Then there’s the weirdness with renders you’re expirenceing (I’ve had some troubles too). Those things along with the fact that GPU acceleration is enabled on export (as well as in-timeline rendering) have led me to the methods above.
-
If it suits your needs, Preference Manager from Digital Rebellion is an excellent and free option for trashing some prefs.
-
Unfortunately I’m not familiar with the ATEM, hopefully someone who is will chime in.
Are you sure that your all settings match the video format?
-
What is the format of the video you are playing? Codec? frame size? Frame rate? Select the video file, right-click (or control-click) and choose “get info” or open the video in quick time and press command-i.
The frame rate 50 is a PAL format. Are you in the US? Probably won’t want to use that. 23.976, 24, 29.97, 30, 59.94 and 60 are your NTSC options.