|
|
|
Quote:
What you've found is exactly what happens here. Once white balance has been adjusted and applied to all, it interferes with future colour changes that are applied to all. I repeated the procedure going through ColorDirector and got different results.
It doesn't fix the problem, but I'm happy to hear someone else can duplicate my results.
I don't have ColorDirector, so that's not an option for me.
I went through each clip and adjusted the color settings individually. Kind of a pain, but it got the job done.
|
|
|
OK, I tried an experiment with a few sample clips.
If "Color Adjustment" is the only enhancement checked, "Apply to All" works as expected. I can adjust the color settings, apply to all, then go back and make changes, and apply to all again. That works.
However, if I have "Color Adjustment" AND "White Balance" checked, the "Apply to All" button fails as before. It will change all clips the first time, but any following adjustments only affect the currently selected clip.
I am using 1920x1080x30p @32mbps MPEG2 files as my source video.
Do you get different results?
|
|
|
> Can you not simply use the 'Undo' function
Only if I am making color changes one after the other.
What usually happens is that I'll adjust the colors, do some editing, maybe produce a range for testing, etc. Then after seeing the final video I decide I need to tweak the color a bit more. Undo is of no help in that situation.
|
|
|
> I think that there is one misunderstanding here.
No misunderstanding, Apply to All does not affect OTHER clips on the track that have already been color adjusted.
In other words, if I have five new clips I can adjust the first clip and click "Apply to All" to set the other clips to the same color settings. That works fine.
The problem is if I decide to change the color settings, Apply to All will have no effect on the other clips. They retain the settings from the first adjustment.
Once the clips have been adjusted, the only way to make changes is to adjust each clip individually. No biggy for a few clips, major hassle when you've got 50 or more.
|
|
|
> Try selecting all the clips, then go through the fix steps.
As I suspected, PD13 does not allow you to Fix/Enhance if you select more than one clip.
> Notes that is shown letter (i) all of the clip's band.
Hmm... Interesting discovery.
If the clip DOES NOT have any color settings (No "i" displayed), then the "Apply to All" button will adjust the settings for that clip.
However, if a clip already has color adjustments, the "Apply to All" button does not change the existing settings.
Unfortunately, that kind of makes it useless for all but the first attempt. For example, if I change the color settings and play parts of the video to see how it works. If I change my mind later after performing other operations, the only option is to go through and change each clip individually. Slow and awkward.
|
|
|
> Try selecting all the clips, then go through the fix steps.
I'll give that a try when my current project is finished processing.
> Here everyone works Color Ajustament, is applied to the entire track.
Hmm... For me the "Apply to All" button is only affecting the currently selected clip?
> When using White Calibration (Calibrate button), disables Color temperature and Tint, controls.
It would be nice if there was a way to "tweak" the white calibration slightly. The way it is now, I have no way of knowing what settings it is using.
|
|
|
When I click Fix/Enhance and adjust the white balance and make color corrections, the "Apply to All" button does not change any of the other clips on the same track. I think it is changing the color temperature settings for all clips, but it has no effect on the color corrections (brightness, contrast, etc.). Also, even though it seems to change the WB color temperature settings, it does not select the same WB option (temperature or white calibration).
Is there a way to really apply all Fix/Enhance settings to all clips on the same track?
On that same topic, it would be nice if the white calibration would set the temperature sliders so I know what the settings were changed to. The temperature settings stay at 50/50 regardless of the white calibration. So, I can't make slight tweaks to the eyedropper settings.
|
|
|
|
Quote:
Because it requires a dedicated video card...
Does the video card help with timeline editing, or just with the final encoding of the video? I prefer CPU only encoding to get the best quality, even if it takes longer.
I have an Asus ENGT440 (Nvidia GEForce GT440), i5-2500K, 240GB SSD, 2tb drive for video.
What video card would you recommend for video editing (to improve MP4 playback)? I do not play video games, video and photo editing only.
|
|
|
|
Quote:
MP4 with H264 is a better option at all of those above points. And has a better quality at the same bitrate.
PS: For "Edits quickly": as opposed to mpeg2, h264 accepts hardware acceleration, so is even faster on most computers.
It may just be my hardware, but MP4 didn't edit as smoothly as MPEG2 does on my system. Lots of stuttering while playing the MP4 clip on the timeline. MPEG2 plays smoothly in real time.
|
|
|
|
Quote:
you must modify the Profile.ini.
Awesome, that worked perfectly. Thank you!
|
|
|
In PowerDirector 12 the maximum bitrate for MPEG2 files was 30mbps.
Since "upgrading" to PD13, the max bitrate for MPEG2 files is only 25mbps?
I prefer to use MPEG2 with the highest bitrate possible as my final archive format (Bluray compatible, edits quickly, widely supported, etc.).
Is there any way to get the original 30mbps bitrate back for MPEG2 output?
|
|
|
|
1. Please give us more detail on what it is that you are editing.
1920x1080 @ 30fps. MPEG4 @ 48Mbps (rendered with a custom profile in PowerDirector 12).
2. Please make sure that your PC meets the "minimum" needs of your project (found on the product web site).
My system should meet the minimum requirements, though my video card is on the low end (chosen for silent operation over all out encoding power). I realize the video card may slow down encoding times, but PD12 seems much slower than Studio 15 was. Unfortunately, I haven't created the same video in Studio to run actual timing comparisons.
I was mostly curious why the CPU and RAM usage was so low, when the encoding takes so long.
The other issues aren't related to performance, they are usability problems.
One other wishlist item:
1. The "Produce" screen should remember the format you last used. Every time I want to produce a video I have to select MPEG4, then the Custom format, then the hardware acceleration. I always use the same encoding, so it should remember this.
|
|
|
I just switched to PowerDirector 12 after using Studio 15 for a couple years. So far it has worked fairly well, but I have run into a few issues.
Question:
1. My finished video is 17 minutes long. Unfortunately, it takes over an hour to render it. According to Windows task manager, it's only using 30-50 percent of the CPU load, and only about 2GB of RAM? I tried rendering to a different hard drive thinking the drive was being overloaded, but it made no difference. I have a lot of transitions (fade), but practically no effects. My system is Win7 Home Premium 32-bit SP1, i5 2500K@3.3Ghz, 4GB RAM, 2TB hard drive and 1TB hard drive. Why is the rendering so slow?
Wishlist:
1. PD12 should save the zoom level I have set up on the time line. Every time I open PD12, it goes back to showing the full video. This means I have to zoom in to my desired scale every time I start PD12. Annoying.
2. On several occasions I have somehow created very short clips (scenes, or whatever you want to call them). These are usually just a few frames in length, and don't show up on the time line. The only way I know they are there is if I try to place two clips next to each other and am unable to apply a transition. I can also see a short blip of video when I play it back. It would be nice if PD12 let you set a limit for the shortest clip. For instance, I will never want a clip less than two or three seconds. Ideally PD12 would prevent you from creating a clip this short, but at least it would show up on the time line if it did.
Bugs:
1. In a few random cases, I get a weird "echo" in the audio. I'm just using a single video track and a second MP3 song for background music. I haven't determined what causes it, but it usually starts when there's a transition. Sometimes I can fix it by muting the clip on my main video track, but not always. Of course, I don't always want to mute my main track either. I converted one of my songs to WAV format before editing, and didn't notice the problem anymore. But, it's really random so I don't know that it's really solved.
2. I created a couple of titles at the end of my first video. Basically just some static text and a photo I added to the title screen and scaled to size. When I render (produce) the video and play it back, the image flashes wildly, while the text displays normally? There are a couple of ways I can work around this, but it shouldn't happen in the first place.
3. When I use SVRT to render (produce), the final video is unplayable in VLC. It says the h.264 format is unsupported? I have no problems if I export with hardware acceleration instead. For what it's worth, I didn't notice any difference in speed rendering with SVRT anyway, even though the output format is exactly the same as the input files (I encoded the source files with the same setting in PD12).
|
|
|
