peakamp affecting movie framerate


    Mar 27 2006 | 3:56 pm
    Hi there.
    I'm creating a patch that plays a different movie file in a window based on the amount of volume the sound input picks up. The reason i want to do this is to make a man dance differently to different amounts of volume. This is actually very easy and ive adapted most of it from tutorial28 in the jitter tutorials. However my problem is probably so basic it falls under a max one not jitter
    Each movie file will be 5 seconds long. So i Only want it to select a movie file every 5 seconds, once the current movie is finished and the point where it will play semlesly into any of the other movie files. (each movie file will start and end with the man in the same position)
    My problem is that if i set peakamp to check for sound every 5 seconds with the right input the movie then plays at that speed, 25 frames per 5 seconds instead of 25 frames per second.
    I've tried using onebang and metro to have it detect sound every 25m/s but only choose a movie every 5 and it hasnt worked I've tried forcing the movie framerate with metro but then it stops working alltogether.
    What do i need to do? Basicaly i dont care wether it detects sound every 25ms or once every 5 seconds as long as it only selects my movies every 5 seconds
    heres my patch as it is at the moment, note i havent tidied it up from its tutorial28 origions very much at the moment
    Thanks in advance everyone

    • Mar 27 2006 | 5:58 pm
      Hi Richard, The problem you are having is due to the fact that you are using the output of peakamp~ to bang your jit.qt.movie objects. This is *not a reliable way to accomplish what you want to do. You will be better off using one jit.qt.movie object driven by a metro/qmetro, and then use the peakamp~ output to load different movies. This will ensure that your movie reads from the beginning to end. You can use a float/int object or qlim to thin your data stream to only output readings once every 5 seconds. Here is a sample of patchery to give you an idea:
      Cheers, Andrew B.
    • Mar 28 2006 | 11:29 am
      thanks very much
      You put into words what i knew the peoblem was and fixed it. I knew what the problem was but didnt know enough max objects to be able to find the object i needed to use. i.e qlim and prepend
      Whats the best way of going around this problem in the future, I am reading through the tutorials but is that really the quickets way to get a working knowledge of all the max objects?
      Also I dont fully understand the difference between the 1 jit.qt.movie and the 5 i had. Whilst im gratefull of course I'd still like to understand why 1 jit.qt.movie object is better than 5. I assume because it is easier on the computer.
      Thanks in advance
      Richard
    • Mar 28 2006 | 11:59 am
      On 28 Mar 2006, at 12:29, Richard Powell wrote:
      > I am reading through the tutorials but is that really the quickets > way to get a working knowledge of all the max objects?
      Erm... yes.
      nick rothwell -- composition, systems, performance -- http:// www.cassiel.com
    • Mar 28 2006 | 2:08 pm
      On 28-Mar-2006, at 13:29, Richard Powell wrote: > Whats the best way of going around this problem in the future, I am > reading through the tutorials but is that really the quickets way > to get a working knowledge of all the max objects?
      Your alternatives:
      1) Read the Reference Manuals cover to cover. Size: Max+MSP make 1200 pages. Organizational principle: alphabetical order.
      2) Work through the tutorials. Size: Max+MSP ca. 600pp (leaving out the "Topics" sections). Organizational principle: structured lessons.
      3) Fiddle around with example patches and hope that you'll eventually pick up all you need to know. Size: unbounded. Organizational principle: serendipity.
      Oh, and
      4) None of the above, ask the list questions like "how do you get those patch cords at 90-deg angles?" and "how do I print text in the Max window?"
      Organizational principle: none. Size: depends upon how patient people are that week (we all know that it's confusing at the beginning, but, well, some people ask a *lot* of questions that are answered in the Getting Started, and after a while it does get, as my mother-in-law would say, rathatahhsom).
      Not to discourage you from asking questions, but to remind all the newbies that the newbie questions are already answered.
      Good luck, Peter
      -------------- http://www.bek.no/~pcastine/Litter/ ------------- Peter Castine +--> Litter Power & Litter Bundle for Jitter
      iCE: Sequencing, Recording & |home | chez nous| Interface Building for |bei uns | i nostri| Max/MSP Extremely cool http://www.castine.de http://www.dspaudio.com/
    • Mar 28 2006 | 2:41 pm
      Richard Powell wrote: > Whats the best way of going around this problem in the future, I am > reading through the tutorials but is that really the quickets way to > get a working knowledge of all the max objects?
      Yes, plus working practice with your own projects, what you are obviously doing already. Its complex and will need its time, but its worth it. And keep reading the list and look and analyze all the patches which are posted or reffered to...
      Your welcome
      Stefan
      --
      [][] [][][] [][] [][][] [][][][][][][][][][][][][][][]
      Stefan Tiedje Klanggestalter Electronic Composition & Improvisation
      /~~~~~ \ /|() ()| ))))) )| | |( \ /// _/)/ ))))) ___/ ///
      -------------------------x---- --_____-----------|----------- --(_|_ ----|-----|-----()---- -- _|_)----|-----()----------- ----------()------------x-----
      14, Av. Pr. Franklin Roosevelt, 94320 Thiais, France Phone at CCMIX +33-1-57 42 91 09
    • Mar 28 2006 | 4:16 pm
      Quote: Richardo P wrote on Tue, 28 March 2006 04:29 ---------------------------------------------------- > Whats the best way of going around this problem in the future, I am reading through the tutorials but is that really the quickets way to get a working knowledge of all the max objects? ----------------------------------------------------
      definately, but also check the help patches of every object you have doubts about, if you want to know all about an object, refer to the reference manual.