What it means iwl3945: Could not read microcode: -2 ?

My iwl3945 module work fine ( intel pro/wireless 3945abg ).
I put it in /etc/rc.conf
1)
MODULES=( ... iwl3945 ...)
2)
wlan0="dhcp"
INTERFACES=(lo wlan0 ...)
and in /etc/conf.d/wireless
1)
wlan_wlan0="wlan0 mode managed essid MariaTeresa channel 7 ap 00:17:3f:0d:81:20 key restricted [1] 1a3d9d0d8c27819e7c23103ea$
WLAN_INTERFACES=(wlan0)
So I have ( as root ) type:
modprobe -r iwl3945
modprobe iwl3945
restart network daemon ( /etc/rc.d/network restart )
because the module is not detected in boot.
After the procedure above thats ok.
The dmesg is
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.0ds
iwl3945: Copyright(c) 2003-2007 Intel Corporation
iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2
iwl3945: Could not read microcode: -2
ACPI: PCI interrupt for device 0000:07:00.0 disabled
iwl3945: probe of 0000:07:00.0 failed with error -2
With old kernel all was perfect. But with last kernel ( clean install from ftp ) not work.
Thank you!

Delete the 3945 ucodes in /lib/firmware/. Remove the iwlwifi-3945-ucode package (pacman -R iwlwifi-3945-ucode) en reinstall the package. I think that should fix your problem...

