Adobe media encoder cc won't save destination output file

Similar Questions

• Encoder Media won't save destination output file

  I'm running on a rugged PC.

  I've always had my encoder media dump all my makes it in the same folder.  For no reason I can understand, gives ME my destination output file by automatically turning off that box in my Preferences each time menu that I send a video for the first rendering.  I then go back to preferences, select the check box and specify my destination.  To test this, I set my destination then close me.  I opened ME and the destination is always there.  When I send a file of first for ME, the destination of the file area is now disabled.  Am I missing something simple here?  The question is perhaps something first?

  I had a separate issue with the titration in the first module not opening any more.  This issue is still unresolved, but a member of Adobe suggested I have delete the workingset.prsl.  This ME issue has been a problem since then.  I can't find where the problem is.

  Any help would be great.  Thanks in advance for reading and helping.

  T

  What version of Adobe Media Encoder and Premiere Pro are you using?

  You could try running SOUL alone without running first.  Now please change the destination of output in preferences and then leave the SOUL.  This makes the change lever?  This destination is used when you import directly files in the SOUL.  Please note that this output destination is replaced by a destination specified in the parameters of Premiere Pro export dialog box before queuing of SOUL.

• Adobe Media Encoder CC won't let me import a specific sequence of Premiere Pro

  I'm on a trial version of Adobe Media Encoder CC. I try to import a Premiere Pro sequence (I have an old version 2.0) and it won't let me choose a specific sequence within the project, it will let me only import the first sequence. The dialog box sequence which is supposed to open when I select 'Import first Pro Sequence' under 'File' does not, let me only to select a project and will then automatically import the first sequence for this project. The box in the preferences for "Import sequences of natively" under Premiere Pro is grayed out and I can't seem to change, which is what I apparently have to do to activate dynamic links. However, I think that it is possible that either the trial version doesn't let me do, or my first version is just too old and there is a mismatch.

  You must have a newer version of Premiere Pro to use dynamic linking.  The versions of Premiere Pro and SOUL should be of the same generation.

• Adobe Media Encoder save/export as swf formats?

  Adobe Media Encoder save/export as swf formats?

  If yes how?

  Thank you

  N °

  Why would you do that?

  You can view and export to F4V or FLV formats if your intention is to play the videos in Flash Player.

  formats that SOUL can export:

  http://helpx.Adobe.com/Media-Encoder/using/file-formats-supported-export.html

