Nigel Jones

My feedback

  1. 7 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Nigel Jones commented  · 

    Update
    Just tried to see if new version 14.6 of Premiere Pro fixes this 'Lost Preview Files' issue - but doesn't.
    When using Quicktime based preview files (I'm using Apple Pro Res 422 files) they somehow get lost - plus looking at the file information in the Preview Video files folder reveals that they are there BUT time stamped into the future !. eg Today (24 November) some of my preview files are date stamped December 2nd 2020 ?. Weird.
    The Windows 10 Pro operating system is at 1909 version (all Updates installed) and no other software on my machine exhibits such behaviour.
    So Adobe team - what is being done to investigate this issue of lost Quicktime preview files?.

    An error occurred while saving the comment
    Nigel Jones commented  · 

    So I eventually tried version 14.2 again then to 14.3 on this Rendered Files lost issue with still same problem
    I also had a weird problem of all rendered files in the Video Preview Files folder being dated 5 days in the future !!.

    I posted something on the Premiere Pro community forum about this see -

    https://community.adobe.com/t5/premiere-pro/losing-rendered-video-clips-and-time-travel/m-p/11262981?page=1#M280886

    Ann Bens said she had seen this issue in some AE cases and thought it was related to QuickTime files only. I see Rasheed is using Pro Res.
    Updating to 14.3.1 (and some Windows 10 updates as well to version 1909 ) seems to have made this issue go away....at least the dates for Rendered files are OK now and so far I do not appear to have lost rendered files when re-loading the project, but I am keeping a close watch on this.

    I'm editing 150MBs H264 4K 3840x2160p files from my GH5 (no proxies) and the rendered files are Pro Res 422 (not i-Frame MPEG) with plan to make ProRes422 full rendered master from which then to produce various format copies - eg H265 4K etc

    Some response from Adobe Engineering on this bug report thread would be useful please. eg: Have they addressed it as enough examples below to try to reproduce it on Quicktime files?

    Nigel Jones supported this idea  · 
    An error occurred while saving the comment
    Nigel Jones commented  · 

    I've just come across this problem. I'm editing in 4K and creating a final Master Pro Res 422 file so all render previews are in Pro Res 422.
    I created a folder in Preferences to make sure each Video preview is in he right posiiton. But reading below I see that you should not change default files - which is a bit crazy on Adobe's side as you have an option to create a Custom Location for Rendered files.
    I am losing rendered files every time I close project and re-open it.
    This is taking ages each time the project opens and is a pain in the xxxx.
    I'm using Version 14.1 (not very latest).
    Any comments Adobe?

  2. 92 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Nigel Jones commented  · 

    ...there are some sensible comments in this thread Adobe Premiere Pro team - so if you have been doing some work behind the scenes to improve stability, then it would be worth your time outlining what improvements you are making to your customers.
    This is after al, not a one way User Voice Forum is it ?

    An error occurred while saving the comment
    Nigel Jones commented  · 

    I think the code base for such a program encompassing all those funmctional blocks could be a bit difficult to manage. I think the focus on this post is trying to improve QA process on Premiere Pro releases - please.
    With Premiere Pro it is ensuring the basic foundation is strong across a selection of MAC/PC Windows environments (wherever possible - not easy I accept that)
    But I don't want my house painted a fancy colour if the foundations are going to crumble

    An error occurred while saving the comment
    Nigel Jones commented  · 

    Also agree - QA process of Premiere releases appears to be becoming non existent and they rely on the user base to debug fundamental errors. Makes you wonder if the code is a Patch work quilt !!!.
    Also agree - to stop releasing features that are not priority - Adobe are just releasing these to add to their Marketing glossy brochure. Forget those and focus on making an application work and stable please.

    Nigel Jones supported this idea  · 
  3. 5 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Nigel Jones commented  · 

    Thank you James for coming back to me. I am not a professional user and would say I was at an intermediate level on Pr and only just learning the Ae app.
    On the Pr Graphics question you asked about problems with re-sizing.
    I think Pierre Lois has summarised this well. I tried to move/resize a wipe on graphics element in Pr and found that all manner of changes were taking place when I wanted to only move the group itself.. This may or not be attributed to the Grouping method, my unfamiliarity, or an actual software issue.
    Again, I'm not sure this is possible but can elements have different boundary and anchor point colours (colors) to help see what you are doing?.
    I understand the need to not have to maintain two functional parts of software code (eg Legacy titler as well) for streamlining maintenance, but finding better ways to gather user feedback on such an important user interface would help us and Adobe in the longer term.
    There will always be a compromise, but engaging with your customers in a better fashion will help Adobe gain better credibility in the longer term too and stop users migrating to the competition.

  4. 161 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  86 comments  ·  Premiere Pro » Essential Graphics  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Nigel Jones commented  · 

    I've been following this and many other User Voice threads now for some time and I think this is one of the few threads where I have seen any proactive positive response from Adobe on User Comments/Feedback.
    This is a positive thing, but clearly there seems a distinct lack of formal process and information gathering on User Feedback by Adobe on introduction of new features/User Interfaces.
    I question why it has taken until now for Adobe to interact on this Legacy Titler issue.
    I have switched to using the Graphics Tab titler tool myself and have to agree with the recent User Feedback posts that it falls short in a number of areas.
    In particular I have also had issues with the Shapes/Titles resizing and this is very messy.
    In some cases Premiere (14.3.1) has repeatedly crashed whilst I was trying to change a Font in a MOGRT template.
    I'll check out the exact circumstances of this again and post a reported bug

    In the meantime - can Adobe provide feedback to this forum on how the formal process of how you collect User Feedback in a 'structured manner' prior to pulling the plug on established features and User Interfaces.
    To me this is not obvious !!!

    I will check out the title in

    Nigel Jones supported this idea  · 
  5. 4 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Nigel Jones shared this idea  · 
  6. 45 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Nigel Jones commented  · 

    Can we have some feature updates that users actually need for a chnage instead of some of the obscure stuff that new releases seem to contain

    Nigel Jones supported this idea  · 
  7. 3 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Nigel Jones shared this idea  · 
  8. 37 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    41 comments  ·  Media Encoder » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Nigel Jones commented  · 

    Regarding comment below about Premiere 2020 H264 bluRay export - not tried this yet but Premiere 2019 (13.1.5) exports work but you have to run Encore.exe as windows 7 compatibility and run as administrator as well. In my opinion the chances of Adobe fixing anything to do with BluRay issues in future are zero. No interest shown in over 2 years.

    An error occurred while saving the comment
    Nigel Jones commented  · 

    Can Adobe Engineering or Product Management please advise if any changes have been made to AME in the last update version (13.1.3 - Build 45) relating to H264 Blu Ray Preset
    Just for info I have just created a fairly large project (18GB) on Blu Ray using H264 Blu Ray Preset export via Premiere Pro (13.1.4 Build 1) which I assume uses AME engine.
    The original problem is with Encore 6 and the Session Script issue.

    With the latest version of AME and running Encore in Win 7 compatibility mode - and as Administrator the project built successfully
    It would however be helpful for users do know what is going on as there has still been no feedback on this issue since I posted the original problem in Sept 2018.

    Have engineering fixed it or not ?? - as my last Project Build worked.

    Please can you break the radio silence and advise

    Thanks

    An error occurred while saving the comment
    Nigel Jones commented  · 

    Closing this one. It has been repeatedly ignored by Adobe , despite the fact some people still cannot get the project to build with Win 7 compatibility. Doesn't explain failures on MACs either.
    After 9 months of wasted time with Adobe support. Move on.
    ...and they slept happily ever after.

    An error occurred while saving the comment
    Nigel Jones commented  · 

    So a global mail from Adobe Support telling me that Media Encoder 2017 (Version 11.1) would now infringe third party copyright issues implies this version (the last one to work for Blu Ray Preset encoding correctly) would be pulled.
    [Did any of you posting here get such an email ? - dated 10th May 2019]

    So far we have no comment or explanantion from Adobe Product Support Management on this issue whatsoever.
    The whole scenario is puzzling - since many got Media Encoder version 2018/2019 version 13.x files to run in Encore 6 by running this is Windows 7 mode - which implied a Windows related issue in the later AME releases.

    However, given this new statement from Adobe about Third Party IPR in Media Encoder 2017 (V 11.1) - it would suggest the later AME versions had different encoding software code entirely for AME 2018, 2019 etc to support Blu Ray Export??

    As of May 2019 - This still leaves users without a stable solution and what seems difficult is to communicate the fact to Adobe Product Management heads is that Blu Ray encoding is still widely used.

    If it can't be fixed - then the proposal to Adobe AME team is to source another third party solution house for Blu Ray encoding within AME future versions ....

    Rather than continue this thread - can we get some positive response from AME team please.
    This is what this Forum is designed for - correct ?

    An error occurred while saving the comment
    Nigel Jones commented  · 

    I thought I would add some new comments on this issue. I was surprised to see this is also affecting Mac users so the Windows 7 or 10 issue doesn't apply ??. I was also called by an Adobe customer service advisor last week who assured me that there were 'thousands of fixes' in 13.1 version and the BluRay H264 issue had 'probably' been fixed in the latest release. Sadly, it does not appear to be the case.
    The other useful info someone posted was to download the TMPGEnc plug in - which has a separate H264 encoder with the BluRay H264 option - but that will cost you money which is not really acceptable when you are paying your monthly Creative Cloud fee.

    Adobe - >> we are still waiting for your response months later ?.

    An error occurred while saving the comment
    Nigel Jones commented  · 

    Thanks to those who have added comments and voted on this from my original posting back in September last year. Still no news / response on Adobe AME Product Mgr / team about this.
    Do we need over 1000 votes ? !

    An error occurred while saving the comment
    Nigel Jones commented  · 

    Can we please get some comment from Adobe AME Engineering or Product Managment on this issue please. It is very clear people still need to produce H264 based Blu Ray discs. This is broken and used to work.
    Total radio silence from Adobe on this issue is not acceptable - as per comments of several users.

    An error occurred while saving the comment
    Nigel Jones commented  · 

    Regarding Justin's comment. Encore 6 seems to be running on Windows 10 64 bit version OK on my machine - apart from the annoying _ves issue caused by AME 2018 as per this thread.
    My whole creative suite is running on Windows 10 64 Bit - but I have stuck with the Windows 10 1709 release for now (not 1803 version). Take an ISO system image of a running system is also always wise.
    You could configure your machine to have Windows 7 and Windows 10 dual boot if you wanted to avoid having 2 computers.

    An error occurred while saving the comment
    Nigel Jones commented  · 

    Thanks to those who have voted and supported this request for the BluRay H264 export in 2018 AME to be fixed. Agree with all the comments that BluRay disc production is still important.
    Can anyone inform me and others how we get any feedback on this request for bug fix from the Adobe AME engineering team?.
    I assume this Bug report/Feature Forum is monitored by Adobe AME team (mediator) ???. I hope so.
    Bugs like this are more important to fix than new features - customers are paying for working software. I can't 'create' with my Creative Suite anymore.
    Any feedback on this would be welcomed.

    Nigel Jones shared this idea  · 
  9. 1 vote
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Rush » Working Across Devices  ·  Flag idea as inappropriate…  ·  Admin →
    Nigel Jones shared this idea  · 
  10. 1 vote
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Media Encoder » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    Nigel Jones shared this idea  · 
  11. 86 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    50 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Nigel Jones supported this idea  · 
    An error occurred while saving the comment
    Nigel Jones commented  · 

    Would support the comments about re-instating Legacy Titles as they were. This got me the other night and thought my Premiere Pro installation was screwed up - then realised this was infact a 'new feature' of the latest release. When Wes Howell refers to a new patch below - is this the latest 2019 13.0.2 version?.

  12. 83 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    24 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Andrew,

    your comments are as thoughtful as they are timely.
    While I usually would have to close this item as it isn’t specific enough, I’m gonna leave it open so others can see this and add comments:

    Please come back and vote for exactly the items that you feel need a V2, some polish, or just remove friction in areas that have grown over time. Add a new request if what you’d like to see revised isn’t discussed yet.

    We’re already seeing good patterns on User Voice as to which items and areas would be good candidates for upcoming releases. You can see some of the top runners already marked as “Under Review”. And while that won’t tell you with which release exactly we’ll have things ready for you, it’s an indicator of an investment we’re making to improve features and workflows where most users express their needs.

    Cheers,…

    An error occurred while saving the comment
    Nigel Jones commented  · 

    Agree with all comments so far that focus for Adobe PP Engineering team needs to be on fixing things that don't work - eg: not being able to make a BluRay H264 disc from a PP2018 project. AME related bug - as PP 2018 calls AME 2018, ... so users are stuck. Paying a monthly Creative Suite subscription where PP existing features no longer work is not acceptable. Get bugs ironed out, otherwise having a glossy Marketing feature tick against other SW vendors list won't help you sell PP software anymore. Your customers will have gone elsewhere because of unreliable products !..
    R&D teams might like to develop new cool features - but in the real world making sure youyr software is stable, reliable and can reduce cutomer frustration is priority.
    I know as I have been R&D Manager in a large Telecomms orgnaisation for Hardware and Software. If we screwed up a release that caused one feature to stop working - we had to put this on a top priority programme and release a patch if necessary. It would be refreshing to see this from Adobe, then we would be encouraged to stick with you.
    I also like the comment below about User Voice being a good start - however, Adobe is not talking to its end customers properly. Its one way traffic guys..........

  13. 5 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    Nigel Jones shared this idea  · 

Feedback and Knowledge Base