Hello,

I have this nagging question about working on high res images with DS. What should I do to be able to pan and zoom onto large graphics just like AFX without having cropped out images upon zoom out. I am importing images in their original size. Thanks.

Baffled,

The trick is NOT to import these files but instead to right click on these sources and select Link.  No media is created on the video storage but you can then load these clips (identified by a red underscore on the clip's icon) on the timeline, add a DVE and scale and pan and scan to your liking.  The media will be real-time after you process the result as a playable cache. 

Consult the Online Help for further operational details.

Hi!

You can link them, not capture (drag from windows folder + mouse right button) You must see menu with option: Capture settings, capture, link and etc. Choose "link". Now place clip on timeline, choose duration, add DVE for example...

Voila

Second option (usually I use that): import image in paint module. Now freedom is yours!

I like this method, in effect tree is so great :-)))

HAH, Mr. Labrosse! You are so fast! In the same time I write response

Some things to take into consideration when it comes to "just"
linking an image versus importing images into a "Graphics" effect.

The downside when importing an image or a bunch of images into
"graphics" is that the sequence filesize may rize rapidly, or course
depending on how many files there are and how large they are.
But nevertheless an image imported into Graphics will increase
sequence filesize.

And I think that multiple copies of an identical Graphics effect will
increase the sequence filesize accordingly. Can you perhaps verify
that Mr. Labrosse?

So what's the big deal if the sequence filesize increases? Well, when
you reach sequence filesizes of 100-1000MB, loading and saving a 
sequence (i.e timeline)  become painfully slow. You might end up
waiting several minutes while doing the occasional save. And that
will probably keep you from saving as often as you want. And finally
you end up with not having saved at all when (not IF) the machine
decides to crash. Ideal scenario isn't it.

The upside is that by importing images into Graphics you can
build Presets that holds all the image-material that you want
a specific Preset to contain. So you can easily distribute "Presets"
to other machines on the network, and even send complete
Presets by mail. And since the imagery is in the project on the
DS project-disk any renders probably are as fast as they can be.

The render issue could probably something to consider when
dealing with linking files and specifically where to link from.
Putting linked files on a slow network storage will inevitable
decrease rendering and screen update performance.
But sequence filesize will be kept low.

...and so will loading and saving times.

So if I have to choose one or the other (which I of course won't
have to) it would be linking.

//mike

Exelent explanation!

Good work!

So, all that M-Edit write out is important if your work consist a lot a stills.

Documentary film for example. I'm afraid to use network drive for linked file.

In every case I copy them on local drive.

btw, for every project I make separate folder for source file (including all music, stills, text notes from producers, fonts and etc. & etc.) It's easy for me to archive and save my life

Personaly I use import in Graphics node for logos (sponsors and etc.).

In this way it's easy to manage and save how they look every time.

Respect to you M-Edit!

Just did a test to confirm the theory on how importing images
into the Graphcis module affects sequence filesize.

Linked a 4MB JPG-image and put it as a 5sec clip on the timeline.
Sequence filesize = 79kB

Copied the clip so there where 10 5sec instances of it on the timeline.
Sequence filesize = 134kB

Took the same 4MB image an imported into Graphics and put it
as a 5sec "Graphics on black" clip on the timeline.
Sequence filesize = 22MB

And then copied so there where 10 5sec "Graphics on black" clips
on the timelinte.
Sequence filesize = 220MB

So there you have it.

But as lordoff2 says it's great to import logos with alpha etc. into the
Graphics module cause it's easy to rearrange and reposition objects
in there. So I use that a lot too, especially on promo packhots and
the likes, but seldom when it comes to large graphics that's you're
going to pan and zoom. For example when roaming around in hirez
maps then you're better linking and using the DVE.

Finally, one thing to remember when importing images into
"Graphics" is that it's the "Pixel ratio"-setting at the bottom of the
"Capture Settings"-window that also determines how the imported
images will be treated. Most of the time, when working with PAL or
NTSC SD-projects this should be set to "Computer Graphics (1.0)",
i.e. square pixels, cause almost all graphics material you will recieve
is "square pixel'ed".

//mike

Forgot one thing that's also rather important.

I then deleted 9 of the 10 "Graphics on black" clips on the
timeline and re-saved and then you think you would end up
with a sequence filesize of 22MB again. But no, you end up
with a filesize of 198MB, so it's like 220-22=198MB instead.
The other way round you might say? So it's like memory isn't
released the right way when you delete the clip instances.

But if you save with a new name you finally end up with
a sequence filesize of 22MB again.

So if you're using a lot of imported images and you know
you deleted a lot of the stuff and your sequence still feels
sluggish it could be a good idea to save to a new sequence
name. At least just to have tried it.

//mike

Mike, thank you for useful tests!

I have only one question: In "Graphics on black" clips, on Property tab, "Output Frame Size"

checked or not? I'm afraid that is not switch on by default...

Sorry, I' m not behind DS right now to verify this

I've tried both and it surely doesn't make any difference
when it comes to sequence size, but the strange thing is
that it didn't make any substantial impact on rendering
times either.

So maybe I'm doing something wrong here, but the image
I've used is a 3172x1760 pixel image that I zoom from
100% to 20% for a duration of 5sec in the Graphics module.

I expected a longer render time when I un-checked
"Output Frame size", but it was about the same, say
around 5 sec.

//mike

M-Edit:

I then deleted 9 of the 10 "Graphics on black" clips on the
timeline and re-saved and then you think you would end up
with a sequence filesize of 22MB again. But no, you end up
with a filesize of 198MB, so it's like 220-22=198MB instead.
The other way round you might say? So it's like memory isn't
released the right way when you delete the clip instances.

But if you save with a new name you finally end up with
a sequence filesize of 22MB again.

Hi Mike,

You can't do what you did with any reliability as to the file size of your sequence without doing a "Save As" after every step.  The part that you're forgetting is the size of the Undo Stack which increases every time you perform an operation on the Timeline (this is also dependant upon your User Prefs for number of Undo levels).

If you want to make comparative size estimates you MUST do a Save As every time.

Regards,
Tone :)

Thanks, Tone, I guessed that there was something I had overlooked.

So from now on "Save as..." is going to save my ass.

//mike

This is what I explained in another response.

Save (and autosave) always saves sequence content incrementally.  So the changes that you make will NOT remove the previous history.  yes it will substract information that is not on the timeline but it cannot remove what has been saved in previous incrementation.  All this data is kept in order to make this process a very fast save and to interrupt the editor the least possible amount of time.  That is why autosave usually flashes on screen if the autosave is set low (5 to 10 minutes) but can appear on screen for a longer time if the autosave is set at 1 hour or more.

Save As..., as Tony reports, do not care about what you did last week or yesterday.  It only reads the current timeline content and will write a sequence with this current data, hence the size might actually be much smaller if you indeed removed lots of "heavy" item in your final edit decision.

Knowledge is power!

Thanks, Mr. Labrosse, for straightening out
another of my misconceptions.

//mike

Today is not lost for my education!

I learn something new details about DS!

This process continue 7 years! I'm so happy with every new!

Thank you Mr.Labrosse!

Ho, I still learn something every day......