• Adobe Media Encoder CC 2015 slow rendering time

  Hello!

  I'm new to video editing in general, but I'm quite intimate with the PC hardware so here.

  Specifications:

  • The stock of 4770K i7, no thermal regulation speed
  • 8 GB 1600 MHz CL9 DDR3 RAM
  • GTX 780 + 170 MHz clock and 110% limit/95 degrees C temp power target
  • Driver 368.39 used
  • 3 x Samsung 840 EVO (no raid)
    • Windows 10 64-bit running off SSD1
      • PE/AE/SOUL installed on this drive
      • Cache / Scratch areas on this drive
      • Images under development
    • SSD 2
      • Games
    • SSD3
      • Games

  I save images using shadowplay NVIDIA from a 75 Hz screen 2560 x 1080. The output file is a 1920 x 1080 60 fps 35Mbps bitrate H.264 MP4 file. (1920 x 810 with black bars).

  I would add that sequences Adobe Premiere elements 14, do any editing that I have to do, and then export it to a file of bitrate MP4 1080 p H.264 12Mbps. The rendering process usually take around 10-12 minutes to 6 minutes video.

  I then add this file to output in Adobe After effects CC 2015, create a composition with drag and create a button, add a few layers of text and export it via Adobe Media Encoder CC 2015 (AE supports native H.264 from what I understand) with the SAME PARAMETERS. But this time, and I estimate that I type here, render times are 40 minutes.

  I ran a few tests and in the course of the first to make the CPU turns to about 80% CPU and the use of 1.8 to 2 GB, as I watch often some youtube in the meantime, so that understandeably not 100%. However, to the course to make AE/SOUL, le CPU CPU remains at about 30% CPU and 1.8 GB ram usage. With the help of the Mercury Playback Engine GPU Acceleration (CUDA) I expect to see more high on my GTX 780 loads, but he is 2-3% of load, so anything.

  Since my render outputs are (to the best of my knowledge) identical between the EP and shall return AE/SOUL, it seems that the use of material by SOUL is in this case. Other posters have suggested that some effects require the previous frame to be returned to pass, but I have not used such effects, are limited to simple text.

  So what's happening? I would appreciate any insight you have on this and I stand ready to provide more information that you need.

  Kind regards

  Corentin Robin wrote:

  First of all, wow. Thank you so much for the depth and quality of your response! If everyone had that kind of mentality, forums would be a very different place...

  No problem! That's why I'm here.

  It is certainly useful that you said your question clearly, with a lot of info and he asked respectfully. Quantity of, "why his does not work u should help me solve this NAOW! 1. 1. ' messages with no information is astounding.

  Corentin Robin wrote:

  I'll try to be to condense my game data on a single disk or both and use the third exclusively for editing. Or I could buy a new one, if the budget allows.

  This would be ideal. In my freelance studio, I have three separate units

  1. OS/software
  2. Footage
  3. Cache (if there are different types of player, it should be faster than you [I know your are currently all the same, it's more for future fans forum])

  It will probably not help much for the rendering speed, but it should help when you're interacting.

  Corentin Robin wrote:

  Before moving on to something else, I want to explain what I'm doing with text. I add text and overlay video, with sometimes a few very basic motion tracking (I can't forget this feature if I need). To the best of my knowledge, PE lets just add a black screen with text over time, like on a Blackboard for example. No text overlays/over-the-video (if it has no meaning...). So respect that, Premiere Pro have these features? If so I could make the switch.

  Certainly, you should stop using the Premiere Elements and start using Premiere Pro. Not only it gives MUCH more flexibility in the work, but you can layer objects of type as much as you want on top of your film.

  He was also transparent enough with AE. By example, if you have a shot that you want to add text, you could cut the part that would have text and simply right-click and choose "replace with After Effects composition. That images will be replaced with a dynamic link to a model of EI that already contains the images that you are handling. You save your AE project and results will be displayed immediately on the first! It's really convenient. If you want to keep this direct link, you can. Or if you are sure you are finished with AE work and wants to read smoothly at first, you can choose to make and replace it. It restores an intermediate file to AE and replaces the model tied first with her. VERY useful feature.

  If you keep track of movement, you probably want to use AE. Although you can make an animation in Premiere Pro, AE is much more suited to do. And if you start to get really fancy, you probably want to do some rotoscoping too.

  Corentin Robin wrote:

  I understand that EI requires much more accurately, and the way you explained it enabled me to understand one of the big question I had with her, which was "why reading in real time is so difficult in AE? You answered that perfectly, cheers!

  There is much more detail in the fact that I could get! Basically, AE must first build a cache, and then he reads. Maybe I should have said that. It is even simpler and shorter!

  Corentin Robin wrote:

  On the issue of compression, I realized that the work of a compressed codec is not ideal. My gross output of Shadowplay file was indeed H.264 because I believe that is the single output file, it allows. I don't think I can do without shadowplay for now because it has unique characteristics which cannot be replaced:

  • For extremely low hardware with Nvidia drivers
  • Ability to retroactively save a video after an interesting "keep-worthy" event, to avoid recording 24/7 in the hope of something interesting

  Those who do not sound like some very useful features. Just make sure that you get quality settings in the codec to achieve a data rate as it allows.

  Corentin Robin wrote:

  Also, to continue on the issue of compression, I got mixed responses regarding this. Some, like you, would say that working with H.264 sacrifices quality and performance, but some say that it is not a problem since the youtube compression will be severely disfigue the file in any case.

  YouTube can recompress, Yes. But if so, it adds ANOTHER layer of compression. That would be an argument even more important to preserve the quality of your side as much as possible.

  Corentin Robin wrote:

  I think my question would be: I would win a much higher quality using Fraps/Dxtory where I can control the settings of the raw images (keeping in mind I lose the comfort of ShadowPlay) even though the compression of Youtube should (I think?) disfigure this film?

  I think that the benefits of ShadowPlay outweigh the concerns that I had about compression in only one step. I still say don't do any other steps in making H.264s again and again that you transmit your project between applications. If you need to make something (you won't have to if you start to use together the Premiere Pro and AE), renders an intermediate codec until you create your deliverable.

  Corentin Robin wrote:

  So, keeping in mind of all of your suggestions and the constraints I have / has chosen to conform to, I should:

  • Have the work files on a separate disk, with areas scratch on this drive or free
  • Replace PE PP to eliminate the need for the AE and have only a single record
  • Since a single rendition is necessary, it is therefore more a real need for an intermediate codec low compression/lossless

  Yes. Although, you can still use AE, you have eliminated the need to make the intermediate files if you use Premiere Pro and AE set.

  In addition the Dynamic Link workflow I mentioned, you can also (once you have finished your editing in Premiere Pro), your Premiere Pro project import into AE. Use import > import Premiere Pro control project. She puts your complete sequence in AE with each cut on its own layer. You really need to do if you started to do really complex with your AE work if.

