I do this quite a lot and it 'rasterises' the file during import before I can edit it.
The thing I don't get is the amount of disk space usage and time it takes to rasterise that accompanies this action.
Sometimes a huge PDF (hundreds of megs) will rasterise in 10 seconds and be ready to edit straight away.
Sometimes the PDF may only be a few hundred KB and take a few minutes, or sometimes only a few megs big and take tens of minutes.
Is it to do with the complexity of the PDF or layers? I'm not familiar with the underlying structure of PDFs so this just made me curious, that's all.
Also, what I don't really get is how when I import a PDF that's only a couple of hundred KB, it can use up to a gig of scratch disk space, I can see this because I see my c: remaining space deplete after each consecutive file that I open. What causes this huge usuage, is it normal?
Anyone got any ideas?
The thing I don't get is the amount of disk space usage and time it takes to rasterise that accompanies this action.
Sometimes a huge PDF (hundreds of megs) will rasterise in 10 seconds and be ready to edit straight away.
Sometimes the PDF may only be a few hundred KB and take a few minutes, or sometimes only a few megs big and take tens of minutes.
Is it to do with the complexity of the PDF or layers? I'm not familiar with the underlying structure of PDFs so this just made me curious, that's all.
Also, what I don't really get is how when I import a PDF that's only a couple of hundred KB, it can use up to a gig of scratch disk space, I can see this because I see my c: remaining space deplete after each consecutive file that I open. What causes this huge usuage, is it normal?
Anyone got any ideas?
