Re: Re: Jitter Video Playback - Amatuer or Professional Grade?

I would most definitely not use jitter in a broadcast environment. You can guarantee a stable 30 fps *video signal* output from something like a Kona card which jitter can create but that doesnt pledge that the circumscribe will be desire it has a stable 30 fps. Yeah. I would shy away from that very fast. On Jun 30. 2007 at 10:33 PM robert vanrhyn wrote:>> This is a simple question.>> Can jitter be relied upon to give shelter playback at 30 fps> with more than 1 jit-object at 720x486?>> If I have just 1 jit qt movie disapprove all playsback fine but> I now extract an alpha with let's say jit unpack or jit compel,> etc. I can surely expect inconsistent playback despite any> system specs (exploit are beefy pc w/intel quad core out).>> Playback is ok most of the time but "most of the time" isn't> good enough for air work.>> Is there a consensus on this?>>> help!!!>>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 arrange? 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 disapprove 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 alter it smoother? Even an additional close in delay would be tolerable if it was predictable and gave smooth output. This issue is the single thing that stops me using Jitter for a whole clump of 'professional' projects. Looking send to doing my create by mental act bring home the bacon with a graphics tablet a Lemur a Matrox MXO and a (rented in) HD deck. Someday? Well. Its complicated you could probably alter your timing bya) if just using playback use enjoin to window method (see back up)b) not use any UI elements that modify rapidly and if you have to use qlim to slow them drink 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 measure (each metro delay speedlim qlim etc object spawns its own timer). (only matters if you are using tons of lie/delay etc objects)and of cover try and optimize 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 will 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 compete back a quicktime > with a few objects in the arrange? 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 program > architecture? Or is it something that could be sorted out with a > 'timing external' or something similar?>> Could the output be buffered in some way to alter it smoother? change surface > an additional close in delay would be tolerable if it was predictable > and gave smooth output. This issue is the single thing that stops > me using Jitter for a whole bunch of 'professional' projects. > Looking send to doing my design work with a graphics tablet a > Lemur a Matrox MXO and a (rented in) HD deck. Someday?>>>>v a d e //www vade infoabstrakt vade info Thanks for the advice. Vade. Not much point in using Jitter unless you're getting into some GL at this point will look at clocker more carefully. In the past even a simple movie-playing patch has had problems playing back smoothly. (especially in PAL)normally I run everything from a single qmetro or metro disapprove and use the trigger object. Inherent jitter sounds bad though. Obviously patches all do different things but if we can't get a basic movie player to work accurately there's not much of a benchmark. Here's what I'd desire to do as a minimum:compete a quicktime movie in PAL or NTSC format do some minor processing (cropping thru submatrix colour correction)show 2 videos on videoplanes in window no tearing locked 25fps or 30 fps playback output thru Matrox MXO or similar. Any chance for Jitter 2.0 cyclists?shelter 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 write of professional playback.[ADVERTHERE]Related article:
http://www.cycling74.com/forums/index.php?t=rview&goto=113763&th=27143#msg_113763

0 Comments:

No comments have been posted yet!

From:   Website: Subject:   Code: Message: