Yes indeed. I've just contacted Cyberlink technical support and asked them if they are going to address this API problem. Let's see what the response is. Peter Ilyk

Not that it helps any at this point, but, I'm having the same problem, all of a sudden. Just spent two weeks editing film of a jazz clinic by Dewey Redman in Houston, 1993, and am itching to broadcast it. Most frustrating...
Bob Morgan

Sam problem with my PD recently, and I have spent hours with it but failed. Frustrated!

Ladies & Gentlemen -

What I don't understand is, why my PDR 13 is able to upload to YouTube without those issues. There's nothing special about it. It's probably just like yours.

Based on what Peter Ilyk posted, CL has some modifications to make.

Cheers - Tony
Visit PDtoots. PowerDirector Tutorials, tips, free resources & more. Subscribe!
Full linked Tutorial Catalog PDtoots happily supports fellow PowerDirector users!

I'm also having the same problem..

That's really interesting Tony. When was the last time you uploaded to YouTube directly from PD13? I was able to do so until about 1 June - and have not been able to do so since then - like so many others it seems. The same thing happened with MovieMaker. One day I could upload direct from MovieMaker and then suddenly I couldn't (and still can't). However, no problem uploading from Corel VideoStudio X8. Also no problem uploading direct from PD 13 to Vimeo - just to YouTube - which suggests that it is a communication problem between PD and YouTube - which is probably due to an API problem. Peter Ilyk

Ditto. No problems at all until a few days ago. So annoying. No issues with my google account not being linked - so why wont they upload?? There must be a fix or I want my money back- I only use this to upload directly to youtube. I can upload to vimeo but not youtube.

The link to PD13 for me DOESN'T work whilst the Photodirector6 link DOES!

Quote: That's really interesting Tony. When was the last time you uploaded to YouTube directly from PD13?

Just now!



*This* is the video I uploaded through PDR 13

This evidence is not submitted to disprove anything - just to show an anomaly... just like philwizzer's PhD6 anomaly

Cheers - Tony
Visit PDtoots. PowerDirector Tutorials, tips, free resources & more. Subscribe!
Full linked Tutorial Catalog PDtoots happily supports fellow PowerDirector users!

I don't know if this has anything to do with anything - but as this thread is getting longer with the same issue, I thought I might try and see what would happen;

I actually never use direct upload - except for 2 times earlier years. I prefer to use YT's uploader. Anyway; I put a few seconds on timeline and go through the procedure. NO - no linking luck. I close PD, open and go through the procedure again. NO - no linking luck. Give it a rest. Upon checking my mail, I have now 2 warnings from Google telling me there has been 2 attempts to sign in to my account with Internet Explorer on Windows, - do I recognize this activity? Yes, I do - but my default browser is not IE but FireFox. Is the use of IE the default for direct upload? If so, it's CL's choice?
Just something.
https://www.petitpoisvideo.com

I, too, am a FireFox person. Just tried upload via IE. Same freaking problem...

FYI, here is response from PD Technical Support:
(I have not attempted the complicated stuff...)
"Dear Robert,
Thank you for contacting CyberLink Technical Support.
I understand that you are facing issue while uploading video on YouTube using PowerDirector software.
Regarding your concern, I would suggest you to follow the below steps and check if it helps ressolving your issue
1. Open Internet Explorer
2. Go to YouTube.com
3. Sign in with your Google account
4. Connect YouTube account with Google account
5. Log off YouTube
6. Launch PDR12
7. Upload to YouTube again
If issue persists, please let us know if you can upload a video to YouTube via web browser with the same Google account.
I would like to inform you that PowerDirector uses YouTube's API to verify account. If the you cannot upload via web browser also, then you need to contact YouTube for more assistance.
Also, if the issue persist only with PowerDirector, I would request you to provide below mentioned information to analyse the issue in better manner and provide you the solution:
1. SR-Number
Open PowerDirector--> Click on the "PowerDirector" logo which is at the top right corner. Then the "About" page will open.
Here you will find the the version, build number and the SR number of the software.
To take screenshot, please follow the steps given below :
a. Press the Print Screen key on your keyboard when the message appears on your screen.
b. Click on Start -> Programs-> Accessories-> Paint.
c. Paste the screen capture there by pressing Ctrl+V
d. Save the file with the extension name .jpg and then send to CyberLink Support for analysis.
2. Provide the DxDiag Log file.
DxDiag.txt You can use the steps that follow to create this file
a. Press the Windows Key + R.
b. Type in DxDiag and press Enter or click OK. This will open the DirectX diagnostic tool.
c. Click on the Save All Information button.
d. Save this file to your Windows desktop and name it dxdiag.
3.Sreenshot of the error message, with full background.
To take screenshot, please follow the steps given below :
a. To take a screen shot, press the [Prt Scr] key on your keyboard when you encounter this error.
b. Click on Start -> Programs-> Accessories-> Paint.
c. Paste the screen capture there by pressing Ctrl+V
d. Save the file with the extension name .jpg and then send to CyberLink Support for analysis.
4. Provide the following information as Proof of Purchase to validate your purhcase record:
i. The order number of the purchase.
ii. The E-mail address that you have used while purchasing the software.
iii. The copy of invoice of the purchase that shows the name and version of CyberLink software purchased by you.
iv. If you received the software (as an OEM software) with any hardware (PC, graphics card, DVD/BD drive etc...), please let me know the name & model of the hardware. (If you have the installation disc, please send me snapshot of the installation disc, to find out the version of OEM software, provided to you.)
Please feel free to contact us back for any further clarification or for any assistance related to CyberLink products.
Use the below mentioned link to get back for further queries:
https://membership.cyberlink.com/support/service/technical-support.do
Thank You and Best Regards,
Avanindra
CyberLink Technical Support

I have no English words to describe what I am reading.....reading.....reading....
Just something.
https://www.petitpoisvideo.com

:

Just sent opened a support ticket for my PowerDirector 11 issue. Same as everyone else in this thread. It used to work fine....now not at all.

PowerDirector 10 - same issue. Was working fine then around the 1st of June received the "Your Google account does not link to a YouTube account." Ok fine. While I'm waiting for a solution that I can understand can anyone tell me what format is used to render the video? I've tried to use PD10 to produce the video using different formats and then use YT to upload, but the quality was crappy compared to using the PD10/YT process. Typically, I cancel the upload anyway and upload from YT.

Looking at Avanindra's (CyberLink Tech Support) response above I've had this installed for a while now and who knows where all the receipt and validation information that is being requested is located at this point.

Still no reply to my support ticket.....no sense of urgency on their part at Cyberlink.....very disappointed......and they want me to upgrade to a newer version?

Quote:

Quote: That's really interesting Tony. When was the last time you uploaded to YouTube directly from PD13?

Just now!



*This* is the video I uploaded through PDR 13

This evidence is not submitted to disprove anything - just to show an anomaly... just like philwizzer's PhD6 anomaly

Cheers - Tony

Peter Ilyk

That's really interesting Tony. Seems some people can upload - while so many can't. Something weird going on here. Peter Ilyk

This is the response I just received from Cyberlink support:

"Thank you for writing back.

This is to inform you that I have escalated your concern with details to our Product & Development team for further analysis.

We will get back to you on your original CSID # CS001473743 as soon as we get updates about your case.

I would appreciate your patience and understanding regarding the same.

Please feel free to contact us back for any further clarification or for any assistance related to CyberLink Products. Use the below mentioned link to get back to us for your further queries:

https://membership.cyberlink.com/support/service/technical-support.do

CyberLink Technical Support "

However, I also learnt from YouTube that Google had advised developers in 2012 that it would be retiring old APIs and putting in new procedures. Under the new chganges APIs (including the YouTube data AOI would change every year. Google advised developers that it was giving them advance notice of these changes. This is what the Google notification said:

" It’s 2012. These days technology moves fast and we want to keep our developer products moving and innovating fast, too. In an effort to align our pace of development with the market, we did a careful analysis of our API deprecation policies. Based on our conclusions, we've decided to adopt a one-year policy for some APIs, remove the policy for other APIs and make the policy itself simpler and clearer. This doesn't mean we have changed the way we think about our APIs - we are more committed than ever to offering stable and relevant APIs to our developer community.

Most of these changes will happen over the next several years, but today we are giving you advance notice. As always, we will strive to keep changes to a minimum and announce them in a timely manner.

One-year API deprecation policies

As part of our effort to evolve our developer platform (like introducing the Google APIs Terms of Service), we are moving some services to a one-year deprecation policy, a common industry practice among similar APIs. The four services moving to a one-year policy are:
Google App Engine
Google Cloud Storage
Google Maps/Earth APIs
YouTube API
Google App Engine, Google Maps/Earth APIs and YouTube API will wind down their current 3-year deprecation policy and will transition to the one-year policy in April 2014. Google Cloud Storage keeps its current one-year policy. To be very clear, we are not deprecating the APIs themselves.

Clearer deprecation policy language

For the above APIs, we've shortened our deprecation policy to be clearer and more concise. The new policy simply states that we will strive to provide one year notice before making breaking changes. For details, see each API's Terms of Service, such as the Google Maps/Earth APIs.

Removal of deprecation policies

For Google's other APIs, we are removing the deprecation policy - not the API. In most cases, this change will not take effect until April 2015. Check the following affected APIs' Terms of Service for details: Accounts API, AdSense Host API, Chart Tools API, Checkout API, Contacts API, Custom Search API, Documents API, Doubleclick for Publishers API, Feed API, Google Apps Admin APIs, Libraries API, Orkut API, Picasa Web Albums API, and Prediction API.

During the remainder of the deprecation period, these APIs will also benefit from the clearer deprecation policy language. Our commitment to the underlying APIs remains unchanged. We will continue to work very hard to communicate any changes to our APIs well in advance, regardless of the APIs' deprecation policy.

Retirement of older APIs

In addition, we are announcing the deprecation of several older APIs and versions. Please visit the documentation for each API for more information about the deprecation period and suggested alternatives:
We are deprecating the Moderator API and Legacy Portable Contacts API, as well as part of the Account Authentication APIs (ClientLogin, AuthSub and OAuth 1.0) and Google Chart Tools (Image Charts and Infographics).
We are also deprecating the non-current versions of the Spreadsheets, Contacts, Documents List and Freebase APIs.
Finally, we are adding a shutdown date for the Finance API and Feedburner Administrative APIs, which were deprecated last year.
Our commitment to developers

Our change in policy is designed to make it easier for us to bring you the technology you’ve come to expect from Google: technology that excels at ease-of-use and scalability, and enables you to focus on building your unique application. Our team remains committed to existing APIs as well as building powerful new Google technology into our developer platform. Peter Ilyk

Check: http://forum.cyberlink.com/forum/posts/list/0/44094.page#228091
Dafydd