Premiere Pro & Windows 8

Does Premiere Pro work with Windows 8? I'm having some major issues. When I first installed Premiere Pro I got this warning message:
"DirectX cannot be run on this version of Windows. This version of Windows is either Windows3.s or a version of Windows NT that does not support this version of DirectX. Please do not attempt to install DirectX except in these operation systems. ctX is designed to work with Windows 95 or later and Windows NT4.0 and later only. This error message can also occur if the computer hardware is incompatible with this version of DirectX"
It then gave me the option of continuing anyway. When I finally got Pre Pro installed when I started it I got this error message:
"The Currently installed soundcard driver does not support Direct Sound Input. Recording Audio is not possible"
About my computer. It's brand spanking new. Pre Pro is the first program I have installed on the system. I called the store that built the computer. They took remote access to it and installed a different sound card driver. That "apparently" took care of the sound card problem. However when I try to capture video I get this error
"can't find capture inpoint"
I've combed multiple forums and such and no one really seems to know what's going on. I've tried all the solutions I've come across and nothing seems to work. So now I'm wondering if Premiere Pro & Windows 8 are even really compatible.
Thanks in Advance.

>About my computer. It's brand spanking new.
There have been a few messages about Win8 problems (I've seen more of those in the PreElements forum) and a few more saying Win8 works just fine... so it MAY be your hardware
Details please... Information FAQ http://forums.adobe.com/message/4200840

Similar Messages

Premiere Pro Windows crashing after recent updates

Machine specs: HP Z820 - zeon e5-2690 48gb ram quadro k5000. Since the recent updates & complete wipe of the system & fresh install, Premiere pro CC crashes regularly without any pattern. Using MXF files while editing if that helps-i did read a thread about that - but it was old. This is a new problem. The event viewer information:
Faulting application name: Adobe Premiere Pro.exe, version: 8.1.0.81, time stamp: 0x5426694c
Faulting module name: mc_dec_mp2v.dll_unloaded, version: 0.0.0.0, time stamp: 0x53f72b76
Exception code: 0xc0000005
Fault offset: 0x000007feea381a30
Faulting process id: 0x2168
Faulting application start time: 0x01cfe7cdce8c2c97
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: mc_dec_mp2v.dll
Report Id: ba9aeb2b-53c1-11e4-b3dd-24be05e2e6a2
Audition has also started crashing as well. Info:
Faulting application name: Adobe Audition CC.exe, version: 7.1.0.119, time stamp: 0x5421531b
Faulting module name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098826e
Exception code: 0xc0000005
Fault offset: 0x000000000003c780
Faulting process id: 0x249c
Faulting application start time: 0x01cfe7ebfe3ea9e0
Faulting application path: C:\Program Files\Adobe\Adobe Audition CC 2014\Adobe Audition CC.exe
Faulting module path: C:\Windows\system32\MSVCR110.dll
Report Id: 4d975a0f-53e3-11e4-b3dd-24be05e2e6a2
Any Ideas?

Re:
Premiere Pro Windows crashing after recent updates
Try finding MSVCR110.dll file on internet and replace it in the path C:\Windows\system32\MSVCR110.dll
hopefully it works...

CS6 Premiere Pro Windows Capture Format

Can Premiere Pro CS6 for Windows be set to capture Quicktime instead of AVI?

But that's actually a good thing. AVI is the better container, and doesn't suffer from the flaws that QuickTime has.

Premiere Pro (Windows 8) Quicktime Export Errors

I'm trying to export Quicktime h264 files from Premiere to deliver to TV Stations. Everytime I try I get an "Error encoding movie" message and a crash. I know QT has trouble w/multiprocessing and I've tried the msconfig fix mention here : http://helpx.adobe.com/premiere-pro/kb/error-compiling-movie-warning-or.html
This only works once in a while, but I constantly get this error. Is there a fix or workaround out there that will save me from this?

I have NOT used either, but many say to try these for SD capture http://windv.mourek.cz/ or http://www.exsate.com/products/dvcapture/
I have NOT used it, but many say to try this for HDV capture http://strony.aster.pl/paviko/hdvsplit.htm
http://helpx.adobe.com/premiere-pro/kb/cant-capture-dv-hdv-video.html -and http://forums.adobe.com/message/4708997 for general information

I lost my Effect Controls on the top left of my Premiere Pro window.

All i did was pressing X, and then it happened. No clue how to get it back. Plz help.

If shift+F5 does not cut it:
Windows/workspace/reset current workspace.

Super annoying bug: Premiere Pro CC (and probably older versions) encoding/exporting window keeps stealing focus while working

This is something that has caused me to lose a lot of hair due to pulling it:
1. Open Premiere Pro on Windows (8.1, but that hardly matters, I think).
2. Open some video.
3. Export (encode) it to the desktop. The encoding/exporting child-window starts showing the progress bar as it works.
4. Click the bottom-right corner of the screen to show your desktop.
5. Now open any folder on the desktop, such as a dir called "test".
6. Does the Explorer window showing the "test" dir open, as expected? Nope! Instead, Premiere Pro goes: "HEY! What's up?! I'm gonna push myself in front of everything and show you this export/encoding child window as well as the main Premiere Pro window in front of everything! What do you think about that? Heh-heh! Whatever you tried to open is now in the background and I'm in the foreground!"
For the entire remainder of the encoding/exporting process, which can sometimes take hours, I am therefore crippled and cannot do any real work on my computer because Premiere Pro insists on force-showing itself against my will whenever I try to do anything else. This makes working with the computer while Premiere Pro is working (when I can't use the program anyway!) impossible. I'm left to Alt-tabbing around applications if I want to be able to do anything at all.
Without a doubt, I'm not the first person to be annoyed by this. In fact, I'm 99.99% sure that Adobe is well aware of this. Still, I have to make an attempt at reporting this, because it's crippled me every day for the last few years and made me really, really angry. I primarily associate Premiere Pro with frustration and anger at this point. I really hope there is a hidden preference to turn this madness off or something.
I predict that somebody will be tempted to respond with something along the lines of: "Use the Media Encoder!". Well, I don't like the Media Encoder. I want nothing to do with the Media Encoder. I just wanna use Premiere Pro and not have it steal focus against my explicit wishes.
Please tell me this is possible somehow. And please don't tell me to report this to Adobe with some form. I'm reporting it here and now, thanks. Plus, once again, I'm sure they know about this already. (If they don't, they aren't using their own software.)

I only asked two questions of you!!!
Both of them intended to get to a solution for you from understanding your workflow... .
Sheesh.
Don't understand why you put up with something that's made you go crazy"for years" and yet never mentioned by anyone else!
He's doing a Direct Export, not going through AME. That calls up a small dialog showing the progress of the export. Kind of like when you render.
I still don't know how that is done or how one even accesses a "direct export" option/menu.

Adobe Media Encoder pausing rendering while working in Premiere Pro

Hello everyone,
So I am redering a video in Adobe Media Encoder and at the same time I am editing a new one in Premiere Pro.
I noticed that AME is constantly pausing the rendering and did not know why. It turns out that while I'm editing a video in Premiere Pro, I am constantly pressing the space bar to start/pause the video I'm editing. While I do that, AME keeps pausing/unpausing the rendering. Somehow, pressing the space bar in PP has an effect in AME.
I have no clue why it does that because the Premiere Pro window has the focus, not the AME one.
Has anyone ever seen that?
I use Windows 8 and Adobe CC.

Hi Rallymax,
Yes I do queue footage by having an Autowatch set up on the directories where the video is written to. I rarely do a direct export unless testing new settings.
Don't take this as gospel but I too had a feeling that GPU acceleration didn't happen with AME, only direct export. Not sure where that came from, I did watch some of the recent Adobe TV Web Seminar's about new features of CC products etc, so maybe on one of those?
I found this while trying to find out where I had seen it but it is from AMD site not Adobe so whether it's fully 100% correct I dunno:
Adobe Media Encoder
The Adobe Media Encoder (AME), with support for OpenCL™ and GPU acceleration, automates the production of multiple encoded versions of source files, sequences, and compositions in Premiere Pro CC. With the GPU-accelerated AME and AMD graphics technology, editors can quickly encode projects and output files for virtually any destination. AMD GPUs handle the heavy lifting, freeing the system’s CPU to perform other functions.
I will try the same test as Jason, if I can find any AVHCD video and see what the results are. Will be interesting.

Premiere Pro / Media Encoder crash during encoding

Afternoon guys, wonder if anyone has any tips on how to solve my issue. It's a new pc that I'm working on, my first project on it, everything working great in terms of the edit, but crashing whilst encoding both through Premiere Pro and Media Encoder with an error message (below). I'm not great with this stuff so please let me know if I need to provide more info and I'll provide much information as I can.
I'm a creative cloud user.
-Premiere Pro cs 6 (6.0.3) - I have tried to re-install the software, and ran all the updates yesterday after the install. Problem still persists.
-Encoder cs6 (6.0.3.1)
-Windows 7 Professional service pack 1, 64bit. Whilst I was online re-installing Premiere Pro windows did some updates (I generally keep my editing pc's offline).
-DSLR footage (.mov) for video, up to 3 sources of video (nested for multicam shoot) and running one source of audio (mp3 file). Two of the timelines I'm trying to encode are about 45 minutes long.. I have succesfully encoded other clips (a 5 minute, and a 35 minute previously. Miraculously this morning I encoded a 1h12m clip using the mpeg2-dvd preset with only adjustment of quality bumped from 4 to 5). So this was encoded after all the updates, however since then everything else is not working.
-Initially encoder was either freezing, or giving me an error message. Since re-installing all the software yesterday it now does not freeze, but I get the error message: "Adobe Media Encoder CS6.0 has stopped working... A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." I get the same message when encoding with both AME and Premiere Pro. I click "close" from here and nothing else happens.
-Trying to export to mpeg2-dvd, I have tried the PAL widescreen preset, as well as trying to adjust the settings, doesn't seem to make a difference, the error message pops up different points during encoding.
-The only plugin I have used is magic bullet looks for some grading. It also fails to encode with no plugins used.
-PC     - Intel i7-3770 @ 3.40ghz,
          - 32GB ram
          - Operating system and Adobe Suite on c: (SSD 240gb)
          - Project source footage (video, audio, etc) f: (2tb)
          - Encoding files to e: (SSD 240gb)
          - my case is an Antec 902, with no additional fans. It does sound like it's working harder during encoding, not sure if a heat issue could be causing the software to error?
-I am using the mercury playback engine with a Gefore gtx 680 (2gb).
I have not been able to find any definitive answeres with regard to the crashes. I did also have encoder hanging whilst reading the xmp file. I have tried encoding video only (audio disabled) and whilst it doesn't hang during reading of xmp file, it still stops working with the above error message.
I also run an older PC with i920, 24gig, gtx570 and it never crashes but performs much slower. It is also running windows 7, same setup but different hardware. Not sure if the hardware on my new pc could be causing the issues, if you you guys have any troubleshooting tips it would be much appreciated. At this point i have tried starting a new project, new timelines, nothing seems to work, so I have transferred the data to my old pc for encoding (as I need to deliver the discs to a client), but I need to get this new setup working properly.
Cheers,
Stevan

Hi Axel,
Thanks for your suggestions, I just tried cleaning out the media cache and also rendered out a wav file of the audio and placed it in the timeline and deleted the mp3 version.. Tried once again to encode an mpeg2-dvd file.
1st attempt encoding through Media Encoder, pal widescreen with variable bit rate set to 6, 7 and 8 = everything froze, had to restart via button.
2nd attempt encoding through Media Encoder = this time tried video only same settings just no audio = same error (Adobe Media Encoder cs6.0 has stopped working...)
3rd attempt encoding through Premiere Pro, same settings with audio = same error message.
4th attempt encoding through Media Encoder, pal wide preset as standard with no change = same error message.
5th attempt encoding through Media Encoder, h264 preset for vimeo, 720p = same error message.
6th attempt encoding through Media Encoder, AVI (Uncompressed) 720 x 480 preset. 1m40s in the dreaded blue screen appeared. "A problem has been detected and windows has been shut down to prevent damage to your computer. A clock interrupt was not received on a secondary processor within the allocated time interval. " Bla bla bla.
In all instances the encoding is absolutely flying, but always ends up crashing.

Why is Premiere Pro CS5 slower on my system than Premiere Pro CS 4?

I just upgraded from Production Premium CS4 to Production Premium CS5. Have Windows 7, 64 bit OS, 9 GB ram,
Intel I-7 quad 2.67 processors (over clocked to 2.90 ghz) with hyperthreading. I have nothing of any real substance
operating on my system besides Adobe. I have just loaded in a ton of DVC PRO HD 60 footage and am editing a 30 minute
program. Once I am in Adobe Premiere Pro CS 5, it works fairly well, everything works well real time. However, the moment
I click outside of Premiere Pro like to my desktop, then try to click back into Premier Pro, my screen goes white, Premiere Pro says
"not responding" in the title bar and everything freezes for about a solid minute. CS 4 did not do this at all. Anyone know what is happening?
Tks. eddiem

Thank you Harm for the info so far. I appreciate it. Seeing that this is an issue, let me give you a little more data than I might normally do in the hopes of helping to resolve this issue and possibly, you will be able to distill from this something of use for all of us.
I tried out what you said to do, clicking in the timeline first or even while the blue wheel is in motion, but it makes very little difference. Let me give you a little more info. As an attempt to have resolved this which I have not, I am essentially working offline and the problem still persists. I have internet connection disabled, I have all anti-virus and firewalls turned off, I have gone through the task manager and have ended every single process not essential to running Premiere Pro CS5.
All it takes is for me to click on the desktop with nothing open and then click back to the Premiere Pro CS5 window whether it be in the timeline or anywhere and I get the blue circle going. When I do what you say, even while the blue wheel is going, and I try to click on the timeline, the premiere pro window goes white with the blue wheel still going and locks up for at least a minute.
Some other outpoints that may be related to the same issue:
Additionally, when using the media browser and I double click on the P2 media thumbnails to bring the media to the source window, I get a long delay
to load the footage. Usually about 10-15 seconds for EACH piece just to view it. Needless to say, this makes editing essentially impossible. I have also tried settings on the memory preferences section changing between "performance" and "memory" not really knowing if that would have anything to do with it, but it didn't.
Another mysterious thing is that my editing tools window never shows up even, even when I reset the editing workspace (window-workspace-reset current workspace (with "editing" bulleted). I have to manually open up the window and then drag and drop it back to its normal place each time.
Needless to say this is making the experience terrible.
I checked my loaded and running programs to further resolve this to make sure I did not have some unknown system drain, and happened to see I still had the old Production Premium CS 3 installed but not running, so I uninstalled that and it made no difference. It hadn't been running anyway.
What is frustrating, Harm, is that my Premiere Pro CS4 was running great. When I started working with P2 media on CS 4 on the same system, I had noticed a similar lag in loading P2 media which I thought was odd, but I NEVER had the delay and blue wheel and white screen clicking from one application to another. The only time on CS4 I even experience a slow was when I had PPro4, AE4, AME4 and Encore 4 all opened at the same time!
Funny thing though, when I have Premiere Pro CS5 and AE CS 5 opened, AE runs fine, but Premiere seems to be hog and is just slow. I never have a problem going in and out of the other Production Premium applications.
I am using an Asus computer, with Intel Core i7 processor 920 @ 2.67ghz. I have standard overclocking software, and when I overclocked my processor to run as an i7-940-2.93 ghz, that lag on the loading the P2 media into the source window went away on CS4.
However, since being on CS5 it now does the same thing.
It is so bad that I thought I okay I will go back to CS 4. However, now when I try to use CS 4, it is doing the same thing, yet this did not do that before installation of CS5!
Let me give you just one more bit of data in the hopes that it may help in resolving this. The way I installed Production Premium CS 5 was first via
the trial software. While that was downloading, I purchased the software and I installed the serial number at the time of installation. The reason I mention this is that before I purchased it, I was interested in seeing if CS5 would handle a codec problem I was experiencing going from premiere pro to encore DVD ( this will be the subject of another thread) and I was assured by the salesman it would (it didn't) and that the trial software is fully functional!
Well, that is untrue, and the salesmen and the sales supervisors (spoke to them all) are very seriously misinformed. The Trial version is NOT fully functional, however, you do not find out about it until you actually get the download page and then it clearly says in small print that encore and various HD codecs are not operational as well as some AE aspects on the trial version.
The reason I tell you this is that I don't know if installing via the trial software version makes any difference in how it sets up.
The significance of this is that I was told that Premiere Pro, After Effects and Encore build upon CS4 and you cannot uninstall CS 4 before loading the upgrade to CS5 nor should you uninstall it afterwards.
So this now possibly explains why the previous CS 4 I have on the system is also now responding just like CS5. (I don't know if it makes any difference, but CS5 installed Premiere Pro, After Effects and Encore in the C:\Window\Programs folder yet all other components are installed in the C:\Windows\Programs(86) folder. (My dynamic links work fine (so far) between Premiere and AE and Encore)
Okay, Harm, sorry I wrote so much but possibly this will help, and I hope there is something I can do immediately to resolve these serious delay (lag) issues.
PS: I have three internal hard drives. CS5 is installed on the C drive same as my OS and all my footage and premiere pro pjts are saved onto a different drive. Everything is 7200 rpm, 1TB, Sata 3Gb/s.. Except the internal drive where the PrPro Pjts and footage are stored is 2TB , 7200 RPM and 6Gb/s.

Adobe Premiere Pro CS6 crashes with not finding a capable play module on a windows desktop with a AMD Radeon R9 200 series board.

I installed Premiere Pro CS 6.0 on a brand new system.
Win 8.1,
i7 3.4 GHz on an Asus Sabertooth
16 Gig memory
AMD Radeon R9 290 Graphics Board with the latest drivers and Bios.
On starting Premiere I get the (as I noticed quite frequent appearing) error message that Premiere cannot find a capable play module and the suggestion to update my video drivers.
I tried everything I found in this forum or on the web:
Installed the latest drivers
Run the program as an administrator
Updated the Graphics board Bios
Updated Premiere CS6
Started Gpusniffer in CMD-mode to find out what board it found and added that to the cuda_supported_cards.txt in the Premiere directory.
All to no avail. The app will simply not start.
The Gpusniffers report states:
Loadlibrary “n” failed
Loadlibrary “n” failed
--- OpenGL Info ---
Vendor: ATI Technologies Inc.
Renderer: AMD Radeon R9 200 series
OpenGL Version: 4.4.13084 Compatability Profile Context 14.301.1001.0
GLSL Version 4.40
Monitors: 1
Monitor 0 properties –
Size: <0, 0, 1920 1080>
Mex texture size: 16384
Support non-power of two: 1
Shaders 444 :1
Shaders 422: 1
Shaders 420: 1
--- GPU Information Info –
Did not find any devices that support GPU computation.
As I invested a lot in the CS6 Master Collection I am not considering an update tot the CC version, also because the same problem occurs in that version too.
I would be much obliged if someone has an answer that truly will work. This problem costed me the best part of two days’ work and fouled up my workflow considerably.

==========
I tried to go into display settings and disable the Intel card. (this caused low resolution which is unexceptable)
==========
This makes me think it's using that graphics "card" ( probably built into mobo ? ...called 'onboard graphics ? )
This stuff gets tricky and sometimes the only way to make windows 'recognize' the pci graphics card is to actually take it out and boot, and then put it back in...
Then you get mssg " windows detected new hardware" and you install the drivers...
usually bios gives you choice of using onboard graphics or not ( but this too is wanky sometimes...sorry to say ...)
I recently ( this past year ) had a similar sort of situation but have a desktop, where its easy for me to take off side panel and pull the pci-e graphics card and boot, and get that horrible low res default screen...turn off, install card, reboot etc...
but anyway, it sounds to me like you're notebook is using that mobile graphics driver stuff and not the radeon. Somehow you've got to make it switch to that graphics card is maybe your solution.
sorry I dont have notebook but maybe someone else here does and can help more...
good luck.
ps..its always a weird fact of life...when things aren't working 'right' something has to get done fast....
edit:
I dont know how much you know about windows stuff, but after you disable that intel thing and get your low res screen.. you DID try to update the driver for that card using 'my computer / device manager ' right ??

Premiere Pro CS4 "Export Settings" window does not show up.

Hello,
I've run into a new problem with Premiere Pro CS4. Basically, when I select "File > Export > Media" my Export Settings window doesn't show up. If I click on the Premiere window I hear the beeping sound and nothing happens, if I hit Enter the Export Data window pops up and then Media Encoder opens. So, it seems that my Export Settings window is still open but I can't see it and make the necessary setting changes. It does not appear to be minimized and I can not locate it on my desktop anywhere. This is really frustrating because I was able to see the Export Settings window just a few weeks ago when I was exporting my last project. I've tried changing my screen resolutions but that didnt reveal the Export Settings window.
Does anyone know what is going on here and, more importantly, how I can fix it? I am really stuck here and am working against a deadline. Any and all help is greatly appreciated!
-Ben

Ben,
THANK YOU!!!! For two days I have been struggling with the exact same issue. And of course it was simple to fix, if I had just thought about it. Thank you for taking the time to post your experience. I had tried all sorts of stuff trying to get everything onto my #1 monitor, with desktop & workspace resets, resizing my display, etc. After reading and printing your post,
Hitting ALT+Space,
Down Arrow,
Enter,
and then pressing the left arrow and watching my Export window slide into view, I was laughing so hard, that I was tearing up. It would have been a month waiting for my second monitor to get repaired to get to see what was still being displayed on this ghost monitor. Each week, I video and edit our church's service and then post three versions (Windows Media Player, Ipod-MP4, MP3 Audio) of it to our web site. I would have been four weeks behind were it not for your post.
Again, a BIG Thank You!!!
Tony Salso
[email protected]
Cedar City, UT 84720
Tony—Professional Digital Pictures
--Videographer and Webmaster
Red Hills Southern Baptist Church
Serving Jesus in Southern Utah
[email protected]
www.redhillssbc.org

After Effects CS5.5 will not open a Dynamically Linked Premiere Pro sequence in the comp. window

Hi all,
I'm trying to export a Premiere Pro sequence which is in 2K and the footage has been shot as RED 5K. Adobe Media Encoder will simply not work as I am having the quite widely discussed issue where it will just 'hang' at certain points and not complete the export.
The most popular solution to this problem is to export via the Render Queue in After Effects instead. However, therein lies the problem.
I go onto After Effects. Choose File -> Dynamic Link -> Import Premiere Pro Sequence.
The box pops up, I choose the Premiere Pro Project File then select the sequence I want to export. It then appears in the After Effects project panel window like so:
However - when I try and drag this to a new composition window, one of two things have happened. Either A) nothing happens (literally, NOTHING changes) or B) as the following example shows, it seems to add it to a new composition, but the video is entirely black. I have tried rendering it and it just produces a black video.
The other thing people seem to suggest is to just import the entire Premiere Pro sequence into After Effects. I've tried this, but any titles I have added in PP force the video to fade out then back in, in the place where the title should be?? So I can't export the video this way either.
My system is as follows:
Thanks massively in advance for any help that is provided!

This is months old but I'm now having the same problem with AE and Premiere CS6 after updating last night: Dynamic linked sequence shows up in the project window in AE and even plays video if previewed, but will not drag or alt-drag into any comps, including a new comp (makes a new comp with matching settings, but empty).
Furthermore, I do actually have an earlier version of the same sequence placed in one of my AE comps, which I think was done using the same steps just prior to updating the apps last night. Did this break?
I'm a little concerned since the biggest reason I'm trying to use premiere is to eliminate the exports when adding graphics in AE.

Premiere Pro CS3 (Version 3.0) will not start following upgrade to Windows 8-- rest of CS3 is fine

Recently upgraded from Windows 7 Ultimate to Windows 8 Pro;
next time I tried to open Premiere Pro 3.0 (Adobe Master Collection CS3), splash screen scrolled normally through files being loaded until "SolidComposite.AEX", where it white-screened & crashed.
Tried removing that file, it crashed on the next ".AEX" file; removed all ".AEX" files, it began crashing on ".dll" files;
kept removing THEM, just for the heck of it, until the software loader couldn't even start.
I popped in the CS3 disc to repair the installation-- on the entire suite, for good measure;
re-booted & started Premiere-- crashed at the exact same point.
Uninstalled and then re-installed Premiere-- the entire suite in fact, since there are so many common processes;
couple of hours later, re-booted & started Premiere-- same exact thing at the same exact point.
I found this same problem in at least a half-dozen threads, going back to '07--
and several of them even mentioned the same exact file as the trigger for the crash!
Unfortunately, not one of those threads has ever ended with an accurate diagnosis of the problem,
nor a solution more insightful than reinstalling both the CS & the OS.
I don't want to abandon Windows 8...
but on the other hand, I just can't afford to pony up another grand to upgrade the CS Suite again, either...
Besides: CS3 is everything I need, and it has worked wo well for so long--
even now, Premiere Pro is the only software in the suite with a problem!!
(I used Photoshop to create the above screencap)
So I'm hoping against hope that one of you techno-gurus may have come across this ITRW--
and actually SOLVED IT!!

Thanks for your prompt reply, John-- and for NOT simply advising me to spend my kid's tuition on more of your company's products...
Actually, I had tried the "Run as Administrator" option already, having found it in one of those other threads;
there was no change in the sequence described above.
I decided to try another possible solution which I read about in one of those other threads: opening Premiere from a different account.
Incredibly, it WORKED-- sort of...
I got a couple of popups advising me that missing codecs had to be installed-- and upon completion, Premiere opened!
Here's an interesting note: the last file to load was still "SolidComposite.AEX"-- and the "White Screen" I kept seeing was Premiere opening normally. The next thing that displayed was the normal dialog box "Open/New Project"-- I entered a new project name, and Premiere started normally. I even added a few video files as a test... all opened normally.
I returned to the Admin account to see if the fix was in here, too;
but clearly the war wasn't over, over here...
It now appears that some personal setting in the Admin account is causing Premiere to close itself;
I've been reading about the layered security measures embedded into Windows 8-- I'm suspecting the conflict lies there...
I ran the Windows Troubleshooter & got this:
both MS & Adobe confirm that CS3 is fully compatible--here's my sytem info:
Since I seem to have established a fall-back position that lets me use Premiere, my crisis becomes a mere conundrum;
but I know this is gonna gnaw at me anyway, & I'm hoping that this new information might suggest further troubleshooting options to someone who understands the Adobe software and/or the Windows software better than I do!
Speaking as someone who has found many solutions on forums like this over the years, I assure you:
for every person whose post you reply to, there are many more whom you will never know you have helped!!!

Is it possible to show the sequence name in Premiere Pro's window titlebar?

Currently the Premiere Pro titlebar displays "Adobe Premiere Pro" and the project file (ie. D:\Videos\2014-04-30 - PPK\_Project Files\PPK.prproj)
I was wondering if anybody knows a way to also display the name of the current sequence you're editing?
I use time tracking software to monitor my Premiere editing times and uses the tilebar name... so if the Premiere titlebar included the sequence name, I would know how long I spent editing a specific sequence in that project.
I'm using Windows 8.1
-Pete

This is not possible.

Will Adobe Premiere Pro 2.0 run on a 64 bit (Vista, Windows 7) OS?

I have been using my Premiere Pro 2.0 application on a Wndows XP machine for the past couple of years. It's time to upgrade may computer and enjoy the increased power and speed that should come with it. All that is available nowadays are Vista or, more commonly, Windows 7 operating systems. In order to get RAM above 3 GB, I have to get a 64 bit system. Will I have problems running my older Premiere program on these systems?

Problems = Likely
Possible Solution for Win7 Pro = http://www.microsoft.com/windows/virtual-pc/
Also...
Win7 Help http://social.technet.microsoft.com/Forums/en-US/category/w7itpro/
Compatibility http://www.microsoft.com/windows/compatibility/windows-7/en-us/Default.aspx
Adobe Notes http://kb2.adobe.com/cps/508/cpsid_50853.html#tech
Optimizing http://www.blackviper.com/Windows_7/servicecfg.htm

Premiere Pro & Windows 8

Similar Messages

Maybe you are looking for