Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Adobe plugin update

Deanan said:
Adobe plugin update:

We've been working hard on the Adobe plug-in, and focusing on creating a
solid workflow that encompasses Premiere Pro and After Effects. We're
almost there, but there are a few tweaks that we want to the make to the
plug-in before we release it. In addition, there is going to be an After
Effects update out in the next couple of weeks which is essential to our
ability to create a really good workflow for RED files.
Click to expand...




ohhh, not again:waaa:
 
Premiere CS4 update issues

Premiere CS4 update issues

What kind of issues are having?
 
Heck I may as well wait for FCS to be released.
 
Deanan said:
Yes. As much as it pains all of us to delay the release, we need all the ducks lined up.
Click to expand...

I feel like you could have told us that earlier... Why couln't you do so?
We are not talking about a few more days, but weeks... What has suddenly changed today, on the 20th, that you didn't see coming, say, a week ago?

Sorry to be asking like that, but I'm just really disapointed. I come and check this thead everyday, hoping for good news...
Plus, I had made big plans for the following weeks, using this magical plugin... What am I gonna do??? :sad:
 
salemas said:
ohhh, not again:waaa:
Click to expand...

Putting a target date on a software release is just that ... a target.

Obviously, MANY people want this yesterday.

All I can say is ... if you knew how hard, and how many people were working on this, and other RED post solutions while you sleep .... your head would spin.

Take a deep breath ... it's all coming.
 
Dont worry Deanan, I know you can pull it out!!

I rather have a working plugin, than a patched version trash crashes every once in a while!!!

Cheers for the good work!
 
Mark L. Pederson said:
Putting a target date on a software release is just that ... a target.

Obviously, MANY people want this yesterday.

All I can say is ... if you knew how hard, and how many people were working on this, and other RED post solutions while you sleep .... your head would spin.

Take a deep breath ... it's all coming.
Click to expand...

Sorry. I appreciate Adobe plugin team work, but I'm just disappointed .
 
Spoken like a true beta tester. Perhaps?

Yeah, I know about software. Sure, it's hard like a diamond. But it's really about managing expectations and project management.

It's all fine. Get it to work - I have no real choice.

Over a barrel,
Pete

Mark L. Pederson said:
Putting a target date on a software release is just that ... a target.

Obviously, MANY people want this yesterday.

All I can say is ... if you knew how hard, and how many people were working on this, and other RED post solutions while you sleep .... your head would spin.

Take a deep breath ... it's all coming.
Click to expand...
 
Here's from the forums at Adobe. They sure do pat themselves on the back for getting the software workable a month after release. Premiere CS4 4.0.0 was probably the first beta that people were actually charged for.

