my X9 mishaps today...

[asik1]

I'm on a deadline for few ~2min segments, with up to 15 jpg's with motions each on 4 overlays.
First I had few "out of memory" - never had this before. So I resized the 20Mpix jpg's to normal 3-4Mpix and solve that.
Second X9 stopped render at one point but did not crash, it just "felt" like it's tired.... So I had to render that segment in two parts, till now can't tell whats wrong .

Average render was ~10min for each segment.

[asik1]

Do you care to do a simple test?
on main track place a background HD image from samples
on overlays 1-2-3 place large 12Mpix (or more) from your photos.
Apply NB PIP to each with some movement ,
so the final layout will have 3 moving PIP's over the background.
Render to MP4.
My X9 crashes on such setup with NB PIP dll error report, unless I replace the jpgs with ~2-3Mpix ones.

If all well will you try to load overlay 4-5-6... and see if your NB PIP crashes at all?
Thank you.

[lata]

Hi Asik

No problems

I tried with 12mb and 18mb images

Can you attach your VSP file, I can then replace your images, at least I will be using the same P in P settings.

[asik1]

As I was on XP this morning I tried 5 15Mpix NB-PIP's with X8.0 and it rendered fine. but as such test is isolated from my original long project, further test is needed.
I'll do so on X9 later today.

And just as side note, I don't understand why people shoot those unnecessary high Mpix images. Not many of them will be placed on Piccadilly sq.

[bitman]

As I was on XP this morning I tried 5 15Mpix NB-PIP's with X8.0 and it rendered fine. but as such test is isolated from my original long project, further test is needed.
I'll do so on X9 later today.

And just as side note, I don't understand why people shoot those unnecessary high Mpix images. Not many of them will be placed on Piccadilly sq.

High mpix is useful for posters (but indeed, who does that), but mostly for cropping and zooming in.
With the digital zooming in you can overcome your lens reach a bit, without to much loss of quality, providing you limit your output format.

Then there is the output media itself:
A printer needs to use more pixels per inch to produce a high-quality image than your monitor... there you go.

[bitman]

Hi Asik

No problems

I tried with 12mb and 18mb images

Can you attach your VSP file, I can then replace your images, at least I will be using the same P in P settings.

You may have no problems because you have 64 bit and asik has 32 bit (looking at your profile).
With memory issues, (like running out of memory) you will have less issues with 64 bit OS, as it can address beyond 4GB memory, 32 bit OS can only address 4GB.
(in practice there is even less available free RAM for applications, maybe a little over 3GB, due to system reservations, etc ...).

[lata]

Hi

Whilst that may be true there is a big difference between a 12mb resolution image, to a 4 Gb memory limit.

Asik is also applying P-in-P and to test as near as possible I asked for his VSP so I can use P-in-P with same settings.

Although creating a Smart Package would be the best option.

[asik1]

Trevor, the exact PIP's has nothing to do with a crash as they all use the same DLL.
Retesting "just" the PIP's segment on my X9 did not re-crash , strange but that's it.
I delivered all work , the costumer is happy so I'm happy.
And surly he didn't notice that I swapped his 15Mpix photos with resized 3Mpix ones.
(Should I give him a discount?)