Dennis Radeke
Forum Replies Created
-
hi Yair,
I didn’t read the forum post you linked to but when you open an older project with a newer version of Premiere Pro, you are automatically prompted to save “AS” in order to preserve the original project version.
We always open older projects but as Walter stated, you can’t open newer version projects with older versions of Premiere Pro.
HTH,
Dennis – Adobe guy -
[David Powell] “I was really hoping for improved track targeting, patching and marker function. Color following playhead is great. Its one thing I sorely missed from Avid.”
What specifically are you looking for that is missing in Premiere Pro in these respects?
Thanks,
Dennis – Adobe guy -
If the camera captured it that way, it does seem a bit weird and I can see where Premiere Pro might fall down when trying to bring them all in.
Perhaps the best solution is to simply rename the other sequences so that you can bring them in. It is one thing that Adobe Bridge is actually quite good at doing. If you have any semi-recent version of Bridge or CC version, you can look at using the batch function to rename your files so that they import correctly.
HTH,
Dennis -
Lance,
As you probably already know, we cannot discuss ship dates. Sigh – I wish I could. Glad you’re intrigued by some of the new workflows and features.
Cheers,
Dennis -
[Ryan Holmes] ”
I’m surprised that they are already incorporating codecs from cameras that just got announced yesterday! Obviously. they’ve been in talks with Canon, Apple, Panasonic, etc but that’s very on-top of it. So when the new Canon C300 Mark II ships in September Premiere will natively edit the footage. I’ve rarely seen any of the major “A’s” be that aggressive in new camera support.”We do work with many camera manufacturers as it is essential for everyone to be able to edit quickly if possible. I’m really rather proud of our aggressive support for the past several years.
Dennis
-
Among the other bits that are out there talking about new features/workflows is this 30 minute video video
It tries to hit all of the big points with some detail in a reasonable amount of time. Something else to look at.
I’ll be in Vegas until end of next week but will jump on the forums as I can.
Dennis – Adobe guy
-
[Oliver Peters] “Premiere Pro often won’t draw them or only draws interrupted sections of the waveform in a track.”
Very true that all NLE’s can have struggles with this aspect of visual representation.
Whereas Avid of old and FCP7 created uncompressed audio and therefore frame accurate and viewable waveforms as part of their mandatory transcode process, Premiere Pro doesn’t have to do that – we just play the video natively. However, this is not 100% true for audio inside of Premiere Pro. We make the assumption that you want to have viewable waveforms in the timeline and if you put compressed audio in the timeline, we need to either generate a visual representation of this or in some cases conform the audio to uncompressed.
Premiere Pro does offer some choice though between immediate editing and creating those visual waveforms. In Premiere Pro Preferences>Audio there is an option called “Automatic peak file generation”. If you deselect that, some compressed audio files won’t automatically generate the waveforms but will play.
If we are generating peak files or conforming audio, you will see a progress bar in the bottom right hand of the Premiere Pro interface. This is a one time operation. We allow you to edit while this is happening, but it does sometime affect performance during this one time operation. Again, we’re trying to balance the immediate playback experience (edit now!) versus creating a visual representation for the overall edit. Turning off the peak file generation will allow more immediate editing if you don’t care about audio waveforms.
In general, we want to import, visually represent and play immediately all audio types just as we do with video types. We do look to continue to improve the audio aspects of Premiere Pro as we continue to innovate.
I hope this helps,
Dennis – Adobe guy headed to NAB…again. 😉 -
right click on the meters themselves and see if ‘solo in place’ is checked.
-
It could be that your system isn’t up to the task of that much large frame footage – there are a lot of factors.
Two things to try
1) if the large 100GB file comes into a new project without error, then perhaps you have a corrupt file on the project you’re working on. Create a new project, import the 100GB file, make sure it is fine. Then save the project. Then, import the other project into the new one. If you point Premiere Pro to the existing project, you will have the option of bringing in select timelines or the entire project. You can use this method to see if a clip or sequence is somehow corrupt.
2) You can try to bring the project over to a computer that has more RAM (32GB or greater) and see if the project can successfully import that one large asset.HTH,
Dennis – Adobe guy -
Don’t use the standard WHQL Windows driver. Go to the NVIDIA website, download the latest driver, install it, restart the computer and you should be good to go.
Dennis – Adobe guy