• Media Encoder CC won't start not

  Windows7 64 bit

  Media encode CC (7.0.1)

  SOUL has worked some time. I exported a few jobs in its queue. Everything is good. Tried to cancel work and it appears to hang. You had to kill the application from the Task Manager.

  Since then SOUL will not run. It crashes at startup. No screen... nothing. Appears briefly in the Task Manager, then disappears.

  I deleted all the files from C:\Users\login\AppData\Roaming\Adobe\Adobe Media Encoder\7.0

  Have reinstalled PremierProCC after uninstalling and using the cleaning tool.

  Still no luck. Is there a queue no matter where that should be removed?  A may entry registry?

  A MUCH SIMPLER SOLUTION: open the file (C:\Program Files (x 86) \Common Files\Adobe\SLCache\X19zbGNfZmVhdHVyZXNfXw==.slc) in any text editor, remove all content, save it and put the file read-only. You never have to remove it again and you won't have to mess with all this batch file, load order stuff.

• Adobe Media Encoder CC2015.3 stuck in reading XMP

  I'm really really frustrated with Adobe CC bugs.

  I just formatted and reinstalled all (Adobe CC2015.3) on my new PC:

  -10 Windows

  -intel I7 - 6900K

  -128 GB DDR4 RAM

  -OS on a GB 512 m2

  -Project files on two SSD RAID 0.

  Now, when I send my soul and start the queue, SOUL rest hung on "reading XMP" for like an hour. After that, he moves and restores, but once the sequence is complete, it restarts to read XMP...

  You do understand that I need to export 70 sequences (which take 5 minutes each) and I can't wait for this 100 hours just to read XMP SOUL!

  I also tried the following in the SOUL: edition-> Preferences-> metadata-> set to none (no metadata export) all fields

  But it does not work.

  I read ALL the threads on this subject, without finding any solution.

  Please help me, I'm going to face a huge backlog that will make our customers very angry...

  Thank you

  Hi, thanks for your answer! I just finished a call with the help of Adobe and we tried your suggestions with no result.

  Moreover, after an hour of troubleshooting came us to this conclusion:

  The problem may be related to the fact that this project was converted in to CC2015.2 under Windows 7 CC2015.3 in Windows 10. It is unclear why this is happening and it seems that there is no solution to this. They said that if I create a new project from scratch I shouldn't re-encounter this problem.

  However, we found a working solution:

  Put out the sequence you want to export, click on file > export > selection as a Premiere Pro project (I have the Italian version and I translated it here on the fly... not sure whether this is in fact the correct translation) and save some part of these projects.

  Then, open the project just created, export the sequence on Adobe Media Encoder, click the game and this is! Loading XMP spend 1 hour to like 3-5 minutes (acceptable).

  Well... it's a workaround, not a solution. But it works a little bit.

  I'll let you know if I have other problems with new projects.

