Leo Mayberry

I've been cobbling together A/V performance software with Max/Jitter on a PC. I was hoping Max 7.0 was going to be better, but it looks like there isn't going to be a way to get any better performance out of it. I really am having a hard time justifying an upgrade. Please disabuse me of the following hangups about 7.0 I hope they are just temporary setbacks toward something better.

1) Whatever performance improvements might be had in Max 7.0 seem to rely on using the alternate movie backend to quicktime. On a PC, it seems like quicktime is currently the only option, and therefore I can't expect to see any performance increase until some nebulous date in the future when the other engine is implemented for PCs.

2) The only way to get audio out of a movie in MSP still seems to be the frustrating, but doable "Spigot~" object. Even if I went so far as to get a MAC, it seems like the Spigot~ object only works with the quicktime engine in use for movies.

3) since the Jitter movie engine setting seems to be a system-wide either/or situation, it seems like if I want to use audio on ANY movies with Spigot, that I wouldn't be able to use the other engine for better video performance. On a Mac or a PC if I want to use audio from movies in MSP, I'm stuck still using the Quicktime object for everything... which puts me back at essentially Max 6.

Is there a way to choose the engine per Movie instance, so that Spigot~ needing movies could be set to quicktime and the others to the hopefully better method?

I really seems like the movie object needs to get upgraded to supporting MSP audio output to evolve it into the more A/V heavy world of today. Hopefully it can do this without have to use the Quicktime backend, which has theoretically been the cause of a lot of performance issues.

I've been cobbling together A/V performance software with Max/Jitter on a PC.  I was hoping Max 7.0 was going to be better, but it looks like there isn't going to be a way to get any better performance out of it.  I really am having a hard time justifying an upgrade.  Please disabuse me of the following hangups about 7.0   I hope they are just temporary setbacks toward something better.
1) Whatever performance improvements might be had in Max 7.0 seem to rely on using the alternate movie backend to quicktime.  On a PC, it seems like quicktime is currently the only option, and therefore I can't expect to see any performance increase until some nebulous date in the future when the other engine is implemented for PCs.
2) The only way to get audio out of a movie in MSP still seems to be the frustrating, but doable "Spigot~" object.   Even if I went so far as to get a MAC, it seems like the Spigot~ object only works with the quicktime engine in use for movies.
3) since the Jitter movie engine setting seems to be a system-wide either/or situation, it seems like if I want to use audio on ANY movies with Spigot, that I wouldn't be able to use the other engine for better video performance.  On a Mac or a PC if I want to use audio from movies in MSP, I'm stuck still using the Quicktime object for everything... which puts me back at essentially Max 6.

I really seems like the movie object needs to get upgraded to supporting MSP audio output to evolve it into the more A/V heavy world of today.  Hopefully it can do this without have to use the Quicktime backend, which has theoretically been the cause of a lot of performance issues.


max-7-0-on-a-pc-av-performance-hurdles-to-conquer

yes, type the desired engine name into the max box, e.g. [ jit.movie @engine qt ]

Is there a way to choose the engine per Movie instance, so that Spigot~ needing movies could be set to quicktime and the others to the hopefully better method?


yes, type the desired engine name into the max box, e.g. [ jit.movie @engine qt ]


That's very good news about the engine being able to be modified per instance of jit.movie. I can deal with A/V clips being a "special" thing, since I already have them segregated.

That's very good news about the engine being able to be modified per instance of jit.movie.   I can deal with A/V clips being a "special" thing, since I already have them segregated.


Max 7.0 on a PC A/V performance, hurdles to conquer.