robin.meier

is there a way to know the number of clips present in a track using the m4l api?

is there a way to know the number of clips present in a track using the m4l api?
thank you, robin


number-of-clips-in-track

https://cycling74.com/docs/max5/refpages/m4l-ref/m4l_live_object_model.html

I found has_clip. I'm not sure that's the right thing to use. And I know it will take more than one patcher to get the list of clips. Max isn't straightforward around simple tasks. Not sure if the manual is the best answer in this case, I'd love an example if someone has one.

Here's my initial stab at it, which fails as I can't figure out how to get a list of all clips with has_clip = 1.

Thanks for the manual! However, 
is there a way to know the number of clips present in a track using the m4l api?

I agree with Broc. You should deep dive into the LOM reference and also in the Live API Overview. It is more than worth the effort i would say.

Here is one way to count the number of clips in one track.

Yes. 
I agree with Broc. You should deep dive into the LOM reference and also in the Live API Overview. It is more than worth the effort i would say.

Thank you Len that's exactly what I was looking for. And thanks for the encouragement to study those documents, which I will do in more depth. Still, after looking at your example I feel that's more valuable to me to understand common practices, flow, etc, that isn't included in a patcher-by-patcher description. I think like a lot of programming languages Max has a ton of hidden knowledge and gotchas all over the place. For me, I've been turning the forum and examples to get most of my working knowledge of Max as I also find the documentation very difficult to learn from.

Thank you Len that's exactly what I was looking for. And thanks for the encouragement to study those documents, which I will do in more depth. Still, after looking at your example I feel that's more valuable to me to understand common practices, flow, etc, that isn't included in a patcher-by-patcher description.  I think like a lot of programming languages Max has a ton of hidden knowledge and gotchas all over the place. For me, I've been turning the forum and examples to get most of my working knowledge of Max as I also find the documentation very difficult to learn from.

I'm actually going to confirm this and say that, yes Len thank you, you showed me the solution and I'm grateful for that example. But the number of patches necessary to make this work was a bit astonishing to me. For me to really understand it took a while. Whenever I go to the documentation, I just don't get knowledge. I get descriptions. I want to javascript for most of what I do because that's something that makes much more sense and I can refer to so many more resources. I'm kind of at odds with programming a lot of the time and really it's around this. There are so many functions and little devices out there. But the documentation only covers the alphabet, whereas reverse engineering is one of the few ways that teaches you the words! The tutorials in Max help to know some words, but in real life application, I'm seeing totally different words being commonly used. And by words I mean groups of patches that do certain things. I really want to keep going with Max but it's pretty disheartening that the learning curve is: climb this enormous cliff, then you can check the API!

PS maybe the tools section was supposed to be that. Patch to know how many clips you have on a track: X. Patch to know how to stop a clip: Y. But it turned out to be such a jumbled mess that they stopped supporting it. So I'm only turning to the forum for help because either you have a-b-c or you have actual examples in a semi disorganized forum but based on practicality anyway.

Posting just for reference. Somehow, I'm finding that JS is way more readable and easy. This may not be the most efficient function, but gets the job done in a way I can totally relate to and reuse. I figured out how to use this by looking at JS functions in devices I've picked up from various places.

    var selectedTrackObject = new LiveAPI("live_set view selected_track");

    var selectedTrack = selectedTrackObject.path;

    var trackNumber = Number (selectedTrackObject.unquotedpath.split (' ')[2]);

    log("Track Number:", trackNumber);

    log("Track Path:", selectedTrackObject.path);

    outlet(2, selectedTrackObject.path);

    // GET ALL CLIP SLOTS ON THE TRACK    

    var clipSlotCount = selectedTrackObject.getcount("clip_slots");

    log("Total Clips:", clipSlotCount);

    // GET NUMBER OF CLIPS THAT EXIST

    for (var j=0 ; j<clipSlotCount ; j++) {

        var clip_slot_path = selectedTrackObject.path.replace(/['"]+/g, '')+" clip_slots "+j; //'

        clipSlot.path = clip_slot_path;

        var hasClip = parseInt(clipSlot.get("has_clip"));

            var clip_path = clip_slot_path + " clip";

            var clip = new LiveAPI(null, clip_path);

            hasClipCount = hasClipCount+1;    

    log("Last Available Clip:", clip_path);

    log("hasClipCount:", hasClipCount);    

function getSelectedTrack() {
	// GET SELECTED TRACK DETAILS
	var selectedTrackObject = new LiveAPI("live_set view selected_track");
	var selectedTrack = selectedTrackObject.path;
	var trackNumber = Number (selectedTrackObject.unquotedpath.split (' ')[2]);
	var trackId = Number(selectedTrackObject.id);
	log("Track ID:", selectedTrackObject.id);
	log("Track Number:", trackNumber);
	log("Track Path:", selectedTrackObject.path);
	outlet(0, trackId);
	outlet(1, trackNumber);
	outlet(2, selectedTrackObject.path);

	// GET ALL CLIP SLOTS ON THE TRACK	
	var clipSlotCount = selectedTrackObject.getcount("clip_slots");
	log("Total Clips:", clipSlotCount);

	// GET NUMBER OF CLIPS THAT EXIST
	var hasClipCount = 0;	
	for (var j=0 ; j<clipSlotCount ; j++) {
		var clip_slot_path = selectedTrackObject.path.replace(/['"]+/g, '')+" clip_slots "+j; //'
		clipSlot.path = clip_slot_path;
		var hasClip = parseInt(clipSlot.get("has_clip"));

		if (hasClip==1) {
			var clip_path = clip_slot_path + " clip";
			var clip = new LiveAPI(null, clip_path);
			hasClipCount = hasClipCount+1;	
		}
	}
	log("Last Available Clip:", clip_path);
	log("hasClipCount:", hasClipCount);	
}

Thanks for your code Jay. I am a beginner in all means and despite trying to document deep dive I am struggling with finding solutions. Your getcount("clip_slots") made my day.

"check LOM" ... I'm sorry that's just the most useless reply I've ever heard..

session clips are easily done in the manner explained above, however I have trouble finding some neat way of getting the arrangement clips in specific track.

Trying to write function that makes currently playing clip in arrangement view always focused when in clipview.

im thinking about just checking "is_playing" for every "M" up to 200 or something in "live_set tracks N arrangement_clips M "

should do it but not so nice and what if i have 201 clips (would never though)

im thinking about just checking  "is_playing" for every   "M"  up to 200 or something in "live_set tracks N arrangement_clips M "
should do it but not so nice and what if i have 201 clips (would never though)


Thanks a lot for "getcount". Definitely not documented in the LOM reference, is it

number of clips in track