• Adobe Media Encoder crashes on Windows 10

  A week ago, I "upgraded" to Windows 7 Pro for Windows 10 Pro and now...

  In my Premiere Pro CS3 (I know, I know, why am I not spend a ton on an upgrade of the CC...).

  When I'm ready to export a sequence, and select Adobe Media Encoder, I get one almost

  immediate crash and the popup says: "sorry, a serious error has occurred which requires.

  Adobe Premiere Pro to stop.  We will try to save your current project".

  Everything on my Adobe Creative Suite CS3 Master Collection worked perfectly

  with Windows 7, but go back to Windows 10 is not an option.

  I am running a Dell XPS 8100 Intel i7, 8 GB of memory, 64-bit operating system.  Should be enough

  horsepower!

  Thus, Adobe has a 'fix', and/or the community of users has a method/work around

  that I could use?  For now, my only option is to export an AVI 'Movie.... ', but I

  was happy with Adobe Media Encoder and I want much she's still running.

  Suggestions?  Miracles?

  Thank you!

  Hi Johnnie_D,

  I apologise for this inconvenience, but I'm not sure if the CS3 products are compatible for Windows 10 or not.

  Because Adobe Premiere Pro CS3 was launched in 2007, Adobe does not any further development on this version of Premiere Pro.

  In addition, Windows 10 was launched in 2015 and only creative cloud products have been tested with this operating system.

  My suggestion would be to re - install the Premiere Pro and SOUL on this machine.

  Otherwise, use it on Windows 7.

  Thank you

  Ilyes Singh

• First and Adobe Media encoder crashing with the module KERNELBASE. DLL

  I have 2 computers windows 10 crashing while selecting a folder in the window of browser Explorer of files within these programs. These machines is 2 weeks, with 10 Pro from the start windows. The other machine has 3 months with windows 7 upgraded to Win 10.

  Machine 1
  

  ASUS X 99-Pro

  Six Core i7
  

  32 GB of Ram

  GTX 980

  Intel 750 PCIE SSD

  
  

  Computer2

  ASUS Rampage IV

  Six Core i7

  64 GB of Ram

  GTX 780

  Samsung 1 TB SSD PRO 850

  
  

  
  

  
  

  
  

  Name of the failing application: Adobe Media Encoder.exe, version: 9.1.0.163, time stamp: 0x564db283

  Name of the failed module: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3

  Exception code: 0xe06d7363

  Offset: 0x000000000002a1c8

  ID of the process failed: 0 x 4150

  Start time of application vulnerabilities: 0x01d136ce9193dbc6

  The failing application path: C:\Program Files\Adobe\Adobe Media Encoder 2015\Adobe Media Encoder.exe CC

  Path of the failing module: C:\WINDOWS\system32\KERNELBASE.dll

  Report ID: 3725abd1-4ce3-44bc-97d0-f44f2a9ec7a5

  Faulting full name of the package:

  ID of the failed package-parent application:

  Name of the failing application: Adobe first Pro.exe, version: 9.1.0.174, time stamp: 0x564dce25

  Name of the failed module: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3

  Exception code: 0xe06d7363

  Offset: 0x000000000002a1c8

  ID of the process failed: 0x3c74

  Start time of application vulnerabilities: 0x01d136cc8be4d555

  The failing application path: C:\Program Files\Adobe\Adobe Premiere Pro 2015\Adobe first Pro.exe CC

  Path of the failing module: C:\WINDOWS\system32\KERNELBASE.dll

  Report ID: f4c46647-06bd-4e15-a3ac-13a2433d77f1

  Faulting full name of the package:

  ID of the failed package-parent application:

  Thank you Lord! SOLUTION AT LAST!

  After having been informed by tech adobe support that: "I'm sorry, but this is a file from the base of the core of the system, we cannot do much."

  I decided that I was going to test each component in user accounts and find the culprit manually.

  I have studied everything that I could all kernelbase.dll NTUSER.dat and parameters of the first.

  From what I could gather kernelbase.dll if crushed more often when the 32-bit and 64-bit settings are not configured right.

  I downloaded Registry Explorer 0.7 and analyzed a new vs account a "corrupted".

  I discovered that windows keeps a record of the last access programs via OPEN/SAVE location.

  It is located in:

  HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\OpenSavePidl MRU\prproj

  To solve the problem:

  It comes to registry changes, do at your own risk!
  

  1. Create a new user account with admin rights. I'll call it "AdminRescue".
  2. Connection in "AdminRescue" and open first cc, check that the problem has disappeared.
  3. Now you could start using the new account and forget the old, but I find myself that making 3 times in 4 months, the issue will come back again.
  4. The solution is to runREGEDIT under the new account that you created.
  5. Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\OpenSavePidl MRU\prproj
  6. Select prproj and export it to a disk usb or c:\adobefix
  7. Disconnect from the new user account and log in to the old damaged account
  8. Run Regedit
  9. Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32\OpenSavePidl MRU\prproj
  10. Select prproj and Delete
  11. Select OpenSavePidMRU and import the regkeys exported in the new account. located in the usb or c:\adobefix
  12. FIXED!

