Re: Friday Flashback #239

[peter_b]

don’t call those vintage, you’ll wake up the dinosaurs! 

‘...back when I was starting 3D, computers had to be fed punched cards - 
rroooaarrr’
From: Stephen Blair 
Sent: Friday, September 04, 2015 8:21 PM
To: softimage@listproc.autodesk.com 
Subject: Friday Flashback #239

Vintage Softimage software CDs and docs, and some vintage SGI boxes

http://wp.me/powV4-3dX

Re: Last Friday's Flashback #238

[peter_b]

call me old-fashioned, but ‘more 3D in the comp’ was not really what I was 
after.

what good is a 3D environment without proper modelling, animation, simulation 
tools? Adding a decent renderer to the comp raises more problems than it solves 
IMO. quick placement of some imageplanes or 3D objects in 3D sure, but 
‘integrating’ those properly into backplate or 3D elements can become so 
involved (sometimes unexpectedly) that the broad toolset of a full 3D software 
becomes a necessity.
Also, the time needed to do the job becomes incompatible with the fast workflow 
in an editing environment (and compositing to some degree).

however, timing footage is usually a weak point, both in 3D and comp software – 
and there DS really shined - it’s ‘timeline with effects’ – and in good 
Softimage tradition, nonlinear & non destructive. I found DS and XSI so 
complimentary – without too much overlap. If you will, the overlap was 
compositing, which to both was a natural companion. But in it’s respective core 
disciplines editing and 3D, there was little confusion – and that was perfect 
IMO. It just needed more links/bridges/interop between the two.

Anyways – what good ruminating on how the synergy between these two unique and 
sadly discontinued softwares could have been? 
And how precisely that synergy does not exist elsewhere atm – whatever nice 
things Foundry and others may be doing.

Perhaps it’s just my pipe dreams, with XSI and DS independently becoming my 
preferred softwares (not for lack of exposure to others, some of which I also 
had a soft spot for), and naturally whishing for them to play together ever 
more.



From: Jason S 
Sent: Saturday, September 05, 2015 2:25 AM
To: softimage@listproc.autodesk.com 
Subject: Re: Last Friday's Flashback #238

Erratum : didn't differentiate things that were later developped & introduced, 
to things that were wished-for.

Actually, good 3D in DS was among the few things that users were wishing for DS 
to make it current again
(had it been more seriously  developped passed V4 (2002) apart for things 
*introduced in later versions* like new hardware support, still quite decent 
GPU Acelleration, MotionFlow Time Stretching & lots of compatibity and interop 
endeavors with MC) 

cheers,

On 09/04/15 19:53, Jason S wrote:

  About last Friday's Flashback, 

On 08/28/15 16:40, pete...@skynet.be wrote:

[...]

  I guess the industry as a whole didn’t need that integrated Digital 
Studio, and few really used DS and XSI in tandem 

- but I feel we are all the poorer without it.

Sure, there’s some interesting convergence happening between 3D and 
comp these days – but how I miss that particular Softimage spin on it. 


  Actually, good 3D in DS was among the few things that users were wishing for 
DS to make it current again
  (had it been more seriously  developped passed V4 (2002) apart for things 
like new hardware support, still quite decent GPU Acelleration, MotionFlow Time 
Stretching & lots of compatibity and interop endeavors with MC) 

  few wished-for things which included:

  * introduction of new file based camera formats,  
  or bringing-in arbitrary common media types without transcoding or conforming 
to DS's native format
  ( That single and relatively simple point would have addressed the bulk of 
what users might have been pressing most upon, despite introduction of -some- 
new formats.)

  * keying tools coming closer Smoke/Flame counterparts 

  *** and ironically, given where it's coming from and what were the original 
plans-- a more complete 3D environment compared to these same packages.

  But it's 3D was at least more than good enough for mapping (rez independant) 
cutout/blended clips on cards in a 3D environment with artifact free results, 
and creating or animating hierarchies of elements with relative and manipulable 
axies.

  

@schnittman @editblog @patInhofer Favorite edit system I ever worked on. 
The death nail was it's inability to work w/ file based cameras

— Nathan Downing (@nathandowning) August 6, 2013

  In the very niche market of high-end finishing workstations (much more niche 
than it's original sister 3D flagship), DS was considered as the very top of 
the line of Avid's offerings 
  (despite relatively little significant changes over time, it's near abscence 
in marketing campaings, and noticably living in the shadow of MediaComposer 
itself very much coming-up with support for things like file based formats)

  While as Avid's only truly resolution independent high-end solution (only one 
that could do 4k (+) or even slightly over HD 2k film), that also had node 
based processing trees on timeline clips or entire timelines, and other things, 
  it was typically compared to Smoke/Flame stations rather than other Avid 
products, but despite increasing comparative drawbacks compared to something 
like Flame as DS was in a 'left behind' state, it was also considered 

Re: Softimage with Windows10

[Olivier Jeannel]

We're not dead yet !

