memory in adobe

[Tim Kolb]

[Brian Louis] ”
Premiere 7 is still sold by people
https://www.websoft.ws/P33/Digital_Video/Premiere_7_Pro_XP.html“

Those would be thinly disguised pirates…not “people”…and certainly not Adobe.

TimK,
Director, Consultant
Kolb Productions,

[Chris Knight]

I used to get the “Memory is low” every time I opened the Titler in CS3 (XP 32-bit, 3GB of RAM). The Task Manager would conflict with that information (there was plenty of RAM available), but it didn’t seem to hinder performance. CS4 in W7x64 with 12GB of RAM does not have this problem (my AJA Xena/Kona, on the other hand, needs a good smack).

[Pushpanatha De silva]

Hi Tim,

Someone here mentioned that u have produced some training DVDs for APProCS4. I would like to know where they available to purchase and the prices?? Thx.

Pushpa
Brisbane
Australia

[Andy Prada]

I think a lot depends on the project being employed as to whether memory is a bugbear or simply not an issue. I use a Core i7 950 with 12Gb RAM and a Decklink card.(Win7 64bit)

I do a lot of uncompressed work with chromakey and Boris BCC6 effects – storage isn’t a problem and this is the most efficient workstream for me. On these and DV projects I sometime get memory issues but they tend to be on more complex projects where other assets are mixed on the timeline – stills, WMVs etc. (DV is, of course, highly compressed but in essence an efficient stream.)

HDV on the other hand gives me all kinds of issues. MPEG is hugely processor hungry but also memory too. Just watch how long it takes to load files at the startup. I’ve recently been working on an HDV project for a client where the amount of footage keeps growing and growing. It’s got to the stage that CS4 simply hangs for ages quite regularly even though processor and memory take seem quite within W7 64bit tolerances. Pro itself shows almost 2Gb memory taken and Importer processor nearly 1Gb. It grinds to a halt, plays erratically and eventually exports to AME if I schedule a meal break in.

Re-booting does help but not much. But why should I HAVE to re-boot? The answer was to split the project and work with a smaller input of data. Hey presto memory problems disappear.

Now what does that tell us?

Well, for a start it tells us a lot about the way CS4 handles memory which is not optimal to say the least. Having to split the core processes of CS4 into various importer functions and coordination servers – photoshop etc seems to me to be a complete mess and no one can convince me otherwise. I can appreciate that it seems, on the surface, to facilitate better the linking of Adobe’s various other applications “seemlessly”. Mmm, but not at the expense of the core product surely?

Also, the fact that CS4 is only optimised for 64bit also suggests that Adobe is filling a hole here before the introduction of CS5 – hopefully a radically new architecture. (Hopefully)

The reason I use Premiere in the first place (I also use Avid, FCP and Liquid professionally too) is because it’s got the best intuitive interface and the best potential architecture. It just feels right.

But if I had a wishlist for 5 it would simply be based on Microsoft’s recent conversion on the road to Damascus re Windows 7 – keep it simple stupid! I want Premiere to do what it says on the tin VERY WELL without compromise or the need to link elsewhere.

Oh and by the way (personal whinge here!) – RS442 capture over time-code breaks is a lot more useful for real editors than a garbled speech recognition facility that takes more time to edit than transcribing from scratch.

[Tim Kolb]

Hi Pushpa,

I missed this message in the thread…sorry. A quick Google of my name and the software package should get you lots of info…

TimK,
Director, Consultant
Kolb Productions,