An update to Adobe Premiere Pro CS4 will be available via Adobe Update Manager shortly. The file will also be available for download tomorrow (November 20) on Adobe.com, as will the readme (at http://www.adobe.com/support/documentation/en/premierepro/releasenotes.html). In the meantime, here is the text of the readme.

We're really excited about this update, especially considering we released CS4 just one month ago. To force an update, choose help --> find updates from any Adobe application. The AME update that releases with this update is required as well.

Important note: if you are using the Elemental Technologies RapiHD plug-in, you must update to the latest version in order to use Adobe Premiere Pro CS4 4.0.1. You can update the plug-in by visiting the Elemental Technologies web page: http://www.rapihd.com/?q=node/129”

New in this release
- OMF export
- Final Cut Pro import
- Edit in Audition (Windows only)
- Surcode support
- AAF import and export
- High quality motion
- Third-party support

Notable fixes
- Attempting to trim locked tracks results in a crash (#1888355)
- Crash on Win and error on Mac when using Numpad-Asterisk keys to generate marker when
playing in Program Pane when Effect Controls pane is closed (#1890626)
- Crash when the Metadata panel is brought into focus when a DVCPro HD clip is selected
(#1884633)
- When a filter/search is applied in the Metadata Panel and then a different asset is selected, the
filter does not update (#1876954)
- Custom schema causes Adobe Premiere Pro to crash performing many basic operations,
starting with New Project (#1888938)
- Render of transition in imported EDL-based sequence fails; on Mac, causes application to hang
indefinitely, user must be force-quit application (#1873434)
- After ASND is saved, an effect is always ON if it turns OFF while playing (#1864978)
- Crash when attempting to load a project that contains a composition if headless Adobe
Premiere Pro is serving Adobe After Effects (#1871578)
- Exporting video as MPEG 4 will create a video file that imports at the incorrect length
(#1851063)
- Trimming both ends of a clip, then moving the clip will cause looped playback to be silent, or
only playback portions of the clip (#1868409)
- When exporting a timeline containing cuepoints, deleting a cue point via AME Batch-> Export
Settings, the cue point is still present in the output file (#1866690)
- Playing an audio-only file in the source monitor will cause the application to lock up (#1887330)
- Exporting any MT session as 24bit WAV leads to garbled audio – Mac only (#1881684)
- Adobe Premiere Pro allocates too much memory and reads too much data from disk when
loading project files on the Mac (#1890579)
- With camera connected, opening clip from Timeline into Source and selecting File  Debug
results in a serious error (#1889197)
- Export to tape is active from DVCPRO HD sequences (#1863718)
- Application intermittently crashes when exporting a movie (#1868405)
- Render and Replace of offline clips takes over 20 minutes (#1885273)
- Application crashes when cancelling “Normalize Audio Track” dialog (#1887615)
- When an AVCHD clip is inserted into a DV timeline with Scale to Frame Size applied, rendered
previews of the clip show artifacts during Timeline playback (#1863988)
- Using scale to frame size in a timeline lowers output quality and softens detail and sharpness;
typing in scale attributes manually or using Adobe After Effects produces much better results
(#1527669)
- Multiplexed MPEG files exported to HD size and then imported back in to Adobe Premiere Pro
show up as 601 color space instead of 709 color space and hence the colors of the imported
files are off (#1852977)

HERE"S WHAT IS STILL A MATTER.

Known issues for Adobe Premiere Pro CS4 4.0.1

- Re-installing Adobe Premiere Pro CS4.0.0 after it has been patched will generate an error dialog at the end of the installation. This dialog can be ignored.
- Uninstalling Adobe Premiere Pro CS3 after CS4 is installed will result in AME exports in CS4 to fail with ‘Could not read from the source’. Creating a shortcut named Premiere alongside the dynamiclinkmanager.exe that points to the Premiere.exe will fix the problem.
- When converting Final Cut Pro project with Color correction applied, the color correction will be incorrect within Adobe Premiere Pro.
- When converting Final Cut Pro project with Bins, the bins do not appear in Adobe Premiere Pro unless selected in the Final Cut Pro xml export.
- Multicamera enable sequence with HDV clips does not playback as normal; severe drop frame or stopping playback occurs
- Audio in a nested 16 channel sequence does not simultaneously playback all of its audio tracks in the Source Monitor.
- File>Adobe Dynamic Link>Send to Encore selection is available when a 16 channel sequence is selected; however, Adobe Encore does not support 16 channel sequences.
- File>Export>Export to OMF... selection is grayed when the Audio Mixer Panel is selected on the Mac.
- File>Export>Export to EDL... selection is grayed when the Audio Mixer Panel is selected on the Mac.
- 5.1 sequences use output mapping from the stereo channel column of the Preferences>Audio Output Mapping dialog when the audio device selected from the Map Output for menu has less than 6 channels.
- All 16 channels of a 16 channel sequence are summed to mono without attenuation when exported as media when Audio>Basic Audio Settings>Channels is set to Mono.
- Both odd and even numbered channels of a 16 channel sequence are summed to both stereo channels when exported as media when Audio>Basic Audio Settings>Channels is set to Stereo.
- 16-channel selection does not appear in the Export Settings dialog Basic Audio Settings
Channels menu when a 16-channel sequence is selected.
- All channels of a 16 channel sequence are summed to Ls, Rs and Center channels when
exported as media when Audio>Basic Audio Settings>Channels is set to 5.1.
- Setting the Optimize Rendering preference to “Memory” is highly recommended when Max Quality or Max Bit Depth rendering is on. These settings are designed for high performance systems. Please check Adobe Online Support for recommended system requirements.
- Loading an existing project with a P2 sequence that is missing media may cause a crash.
- Adobe Premiere Pro crashes when importing AAF from Avid if it contains references to clips with OMF audio (WAVE or AIFF).
- AAF may not provide consistent results for complex projects in formats other than DV or HDV.
 
Richard Darge said:
Deanan, based on 'Jannard Time', one week equates to 16 weeks. So does that mean we have to wait another 16-48 weeks??

;)
Click to expand...

LOL... the veterans on here know its a long haul.
 
Unless Adobe puts some more techs to figuring out all the Premiere cs4's core editing bugs you might as well wait. The Adobe Media Encoder can't spawn copies of the program for each core with 4bg ram/per core like After Effects can. That's something nobody has addressed.
 
Richard Darge said:
Deanan, based on 'Jannard Time', one week equates to 16 weeks. So does that mean we have to wait another 16-48 weeks??
.​
facetmedia said:
LOL... the veterans on here know its a long haul.
Click to expand...
Other just take it as a cheap shot!!
Click to expand...

Deanan said:
We're almost there, but there are a few tweaks that we want to the make to the plug-in before we release it.
Stefan said:
So your saying a few more weeks for the release?
Click to expand...
Deanan said:
Yes.
Click to expand...
Click to expand...

Deanan, please stop saying this as you said it quite a few time over the last months.

People make 'loose' plans/purchases based on it and it can affect them quite badly.
One example, we go out and make CS3 product purchases based on this information and now must purchase CS4.
This mis-information only fuels fires/problems.
Sorry to put it like this but the pattern hasn't changed.
D
 
C.K. said:
I feel like you could have told us that earlier... Why couln't you do so?
We are not talking about a few more days, but weeks... What has suddenly changed today, on the 20th, that you didn't see coming, say, a week ago?

Sorry to be asking like that, but I'm just really disapointed. I come and check this thead everyday, hoping for good news...
Plus, I had made big plans for the following weeks, using this magical plugin... What am I gonna do??? :sad:
Click to expand...
Buy a Birger mount
 
joshtownsend said:
Here's from the forums at Adobe. They sure do pat themselves on the back for getting the software workable a month after release. Premiere CS4 4.0.0 was probably the first beta that people were actually charged for.

An update to Adobe Premiere Pro CS4 will be available via Adobe Update Manager shortly. The file will also be available for download tomorrow (November 20) on Adobe.com, as will the readme (at http://www.adobe.com/support/documentation/en/premierepro/releasenotes.html). In the meantime, here is the text of the readme.

We're really excited about this update, especially considering we released CS4 just one month ago. To force an update, choose help --> find updates from any Adobe application. The AME update that releases with this update is required as well.

Important note: if you are using the Elemental Technologies RapiHD plug-in, you must update to the latest version in order to use Adobe Premiere Pro CS4 4.0.1. You can update the plug-in by visiting the Elemental Technologies web page: http://www.rapihd.com/?q=node/129”

New in this release
- OMF export
- Final Cut Pro import
- Edit in Audition (Windows only)
- Surcode support
- AAF import and export
- High quality motion
- Third-party support

Notable fixes
- Attempting to trim locked tracks results in a crash (#1888355)
- Crash on Win and error on Mac when using Numpad-Asterisk keys to generate marker when
playing in Program Pane when Effect Controls pane is closed (#1890626)
- Crash when the Metadata panel is brought into focus when a DVCPro HD clip is selected
(#1884633)
- When a filter/search is applied in the Metadata Panel and then a different asset is selected, the
filter does not update (#1876954)
- Custom schema causes Adobe Premiere Pro to crash performing many basic operations,
starting with New Project (#1888938)
- Render of transition in imported EDL-based sequence fails; on Mac, causes application to hang
indefinitely, user must be force-quit application (#1873434)
- After ASND is saved, an effect is always ON if it turns OFF while playing (#1864978)
- Crash when attempting to load a project that contains a composition if headless Adobe
Premiere Pro is serving Adobe After Effects (#1871578)
- Exporting video as MPEG 4 will create a video file that imports at the incorrect length
(#1851063)
- Trimming both ends of a clip, then moving the clip will cause looped playback to be silent, or
only playback portions of the clip (#1868409)
- When exporting a timeline containing cuepoints, deleting a cue point via AME Batch-> Export
Settings, the cue point is still present in the output file (#1866690)
- Playing an audio-only file in the source monitor will cause the application to lock up (#1887330)
- Exporting any MT session as 24bit WAV leads to garbled audio – Mac only (#1881684)
- Adobe Premiere Pro allocates too much memory and reads too much data from disk when
loading project files on the Mac (#1890579)
- With camera connected, opening clip from Timeline into Source and selecting File  Debug
results in a serious error (#1889197)
- Export to tape is active from DVCPRO HD sequences (#1863718)
- Application intermittently crashes when exporting a movie (#1868405)
- Render and Replace of offline clips takes over 20 minutes (#1885273)
- Application crashes when cancelling “Normalize Audio Track” dialog (#1887615)
- When an AVCHD clip is inserted into a DV timeline with Scale to Frame Size applied, rendered
previews of the clip show artifacts during Timeline playback (#1863988)
- Using scale to frame size in a timeline lowers output quality and softens detail and sharpness;
typing in scale attributes manually or using Adobe After Effects produces much better results
(#1527669)
- Multiplexed MPEG files exported to HD size and then imported back in to Adobe Premiere Pro
show up as 601 color space instead of 709 color space and hence the colors of the imported
files are off (#1852977)

HERE"S WHAT IS STILL A MATTER.

Known issues for Adobe Premiere Pro CS4 4.0.1

- Re-installing Adobe Premiere Pro CS4.0.0 after it has been patched will generate an error dialog at the end of the installation. This dialog can be ignored.
- Uninstalling Adobe Premiere Pro CS3 after CS4 is installed will result in AME exports in CS4 to fail with ‘Could not read from the source’. Creating a shortcut named Premiere alongside the dynamiclinkmanager.exe that points to the Premiere.exe will fix the problem.
- When converting Final Cut Pro project with Color correction applied, the color correction will be incorrect within Adobe Premiere Pro.
- When converting Final Cut Pro project with Bins, the bins do not appear in Adobe Premiere Pro unless selected in the Final Cut Pro xml export.
- Multicamera enable sequence with HDV clips does not playback as normal; severe drop frame or stopping playback occurs
- Audio in a nested 16 channel sequence does not simultaneously playback all of its audio tracks in the Source Monitor.
- File>Adobe Dynamic Link>Send to Encore selection is available when a 16 channel sequence is selected; however, Adobe Encore does not support 16 channel sequences.
- File>Export>Export to OMF... selection is grayed when the Audio Mixer Panel is selected on the Mac.
- File>Export>Export to EDL... selection is grayed when the Audio Mixer Panel is selected on the Mac.
- 5.1 sequences use output mapping from the stereo channel column of the Preferences>Audio Output Mapping dialog when the audio device selected from the Map Output for menu has less than 6 channels.
- All 16 channels of a 16 channel sequence are summed to mono without attenuation when exported as media when Audio>Basic Audio Settings>Channels is set to Mono.
- Both odd and even numbered channels of a 16 channel sequence are summed to both stereo channels when exported as media when Audio>Basic Audio Settings>Channels is set to Stereo.
- 16-channel selection does not appear in the Export Settings dialog Basic Audio Settings
Channels menu when a 16-channel sequence is selected.
- All channels of a 16 channel sequence are summed to Ls, Rs and Center channels when
exported as media when Audio>Basic Audio Settings>Channels is set to 5.1.
- Setting the Optimize Rendering preference to “Memory” is highly recommended when Max Quality or Max Bit Depth rendering is on. These settings are designed for high performance systems. Please check Adobe Online Support for recommended system requirements.
- Loading an existing project with a P2 sequence that is missing media may cause a crash.
- Adobe Premiere Pro crashes when importing AAF from Avid if it contains references to clips with OMF audio (WAVE or AIFF).
- AAF may not provide consistent results for complex projects in formats other than DV or HDV.
Click to expand...


ohhh shi... this list is long....

:)
 
You must log in or register to reply here.
Back
Top