Do bugs in premiere demage projects in memory and/or on disk?

Above this is clearly a bug and I've submitted a bug report already. Being a C programmer by myself I know very well what this can cause for havoc. My question is: has anybody noticed that their premiere project has become unusable through a crash/bug? I'm editing a very large project at the moment with about 100 scenes which then go into a master track (nested sequences). Obviously, the worst nightmare is that I arrive at some point at scene 100 and then notice that scene x is totally garbled. Can I save sequences separately so that I have separate files just in case my huge master file becomes unusable through whatever reasons?

hey there melody74,
what you ask isn't possible w/ iDVD, but is w/ DVD SP4, part of Final Cut Studio. you would need to make 2 versions of your movie--1/ widescreen 16:9 & 1/ standard 4:3, then author matching DVDs for each movie version.
good luck.

Similar Messages

  • Premiere CS5 consuming all memory and freezing up

    I spent a couple of days farming around 2000 images into a Premiere project on  a Mac Pro, Premiere CS 5.0.0 and when I opened it this morning I could see from Activity Monitor that it very quickly consumed 12gb of memory, leaving a figure between 17-24Mb handling the system, therefore freezing the entire system and unable to do anything other than watch the beachball or Force Quit Premiere. I'd only pulled a handful of images into the timeline, so it wasn't a heavy project. Just linked to a lot of hi-res files. But why would they eat up all the RAM when I wasn't accessing or using them, they were just sat there in the project window. I have plenty disk space for scratch and running Mac OS 10.7.1.
    I've had to just bail on Premiere and take it over to Final Cut, but still curious to know why this happened and if I might be able to return the project to Premiere at some stage? I've since ran the 5.0.4 update in the background and it still eats up the memory and still freezes up, even crashing the first time I opened it after update.
    Any ideas?

    My experience using stills with FCP7 is far worse than with Pr.  Crash City.  Very painful.  Esp. with JPEGs.
    I've seen issues with stills that are very large, scaled down in a sequence.  From what you describe, it sounds like the stills are being loaded into RAM, leaving nothing for other operations.  If this is so, you could try scaling down your images, perhaps by automating the process in Photoshop.
    I don't know if it's normal to load images in the project (and not in a sequence) into RAM.  That doesn't seem right.  Another cause for the beachball could be corrupt source images.  You could determine this by adding a few stills at a time, and waiting for the axe to fall.
    I never used Pr 5.0.x, other than playing around.  I didn't think it was ready for professional use until 5.5, so my experience.  Maybe somebody else with experience on that version has more helpful info.
    I have done a couple of "slide show" style projects in Pr, and other than suffering the occasional corrupt image, it's been pretty painless, and far better than my experience trying the same thing in FCP.
    Good luck.

  • Crash bug in Premiere when editing Marker descriptions and using scroll wheel

    So I've noticed a really particular bug:
    If I go to edit a Marker description in the Markers panel, and I add some text, then move the scroll wheel of my mouse, the program immediately crashes, with these errors:
    "[/caravan/releases/2014.09/PremierePro/UIFramework/Src/HotTimecodeControl.cpp-203]"
    "[/caravan/releases/2014.09/PremierePro/UIFramework/Src/InlineEditText.cpp-140]"
    Then it has the standard: "Sorry, Premiere has to shut down. It will try to save your project" - But it never does make a recovery.
    More details:
    This happens when the cursor is still active in the description box. If I've clicked out of the description box, everything works normally.
    It only happens in the Markers panel, not in the individual Marker dialog box
    It only happens after new text has been typed in or pasted in.
    It doesn't happen with the Name box
    It happens immediately upon touching the scroll wheel, even if it's just a nudge (in either direction)
    It happens in every sequence I've tried it in
    Tech specs:
    Premiere CC 2014 (version 2014.1)
    MacBook Pro (15-inch, Late 2011), OSX Yosemite 10.10.1, 2.2 GHz clockspeed, 8GB RAM
    Wireless Logitech Mouse (the Anywhere MX) (with Logitech wireless keyboard)
    Not a single mouse issue before!
    Anyone know if there's a patch or a workaround for this? I know it's specific enough of a problem to avoid, but I work with markers a lot and the scroll wheel on this mouse is sensitive, so can get easily nudged and thus instantly muck up all the work I've done since the last save...
    Thanks for your help!

    Hi Bob,
    So I've noticed a really particular bug:
    If I go to edit a Marker description in the Markers panel, and I add some text, then move the scroll wheel of my mouse, the program immediately crashes, with these errors:
    "[/caravan/releases/2014.09/PremierePro/UIFramework/Src/HotTimecodeControl.cpp-203]"
    "[/caravan/releases/2014.09/PremierePro/UIFramework/Src/InlineEditText.cpp-140]"
    Then it has the standard: "Sorry, Premiere has to shut down. It will try to save your project" - But it never does make a recovery.
    No promises, but this bug has been marked as fixed in the upcoming version of Premiere Pro. Sorry for all the frustration this has introduced.
    Anyone know if there's a patch or a workaround for this?
    The workaround listed is, "always remember to exit the control by clicking outside it or tabbing to the neighboring box before scrolling."
    Hopefully, the upcoming fix will be done to your satisfaction.
    Thanks,
    Kevin

  • Audio recording in memory and not on disk...

    Hi all,
    after searching on Apple reference I found that it's possible, using Audio Queue Services, to record not only on a physical file (ref: Audio Queues Services Programming Guides).
    I saw the SpeakHere example and some other threads in this forum, but all are recording on a file...
    What paremeter I have to pass to the recording callback function instead of the pathToFile or the AudioFileID?? I'd like to have a in memory buffer (byte array, or something similar...)...
    Any Help??

    First question: 192 bit audio -- does iDVD support this?
    I thought i heard that iDVD8 was supposed to support MPEG muxed?
    If not, your best bet is MPEG Streamclip - free from Apple
    Tho you MAY need:
    1. QTPro &/or
    2. MPEG2 plugin) to do what you want. -
    Streamclip has several 'demux' commands (I can't speak for whether or not this touches/degrades video - but seems likely not.. ).
    I really think iLife is fabulous -- but Apple makes it REALLY difficult to figure out what these Apps support & Worse how to get from point A to B without degrading quality.
    HTH - xandra
    Please post back if you find a solution.

  • Premiere Elements project imported into Premiere Pro CS5.5 becomes unusable after first save

    I have Premiere Pro CS5.5, and I have been trying for some time to successfuly edit an old project that was originally created in Premiere Elements (not sure which version--probably 7.0). It has the .prel extension. The project imports just fine, and I am able to edit it initially. However, if I save my new Premiere Pro project, close Pr and try to open the new project again, I get the "The project could not be loaded, it may be damaged or contain outdated elements." error message. I have tried many of the various project recovery suggestions people have made in this forum and elsewhere online, but none of them seem to work. I even opened the project in XML Wrench, but there were no errors returned when I clicked "check is well formed." Once I close the project after doing some initial editing, it is gone. Is this a known issue? Is there any way I can be able to edit the old project in Pr and save my work? Thanks!

    Have you tried using the project manager to re-copy all elements and timeline etc into a totally new directory. I'm just curious to see if that would make a difference. I'd be intrested to see if when making a new project in this manor if it would because as you have stated the normal save methods haven't.

  • Does iOS support virtual memory and a swap file?

    I'm getting conflicting reports on this one...

    From +Memory Usage Performance Guidelines+
    Both Mac OS X and iOS include a fully-integrated virtual memory system that you cannot turn off; it is always on. Both system also provide up to 4 gigabytes of addressable space per 32-bit process. In addition, Mac OS X provides approximately 18 exabytes of addressable space for 64-bit processes. Even for computers that have 4 or more gigabytes of RAM available, the system rarely dedicates this much RAM to a single process.
    To give processes access to their entire 4 gigabyte or 18 exabyte address space, Mac OS X uses the hard disk to hold data that is not currently in use. As memory gets full, sections of memory that are not being used are written to disk to make room for data that is needed now. The portion of the disk that stores the unused data is known as the backing store because it provides the backup storage for main memory.
    Although Mac OS X supports a backing store, iOS does not. In iPhone applications, read-only data that is already on the disk (such as code pages) is simply removed from memory and reloaded from disk as needed. Writable data is never removed from memory by the operating system. Instead, if the amount of free memory drops below a certain threshold, the system asks the running applications to free up memory voluntarily to make room for new data. Applications that fail to free up enough memory are terminated.

  • Keyframes in Speedgrade with a Premiere Pro project

    I'm using Speedgrade to grade clips in a Premiere Pro project.  I'm trying to adjust a primary layer grade across a clip using different keyframes.  It is not working: when I set up a second keyframe, I try to make adjustments to the offset, gamma, and gain in the second keyframe and, while the sliders slide, I'm not seeing any results in either the clip or the scopes.
    It's working fine when I create a Speedgrade project.  But it's not working with an imported Premiere Pro project.
    I can't find any indication of a bug related to this.  Anyone have any suggestions?

    I've submitted the bug report. 
    Here's a bit more information about my environment:
    MacOS 10.10.1.
    Macbook Pro Retina (mid 2012)
    2.7 GHz Intel Core I7
    16 GM memory
    Intel HD Graphics 4000 1024 MB
    I have some 3rd party plugins installed in Premiere, but none used in the test case.  And in fact I can reproduce the problem with a fresh project by following these steps:
    1. Create a new project in Premiere.
    2. Import a video file.  (The video file is one that I recorded with my Canon 5D mk iii, but the original problem was using files gotten from a GoPro, so that detail doesn't seem to matter.)
    3. Create a new sequence.
    4. Take a 3 second clip from the video file and put it in the sequence.
    5. Take a different 2 second clip from the video file and add it to the sequence.
    6. Use the File/Direct Link to Speedgrade menu option to load the sequence in Speedgrade.
    7. In Speedgrade, select the first clip.  Make changes to the Offset and Gain brightness sliders for that clip.
    8. Select the second clip.  Position the cursor over the first clip and hit "c" to copy the grade changes from the first clip to the second.
    9. Position the read head about midway through the second clip.
    10. Hit the diamond to add a keyframe.
    11. Make changes to the offset and gain brightness sliders at that keyframe.
    12. Hit the keyframe left arrow to move to the initial keyframe in the clip.
    13. Notice that the brightness changes made on the original keyframe show in this keyframe.  This is unexpected behavior.
    14. Attempt to make changes to the offset and gain brightness sliders at this keyframe.  The sliders slide, but there are no changes to the clip itself.  If you bring up the scopes at this point, making changes to the sliders don't change the scope values either.
    Joe

  • Premiere CS5 - Project Monitor playback is jerky after resintall of operating system and CS5

    PROBLEM: Premiere CS5 - Project Monitor playback is jerky
    This had NOT been an issue prior to reinstalling the operating system and all software.  I have read numerous articles on the forums and have tried everything I can find...with no results.
    STEPS TAKEN TO RESOLVE THE PROBLEM:
    I have scoured the articles here http://www.adobe.com/cfusion/search/index.cfm?loc=en_us&term=choppy%20video&cat=support&pr oduct=premierepro and others at Cretive Cow
    I have installed all updates for CS5 Master Collection, immediately following a fresh install of the operating system and SC5 Master Collection.
    I have ensured that sequence settings match resolution and frame rates of footage - the problem persists.
    I have tested by importing both standard def AVI files created from tape and high def SONY MP4 files - the problem persists.
    I have ensured the latest Video drivers are installed (clean installation selected, so that the Windows default would be removed) - the problem persists.
    I have tried the 3D settings in NVIDIA control panel | Program Settings tab... selected Adobe Premiere Pro from the drop down menu | and chaged 'Multi-display/mixed-GPU acceleration from the value of 'Multiple Display performance' to the value of 'single display performance'; although, I ran two monitors before using this latest NVIDIA video driver and I didn't experience this jerky footage issue - the problem persisted after affecting that change; so, I switched it back. 
    Since I have 96 GB of RAM, I don't use a pagefile.  A zero MB page file is the same setting I had prior to rebuilding the C:  Regardless of whether I have a pagefile or not, the problem persists.
    I have tried creating a fresh user profile, where the user profile is created on the C: drive by default; and, where I left it there on C: to test for the jerky playback in a new PrPR project  - the problem persists.
    Regarding the C: (system drive) and why I reinstalled everything, it had become unstable and was locking up.  I ran DISK ERROR CHECKING with the FIX parameter and the system was still locking up on me.  Keep in mind that the System drive is a solid state drive.  Anyhow, I had no choice but to dive in and reinstall everything.  I wiped the system partition of the SSD using quick format and started installing the operating system.  Now, I've read the CLAIM that this cuases performance issues; but, the only place I see issues is in the video monitor playback in PrPr.  Everything else - Office applications...printing...browsing the Internet...works just fine, everything is responsive, whereas, I couldn't do ANYTHING with it before.
    SYSTEM CONFIGURATION:
    The Operating system and all software is installed on C:
    All data files and most profile related folders are stored on D:
    C:\ (one Intel Solid State Drive - SYSTEM DRIVE)  Used Space: 57.5 GB  Free Space: 388 GB
    D:\ (four Western Digital 2TB drives in an on-board INTEL hardware RAID5 array & hotswapable backplane) used space: 1.28 TB Free space: 4.16TB
    Adobe Premiere Pro CS5 VERSION: 5.0.3 (005 (MC: 218798))
    Operating System    Microsoft Windows 7 Ultimate Version    6.1.7601 Service Pack 1 Build 7601
    System Manufacturer    Intel Corporation
    System Model    S5520SC
    System Type    x64-based PC
    Video    NVIDIA Quadro FX 4800 driver v.320.78
    Display        Dell 27" LCD (DisplayPort)
    Display        Dell 27" LCD (DisplayPort)
    Processor    Intel(R) Xeon(R) CPU           X5680  @ 3.33GHz, 3326 Mhz, 6 Core(s), 12 Logical Processor(s)
    Processor    Intel(R) Xeon(R) CPU           X5680  @ 3.33GHz, 3326 Mhz, 6 Core(s), 12 Logical Processor(s)
    Installed Physical Memory (RAM)    96.0 GB
    Page File Space    0 bytes
    PREMIERE PRO CS5 SETTINGS:
    Monitor PLAYBACK RESOLUTION: Full
    Monitor PAUSE RESOLUTION: Full
    (regardless of this setting, the problem persists)
    PREFERENCES:
    MEMORY:
    Installed RAM: 95.9 GB
    RAM reserved for other applications: 10 GB
    Optimize rendering for: Performance
    (Changing this setting to 'memory' does not resolve the problem)
    MEDIA:
    Media Cache Files
    X - Save Media Cached files next to originals when possible
    LOCATION: D:\Users...\AppData\Roaming\Adobe\Common
    (User Profile folders were relocated to D:\ from within the properties of each folder's 'LOCATION' tab.  This is the same configureation I had prior to rebuilding the C:\drive.  Testing under a new profile where it's allowed to stay on teh system drive does NOT resolve the problem.)
    Media Cache Database
    LOCATION: D:\Users...\AppData\Roaming\Adobe\Common
    PROJECT SETTINGS:
    Scratch Disks
    Path: D:\Users...\My Documents\
    General
    Video Rendering and Playback: Mercury Playback Engine GPU Acceleration
    (Setting Viideo Rendering and Playback to 'Sofware' does not resolve the problem)
    If any of y'all have any other suggestions, I'm all ears.
    Thank you.

    I'VE RESOLVED THE PROBLEM!
    PREFACE:
    OK, I am hoping that through this week-long Operating-System-and-Software-reinatalltion excerise of mine, I have revealed something that everyone -- whom have been cursing Adobe over -- can apply to their systems to resolve this jerky video problem within PremierePro CS5 (and quite possibly other versions, too). 
    If you've read my post above, you've seen all the steps I've taken to resolve the problem.  I've read many posts, some of which have mentioned  hardware upgrade / opitmization steps that one may take to enhance performance, and hopefully resolve the problem.  I've read where people have taken these steps and have still experienced the problem...and then they curse Adobe.  Fer-shame, fer-shame, fer-shame! (nod to Gomer Pyle). 
    In my case, I knew it wasn't an Adobe issue, as it had worked flawlessly before; and, it wouldn't require a hardware upgrade or reconfigureation, as my system is completely maxed out with two processors, a system drive and a hardware RAID5 array, a CUDA-suported nVIDIA 4800 FX card, and 96 GB of RAM.  bla bla bla, puke...whatever.  Bottom line is this:
    It's not a software issue.  It's not and Adobe issue; and Gawd no!  It's NOT a PC vs. Mac issue!  HA HA.  The software had worked swimmingly well prior to the reinstallation / 'lobotomy' I perfomed on the system drive.
    SOLUTION FOR ME:
    Download and install the updated drivers for the motherboard.  Mine is an Intel Workstation Board S5520SC.  Intel has an INTEL DRIVER UPDATE UTILITY which automatically scaned my Intel system and identified drivers which needed updating.  A very handy, time-saving tool!!!  Here's the URL: http://www.intel.com/p/en_US/support/detect?iid=dc_iduu
    The scan revealed two Intel drivers needing an update:
    Intel Chipset
    Wired Networking
    and one non-intel driver:
    Creative Labs Sound Blaster X-fi
    I downloaded and installed these three drivers, rebooted, and tested PremierePro, and was extatic to find this resolved the problem.
    If you have a motherboard from another manufacturer, then you may want to navigate over to their wibsite to locate chipset and other updated drivers for your motherboard. 
    ROOT CAUSE:
    While Microsoft Windows 7 Ultimate was able to install certain default drivers during the Operating System installation (keeping in mind that this was done on an Intel Solid State Drive that I formatted using Quick Format) these default chipset drivers apparently weren't current and were ultimately the root cuase of the jerky video playback within PremierePro CS5.
    Peace

  • After Effects export as Premiere Pro project weird PAL/NTSC problem

    This post is not a question. It's here, because I've found a solution and want to share with You.
    I've noticed a strange problem during export from AE to PR.
    Ok, here I go.
    AE = After Effects CS3
    PR = Premiere Pro CS3
    My AE project is D1/DV PAL Widescreen. It is a sequence of slideshow with some video effects applied. I needed that sequence in PR. I was happy to find a new feature - export as premiere pro project (new for me - i am pretty rookie ;). Thaks to this feature I have saved most of my disk space that is always to low. But, like every first try, this one was not perfect too. I had two problems.
    Problem no 1.
    I opened exported project in PR and saw message like "video effect AE.CC COMPOSITE not present".
    Whole composition was working perfectly except that one video effect that was fundamental for this project.
    *Solution was as easy as it can be. I've just copied that effect from AE plugin folder to PR plugin folder. It worked for this.
    Problem no 2
    Like says AE Help "When you export an After Effects project as an Adobe Premiere Pro project, Adobe Premiere Pro uses the settings from the first composition in the After Effects project for all subsequent sequences."
    Project settings in PR was exactly D1/DV PAL Widescreen. So where is the problem You ask?
    Therefore why my Timeline works in NTSC 29,97 frame rate if all settings match PAL 25 frame rate?! I don't know.
    *Solution to fix this annoying bug is to create a new project in PR with all settings for D1/DV PAL Widescreen in this case. Than just import that PR project exported from AE. Now timeline works like it should in PAL frame rate.
    That's it.
    I hope this post is helpful, because I didn't find any answer for this here in Adobe forum.
    Adam

    Who's says that Microsoft can't debug?
    I used msconfig, first disabling startup items, -same result.
    Enabled all startup items, disabled all non-microsoft services - AE worked!
    I re-enabled each service in turn until AE crashed.
    The fault was related to an item for a video streaming device I have in my house.  It was Monsoon-multimedia's Vulkano Service.  Sometimes under the old name of Hava, this is an app that acts like a sling-box to send my Cable TV to my screen.  It does load a couple of virtual devices in device manager, and uses a proprietary codec.
    I uninstalled the vulkano streamer application and rebooted the external Vulkano device.  I reinstalled the Vulkano and verified it connected to the device and could stream.  Once it did, I tried AE again and IT WORKED!
    I wonder if simply rebooting the Vulkano would have fixed it.  Its like opening the garage door to turn on the refridgerator.
    Thanks for the help!
    Jim

  • Importing a Premiere Pro Project file in AE

    Hi,
    I've just finish editing a long feature with Premiere Pro that I've broken down into 10 project files to allow Premiere not to have the memory crash.
    Now I'd like to import in AE the project file to be able to do image stabilization on different shot and sky replacement.
    My questions are:
    a) If I import the project files, can I make modifications in AE (like color correction, stabilization, sky replacement,...) then save the project so that it can still be opened in Premiere
    b) Can I recombined my whole feature into one project in AE or the memory won't handle it as Premiere's memory didn't ?
    Thank you.

    > If I import the project files, can I make modifications in
    > AE (like color correction, stabilization, sky replacement,...)
    > then save the project so that it can still be opened in Premiere
    You can save a Premiere Pro project from After Effects. See
    "Export an After Effects project to Adobe Premiere Pro".
    Note that there are several other ways of moving data between After Effects and Premiere Pro, including copy & paste and Dynamic Link. See
    "Working with Adobe Premiere Pro and After Effects".
    > Can I recombined my whole feature into one project in AE
    > or the memory won't handle it as Premiere's memory didn't ?
    The size of the project doesn't tend to be a problem for After Effects. (Frame size, occasionally; image buffer size, occasionally; but not project size.)

  • Premiere Pro Project loads then immediately shuts down

    I have a large Premiere Pro CS4 project which is completed and has written a standard DL DVD but I now wish to incorporate it into a Bluray DVD.  I have had numerous problems doing this but the system which has worked well so far is to load the PP project, export each sequence to the HD 1080 PAL 25fps format and then create a new Encore project, importing assets as I go.  So far so good.  I have completed a couple of other projects using this method and all goes well.
    The current problem is I had done three sequences of a project (there are 6) and I needed to go out and so I stopped and let the machine encode those three before going on.  Unfortunately I had begun exporting the fourth sequence and I attempted to cancel it but the machine ended up in a hopeless knot.  Eventually I had to kill PP and Media Encoder and reboot the machine.  I had to delete the preferences in Media Encoder to get it going, but it then worked and all three are now encoded.  The fourth (which was in progress but cancelled) just disappeared - it was not saved in the MEdia Encoders queue and so that is what I expected.
    This morning I attempted to load the pp project again and it loaded pp, then loaded the project but just as the yellow bar got to the end of the load sequence (no sub-windows up at all yet) it terminated pp with no messages.  I tried again - same result.  I had a generational backup and so I went back one version - same result.  I cleaned the cache and deleted all the "Encoded Files" folders.  No different.  I can load other projects, and in fact the machine is now encoding another project successfully.
    How do I get my project to load?
    The machine is a 64bit I7-950 running Windows 7 64 bit Ultimate - it has 8gb of memory and 3.5tb of disk in a raid 5 Format

    I have solved my own problem.
    I had to delete User\Users\AppData\Roaming\Adobe\Common\Media Cache Files myself - Cleaning the cache did not do it completely.
    Now I have restored the latest version and it works just fine.
    PiccadillyPunter

  • Please Fix FPS sequence bug in Premiere !

    every time you move a folder with a project or for example you copy a project into a hard drive to work in another computer all image sequence FPS changes to original frame rate instead what FPS you choose to assume.
    To replicate the error:
    in a mac OSX
    in finder prepare a folder with an image sequence
    1) create a project, with a PAL Timeline,
    2) insert a image sequence, modify the intepretation FPS to "assume this frame rate" change it to 25 or something different from the original FPS
    3) drag and drop the sequence into the timeline
    4) save and quit
    5) Copy the folder containing the project and the sequence to an external hard drive
    6) open the project in another computer.
    you will notice that the FPS interpretation has changed to the "use frame rate from file" instead the "assume this frame rate" option
    this is easy to fix when it's only one clip, but when you are doing huge edits with some differents Frame rates on same timeline, (especially intrepreting 60fps to 30fps) it's a really painful bug
    Adobe premiere Ver 7.2.1(4)
    OSX 10.8.5  2 x 2.4 Ghz Quad Core intel xeon 24G Ram

    Hi Mariano,
    I know this is fixed in Premiere Pro CC 7.2.1 for standard video clips. However, I'm not sure how it affects image sequences. Please file a bug. In the mean time, you could have this option if you convert your image sequences to video files.
    Thanks,
    Kevin

  • FAQ: Can I open my Adobe Premiere Clip project in Adobe Premiere Pro?

    Yes. When you are ready to export your project to Premiere Pro, begin by tapping the share button in the upper right corner of your screen. Next, simply tap the Edit in Premiere Pro button. Within a few minutes, this will send your project and media to your Creative Cloud folder. Open up Premiere Pro on your computer, and from the Welcome Screen select the option to “Convert Premiere Clip Project” under the “New” heading. Next, choose the project XML file you wish to continue editing in Premiere Pro. All of your project edits will show up in your Premiere Pro timeline, making it easy to continue working.

    Since PrPro project is an XML file, you can open it up in any script editor (e.g. Adobe ExtendScript Toolkit) or even text editor, in fourth line find Version="25"
    <?xml version="1.0" encoding="UTF-8"?>
    <PremiereData Version="3">
         <Project ObjectRef="1"/>
         <Project ObjectID="1" ClassID="62ad66dd-0dcd-42da-a660-6d8fbde94876" Version="25">
    and replace it with Version="23".
    Although it works just fine most of the time, bear in mind: everything is at your own peril.

  • Error Importing Premiere Elements project into Premiere Pro CS5

    Hi,
    I am working on a multi-part video project that I started in Premiere Elements 8.  I put in hours upon hours of editing on the first part and I found that the more I edited, the more often the program would crash (infuriating!).  So I started using Premiere Pro CS5 to produce the second part, resolving to come back to the first part later.  Well, I've come back around to needing this first part done, and it is just undoable in Elements (crashes every 20 seconds!).  I'd like to import that project into CS5 if possible.  The help documentation says this should be perfectly possible... but I'm having no luck.
    When I attempt to open my Premiere Elements project in Premiere Pro, it tells me the project must be converted from Elements .prel to Pro .prproj, and I click through the prompts as normal.  But then as soon as it starts trying to open the project, I get this:
    "The Project could not be loaded. It may be damaged or contain outdated elements."
    I downloaded the Premiere Elements 9 trial to see if it would be less crashy (and it is), but I'd really prefer to have all my video in one program, and CS5 does the best job (and has most of my hours invested).  Elements 9 opens the "damaged" project just fine and I can edit and export normally, so why can't CS5?
    Am I stuck recreating the project from the ground up in CS5?

    In very general terms, a contemporary PrE Project (PREL), will Open in PrPro, with the steps that you outlined.
    Now, there are all sorts of considerations, for aspects that will not likely work:
    Instant Movie/Themes, as PrPro cannot read those
    Some Effects that PrPro does not have, like the NewBlue FX
    Some Transitions that PrPro does not have
    Some Title animation Presets, that PrPro does not have
    Do you have any of the above in your PrE Project? There are probably other circumstances, but those are all that come immediately to my mind.
    The simpler the PrE Project, the greater the likelyhood that it will Convert to a PrPro PRPROJ file.
    PrE 8 and PrPro CS5 should be close enough to work, again in those general terms. I can Open simple PrE 4.0 Projects in PrPro 2.0, but cannot Open PrE 7, 8 or 9 Projects in PrPro 2.0.
    Good luck,
    Hunt

  • Bug in my code or strange memory behavior ?

    Hi, Guys !
    It's been a while since I post something in this forum - trying to use your help when it's really needed.
    So, here we go ...
    (we use Oracle 8.1.7 on Unix box and SQL * Plus 8.1.6)
    While back I wrote "core" PL/SQL package that resides in let's say DB1 database. It has RECORD_EXISTS_FNC function designed to dynamically check If the record exists in certain table/view. Assumptions are that you pass in :
    Table/View name, Column name, and unique numeric value (because by DBA rules all of our Tables have SEQUENCE as a Primary Key. And I plan soon to put in overloaded function to accept unique character value)
    Also every Table has SYS_TIME_STAMP and SYS_UPDATE_SEQuence columns that populated by Trigger before Insert/Update representing Last Update time_stamp
    and how many times record was updated within same second.
    (in case more than one User updates same record in same time - that was written before Oracle had more granular date/time). So function has SYS_TIME_STAMP and SYS_UPDATE_SEQUENCE parameters (optional) accordingly.
    And It looks something like :
    FUNCTION RECORD_EXISTS_FNC
    (iBV_NAME IN USER_VIEWS.VIEW_NAME%TYPE,
    iPK_FIELD IN USER_TAB_COLUMNS.COLUMN_NAME%TYPE,
    iPK_VALUE IN NUMBER,
    iSYS_TIME_STAMP IN DATE DEFAULT NULL,
    iSYS_UPDATE_SEQ IN NUMBER DEFAULT NULL) RETURN BOOLEAN IS
    TYPE REF_CUR IS REF CURSOR;
    CR REF_CUR;
    i PLS_INTEGER DEFAULT 0;
    vRESULT BOOLEAN DEFAULT FALSE;
    vQUERY USER_SOURCE.TEXT%TYPE;
    BEGIN
    vQUERY := 'SELECT 1 FROM ' || iBV_NAME || ' WHERE ' || iPK_FIELD || ' = ' || iPK_VALUE;
    IF iSYS_TIME_STAMP IS NOT NULL AND iSYS_UPDATE_SEQ IS NOT NULL THEN
    vQUERY := vQUERY || ' AND SYS_TIME_STAMP = TO_DATE (''' || iSYS_TIME_STAMP || ''')
    AND SYS_UPDATE_SEQ = ' || iSYS_UPDATE_SEQ;
    END IF;
    IF iBV_NAME IS NOT NULL AND
    iPK_FIELD IS NOT NULL AND
    iPK_VALUE IS NOT NULL THEN
    OPEN CR FOR vQUERY;
    FETCH CR INTO i;
    vRESULT := CR%FOUND;
    CLOSE CR;
    END IF;
    RETURN vRESULT;
    EXCEPTION
    WHEN OTHERS THEN
    IF CR%ISOPEN THEN
    CLOSE CR;
    END IF;
    INSERT_ERROR_LOG_PRC ('CORE_PKG', 'ORACLE', SQLCODE, SQLERRM, 'RECORD_EXISTS_FNC');
    RETURN vRESULT;
    END RECORD_EXISTS_FNC;
    So the problem is when I call this function from let's say
    database DB2 (via db remote link and synonym) and I know exactly that record does exists (because I am selecting those SYS fields before pass them in) - I get the correct result TRUE. The other programmer (Patrick) calls this function within same DB2 database, within same UserID/password (obviously different session), running exactly the same testing code and gets result FALSE (record doesn't exist, but it does !) He tried to Logoff/Login again several times within several days and try to run it and still was getting FALSE !
    I tried to Logoff/Login again and I was getting mostly TRUE and sometimes FALSE too !!!
    I thought may be It has something to do with REF CURSOR that I use to build SQL on the fly, so I changed to NDS
    using EXECUTE IMMEDIATE statement - nothing changed.
    vQUERY := 'SELECT COUNT (1) FROM ' || iBV_NAME || ' WHERE ' || iPK_FIELD || ' = ' || iPK_VALUE;
    IF iSYS_TIME_STAMP IS NOT NULL AND iSYS_UPDATE_SEQ IS NOT NULL THEN
    vQUERY := vQUERY || ' AND SYS_TIME_STAMP = TO_DATE (''' || iSYS_TIME_STAMP || ''') AND SYS_UPDATE_SEQ = ' || iSYS_UPDATE_SEQ;
    END IF;
    EXECUTE IMMEDIATE vQUERY INTO i;
    vRESULT := NOT (i = 0);
    RETURN vRESULT;
    Interesting note : when Patrick doesn't pass SYS parameters (Time_stamp, Update_sequence), or passes NULLs - function always finds the record ! (Statement 2 below)
    May be it has to do with the way TO_DATE () function gets parsed in that dynamic SQL - I don't know ...
    Here's the test code :
    SET SERVEROUTPUT ON;
    DECLARE
    SYS_TIME DATE;
    SYS_SEQ NUMBER;
    bEXISTS BOOLEAN DEFAULT FALSE;
    BEGIN
    SELECT SYS_TIME_STAMP, SYS_UPDATE_SEQ INTO SYS_TIME, SYS_SEQ FROM LOCATION_BV WHERE PK = 1;
    bEXISTS := CORE_PKG.RECORD_EXISTS_FNC ('LOCATION_BV','PK',1, SYS_TIME, SYS_SEQ); -- STATEMENT 1
    --bEXISTS := CORE_PKG.RECORD_EXISTS_FNC ('LOCATION_BV','PK',1, NULL, NULL);        -- STATEMENT 2
    IF bEXISTS THEN
    DBMS_OUTPUT.PUT_LINE ('TRUE');
    ELSE
    DBMS_OUTPUT.PUT_LINE ('FALSE');
    END IF;
    END;
    I asked our DBA, he has no clue about this strange inconsistent results.
    I debugged line by line, extracted that generated SQL and ran it in same account - works fine !
    Does anyone knows or have clues or can help what's going on ???
    I don't know If this is bug in my code or strange memory behavior ?
    (Please let me know If anything unclear)
    Thanx a lot for your help and time !
    Steve K.

    see your other thread
    Bug in my code or strange memory behavior ?

Maybe you are looking for