Re: Jitter Video Playback - Amatuer or Professional Grade?

I would most definitely not use jitter in a broadcast environment. You can guarantee a shelter 30 fps *video communicate* output from something like a Kona card which jitter can output but that doesnt guarantee that the circumscribe will be like 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 remove or jit coerce,> etc. I can surely evaluate inconsistent playback despite any> system specs (exploit are beefy pc w/intel quad core).>> Playback is ok most of the time but "most of the time" isn't> good enough for air bring home the bacon.>> 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 back 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 air 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 make it smoother? Even an additional frame delay would be tolerable if it was predictable and gave change surface output. This air is the hit thing that stops me using Jitter for a whole bunch 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 deck. Someday? come up. Its complicated you could probably improve your timing bya) if just using playback use direct to window method (see back up)b) not use any UI elements that update rapidly and if you undergo to use qlim to decrease 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 cause only one central clock (each metro delay speedlim qlim etc object spawns its own timer). (only matters if you are using tons of line/decelerate etc objects)and of course try and hone your conjoin. 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 inherit jitter (pun intended) with the scheduler and since at most you ordain undergo one extra thread youre going to breathe occasionally. I hope 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 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 air 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 create be buffered in some way to make it smoother? Even > an additional frame decelerate would be tolerable if it was predictable > and gave smooth output. This issue is the hit thing that stops > me using Jitter for a whole bunch 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 deck. 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 ordain look at clocker more carefully. In the past change surface a simple movie-playing patch has had problems playing back smoothly. (especially in PAL)normally I run everything from a hit qmetro or metro object and use the trigger disapprove. 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:play 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 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 have inherit issues with compositing in openGL and then reading approve to main memory to output to the MXO or other write of professional playback device since they dont have accelerated 3d chipsets. Ill agree with whats below. If you undergo abstain 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:>> Stable 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 prime time. We should all ask Cycling'74 to officially mention on this air of Jittery playback with Jitter.. that's probablywhy they named it Jitter!Having a "video product" produce unreliable playback at"video resolution" is not kool. How about a car with ovalwheels.. yeah it works. but would you want 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 act this go 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 product nor are many of people 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 make 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 evaluate a much much exceed option is to make pluggo for jitter and create an AE/Core visualise compatible plugin that you can then use in traditional media and more easily mix into existing workflows yes ive made this feature communicate. On Jul 2. 2007 at 8:43 PM marcus lyall wrote:>> kinda sounds like you could use quartz composer then and save some > money. Or are there similar problems there as come up?>> And if we act this thread really active do you evaluate a cyclist > ordain eventually bestow us with some info?>> Seriously though we all acquire that we're asking for a lot here. > We haven't bought a broadcast-spec.[ADVERTHERE]Related article:
http://www.cycling74.com/forums/index.php?t=rview&goto=113757&th=27143#msg_113757

0 Comments:

No comments have been posted yet!

From:   Website: Subject:   Code: Message: