Erik Lindahl
Forum Replies Created
-
This is my point too:
– Motion is built from the perspective “do it realtime, all the time”. This has it’s drawbacks couse at one point or another you will drop frames and the performance drop and “realtime workflow” can be a problem. I don’t know exactly what Adolfo is going too with the VJ – play it as fast as possible, cause Motion caps at 25 fps if you have a 25 fps project
-
Then again, look at what Apple is doing with applications like Motion. This is in some ways a compositing, or animation app, that work A LOT more in realtime than After Effects. Sure, Motion won’t let me do everything that I can do in After Effects and it too will eventually bog my system down. But I reackon the main aspect of AE being “render always” is that it was written back in the late 1980’s/early 90’s where it’s approach was a must. Shake suffers in a similar way, when I reckon they shouldn’t need too.
Good this will probably happen in the future surrounding this… a Motion / AE / Shake “blend” would be a good blend of all worlds. The sad thing is that AE probably will require more or less a re-write to achieve true realtime performance.
-
Yeah
-
We had similar issue’s when doing comp with 3D and real-filmfootage with loads of DoF as well has the project was full 1080i50 HD. It was a hard to get everything to work for us
-
I’ve got the same problem using a Quad G5 with Kona LHe-card. Exporting RAM-previews as QuickTime files and playing them from the Kona TV app makes it possible.
AE gives me between about 4 to 12 fps in HD (16-bit kills, 8-bit is still more or less useless to monitor motion).
AE’s interface also takes a performance hit for no good reason while outputting to the monitor. My video-card is native HD and handles the SD down-convert by it’s self.
My fix is to turn off monitor aside from checking colors and such and render out files for previews. Motion I can see on the comp’s TFT-screen well.
This shouldn’t be an issue. RGB-files out of memory should play in realtime.
-
Note that the “pop-pop” is visible on the ref-monitor as well with the screen jumping, green flashes and all…
-
No, the XLR from the Kona LHe KL-Box goes into my Mackie mixer. This is then connected via XLR to my Genelec speakers.
I have a XLR to mono-tele (don’t know if that’s the correct english word, “large mono headphone cord”) converter to the mixer since the XLR-connectors there are powered.
I didn’t have this issue at all on another Kona LS system (different machine), a small “tick” was eminent sometime with v 2.01 of the Kona software. But this is a loud “pop-pop” that reads out on the mixer’s led.
More tests show:
– the pop-issue only happens during SD to HD switching on the Kona LHe board. This is a huge problem. A semi-solution is to have SD as my standard framebuffer and get the “pop” everytime I open a HD show -
Okey
-
-
*Mumble muble* Nah, it’s great with these improvements however they are really NTSC-land focuses. What would make my day is SD 16×9 FHA > 4×3 LTR conversion as well as single-system usage of the Kona scaling hardware (having to go to/from Digibeta och a secondary system is a pain). Also, true 720p25 support, but that ball might be in Apples playingfield at the moment