Page 1 of 1
[FEATURES REQUEST]

Posted:
Sat Sep 12, 2015 3:21 pm
by phantom-studio
Hi all,
a few features request for upcoming Fusion8 :
-gamma and exposure sliders for viewer, without to have to go to the lut menu
-pipes in flow for expressions with a specific color (differents of classic pipes)
-expressions in filename field of loaders and savers
-per saver render range in the same .comp file
-3d navigation from most common 3D app (maya, max, houdini...)
-in the console script , let us have more than one line to enter code.
Thanks.
Re: [FEATURES REQUEST]

Posted:
Tue Dec 29, 2015 3:27 am
by Friedrich Schnittker
3d navigation from most common 3D app (maya, max, houdini...)
I very much agree!
I work in Maya, Houdini and Nuke and the Fusion controls are confusing. An option to change these to something else would be really appreciated.
cheers
Re: [FEATURES REQUEST]

Posted:
Thu Jan 07, 2016 3:13 pm
by Friedrich Schnittker
Actually:
For me, even though Fusion looks like it got everything I need, I can't really consider it until the controls are adjustable in a way so that I can work with multiple applications at the same time.
And to be honest, I think this is an issue for a lot of potential customers.
Re: [FEATURES REQUEST]

Posted:
Thu Jan 07, 2016 5:35 pm
by Tim McGilly
Also it would be nice if they added:
A 3d tracker
A way to import materials and Model with pre-made materials.
Re: [FEATURES REQUEST]

Posted:
Thu Jan 07, 2016 9:34 pm
by Chad Capeland
Tim McGilly wrote:Also it would be nice if they added:
A way to import materials and Model with pre-made materials.
Import FBX already does this. All the materials / maps are loaded and connected to the correct meshes.
Of course if you have vertex data needed by the material that Fusion doesn't support, then it's not going to work. While Fusion itself can support things like vertex color, the FBX loader doesn't.
Re: [FEATURES REQUEST]

Posted:
Tue Jan 12, 2016 7:10 am
by Massimo Moneta
phantom-studio wrote:Hi all,
a few features request for upcoming Fusion8 :
-gamma and exposure sliders for viewer, without to have to go to the lut menu
-pipes in flow for expressions with a specific color (differents of classic pipes)
-expressions in filename field of loaders and savers
-per saver render range in the same .comp file
-3d navigation from most common 3D app (maya, max, houdini...)
-in the console script , let us have more than one line to enter code.
Thanks.
+1
Re: [FEATURES REQUEST]

Posted:
Tue Jan 12, 2016 10:40 am
by michael vorberg
phantom-studio wrote:H
-per saver render range in the same .comp file
you can already do that: you can animate the blend slider in the saver to the range you want it to be active.
and there is already a nice script for this:
http://www.steakunderwater.com/viewtopic.php?f=6&t=278
Re: [FEATURES REQUEST]

Posted:
Tue Jan 12, 2016 5:39 pm
by Joël Gibbs
michael vorberg wrote:phantom-studio wrote:H
-per saver render range in the same .comp file
you can already do that: you can animate the blend slider in the saver to the range you want it to be active.
and there is already a nice script for this:
http://www.steakunderwater.com/viewtopic.php?f=6&t=278
The script is great, and the blend slider works, but you have to admit that a render range input would be nice. By default on the work area set in timeline, or a custom range input. Seems like that wouldn't be hard to implement or go against Fusion's way of doing things.
Re: [FEATURES REQUEST]

Posted:
Tue Jan 12, 2016 7:58 pm
by Chad Capeland
It should work with the ranges in the timeline, though, right?
Re: [FEATURES REQUEST]

Posted:
Wed Jan 13, 2016 5:30 pm
by Shawn Astrom
Customizable 3D navigation is a must for me. Would be amazing if I could match it to Cinema 4D's navigation.
Amazing job on the new UI!
Getting ready to pull the trigger on Fusion Studio...
Thanks for the hard work!
- Shawn
Re: [FEATURES REQUEST]