• Rendering of the texts of the composer issues each line with Adobe Media Encoder

  I find the paragraph of text defining "Each Adobe line Composer" a huge time saver when dealing with large amounts of text in the aftermath. I rarely have to do manual breaks follow-up or line to make look it good, rather than working with the standard single-line composer.

  The problem is that when I give thanks to Adobe Media Encoder (which I have to do because they removed H264-mp4 AE:s internal renderer support) the text is treated as a single line of typeset text. If the final result does not resemble my AE project.

  I found two solutions to this problem:

  1. make a video file without loss in the AE render engine and then compress him with Media Encoder. It takes more time and HARD drive space, and it did not allow me to continue working at AE while rendering.

  2. only use single line text composed and make all the settings manually, the old school way. It would not be a problem if I had not already used and fell in love with, the option of each line.

  Is there someone who can think of a third and better preference, solution?

  I use both CC 2014 of AE and AMC.

  Looks like you have found a bug that has never bitten me before and has nothing to do with h.264 compression. Here's the rendering of your text to a tiff file.

  I have filed a bug report and suggest you do the same.

  

• script: Add to the adobe media encoder

  Hello guys!

  Tout d’abord félicitations les nouveautés et le badass look d’After Effects. I really enjoy!

  But I'm really disappointed to see that the function of rendering h264 has disappeared. Who really destroyed my workflow boom!

  Because I have a lot of jobs for a show room, where I very often do 360 degree projection mappings and the overall resolution there are approximately 26 000 width px. What we do, because we're using watchout as reading system and the management of all the projectors, is splitting h264 movies to their maximum width resolution. The things is that for example for an event we have around 20 to 30 animations and 1 animation is divided into 6 movies... What we did usually - we wrote a little script that automatically splits the film in 6, dial before all, align them all and returns all videos with predefined parameters h264. So... my question is now... How can I modify my script and configure it to send all the comps pre composed, resized, aligned, new to Adobe Media Encoder and use a h264 predefined make the adjustment? I couldn't find any more info on the bridge between AE and Media Encoder script.

  See you soon,.

  Marin

  PS: I know that we can use Final Cut Pro or Motion for resolution of the h264... but it's a kind of workflow I had used to work... everything happens in a single application... and no annoying hundred times save slot, not made in the form etc.

  Hello sailor,

  It is true that it is a pain to manage outside EI h.264 encoding.  You can write a script that calls the app.executeCommand () function and passes the code that calls the "add to Adobe Media Encoder queue... "under menu Composition of AE.  OK, digital, code for this command is 3800.  So you would simply browse the comps you wanted and then open them in the main Viewer using the method. openInView() that brings them into focus for say.  Once it is open you can then send the SOUL model with app.executeCommand (3800).  On the side of the SOUL, you need a default template to render output parameters you want.  When your script adds a model to the queue of the SOUL, it will take these parameters.

  Now, you could do all this, but have you seen AEmpeg than aescripts posted yesterday?  It allows you to 100s of codecs using ffmpeg right of AE.  While it costs money, at least it will open the door to a streamlined workflow and a variety of codecs you might need.

  Arie-

• 'Add to the Adobe Media Encoder queue' missing

  Does anyone know why my version of AE CS6 doesn't have the option "Add to Adobe Media Encoder Queue"? http://t.co/UFTfFXN8VL

  The Add To Adobe Media Encoder Queue command is new after effects CC; There is no in After Effects CS6 or earlier versions. The command is available under both the file > export and Composition of menus. The keyboard shortcut is CTRL + Alt + M (Windows) or CMD + Opt + M (Mac).

  To add a model of EI to the queue of the SOUL in CS6, you can do the following (which also works in AE and SOUL CC):

  1. Drag one or more comps in the AE project Panel to Panel line of SOUL. (Save your project first.)
  2. Drag the Office AE project file in the queue of SOUL Panel. Choose a unique model, and then click OK.
  3. In the SOUL, open the Add Source dialog box: Choose file > Add Source OR click the Add Source button (plus sign) in the queue Panel OR double click in the empty area of the SOUL queue Panel. Choose the AE project file, click Open, and then choose a unique model and click OK.
  4. In the SOUL, choose file > add After Effects Composition. Choose the project file AE on the left side of the dialog box, and then choose one or more compositions on the right side.