Similar Messages

  • What this mean? "could not rasterize because the pixel data for this layer is not"

    I've taken a color picture and made it black and white by doing the following: Layer>New Adjustment Layer>Hue/Saturation. I brought the saturation down to -100.  The pencil is selected and my foreground color is black.
    When I try to select the flowers in my picture to bring out their color (within the black and white image), I get a circle with a black line thru it and the error message "could not rasterize because the pixel data for this layer is not directly editable".  The steps I followed are working for most of my team but some of us are getting this error message.
    Any idea why and/or how to fix it?

    Ah, thank you!  I didn't have the mask selected. So once I did select it, the color came thru like magic. 

  • Hello,this error comes up all the time:Could not read chrome manifest file 'C:\Program Files\Mozilla Firefox\extensions\{972ce4c6-7e08-4474-a285-3208198ce6fd}\chrome.manifest'. What does it mean? and how can I fix it?

    Could not read chrome manifest file 'C:\Program Files\Mozilla Firefox\extensions\{972ce4c6-7e08-4474-a285-3208198ce6fd}\chrome.manifest'.
    This is pretty much it, It was in my error console and its there
    every time I check on my errors

    I used the 64bit win7,when I start firefox it will be no response just in one
    minute ,the console show me this error ：Could not read chrome manifest file 'C:\Program Files\Mozilla Firefox\extensions\{972ce4c6-7e08-4474-a285-3208198ce6fd}\chrome.manifest！

  • ERROR:Could not read archive file - during Processing Base System Part 2

    Hi there,
    What I have:
    * I have problem with installation of the Mac OS X Panther v10.3 on iMac.
    * I have 3 original CDs (black with silver X).
    What I did:
    * I made new 1 partition and formated disk as Mac OS Extended (Journaled) over the Disk Utility in the first CD as normal without additional options (if I tried to format disk with zero all data and 8 way random write format after 3 days computer freeze)
    * I verified disk over this utility - that was ok - HFS volume verifed.
    * Then I restarted the computer and ran installation from this first CD
    What happened:
    * installation did not finish, because there were some problems during installation process.
    * i tried to customize installation just for essential work (without other languages support, printers etc), but it was still the same problem
    Installation log:
    After I choosed installation type, there was first error, but it did not look like important.. - root: bootstraplookup(): unknown error code
    Checking your installation disk - OK
    Preparing disk - OK
    Preparing base 1 and 2 - OK
    Other preparing.. - OK
    Processing Base System Part 1 - OK
    Processing Base System Part 2
    ==
    ERROR:Could not read archive file. - pax: Invalid header, starting valid header search.
    ERROR:Could not read archive file. - pax: Invalid header, starting valid header search.
    last message repeated 2 times
    ERROR:Could not write file. - pax: WARNING! These patterns were not matched:
    Some files for Essentials may not have been writen correctly.
    root: Installer[108] Exception raised during posting of notification. Ignored. exception: Some files for Essentials may not have been written correctly. (code 1)
    Install Failed
    Error detected
    Name: NSGenericException
    Reason: Some files for Essentials may not nave been written correctly. (code 1)
    ==
    It seems like a problem with reading some data from the CD, but during the installation checking of disk was ok.. maybe it can be problem with the cd-rom..? Or problem with data on cd-rom - I mean bad archive file..? But it is original CD.. What do you think??
    Thank you!

    Tomas,
    On THIS Page, locate your iMac model.
    From the Documents column, click on the appropriate number link.
    Using the info in the document that opens, locate the serial number of your iMac.
    On THIS Page, in the text field for Search Tech Specs, enter that serial number.
    Click on the model of iMac that appears.
    Post a link to the page that opens, or post the info requested below.
    Exactly which model iMac is it?
    What is the Processor speed?
    What size is the Hard Drive?
    How much Memory is installed?
    What type of internal Optical Drive does it have?
    Which version of OS, was the original Installed Software?
    ali b

  • Could not read from the source. Please check if it has moved or been deleted

    hi all,
    when i try to render a afx project from media encoder i get the following message
    "Could not read from the source. Please check if it has moved or been deleted"
    i've read on the forum that this is due to an old installation of Premiere.
    I'm using a brand new computer. the only software installed is my cs5 master collection and the updates from adobe website.
    win7 pro
    i7
    16 gig ram
    cheers
    s

    Hello, this is terrible problem, which i found in CS 6 softwares ...
    solution i found only working, is uninstall and reinstall full package.. but it is not all,
    you need to do BRAND NEW admin account in windows, and install it there.
    that means, i could not export after repair from encoder in my original account never more (!!)   .. this is really terrible way how to repair this issue, because :
    1.by reinstalling of software, client WASTE HIS TIME
    2.by necessity to begin work in another windows profile you again WASTE YOUR TIME because of learning and migrating all other profile modifications, which i see really unaccpetable. Adobe means, this solution of repair is ok, and they did not do till today any steps of creating some "clever" solution.
    I ask everybody, who will meet this issue in future, guys, please, complain about this situation, give "BUG Report" to them, and write "feature request" to them , in the way of creating some repair tool, which check actual  "broken" connections between encoder and premiere, which refuses to "take material" from it and encode, and REPAIR it automatically..  
       I am not IT, but ..does it seems so hard to create this ? Adobe IT developers should know their systems, and should create such utility tool really easy.
    Steps to reproduce bug:
    1. i export anything by button "queue" from premiere to Encoder
    2. Encoder will start encoding
    3. Encoder does not show the window of media encoding (down left )
    Results: sound of sheep occur,
    in encoding error file is this reason of canceling the encoding :
    01/02/2014 10:10:48 AM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    History of this problem and detailed description, HOW i did "repair" this. With wasting of app 2,5 days of my working time :
    1. after repairing "error 5" problem , i solved it by reinstalling the suite from the new admin user profile (profile B) . 
    I continued my work on my normal working windows profile . (profile A)
    Every cooperation (AE+Pr, export media via "queue" to Encoder) was working fine . . .
    2. suddenly it stop working (without knowing any possible reason - i did not do installations )
    and showed in error export log file :
    "Could not read from the source. Please check if it has moved or been deleted."
    3.repair via procedure(procedure "a"):
    i did this procedure on the profile B (profile from last time installation of repairing problem error 5)
    I did these steps :
    a-uninstall master coll suite
    b-i used Adobe cleaner tool (remove ALL)
    c-removed raw directories in locations
    •C:\Program Files\Adobe
    •C:\Program Files(x86)\Adobe
    •C:\Program Files\Common Files\Adobe
    •C:\Program Files(x86)\Common Files\Adobe
    •C:\ProgramData\Adobe
    d-removed these links from registry file
    •HKEY_LOCAL_MACHINE\SOFTWARE\Adobe
    •HKEY_CURRENT_USER\Software\Adobe
    •HKEY_LOCAL_MACH INE\SOFTWARE\Wow6432Node\Adobe
    •HKEY_CURRENT_USER \Software\Wow6432Node\Adobe
    e-restarted the PC
    f- newly installed the Master Coll CS6
    g-update the software
    result of repair of "3" : problem still exists
    4.Ok i find out after coordination with support, it should have been created  ANOTHER NEW admin account.
    4a:so i did the same procedure (uninstalling) in profile B
    4b: and then i created brand new admin profile (profile C)for INSTALLATION of software
    4c: restarted the pc (and did not updated it yet)
    result :
    ==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile C) : export WORKS
    ==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile B) : export WORKS
    ==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile A) : export DOES NOT WORK ! ! !
    (in profile A, is possible to export some raw video material in encoder which is imported to it via "drag and drop)
    problem i see:, i have my basic profile A, which i am interested to work, because of all my directory modifications are in there..
    this issue should be some "broken" connections between encoder and premiere, which refuses to "take material" from it and encode.
    what i expect :
    to get from Adobe some repair tool, which automatically checks these connections and repair if necessary, without necessity of founding the new profile and reinstallation of whole software.. this is madness !
    what i do NOT expect from Adobe:
    to get from Adobe advice of kind : you have to reinstall full software in new admin profile. sorry , we do not know the solution, because we do not know, how do behave our software.

  • Could not read ruv entry

    Can anyone explain what exactly below WARNING message means.
    +[01/May/2009:12:56:47 +1200] - WARNING<20515> - Backend Database - conn=-1 op=-1 msgId=-1 - could not read ruv entry, this ldif should not be used to initialize replicas+
    I see above warning is logged to error log everytime I execute "dsconf export" command in a standalone directory server 6.3.1 instance (not in a replicated environment).

    Yes, it is.
    all-ids-threshold : inherited (4000)
    compressed-entries : overflow
    compression-mode : none
    db-name : usergroupdb2
    db-path : /opt/SUNWdsee/dsinst-mldap1/db/usergroupdb2
    enabled : on
    entry-cache-count : unlimited
    entry-cache-size : 100M
    entry-count : 43452
    index-filter-analyzer-enabled : off
    index-filter-analyzer-max-entries : 2000
    moddn-enabled : inherited (off)
    parent-suffix-dn : undefined
    referral-mode : disabled
    referral-url : ldap://mldap2:389/o%3Dusergroup
    repl-accept-client-update-enabled : on
    repl-cl-max-age : 1w
    repl-cl-max-entry-count : 0
    repl-id : 10
    repl-manager-bind-dn : cn=replication manager,cn=replication,cn=config
    repl-purge-delay : 1w
    repl-rewrite-referrals-enabled : off
    repl-role : master
    require-index-enabled : off

  • I ran a virus/trojan fix and this is what it said it could not repair something in the main library core or something like that.  What do I do?  The problem seems to be with safari?

    I ran a virus/trojan fix and this is what it said it could not repair something in the main library core or something like that.  What do I do?  The problem seems to be with safari?

    I ran the utility disk and this is what it said.
    Warning permission differ Applications/Safari drwxr-xrx they are -rwxr-xr system/livrary Cores has been modified and will not be repaired.
    Permission apllication differ on System/livrary/Pr or could be -rw-r--r-- they are rwxr-xr-x Application/iTune be droxr-xr-x they are rwxr-xr-x
    Then I hit fix permissions and it said this
    Warning SUID file Systm/Library/Core has been modified will not be repaired
    I also downloaded Bitdefender Virus Scanner and it found nothing.

  • VSTS loadtest error while running Loadtest with Runsettings as No of test iterations , ERROR is : could not read result repository: unknown transaction id in results:

    Subject: VSTS loadtest error while running Loadtest with Runsettings as  No of test iterations ,  ERROR is :  could not read result repository: unknown transaction
    id in results:
    Hello All,
    I am facing the following error while running a loadtest (when i choose the scenario to be executed for No of test iterations). But the same loadtest with the Run duration for X minutes is running fine without any issues. 
    Any suggestions on the issue i am facing
    error is :
    could not read result repository: unknown transaction id in results:
    or
    could not read result repository: unknown request id in results: 
    Thanks
    Satish

    Hi Kotapati,
    >>Subject: VSTS loadtest error while running Loadtest with Runsettings as  No of test iterations ,  ERROR is :  could not read result repository: unknown transaction
    id in results:
    According to your description, you mean that when you run your load test using the Test Iterations way and then get the error message, am I right?
    If yes, please you try to close the VS, and then open this VS again. Then clean your load test project/solution and then re-build it, run your load test again check this issue again.
    In addition, I suggest you could try to create a new load test and then run it using Test Iterations way check if you get the issue for the specified load test or all load tests.
    If possible, I suggest you could share me simple load test for us so that we will further help you.
    You could upload your load test to OneDrive and then copy link here.
    Best Regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Media Encoder crash in CS6. Could not read from the source. Check if it has moved or been deleted.

    I'm having a problem getting Media Encoder to get past the dynamic link portion of encoding a time line sequence.
    I can send it over to Media Encoder, but it crashes consistently after the yellow bar saying something about dynamic link.
    I have CS6 installed in my computer here at work, it previously had CS5.5 installed on it.
    I read some answers about CS4 having this problem and tried to create a shortcut and put it in the dynamic link folder, but that didnt work.
    I would hate to have to reinstall the software here at work as the IT department is a pain- but I can't encode video on one of the computers we use here.
    Any ideas on what may be happening and how I can solve the problem?
    Thanks!
    Its a Dell Workstation with Windows 7 Ultimate installed dualE5620 processors at 2.4GHz. .
    only 6 GB RAM, and a RAID 5 hard drive setup with 3- one gb drives giving the C drive space of 1.8Gigs
    Its got an NVIDIA Quadro NVS 420 video card.
    I'm upgrading this computer to better work with editing video, so this is a good time to get this all cleaned up.
    Im adding RAM (24GBs)- replacing the video card to a GTX 780 3GB running 3 monitors.
    I'd also like to either split up the RAID (ugh)..or just add 2 internal SAS HDDs. to split up the video and the cache and the OS/programs as is usually done with editing video.
    Thanks for your help in advance...
    Mike

    ...more information...problem still not solved....
    After searching more in the forums, I tried a couple more things:
    I tried to restart AME and clearing the preferences. This didnt help.
    I also deleted the ...appData/Roaming/Adobe/AdobeMediaEncoder/6.0 folder and all subfolders   No help here either.
    I also tried to import the sequence via AME rather than export via PP. This worked. The sequence loaded immediately and processed perfectly.
    When I export via PP, I hit the queue button, it hangs for about 3 mins, then the yellow bar appears saying "Connecting to Dynamic Link server"
    it then hangs for approx 3 mins again and then I get the Failed alert.
    the error log reports:
    Encoding failed
    Could not read from source. Please check if it has moved or been deleted.
    any help available here????

  • Problem: 'Could not read from source' when exporting project.

    Hi everybody
    I am using Adobe Premiere CS4 on my MacBook Pro 15'' (i5 processor, 4 GB RAM, 500 GB Harddisc, 256 MB video memory (high-clockspeed))
    Everything works well except of one big thing, every time when i try to export my finished project the Media Encoder tells me always the same thing directly after pushing the start button. 'Could not read from the sorce. Please check if it has been removed or deleted'.
    I tried removing any offending plugins, i fixed the disk permissions.. But it all doesnt matter anything.
    No matter what i try to export, no matter in what file format. It just doesnt work. I even tried exporting a project which only contains a video file of 5 seconds without anything more but it just doesnt work. Its impossible that i have touched or modified or replaced any source files...
    Some help would be very very appreciated!!
    Martijn

    Welcome to the forum.
    Perhaps this Adobe KB Article will be able to help you.
    Good luck,
    Hunt

  • "ERROR: Could not read block 64439 of relation 1663/16385/16658: Result too large"

    Hi,
    I've already archived a lot of assets in my final cut server but since one week there is a message appearing when I click on an asset and choose "Archive". The pop-up says: "ERROR: Could not read block 64439 of relation 1663/16385/16658: Result too large"
    Does anyone know what's the problem and/or have any suggestions to solve my problem?! I can't archive anymore since the first appearance of this message.
    What happened before?
    -> I archived some assets via FCS and then transfered the original media to an offline storage media. That system worked fine for the last months and my normal server stays quit small in storage use. But now, after I added some more new productions and let FCS generate the assets, it doesn't work anymore...
    It's not about the file size - I tried even the smallest file I found in some productions.
    It's not a particular production - I tried some different productions.
    It's not about the storage - there's a lot of storage left on my server.
    So, if someone knows how get this server back on the road - let me know.
    THNX!
    Chris

    I would really appreciate some advice re: recent FCS search errors.
    We're having similar issues to C.P.CGN's 2 year old post, it's only developed for us in the last few weeks.
    Our FCS machine is running 10.6.8 mac os and 1.5.2 final cut server with the latest
    OS 10.6.x updates.
    FCS is still usable for 6 of 8 offliners, but on some machines, searching assets presents "ERROR: could not read block 74012 of relation1663/16385/16576: Input/output error."
    Assuming the OS and/or data drives on the FCS machine were failing, I cloned the database drive today and will clone the OS drive tomorrow night, but after searching the forums and seeing similar error messages I'm not so sure.
    FCS has been running fine for last 4 years, minus the recent Java security issues.
    Thanks in advance, any ideas appreciated!
    cheers,
    Aaron Mooney,
    Post Production Supervisor.
    Electric Playground Daily, Reviews On The Run Daily, Greedy Docs.
    epn.tv

  • Premiere Pro CS4 Export fails with Media Encoder CS4 "Encoding Failed"," Could Not Read From Source.

    There has never been a history of Adobe CS3 installation on the brand new MAC Pro I am using prior to installing Master Collection CS4, despite other posts claiming that chief cause of this issue is a previous CS3, Beta or trial installations of previous versions. I simply had a straightforward installation of CS4 and have had trouble since day 1.
    I have uninstalled and reinstalled Master CS4 three times, two times with the action script cleaner for CS4. I tried changing Adobe Cache folder locations to alternative drives. I ran shift start many times to correct any inconsistencies and corrected for permissions using disk utilities repeatedly. All updates have been installed and I am still getting the same error when exporting my timeline to Media Encoder CS4, be it a large High Definition project or a small one consisting of few stills.
    No matter what presets I chose, the job appears as one of the items in the render qeuee of Media Encoder CS4 and sits there with the status WAITING until i hit Start Queue. When I do, it still says WAITING under Status and at the bottom corner of the window it reads : Loading "project name.prproj" and after an average of about 6 minutes, a yellow caution sign appears. No render whatsoever takes place. When I click on the yellow caution sign, it reads a log of all errors in connection with each job, including the ones that have gone before it. Here is one:
    Start of the Error Paste
    - Source File:/users/myname/Library/Caches/TemporaryItems/test.prproj
    - Output File:/ users/my name/Documetns/Adobe/Premiere Pro/4.0/Sequence 01.mov
    - Preset used :NTSC DV
    - Video:
    - Audio:
    - Bitrate:
    0 Encoding Time: 00:33:01
    Sat Mar 21 17:12:25 2009 : Encoding failed
    Could not read from the source. Please check if it has moved or been deleted.
    END OF ERROR Paste
    Please any gurus out there know how to troubleshoot this damn thing on Mac, I really appreciate it. I have not yet encountered any posts of Mac owners with no previous CS3 installation having this issue. I am in the middle of 3 projects with tight deadlines and need your urgent help. THANK YOU!

    Hello There,
    I resolved the issue through a simple process of elimination. So simple in fact I wonder how I missed it. Since there has been no history of prior CS3 installation on this machine and every conceivable trick was applied to resolve the problem (refer to my original post earlier in the thread) ending in frustration, the problem had to reside in a factor or series of factors that were only present in this machine. Of the two remaining causes different in compare to other machines, I had to look into the possibility of any hardware and/or software conflicts. After all, this very same installation works perfectly fine on my colleague's Apple Macbook Pro and several Windows machines.
    It turns out that I had installed Pro Tools on this machine that comes with all kinds of optional plug-ins in the so called ignition pack. One of these optional plug-ins is called IZOTOPE (three varieties include Spectron, Trash and another one that escapes my mind). They were all lite version licenses that would automatically pop up on their own when you would start a program where they had been residing. One such program where an association existed was indeed the Premiere. An annoying dialogue box directing you to buy the full version when you would start the premiere would refuse to go away. Sometimes it would even start on its own culminating in a a permanent dialogue box.
    The cause of the problem was right before my eyes and I had overlooked it. Once uninstalled using IZOTOPE clean uninstaller on step 4, the problem was resolved. Projects are now loading very fast into the AME and encoding begins in earnest. I have never had any issues ever since.
    Long story short, if you have any plug-ins specially the ones that are loading upon the start of any program or the ones that reside inside the premiere or the ones that start on their own independently, they could be one of the highly probable causes of this error. I have seen other similar posts complaining of plug in folders inside premiere that needed to be moved to resolve the issue for instance the ones that needed to be moved to AE folders. If you are a plug-in admirer, I would suggest to look into them seriously.
    On the side note, many combination and causes may lead to the same error. I am not claiming that this is the solution for everyone.
    It must also be noted that I applied the trick of creating a shortcut of Premiere (and naming it exactly as such) and dropped it into the Adobe Dynamic LInk folder (even though this was suggested for windows)and have changed the adobe Cache locations to an alternative folder on a separate drive. I haven't been able to establish conclusively if the latter steps are also essential in fixing the error on MAC but I can confirm that since the latter steps were taken before the uninstalling of Izotope plug-ins and i still had issues, probably uninstalling those plug ins or finding a way to move them to a place where they don't interfere (if you absolutely need to keep them) is the one essential step that solved the problem.
    Hope this helps.

  • "Could not read from source" exporting on Mac with CS4

    I'm using Premiere CS4 on a MacBook Pro, trying to export a film and getting the  "could not read from source" message.  I did not have CS3, and I'm not on a pc, so the Windows KB articles and posts don't apply.  I've read all the posts I can find on the forums but none of these solutions is helping to date.
    Are there any troubleshooting steps someone can recommend to figure out what I need to do here?
    Here's the trace, any assistance is MUCH appreciated!
    - Source File: /Users/johnchmaj/Library/Caches/TemporaryItems/circle _6.prproj
    - Output File: /Users/johnchmaj/Documents/Personal + Projects/Living Universe/Snoqualmie Valley/Valley Breezes Premiere/1circle:introitus/Valley Breezes 6-41.m2v
    - Preset Used: NTSC High Quality
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 30:44:29
    Wed Aug 19 16:52:56 2009 : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.

    I have been having the same issue on my desktop and laptop, although I have Windows XP Professional.  Originally had CS3 and then installed CS4.  The problem was fixed by uninstalling everything Adobe (even Reader), using the wincs3sclean, and reinstalling the CS4 products.  The first time it did't work on my laptop, so I did it a second time and it worked.  I don't have Creative Suite, but this still works.  Here is the link to wincs3clean:
    http://kb2.adobe.com/cps/401/kb401574.html

  • File Import error: Could not read from source (OS X 10.8.2)

    I am having this time-wasting problem on a new Creative Cloud CS6 installation. I queue my Premiere exports normally on AME (CS6 updated versions), and they work fine if I start them right away. If the Mac is restarted however, they will fail giving this error. The log shows "Could not read from the source. Please check if it has moved or been deleted". It looks for the source file at /Users/Username/Library/Caches/Temporary/projectname.prproj. Isn't AME supposed to hold the queue even after a shutdown/restart? Premiere has been uninstalled and reinstalled once, so maybe that's the cause of it? Thanks.

    Unfortunately, it looks like you've found a bug, an unplanned interaction between Premiere Pro's choice of temp directory and automatic OS behaviors.
    Jeff is correct, AME will hold the Queue between reboots. The problem is with the temporary project that Premiere creates.
    When you queue a sequence to AME from within Premiere (File > Export > Media, click the Queue button), Premiere creates a copy of the project in that temp directory. That is the file reference it sends to AME.
    The problem is that Mac OS appears to flush that directory on reboot. Thus, when you reopen AME, it can't find the file anymore.
    The bug is therefore that Premiere Pro is putting the file in a place where it can be deleted before being used. Sorry about that. I'll file the bug.
    You can work around the problem using a different method to add your sequence to the AME queue. Inside AME, use the File > Add command. You can also drag and drop the sequence icon from the Project panel in Premiere to the Queue panel in AME. Or you can just not reboot until you've rendered what's in the queue.
    I suppose it's possible that you could make Mac OS not flush the temp directory on reboot. There's a lot of fun things you can do in Terminal if you know the right commands. That's beyond my personal skillset.

  • CS4 Pr-Encoder: "Encoding failed/Could not read from the source..."

    When i start queueing it apears to be loading fine but then after a few minutes it gives me the yellow hazard triangle on the status column. I have tryied changing settings and still the same.
    "Could not read from the source. Please check if it has moved or been deleted."
    ...is what the details notepad displays
    This is my first Pr CS4 editing, Please help.
    Thanx!

    latest versions of CS4 and snow leopard 10.6.1.
    May have no part in your problem, but many are having real issues with almost anything Adobe with Snow Leopard. There has been a lot of chatter saying that Apple is aware of this, and is working on an OS update to be released soon.
    While I have not seen this particular issue with Snow Leopard, there have been so many more, that I'd certainly put the OS into the list of "usual suspects." In the Encore forum, some had great success by rolling back the OS to whatever was prior to Snow Leopard, just plain old "Leopard?"
    Wish I had a definite cure for your ills, but the best that I can offer is that it does not seem that you are alone.
    Good luck, and I hope that the Mac OS update does fix things for you.
    Hunt

Maybe you are looking for