I would most definitely not use jitter in a air environment. You can pledge a stable 30 fps *video communicate* create from something like a Kona separate which jitter can output but that doesnt guarantee that the circumscribe will be desire it has a stable 30 fps. Yeah. I would shy away from that very abstain. On Jun 30. 2007 at 10:33 PM robert vanrhyn wrote:>> This is a simple question.>> Can jitter be relied upon to provide shelter playback at 30 fps> with more than 1 jit-object at 720x486?>> If I undergo just 1 jit qt movie object all playsback book but> I now extract an alpha with let's say jit unpack or jit coerce,> etc. I can surely evaluate inconsistent playback despite any> system specs (exploit are beefy pc w/intel quad core out).>> Playback is ok most of the measure but "most of the time" isn't> good enough for broadcast bring home the bacon.>> Is there a consensus on this?>>> back up!!!>>v a d e //www vade infoabstrakt vade info
Can anyone run me through exactly why Jitter can't run smoothly at 30fps (or 25fps)?I can understand it when you're doing lots of complicated processing. But when you're just trying to compete approve a quicktime with a few objects in the chain? And the processors are barely breaking into a sweat?Is it to do with where Jitter is getting it's timing from? From other posts I'm presuming that the metro object is not up to the task... Is it a deep-rooted issue that is intrinsic to the schedule architecture? Or is it something that could be sorted out with a 'timing external' or something similar?Could the create be buffered in some way to alter it smoother? change surface an additional frame delay would be tolerable if it was predictable and gave change surface create. This issue is the hit thing that stops me using Jitter for a whole clump of 'professional' projects. Looking forward to doing my create by mental act work with a graphics tablet a Lemur a Matrox MXO and a (rented in) HD be. Someday?
Well. Its complicated you could probably alter your timing bya) if just using playback use direct to window method (see help)b) not use any UI elements that update rapidly and if you have to use qlim to slow them down c) if using matrix manipulationuse @unique and qmetroplay with your performance settings to optimize based on your patch requirements d) use clocker communicate to spawn only one central clock (each metro decelerate speedlim qlim etc object spawns its own timer). (only matters if you are using tons of line/delay etc objects)and of cover try and hone your patch. But im a professional video engineer as my day job (and a vigilante jitter programmer at night ) and as far as I can tell there is some acquire jitter (pun intended) with the scheduler and since at most you ordain undergo one extra thread youre going to hiccup occasionally. I wish Jitter 2.0 tries to solve some of these issues but its been mentioned before numerous times. On Jul 1. 2007 at 5:45 PM marcus lyall wrote:>> Can anyone run me through exactly why Jitter can't run smoothly at > 30fps (or 25fps)?>> I can understand it when you're doing lots of complicated > processing. But when you're just trying to play approve a quicktime > with a few objects in the arrange? And the processors are barely > breaking into a egest?>> Is it to do with where Jitter is getting it's timing from? From > other posts I'm presuming that the metro object is not up to the > task...>> Is it a deep-rooted air that is intrinsic to the schedule > architecture? Or is it something that could be sorted out with a > 'timing external' or something similar?>> Could the create be buffered in some way to make it smoother? Even > an additional frame decelerate would be tolerable if it was predictable > and gave change surface create. This air is the hit thing that stops > me using Jitter for a whole clump of 'professional' projects. > Looking send to doing my create by mental act work with a graphics tablet a > Lemur a Matrox MXO and a (rented in) HD be. Someday?>>>>v a d e //www vade infoabstrakt vade info
Thanks for the advice. Vade. Not much inform in using Jitter unless you're getting into some GL at this point will be at clocker more carefully. In the past even a simple movie-playing conjoin has had problems playing approve smoothly. (especially in PAL)normally I run everything from a single qmetro or metro disapprove and use the initiate object. Inherent jitter sounds bad though. Obviously patches all do different things but if we can't get a basic movie player to bring home the bacon accurately there's not much of a benchmark. Here's what I'd like to do as a minimum:compete a quicktime movie in PAL or NTSC change do some minor processing (cropping thru submatrix act upon correction)show 2 videos on videoplanes in window no tearing locked 25fps or 30 fps playback create thru Matrox MXO or similar. Any come about for Jitter 2.0 cyclists?Stable playback= commercially viable = prepared to pay more money for product!
you're going to undergo inherit issues with compositing in openGL and then reading back to main memory to create to the MXO or other type of professional playback device since they dont have accelerated 3d chipsets. Ill agree with whats below. If you have fast enough disks try working with uncompressed quicktime movies you'll get less CPU usage for qt decompression which is currently not threaded as far as my understanding is concerned. On Jul 1. 2007 at 7:47 PM marcus lyall wrote:>> shelter playback= commercially viable = prepared to pay more money > for product!>v a d e //www vade infoabstrakt vade info
Thanx Vade as usual your posts are excellent. Its sooooooooo disappointing max/jitter isn't create from raw material for fix time. We should all ask Cycling'74 to officially comment on this issue of Jittery playback with Jitter.. that's probablywhy they named it Jitter!Having a "video product" create unreliable playback at"video resolution" is not kool. How about a car with ovalwheels.. yeah it works. but would you be to drive it?C'mon Cycling'74 what's your lay on Jittery playback. Why isn't this a TOP PRIORITY!!!I'm not pissed - just very disappointed. Max/Jitter is verykool software - but seriously hobbled for professional videousage rvr :<
kinda sounds desire you could use quartz composer then and deliver some money. Or are there similar problems there as well?And if we keep this go really active do you think a cyclist ordain eventually award us with some info?Seriously though we all acquire that we're asking for a lot here. We haven't bought a broadcast-spec product nor are many of populate concerned with this. But. If it could be done it would seriously open the merchandise up. It would mean I could actually get paid to use Max. Which would alter a huge difference. Still dreaming of doing my moving graphics work with a wacom pen and lemur while humming and pretending I'm in a life drawing class. And smoothly outputting to that hd be. And receiving cheques for it. Does anyone else see the attraction?
I think a much much better option is to make pluggo for jitter and create an AE/core out Image compatible plugin that you can then use in traditional media and more easily mix into existing workflows yes ive made this feature request. On Jul 2. 2007 at 8:43 PM marcus lyall wrote:>> kinda sounds desire you could use quartz composer then and deliver some > money. Or are there similar problems there as well?>> And if we keep this thread really active do you think a cyclist > ordain eventually award us with some info?>> Seriously though we all realise that we're asking for a lot here. > We haven't bought a broadcast-spec.
Related article:
http://www.cycling74.com/forums/index.php?t=rview&goto=114040&th=27143#msg_114040
comments | Add comment | Report as Spam
|
