Forum Replies Created
-
Posts
-
@rfer79 25061 wrote:
Hi,
My company has both avid and final cut editors so xstoner might be better.
Thank you
What makes you think Xstoner is better in an Avid environment?
You can actually keep the P2 in native format if you like. Edit in FCP, export XML of timeline. Drag XML into tether, it will upload all associated media, QTs, aiff, etc… no matter what codec or resolution straight into StoneFS. You can then use the XML in Smoke to Re-Link to the media.
see a screencast of this here:
http://www.instinctualsoftware.com/Instinctual_Software/tether_xml.htmlAlan
@rfer79 25053 wrote:
Hi,
I’m soon going to start the online in smoke of a feature film shot with a Panasonic AG-HVX200. This camera records into P2 (storage devices) and these files were converted into ProRes 422 quicktimes and edited in final cut. I was wondering if anyone has an opinion on what is the best workflow to take the files and cut from final cut into smoke. I should also mention that this an effect heavy film and i’ll start working on the effects in smoke before picture lock so it would be ideal to find a way that would give some handles in online.
Thank you
there has recently been a large thread on smoke-news about this.
sell it on ebay.
shrink can crop the a given aspect ratio during the encode.
you could also create a preset using the quicktime size/crop tools.
all this directly from the stone.Alan
sapphire has one.
Dude, if someone is selling you a turnkey Flame 2007, it for sure is NOT legal.
The cheapest way to build your own though, would be a Linux machine. I got a Flame compatible one off ebay for $350. It has no video I/O, but hey, I am just developing sparks and stuff.@Clint Nitkiewicz Hernande 24278 wrote:
Hows it going, Iam in the market for a used flame system, I found a turnkey system for 12,000, which is not bad for flame 2007, the new linux boxes are just way out of the question though for me, I just stay at my facility to work on the 08 version.
Though I realize I could save a lot of money If I get a deal on the software and licenses, etc, by building my own box.
Are these requirements acurate I found. Let me know if this is true for the system requirements for the Irix Flame 2007.
The article says Flame 2007 requires;
– Dual processor Octane2
– V12 graphics
– 1GB RAMCan I possibly run Flame with the following setup instead?
– Octane 2 with single core processor
– V10 Graphics
– 2 GB RamHere is the link to the site where I got this from.
http://findarticles.com/p/articles/mi_m0EIN/is_2001_August_14/ai_77184207Iam not seeking maximum functionality and speed, just simple installation and basic compositing, keying at the moment, if crucial I would upgrade and just swap out the V10 for the V12 and add another processor if possible, but for now I just need a system of my own as long as it works and starts up fine.
Yeah, you definitely need to have wiretap turned on.
If you are running Wiretap 1.7 you must append the IP addres with :7549, example, 192.168.1.55:7549.
If you have Wiretap 2007, then it should be found automatically.
Contact me directly if you have any further questions.
@julik 24083 wrote:
Maybe you know some DPX decoders one can snatch for such a task?
Sorry, I don’t. We rely on on Quicktime to do all that stuff. There was a post on the 2008 beta forum from Dan: “Reading DPX files is quite easy and reliable if you stick to commonly-used variation of DPX. I suggest you start with that. 10 bit is dead simple.”
Alan
you could always install the GlueTools DPX plugin and use tether to transfer the DPX into stoneFS.
@julik 24063 wrote:
Hello everyone!
I’m having some trouble with importing DPX files from our XServe to the flame 9.5.13/14. When I select the sequence and hit “Soft import”, it imports the sequence but the proxies are corrupted. When I try to look at the full-res clip I see nothing but black. Same in Batch – either a black screen or garbled proxy.
While I run the import, the console fills up with the messages like this:
Unable to read file ‘/usr/discreet/clip/standardfs/bin6010/’: invalid argument
I checked specifically – this has to do with the format they are in, as soft-importing an SGI seq just works. Simply loading the files to the framestore works too.
How should I go about it? Maybe there is some converter to “normalize” the .dpxs that Flame does not like?
tether transfers quicktimes into StoneFS without this gamma problem.
Just got back from IBC. Spent some time talking with Marc-Andre and Graham from RED about workflows. Since RED has integrated their component at the Quicktime system level, tether is able to directly send the QT reference files from RED Alert into StoneFS.
I am not sure if Glue Tools is necessary. If the wrapped QTs are in DPX format and RED has not provided a proper codec, then Glue may be required. But it sounds like RED is in a proprietary Wavelet format which they have provided a codec for. In that case just tether & RedCodec alone would be able to send Red footage into Autodesk Stone/Standard FS.
@mseymour7 23906 wrote:
Red Alert very quickly (near instantly) makes warpper versions of r3d files which most certainly play in a quicktime player. We now do this all the time. It access the wavelet technology to do this at multiple resolutions too. I think you’ll be pleased with RED’s qt implementation – but still more work is being done.
So your suggesting a combination of (dream team) of RED -> flame via a Glue tools DPX path would allow tether to transfer dpx – to most anything?
Mike
Tether can use any default or 3rd party codec. Such that QT does not natively read DPX files, but with Glue Tools it can, which means tether can then transfer any DPX movie/sequence into Stone. Same with Window Media, with Flip Factory tether can directly transfer .WMV files. So, if RED did a proper job, tether could tranfer your RED QT wrapped files.
The litmus test is if Quicktime Player can view those files, then tether can transfer it. It is possible that RED did not fully implement QT, something you would have to test. Drop me a mail if you need an extended license for tether.
Let’s meet at IBC to discuss.
@mseymour7 23897 wrote:
Sorry I dont know how that would work
The RED code quicktimes are qt wrappers of the r3d files – I know Teather says it will copy any quicktime codec – but it doesn’t yet handle native r3d files does it ? If so how is it accessing the wavelet technology – I am only aware of Red Alert, RedCine Scratch and FCP?Can you explain please?
Mike
Tether will also be an important part of the RED workflow with Autodesk systems. It will allow you to transfer the QT files that RED Code creates directly into StoneFS without any transcoding or intermediate steps.