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 >
Thanks guys. Not sure what is happening. I also get the blue bar which says "uploading video...complete", but then I also get a message to say "PD could not upload your video to YouTube". Which is a bit strange as the 2 messages are completely contradictory". But I have no problem uploading direct to Vimeo. So something odd is happening with YouTube connections. I'm using Windows 7 64 bit with 16GB RAM - the system is not the issue as I have been successfully uploading to YouTube for several years.
Last year at around this time there was a problem with PD uploading to YouTube. This was a result of an API issue between Cyberlink and YouTube. Cyberlink issued a patch that fixed the problem. I've been uploading to YouTube for the last 12 months and have had not problems. A few days ago I upgraded to PD14 and now can't seem to upload to YouTube - no problem with uploading to Vimeo. Are we having the same problem this time again? Last year advised that under their new policy the API would only remain valid for 12 months (which is about now). Does the Cyberlink API for YT need to be updated again - or am I having a different problem won't allow me to upload to YouTube?
Optodata V2907.1 did the trick for me - or so it seems. After installing the patch I initially had no problems uploading to YouTube. But a couple of weeks later I seem to have other YouTube problems. The last few times I have tried to upload I get the authorisation message to allow PD to upload to YT, and after giving the authorisation PD 13 produces the appropriate file for YouTube. After the file is created I either get an immediate message to say the PD can't upload the file to YouTube OR it starts uploading but after uploading about 50% I then get a message to say that PD "could not upload the file to YouTube". Is this an issue with PD or YouTube? Obviously it's not an API issue - but something else. Has anyone else had this problem? If so, what is the solution? If I upload to Vimeo I have no problem - the problem only seems to be with uploading to YouTube?
You can't blame Cyberlink for this. This is a Google initiated problem - and affects other programs as well - such as MovieMaker. At least Cyberlink fixed the problem - you probably won't see the same response from Microsoft and MovieMaker.
From what I read, YT will change the YT/API every 12 months. So will Cyberlink be updating the API each time there is a change? According to Google:
"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. "
So will Cyberlink be keeping an eye on this and providing new API patches for YT each year? They must be aware of this new Google policy.
Thanks You Thank You Thank You - VERY MUCH!! Downloaded the patch and it now works!!! Fantastic. Why isn't this patch included in new versions of PD13 - I only upgraded to PD 13 2 weeks ago!!
Thanks You Thank You Thank You - VERY MUCH!! Downloaded the patch and it now works!!! Fantastic. Why isn't this patch included in new versions of PD13 - I only upgraded to PD 13 2 weeks ago!!
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:
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.
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.
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.
I just received a response from YouTube which says: "Yes, Google retired several APIs in the past couple of months that might be part of the problem, including the YouTube Data API.
It's likely CyberLink needs to update their software."
Quote: So - it must be related to the way the PDR/YT interface works to connect to Google/YouTube. This was a monster created by Google in 2009, where Google & YouTube accounts had to be linked...Cheers - Tony
And yet, there's many of us reporting the identical problem as only happening in the last couple of days. A search on here brings up 11 results - all happening in last few days & all working perfectly a few days ago.
Although I bought a copy of PD12, my new 'puter (running Win 8.1) came with PD12 & I've been using it to upload vids successfully since February.
My last successful upload was 31st May. A couple of days later & suddenly there's a problem!
That's correct for me as well. Had no problem with uploading to YouTube with PD until 3 June. After that date I can no longer upload and just get a message that says "Your Google account is not linked to a YouTube account. Go to YouTube and try to upload a video to cerate a YouTube account". This is clearly nonsense as ifmy accounts weren't linked then I could not have been able to successfully upload video to YouTube before 3 June. But I could and had no problems. And when I go to my Google account it says that Cyberlink is authorised to manage my YouTube account and my YouTube videos. And I have no problem upload to YouTube from Corel VideoStudio X8 (at least not yet!). But the same thing happened with MovieMaker. Whereas previously I had no problems uploading direct from MovieMaker -now I can't. So there is clearly a communication problem between these programns and YouTube/Google.
I keep getting emails from Cyberlink which are in German. The lastest one seems to be advisining of a free update. Part of the message is:
Für alle PowerDirector 9 Nutzer gibt es ein neues kostenloses Update. Dieses Update optimiert den Videotranskodierungsprozess für die 2. Generation Intel® Core™ Prozessoren. Für Besitzer der Vorgängerversion gibt es das Upgrade jetzt besonders günstig.
I don't read german - and there seems to be no facility to translate the emails. Does anyone know what this update is about?? Anyone else get German emails? And why would they send emails in German to someone in Australia????
I have a clip in my timeline in PD9 where the audio is fairly soft. I therefore unlinked the video and audio and opened up the audio in Wave editor where i boosted the audio by about 15 db. This modification was saved and then I was back into the timeline. I then re-linked the audio and video. The sound was now nice and audible. However. I then wanted to trim the clip - but I could not do this. There was no trim tab above the timeline and it was not possible to grab the end of the clip and trim it that way either. I then tried going to "edit" in the top tool bar - and selected "edit audio" - but all the edit functions were greyed out.
Does this mean that once a clip's audio has been modified in Wave editor it is no longer possible to trim the clip. Seems a bit odd if that is the case. All the other clips in the time line - which had not been modified in waveEditor were fine - and all the edit tools appeared when the cliops were highlighted. But it was not possible to trime or edit the clip which had its audio boosted in Wave Editor. Has anyone else had this problem - and can it be overcome??
Thanks for the response. The original video was mostly (standard) DV (90%) - shot on an Panasonic DVC 30 camera. There were also a few clips from a JVC camera - which uses MOD files -- which I understand are just MPEG 2 files with a different extension.
Cyberlink.com uses analytical cookies and other tracking technologies to offer you the best possible user experience. By using our website, you acknowledge and agree to our cookie policy. For more information on cookies or changing your cookies settings, read CyberLink’s Cookie Policy.
