|
|
Quote
Hi Nerov -
I've wasted a lot of time with this... editing WMV profiles at resolutions greater than 1920x1080. Using Windows Media Profile Editor.
BTW I have read that it's not compatible with Win 10, but it's working here OK.
Anyway, using Windows Media Profile Editor to edit 2K, 2.5K, UHD or 4K profiles I was getting constant errors and couldn't save because of that.
Finally it dawned on me to edit the profiles with Notepad or Wordpad... & it worked!
Attached is a batch of WMV profiles (zipped), including 2560x1440 for YouTube & local production. After unzipping, drop the profiles (not the containing folder) into C:\Program Files\CyberLink\PowerDirector15\Language\Enu\Profiles (or whichever language folder is appropriate)
If you don't want all the lower res profiles, just use the separate zip file for 2.5K profiles, & follow the same steps.
That's just for WMV. If you want 2560x1440 profiles for other formats the Profile.ini needs to be edited, shown here.
Cheers - Tony
P.S. Yes, I tested the 2.5K profiles & - yes - they work. YT test here - https://www.youtube.com/watch?v=4A-fnoQwzxU
Is it possible to upload the profiles again? The links do not work anymore. My new version of Powerdirector 16 has no WMV profiles at all.....
Forget the above: it's because the Media featurepack for Windowws didn't install right, that I had no WMV-export options. Reinstalling Windows 10 pro N now
|
|
|
Quote:
Quote:
- settings PD13: Link
Your link there shows you selected 1920x1080/60p (28Mbps) which was not the test being performed and compared. The time you quote of 3:50 would be consistent for that profile, charts show everythings working fine. The test being performed was 1920x1080/60i (24Mbps) for which your GTX 650 should be well under 2:00 to encode.
Jeff
I'm sorry, messed up a bit. However, with 1920x1080/60i (24Mbps) it is 2:34. So well above the 2:00 mark.
|
|
|
Quote:
Quote:
3:50 for my aging PC with:
- AMD 1055 Phenom (6 cores, 50% load)
- Nvidia GTX650 (full load according to GPU-Z)
- 8 Gb DDR2-memory (30% load or something like that)
- 512GB harddisk (probably 5400 rpm)
What is irritating however that when I use the same setting (1080P60 AVC 264) on a multi-cam video, the Nvidia gets almost zero load and the CPU nearly 100%. It has a lot of fading in/out and positioning changes for every camera, so that might be the reason the graphics card isn't working alongsite. But it would have been nice to let the Nvidia sweat on it
Something a little funny here with your GTX650 performance times with the sample timeline, can you please post:
1) Screen capture of GPU-Z GPU load
2) Screen capture of produce screen so one can see selections
3) Version of PD13
4) Version of Nvidia drivers
Almost looks like you are using the older CUDA encoding with your GTX650, nothing really wrong with that, just slower. The above 4 should give a little insight as each point to a different potential cause.
Jeff
Hi Jeff, if you could give a clue to what's missing, that would be nice. Rendered a video last night with 34 tracks (multicam, 5 stationary cams) with a lot of keyframes to switch from one cam to the other, and with zooming in and panning using keyframes. It took almost 7 hours for a resulting duration of 1:20 (1080P60 same settings as the boat-test), with 100% CPU usage and the Nvidia-card doing nothing....
Screen captures:
- GPU-Z output: Link
- settings PD13: Link
- Version PD13: 13.0.2408.0
- Version Nvidia-drivers: 347.52 (d.d. 10 Febr 2015, not the latest)
Thnx, Joop
|
|
|
3:50 for my aging PC with:
- AMD 1055 Phenom (6 cores, 50% load)
- Nvidia GTX650 (full load according to GPU-Z)
- 8 Gb DDR2-memory (30% load or something like that)
- 512GB harddisk (probably 5400 rpm)
What is irritating however that when I use the same setting (1080P60 AVC 264) on a multi-cam video, the Nvidia gets almost zero load and the CPU nearly 100%. It has a lot of fading in/out and positioning changes for every camera, so that might be the reason the graphics card isn't working alongsite. But it would have been nice to let the Nvidia sweat on it
|
|
|