On Sat, Sep 5, 2015 at 7:37 AM, Daniel Kim  wrote:

> Hey Mirko
>
> Good info.
> Thanks :)
>
>
> 
>
>
> On Sat, Sep 5, 2015 at 12:57 AM, Mirko Jankovic  > wrote:
>
>> Works perfectly fine here
>>
>> On Sat, Sep 5, 2015 at 12:30 AM, Daniel Kim 
>> wrote:
>>
>>> Has anyone tried if Softimage 2015 is compatible with Windows10?
>>> I'm kinda scared to upgrade Windows.
>>> Let me know if anyone has already upgraded it.
>>>
>>> Thanks
>>>
>>> 
>>>
>>>
>>
>

Re: Random expression for "noise" on Local.posy - please help

[Olivier Jeannel]

Not sure exactly how, but you might need to add another SRT to Matrix or a
Multiply Vector by Matrix to take in account the master parent.
Worth a try.

On Fri, Sep 4, 2015 at 6:38 PM, Pierre Schiller <
activemotionpictu...@gmail.com> wrote:

> Thank you for sharing the setup on ICE.
> What I got is: a camera root parented to a null, that null will be the one
> to recieve the noise.
> Over that null, there´s a master parent which is already animated.
> I´ll try this setup and see how it goes.
>
> Regards.
>
> On Thu, Sep 3, 2015 at 4:05 PM, Olivier Jeannel 
> wrote:
>
>> Like this :[image: Inline image 1]
>>
>> On Thu, Sep 3, 2015 at 8:01 PM, Olivier Jeannel 
>> wrote:
>>
>>> Multiply by the global Kine of the Parent, no ?
>>>
>>> On Thu, Sep 3, 2015 at 7:38 PM, Pierre Schiller <
>>> activemotionpictu...@gmail.com> wrote:
>>>
 not at all. I want to do it on ICE. I checked out this one:

 http://caffeineabuse.blogspot.com/2012/01/turbulize-position-of-locator-with-ice.html

 But the setup only worked with global pos. not local. I´d like to give
 my null a local property since it´s parented to another null
 which already carries animation.



 On Thu, Sep 3, 2015 at 1:36 AM, Olivier Jeannel  wrote:

> Any reason for not doing it with ice ?
>
> On Thu, Sep 3, 2015 at 12:54 AM, Pierre Schiller <
> activemotionpictu...@gmail.com> wrote:
>
>> Thank you, sure will go write the expression now :)
>> This is amazing for camera tilts :)
>>
>> Cheers.
>>
>> On Wed, Sep 2, 2015 at 4:25 PM, Grahame Fuller <
>> grahame.ful...@autodesk.com> wrote:
>>
>>> >ahem< That should be “noise” field…
>>>
>>> From: softimage-boun...@listproc.autodesk.com [mailto:
>>> softimage-boun...@listproc.autodesk.com] On Behalf Of Grahame Fuller
>>> Sent: Wednesday, September 02, 2015 5:24 PM
>>> To: softimage@listproc.autodesk.com
>>> Subject: RE: Random expression for "noise" on Local.posy - please
>>> help
>>>
>>> Try this:
>>>
>>> 0.02*noise(fc, 15, 8)+0.042
>>>
>>> The three arguments to the noise function are (x,y,z) coordinates in
>>> a smoothly varying nose field, so at least one of them needs to be
>>> time-dependent (e.g. fc or t) so that you take a walk through the noise.
>>> Noise returns a value between 0 and 1, so you need to scale and offset 
>>> it
>>> to fit your desired range.
>>>
>>> gray
>>>
>>> From: softimage-boun...@listproc.autodesk.com>> softimage-boun...@listproc.autodesk.com> [mailto:
>>> softimage-boun...@listproc.autodesk.com] On Behalf Of Pierre
>>> Schiller
>>> Sent: Wednesday, September 02, 2015 4:35 PM
>>> To: softimage@listproc.autodesk.com>> softimage@listproc.autodesk.com>
>>> Subject: Random expression for "noise" on Local.posy - please help
>>>
>>> Hello group. I am trying to make a Y value have a noise driven
>>> parameter directly in it´s local.posy
>>> I found out noise can do the job on the expression editor.
>>>
>>> But it only generates 1 value on 1 frame. I tried FC and end up on
>>> an error:
>>> FC noise( 15, 8, 5 ).
>>>
>>> How is the expression to be written? I want it to vary (randomly
>>> between a 0.042 and 0.062) each frame.
>>>
>>> Thanks.
>>> David R.
>>> --
>>> Portfolio 2013
>>> Cinema & TV production
>>> Video Reel
>>>
>>
>>
>>
>> --
>> Portfolio 2013 
>> Cinema & TV production
>> Video Reel 
>>
>
>


 --
 Portfolio 2013 
 Cinema & TV production
 Video Reel 

>>>
>>>
>>
>
>
> --
> Portfolio 2013 
> Cinema & TV production
> Video Reel 
>