Posted:
Fri Jan 15, 2016 10:32 am
by michael vorberg
i would vote for:
start each (lua/python) script as a own thread or at least each user dialog, so i can have many customs panels and scripts open and use them all
Re: [FEATURES REQUEST]

Posted:
Fri Jan 15, 2016 4:25 pm
by Chad Capeland
michael vorberg wrote:i would vote for:
start each (lua/python) script as a own thread or at least each user dialog, so i can have many customs panels and scripts open and use them all
Can't you already do that? If you launch the thread outside of Fusion, but connect to the active Fusion instance, wouldn't that do it? I seem to remember Daniel showing an example of that to make non-modal dialog boxes.
Re: [FEATURES REQUEST]

Posted:
Fri Jan 15, 2016 7:32 pm
by michael vorberg
Sure you can do that with studio, but then you can't attach a keyboard shortcut or a link in the menu
I think you can also launch a pyqt dialog as separate thread but I didn't try it yet
Re: [FEATURES REQUEST]

Posted:
Fri Jan 15, 2016 10:41 pm
by Chad Capeland
Oh, you might be right about studio, but hotkeys and menus should be fine, you would just launch the script externally, like with executebg(), right?
Re: [FEATURES REQUEST]

Posted:
Fri Feb 26, 2016 8:06 pm
by Dmitry Abdeev
Hi there
I work as broadcast designer mostly in Cinema 4D and use After Effects for compositing.
There are some features that would be fantastic to have in Fusion to replace After Effects:
-customizable viewport navigation
-light wrap node
-Frischluft-like adjustments in Depth Blur Node
-I think it would be wonderful to have an Optical Flares-like system in Studio version, I mean more subtle adjustments
-import of Cinema 4D lens distortion data
-3D and planar tracking
Thank you for attention
Re: [FEATURES REQUEST]

Posted:
Tue Mar 08, 2016 12:20 am
by Mike Bozulich
Yes to all of these please. But I don't think we'll see any of it until Fusion 9. F8 seems to be a interface tweak and the addition of the Mac version. Have there been any new features added to Fusion 8 over 7?
Re: [FEATURES REQUEST]

Posted:
Thu Jul 07, 2016 10:06 pm
by Friedrich Schnittker
Any news on this:
-3d navigation from most common 3D app (maya, max, houdini...) ?
Fusion 9 maybe?
Re: [FEATURES REQUEST]

Posted:
Fri Jul 08, 2016 3:28 am
by Michael_Smith
I would love to see a middle mouse scrub on all numerical input boxes. I would like to be able to scrub hue, sat value in the color chooser. Also would be helpful to have shift snapping of the values; say snap to .01 or maybe 1 degree in angle entries.
Re: [FEATURES REQUEST]

Posted:
Fri Jul 08, 2016 10:07 pm
by Eugene Afanasiev
1)I hope to see the proper working description of ACES (and for ACEScc as well, covering all the right working methods to do just that) workflow between Fusion and DaVinci.
Also willing to see support for BMC DNG footage(so the image appears the same as viewed in DaVinci and with the same raw settings, and backwards in the DaVinci).
2)Keyframes and masks and trackers and color curves exchange between the two. Name the rest...
And the rest is... If only it could use the same Optimized Media that was generated previously in DaVinci... But that's too much I guess, at least this as a request:
3)DaVinci's fast and robust Optimized Media - like workflow for Fusion (What do I mean: select all the footage to be optimized, click one button - Bam - OM is done! Switching between the source and OM with one button - no problem! (The current Cache to Disk and Proxy option in the Loader is way-way away from the OM in terms of speed and usability))
Re: [FEATURES REQUEST]

