Julien Bayle

I have a student with a weird problem on his windows 8 x64 and Max 7 when he tries to play one of the .mov (Apple QT codec) from the Max' assets (examples)

It doesn't work and we don't have any error messages.

windows-8-problem-with-max-7-all-mov-qt-movie-not-readable-in-jitter

Probably a very obvious thing: QT is installed? do the .mov play inside the media player? just for checking if that is a system problem or Max related...

which codec is used inside the mov container...

i guess most of the jitter stuff is still not supported for Win x64.

Subtle Max OSX racism ( joke...but kind'a true :-) ).

Even most of the third party externals are available for OSX only.

It causes a little bit of frustration for the Win community wich i belong to :-).

But i guess the most C74 developers deal with OSX machines.

I can't either run jitter examples on my Win 7 x64.

I can run all the stuff ( except the stuff marked for Mac only by the objects itself ) in x32 mode.

Definetly i must say that after several years on Max on Win i still have to say that Win version is a less beloved sun of C'74 and the whole Max community. I understand why. Obviously because the majority of people doin' music and media arts is on OSX. Nevertheless I have to say that now Win7/8 are on par in term of permormance (if not better at lower cost) if you have the wisdom of choosing the right laptop/desktop machine. I can verify this workin' with mates and collegues who run OSX. Let's see if the situation will improve. On the C'74 side the only two thing i complain' a litte are some object not available for Win x64 and SDK not workin' with Open Source developing tools as WinMG x64 ( wich is obviously an obstacle of havin' more third party externals for Win, great stuff as Jamoma and TapTools are not available for Win in their last versions i.e. ).

Anyway long life to C'74 and the whole Max communuity, i know future will be brighter.

hi,
i guess most of the jitter stuff is still not supported for Win x64.
Subtle Max OSX racism ( joke...but kind'a true :-) ).
Even most of the third party externals are available for OSX only.
It causes a little bit of frustration for the Win community wich i belong to :-).
Sad truth but truth.
I hope things will improve with time.
But i guess the most C74 developers deal with OSX machines.

I can't either run jitter examples on my Win 7 x64.
I can run all the stuff ( except the stuff marked for Mac only by the objects itself ) in x32 mode.
Definetly i must say that after several years on Max on Win i still have to say that Win  version is a less beloved sun of C'74 and the whole Max community. I understand why. Obviously because the majority of people doin' music and media arts is on OSX. Nevertheless I have to say that now Win7/8 are on par in term of permormance (if not better at lower cost) if you have the wisdom of choosing the right laptop/desktop machine. I can verify this workin' with mates and collegues who run OSX. Let's see if the situation will improve. On the C'74 side the only two thing i complain' a litte are some object not available for Win x64 and SDK not workin' with Open Source developing tools as WinMG x64 ( wich is obviously an obstacle of havin' more third party externals for Win, great stuff as Jamoma and TapTools are not available for Win in their last versions i.e. ).
Anyway long life to C'74 and the whole Max communuity, i know future will be brighter.


We are just trying to play the dozer.mov movie with jit.movie and yes, this movie and all the others are readable with other external player (outside of Max I mean)

Thanks for your answers.
We are just trying to play the dozer.mov movie with jit.movie and yes, this movie and all the others are readable with other external player (outside of Max I mean)


even here i can play .mov movies with QTPlayer.

The thing is that jitter is still not complete on Win x64 i guess

Yes Julien,
even here i can play .mov movies with QTPlayer.
The thing is that jitter is still not complete on Win x64 i guess


as mentioned, its a 64 bit problem. just have your student run the 32 bit version and all will be well.

:-) until Max will be totally landed on Win present and future wich is 64 bit given the amount of memory request for modern live set and DAW work-horses ( lot of plugins, lot of sample data, increased gfx resources requested ).

Let's hope for a Max 7.1 soon ( is a lot of time that jitter is not working on Win x64 ).

