Scene name search with keyword

madlab · Post by **madlab** » Mon Sep 24, 2012 4:53 pm

What is your computer, os live and max version ? It's been widely tested by a friend (in a set approaching 800 scenes) and I and works every time, apart from the problem I described above. Are there any error messages in the max window ?

bosonHavoc · Post by **bosonHavoc** » Mon Sep 24, 2012 5:16 pm

win 7, live 8.3.1, max 5.1.9,

so it seems you made the patch in max 6,
is max 6 running stable with live?

the only error code i am getting is
zl.select:no such object found

madlab · Post by **madlab** » Mon Sep 24, 2012 5:35 pm

I think you mean zl.sect ? ok, so I think I got where the problem lies : type [zl sect] instead of [zl.sect]. The zl family has changed between max 5 and 6, but I hadn't noticed this name difference.
And please tell me if that works.
As far as max 6 is concerned, I 've been using it in Live for a while now and it seems to work rather nicely to build api and audio stuff. The official word is that it's not yet officially supported. But for a noob like me, the interface of max 6 is much quicker and intuitive to work with (auto completion and the magic wheel are great ideas !).

bosonHavoc · Post by **bosonHavoc** » Mon Sep 24, 2012 6:02 pm

awesome works great.
thank you.

I also added the plug in and plug out so audio will pass through
instead of dead heading at the plug.

madlab · Post by **madlab** » Mon Sep 24, 2012 6:55 pm

You are right about audiothru. When cleaning the patch, I accidentally got rid of it and put it back and reloaded the device this morning... If your max guru friend can tell where the problem about scene duplication comes from, I will be the happiest man in the world !
Glad that you comment it because I work hard to improve my skills and all testers and hardcore coders' comments are welcome !

natecraypo · Post by **natecraypo** » Sat Sep 29, 2012 11:38 pm

Hey, so are you still trying to figure this out? I gotta say the patch is pretty tight. I know very little about the regexpr object, however. With that in mind, my guess with the scene duplication trouble you've described is this...

This process is set to report a single integer which represents the scene index associated with the symbol given in the text box. It's seems this process is terminated as soon as a match is found. You might want a process that occurs in serial, meaning that each time the device matches a scene index with a scene name, it will poll the entire set from the very first scene AND report a match every time it's found.

So, in this instance, the very last scene in your set matching the give symbol will be reported, rather than just the first. This may be a step towards a solution. I'm tinkering around. Let me know what you think of all that. Did I make sense or miss the mark completely?

bosonHavoc · Post by **bosonHavoc** » Sun Sep 30, 2012 3:36 pm

awesome nate, thank you for getting involved.
I have not had time to test it yet but from what you said about it indexing each instance of the scene name
could be A really handy add on. we could use that to create a a quick way to select the beginning of a song in a live set.
IE: search "song" then it indexing all scenes named song.. which could be the first scene for each song in the set.
then use a up/down navigation to scroll through the songs till the song you want to play is in focus.

madlab · Post by **madlab** » Sun Sep 30, 2012 7:58 pm

I feel like I have to clarify the way it's designed to work, because it seems to me that this device works the way Bosonhavoc describes it :
You launch a search using a keyword, the device searches scene names then selects the first scene which name includes the keyword. As you mention different scene names including the keyword, it should already work that way. Once that first relevant scene is selected, you can launch it directly because it's already selected, then going to the following scenes using arrows or just launching them if the 'select next scene on launch' is activated in the prefs. What Nate made me think about would be a 'continue search' function from that point if the first scene found isn't the one you're looking for. But maybe I'm misunderstanding what you mean ?
It seems to me the copy / paste or duplicate scene issue is a totally different problem.

Re-read your post Boson and... yeah, that's a cool idea. Gonna think about it and patch. I attend a max worshop the whole week so maybe that will be later, but... Yeah !

natecraypo · Post by **natecraypo** » Sun Sep 30, 2012 8:42 pm

My suggestion would be to add a umenu that stores the desired scenes. The user then being able to select among those scenes using this menu. I have a version of your patch I'm toying with. PM me your email and I can forward it to you if you like.

Scene name search with keyword

Re: Scene name search with keyword

Re: Scene name search with keyword

Re: Scene name search with keyword

Re: Scene name search with keyword

Re: Scene name search with keyword

Re: Scene name search with keyword

Re: Scene name search with keyword

Re: Scene name search with keyword

Re: Scene name search with keyword