[Accountclosed]

Good question, short clip or not, and thanks to those who responded. As stated in an other thread, I’m learning and using blockers more and more, and such tips are great.

And, yeah, good music to get “in the zone” helps too, for using PI is kind of like a photonic neuro-surgery. Got to keep those good vibes in the OR 🙂

[Accountclosed]

That’s fine. Thanks for trying (10 hours in Vegas, well, I’ve got a handful more clocked – lol 🙂 One way or another, there will be some kind of solution or solutions. There is no way I am I going to give up on all the tlc poured into my “Wow, that’s really coming out nice!” PI files.

For that export issue aside, it’s funny how occasional seeming mistakes in particle tweaks can turn into new effects. Had just one mistake or discovery recently using something I’m starting to master: blockers!

The fun only increases the more one learns indeed.

[Accountclosed]

Thanks for the suggestions, although as far as alpha channel and remove black, that info was included in the bottom title part of the page where the actual exported PNG frame files were (“… with Alpha Channel/Mask & Black Removed”).

One can save and open these and see that it is so. I always export particles as shown (on black/no background image) for I need the transparency.

As far as what you said, “Although I’m not sure exactly what the problem is, or which images on that page you think are good and which are bad (…)”:

I put some time and effort into creating that page for this question with its provided visual and written info, but the short version is that:

— It seems (to me) that simply looking at the before and after (in-PI and in-Vegas) same resolution shots (100% 640×480) on black/no background, the deterioration of the details is very obvious. What shows up in Vegas is definitely degraded/flat compared to its pre-export in PI.

I will try the “preserve” color option and keep in mind what you said about its potential effect on particles, but it may already be activated in that project for both particles.

My system in tied up rendering something right now, so I can’t open up PI to double-check without it struggling. No point taking chances.

Whatever the case, I’ll experiment with and without the preserve and see what happens.

___________________________________

As to getting input from the Sony forum, I’ve already gotten some for they’ve viewed the same page and a slightly edited version of my opening post to you here at this board.

From the feedback I have gotten so far on this, it is also possible that Vegas Pro 8 does in fact have some new alpha channel and other stuff that may be useful in such cases.

But it’s too soon to tell, for the IBC conference where it will be formally unveiled is this weekend.

September seems to be an important month for media applications (i.e. PI is to be updated, too 🙂
.

[Accountclosed]

P.S.: I’ve also addes the actual PNG files for each of the two particles in the example to that page.
.

[Accountclosed]

“Well, since pI3 is just 8-bit per channel right now, this won’t really help much.”

— Makes sense, but from what I’ve seen in test 8-vs.-32 renders (with absolutely no color or other tweasks) off of a basic DV shot, there was some subtle but definite improvement. PI files may or may not get that lift.

My is guess is that the higher the PI file output rez, the better the chances of some improvement. Yet until when/if I upgrade to V-8 to test this for myself, it’s all just “Well, I hope that…” speculation.

“If the rendered output of pIllusion has banding, Vegas won’t get rid of that.”

— How to avoid and/or minimize banding — or which kinds of particles would be more prone to it? And, which type of exports — seems like .png may be less banding prone?

[Accountclosed]

Perhaps redundant adding the following since the reference page may already be known by some of you, but figured I’d so so anyway.

I stole and shortened what follows from one of my recent postings at the Creative Cow Particleillusion forum (I feel 32-bit float will help with PI files imported into Vegas also).
______________________________

From Vegas Pro 8:

32-bit Floating Point Video Processing

“Surpass traditional 10-bit standards with 32-bit floating point video processing. Take advantage of greater color range for more vivid colors, reduced gradient banding and posterization for smoother color transitions, linear light capability for optically correct compositing, and many other precision enhancements.”

………………………………………

The keyword is “processing” — and not output. Meaning that your project settings will determine the end result as rendered files, but while in the kitchen, you’ll get spicier work done 🙂

A Bit More on Higher Bit

For more in-depth understanding of higher bit process, see the article on Creative Cow about a competitor’s 32-bit float color processing (Adobe Premiere), and why it matters in overall editing.

A bit techie but supports what I see as a boon to PI + Vegas users since Vegas has now incorporated a similar engine.

High-bit Color Support in Adobe Premiere Pro 2.0

[Accountclosed]

BOARD ADMIN: Sorry about the repeat posts, tried to go back and edit and it just accumulated, feel free to delete all but first one.

[Accountclosed]

Ah-haa, so that’s what FrameServer does! 🙂 Thanks.

I had passed on FS back when I first got Vegas as I was scouring VASST and such for extra ditties. Definitely a space saving solution and more.

I’ll have it intstalled by the time you read this reply.

[Accountclosed]

Ah-haa, so that’s what FrameServer does! 🙂 Thanks.

I had passed on FS back when I first got Vegas as I was scouring VASST and such for extra ditties. Definitely a space saving solution and more.

I’ll have it intsalled by the time you read this reply.

[Accountclosed]

Ah-haa, so that’s what FrameServer does! 🙂 Thanks.

I had passed on FS back when I first got Vegas as I was scouring VASST and such for extra ditties. Definitely a space saving solution and more.

I’ll have it intsalled by the time you read this reply.
.