Posted:
Sun Jul 10, 2016 11:25 am
by michael vorberg
Eugene Afanasiev wrote:3)DaVinci's fast and robust Optimized Media - like workflow for Fusion (What do I mean: select all the footage to be optimized, click one button - Bam - OM is done! Switching between the source and OM with one button - no problem! (The current Cache to Disk and Proxy option in the Loader is way-way away from the OM in terms of speed and usability))
most of this can be done right now:
create a script that adds a saver to each selected node, fill in the path and settings for the new media, put the path from the new media in the proxy field of the orignial loader, render the new media, delete the new saver nodes and your done.
now switching to proxy mode uses the new created (compressed, optimizied) media and without proxy the original files.
only thing that takes some time is rendering the new media files.
Re: [FEATURES REQUEST]

Posted:
Mon Jul 11, 2016 8:51 am
by Eugene Afanasiev
Yeah, I've heard it a hundred times on Fusion forums, but one missing link though: how learn and how much time is it to learn to be able to write scripts like that in no time so it won't be bothering you as writing a script like that would cost you less time than doing everything by hand.
To me writing a single string expressions takes lots of time while I'm debugging for errors. So instead of already compositing for a half an hour I would be developing a script of an absent functionality within a software that could only help me start doing my actual job oif compositing, I'm more into scripts that could actually get better results with compositing itself, for ex doing some complex math for me.
Re: [FEATURES REQUEST]

Posted:
Mon Jul 11, 2016 9:28 am
by Achim Dietze
Eugene Afanasiev wrote:Yeah, I've heard it a hundred times on Fusion forums, but one missing link though: how learn and how much time is it to learn to be able to write scripts like that in no time so it won't be bothering you as writing a script like that would cost you less time than doing everything by hand.
To me writing a single string expressions takes lots of time while I'm debugging for errors.
Exactly. Clients don't pay us for creating tools but for
using them

Anyway, apart from more UI convenience I would like to see better alembic data support (not just meshes, but also cameras and transform data) and being able to retime alembic animations.
And it needs much easier handling of LUT and Colorspaces.
Re: [FEATURES REQUEST]

Posted:
Mon Jul 11, 2016 5:29 pm
by Joël Gibbs
Anyway, apart from more UI convenience I would like to see better alembic data support (not just meshes, but also cameras and transform data) and being able to retime alembic animations.
And it needs much easier handling of LUT and Colorspaces.
You can currently import cameras with their animation through alembic ( at least in 7.7..not sure about 8, but I don't see why you couldn't). As far as retiming it's animation, I'm not quite sure. There used to be a time3D fuse out there. I wonder if it would work on alembic caches...
Re: [FEATURES REQUEST]

Posted:
Mon Jul 11, 2016 6:57 pm
by Chad Capeland
Joël Gibbs wrote:I wonder if it would work on alembic caches...
Does.
Re: [FEATURES REQUEST]

Posted:
Tue Jul 12, 2016 10:06 am
by Achim Dietze
Chad Capeland wrote:Joël Gibbs wrote:I wonder if it would work on alembic caches...
Does.
Supercool, thanks.
Re: [FEATURES REQUEST]

Posted:
Tue Jul 12, 2016 10:09 am
by Achim Dietze
Joël Gibbs wrote:Anyway, apart from more UI convenience I would like to see better alembic data support (not just meshes, but also cameras and transform data) and being able to retime alembic animations.
And it needs much easier handling of LUT and Colorspaces.
You can currently import cameras with their animation through alembic ( at least in 7.7..not sure about 8, but I don't see why you couldn't). As far as retiming it's animation, I'm not quite sure. There used to be a time3D fuse out there. I wonder if it would work on alembic caches...
When I tried to import cameras it only gave me ma, aes and lws format as option.
Re: [FEATURES REQUEST]

Posted:
Tue Jul 12, 2016 2:45 pm
by Joël Gibbs
You have to import it through the Alembic importer, not the camera. It will create a camera node with it's transforms for you.