I forget, which is the “new” one that we should be using.
Import.
1 Like
How have I gotten this far without noticing there are two of them…?
1 Like
Cuz…
You saying I could have ranked higher in my efforts to finally be not the Assistant to, but THE Regional Renderdome Champion: Northeast Region had I known that Read File exists?
So much effort, wasted due to my ignorance. Oh woe is me, an Assistant To, forever.
2 Likes
Save the self flagellation. Read File is over.
1 Like
Unpopular opinion, a fully functioning readnode that doesn’t rely on wiretap and that just reads sequences from a file system without any hootenanny like Nuke would be rad.
4 Likes
One of the largest differences between the two is with a read node, Flame doesn’t “know” about the clip as it’s not added to any your batch group reels. With the import node, it is. It acts like any other imported clip…thus it’ll be archived.
Back in the day we used the read node for CG as we cached everything on archive (if it wasn’t cached alraedy) and didn’t want to include those renders as we had another script that would grab the read files and keep a sideline archive with the goal of keeping archives smaller.
When import is soft linked in a batch and media is offline, you can’t see where the media was.
Even though read nodes can’t be seen in archives, at least you can see the address of the clip even if media offline.
I suppose what I’m advocating is a combination of the two with the best of both worlds and saying Thankyou. I’m grateful. So much gratitude.
Yes, A great fix of that issue of read node. I didn’t use it, just by that reason. Import node is a good feature.
Can’t you see it in these locations?
- The Metadata tab in the Extended submenu of the Clip node
- The Information box (Alt-Click) in the Media Panel
- At the bottom of an expanded segment in the Batch Timing view
- At the bottom of an expanded segment in the Timeline
Thank you for calling me out @fredwarren
I did a test and my comments are out of date.
Let me revise my comment - I wish we could make it easier to get the address of the render of a clip that is unlinked when restoring from an archive to make it easier to restore the missing data.
If the media is missing it is not possible to use the python script reveal clip and one must read and copy or take a photo and OCR the text.
Having it more open like in nuke where you can easily copy the address is much more functional.
1 Like
I think that’s my main issue with the existing read node—it’s now missing the ability to just see and edit the path at the root page of it’s settings.
It used to be there and got removed at some point. Double clicking to reveal the path or checking the metadata doesn’t give the same instant feedback nor does it give a quick way to copy or edit the path… a path selection widget which displays the path and filename followed by a load button would be soooo much more helpful.
I totally understand the desire to use import as opposed to a read but I think they both have their places.