:-) until Max will be totally landed on Win present and future wich is 64 bit given the amount of memory request for modern live set and DAW work-horses ( lot of plugins, lot of sample data, increased gfx resources requested ).
Let's hope for a Max 7.1 soon ( is a lot of time that jitter is not working on Win x64 ).


We'll wait for better days and a new version :)

Hi guys. In "defense" of Cycling'74, I would like to say something:

Max was a Mac only application for many years. It made sense back then to rely on the QuickTime architecture, the multimedia base for the OS. When Max came out for Windows (version 4.5?), QuickTime was available for Windows and was still widely used in most audiovisual production contexts, so it made sense to continue using it.

In the last years, Apple has been deprecating QuickTime in favor of more modern technologies like AV Foundation on the Mac. Quicktime, even on the Mac is a 32 bit API. So, Apple is discontinuing QuickTime and, currently, it does no longer make sense to port the entire new architecture (AV Foundation) to Windows. This led Apple to the current QuickTime on Windows problem. There's no more Mac and Windows parity. Essentially, QuickTime on Windows has been left to die a slow death, with only some minor bug fixes and security updates (we're still on QuickTime 7).

So, if you want QuickTime support on Max (Windows), you have to use the 32 bit version.

Cycling cannot rely anymore on QuickTime for the future, hence the transition to AV Foundation on the Mac, and some equivalent infrastructure on the Windows side. With Apple, the framework is very powerful and built directly in the OS, so it was a no-brainer. I guess that the adoption of a similar infrastructure in Windows is proving a little more difficult, hence the absence of any alternative to QuickTime on this first release of Max 7. But it will be unavoidable. See Andrew Benson's response to my question on this thread: 

https://cycling74.com/articles/max-7-sneak-preview-episode-3/

My bet is that they're working hard on it right now... 7.0.1? 7.1? 7.2? It's a matter of time, we'll just have to be patient and, meanwhile, if we want performance, there's always jit.gl.hap!

Max was a Mac only application for many years. It made sense back then to rely on the QuickTime architecture, the multimedia base for the OS. When Max came out for Windows (version 4.5?), QuickTime was available for Windows and was still widely used in most audiovisual production contexts, so it made sense to continue using it.
In the last years, Apple has been deprecating QuickTime in favor of more modern technologies like AV Foundation on the Mac. Quicktime, even on the Mac is a 32 bit API. So, Apple is discontinuing QuickTime and, currently, it does no longer make sense to port the entire new architecture (AV Foundation) to Windows. This led Apple to the current QuickTime on Windows problem. There's no more Mac and Windows parity. Essentially, QuickTime on Windows has been left to die a slow death, with only some minor bug fixes and security updates (we're still on QuickTime 7).

So, if you want QuickTime support on Max (Windows), you have to use the 32 bit version.
Cycling cannot rely anymore on QuickTime for the future, hence the transition to AV Foundation on the Mac, and some equivalent infrastructure on the Windows side. With Apple, the framework is very powerful and built directly in the OS, so it was a no-brainer. I guess that the adoption of a similar infrastructure in Windows is proving a little more difficult, hence the absence of any alternative to QuickTime on this first release of Max 7. But it will be unavoidable. See Andrew Benson's response to my question on this thread: https://cycling74.com/articles/max-7-sneak-preview-episode-3/

My bet is that they're working hard on it right now... 7.0.1? 7.1? 7.2? It's a matter of time, we'll just have to be patient and, meanwhile, if we want performance, there's always jit.gl.hap!


for windows 64 video support, you should check out the viddll-beta package, available via the Max 7.1 package manager.

https://cycling74.com/forums/announcing-viddll-beta-video-engine-call-for-testers/

for windows 64 video support, you should check out the viddll-beta package, available via the Max 7.1 package manager. 

please read the post here for more info:
https://cycling74.com/forums/announcing-viddll-beta-video-engine-call-for-testers/


Windows 8 problem with Max 7 / All .mov QT movie not readable in Jitter :'(