[Paul King]

Sorry, I thought I saw them on the website.

Sorry

Paul

[Paul King]

Hi Bill

If it’s OK with you I answer the question.

The 3GB switch is designed for Windows apps to see more physical memory. Most of us are putting in 4GB, mostly because of MB requirements for RAM installed in pairs. I am unable to go into much detail about why it is that we are doing it (NDA) however you should consult your NLE hardware supplier (incidently who is it? Blackmagic, Matrox?).

The reason behind all of this is best explained here: https://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx

Suficit to say that some of the issues you may have experienced with large projects will relate to this issue. I have had a bit of experience with large projects and have sent a number of those projects overseas to manufactures so they can see first hand what is happening.

The memory switch only works for the new versions of AFX, PremPro etc and not with the older apps.

Hope this helps.

Paul

[Paul King]

Better still get Particle Illusion which is the particle system in Combustion, except PI runs in real time outside of Combustion and has AFX plugs.

Paul

[Paul King]

Hi Ken

Premiere is compiled for the 3Gb RAM switch. You will never see 4GB but you will get 3GB.

Thanks

Paul

[Paul King]

I agree about missing the home key taking you to the head of the clip. I too used it for setting keyframes. At least the other way you had a choice to deselect all clips and then hit the home key.

So what Premiere needs is a set of edit preferences (like AVID) that tells it how the user would like it to behaive for specific commands, like the home key.

Other would be how to behaive when doing an audio automation mix – clip or track, where to save titles and whther to use project embeded ones or externally saved versions and whether to offer speed or duration change for Crtl R.

Switches would fix everything because users could make Premiere behaive how they want it to.

Thanks

Paul

[Paul King]

Are we talking about editing the video and leaving the audio where it is?
So we are making a change to the interview and overlay vision and not touching the interview audio?

A’lt’ key – edit video or audio only. Works with all the tools and video and audio stay in sync.

Paul

[Paul King]

Hi Tim

I am a bit disturbed you say you haven’t heard of this before. I would have thought you would have seen it as a forum topic somewhere we cant talk about.

I am with Shane on this one – it’s broken.

In 6.5 the automation mix affected clip keyframes, not track keyframes.
What poissible reason would you want to record a volume mix on a track?
As Shane says if you alter the timeline the whole mix is out the window so you have to do the whole thing again.

Nesting timelines makes no sense and defeats the purpose of finishing audio in an NLE.

I’m not having a go at anyone but this is clearly wrong. I do understand that there are different workflows, but again, why would you record mixer changes to the track and not the clip? Like 6.5?

Thanks

Paul

[Paul King]

Hi Denzel

The only rule is playback without FX. If your disk system can handle it then you can play it back with little or no FX.

However you will be lucky to find a hard drive subsystem that can deliver more than two streams of HD with audio and graphics (370MB/sec).

The Axio is worth while looking at because it uses a software CODEC, even though it’s a hardware solution. Because it’s software it’s adaptable and upgradable. I don’t think it’s fair to compare and Axio with a Decklink as the Decklink is little more than a frame buffer whereas the Axio is a video engine for Premiere Pro.

I have used the Axio and found it to be the multi-steam solution that is missing from the market today – it really fills the gap between AVID and the frame buffers.

Do yourself a favour and get a test drive.

Paul