Announcing Playtime, a Session View for REAPER

[helgoboss]

Originally Posted by klong

I wanted to try this tonight and bought the license (~22 usd) but it looks like it isn't going to work on my M1 Macbook Air, as the plugin is x86_64 only (not Apple Silicon), and it needs to run in "native mode" in REAPER and not bridged, which is the only way to run x86_64 intel plugins on Apple Silicon .. wrote the developer to see if there is any workaround

The workaround for now is to use the x64 REAPER version with Rosetta. Playtime 1 will not get Silicon builds anymore, but ReaLearn (which will be the plug-in on which Playtime 2 is based) has Silicon builds already ... so full Silicon support can be expected as soon as Playtime 2 sees the light of the world.

Originally Posted by biasply

Hi All,
I'm very new to Playtime, but I'm getting it together pretty quickly.
It's a great solution for a replacement workflow using Reaper instead of Ableton.

I have my Launchpad Mini (original) playing clips from the Playtime grid just fine, but there's no feedback at all to my Mini. I can confirm it does the usual boot and shutdown visuals, just nothing while in use in Reaper. I'm sure I'm missing a toggle of some sort somewhere.

Any help, greatly appreciated.

Cheers!

To enjoy feedback in Playtime 1, it's necessary to add a hardware send to your controller (in REAPER's track routing window). That might be the reason. Another reason ... I'm not sure if I added a "Launchpad Mini" preset back then, did I? The "Launchpad" preset might not be compatible with the Launchpad Mini. In that case, you would need to roll your own controller preset as described in
https://www.helgoboss.org/projects/p...own-controller

[biasply]

To enjoy feedback in Playtime 1, it's necessary to add a hardware send to your controller (in REAPER's track routing window). That might be the reason. Another reason ... I'm not sure if I added a "Launchpad Mini" preset back then, did I? The "Launchpad" preset might not be compatible with the Launchpad Mini. In that case, you would need to roll your own controller preset as described in
https://www.helgoboss.org/projects/p...own-controller[/QUOTE]

Thanks @helgoboss, the hardware send seems to be part of it, but it's weird (two red pads and nothing changes when I press something), so I think I have to roll my own. At least this gets me exactly what I need!

EDIT/UPDATE: I wasn't able to find the controller folder in the location specified in the roll your own link, however, checking my install log, I discovered they were installed here: C:\ProgramData\Playtime\controllers. Yes there is one for Launchpad Mini, and it has lights specified in the json. It would seem likely that since i can trigger clips, it must be accessing the controller JSON, but for some reason ignoring the lights/feedback instructions. Weird. I'm gonna keep at it.

EDIT/UPDATE 2: Got lights working about 80% normal, good enough for the functions I need. Colours and behaviour are a bit off, but workable.

[dbonejones]

Hi all,

I'm having trouble editing AUDIO clips recorded in Playtime 1. Whenever I double click on an audio file it zooms to the clip on the timeline and zooms the track, but the clip is not visible, it's hidden somehow.

Everything else seems to work normally. Any insight would be helpful!

Edit: Figured it out, turned off "free positioning" on the track.

[tjaardvandervaalt]

Hello,

I need help with playtime vst. For my use, I need a midi controlled next-scene launcher, like on Ableton. But I can only find the scene-stop button. Is there a launch next scene button or midi function hidden someplace?

Also, I have clips from a previous scene that are supposed to run longer than the scene itself, and continue into the next ones (f.ex., drones). This works fine, but despite the track being in exclusive mode, the clip will not stop eve if I put a silent track in below it. It just goes on. Is there a stop button function, like in Ableton?

And what is the difference between a track and a group, they tend to transform independently of my will...

Thanks!

[mschnell]

Welcome to the Reaper forums !
AFAIK, "Playtime 2" is on it's way.

-Michael

[algx]

Hi
What's the likely release date of version 2? And will there be free updates from version 1?

The reason I ask is because I'm thinking of using it but if version 2 is imminent then I don't want to be left on version 1.

Thanks

[andy79]

Hello,

Is Playtime 2 going to be compatible with Novation Launchpad Pro and the like?

Thanks

[helgoboss]

Originally Posted by algx

Hi
What's the likely release date of version 2? And will there be free updates from version 1?

The reason I ask is because I'm thinking of using it but if version 2 is imminent then I don't want to be left on version 1.

Thanks

