still doesn't understand int

charred

Have searched the Forum but can't find an answer for this, and I'm going around in circles here over something that is probably quite simple: I've uninstalled and reinstalled Max8 (following various directions for installs rather than updates) but still have a frustrating problem with Vizzie. As soon as I drag AVPlayr into a window I get the error message "jit.movie~ doesn't understand int". Playr does the same along with multiple messages of "patchcord outlet out of range: deleting patch cord". Neither will play movies. I have tried using avf and viddll settings, and have deleted various preference and system files. Suggestions?

Source Audio

instead of dragging anything, doubleclick
that avplayer to open it as patch.
get out of presentatioin mode and see what's wrong.
using that premade stuff seems attractive to begin with, but as soon as something goes wrong, one is left in the dark with all that subpatchers, dependencies,
locked subpatches etc which one does not understand at all.

Roman Thilenius

not every error message from someone else´s patch means that there is an actual problem.

for example if you send an int into an object which does not understand ints, will throw an error message "i dont understand int", but will still function as expected when you send it a float.

something printed to the max console is not the same quality of problem as a unix kernel panic oder an unreadable sector on a harddisk.

the more serious issue in max is when something is not producing the correct error messages :)

Robert Ramirez

i'm fairly sure this was fixed some time back. can you let me know what OS and the exact Max version you are running?

charred

Thanks for everyone's responses -- sorry for the tardy reply, I'm up to my ears in development and all-day rehearsals on three interactive pieces for a video shoot later this week.

Double clicking to spawn Playr or AvPlayr results in the same behaviour. Tracing the toggle message into the Play/Stop button message (1/0) in the playr_controls bPatcher shows it coming out and going directly into the jit.movie~ object as an int (?), causing one of the error messages. Neither of the players will play a file. (Our UBC Toolbox bpatchers don't generate errors and will play files. Self promo: we're finishing up a new version of the Toolbox to release as a package.)

I'm on OS 11.4 on a 16 inch 2019 MacBook Pro, running Max 8.1.11.

Rob Ramirez

hmm, I can't reproduce. Can you let me know what version of Vizzie is installed?
File -> Show Package Manager -> In the dropdown window top right corner change "Remote Packages" to "Installed Packages", scroll down to find vizzie and click on it.
Let me know if it says 2.1.4.

also, can you try the following steps
new patcher
add an avplayer
select the module and open the inspector
scroll to the bottom of the inspector and click the checkbox next to "Embed Patcher in Parent"
save the patch
attach the patch to your reply here

charred

Hello all,

Thanks to everyone for the help -- have finished a major project so I'm back looking at this issue. Vizzie version is 2.1.4

AVPlayrTest.maxpat

Max Patch

Source Audio

charred

Many thanks, and thanks for the info - will check that out

Rob Ramirez

thanks for sending along the file. I am not seeing anything amiss, so there must be something more fundamental happening with your install. re-reading your post I missed the part about all the errors (definitely not expected).

I think your best option is to get in touch with support about this so we can attempt to track this down. out of curiosity, are you able to instantiate "vanilla" jit.movie and jit.movie~ objects, and do they function?

charred

Hello all,

As one does, I spent part of this holiday weekend doing the tedious work of spending hours isolating projects and patches and relaunching Max. Finally found the problem: a corrupted copy of playr_controls in a student assignment. Somehow this became what my system would load. I don't know what exactly in the particular playr was corrupted (other than the behaviour I described above) but having deleted it Jitter seems to be back to normal.

Another positive outcome of this exercise was recognizing (and starting to purge) the ridiculous amount of third-party materials I have in my system due to MMJ teaching examples over the years...

Many thanks to everyone for their suggestions and assistance.

Onwards!

bob