Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum
where the experts meet
| Advanced Search >
Going from PD12 to PD14 couple questions.
calum123 [Avatar]
Newbie Joined: Aug 18, 2013 05:30 Messages: 41 Offline
[Post New]
Should I just fully uninstal PD12 before installing PD14?
Can I still use my PD12 templates and saved projects in PD14?

Thanks.
Dafydd B [Avatar]
Senior Contributor Joined: Aug 26, 2006 08:20 Messages: 11973 Offline
[Post New]
If you purchased the full license of PowerDirecter 14 you can install and retain PDR12. If you're upgradingvia an Upgrade purchase of 14, then you wont retain PDR12, it'll be "lost" during the installation.

PDR 12 templates - which are you referring to. I always back up my Profile.ini file as this contains the profile templates I have made to produce video to.

Saved projects - reverse compatibility. There is always a risk with opening an older project in a newer version of a software. Newer software is a "change". Generally previous versions can be opened. Make sure you pack all your projects - save the data.

Come back with any follow up questions. I hope I've helped, other editors may have a different perspective to write from etc.

Dafydd
calum123 [Avatar]
Newbie Joined: Aug 18, 2013 05:30 Messages: 41 Offline
[Post New]
Thanks, very helpful. I'm upgrading from a full version to a full boxed, amazon version of DP14.

I have no real interest in keeping 12 I guess. I fear there could be a confliction "somewhere" so would probably rather uninstall and start a fresh.