Playtime 2 release is not imminent but I plan to send discount codes to Playtime 1 customers that can be used to purchase Playtime 2 for the price difference (so that there's no disadvantage buying Playtime 1 now). Playtime 2 will definitely have a higher price than Playtime 1.

[helgoboss]

Originally Posted by andy79

Hello,

Is Playtime 2 going to be compatible with Novation Launchpad Pro and the like?

Thanks

Yes. Not all controllers will be supported at first, but I will improve support gradually.

[andy79]

Originally Posted by helgoboss

Yes. Not all controllers will be supported at first, but I will improve support gradually.

Great news! Looking forward to the release, thanks for this great app!

[brummbear]

Originally Posted by Doflow

Hi, I noticed this behavior and pinpointed it was introduced in v6.54.
v6.53 works fine.
I don't know which change caused this, but it's kind of annoying, imho.

Any progress on v2 or maybe a small update on v1?

I love Playtime and use it all the time in a pretty mature setup (live looping with a lot of customization scripted around Playtime and ReaLearn). The graphics glitch is quite annoying indeed although it does not affect the actual performance. Has anyone been able to figure out why this happens and if there is anything we can do about it?

EDIT:
So I found out where the problem originates from: It is about 'Media Item Positioning'. Reaper moved the setting which previously was 'show overlapping items in lanes' to the preferences where it is now 'offset overlapping media items vertically'. It is the same thing just with a different name (to avoid confusion with track lanes which is a feature under development). However, the change has lead to the peculiar glitch as seen on the screenshots from daniellumertz https://forum.cockos.com/showthread.php?p=2510913. One way of getting rid of the glitch is to force collapsing of free item positioning in the same preference section 'Media Item Positioning' by e.g. setting the pixel limit really high. But that is of course not desirable if you want to see all items in "lanes" = "vertically offset". Funnily it does work if more than one item is playing in playtime on one track! In that case the items do align properly vertically offset in one single track rather than the red shade all across the screen. But if there is only one item playing then the glitch happens. Whatever happened in the change in Reaper it obviously does not like whatever Playtime communicates via the API when only one item plays on the track. Reaper then miscalculates the proper vertical offset. It only works with multiple items or - of course - if vertical offsetting is suppressed via the first trick.

Neither solution is really satisfactory.

[brummbear]

Yet another update on the graphics glitch. I think what happens is that Playtime "fights" Reaper in the following fashion: Playtime seems to try to achieve what Reaper already does natively now, i.e. displaying the items in "lanes". Playtime does that by configuring a track that stores items (= clips in Playtime language) with 'Free Item Positioning'. It then positions the items in a way that they appear in "lanes", i.e. vertically offset. However, Reaper itself can arrange the items automatically in such a manner. It does that via the settings I was talking about above under preferences (and of course 'Offset overlapping media items vertically' enabled under Options).

There would be multiple ways to solve this problem. E.g. If Playtime would not force 'Free item Positioning' on the tracks (it does so every time when you record, even if you switch it off per track beforehand via right mouse click menu) the problem goes way and you can still enjoy a proper layout by letting Reaper arrange the items as defined in preferences. This would be my preferred way, it would only take a small change in Playtime, i.e. not force this setting.

Wondering if Ben would be willing to do that. I tested by constantly right clicking the track in different scenarios and always disabling 'Free Item Positioning' whenever Playtime sets it to enabled and it works fine. I even prefer the fact that with this one can fine tune the overlap via Reaper's preferences.

[helgoboss]

Originally Posted by brummbear

Yet another update on the graphics glitch. I think what happens is that Playtime "fights" Reaper in the following fashion: Playtime seems to try to achieve what Reaper already does natively now, i.e. displaying the items in "lanes". Playtime does that by configuring a track that stores items (= clips in Playtime language) with 'Free Item Positioning'. It then positions the items in a way that they appear in "lanes", i.e. vertically offset. However, Reaper itself can arrange the items automatically in such a manner. It does that via the settings I was talking about above under preferences (and of course 'Offset overlapping media items vertically' enabled under Options).

There would be multiple ways to solve this problem. E.g. If Playtime would not force 'Free item Positioning' on the tracks (it does so every time when you record, even if you switch it off per track beforehand via right mouse click menu) the problem goes way and you can still enjoy a proper layout by letting Reaper arrange the items as defined in preferences. This would be my preferred way, it would only take a small change in Playtime, i.e. not force this setting.

Wondering if Ben would be willing to do that. I tested by constantly right clicking the track in different scenarios and always disabling 'Free Item Positioning' whenever Playtime sets it to enabled and it works fine. I even prefer the fact that with this one can fine tune the overlap via Reaper's preferences.

Hi brummbaer. To be honest, I can't do Playtime 1 changes at the moment, not even small ones ... or to be more specific, I can't compile/release them. I'm away from home for quite a while and only have my ARM MacBook with me. Even back home, it would be more effort than one might think because I would have to restore the build environment (on Win and macOS). Unfortunately, Playtime 1 build requirements/docs are much worse and old-school compared to that of ReaLearn/Playtime2.

[brummbear]

Originally Posted by helgoboss

Hi brummbaer. To be honest, I can't do Playtime 1 changes at the moment, not even small ones ... or to be more specific, I can't compile/release them. I'm away from home for quite a while and only have my ARM MacBook with me. Even back home, it would be more effort than one might think because I would have to restore the build environment (on Win and macOS). Unfortunately, Playtime 1 build requirements/docs are much worse and old-school compared to that of ReaLearn/Playtime2.

I understand! The change is tiny from a development perspective but the administration around it is a different story. I have a wacky workaround in my specific setup which is CPU efficient because I trigger everything in Playtime via MIDI. Maybe I can come up with a more universal approach that works for others too. It will still be wacky (i.e. likely a running script that periodically checks if Free Item Mode got enabled on specific Playtime tracks just to unset it again). If so, I will publish it here. Anyway, it is more of a nuisance than a deal breaker. Playtime still works with the glitch. Take care.

[brummbear]

So... updated to Reaper v6.77 and the graphics glitch now presents itself in yet another fashion probably due to recent updates when calculating item height etc: Now, when only one item plays on a track it is not visible at all anymore on the timeline. Sigh. The annoying red shade as in previous versions of Reaper is gone, but no item at all is also not great. As soon as multiple items play simultaneously on one track all is good again.

I caved and wrote a script which remedies the graphics problems: "Playtime Whack A Mole Workaround (TM)".
https://stash.reaper.fm/v/46460/Play...Workaround.lua

It runs in the background and is very resource friendly. See code comments for details. What it basically does it puts Playtime under surveillance and squashes "Free Item Positioning" every time when Playtime sets this to enabled.

Reaper Settings for this script to work nicely:
Project Settings -> Item mix behavior = Items alway mix (otherwise Playtime Exclusive Mode = Off won't work as expected)
Options -> Offset Overlapping Media Items Vertically = Enable (simultaneously playing items will be nicely shown on tracks, can be fine tuned under Options -> Preferences -> Appearance -> Media Item Positioning

-- Playtime Graphics Glitch Workaround "Whack A Mole" (TM)
-- Author: brumbear

-- Reaper Settings for this script to work nicely:
-- Project Settings -> Item mix behavior = Items alway mix (otherwise Playtime Exclusive Mode = Off won't work as expected)
-- Options -> Offset Overlapping Media Items Vertically = Enable (simultaneously playing items will be nicely shown on tracks, can be fine tuned under Options -> Preferences -> Appearance -> Media Item Positioning


function main()

    -- Assemble list of tracks that contain Playtime
    -- Scan only one track at a time in each defer cycle (1/30s) for performance reasons
    total_trackcount = reaper.CountTracks(0) - 1
    if total_trackcount >= 0 then
        if i <= total_trackcount then
            -- scan next track
            track = reaper.GetTrack(0, i)
            if reaper.TrackFX_AddByName(track, "Playtime (Helgoboss)", false, 0) > -1 or reaper.TrackFX_AddByName(track, "Playtime Worker (Helgoboss)", true, 0) > -1 then
                pt_trackcount = pt_trackcount + 1 -- tracklist starts with index 1
                tracklist[pt_trackcount] = track
            end
            i = i + 1
        else
            -- reached end of all tracks in project
            delta = total_pt_tracks - pt_trackcount
            if delta > 0 then
                -- shorten list when Playtime tracks get removed
                for j = 1, delta do
                    tracklist[pt_trackcount+j] = nil 
                end
            end
            total_pt_tracks = pt_trackcount
            -- start from beginning
            i = 0
            pt_trackcount = 0
        end
    end
    
    -- Whack a Mole: Every time when Playtime sets Free Item Positioning to enabled unset it again = "whack a mole"
    play_state = reaper.GetAllProjectPlayStates()
    if total_pt_tracks > 0 and play_state > 0 then
        for j = 1, total_pt_tracks do
         if reaper.GetMediaTrackInfo_Value(tracklist[j], "I_FREEMODE") == 1 then
                reaper.SetMediaTrackInfo_Value(tracklist[j], "B_FREEMODE", 0) -- "WHACK IT"
                -- parameter name should actually be "I_FREEMODE" according to API docs. Bug reported here: https://forum.cockos.com/showthread.php?t=276792
                -- reaper.SetMediaTrackInfo_Value(tracklist[j], "I_FREEMODE", 0)
            end
        end
    end
    
    reaper.defer(main)
    
end

tracklist = {}
pt_trackcount = 0
total_pt_tracks = 0
i = 0
main()

[AndreiMir]

Hello, are there any updates planned at all? New versions of Reaper are coming out and some things are no longer working as we would like...

[AndreiMir]

Originally Posted by brummbear

So... updated to Reaper v6.77 and the graphics glitch now presents itself in yet another fashion probably due to recent updates when calculating item height etc: Now, when only one item plays on a track it is not visible at all anymore on the timeline. Sigh. The annoying red shade as in previous versions of Reaper is gone, but no item at all is also not great. As soon as multiple items play simultaneously on one track all is good again.

I caved and wrote a script which remedies the graphics problems: "Playtime Whack A Mole Workaround (TM)".
https://stash.reaper.fm/v/46460/Play...Workaround.lua

It runs in the background and is very resource friendly. See code comments for details. What it basically does it puts Playtime under surveillance and squashes "Free Item Positioning" every time when Playtime sets this to enabled.

Reaper Settings for this script to work nicely:
Project Settings -> Item mix behavior = Items alway mix (otherwise Playtime Exclusive Mode = Off won't work as expected)
Options -> Offset Overlapping Media Items Vertically = Enable (simultaneously playing items will be nicely shown on tracks, can be fine tuned under Options -> Preferences -> Appearance -> Media Item Positioning

-- Playtime Graphics Glitch Workaround "Whack A Mole" (TM)
-- Author: brumbear

-- Reaper Settings for this script to work nicely:
-- Project Settings -> Item mix behavior = Items alway mix (otherwise Playtime Exclusive Mode = Off won't work as expected)
-- Options -> Offset Overlapping Media Items Vertically = Enable (simultaneously playing items will be nicely shown on tracks, can be fine tuned under Options -> Preferences -> Appearance -> Media Item Positioning


function main()

    -- Assemble list of tracks that contain Playtime
    -- Scan only one track at a time in each defer cycle (1/30s) for performance reasons
    total_trackcount = reaper.CountTracks(0) - 1
    if total_trackcount >= 0 then
        if i <= total_trackcount then
            -- scan next track
            track = reaper.GetTrack(0, i)
            if reaper.TrackFX_AddByName(track, "Playtime (Helgoboss)", false, 0) > -1 or reaper.TrackFX_AddByName(track, "Playtime Worker (Helgoboss)", true, 0) > -1 then
                pt_trackcount = pt_trackcount + 1 -- tracklist starts with index 1
                tracklist[pt_trackcount] = track
            end
            i = i + 1
        else
            -- reached end of all tracks in project
            delta = total_pt_tracks - pt_trackcount
            if delta > 0 then
                -- shorten list when Playtime tracks get removed
                for j = 1, delta do
                    tracklist[pt_trackcount+j] = nil 
                end
            end
            total_pt_tracks = pt_trackcount
            -- start from beginning
            i = 0
            pt_trackcount = 0
        end
    end
    
    -- Whack a Mole: Every time when Playtime sets Free Item Positioning to enabled unset it again = "whack a mole"
    play_state = reaper.GetAllProjectPlayStates()
    if total_pt_tracks > 0 and play_state > 0 then
        for j = 1, total_pt_tracks do
         if reaper.GetMediaTrackInfo_Value(tracklist[j], "I_FREEMODE") == 1 then
                reaper.SetMediaTrackInfo_Value(tracklist[j], "B_FREEMODE", 0) -- "WHACK IT"
                -- parameter name should actually be "I_FREEMODE" according to API docs. Bug reported here: https://forum.cockos.com/showthread.php?t=276792
                -- reaper.SetMediaTrackInfo_Value(tracklist[j], "I_FREEMODE", 0)
            end
        end
    end
    
    reaper.defer(main)
    
end

tracklist = {}
pt_trackcount = 0
total_pt_tracks = 0
i = 0
main()

Great, I'll try it now!!!

[AndreiMir]

https://gifyu.com/image/S7oF4
How to make a midi recording without repeated silence before and after recording? I tried to change the settings, but it still works

[krahosk]

Originally Posted by helgoboss

Hi brummbaer. To be honest, I can't do Playtime 1 changes at the moment, not even small ones ... or to be more specific, I can't compile/release them. I'm away from home for quite a while and only have my ARM MacBook with me. Even back home, it would be more effort than one might think because I would have to restore the build environment (on Win and macOS). Unfortunately, Playtime 1 build requirements/docs are much worse and old-school compared to that of ReaLearn/Playtime2.

With the same honesty, will PLaytime 2 be available for Linux?

[TonE]

Yes, it is built into realearn already. You can use it now. Only without any gui. Headless playtime or clip engine.

[deseipel]

hi there, I use Playtime to trigger mostly one-shot video samples. The issue I'm seeing is that if I'm using an arpeggiator, the video is triggered correctly but the cpu usage jumps to 40-50% in some cases (but not always). Lowering resolution seems to help a bit. Any ideas?

I suspect this is more of an issue with how video is decoded rather than how Playtime is handling it. If Reaper supported the HAP codec and preloading videos, then the cpu wouldn't have to work as hard since HAP is decoded on the GPU.

[brummbear]

Recording of clips breaks with V7.10, see

https://forum.cockos.com/showthread.php?t=288171

EDIT: Problem will be solved in Reaper 7.11 (see details in linked thread if you are interested). For those using Playtime 1 and recording audio clips you should use Reaper 7.09 or earlier until 7.11 gets released.

Playtime 1 is still going strong in my opinion, amazing capabilities especially as a live looper.

[Ape_Din]

any news? still waiting for version 2

[helgoboss]

Originally Posted by Ape_Din

any news? still waiting for version 2

Feel free to join the early-access testing (write to info@helgoboss.org).

[JanPieter]

hi guys,

new user here. I just bought playtime, but reaper only seems to see the worker vst. it doesn't see playtime vst, nor is the template there. I saw similar problems upthread, but I'm not sure what to do.
can anybody help or point me in the right direction?

thank you!

[AtmanActive]

Novation Launchpad Mini MK3 with Helgoboss PlayTime:


Step 1: Download and unzip this file to your folder REAPER/Playtime/controllers

launchpad-mini-mk3-legacy.zip

Step 2: Put your Launchpad Mini MK3 into Legacy mode by holding the [Session] button for 2 seconds and then, when the pad "screen" changes, press the pink [>] button. Then press [Session] again to exit the setup. Your Launchpad Mini MK3 is now in Legacy mode.

Step 3: Start Reaper and Playtime and choose "Launchpad Mini MK3 in Legacy Mode" as your controller.

Step 4: Enjoy.


If you would like to change the colours, edit the file launchpad-mini-mk3-legacy.json and change the numbers under the "lights" section. Pads can not have the Reaper item colours as that functionality is not supported by Playtime (yet). The only colour-coded-states supported are: "almostPlaying", "almostStopping", "empty", "playing", "recording" and "stopped".

[AtmanActive]

@helgoboss: why are scenes row-bound?

That's a bit of a letdown for me.
I honestly expected that each scene internally saves the play state of each of 64 slots.
The fact that they are just row-play shortcuts is ... wasted potential?

Here is my biggest grievance with it: if I spend time adding my clips to a group, then, in my mind they are mapped 1, 2, 3 as some kind of a logical progression. But now, if I want to save my currently playing state to Scene 4, for example, PlayTime copies my slot from 1, 2 or 3 into 4, adding a completely unnecessary new slot which I never wanted or neededed in the first place. In other words, the way Scenes are working right now, they are just making a mess in my slots. This forces me to have to remember that slot 4 is a duplicate of some other slot which is there just to satisfy a row-bound-scene-playback and is otherwise not useful at all on my grid.
The fact that we can't propagate reaper item colours onto the pads makes this so much worse.
I mean, what good are Scenes if they have to mess up my grid in order to work?

I have never touched Ableton and I have no idea how it works, but this scenes-are-just-row-play design decision is ... "highly illogical, captain".

Any plans for future versions or, any settings hack to escape this constraint? Any way I could make scenes just simply memorize the matrix play state without having to copy my clips/slots?

Thanks.

[helgoboss]

Originally Posted by AtmanActive

@helgoboss: why are scenes row-bound?

That's a bit of a letdown for me.
I honestly expected that each scene internally saves the play state of each of 64 slots.
The fact that they are just row-play shortcuts is ... wasted potential?

Here is my biggest grievance with it: if I spend time adding my clips to a group, then, in my mind they are mapped 1, 2, 3 as some kind of a logical progression. But now, if I want to save my currently playing state to Scene 4, for example, PlayTime copies my slot from 1, 2 or 3 into 4, adding a completely unnecessary new slot which I never wanted or neededed in the first place. In other words, the way Scenes are working right now, they are just making a mess in my slots. This forces me to have to remember that slot 4 is a duplicate of some other slot which is there just to satisfy a row-bound-scene-playback and is otherwise not useful at all on my grid.
The fact that we can't propagate reaper item colours onto the pads makes this so much worse.
I mean, what good are Scenes if they have to mess up my grid in order to work?

I have never touched Ableton and I have no idea how it works, but this scenes-are-just-row-play design decision is ... "highly illogical, captain".

Any plans for future versions or, any settings hack to escape this constraint? Any way I could make scenes just simply memorize the matrix play state without having to copy my clips/slots?

Thanks.

Could be illogical for your taste/workflow, but in general it isn't. That's the way it has been in Ableton from day one and all follow-up session views copied this design as far as I know. I think the rationale is that the user can immediately see which scenes contain which clip. If you think about scenes as different parts of a song, this is in fact a very intuitive visualization.

That said, KISS designs are not always the right fit. I also found this design restrictive for some advanced scenarios. That's why Playtime 1 (and 2) has an alternative to scenes, that comes very naturally due to the fact that they are VST instruments:

1. Create a MIDI clip in a column.
2. Route the column to Playtime itself.
3. With the right MIDI assignments, this MIDI clip can now play arbitrary clips of Playtime, no matter the row.

This approach is not as streamlined as scenes and also has some drawbacks, but I'm looking into improving this for Playtime 2 in the future. Playtime 2 has been in development for a long time and is currently in alpha testing (in case you haven't heard yet). Write to info@helgoboss.org if you want to join.

For Playtime 1, this approach probably conflicts with your device

BTW, Playtime 2 brings support for projecting clip colors to devices, powered by ReaLearn.

[AtmanActive]

Woohoo, great news, looking forward!

Yes, if clips have colours, and those colours are propagated to the launchpad, then, I can see how scene-as-a-row-play can be useful; the simple per-row-scene-arrangement is then visible right on the pads. But, without it, my brain can't keep track of what clip was on A1 or A2 or A3, and now, all of a sudden, copied to A4 just because of the scene.

There could be, an interim solution in colouring the clips/pads where Playtime wouldn't necessarily have to follow the item colours from Reaper, but could internally keep track of which one was assigned/loaded/recorded (but not copied!) to which slot and could then expose those in the json as "stopped_1", "stopped_2", "stopped_3", "stopped_4", "stopped_5", "stopped_6", "stopped_7" and "stopped_8". Then, the JSON creator could just set 8 different colours for those and that's it. Rationale here being that I don't really care that much about how my items are coloured in Reaper. What I do care about is which clip is which on my pad grid. So when a scene action copies my clip, for example A1 to scene 4, I can see by the pad colours that slots, for example, A1 and A4 have the same clip inside.

Of course, having direct translation between Reaper item colours and pad colours make the management of all this much, much easier and straight forward.

Thanks.

[AtmanActive]

Originally Posted by helgoboss

1. Create a MIDI clip in a column.
2. Route the column to Playtime itself.
3. With the right MIDI assignments, this MIDI clip can now play arbitrary clips of Playtime, no matter the row.

Yes, this is a great idea.
Use any group (presumably the 8th) to play MIDI clips re-routed back to Playtime to create my own MIDI-controlled scenes. So a clip can become a scene.
Ingenious!
Thanks!