• Adobe Media Encoder CS6 crashes when exit

  OS X 10.7.4

  Several types of materials

  Adobe Media Encoder CS6 from Adobe Production Premium CS6 as installed.  NOTE: CS6 has been installed under one user other than the user who is having accident of SOUL.

  Question:

  Open the SOUL.  Encode a file or do not encode a file because the final result is not serious.  Now quit SOUL (shortcut key or file-> exit).  SOUL, then crashes.  Keep in mind that no other program CS6 is affected in this way, just SOUL.

  I came across this problem weeks ago and found a solution that worked.  The fix was to remove one of the many many files adobe creates in your user folder.  The problem now is that I can't find that posting even where was the fix.

  I deleted this "mystery folder" we'll call it and then SOUL CS6 worked well.  The capture was that I had to redo the 'Adobe ID' together in BS sign and re-enter the serial number when I opened one of the other programs.

  Assumptions as to where this file would be so I can delete it again?  I was hoping that others may have run on this same question.  I'll keep looking for the correction and post it back here, if I finally find.

  Try going to "~ \Library\Preferences\Adobe\" and then delete the files 'Adobe Media Encoder' and 'Commons '.

  This put SOUL in default state and remove the media. Personalized presets will be deleted so make sure to save them.

• Adobe Media Encoder CS4 will not convert video .mov

  Hello

  I have Adobe Media Encoder CS4 installed on my computer and I am trying to convert a .mov video in a format that can be edited on windows movie maker, and when I convert the video converts audio very well, but there is only a black screen. Any ideas as to why this could happen?

  Thanks in advance.

  John Marks

  Right on happy it worked. Now, technically, we could probably use FFmpeg convert these into something that WMM would accept, and you should really be style, then.

  Let's try this: duplicate the BAT file, I sent and replace the name 'mov2avi '. Right-click and select Edit, and then replace the last line with this:

  for %%a in (*.mov) do ffmpeg -i "%%a" -vcodec mjpeg -qscale 1 -acodec pcm_s16le -f avi -y "%%~na".avi
  

  Save, and then run it. This will make a larger file, but you should be able to import this right in WMM. Let me know!

  Yes, just downloaded WMM Live 2011 (or whatever it is called) and the import AVI in full. I would certainly recommend that, instead of convert twice.

• Adobe Media Encoder Export Settings window size problem

  Any help on this would be appreciated: I use a MacBook pro, osx 10.6, CS4 Web Premium. I used to have a connected external monitor, which had a much higher resolution, so when you use Adobe Media Encoder I have to click the button settings on a video to get the export settings window, then stretched from the window of export settings for the size of my external screen. Now, I use my laptop computer, and export settings window does not resize top buttons left to adjust it to the size of my laptop and the low third export settings window get cut so I do not see the ok/Cancel buttons etc.

  I tried re-installing media encoder (via reinstalled flash using CDs) to try to 'reset' the window sizes, does not solve the problem.

  If anyone knows of any other preferences or something that I could remove to solve this problem, I can be grateful.

  Yes, I received the same answer. This means that adobe don't use OS native windows (shame on them!). I just tried something with CS4 that worked, however. Try this:

  Stop Media encode

  Go to UserHomeDirectory > library > Preferences > Adobe > Adobe Media Encoder 4.0 > and delete the file called "AMEPrefs.xml" and "AppPrefs.xml".

  Then restart Media Encoder. For me, this reset the window size and placement. I tried to move the window of export settings down to half of it was above the bottom of the screen. Once I deleted those files and rebooted, the window was smaller and repositioned.

  If this does not work, try to download the demo of this product:

  http://irradiatedsoftware.com/sizeup/

  It is said that Adobe programs are programs of "disorder", they won't probably resize, but they should at least move. If nothing else, maybe you can move the window value is negative (upwards) so that the resize handle is visible, then move it down so that the header bar is visible again...