Jitter: Who's been running it and has there been any problem

Nightrider · Post by **Nightrider** » Sun Sep 13, 2009 4:28 am

I'm running Jitter (a four channel, amplitude reactive patch) within Live and it's running amazingly stable at this stage. I'm about to start pushing it further but I'm wondering if others have been experimenting with this? results?

Also is there any limitations with running Jitter within Live compared to natively in Max??

cheers,

Tom.

gavspav_2 · Post by **gavspav_2** » Sun Sep 13, 2009 11:20 am

I've been experimenting with Jitter and a major limitation I've been finding is that I don't know the first effing thing about it!

There's a number of different window options but which is the best way of having a full screen setup on a second monitor?

I know RTFM.....

Might post again in a few hours!

synnack · Post by **synnack** » Sun Sep 13, 2009 12:14 pm

I messed with Jitter yesterday in M4L and it runs great.

I have midi from one track sending bangs to a jit.qt.movie on a completely different track (using send/receive) to bang out frames in perfect time with the midi.

No real noticeable latency. Seems to work great.

emmanuel_2 · Post by **emmanuel_2** » Sun Sep 13, 2009 1:20 pm

gavspav_2 wrote:I've been experimenting with Jitter and a major limitation I've been finding is that I don't know the first effing thing about it!

There's a number of different window options but which is the best way of having a full screen setup on a second monitor?

I know RTFM.....

Might post again in a few hours!

jit.window has a fullscreen attribute. You can also send messages to position it on the second monitor if you have one. You might want to have a look to the jitter tutorials which cover that. I've an abstraction in my ejies (jit.fullscreen) that might help you with that:

gavspav_2 · Post by **gavspav_2** » Sun Sep 13, 2009 1:30 pm

Yes I've been doing a few jitter tutorials and vaguely getting my head around it.

I have a patch that plays a qt movie in an open gl window with buttons to put on the second monitor and/or make it full screen.

From Max4Live putting it on the second monitor works and making it full screen crashes Max4Live.

If I try it from within Live it doesn't work.

Probably my patching though. I'll have a look at your abstraction. Thanks

gavspav_2 · Post by **gavspav_2** » Sun Sep 13, 2009 1:50 pm

I've basically copied Tutorial 38 (from the Jitter tutorials) into a MaxforLive device.

It works when controlled from Max but if I try to control it from within Live I get no output.

I can create a window though and move it to the external monitor but when I go full screen it crashes.

Can anyone else confirm this as a bug or limitation?

mlehmann · Post by **mlehmann** » Mon Sep 14, 2009 2:14 am

I'm having problems with a very simple patch that uses midi notes to select movies in umenu and plays them with jit.qt.movie. Live freezes or crashes everytime.

Nightrider · Post by **Nightrider** » Mon Sep 14, 2009 3:33 am

mlehmann wrote:I'm having problems with a very simple patch that uses midi notes to select movies in umenu and plays them with jit.qt.movie. Live freezes or crashes everytime.

Yes I have also been having crashes with this. I added a simple 'live.numbox' to select video videos from a umenu, this send CPU sky high when using it and crashes live...

I'm about to repost it with my patch included

roberwic · Post by **roberwic** » Fri Sep 18, 2009 2:24 pm

I have also been getting crashes. Iv been trying to run a motion sensitive patch I made and it also crashes every time. will repost with the patch.

andrewbenson · Post by **andrewbenson** » Fri Sep 18, 2009 5:34 pm

In my tests, Jitter works pretty well in Max-for-Live, with a couple of caveats. First, consider a Max Device in Live to always be in Overdrive mode. This, in a lot of circumstances, will reduce frame-rates a bit from what you are used to in non-Overdrive Max functionality. The second thing is that you will want to make judicious use of the jit.qball object to force some interactions into the low-priority queue, particularly QuickTime file reading and anything that will be displayed in a window. For this same reason, I would strongly advise using qmetro instead of metro as the frame-banging source in all your Jitter devices. With these two things in mind, you should be able to do a lot with Jitter inside Live. Of course, if you do wind up getting crashes for any reason, you should post a message to the bug forum with a simple, stripped down patch that demonstrates the issue.

Best,
Andrew B.

synnack · Post by **synnack** » Sat Sep 19, 2009 2:50 am

I spoke too soon. Now, any jit. object crashes max, both in max for live, and just in max.

In fact now if I just open Max 5.1 and create a new object of jit.qt.window and hit enter... boom. Max crashes.

I think it may have to do with a quicktime update that came with iTunes 9. Before iTunes 9 it worked fine.

I will remove iTunes and see.

synnack · Post by **synnack** » Sat Sep 19, 2009 4:31 am

Yep.

http://www.cycling74.com/forums/index.p ... 5e9cc46ea0

Uninstalled iTunes. Uninstalled Quicktime. Installed old version of quicktime. Jitter in Max for Live working fine again.

Avoid iTunes 9.

mlehmann · Post by **mlehmann** » Sat Sep 19, 2009 9:35 pm

The problem's not with iTunes 9 but with QuickTime. I did the iTunes update but not the QuickTime update because i'm on Snow Leopard and I don't have those kind of problems.

synnack · Post by **synnack** » Tue Sep 22, 2009 4:48 pm

mlehmann wrote:The problem's not with iTunes 9 but with QuickTime. I did the iTunes update but not the QuickTime update because i'm on Snow Leopard and I don't have those kind of problems.

How did you do that? When I run the iTunes installer (on windows for this beta) it gives me no option not to do the quicktime update. It just does it. I hacked up the installer package and put the quicktime 7.1.x installer in the iTunes 9.x path to trick it to use that one. But then when I launch iTunes 9 it tells me it requires Quicktime 7.6.4 or later.

There seems to be no way to install iTunes 9 and also use a Quicktime version that works with Jitter.

mlehmann · Post by **mlehmann** » Tue Sep 22, 2009 4:59 pm

Like I said, I'm on Snow Leopard and therefore, iTunes 9 uses Quicktime X. That allows me to keep my old version of QT7.

Jitter: Who's been running it and has there been any problem

Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem

Re: Jitter: Who's been running it and has there been any problem