Good to know the project save files (sorry that's what I meant by my templates I use) will work on 14. That's key for me. I'll uninstall 12 and install 14 tonight and let you know how I get on.

I hope 14 is good!
Anja the Dane
Contributor Location: Denmark (North of Copenhagen) Joined: Mar 03, 2011 15:02 Messages: 347 Offline
[Post New]
Hi Dafydd

Interesting with the Profile.ini file - where do I find it?

Cheers, Anja PDR 14.0.4207.0 / Windows 10 64-bit / Asus / Intel i7-4790 3.60 GHz / 16GB RAM / NVIDIA GeForce GTX 970 / DirectX 12
Dafydd B [Avatar]
Senior Contributor Joined: Aug 26, 2006 08:20 Messages: 11973 Offline
[Post New]
Hi Anja,
A Profile.ini file is "auto generated" when you make your fist customise profile in Produce, for example, when you create a specific profile to render mp4's.

An ini file can be opened using NotePad and by clicking Save will be ok to use. You can also create an ini file simply by altering a text file's extension from .txt to .ini.
The ini here, Profile.ini is a retention of the parameters used to create a template.
Location includes some hidden folders: C:\Users\ComputerName\AppData\Roaming\CyberLink\PowerDirector

Note: To carry forward the contents of a Profile.ini please first generate a customise file in Produce*,
Close PDR
Open the Profile.ini using NotePad,
From the saved previous Profile.ini Copy the contents and Paste to the newer Profile.ini in PDR14.
*Make sure you paste below the starter custome profile you initially generated and you observe that one ampersands (&) start the profile and two ampersand(&&) closes the profile.

Note-2 I have had a problem with a Profile.ini where a corrupt template transferred into PDR14 caused PDR14 to "White Out" in Produce. It was really hard to find and eliminate the profile causing the issue.

If I've "gone on" and lost either Anya or calum123, then please ask for additional clarification.

I don't believe this is a tangential question (asked by Anya) - it is a continuation of what needed to be saved/retained by calum123

Dafydd



EDIT: I have changed the instruction regarding ampersands (&&&) - I muddled up the first and last.

This message was edited 2 times. Last update was at Dec 04. 2015 04:17

calum123 [Avatar]
Newbie Joined: Aug 18, 2013 05:30 Messages: 41 Offline
[Post New]
OK instal has gone great. I will mostly be editing gopro videos (1090p 60fps).
I've set the timeline to 60fps. but am I right in thinking I want to make the produce file as close to the specs of the original file? so data rate / bit rate etc?

Also I cant seem to set the production to 16:10 (for another project im working on).

This message was edited 2 times. Last update was at Dec 03. 2015 13:09

calum123 [Avatar]
Newbie Joined: Aug 18, 2013 05:30 Messages: 41 Offline
[Post New]
Can anyone explain the difference between entropy CABAC vs CAVLC? I am at all time looking for absolute maximum output quality. don't care at all about file size or time it takes to produce. want absolute minimum artefacts and just best quality possible.



This is the settings I will use unless someone is to advise a better "quality" way. (on the right is the original file, they are all like that from the gopro)

file



Link here for closer view - http://s15.postimg.org/3r84pbfkr/dddd.png

This message was edited 3 times. Last update was at Dec 03. 2015 13:08

PepsiMan
Senior Contributor Location: Clarksville, TN Joined: Dec 29, 2010 01:20 Messages: 1054 Offline
[Post New]
welcome to the forum.

Quote: Can anyone explain the difference between entropy CABAC vs CAVLC? I am at all time looking for absolute maximum output quality. don't care at all about file size or time it takes to produce. want absolute minimum artefacts and just best quality possible.


This is the settings I will use unless someone is to advise a better "quality" way. (on the right is the original file, they are all like that from the gopro)...




from the Main or High Profiles choose CABAC coding.



CABAC- Context-based adaptive binary arithmetic coding.

CAVLC- Context-based adaptive variable-length coding.



of the two, CABAC is the higher quality and CAVLC is the lower quality.

if you want quality encoding then the source file's video bitrate should be high, too.

at 60FPS, suggest set the video bitrate to 32 Mb/sec(up to 44 Mb/sec) for your 1080 FHD resolution.

even at 30FPS, i'd set 32 Mb/sec video bitrate...


fyi -> 1 Byte = 8 bits


happy editing.

PepsiMan

'garbage in garbage out'

This message was edited 4 times. Last update was at Dec 03. 2015 13:30

'no bridge too far'

Yashica Electro 8 LD-6 Super 8mm
Asrock TaiChi X470, AMD R7 2700X, W7P 64, MSI GTX1060 6GB, Corsair 16GB/RAM
Dell XPS L702X i7-2860QM, W7P / W10P 64, Intel HD3000/nVidia GT 550M 1GB, Micron 16GB/RAM
Samsung Galaxy Note3/NX1
calum123 [Avatar]
Newbie Joined: Aug 18, 2013 05:30 Messages: 41 Offline
[Post New]
Quote: welcome to the forum.

Quote: Can anyone explain the difference between entropy CABAC vs CAVLC? I am at all time looking for absolute maximum output quality. don't care at all about file size or time it takes to produce. want absolute minimum artefacts and just best quality possible.


This is the settings I will use unless someone is to advise a better "quality" way. (on the right is the original file, they are all like that from the gopro)...




from the Main or High Profiles choose CABAC coding.



CABAC- Context-based adaptive binary arithmetic coding.

CAVLC- Context-based adaptive variable-length coding.



of the two, CABAC is the higher quality and CAVLC is the lower quality.

if you want quality encoding then the source file's video bitrate should be high, too.

at 60FPS, suggest set the video bitrate to 32 Mb/sec(up to 44 Mb/sec) for your 1080 FHD resolution.

even at 30FPS, i'd set 32 Mb/sec video bitrate...


fyi -> 1 Byte = 8 bits


happy editing.

PepsiMan

'garbage in garbage out'




Thanks. Is there any point going over the bitrate of the original video? (typically 30,000 coming from the gopro).
What about fast encoding and stuff, best leave all that off? use deblocking yes?
PepsiMan
Senior Contributor Location: Clarksville, TN Joined: Dec 29, 2010 01:20 Messages: 1054 Offline
[Post New]
typically i leave it as is.



eventhough you've set at video bitrate rate to GoPro, end product isn't and some times is.

i generally set at least +1Mb/sec more than the source video bitrate.

you may test and see...



PepsiMan

'garbage in garbage out' 'no bridge too far'

Yashica Electro 8 LD-6 Super 8mm
Asrock TaiChi X470, AMD R7 2700X, W7P 64, MSI GTX1060 6GB, Corsair 16GB/RAM
Dell XPS L702X i7-2860QM, W7P / W10P 64, Intel HD3000/nVidia GT 550M 1GB, Micron 16GB/RAM
Samsung Galaxy Note3/NX1
calum123 [Avatar]
Newbie Joined: Aug 18, 2013 05:30 Messages: 41 Offline
[Post New]
Quote: typically i leave it as is.



eventhough you've set at video bitrate rate to GoPro, end product isn't and some times is.

i generally set at least +1Mb/sec more than the source video bitrate.

you may test and see...



PepsiMan

'garbage in garbage out'




Thanks mate. I guess by that reconing I could just max her out at the 60,000 then? Just "to be sure" of max quality. or will that make simply daft file sizes?

This message was edited 1 time. Last update was at Dec 03. 2015 13:56

calum123 [Avatar]
Newbie Joined: Aug 18, 2013 05:30 Messages: 41 Offline
[Post New]
P.S. IS there anyway to set the production to 16:10? I have some work to do for a monitor that is 16:10 also.
Anja the Dane
Contributor Location: Denmark (North of Copenhagen) Joined: Mar 03, 2011 15:02 Messages: 347 Offline
[Post New]
Quote: Hi Anja,
A Profile.ini file is "auto generated" when you make your fist customise profile in Produce, for example, when you create a specific profile to render mp4's.
....
Dafydd


Yes Dafydd, it was s a continuation of what needed to be saved/retained by calum123.

I found both Profile.ini for PDR13 and PDR14. And I made a temporary backup.

There are differences that are interesting to look at.

Thanks for the help and for instructions on how to insert a saved profile.

Cheers, Anja PDR 14.0.4207.0 / Windows 10 64-bit / Asus / Intel i7-4790 3.60 GHz / 16GB RAM / NVIDIA GeForce GTX 970 / DirectX 12
PepsiMan
Senior Contributor Location: Clarksville, TN Joined: Dec 29, 2010 01:20 Messages: 1054 Offline
[Post New]
Quote:

Thanks mate. I guess by that reconing I could just max her out at the 60,000 then? Just "to be sure" of max quality. or will that make simply daft file sizes?





by increasing the bitrate that wasn't there will degrade your masterpiece.

rule of thumb is stretching or compressing will degrade the PQ / VQ. period.



Quote:

P.S. IS there anyway to set the production to 16:10? I have some work to do for a monitor that is 16:10 also.





it isn't much. i will not stretch it. 16:9 will be just fine or watch my tutorial then you'd be the judge.

https://youtu.be/CqYynsrvDjg

and or read my quote! laughing 'garbage in garbage out'



PepsiMan

'garbage in garbage out' 'no bridge too far'

Yashica Electro 8 LD-6 Super 8mm
Asrock TaiChi X470, AMD R7 2700X, W7P 64, MSI GTX1060 6GB, Corsair 16GB/RAM
Dell XPS L702X i7-2860QM, W7P / W10P 64, Intel HD3000/nVidia GT 550M 1GB, Micron 16GB/RAM
Samsung Galaxy Note3/NX1
Dafydd B [Avatar]
Senior Contributor Joined: Aug 26, 2006 08:20 Messages: 11973 Offline
[Post New]
Quote:
Quote: Hi Anja,
A Profile.ini file is "auto generated" when you make your fist customise profile in Produce, for example, when you create a specific profile to render mp4's.
....
Dafydd


Yes Dafydd, it was s a continuation of what needed to be saved/retained by calum123.

I found both Profile.ini for PDR13 and PDR14. And I made a temporary backup.

There are differences that are interesting to look at.

Thanks for the help and for instructions on how to insert a saved profile.

Cheers, Anja


Hi Anja, sorry I muddled up the ampersands, I had too much info to write ha ha . See correction in my post here: http://forum.cyberlink.com/forum/posts/list/46503.page#241173

The start of a profile has one ampersand (&) and the closure of the profile has two (&&).

Dafydd

This message was edited 1 time. Last update was at Dec 04. 2015 04:21

Anja the Dane
Contributor Location: Denmark (North of Copenhagen) Joined: Mar 03, 2011 15:02 Messages: 347 Offline
[Post New]
Hi Dafydd, Thanks.
I already have seen that "The start of a profile has one ampersand (&) and the closure of the profile has two (&&)." Anyway thanks for the correction. PDR 14.0.4207.0 / Windows 10 64-bit / Asus / Intel i7-4790 3.60 GHz / 16GB RAM / NVIDIA GeForce GTX 970 / DirectX 12
Powered by JForum 2.1.8 © JForum Team