Announcing Playtime, a Session View for REAPER

[helgoboss]

Dear REAPER users,

for those of you who want a Session View à la Ableton Live in REAPER: Now there is one. It's called Playtime. Technically, it's a VST instrument that makes heavy use of REAPER's awesome extension API.

Playtime is available here (http://www.helgoboss.org/projects/playtime/). Please check it out and let me know what you think. Would appreciate any feedback :)

Cheers
Ben

http://www.helgoboss.org/projects/playtime/slide-non-invasive

[Viente]

Video "in action" would be great ;)

[gwok]

need osx asap!!! :)

[EpicSounds]

This looks pretty awesome and a feature many have been asking for
I also hope OSX version is not too far off.

Benjamin, please get in contact with me via email audiogeekzine[at]gmail.com

[Commala]

Thank you, this is outstanding! Great work, and just what I was looking for.

[Breeder]

Insane! Great job!

[unique]

Away from DAW at the moment. Looks like a handy tool though. If it has a good impact on workflow ill definitely give it a go.

[rjshama]

This looks very interesting but 30 minutes is not enough playtime. Considering how Reaper handles it's trial version you might want to rethink that. You're not asking for much money so that may not be an issue for Reaper users who don't want to chunk out $500 for Live.

Nice work!

[gwok]

this looks awesome!!

[nathanj]

Wow! This does look amazing. I'm continually amazed at the depth of REAPER and it's community.

Eagerly awaiting the OSX build!

[gwok]

Why is it not recommended to leave anticipative fx on and media buffering? I rely heavily on this.

Can it be left on and still have stable playback? A little less than instantaneous triggering is fine.

[sinkmusic]

This seems like an amazing plugin : congratulation for your creation !
Being able to use a midi controller with it is great.

Did you talk to Cockos before releasing it into the wild ?
I'm just asking, as i wish that such a beautiful and useful feature would have been natively integrated into Reaper (instead of being a 3d party vst). Maybe that, just like with Elastique, they could have been interested into licensing it, or find a deal with you to straightly embed it into Reaper ?

[sinkmusic]

msvcr120.dll error is shown at startup (Reaper64bit, win7)

[sinkmusic]

PS : Is there a printable PDF manual somewhere ?
After installation, i don't see any in the VST plugin folder (neither in "start menu > playtime").

[pipelineaudio]

Interesting!

[Win Conway]

Didn't install the track template as mentioned in the instructions, besides that it is a one stop shop i guess, all this can already be done in Reaper using SWS actions (because i already have it set up, SWS seems much easier to me personally) i will test more and see if anything jumps out as new and exciting though ;)

For me, this should have been built in to the project bay from day 1, the project bay may have had some use !

[helgoboss]

Thanks everyone for your feedback and nice words! This is encouraging :)

@Viente
My plan is to create some tutorial videos this month.

@gwok @EpicSounds @nathanj
OSX support is on the very top of my priority list.

@EpicSounds
Looking forward to get in contact with you.

@Commala @Breeder @unique
Thank you!

@rjshama
Thanks for the input. When the 30 minutes are over, you can always remove Playtime from the FX chain and add it again. I can understand though that if you want to evaluate a large setup with many clips that 30 minutes is too little. Rethinking ... :)

@gwok
Yes, you can tell Playtime not to mess with the track's anticipative FX and media buffering settings if you are fine with the triggering latency (Playtime preferences). In that case you can still reduce the global media buffer size in the REAPER preferences to tune the latency.

Please note that Playtime turns off anticipative FX and media buffering just for the tracks which have Playtime clips, not globally. I think most of the times, users want instantaneous clip triggering. That's why it is the default setting.

During my tests I didn't experience any lags with that default setting. I didn't test with SSD only, also with an external USB2 5400rpm hard disk. Same result. That's why I recommend sticking to the Playtime default setting.

@sinkmusic
Thank you! Infact I tried to contact Cockos some months ago to talk about that but they were probably busy :) Then I was thinking it's not that bad to have it as an optional plugin because not everybody needs a session view and is willing to pay for it. So I moved on.

Thanks for spotting the missing DLL. I'm working on a bugfix release. Installing the Visual C++ Redistributable Packages should fix it: http://www.microsoft.com/de-de/download/details.aspx?id=40784.

Right now there's no offline PDF manual, just the online user guide (http://www.helgoboss.org/projects/playtime/user-guide). But it's a no-brainer to provide that. I created a ticket (https://bitbucket.org/helgoboss/playtime/issue/29/offline-pdf-manual).

Ben

[Lazarus]

Very nice, great work - just bought it. One teeny weeny thing that would be great to see would be having an option to insert an empty MIDI clip in a slot. Oh, and being able to rename the Groups independently of the tracks they are assigned to.

Cheers!

[sinkmusic]

I think the installer is a bit strange : first, it ask where you want to install the 32bit, then it ask where you want to install the 64bit version, then it asks you if you want to install both : why not asking first, once and for all which version to install ?
It might be less confusing...

[sinkmusic]

Right now there's no offline PDF manual, just the online user guide (http://www.helgoboss.org/projects/playtime/user-guide). But it's a no-brainer to provide that. I created a ticket (https://bitbucket.org/helgoboss/playtime/issue/29/offline-pdf-manual).
Thank you.
The good thing with PDF is that it is more easy to take on a USB stick, to print, or to put in Reaper Documentation folder (and then it can be opened directly from within Reaper, just like Reaper manual).

[G-Sun]

Playtime is available here (http://www.helgoboss.org/projects/playtime/). Please check it out and let me know what you think. Would appreciate any feedback :)
Cool! Thanks!

[gwok]

do you think it'd be viable to instead of moving the items to the beginning of the project, to be able to set the media items offline and retain their placement?

(Offline is advantageous over muting items I think, because mute states are retained when the items are returned online.)


Though maybe there's some technical reasons why you chose to move them as opposed to other methods?

[sinkmusic]

Or to create a copy of the original projet as a new tab (i don't know if it would be possible, though) ?

[Sunaj]

question : can you time stretch individual notes or blocks? if so i'm almost sold

[Jed]

Fantastic development! - no more using Live to jam in Ninjam :)

Thanks heaps for your efforts here Ben

Cheers
Jed

[plamuk]

thank you.

[Alex Ortega]

Dear REAPER users,

for those of you who want a Session View à la Ableton Live in REAPER: Now there is one. It's called Playtime. Technically, it's a VST instrument that makes heavy use of REAPER's awesome extension API.

Playtime is available here (http://www.helgoboss.org/projects/playtime/). Please check it out and let me know what you think. Would appreciate any feedback :)

Cheers
Ben

http://www.helgoboss.org/projects/playtime/slide-non-invasive
Cool! Thanks!

[Xenakios]

Interesting product, I wish the developer the best success!

[helgoboss]

Just released Playtime 1.0.1. The installer should be less confusing now and the problem with the missing "msvcr120.dll" should be gone. Thanks @sinkmusic for reporting both issues!

BTW, it would be outstanding if you guys could report issues and propose new features here (https://bitbucket.org/helgoboss/playtime/issues?status=new&status=open). Then it's easy for me to keep track of them and you can be notified about progress. If you register, you can even vote for feature proposals.

@gpunk_w
Thanks for trying it! I've not stumbled upon the track template issue yet. Do you mind sending me the contents of your "C:\Program Files\Playtime\InstallationLogFile.log"? Then I might be able to find the cause.

@Lazarus
Congratulations, you were the first buyer :) I just created tickets for the MIDI clip (https://bitbucket.org/helgoboss/playtime/issue/32/option-to-insert-an-empty-midi-clip-in-a) and group renaming (https://bitbucket.org/helgoboss/playtime/issue/33/possibility-to-rename-groups-independently) proposals. Would be very nice to keep the discussion regarding these proposals in the ticket system.

@G-Sun @Jed @nym @Alex Ortega @Xenakios
Many thanks!

@gwok
I chose stowing away the non-playing clips to the beginning of the track so they are in one place and not distributed all over the timeline. That way, users can still access them and modify them without having to open Playtime.

I chose moving for triggering the clips because it can be done in realtime (didn't want to mess with the track state chunks, I think that might take too long).

Setting the non-playing clips offline vs. muting them might be an option I didn't look into it yet. Any idea how to achieve that using the API?

@sinkmusic
Not sure I understand what you mean by "Or to create a copy of the original project as a new tab". Can you elaborate? Maybe I'm missing some context information here :)

@Sunaj
Playtime works on item level. If necessary, it stretches the item and thus all notes within the item (if it's a MIDI item). To be fair, REAPER does the actual stretching :) Playtime just tells REAPER to do so. What do you mean by "block"?

[EvilDragon]

@gwok
I chose stowing away the non-playing clips to the beginning of the track so they are in one place and not distributed all over the timeline. That way, users can still access them and modify them without having to open Playtime.

I chose moving for triggering the clips because it can be done in realtime (didn't want to mess with the track state chunks, I think that might take too long).

Might it be implemented as an option to leave the items where they are? (Isn't that how Live is actually working?)

Other than that, this is a very commendable effort! Congratulations. :)

[Sleep opposed]

Looking forward to trying this out...im sure this is going to attract a shitload of interest, great job!

[sinkmusic]

@gwok
I chose stowing away the non-playing clips to the beginning of the track so they are in one place and not distributed all over the timeline. That way, users can still access them and modify them without having to open Playtime.

I chose moving for triggering the clips because it can be done in realtime (didn't want to mess with the track state chunks, I think that might take too long).

Setting the non-playing clips offline vs. muting them might be an option I didn't look into it yet. Any idea how to achieve that using the API?

@sinkmusic
Not sure I understand what you mean by "Or to create a copy of the original project as a new tab". Can you elaborate? Maybe I'm missing some context information here :)
I was just thinking out loud, without tring Playtime yet ;)
I meant : If Playtime moves the items to the beginning of the project, in order not to screw my project, it might be a solution to silently create an archive otthe project in the existing state, in a new project tab.

For instance, i have made a song, and i am pretty much happy with it as it is. The structure is done, and it can be considered as "finished"
But, after a while, i can suddenly want to jam with it, or create an alternate/extended version on the fly : so, Playtime gets into action, but, i wouldn't want (after a great playtime which i will ant to keep also as a new version of my "song") to lose my song in the state it was before being "playtimed"... So, having a "ghost" version autmatically created in a new Project tab when i start messing aroud with Playtime would avoid losing a song. Does it make sense ?
(sorry if i missed something obvious, again, i'm just thinking out loud)

Again, i am still mesmerized by the existence of Playtime, and i wish it could be natively integrated thightly into Reaper ;)

[BenK-msx]

looks v cool,
regarding moving items, easiest seems to have option to copy rather than move, potentially rippling main project forward in time so its all still there 'or something' ;)

now to hunt down my under-used loops and give this a try.

[helgoboss]

@EvilDragon @sinkmusic @BenK-msx

Well, the clips (= items which are under Playtime's control) are not supposed to stay where they are. They are meant to "wander". All other items (non-clips) are there to stay. Playtime never touches them. If you hit the "Write" button, all the written items will remain in place, not messed up by Playtime.

So I think what you're worried about is the clip loading feature. What I can offer is a new way of loading items into Playtime so they become clips: "Fill with copy of selected item". Instead of moving the item itself, Playtime would copy it and move the copy to the start of the timeline. What do you think? @BenK-msx Maybe this is what you were suggesting?

[sinkmusic]

Ok, i just tried it quickly, and this thing is wonderful, it's a blast, i'm loving it !
I really wish Cockos can see how fun and powerful and efficient such a tool is.
http://i.imgur.com/nD8JO9X.gif

The new installer works fine now (Win7, 64bit, and no more xmqlsjhfdg172.dll missing).

FR :
- being able to rename the groups ;
- being able to copy a clip from a scene into another (like in Live) ;
- being able to copy/paste a scene into another scene ;
- having (like in Live) the Ability to define a play mode (like : "play 2 times and then go to the clip below/above" or "play once and go to a random clip" or "play once and stop", etc).

[helgoboss]

Hi Alex,

do you run 64-bit REAPER? Looks like REAPER tries to load Playtime 32-bit in REAPER 64-bit (bridging mode). Or the other way around, not sure. Playtime doesn't work in bridging mode. The VST path in REAPER is probably not set correctly.

Please have a look in section "1 Installation" of the user guide (http://www.helgoboss.org/projects/playtime/user-guide).

[Lazarus]

does not work
You need to use the 64 bit version so that it runs in the same process as Reaper because you are running the 32 bit version bridged. This means it's technically not running in Reaper, but a thing called reaper_host32. Make sure you set the 64 bit directory correctly when you install Playtime.

[Alex Ortega]

You need to use the 64 bit version so that it runs in the same process as Reaper because you are running the 32 bit version bridged. This means it's technically not running in Reaper, but a thing called reaper_host32. Make sure you set the 64 bit directory correctly when you install Playtime.

thanks, works)

[Nixon]

This looks very promising :) Count me in when OSX version arrives.
Highly appreciated.
Regards

[PitchSlap]

This looks pretty neat, though I have mixed feelings as I hope it doesn't prevent native implementation of this long-awaited functionality.

Any chance of implementing something like Live/Bitwig's follow actions? That's a pretty important feature in my experience.

I also think it would be nice to have better undo support in the future. I'll be following this closely and highly considering a purchase.

Great job!

[plamuk]

Any chance of implementing something like Live/Bitwig's follow actions? That's a pretty important feature in my experience.

I also think it would be nice to have better undo support in the future.


seconded. follow action are a must, and i had some weird undo stuff happen

I'll be following this closely and highly considering a purchase.

i've been in such need of this feature (and for so long) that i bought it before even trying it.

[Jed]

LOL me too :)

[Viente]

This looks pretty neat, though I have mixed feelings as I hope it doesn't prevent native implementation of this long-awaited functionality.

Actually i hope it will. There are more important things to be done. Fix a lot of bugs left and polish all theese great features its already has. No need for another half-baked feature. We have ableton live and bitwig which are great for this task. I'd better see implementation of long awaited editing features and new modern UI. Just my 2 cents...

P.S. I always wonder if people need session view so badly, why they choose Reaper over Ableton Live and Bitwig?

P.P.S. Great work helgoboss! Another good example how flexible and customizable Reaper can be!

[gwok]

ok, checkin this out on parallels.

so is one meant to dedicate 8 tracks in reaper for playtime playback? Because although this is super cool, right away I wonder if all sorts of data can possibly get over written. I'm running a really primitive setup in paralells though, so I can't run any projects I'm familiar with to get an idea how it works, but it seems to me playtime wants to just charge ahead and overwrite anything anhead of it. Hence I wonder if it's meant to have 8 tracks dedicated to it.



Also, I notice playtime always disables looping, which is kind of what I want it to be able to do. I mean, is playtime meant run on an indefinately long timeline (hence overwriting as it goes along), or is also possible to work in sections/regions/loops as well.

It seems to me that working on a section/region in reapers arrange while running loops in Playtime along with it isn't really all that functional right now? or am I missing something? Why is it starting on bar 2 all the time?


this looks wicked, just trying to get my head around it and get an idea of the intended workflow

cheers!

edit: ok, i see nothing is getting over written, though I am still wonderig how one is meant to work within the form of an arrangement, having Playtime cycling loops within the section of a song. PLaytime seems to want to start playback from bar2, so right now to work within a specific section, i have to start reaper first - ahead of the bar, trigger the loops to start with the beginning of the section, the re-enable cycle/loop. I can't just seem to drop the play marker on a bar, and hitplay on a clip in playtime and have playback start at that time, with the loop.

[rvman]

It sure looks better than Ableton. LOL. I don't think I need this now but I might later at some point. Thanks for your work. Bravo.

[Jed]

Ben,

Please please please provide a midi cc mappable button that will allow us to record into whatever slot is currently selected (as per Live 9)

This means you can record on the fly without having to click with the mouse on the individual slot record button before and then after recording the loop (which is a total workflow killer)

Also if you click on this button to end your slot recording, the clip should automatically enter play mode so you can hear what you just recorded straight away (as in Live)

Cheers
Jed

[sinkmusic]

[...]I hope it doesn't prevent native implementation of this long-awaited functionality.
+1 !
Cockos, do you hear us ? it's been a FR for a while, and now we have a very good and working first step in the right direction... It's quite exciting, but nothing beats proper native integration ;)

[todd_r]

Wow! This looks amazing. Can't wait to try it out. Fantastic someone took the initiative on this

[Lawrence]

Exceptionally clever. :)

[jpchartrand]

WOW! This is amazing. I want it on OSX!

[BenK-msx]

had a little fun with this yesterday - few observations .

its good. ;)

heres an FR!:
(you realise developing anything for reaper means users expecting cockos/sws/s&m-like delivery on updates and FRs! ;) )

--------

*looper-like functionality*:

e.g switch a group to a looper 'mode' -

1st slot's (rounded) length sets the length of the subsequent slots, (or is set manually) with option of multiples of that length for subsequent slots.
recordings are punched in and out at that length.
exclusive mode off so all clips can play out.
recorded clips start playing automatically.

possibly auto fill slots per loop-pass:
e.g one pass occupies slot 2, 2nd pass occupies slot 2, previous pass moves to occupy slot 3 etc.

combined with regular existing behaviour of groups/scenes could be pretty powerful if feasible.


seems the difficulty of achieving what you have already is way harder than adding such capabilites!

-
anyones thoughts on the above would be welcome..


more general request:

ability to route/output (i.e move) a clip to a different track from the playtime GUI. for example r-click clip > select a track. item is moved and therefore is routed through different track.

seems we have to select a record track at the actual moment of recording a clip, this should be set first so we can hit record and actually record straight away. you prob know that.

thanks for any consideration and the efforts.

[PitchSlap]

Actually i hope it will. There are more important things to be done. Fix a lot of bugs left and polish all theese great features its already has. No need for another half-baked feature. We have ableton live and bitwig which are great for this task. I'd better see implementation of long awaited editing features and new modern UI. Just my 2 cents...

P.S. I always wonder if people need session view so badly, why they choose Reaper over Ableton Live and Bitwig?


As great as this is and as happy as I am to see it, it can only ever be a "half-baked feature" compared to what Cockos could do natively (I'd love to be proven wrong), and based on your logic, no DAWs should ever advance and implement innovative features from each other.

Why would I want this in Reaper when I could just go spend another $800 on Ableton Suite or $450 on Bitwig just to lose all the great unique things Reaper has to offer? No thanks, I think I'll keep hoping Cockos finally includes this much requested functionality that nearly every DAW geared towards modern music production has added in one way or another.

Not everyone has the same wants and needs, but I'd be pretty disappointed to see Cockos ignore this to spend more time on a "new modern UI" when they already spend god knows how much time on WALTER for 4.0 and there are dozen's of themes and customizations to chose from. Why should they waste time on that? If a "modern UI" is so important to you, go buy the DAW that already has one, and if you want more editing features, just go buy a Pro Tools rig. ;)

[mehmethan]

I was looking for this for a long time. Thanks for this great plug-in. It works perfectly here :) :) :)

Just a FR :

is it possible to add show/hide for settings under the session view. So plug-in will have a smaller view which is nice for laptops

[plamuk]

more important things to be done

subjective. conversely to what you proposed, why would one want "long awaited editing features" or a "modern ui" when they're already apparently available in other hosts that are for whatever reason less desirable to whomever? as are the features others want?

continuing the subjective trend, the most "important thing" is having a host which i can use to produce and perform. i am forced to advocate for anything that advances that, at the hypothetical expense of other features

that said, i don't know if whether or not it's native is ultimately that important. for better or worse, the midi editor is an extension. it's all about how well it's folded in, sometimes with some unexpected benefits along the way (see playtime's user guide). playtime will evolve and improve if it has support commercially and continued support from the reaper API

sws is not native, but i can't tell the difference. off planet mining.

[helgoboss]

@sinkmusic and all other feature requestors
Please use the issue tracker (https://bitbucket.org/helgoboss/playtime/issues?status=new&status=open) to propose the features. You don't have to register there, so just one click on the "Create issue" top right on the screen. Thanks!

@PitchSlap
About the follow actions: Please also propose it on the issue tracker. I will consider it if it gets a reasonable number of votes. Currently, it's not on the top of the list because it's not that trivial to implement and I want to fix/add the things first that hurt most.

Better undo support is already on my list.

@gwok
You don't have to dedicate 8 tracks for Playtime playback. Playtime is very flexible concerning the tracks. It's not like in Ableton where each column corresponds to one track. You can have all 64 slots trigger items in one track (one extreme). Or you can have 64 slots trigger items on 64 different tracks (the other extreme).

The looping (cycle mode) is disabled whenever you start triggering a clip because Playtime achieves the looping by extending the items and the traditional cycle mode would get in its way. The looping in Playtime is more powerful than the one you get by simply enabling cycle mode. You see, every clip can have a different number of bars. In cycle mode, this fact will be just ignored. All clips will be repeated after the same amount of time. In Playtime, each clip is repeated according to its length.

Nonetheless I'm planning to support cycle mode in future - of course with restrictions because naturally these two approaches of looping don't fit.

Oh, and nothing will be overwritten on the timeline. The reason why Playtime always starts at bar 2 in your case is that your project ends on bar 2. The rational behind this is the following: If transport is stopped and I trigger a clip, I expect only that clip to be played and nothing else which is already on the timeline. I think that's also the case in Live, isn't it? So Playtime just seamlessly jumps to the end of the project where it has empty playground. If you want to "jam" along with the items already on the timeline, you just hit the normal REAPER play button and then trigger clips in Playtime.

@Jed
The first feature you requested should be very easy to implement. Please propose it on the issue tracker (https://bitbucket.org/helgoboss/playtime/issues?status=new&status=open). The second feature is already on the list :)

@BenK-msx
Interesting ideas here! Please also use the issue tracker (https://bitbucket.org/helgoboss/playtime/issues?status=new&status=open).

@mehmethan
Not possible yet to hide parts of the GUI. That's a candidate for the issue tracker (https://bitbucket.org/helgoboss/playtime/issues?status=new&status=open) again :)

@all
Thanks for the feedback and praise.

Ben

[jpchartrand]

What is the target release date for mac osx? Just so I can stop checking this thread 1000 times a day lol

[fixerdave]

@mehmethan... you can drag the window so the bottom is off the screen leaving just the top visable, a workaround but usable dave

[gwok]

If transport is stopped and I trigger a clip, I expect only that clip to be played and nothing else which is already on the timeline. I think that's also the case in Live, isn't it?


I will take more detailed discussion to the issue tracker, but to be clear, no, that is not how ableton works. Ableton will play both the session view and the arrangement together, and triggering a clip in session view will still play any audio from the arrangement view along with it, so long as the relevent track is set to play audio from the arrange view.

Now obviously were not going to get the exact same behaviour as Live, although certain aspects are very beneficial. As I say, I'll take more details to the issue tracker, but I think it would be a shame not to have a tightly integrated flow with both Playtime clips and Reapers arrangement view in terms of sections/regions and arrangements. I think the case usage of a person wanting to jam out indefinately versus wanting to work on specific sections in an arrangement is probably much less (imo). I may speak for myself, but one of the main advantages of Live is not just being able to have loops of different lengths, but being able to utilize them if one chose to within the context of an arrangement.

[MotionMindz]

This is super great as a development... BUT 3 things to mention:

1. there are also a lot of MAC users. Why are they left behind?!
I so hope this gets done soon asap. VST before AU if you please.

2. each loop needs to be individually editable in loop length: 1,2,4,8 bars etc

3. each loop needs to be midi/CC controllable (triggers)


Of course, we must be able to edit each loop by double clicking on it.
For the rest, full marks, cant wait for it!


EDIT: COCKOS needs to implement something like this fully native in Reaper 5. Cockos, are you listening?

[jpchartrand]

Cockos, are you listening?

And....+1

[sonnie]

EDIT: COCKOS needs to implement something like this fully native in Reaper 5. Cockos, are you listening?

Would be fair by Cockos to buy his idea and make him rich. ;)

[helgoboss]

Short reply concerning Mac OS X: I'm working on it these days, top priority. All other feature requests need to wait. It's hard for me to name a release date though. My guts tell me, I will have it ready in early December. It's not my intention to discriminate against OS X users :) It's just I'm a Windows guy so I finished and released the Windows version sooner.

Thanks for your patience.

The OS X ticket is here (https://bitbucket.org/helgoboss/playtime/issue/14/os-x-support). You can register at Bitbucket and watch the ticket (there's a watch button) in order to be notified about updates by email. Then you also don't need to check this thread 1000 times a day ;)

[sinkmusic]

Then you also don't need to check this thread 1000 times a day ;)
I understand that for you it might be easier to use bitbucket, and i have made a couple of FR there.
But for discussing about features, it seems more easy for Reaper users to discuss this on the Reaper forum, than having to register, login, and follow another forum, isn't it ?

[Vendetta V]

OSX ?!?!?!?

[jpchartrand]

OSX ?!?!?!?

+9999

[EvilDragon]

Guys, read what the developer wrote. Don't just mindlessly +1 posts.

[jpchartrand]

I don't think it hurts anyone if we show excitement for an OSX release...

[Breeder]

Guys, read what the developer wrote. Don't just mindlessly +1 posts.

+1
:D

[Argle]

Guys, read what the developer wrote. Don't just mindlessly +1 posts.

yeah, at least +2 them.

[vanhaze]

Many thx for this but OSX FTW please !

[EpicSounds]

wow never knew there were so many OSX users... So many that can't read OSX support is already top priority.

[jpchartrand]

wow never knew there were so many OSX users... So many that can't read OSX support is already top priority.

I really hope OSX becomes a priority

[EpicSounds]

I really hope OSX becomes a priority

Post #64 (http://forum.cockos.com/showpost.php?p=1428053&postcount=64)

[EvilDragon]

Mac users really can't read, it seems. :D

[edkilp]

No doubt! My god it's one of the first things he said! Bunch of illiterate whiners, you OSX people! Hahaha! Just kiddin of course, but it probably doesn't speed things along by clogging the thread with repeated desires and +1's for OSX support. Cool things come to those who chill.

[jpchartrand]

Just kidding guys of course I saw that it was a priority. Geez...what's wrong with getting excited about software?

[jpchartrand]

It is better if Justin or Cock Corporation gets excited about this feature.

hahahaha indeed

[todd_r]

Hello Helgoboss

Just wondered why it was implemented as a VST, seems it would make more sense as a Reaper extension?

It would be good if we could select items from the project bay to load into a slot.

Why are items loaded muted to the start of a track? could they be loaded into the project bay and retained?

Thanks again for your work :)

[Dannii]

I must admit, I've never used Ableton Live and have never really worked with that style of workflow but upon investigating Playtime, I am VERY curious to give this a shot. I've just downloaded the demo and will have a play around with it tomorrow when I get time to sit down and map things to my controllers.

:cool:

[plamuk]

this has big implications for external midi controlled devices/software

tempo-synced midi files ready to get blasted to various midi outputs at a buttonpush?

my mind immediately jumps to vjs

you don't see many "midi samplers." piz midi looper was one of the only ones and it's not really suited to this (nor is it as user friendly)

[jico27]

Hi,

Wanted to try this exceptional project but had this dll problem with PT v.1.0.0 mentioned above (#13) when using Reaper.
So i uninstalled this version & tried v.1.0.1 but can't install it. I now have a 'runtime error (at 14:170): Could not call proc' message.
I'm using W7 and also have the Mic Vis C++ 2013 installed.

[evosilica]

Hm, since my overpriced AKAI APC40 is just gathering dust over the last years, maybe this could be a way to use it again!?

Is there a possibility for a ableton live like implementation of the APC 40? With visual feedback and so on?
I know the apc40 is kind of resticted in its firmware, but maybe there's a way to hack this?

I would defenitely pay significantly more than 20€ to be able to reanimate this no-resale-value-pos. ;)

[Mivo]

This adds an entirely new workflow option. Very impressive. :)

[fantasyvn]

It would be great to have video tutorials.

[memyselfandus]

The most useful thing for me with the ableton session view is the ability to click on each cell and record midi or audio into each one and or edit in each cell. Then audition multiple cells at the same time to see what sounds good. This doesn't seem to be anything like that. Unless I'm missing something?

[todd_r]

You can record into cells, and play cells together. Not sure if you can edit directly from the cells though, think it's an fr, you can still edit in the project though. (All AFAIK not had a chance to really get into it properly yet)

[helgoboss]

Wow, so much feedback to process :)

@TonE

# MIDI file references

This is already possible. Remember you have all REAPER goodies at your disposal. Just mark the items on the timeline after recording them with Playtime and then "right mouse click => Item processing => Convert active take MIDI to .mid file reference". Then you can do to the resulting MIDI files whatever you want and it will affect playback in Playtime.

But if you are just interested in keeping the MIDI content of several clips in sync, there's a much easier way. When recording a clip, Playtime creates an in-project MIDI item. When you copy a clip (Ctrl+Drag'n'Drop), it creates a pooled MIDI item - also commonly called a "ghost copy". Every change you make to the source MIDI item will affect the ghost copy and vice versa. No need to cope with MIDI files.

Note that Playtime even creates ghost copies when using the "Write" button. That means the written items are still connected to the initial clips. You can replace the content of all those connected clips and items in one go. AFAIK this is indeed something Ableton doesn't offer.


# Track limit

Each slot can control an item on a different track if desired. So the limit is 64 tracks. But yes, there are only 8 groups (columns). As I wrote above, groups and tracks are not connected in Playtime. If you need more groups, you can fire up a second instance of Playtime. Multiple instances are not synchronized though. I'm thinking about increasing the maximum number of groups and scenes in future. But I think with 8x8 clips one can already come very far.


# Fill scene from selected items

Sounds useful to me. I didn't understand the ONLINE and OFFLINE thing.


# Write in another project tab

I think I know what you're getting at. Yes, reminds me of the old Cubase VST arrangements. This is very difficult though since the two projects (= different arrangments) would be totally disconnected from each other, not sharing the same tracks and items. Would be much easier if Cockos offered multiple timelines for one project. Alternative: Just write into different time passages of the project and use markers or regions to be able to jump to them easily.



@MotionMindz

Everything you mentioned is already possible :)

# 2. Loop lengths
This is already the case. Each clip can have an arbitrary loop length.

# 3. MIDI/CC controllable (triggers)
This feature is at the very core of Playtime.

You can also edit a clip by double clicking on it (MIDI clips: opens REAPER's internal MIDI editor, Audio clips: zooms into the item because REAPER doesn't have a separate audio editor).


@sinkmusic

# Bitbucket vs. Cockos forum

Thanks for making the requests there. Okay, discussions in the REAPER forum are fine. Voting for features and watching their progress is much better solved in Bitbucket.


@todd_r

# VST vs. REAPER extension

Playtime is actually a kind of REAPER extension, it uses the same functions that SWS extension uses for example. It's just deployed as a VST instrument. So Playtime has all the possibilities of a REAPER extension plus those of a VST plugin. That makes sense because Playtime is actually a musical instrument. It's supposed to be played with your MIDI keyboard (although using just the GUI is also nice).


# Select items from project bay

This is already possible. Project Bay => Options => Mirror selection in bay and project. Then select the item in the project bay, go to Playtime, right mouse click on a slot => Fill with selected item.

# Retain items in project bay

It's currently not possible to retain items or access the project bay using the REAPER extension API. I think the nice thing about keeping the items in the arrangement is that people have immediate access to them.


@nym

Wanting a "MIDI sampler" in REAPER was my motivation for writing Playtime :) Yes, you can use external MIDI devices.



@jico27

Are you on W7 32-bit or 64-bit? I will try this later and see whether I can reproduce the problem.



@evosilica

I didn't try Playtime with AKAI APC40 but it wouldn't surprise me if it's working. Playtime works with Launchpad and Orbit, including visual feedback. So if APC40 has the same protocol like Launchpad, it's gonna work. You can just try it. Please let me know if it works. Thanks :)


@memyselfandus

What you are describing is exactly what Playtime does. You can also edit MIDI by clicking on a cell that contains a MIDI clip (opens up REAPER MIDI editor). Audio clips are zoomed on double click because REAPER itself is the audio editor.

[EpicSounds]

Just published an interview with Ben on the REAPER Blog

http://reaperblog.net/?p=1748

[fantasyvn]

I have read your latest interview, which is very easy to understand.

So "Playtime offers 64 buttons into which you can put loops. If you press one of these buttons, the corresponding loop starts to play. If you press a second button, a second loop will start to play, perfectly tempo-aligned with the first loop."

What if the loops are in different keys? Does Playtime put everything in one key automatically?

My sincere thanks,

[EpicSounds]

I have read your latest interview, which is very easy to understand.

So "Playtime offers 64 buttons into which you can put loops. If you press one of these buttons, the corresponding loop starts to play. If you press a second button, a second loop will start to play, perfectly tempo-aligned with the first loop."

What if the loops are in different keys? Does Playtime put everything in one key automatically?

My sincere thanks,

It doesn't. But you can shift the pitch in the item properties.

[SoundsByJB]

Gave Playtime it a spin together with the just released Lemur for Android. Quickly modified a Lemur preset to match Playtime and seems to work great!!

https://www.youtube.com/watch?v=nwy0kPwCPX0

Cheers!

[vanhaze]

Wicked stuff, thanks for sharing !

[plamuk]

awesome. just read the reaper blog articles on playtime. developer seems like a good dude.

keep going, you have my full support.

devs, please grant this man any and all api requests he makes... he is opening your program up to a huge market. I'd like him to weigh in on the native vs 3rd party debate. an open api seems to make nativity irrelevant

[EpicSounds]

an open api seems to make nativity irrelevant

I was going to argue that devs might not see making plugins, or features only available for REAPER users a valuable use of their time. On the other hand, Pro Tools only plugins are still being made, which is making less sense every day.

[plamuk]

good argument. my thinking in response is with a comparison to sws... not useful to anyone other than reaper users but still supported via api for 3rd party devs.

[rjshama]

Hi,

I now have a 'runtime error (at 14:170): Could not call proc' message.
I'm using W7 and also have the Mic Vis C++ 2013 installed.

I'm getting the same error on my W7 32 bit machine. It installed fine on my 64 bit laptop.

Great program, BTW!

[nolman]

anybody any idea why i am not able to use the learn function ? it is not registering any midi-note from any of my midihardware. (which is working perfectly for other stuff in reaper)

update: when i assign trough plugin-fx parameter list-learn-slot(1,1) it works but the midi note is not shown in "midi note" any ideas ?

[helgoboss]

Hi nolman,

can you please insert a ReaControlMIDI fx into the fx chain at the first position, press the key you want to learn and let me know what the MIDI activity log says?

http://forum.cockos.com/attachment.php?attachmentid=22703&stc=1&d=14161392679

Then I might find out what the problem is.

Ben

[Seventh]

Trying this out right now, but I'm not really getting it... A tutorial video for the basic workflow would be great. ^_^

I'm not really interested in using this to trigger loops, but this seems like a quick way to sketch song arrangements. Not sure if I'll be able to accomplish what I'd like to do with this plugin though. Maybe you can consider the following as feature requests:

I would like to be able to select one of the cells, then press a hold pedal to trigger recording with preroll of a couple of beats (maybe also have it enable the metronome?).

Then I would play, say, a guitar riff, and press the hold pedal again. It would trim the clip to the closest bar length (8 bars for example), then start looping it.

Next I would select another cell, again enable the recording with the hold pedal, and record bass this time, maybe 4 bars. Again stop and it would trim & loop it to fit.

I'm not sure how to do this yet, or if it's even possible right now, but that would be an ideal workflow for me for quick sketching. I don't need separate recording triggers for separate cells, but instead one global trigger that would work for the selected cell.

Well, hopefully this is/will be possible with Playtime. It certainly seems like a powerful plugin. Thanks for working on implementing this quite popular feature into Reaper!

PS. Seriously classy website you got there! :)

PPS. "a CC-mappable action to record the currently selected slot" I see that this is already planned. Nice!

[clepsydrae]

I would like to be able to select one of the cells, then press a hold pedal to trigger recording with preroll of a couple of beats (maybe also have it enable the metronome?).

There are threads on this forum on using reaper as "loop station" which is basically what you describe. I don't believe the methods they detail involve locking to an existing tempo: i think when you hit the magic key (or sustain pedal) the loop is immediately created, but i think there are now actions to "delay next action until next measure" that could achieve that (or did i just imagine seeing that come through in a pre a while back?).

Here's one of the threads: http://forum.cockos.com/showthread.php?t=17238

[helgoboss]

@Seventh

You will be able to do this as soon as this (https://bitbucket.org/helgoboss/playtime/issue/35/cc-mappable-global-slot-record-button) and this (https://bitbucket.org/helgoboss/playtime/issue/2/play-item-as-soon-as-recorded) is implemented. These two features will come soon, I guess right after OS X support.

Ben

[nolman]

found my problem : monitoring should be on for the track with playtime ?
now midi learn works.

[Seventh]

@Seventh

You will be able to do this as soon as this (https://bitbucket.org/helgoboss/playtime/issue/35/cc-mappable-global-slot-record-button) and this (https://bitbucket.org/helgoboss/playtime/issue/2/play-item-as-soon-as-recorded) is implemented. These two features will come soon, I guess right after OS X support.

Ben
Sweet! I'll have my wallet ready. :)

[Sunaj]

I want to ask.. is it possible to map individual keys on the typing keyboard to each block? is very easy to do in ableton live

[plamuk]

sunaj, try using the virtual midi keyboard for that, as it allows for keyboard triggering

otherwise, look at some key->midi translators, like bome's, or glovepie

----

regarding launchpad support: helgo, please allow midi out (for LED) customization for custom/less common controllers like the quneo, lemur, and customized launchpad devices.

basically, FR: if a cell is occupied with a clip and it is learned to a midi note, send a NOTE ON for that note out for LED purposes upon load and/or upon "refresh" command (since many of these devices can browse away to different modes and will need their LEDs refreshed). if the clip is stopped or deleted, send a NOTE OFF. if the clip is playing, send NOTE ONs and NOTE OFFs at a tempo synced interval.

users can and will route this to the device LED feedback input as necessary -- trust us to do this. please don't go the ableton/novation way and seize command of the device LEDs.

if this is at all confusing, please reach out and let's talk

[Gates of Horn & Ivory]

This looks excellent, helgoboss. I'm not able to test right now (OSX), but I'm curious... Is this stable enough to play live? Does the limit of 8 columns/slot groups restrict you to eight mixer channels? (And if so, are there any plans to increase that limit, and/or the scene limit?)

For me, this should have been built in to the project bay from day 1, the project bay may have had some use !
Absolutely. Come on Cockos, live a little. Splash out. Seize the day. One of those things.

[EpicSounds]

Does the limit of 8 columns/slot groups restrict you to eight mixer channels? (And if so, are there any plans to increase that limit, and/or the scene limit?)




8x8 are great, but why not allowing multiplications of this structure, e.g. 12 or better 128, one bank for each bank select message? Sending a bank select message to Playtime will shift to the correct bank of 8x8 clips. Each 8x8 matrix can be regard as a 'song playground' and you can design 128 'songs' in one go, for a bigger 'live set'.



It's a VSTi, load multiple instances.

[todd_r]

I like that columns aren't restricted to certain tracks, but still 8 concurrent loops is a bit low I think (I know you can load multiple instances, but would be good of you could keep it all in one instance)

[todd_r]

It would integrate much better into reaper if it could be docked directly, rather than in the fx browser. Is that possible, or is there an FR for it?

[EvilDragon]

You can't dock a plugin's GUI without the FX browser, limitation of Reaper.

[todd_r]

http://forum.cockos.com/project.php?issueid=5100

Here's the FR (turns out I'd already voted on it)

Everyone vote! :)

[EpicSounds]

Enjoy your winter jacket: http://www.spiegel.tv/filme/lebendrupf-bei-gaensen-daune/

That doesn't seem relevant.

[4oMuAjln]

It is great!

[helgoboss]

found my problem : monitoring should be on for the track with playtime ?
now midi learn works.

Yes, input monitoring needs to be on (as in the track template). I just added this information to the user guide. Thanks.

[helgoboss]

sunaj, try using the virtual midi keyboard for that, as it allows for keyboard triggering

otherwise, look at some key->midi translators, like bome's, or glovepie

----

regarding launchpad support: helgo, please allow midi out (for LED) customization for custom/less common controllers like the quneo, lemur, and customized launchpad devices.

basically, FR: if a cell is occupied with a clip and it is learned to a midi note, send a NOTE ON for that note out for LED purposes upon load and/or upon "refresh" command (since many of these devices can browse away to different modes and will need their LEDs refreshed). if the clip is stopped or deleted, send a NOTE OFF. if the clip is playing, send NOTE ONs and NOTE OFFs at a tempo synced interval.

users can and will route this to the device LED feedback input as necessary -- trust us to do this. please don't go the ableton/novation way and seize command of the device LEDs.

if this is at all confusing, please reach out and let's talk

That's how the Launchpad support is implemented right now. Pure MIDI (see user guide section "Visual feedback with Launchpad and Co.").

Two differences however:
- "refresh" command not implemented. Do you know how that refresh command looks like? A special CC value?
- Tempo-synced NOTE ONs and NOTE OFFs are sent only if a clip is going to start soon (countdown)

[helgoboss]

This looks excellent, helgoboss. I'm not able to test right now (OSX), but I'm curious... Is this stable enough to play live? Does the limit of 8 columns/slot groups restrict you to eight mixer channels? (And if so, are there any plans to increase that limit, and/or the scene limit?)

Concerning stability for live use, until now nobody has reported a crash to me yet. But of course Playtime is pretty young. Time will show. If someone experiences a Playtime-related crash, please report it on the issue tracker.

The 8 columns/slot groups don't restrict you to eight mixer channels. Each clip can be on a different mixer channel (track).

[helgoboss]

Hey boss,

8x8 are great, but why not allowing multiplications of this structure, e.g. 12 or better 128, one bank for each bank select message? Sending a bank select message to Playtime will shift to the correct bank of 8x8 clips. Each 8x8 matrix can be regard as a 'song playground' and you can design 128 'songs' in one go, for a bigger 'live set'.

That would actually not be that difficult. There's also no big GUI change involved. I already put a similar feature request (https://bitbucket.org/helgoboss/playtime/issue/22/more-slots-scenes-and-groups) to myself.


Offline, Online thing is important with midi file references and using external midi processors, my favourite is Keykit by Tim Thompson, its command line variant, lowkey.exe in the Keykit package, what I mentioned already a few times in this forum. If you want to use such an external midi processor with Reaper, those referenced midi files inside Reaper have to be 'released' first, this is done with selecting those midi items, changing their status to OFFLINE, now you can process those midi files with your own keykit code, via command line, when command is finished, taking 1 or 2 seconds usually, switching back the processed items to ONLINE and Reaper will update to the new versions. You can do all above in one go, if you use AutoHotkey, triggering required Reaper actions from there, too. In practice it means, press one hotkey, finished. Exactly as you do in Reaper itself, only here, this is an external processor. If you say, Playtime does not cut any of those 'external processing capabilities', everything still will be correctly updated EVEN inside Playtime, then great. Another reason Ableton can go home, to Berlin.

OK, now I get the online offline thing. Makes sense. Yes, Playtime doesn't cut any of those external processing capabilities.

[Susan G]

I've tried the demo and this looks pretty neat.

Does anyone know how PayPal works if the price is shown only in euros and you want to pay in US dollars? Is the amount converted at the point of sale?

Thanks-

-Susan

[helgoboss]

I like that columns aren't restricted to certain tracks, but still 8 concurrent loops is a bit low I think (I know you can load multiple instances, but would be good of you could keep it all in one instance)

I want to extend this in future (FR (https://bitbucket.org/helgoboss/playtime/issue/22/more-slots-scenes-and-groups)). But in order to resolve a possible misunderstanding: There can be only 8 concurrent loops per scene right now, yes. But if you disable "exclusive mode", you can play several concurrent loops in one column. Then you have 64 concurrent loops in total. Already now.

[helgoboss]

http://forum.cockos.com/project.php?issueid=5100

Here's the FR (turns out I'd already voted on it)

Everyone vote! :)

Just voted :)

[helgoboss]

I've tried the demo and this looks pretty neat.

Does anyone know how PayPal works if the price is shown only in euros and you want to pay in US dollars? Is the amount converted at the point of sale?

Thanks-

-Susan

Right before you actually pay, Paypal tells you the converted amount in your currency. So you can still back down at that point if you don't like the amount in your currency :)

[Susan G]

Right before you actually pay, Paypal tells you the converted amount in your currency. So you can still back down at that point if you don't like the amount in your currency :)
Thanks, helgoboss.

-Susan

[jico27]

Wow, so much feedback to process :)
@jico27

Are you on W7 32-bit or 64-bit? I will try this later and see whether I can reproduce the problem.

W7 32-bit. I have this message appearing all along the installation process. But this doesn't prevent the app from being installed.

[vanhaze]

Any known timeframe for osx version release ?
Sorry, cant wait !

[plamuk]

That's how the Launchpad support is implemented right now. Pure MIDI (see user guide section "Visual feedback with Launchpad and Co.").

awesome. thank you for being considerate to users of other software/hardware.

(difference 1) - "refresh" command not implemented. Do you know how that refresh command looks like? A special CC value?

the refresh command is not launchpad specitic. rather, it is intended to replicate this functionality (as described from your site) a little more smoothly:

Start playback in REAPER and stop it again. The device should now indicate which slots are filled.

an arbitrary CC value may be used for this. this is completely optional for users with non-standard launchpad layouts and other controllers that have different modes. Example: mode 1 = Playtime controller. mode 2 = REAPER action controller. when you switch back to mode 1 from mode 2, a user may associate that refresh CC with a return to mode 1, relighting all relevant LEDs even when REAPER playback is stopped.

(difference 2)Tempo-synced NOTE ONs and NOTE OFFs are sent only if a clip is going to start soon (countdown)

cool, that's better than what i'd suggested (flashing during playback). i'm assuming that you'll have active/playing cells light up as a different color?

[kaiman]

Thanx to the creator. This has the potential to be a game changer for many!
Off to download and test!

[PitchSlap]

After reading the user's guide, I'm actually getting a lot more excited by this! :)

I used to use MobiusVST alot as a looper, and while there are a lot of things I LOVED about it, there were also some limitations (audio only recording, hard to integrate with a host, etc).

The workflow from nothing, to all the parts to a song was the more fluid and intuitive of anything I've used, and I really want to get back to that.

A have a few suggestions from Mobius (a few which may already be possible).

1) This is by FAR the biggest. I don't want to have to decide a tempo before hand. I want to be able to record the first midi or audio clip "freely", then have Playtime treat that as the main loop length, assuming 4, 8 or 16 bars, and then change the Reaper project tempo to match (whatever makes sense mathematically, Reapers detect tempo often returns nonsense like 16 BPM when 64 or 128 BPM is correct).

That way I can get the main idea, and after the project tempo is set based on that, other audio/midi loops can be imported and timed correctly.

If you check the Global Quantization FR in my sig, there is a LOT of info on how Mobius and the Echoplex looper it's based on handle this.
http://forum.cockos.com/project.php?issueid=2623

2) Another thing I loved about Mobius was being able to reverse the clip, this is great for audio, and could probably lead to some unexpected and creative accidents with MIDI.

3) Mobius also allows doubling or halving the playback rate. For MIDI this would just be the same as changing the item playback to 0.5 or 2, with audio that amount of time-stretching will some horrible, so when Mobius plays the audio faster the pitch is an octave higher, and slower the audio is an octave lower. Things stay in time and in tune without any nasty artifacts. This is a great way to get interesting textures.

Both 2 and 3 would of course happen in time when the main loop restarts.

(less of a priority, but thought I'd mention it anyway)
4) When using Reaper in general I don't want my MIDI made into external files, but in this instance the MIDI lengths will be perfect loops which makes it far more valuable as it can be reused in the Media Explorer, assigned to a different instrument and will adapt perfectly to any other project tempo. I could probably convert the items to files manually, but some icing on the cake would be a feature of Playtime to create my recorded MIDI clips as external files irrespective of the global setting in Reaper.

Coincidentally, you might be filling my 2 most important and long-standing feature requests (close to 5 years now), so THANK YOU THANK YOU THANK YOU! :D

[fladd]

Tried it yesterday. I like the idea! However, it seemed to work quite differently to how I remembered Live (version 4) to work. The workflow is not the same, unfortunately, which probably makes sense, since it is a plugin and not natively integrated. It might be good for when you are planning a Live session, but for what I used Live for (jamming and trying out stuff) it isn't that intuitive and not "fast" enough (i.e. needs a lot of setting up, planning, etc.).

So I guess it is not for me, unfortunately. Still hope this gets implemented natively, though!
And keep up the good work, I am sure this can be useful for others!

[TripodII]

Funny I was just at Guitar Center trying to reluctantly negotiate a deal on Ableton Live just to get the clip switching functionality. Definitely gonna give this a go

[todd_r]

Question: any chance ton embedd natively Playtime in Reaper ? forum.cockos.com/showthread.php?t=149712 [permalink]
Asked by gilbert (109.19.9.x) on November 9 2014, 1:15pm
Reply on November 10 2014, 11:30pm:
Hmm interesting but we'll see. I know JeffOS wants that too.
http://www.askjf.com/index.php?q=2981s

Promising :)

[sinkmusic]

Promising :)
I hope so. i wish we had a bit more info.

[Seventh]

Hey there. A couple of feature requests here:

-Automatically detect the most probable subdivision for the loop length, instead of assuming everything is in 4/4, for some polyrhythmic goodness.
-Maybe also an option to set this manually
-Waveform preview ;) with where you can set stretch markers & loop points à la Bitwig.

Cheers

[Sunaj]

trying the demo out now. is it possible to record items as midi and not on track as audio? if that makes any sense

[PitchSlap]

trying the demo out now. is it possible to record items as midi and not on track as audio? if that makes any sense

I don't know exactly what you are referring to, but one "advanced" technique covered in the manual is recording your clip triggered as MIDI, which allows editing/arranging afterwards which is more flexible than what can be done in Ableton/Bitwig. Before rendering the project however, all clips must be written to the timeline.

[EpicSounds]

Keep the fire burning.
http://www.youtube.com/watch?v=qqqVS2l_XY8

Why don't you PLAY with me.
http://www.youtube.com/watch?v=YTKZ5vQ6Kk8

Why not post something you've made with Playtime? I don't get why you're posting these music videos.

[MCCY]

Concerning stability for live use, until now nobody has reported a crash to me yet. But of course Playtime is pretty young. Time will show. If someone experiences a Playtime-related crash, please report it on the issue tracker.

The 8 columns/slot groups don't restrict you to eight mixer channels. Each clip can be on a different mixer channel (track).

using it on win8 tablet I had some crashes just from the beginning, but maybe I did something wrong... Now after activating monitoring it seems o.k. Sometimes it just forgets to take the items directly into the slot after recording... but that must be also me only.

I come from mobius too, like someone else here, so my biggest wish is an auto tempo detection... I made a script for that for my own looping experiments and it seems it can be used in combination with this workflow. Wow, so many possibilities, I'getting old and tired of complicated things... Maybe I'll just buy it to support the developement!

1000thanks!

Martin

[MCCY]

Bought it.
It would be great to be able to remotely record active slot and also fill withselected item. I cant mangage to create several triggers for every single slot... i just have a 4x4 padcontroller.
When I create first item with temporecognition and automatic cut (own script) it is not possible to load the cutted item, because the length changes to original lenght before cutting. Would be nice, if item was looped like it is displayed in the arrangement.

Ich würde also das erste item aufnehmen wie gewohnt, es via script zurechtschneiden lassen und das Tempo feststellen lassen und dann das item in den ersten freien Slot einfügen. Andere Slots würd ich auch gerne per Fußschalter ansteuern und dann mit einem knopfdruck die aufnahme starten...

[lxm]

Thank you very much for making this. Will defiantly purchase. Having said that, it does seem a little steep IMO.. Especially compared to the cost to purchase REAPER. Again, not complaing just my opinion. Looking forward to some tutorial videos.

[richie43]

Thank you very much for making this. Will defiantly purchase. Having said that, it does seem a little steep IMO.. Especially compared to the cost to purchase REAPER. Again, not complaing just my opinion. Looking forward to some tutorial videos.

20 Euros/25 USD is steep? For all of the work that is going into it? What sort of price do you suggest then?

[PitchSlap]

20 Euros/25 USD is steep? For all of the work that is going into it? What sort of price do you suggest then?

Relative to the cost of Ableton Live/Bitwig, Playtime is very cheap. Relative to the cost of Reaper or a Reaper update (which may, or may not include similar or expanded functionality and countless other features) Playtime is very expensive. It all depends on the perspective.

Also, until this point most user-created additional functionality (themes, extensions, scripts, JS plugins etc.) has been contributed for free. The creator of this is a professional programmer however, and I think if it's fair for them to seek monetary incentive to continue development considering they could be doing with their time/skills (I'm aware other professional programmers have donated their time to the Reaper community, but that doesn't mean we are entitled, and that everyone else is required to do the same).

[sinkmusic]

Hi
HelgoBoss, any progress or update at the horizon ?

[gwok]

so.......


how's the OSX build coming along? :)

[Giano]

Relative to the cost of Ableton Live/Bitwig, Playtime is very cheap. Relative to the cost of Reaper or a Reaper update (which may, or may not include similar or expanded functionality and countless other features) Playtime is very expensive. It all depends on the perspective.

Also, until this point most user-created additional functionality (themes, extensions, scripts, JS plugins etc.) has been contributed for free. The creator of this is a professional programmer however, and I think if it's fair for them to seek monetary incentive to continue development considering they could be doing with their time/skills (I'm aware other professional programmers have donated their time to the Reaper community, but that doesn't mean we are entitled, and that everyone else is required to do the same).

Reaper is free of charge !
or € 47,50 (I guess most have this non-professional license)
Playtime is € 20 (USD 25), that´s about 42 % of the Price for Reaper (
including all features, inluding all plugins etc. !!!)
How could one plugin based on Reaper structure be worth 42 % ?!
So I agree...

[gwok]

Reaper is free of charge !


no it's not


How could one plugin based on Reaper structure be worth 42 % ?!
So I agree...

WTF is this logic?

I mean I guess if you completely disregard the developers time and right to earn a living from their trade, I guess is makes sense in a twisted sort of way. Do the math, it's probably not gonna put him on Forbes cover

[EpicSounds]

It's pretty simple. One guy creates something that didn't exist for a tiny niche market. There's only a small group of reaper users that want the product and he needs to charge a certain amount to make back the time he spent on it.

REAPER's price is way too low for what you get.

[Giano]

no it's not



WTF is this logic?

I mean I guess if you completely disregard the developers time and right to earn a living from their trade, I guess is makes sense in a twisted sort of way. Do the math, it's probably not gonna put him on Forbes cover

I said something that is obvious:

Compared to the price for Reaper, it is way too much !

Imagine there are people, musicians, artists practising, working, performing,
living on the breadline, and they do that almost their whole life, and some of them are very skilled artists - and very often they have to perform for free ! What´s that compared to something that has been developed within less than 6 months only !?
But it does not really matter what I say, if he wanted € 100 and people would pay ...let them pay...

And imagine there are people in this forum, one has developed a great and special drumkit and it´s for free !
He has spent a lot of time with a lot of passion developing the the drumkit.

I am not saying the dev of Playtime is doing wrong, I simply compared the price to the price for Reaper ! That´s all.

[Stu]

It's pretty simple. One guy creates something that didn't exist for a tiny niche market. There's only a small group of reaper users that want the product and he needs to charge a certain amount to make back the time he spent on it.

REAPER's price is way too low for what you get.

Quoted for truth.

You can buy Cytomics 'Glue' compressor, or you could buy ReaComp for less and get a free DAW with it...but it won't sound like The Glue. If this is useful to people, it is worth as much as people are prepared to pay for it, just like everything else.

[lxm]

Ya'll can simmer down. Im going to support it. Im giving thanks. Just my opinion. You dont have to agree with it. I dont care.

[helgoboss]

Just a small update about OS X support. My plan is to publish a pre-release next week. Things are working already quite nice on Macs without Retina display. On Macs with Retina display, some bugs still need to be fixed.

Minimum OS X version is 10.7 for now.

[gwok]

Ya'll can simmer down. Im going to support it. Im giving thanks. Just my opinion. You dont have to agree with it. I dont care.

i was a little harsh, heheh, no hard feelings.

[gwok]

Just a small update about OS X support. My plan is to publish a pre-release next week. Things are working already quite nice on Macs without Retina display. On Macs with Retina display, some bugs still need to be fixed.

Minimum OS X version is 10.7 for now.


awesome!

[heda]

http://forum.cockos.com/project.php?issueid=5100

Here's the FR (turns out I'd already voted on it)

Everyone vote! :)

Thanks I missed to vote this. I don't know if voting counts but I'm voting anyway :D

[lxm]

Money is an artificial construct, nobody needs it.

See... You get it :P buying it this weekend regardless. Love you all

[ugh]

Is it difficult to set up a Novation Launchpad to use Playtime ?

[plamuk]

no, it's very easy using the learn feature

[ugh]

I don't really know much about MIDI learn, but I will give it a try then.

[ValeryOrloff]

Hi!
He (playtime) launches regions? clips = reaper's regions?
or individually load samples to each cells?
how does this work?

[Taika-Kim]

I have maybe an obvious problem:

I have MIDI clips that I am triggering with a Quneo. However, the trigger notes are being sent forward all the time, so for example if I have note G-3 triggering a clip, when I press the correspondind pad on the Quneo, the MIDI pattern plays with a continuous note G3 overlaid all the time.

Now I'm having a send to another channel that's not listening to the control channel that Quneo is sending on, but this feels unneeded.

Is there a more graceful way to avoid this problem? I have a feeling here that I'm missing something cruelly obvious...

[helgoboss]

Hi all,

it's time to publish a Mac OS X prerelease: playtime-v1.1.0-pre3-installer.pkg (http://www.helgoboss.org/projects/playtime/downloads/playtime-v1.1.0-pre3-installer.pkg)

System Requirements:

OS X >= 10.7
REAPER >= v4.7, 32-bit or 64-bit


Instructions:

Download the installer.
Start it. In some cases, OS X might refuse to start it because the installer is not signed. In that case, just find the downloaded file in Finder, right click it, choose the context menu entry "Open" and when the warning appears, click the "Open" button.
Follow the instructions of the installer.
Open REAPER.
Add the track template "Playtime".
Have a look at the user guide (http://www.helgoboss.org/projects/playtime/user-guide).


Known Issues:

Mouse cursor sometimes doesn't update
Looks a bit lo-fi on a Retina display (I'm going to work on that one later)


Remarks:

Many thanks to @gwok for testing pre1 and pre2! Those prereleases made REAPER crash quite often on certain OS X environments. This is fixed in pre3, so now it's much more likely that you can enjoy a "crash-less" experience.
The installer currently installs Playtime to the folder /Users/<username>/Library/Audio/Plug-Ins/VST REAPER by default looks for VST plugins in that folder. The advantage over a system-wide install is that also non-admin users can install it. A system-wide install (/Library/Audio/Plug-Ins/VST) is perhaps a more common location. For the user experience however, it makes no difference. I have no idea how much Mac users care about this kind of things. Any thoughts on that are welcome.


Have fun!

Cheers
Ben

[Taika-Kim]

Is a completely "super exclusive" mode out of question, so that only one loop would play at a time?

I am using a Quneo to trigger MIDI clips, but now I need to stop the playing every time I trigger a clip from another group... Otherwise like this with immediate switching of loops it would be possible to create really fluid leadlines, especially with an arpeggiator behind, that can change the rhythms too...

Also if it could be somehow to build in support for controllers like the Quneo, it would be very very useful, now I can't see what patterns are playing. I think somebody already explained here how it could be made.

[jico27]

Hi,

Wanted to try this exceptional project but had this dll problem with PT v.1.0.0 mentioned above (#13) when using Reaper.
So i uninstalled this version & tried v.1.0.1 but can't install it. I now have a 'runtime error (at 14:170): Could not call proc' message.
I'm using W7 and also have the Mic Vis C++ 2013 installed.

Hi,

Is there a newer 32bit version for the installer, which doesn't generates error messages during the installation process ?

Regards

[helgoboss]

Released Playtime 1.1.0 (http://www.helgoboss.org/projects/playtime/) including Mac OS X support.

Changes:
#14 Added support for Mac OS X
#42 Improved Windows installer intelligence
#46 Fixed lost recordings
#44 Fixed installer problems on 32-bit Windows systems
#57 Fixed display of unnamed tracks

[mikolo]

Im having touble installing this on Vista.It repeatedly pops up with an error message during installation which says:
"Runtime Error (at 14:170):
Could not call proc."
I can see the download says its for windows XP,7 & 8 but was wondering if anyone else has had any success or any sugestion.
Thanks

[helgoboss]

cool, that's better than what i'd suggested (flashing during playback). i'm assuming that you'll have active/playing cells light up as a different color?

Yes, exactly. Different velocities create different colors (at least on Launchpad and Orbit).

[helgoboss]

Hi,

Is there a newer 32bit version for the installer, which doesn't generates error messages during the installation process ?

Regards

This should be fixed in 1.1.0. At least on Windows XP the errors are gone. Please let me know if it still doesn't work. Thx.

[helgoboss]

Im having touble installing this on Vista.It repeatedly pops up with an error message during installation which says:
"Runtime Error (at 14:170):
Could not call proc."
I can see the download says its for windows XP,7 & 8 but was wondering if anyone else has had any success or any sugestion.
Thanks

I didn't test on Vista. Other users reported that installation is still possible if you just always press okay when the error messages appear. Did you try the latest 1.1.0 installer? I made some fixes that removed this kind of error at least on Windows XP.

If it works on Vista, please let me know.

[mikolo]

Good news! Ive just downloaded the latest version and installed without a hitch.

Thanks!
This looks really good.

[helgoboss]

A have a few suggestions from Mobius (a few which may already be possible).

1) This is by FAR the biggest. I don't want to have to decide a tempo before hand. I want to be able to record the first midi or audio clip "freely", then have Playtime treat that as the main loop length, assuming 4, 8 or 16 bars, and then change the Reaper project tempo to match (whatever makes sense mathematically, Reapers detect tempo often returns nonsense like 16 BPM when 64 or 128 BPM is correct).

That way I can get the main idea, and after the project tempo is set based on that, other audio/midi loops can be imported and timed correctly.

That sounds very useful to me. One major challenge I see here is that the recorded loop has to be cut (start and end) very precisely so the detected tempo makes sense.

Tried it yesterday. I like the idea! However, it seemed to work quite differently to how I remembered Live (version 4) to work. The workflow is not the same, unfortunately, which probably makes sense, since it is a plugin and not natively integrated. It might be good for when you are planning a Live session, but for what I used Live for (jamming and trying out stuff) it isn't that intuitive and not "fast" enough (i.e. needs a lot of setting up, planning, etc.).

I'm planning to provide a project template that get's one started very quickly, tracks already set up. Other than that, can you describe the workflow problems you see? Playtime is in active development, so its future is still shaping. You might be surprised what can be done with just a plugin :)


-Automatically detect the most probable subdivision for the loop length, instead of assuming everything is in 4/4, for some polyrhythmic goodness.

Do you mean after recording, depending on when the recording is started and stopped or the actual musical content?


trying the demo out now. is it possible to record items as midi and not on track as audio? if that makes any sense

Sure. Just do it the REAPER way and select MIDI as recording input for that track.

Sometimes it just forgets to take the items directly into the slot after recording... but that must be also me only.

It's not only you :) That was a bug which is fixed now in Playtime 1.1.0.

Bought it.
It would be great to be able to remotely record active slot and also fill withselected item. I cant mangage to create several triggers for every single slot... i just have a 4x4 padcontroller.
When I create first item with temporecognition and automatic cut (own script) it is not possible to load the cutted item, because the length changes to original lenght before cutting. Would be nice, if item was looped like it is displayed in the arrangement.

#68 (https://bitbucket.org/helgoboss/playtime/issue/68/mappable-button-for-filling-active-slot), #35 (https://bitbucket.org/helgoboss/playtime/issue/35/cc-mappable-global-slot-record-button), #60 (https://bitbucket.org/helgoboss/playtime/issue/60/playtime-always-loads-items-full-length)



I have MIDI clips that I am triggering with a Quneo. However, the trigger notes are being sent forward all the time, so for example if I have note G-3 triggering a clip, when I press the correspondind pad on the Quneo, the MIDI pattern plays with a continuous note G3 overlaid all the time.

There could be several reasons:

- Reason 1: Maybe your Playtime track not only contains Playtime VST but also another synth. This kind of setup is not intended. Just remove the synth.
- Reason 2: Maybe you have another track which has set QuNeo as MIDI input as well? In that case, just choose another MIDI input device for it (or another MIDI channel) ... it's all about routing.

Is a completely "super exclusive" mode out of question, so that only one loop would play at a time?

I am using a Quneo to trigger MIDI clips, but now I need to stop the playing every time I trigger a clip from another group... Otherwise like this with immediate switching of loops it would be possible to create really fluid leadlines, especially with an arpeggiator behind, that can change the rhythms too...

Nice idea. Haven't thought of this. #69 (https://bitbucket.org/helgoboss/playtime/issue/69/super-exclusive-mode)


Also if it could be somehow to build in support for controllers like the Quneo, it would be very very useful, now I can't see what patterns are playing. I think somebody already explained here how it could be made.

Did you try the things described in section "Visual feedback with Launchpad and Co." of the user guide? I don't know the QuNeo but chances are it's working similar to Novation Launchpad. If yes, setting the MIDI hardware output of the Playtime track to your QuNeo should do it.

[Michael_DK]

Installed it to test it - but Reaper can't find the track template.
Tried reinstalling twice.

I'm on a mac. I wonder if this is because my user folder is on another drive? (i.e. not system drive)

[plamuk]

Did you try the things described in section "Visual feedback with Launchpad and Co." of the user guide? I don't know the QuNeo but chances are it's working similar to Novation Launchpad. If yes, setting the MIDI hardware output of the Playtime track to your QuNeo should do it.

launchpads LED control == midi created when pressing the buttons.

quneo uses a different, more complex method of controlling LEDs depending on what mode the device is in.

see page 33 and 34 of http://files.keithmcmillen.com/downloads/quneo/QuNeo_FullManual_1.1.pdf

this is where end users are going to have to be expected to do some work on their side via bidule or JS...it's not worth your time or money to buy every midi controller with LEDs in existence and code it into Playtime. better to spend your time on the direct functionality in my opinion. and i say that as a quneo user myself.

[EpicSounds]

launchpads LED control == midi created when pressing the buttons.

quneo uses a different, more complex method of controlling LEDs

Everything about the QuNeo is more complex amirite?

Did you set up a custom mapping for QuNeo and Playtime? I'm using Preset 9 "Ableton Live Clip Launching". Using the pad corners to launch clips and scenes.

[plamuk]

nah i use the quneo exclusively for drums, transport control and control changes. i use a mode in my custom launchpad setup for playtime. it replaced the MPC1000 in my studio configuration when i switched from a hardware sequencer to REAPER's arrange/midi sequencer.

i think there's a quneo launchpad emulator. that may well be what you're referring to.

and yes, everything is more complex with quneo...unfortunately, due to the different LED triggering methods, it needs to be. i really wish the quneo editor was better. it's like building a ship in a bottle.

quneo is one of those terrific platforms that didn't blow up as much as it needed to in order to get the development it shouldve

[helgoboss]

Installed it to test it - but Reaper can't find the track template.
Tried reinstalling twice.

I'm on a mac. I wonder if this is because my user folder is on another drive? (i.e. not system drive)

Where is you REAPER settings folder? The Mac installer expects it at "/Users/USERNAME/Library/Application Support/REAPER" and puts the file "Playtime.RTrackTemplate" into its sub folder "TrackTemplates".

[Seventh]

-Automatically detect the most probable subdivision for the loop length, instead of assuming everything is in 4/4, for some polyrhythmic goodness.
Do you mean after recording, depending on when the recording is started and stopped or the actual musical content?

First one. I'd like to use the hold pedal to toggle recording on and off for the selected cell to quickly create layers of sounds that would play in time, no matter if I suddenly feel inspired to put some 7/8 stuff in there. :)

So yeah, instead of having everything snap to whole note grid, it would be more useful if it also recognized subdivisions for recorded items, and stretched them accordingly to the closest probable length.

[Michael_DK]

Where is you REAPER settings folder? The Mac installer expects it at "/Users/USERNAME/Library/Application Support/REAPER" and puts the file "Playtime.RTrackTemplate" into its sub folder "TrackTemplates".

Yeah, it wasn't there.

I logged into my other account which IS on the system drive, and it installed the template with no problem. I copied that to my "normal" account's tracktemplates library and now it works.

[Thurston]

Someone posted a video using Playtime with Lemur for Android:

https://www.youtube.com/watch?v=nwy0kPwCPX0

[sonnie]

Easy install without issues here on 10.9 and 10.10.

[memyselfandus]

For me the whole benefit of the Ableton type version is to be able to record or mouse in notes inside your clips and then trigger them after. The clips are a totally separate area where you can compose little parts. And then put them together later. This seems to be all on the main timeline and not inside cells that can be drag and dropped and or recorded into the project after?

[memyselfandus]

If we could have a separate workspace where we can punch in and record different ideas and then drag and drop them into the main project later on.. That would allow me to work only in Reaper.

Either way.. This is super awesome to have in Reaper! Thanks for all the hard work. I will buy a copy soon.

[vitalker]

Someone posted a video using Playtime with Lemur for Android:

https://www.youtube.com/watch?v=nwy0kPwCPX0
Maybe he?
Gave Playtime it a spin together with the just released Lemur for Android. Quickly modified a Lemur preset to match Playtime and seems to work great!!

https://www.youtube.com/watch?v=nwy0kPwCPX0

Cheers!

[helgoboss]

Small intermediate release Playtime 1.2.0 (http://www.helgoboss.org/projects/playtime/).

Changes
#35 Added mappable global slot record button
#64 Added forwarding of keyboard shortcuts to REAPER for better integration
#71 Fixed crash when retriggering MIDI clip that is open in MIDI editor

Thanks to Vladimir for reporting the crash.

[helgoboss]

First one. I'd like to use the hold pedal to toggle recording on and off for the selected cell to quickly create layers of sounds that would play in time, no matter if I suddenly feel inspired to put some 7/8 stuff in there. :)

So yeah, instead of having everything snap to whole note grid, it would be more useful if it also recognized subdivisions for recorded items, and stretched them accordingly to the closest probable length.

The Trigger and Untrigger Mode also applies to recording. You can set these to "Next Beat" instead of "Next Measure" (for all slots or just particular ones). If you do that and record a slot, the recording is cut on the closest beat instead of the closest measure. With that you could achieve crazy 7/8 stuff :) Playtime doesn't look at the musical content of the clips though. It just recognizes the points in time at which you started and stopped recording.

Release 1.2.0 should enable you to do the thing with the hold pedal.

[PitchSlap]

Release 1.2.0 should enable you to do the thing with the hold pedal.

Interested to see what else is in 1.2, and hope eventually to see some of my suggestions from post #136 based on the Mobius and Echoplex loopers considered.

I'm looking into getting a used Launchpad or other dedicated controller to take best advantage of Playtime. :)

[Seventh]

The Trigger and Untrigger Mode also applies to recording. You can set these to "Next Beat" instead of "Next Measure" (for all slots or just particular ones). If you do that and record a slot, the recording is cut on the closest beat instead of the closest measure.
Ahh ok, I missed the purpose of the trigger modes :)

With that you could achieve crazy 7/8 stuff :) Playtime doesn't look at the musical content of the clips though. It just recognizes the points in time at which you started and stopped recording.

Release 1.2.0 should enable you to do the thing with the hold pedal.
I gave the new version a try. A couple of observations:
- Playtime needs separate settings for triggering and recording modes. Maybe separate settings for different instruments/columns too.
- Using "immediate" recording toggle, the recorded items don't sync up with the grid. Could Playtime offer an option to automatically stretch them to the correct length?
- Looped items tend to have clicks in them. This is a "feature" of Reaper, as you can't set fades for loop seams, but could Playtime offer an option to render a certain amount of fade in/fade out into the recorded item?
- Could use an option in the preferences to map the global record cc, instead of having to go to the track's envelope window
- Got a crash in the end, can't remember how to replicate though. :P

[Jed]

Small intermediate release Playtime 1.2.0 (http://www.helgoboss.org/projects/playtime/).

Changes
#35 Added mappable global slot record button


Ben could you please explain how this works? I cant see a global button to map to! (V1.2.0)

Thanks
Jed

EDIT: Found it in the list of automatable parameters for the VST. However when recording into a slot using it, the resulting clip should automatically appear in the slot once the recording is complete (as per Live) and then start playing.

Small steps!

Cheers
Jed

[EpicSounds]

Made a video, basic overview and demo
http://reaperblog.net/2014/12/video-helgoboss-playtime-plugin-demo/

[Melvin J.]

Looking good! Thanks for the video.

[mehmethan]

Hi, I need help. I'm trying to trigger audio loops and samples with using next beat trigger mode but I always get clicks between samples and false sync. What am I doing wrong?
Edit :
Solved... It is not related with playtime. It's about bad drivers's of focusrite scarlet soundcard. I changed the soundcard with motu 828mkIII with same latency settings and there we go.. no problem.

[Taika-Kim]

It seems that Playtime doesn't take changing tempo into account?

Only when I started adding audio loops I noticed this...

I am building a live set based on several instances of Playtime a lot now, and this is a big problem, since different tunes have different tempo.

I see that it might be unpractical to have this realtime, but how about even a "calibrate" button that would calculate all playback rate values again for the loops?

Please consider this question!

Also I can report that now the 32 bit Win7 installer works without the error messages.

[Taika-Kim]

Also, the preset handling is bugged somehow.

Once all my loops (I had 48 MIDI loops in the only instance) were randomly placed for all pads. I mean, literally.

Now a strangest thing happened: after adding another instance of Playtime and saving a few times, the MIDI loops in the original instance were mirrored 1:1. So the last loops was now in the first pad, and the first in the last, and so on for all the loops.

I had saved the original preset, but now that I load it, a few of the slots are empty, altough all the files are in place on my memory stick where the project runs from.

[mehmethan]

Hi, I'm using Playtime with Launchpad. When I put a clip on Playtime, Launchpad responds with only red color to show that there is a clip on that pad. I wonder if there is a way to use different colors for different pads on launchpad.

[plamuk]

^ adjust the velocity output of the midi notes being routed back to the launchpad.

[mehmethan]

^ adjust the velocity output of the midi notes being routed back to the launchpad.

I know the velocity thing but :

How can I do that ? By default Playtime generates note on messages which has velocity of 1 to the midi out.That lights a red color on corresponding pad. So I think after Playtime I have to insert a midi plugin to change that velocity.

I think I need a plugin that changes a note's velocity value to a user defined velocity value.

example:
if the velocity of C1 is 1 than then change the velocity of C1 to 100
if the velocity of D2 is 1 than then change the velocity of D2 to 70
....

Am I wrong ? Could you help me on that ?

[plamuk]

try multiple instances of JS - velocity control after Playtime instances.

here's a handy list of values:

http://i.imgur.com/yxUMwR6.png

[mehmethan]

I got it and it works thanks.
But in my situation, I use 2 launchpads which makes 128 pads and 128 velocity control JS.
I just want to make some steady color patterns on launchpad which will make my life easier when playing live.It's really hard to memorize pads for me. Please check my videos on my signature and you'll get it.

Thanks again

[helgoboss]

Interested to see what else is in 1.2, and hope eventually to see some of my suggestions from post #136 based on the Mobius and Echoplex loopers considered.

On Playtime's website you can find the changelog and roadmap for Playtime (at the very bottom).


- Using "immediate" recording toggle, the recorded items don't sync up with the grid. Could Playtime offer an option to automatically stretch them to the correct length?


This is intended. "Immediately" means there's no alignment. If you want alignment, choose "Next Beat" or "Next Measure". Or are you talking about something inbetween? An exact description of what you want to achieve would be useful.


- Looped items tend to have clicks in them. This is a "feature" of Reaper, as you can't set fades for loop seams, but could Playtime offer an option to render a certain amount of fade in/fade out into the recorded item?


This can happen if you record audio and suddenly stop recording while you still have an input signal. How would you do adjust the loop in REAPER itself to make it seemless, without clicks? I guess I would record a little bit more than necessary at the beginning and the end of the loop and then somehow make a crossfade between the end and the beginning and take the result as the loop.


- Could use an option in the preferences to map the global record cc, instead of having to go to the track's envelope window


I'd like to leave the things which can be easily done in REAPER to REAPER. I still need to document it though.


- Got a crash in the end, can't remember how to replicate though. :P

Any chance you can still gather the fault module and offset as described here (http://forum.cockos.com/showthread.php?t=36653) in section "Post error/crash messages!"?


EDIT: Found it in the list of automatable parameters for the VST. However when recording into a slot using it, the resulting clip should automatically appear in the slot once the recording is complete (as per Live) and then start playing.

The recording should automatically appear in the slot after stopping recording using automation "Record Active Slot". If not, it might be a bug. Doesn't it appear in your case? The "then start playing" part is another feature ticket (#2 Play clip as soon as recorded). See roadmap.

Made a video, basic overview and demo
http://reaperblog.net/2014/12/video-helgoboss-playtime-plugin-demo/

Amazing! Thanks!

It seems that Playtime doesn't take changing tempo into account?

Only when I started adding audio loops I noticed this...

I am building a live set based on several instances of Playtime a lot now, and this is a big problem, since different tunes have different tempo.

I see that it might be unpractical to have this realtime, but how about even a "calibrate" button that would calculate all playback rate values again for the loops?

Thanks for spotting this. I hope to look into this soon. Ticket is here (https://bitbucket.org/helgoboss/playtime/issue/77/support-for-tempo-markers).

Also, the preset handling is bugged somehow.

Once all my loops (I had 48 MIDI loops in the only instance) were randomly placed for all pads. I mean, literally.

Now a strangest thing happened: after adding another instance of Playtime and saving a few times, the MIDI loops in the original instance were mirrored 1:1. So the last loops was now in the first pad, and the first in the last, and so on for all the loops.

I had saved the original preset, but now that I load it, a few of the slots are empty, altough all the files are in place on my memory stick where the project runs from.

Are you talking about "presets" as in REAPER's FX presets?: http://forum.cockos.com/attachment.php?attachmentid=22940&stc=1&d=1418598856

If yes, this is not officially supported by now. It might work by some extent.

Also, if you have several instances of Playtime running in the same project, try not to let them make use of the same items and it should be fine. Items should not disappear then. If you let them share items, it can happen. Note that "not sharing" items doesn't mean you cannot make use of the same audio/MIDI content. You actually can, using standard REAPER features (just duplicate the item, for MIDI you need to look into "pooled MIDI items")

I plan to add an option in future that copies the item when filled into a slot instead of moving it. That should make it much harder to actually share items between several instances.

Hi, I'm using Playtime with Launchpad. When I put a clip on Playtime, Launchpad responds with only red color to show that there is a clip on that pad. I wonder if there is a way to use different colors for different pads on launchpad.

There's no built-in way to do that. nym's suggestion should work. In future, I maybe will add limited support for this because it would also help to make Playtime compatible with Launchpad-similar controllers that just have different lights on different velocities (like the Akai APC40 for example).

[plamuk]

This can happen if you record audio and suddenly stop recording while you still have an input signal. How would you do adjust the loop in REAPER itself to make it seemless, without clicks? I guess I would record a little bit more than necessary at the beginning and the end of the loop and then somehow make a crossfade between the end and the beginning and take the result as the loop.


in REAPER, i usually record more than necessary at the end rather than the beginning. this way it lines up better on REAPER's timeline grid and items are easier to move.

we're talking about a couple MS here just to avoid the click. otherwise you start to potentially lose the transient on the new instance of the file.

mehmethan, you're very quickly going to outgrow REAPER's native midi handling. you should look into Bidule. i use it to stitch multiple controllers into 1 coherent system. follow this thread for a starter. http://forum.cockos.com/showthread.php?t=132383

[Taika-Kim]

Preset problems:
Yes I was talking about Reaper's internal preset management... But this has to be made 100% funcional, since isn't it basically the same thing as correctly saving/loading tunes with Playtime correctly? Or do they use a different system for managing plugin data? Since I also recall that once it happpened that a project had mixed up data for Playtime when I loaded it.. But now can't reacall for sure.

How about determining an item's playback speed only at the time it's triggered instead of when it's imported? Shouldn't this work to keep the items in sync with tempo?

Also, when importing some breakbeats, some of them were imported at 50% the intended value, altough they were from the same set of beats. I don't know though, how could this made more intelligent since Playtime can't know how many beats long the loop is meant to be originally. How is this determined now?

[helgoboss]

Preset problems:
Yes I was talking about Reaper's internal preset management... But this has to be made 100% funcional, since isn't it basically the same thing as correctly saving/loading tunes with Playtime correctly? Or do they use a different system for managing plugin data? Since I also recall that once it happpened that a project had mixed up data for Playtime when I loaded it.. But now can't reacall for sure.

You're right, it's basically the same mechanism as saving/loading REAPER projects. The number of cases that Playtime needs to handle is different though. If you change a preset, it can happen that the items referenced in that preset don't exist anymore because the project has changed since the preset was last modified. That kind of thing can't happen if you just save and load the REAPER project. I haven't experienced mixed up data on project load yet but I will have an eye on it. Please let me know if it occurs. A sample project would help in that case.


How about determining an item's playback speed only at the time it's triggered instead of when it's imported? Shouldn't this work to keep the items in sync with tempo?

That might do it. I added your idea as issue comment.


Also, when importing some breakbeats, some of them were imported at 50% the intended value, altough they were from the same set of beats. I don't know though, how could this made more intelligent since Playtime can't know how many beats long the loop is meant to be originally. How is this determined now?


Currently, it uses REAPER's native logic to determine the playrate.

[mehmethan]

Hi Helgoboss,
Today I had a major problem with Playtime. All my 6 hours of work dissappeared... I started a project using playtime. (4 Playtime on different tracks & 2 launchpads). Everthing was going normal. I was using playtime to trigger audio loops & samples and I was creating my live setup. I think 2-3 hours later playtime started to forget clips .I inserted items to playtime again but later playtime forgets the items. I saved project and started reaper again. Still same problem.I reinstalled playtime I configured again. No way... Every sample & and loop I've used are in the project directory. There is a big problem there. I also tried to save my setup as preset. But It still cannot find the items later.

Could you please help me ? (win 8.1 reaper 4.75 playtime 1.2- if it is neccessary I can send you my reaper project,too)

[helgoboss]

Hi Helgoboss,
Today I had a major problem with Playtime. All my 6 hours of work dissappeared... I started a project using playtime. (4 Playtime on different tracks & 2 launchpads). Everthing was going normal. I was using playtime to trigger audio loops & samples and I was creating my live setup. I think 2-3 hours later playtime started to forget clips .I inserted items to playtime again but later playtime forgets the items. I saved project and started reaper again. Still same problem.I reinstalled playtime I configured again. No way... Every sample & and loop I've used are in the project directory. There is a big problem there. I also tried to save my setup as preset. But It still cannot find the items later.

Could you please help me ? (win 8.1 reaper 4.75 playtime 1.2- if it is neccessary I can send you my reaper project,too)

Hi Mehmethan,

sounds a little like the problems described by Taika-Kim. I guess it's related.

Please send me your REAPER project via email (info@helgoboss.org). I hope the RPP itself (without audio files) is enough to figure out the problem.

Do the items also disappear from the REAPER timeline or just from Playtime?

Ben

[sinkmusic]

I think i experienced the same issue a couple of weeks ago.
When i saved a project, and the re-opened it, the original items position on the timeline was messed by Playtime, but no clip was loaded in Playtime itself : so, i had lost both my original arrangement, and my Playtime session.
I thought it was a demo limitation ?
I was using Win7, 64bit, if that helps.

[gwok]

here's another little vid showing some aspects of Playtime -


https://www.youtube.com/watch?v=NFJ631D3NSg

[sonnie]

Good video. Laughed a bit because of you are a little out of it. (no offense) ;)
I like your (osx) panel. What is this quicklaunch (?) mod?

[mehmethan]

Anyone using Playtime with Launchpad may find these 2 JS plugins useful. You can change the colors of pads in a way you want and make your color patterns on launchpad for your clips. These way it's easier to memorize what's on the pads without looking at your screen.
The first one is for row-14 of launchpad and the other is for rows 5-8.
Idea is simple.
Plugin changes the velocity of any specific note which has velocity 1. Altering the velocity you can change the colors on pad.

I'm not a programmer so I don't know if this is the best way to do it (performance/cpu) but it works.

Put these 2 JS after Playtime and add midi out for launchpad from the track you've inserted Playtime

Launchpad Color Control for Playtime (Row 1-4)

desc:Launchpad Color Control Row 1-4
slider1:1<0,127,1>1--------C-1
slider2:1<0,127,1>C#-1
slider3:1<0,127,1>D-1
slider4:1<0,127,1>D#-1
slider5:1<0,127,1>E-1
slider6:1<0,127,1>F-1
slider7:1<0,127,1>F#-1
slider8:1<0,127,1>G-1
slider9:1<0,127,1>2---------E0
slider10:1<0,127,1>F0
slider11:1<0,127,1>F#0
slider12:1<0,127,1>G0
slider13:1<0,127,1>G#0
slider14:1<0,127,1>A0
slider15:1<0,127,1>A#0
slider16:1<0,127,1>B0
slider17:1<0,127,1>3--------G#1
slider18:1<0,127,1>A1
slider19:1<0,127,1>A#1
slider20:1<0,127,1>B1
slider21:1<0,127,1>C2
slider22:1<0,127,1>C#2
slider23:1<0,127,1>D2
slider24:1<0,127,1>D#2
slider25:1<0,127,1>4----------C3
slider26:1<0,127,1>C#3
slider27:1<0,127,1>D3
slider28:1<0,127,1>D#3
slider29:1<0,127,1>E3
slider30:1<0,127,1>F3
slider31:1<0,127,1>F#3
slider32:1<0,127,1>G3



@block
while (
midirecv(ts,msg1,msg23) ?
(
vel=(msg23/256)|0;
note=msg23&127;
note == 0 && vel==1 ?
(
vel =+slider1;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 1 && vel==1 ?
(
vel =+slider2;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 2 && vel==1 ?
(
vel =+slider3;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 3 && vel==1 ?
(
vel =+slider4;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 4 && vel==1 ?
(
vel =+slider5;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 5 && vel==1 ?
(
vel =+slider6;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 6 && vel==1 ?
(
vel =+slider7;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 7 && vel==1 ?
(
vel =+slider8;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 16 && vel==1 ?
(
vel =+slider9;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 17 && vel==1 ?
(
vel =+slider10;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 18 && vel==1 ?
(
vel =+slider11;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 19 && vel==1 ?
(
vel =+slider12;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 20 && vel==1 ?
(
vel =+slider13;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 21 && vel==1 ?
(
vel =+slider14;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 22 && vel==1 ?
(
vel =+slider15;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 23 && vel==1 ?
(
vel =+slider16;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 32 && vel==1 ?
(
vel =+slider17;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 33 && vel==1 ?
(
vel =+slider18;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 34 && vel==1 ?
(
vel =+slider19;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 35 && vel==1 ?
(
vel =+slider20;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 36 && vel==1 ?
(
vel =+slider21;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 37 && vel==1 ?
(
vel =+slider22;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 38 && vel==1 ?
(
vel =+slider23;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 39 && vel==1 ?
(
vel =+slider24;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 48 && vel==1 ?
(
vel =+slider25;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 49 && vel==1 ?
(
vel =+slider26;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 50 && vel==1 ?
(
vel =+slider27;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 51 && vel==1 ?
(
vel =+slider28;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 52 && vel==1 ?
(
vel =+slider29;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 53 && vel==1 ?
(
vel =+slider30;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 54 && vel==1 ?
(
vel =+slider31;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 55 && vel==1 ?
(
vel =+slider32;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
(
midisend(ts,msg1,msg23); // passthru
);
bla=1;
);
);

[mehmethan]

Lauchpad Color Control For Playtime (row 5-8)

desc:Launchpad Color Control Row 5-8
slider33:1<0,127,1>5----------E4
slider34:1<0,127,1>F4
slider35:1<0,127,1>F#4
slider36:1<0,127,1>G4
slider37:1<0,127,1>G#4
slider38:1<0,127,1>A4
slider39:1<0,127,1>A#4
slider40:1<0,127,1>B4
slider41:1<0,127,1>6--------G#5
slider42:1<0,127,1>A5
slider43:1<0,127,1>A#5
slider44:1<0,127,1>B5
slider45:1<0,127,1>C6
slider46:1<0,127,1>C#6
slider47:1<0,127,1>D6
slider48:1<0,127,1>D#6
slider49:1<0,127,1>7----------C7
slider50:1<0,127,1>C#7
slider51:1<0,127,1>D7
slider52:1<0,127,1>D#7
slider53:1<0,127,1>E7
slider54:1<0,127,1>F7
slider55:1<0,127,1>F#7
slider56:1<0,127,1>G7
slider57:1<0,127,1>8----------E8
slider58:1<0,127,1>F8
slider59:1<0,127,1>F#8
slider60:1<0,127,1>G8
slider61:1<0,127,1>G#8
slider62:1<0,127,1>A8
slider63:1<0,127,1>A#8
slider64:1<0,127,1>B8



@block
while (
midirecv(ts,msg1,msg23) ?
(
vel=(msg23/256)|0;
note=msg23&127;
note == 0 && vel==1 ?
(
vel =+slider1;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 64 && vel==1 ?
(
vel =+slider33;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 65 && vel==1 ?
(
vel =+slider34;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 66 && vel==1 ?
(
vel =+slider35;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 67 && vel==1 ?
(
vel =+slider36;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 68 && vel==1 ?
(
vel =+slider37;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 69 && vel==1 ?
(
vel =+slider38;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 70 && vel==1 ?
(
vel =+slider39;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 71 && vel==1 ?
(
vel =+slider40;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 80 && vel==1 ?
(
vel =+slider41;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 81 && vel==1 ?
(
vel =+slider42;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 82 && vel==1 ?
(
vel =+slider43;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 83 && vel==1 ?
(
vel =+slider44;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 84 && vel==1 ?
(
vel =+slider45;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 85 && vel==1 ?
(
vel =+slider46;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 86 && vel==1 ?
(
vel =+slider47;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 87 && vel==1 ?
(
vel =+slider48;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 96 && vel==1 ?
(
vel =+slider49;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 97 && vel==1 ?
(
vel =+slider50;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 98 && vel==1 ?
(
vel =+slider51;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 99 && vel==1 ?
(
vel =+slider52;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 100 && vel==1 ?
(
vel =+slider53;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 101 && vel==1 ?
(
vel =+slider54;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 102 && vel==1 ?
(
vel =+slider55;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 103 && vel==1 ?
(
vel =+slider56;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 112 && vel==1 ?
(
vel =+slider57;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 113 && vel==1 ?
(
vel =+slider58;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 114 && vel==1 ?
(
vel =+slider59;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 115 && vel==1 ?
(
vel =+slider60;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 116 && vel==1 ?
(
vel =+slider61;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 117 && vel==1 ?
(
vel =+slider62;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 118 && vel==1 ?
(
vel =+slider63;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
note == 119 && vel==1 ?
(
vel =+slider64;

vel|=0;

vel > 0 ? midisend(ts,msg1,note+vel*256); // send note on
) :
(
midisend(ts,msg1,msg23); // passthru
);
bla=1;
);
);

[gwok]

I like your (osx) panel. What is this quicklaunch (?) mod?

not sure what you mean?

[Taika-Kim]

Yes something with the presets, one time I was emptying the Playtime pads with the "remove and delete item" option, when at some point after deleting an item, one other item from some other later slot was moved randomly to an earlier one... And this just kept happening every now and then.

[Nineofkings]

Can't wait to try this out!

[mehmethan]

Hi Helgoboss,
Is there any news about lost item issue and preset errors ? Do you have a release date for upcoming update with fixes ?

[helgoboss]

Hi Helgoboss,
Is there any news about lost item issue and preset errors ? Do you have a release date for upcoming update with fixes ?

I think I will be able to fix these issues until end of year.

Until then, try to workaround those issues by considering following advice:

- Don't switch project tabs while Playtime user interface is open (ticket #51 (https://bitbucket.org/helgoboss/playtime/issue/51/switching-project-tabs-with-playtime-open))
- Make sure that several Playtime instances don't share the same items (ticket #80 (https://bitbucket.org/helgoboss/playtime/issue/80/multiple-playtime-instances-should-never))
==> If you fill an item into a slot and it is already used by another Playtime instance, duplicate it first (Ctrl+D) and fill the slot with the duplicate instead.
==> Don't duplicate a Playtime track - because this currently means the new Playtime instance will refer to exactly the same items as the first one (ideally, the duplication would also duplicate the items themselves).
==> Don't use presets because this will often have the same effect.

Doing all this will be possible as soon as the fix is out, it's just a workaround for now.

[mehmethan]

I think I will be able to fix these issues until end of year.

Until then, try to workaround those issues by considering following advice:

- Don't switch project tabs while Playtime user interface is open (ticket #51 (https://bitbucket.org/helgoboss/playtime/issue/51/switching-project-tabs-with-playtime-open))
- Make sure that several Playtime instances don't share the same items (ticket #80 (https://bitbucket.org/helgoboss/playtime/issue/80/multiple-playtime-instances-should-never))
==> If you fill an item into a slot and it is already used by another Playtime instance, duplicate it first (Ctrl+D) and fill the slot with the duplicate instead.
==> Don't duplicate a Playtime track - because this currently means the new Playtime instance will refer to exactly the same items as the first one (ideally, the duplication would also duplicate the items themselves).
==> Don't use presets because this will often have the same effect.

Doing all this will be possible as soon as the fix is out, it's just a workaround for now.

Thanks...

[helgoboss]

Released Playtime 1.2.1 (http://www.helgoboss.org/projects/playtime/).

Changes:
#81 Added support for playing clips even if other project tab is open
#80 Added slot context menu entry 'Fill with copy of selected item'
#51 Fixed loss of items when changing project tab
#80 Fixed loss of items when sharing items across multiple Playtime instances (by totally avoiding shared items)

Please note the last change if you have used multiple Playtime instances per project in the past. Item sharing (2 slots controlling the same media item) was never intended by Playtime. In past versions, Playtime already prevented item sharing within a single instance. However, item sharing was still possible in case of multiple Playtime instances per project. Since Playtime 1.2.1, shared items are not possible anymore, no matter what. Now Playtime duplicates items whenever you try to use the same item in several Playtime instances.

If you have already used multiple Playtime instances in an existing project, chances are high they share items. If you open such a project with Playtime >= 1.2.1 installed, Playtime will ask you if it shall fix your project by duplicating the shared items. If you choose no, slots in the 2nd Playtime instance that were previously filled with shared items will stay empty.

[mehmethan]

Thanks for the fixes. I made a quick test and it seems alright. This week I'll try it with a big project again.

[plamuk]

here's a very useful but simple FR: can you give us the option to tint the background of playtime? this way, multiple instances won't get confused with one another.

[joffo78]

Hi. Congratulations for your wonderfull job.
It would be fantastic if you could add this improvements:
Deduce and set the general tempo of reaper after the first recording (regarding the lengh of the recorded clip). In this way we could have a marvelous looper tool !
record and play automation curve.
I don't know if it's possible but what i use to do in ableton live is using two tracks for "dummies clips" like this i can trig some clip on the first track which contain sound but the output is routed on the second which have clip that only contain automation curve. i can send a a sound with is own volume setting and in a second time , trig an other clip that modulates de volume of the first.
I hope my request would talking to you.
Regards.
JF

[K3Z]

YOU ARE AWESOME!!!!!!!!!

[PitchSlap]

Hi. Congratulations for your wonderfull job.
It would be fantastic if you could add this improvements:
Deduce and set the general tempo of reaper after the first recording (regarding the lengh of the recorded clip). In this way we could have a marvelous looper tool !


This is pretty much the key missing feature for me (I already requested it earlier and thankfully someone copied my suggestion to the PlayTime tracker).

It's really hard to underestimate how important this is. Anyone that has used any hardware looping pedal like the Gibson Echoplex, Roland Loop Station, or MobiusVST can easily attest...

(BTW there's a bunch of useful info in the "Global Quantization" FR in my signature ;) )

[Michi]

Assigning tracks to groups works fine for me but does not save.
Everytime I reopen the project all groups have been reset.
I have newest versions of reaper and playtime installed.

[jaakked]

Hello,

I`m trying to unlock playtime (on osx 10.9.5). The unlock button opens a panel but does not allow me to select the license file(or any other file for that matter).Any ideas? Obviously I`m not very smart but this is making me crazy.

[helgoboss]

Assigning tracks to groups works fine for me but does not save.
Everytime I reopen the project all groups have been reset.
I have newest versions of reaper and playtime installed.

This bug will be fixed in upcoming 1.3.0 (later this week).


Hello,

I`m trying to unlock playtime (on osx 10.9.5). The unlock button opens a panel but does not allow me to select the license file(or any other file for that matter).Any ideas? Obviously I`m not very smart but this is making me crazy.

The panel should allow you to select any file that ends with ".license". The license file delivered via email should have exactly this file extension. Maybe you renamed it?

[jaakked]

The panel should allow you to select any file that ends with ".license". The license file delivered via email should have exactly this file extension. Maybe you renamed it?[/QUOTE]

Thanks for your prompt reply!

But actually, the downloaded license file you gave me ended with the ".txt" file extension.
By deleting the ".txt" I was able to get it to work.

To be clear, the license file that was delivered via email does not end with".license" and must be changed to work.

Anyway,
Peace!

[helgoboss]

Released Playtime 1.3.0 (http://www.helgoboss.org/projects/playtime/)

Changes:
#79 Added support for REAPER pause button
#24 Added memorizing of playing clips (purple play button)
#24 Added option to play memorized clips with arrangement (when pressing REAPER play button)
#61 Added option to play arrangement with clips (no jump to end of project)
#2 Added option to auto-play recorded clips
#27 Added context menu entry 'Show track FX' to slots and groups
#12 Added support for scene drag'n'drop
#89 Added support for group drag'n'drop
#15 Added ability to set exclusive mode per group
#70 Fixed non-working group track loading
#84 Fixed retriggering/untriggering behavior, especially for one shots
#85 Fixed audio clips going offline when REAPER in background
#89 Fixed non-selectable license file if it ends with '.txt'
#90 Fixed loss of group track when changing project tab
Fixed occasionally hanging transport button and countdown

Please note: #84 changes existing behavior. In some special cases, pressing a slot play button or a MIDI trigger while a clip is already playing now has a different effect. Here (https://bitbucket.org/helgoboss/playtime/issue/84#comment-14544978) is an overview of the new retriggering/untriggering behavior. It's more consistent now.

The user guide doesn't reflect the latest changes yet. I will update it within the next days.

Happy new year!

[gwok]

great! looking forward to checking it out!

[helgoboss]

To be honest i find this extremely irritating and i'm very very interested how people can actually use Playtime without messing up their whole arrangement.
Why items have to be moved or muted/set offline at all when Playtime operates at the end of the project anyway?

Playtime doesn't always operate at the end of the project. Especially with the new version that has the option "Play arrangement with clips". For me, it would be quite irritating if an existing arrangement is cluttered with Playtime items all over the place (especially since these items are subject to move anyway). If they are not muted, things get not only confusing visually but also audibly. So I move them consequently to one place if not in use: The start of the project, muted and shortened to 1 measure. Actually for exactly this reason: To avoid "messing up" the whole arrangement :)

That said, I think there might be times when you don't want Playtime to move/mute/shorten the items automatically. For example if you want to edit some items in relation to each other. For such cases, I was thinking about a "Release Items" button (see #83 (https://bitbucket.org/helgoboss/playtime/issue/83)). But this really shouldn't be the normal behavior in my opinion.

Of course, if you have another idea how to approach this, please let me know.


To modify items more easily, why not mirroring clip selection in Playtime with item selection in arrange or scroll to selected (or dbl-clicked or ...) clip ?
I do like the double-click edit already.

While I don't think this replaces the need for moving and muting the items, I think this would be a good convenience feature.

[helgoboss]

Assigning tracks to groups works fine for me but does not save.
Everytime I reopen the project all groups have been reset.
I have newest versions of reaper and playtime installed.

This is fixed in the latest version.

[memyselfandus]

This would be HUGE for me at least.. Excellent update by the way!

If I could click on a cell and see a piano roll... maybe somehow have to load a bunch of tracks and fold them or something and when you click on a cell in playtime.. a different piano roll opens for each cell.. is this possible?

basically I want to be able to click on a cell like in Live where I can record or mouse in whatever I want into clips in playtime.. then drag them into where ever I want in the main timeline...

Has to be a way?

Thanks for all the hard work.

[helgoboss]

record and play automation curve.

This is also on my personal wishlist: #8 (https://bitbucket.org/helgoboss/playtime/issue/8/automation-only-items). The thing is REAPER doesn't have automation items. I think using some clever workarounds it's possible to implement it anyway. Still, I wonder whether REAPER 5 brings automation items. If yes, that would allow for a much smoother implementation of this feature. So before implementing this I will have a close look on the upcoming REAPER 5 prereleases.


Deduce and set the general tempo of reaper after the first recording (regarding the lengh of the recorded clip). In this way we could have a marvelous looper tool !

This is pretty much the key missing feature for me (I already requested it earlier and thankfully someone copied my suggestion to the PlayTime tracker).

It's really hard to underestimate how important this is. Anyone that has used any hardware looping pedal like the Gibson Echoplex, Roland Loop Station, or MobiusVST can easily attest...

(BTW there's a bunch of useful info in the "Global Quantization" FR in my signature ;) )

I will try to add this as an option (in local settings) to the next release. As the reference number of beats I would take the one currently set in REAPER (for example 4/4).

[nofish]

Released Playtime 1.3.0 (http://www.helgoboss.org/projects/playtime/)

The user guide doesn't reflect the latest changes yet. I will update it within the next days.


Please announce here when it's updated as I'm also about checking out Playtime and it'll be nice having the updated manual along with it.

[helgoboss]

This would be HUGE for me at least.. Excellent update by the way!

If I could click on a cell and see a piano roll... maybe somehow have to load a bunch of tracks and fold them or something and when you click on a cell in playtime.. a different piano roll opens for each cell.. is this possible?

basically I want to be able to click on a cell like in Live where I can record or mouse in whatever I want into clips in playtime.. then drag them into where ever I want in the main timeline...

Has to be a way?

Thanks for all the hard work.

Opening a different piano roll for each clip is already possible (REAPER preferences => Editing Behavior => MIDI Editor => One MIDI editor per media item).

But I think you are talking about creating new clips, out of nothing, without recording, is that right? Maybe what you want is #32 (https://bitbucket.org/helgoboss/playtime/issue/32/option-to-insert-an-empty-midi-clip-in-a) then. Double clicking an empty slot could create a one-measure-sized empty MIDI clip and open it in piano roll. Question is only on which track to place the new items. I guess using the group track would be consequent and if no group track set, creating a new one ... just thinking aloud.

[memyselfandus]

Opening a different piano roll for each clip is already possible (REAPER preferences => Editing Behavior => MIDI Editor => One MIDI editor per media item).

But I think you are talking about creating new clips, out of nothing, without recording, is that right? Maybe what you want is #32 (https://bitbucket.org/helgoboss/playtime/issue/32/option-to-insert-an-empty-midi-clip-in-a) then. Double clicking an empty slot could create a one-measure-sized empty MIDI clip and open it in piano roll. Question is only on which track to place the new items. I guess using the group track would be consequent and if no group track set, creating a new one ... just thinking aloud.

That's where I get lost :) no idea. my brain is fried for the day from messing with software all day.
I have my preferences like this already. very awesome feature. just the fact that reaper has this feature makes me think it may be possible with some brainstorming.

[memyselfandus]

Maybe a separate project tab just for this?? hmmmmmmmm

the only thing is you cant drag a midi clip from another project tab.. but you can Copy and paste between projects.. hmmm thinking.. anyone know if there is a keyboard shortcut for toggling project tabs? you could grab a item and while dragging.. hit the shortcut and drag into other project tab?

[memyselfandus]

Basically. If you could get Playtime to use items from another project tab I think this would work.

[PitchSlap]

I will try to add this as an option (in local settings) to the next release. As the reference number of beats I would take the one currently set in REAPER (for example 4/4).

Awesome. I'll be sure to test it out. :)

It's really great to be able to record any random ideas as they come, as I find the time fiddling around trying to fit it to a metronome can compromise the feel.

If you use Reaper's built in actions to calculate the initial tempo, just make sure to check the result is sensible as in my experience it often returns unreasonable numbers like 32 BPM when the actual tempo is 128 by assuming the wrong number of bars.

[helgoboss]

Please announce here when it's updated as I'm also about checking out Playtime and it'll be nice having the updated manual along with it.

The textual content is now up-to-date. Screenshots not yet.

[helgoboss]

If you use Reaper's built in actions to calculate the initial tempo, just make sure to check the result is sensible as in my experience it often returns unreasonable numbers like 32 BPM when the actual tempo is 128 by assuming the wrong number of bars.

Unfortunately there's no way Playtime reads your mind for number-of-bars detection ;)

Following ways how to approach this come into my mind:

1. Define a valid range of BPM values and stay within that range (e.g. define 32 BPM as unreasonably low and therefore assume the intended length of the recorded clip is only half as long as calculated and therefore choose 64 BPM instead)
2. Let the user set the intended number of bars in advance (that promises the best tempo detection but requires user interaction, compromises the feel)

[helgoboss]

Maybe a separate project tab just for this?? hmmmmmmmm

the only thing is you cant drag a midi clip from another project tab.. but you can Copy and paste between projects.. hmmm thinking.. anyone know if there is a keyboard shortcut for toggling project tabs? you could grab a item and while dragging.. hit the shortcut and drag into other project tab?

Basically. If you could get Playtime to use items from another project tab I think this would work.

Sorry, now I'm the one who's lost :) Sounds like a different request than #32 (https://bitbucket.org/helgoboss/playtime/issue/32/option-to-insert-an-empty-midi-clip-in-a). I need a more detailled description about what you want to achieve.

[PitchSlap]

Unfortunately there's no way Playtime reads your mind for number-of-bars detection ;)

Following ways how to approach this come into my mind:

1. Define a valid range of BPM values and stay within that range (e.g. define 32 BPM as unreasonably low and therefore assume the intended length of the recorded clip is only half as long as calculated and therefore choose 64 BPM instead)
2. Let the user set the intended number of bars in advance (that promises the best tempo detection but requires user interaction, compromises the feel)

All good ideas. Personally I think a user definable range in the options would be nice (I usually make music in "double-time i.e. 80BPM at 160) and assuming musically sensible phrase lengths like 2, 4, 8, or 16 bars should take care of most users.

[memyselfandus]

Sorry, now I'm the one who's lost :) Sounds like a different request than #32 (https://bitbucket.org/helgoboss/playtime/issue/32/option-to-insert-an-empty-midi-clip-in-a). I need a more detailled description about what you want to achieve.

Click on a Cell and it opens it's own piano roll (could be items in Reaper)
then you can drag the cells into the main project. would require a area in Reaper (Pip's or tracks from another project tab linked to the vst's or something.

HUGE

http://i.imgur.com/n8SxwkF.gif

[memyselfandus]

sorry about the image size guys but the thumbnail version turns off the animation.

[memyselfandus]

http://i.imgur.com/dbajkI6.gif

[winds350]

Is there a downloadable version of the manual? Preferably PDF, but even the html packaged up would be useful.

Thanks.

[MCCY]

Played a bit with mobius ... saved the project or just one loop. Then loaded it in playtime and using this simple tempodetection: (see attachement)
Worked very well!
It takes a bit too much time, but I think this should be relatively easy to use playtime to record such a file and then calculate tempo... If the tempo is realistic doesn't really matter to me, it should just fit. if its 32 when in fact 128... who cares...?
Hope reaper reacts fast enough for precise start and endpoint of the wav...

I'd just love to build everything from the beginning in a live situation with guitar, voice, cello etc. without being limited to the possibilities of the looper.

Martin

[PitchSlap]

if its 32 when in fact 128... who cares...?


It matters quite a bit actually, especially if you want to develop the project further with other tempo-aware instruments/effects and have a sensible arrangement grid.

Also since the Media Explorer only supports half or double-time tempo matching it wouldn't be possible to get anything to time-stretch properly with a messed up tempo.

It's not a hard thing to get right for 99% of users that aren't making 32BPM SloWave or Breakcore at 200BPM.

If it doesn't matter to someone if it's wrong, I don't see how they could possibly be bothered by it being right. ;)

[jm duchenne]

Hello,

Is there a way to avoid that the clips always start at the begining ?
That is, something like a pause/resume instead of play/stop ?

What I was hoping to do when I bought Playtime was to continue to play the files from the point they have been stoped previously.
I am not good for explaining in english, but is that clear ?

Thanks.

[flipotto]

Hey, just purchased... trying to wrap my head around it.

So I normally record in flac, and all the clips are recorded as wav, is there some way to make the clips use the flac that is already there?
Should I post over at your tracker?

Also - having a difficult time keeping the loops that are playing from drifting out of time...
I will keep playing with it to understand what is actually happening.

EDIT - making a little more sense now. Quantize input seems to help, my midi note entry.

Ok - so is there a way to navigate around playtime? Arrow keys do not work - just seems to work with mouse.
So what I want to do: I guess I should read the other feature requests...
1. Record group clips one after the other with minimal mousing. By pre assigning clips prior to recording. Lets say I want group 1 to be bass. I want to then pre assign all the clips in that group to the same input, be able to (mouseless) record clip 1 then down to clip 2 then three. Maybe a midi command to "record on a track" then the next clip. Not sure if this is clear.

I will go back and read this thread again, then check your site to vote and add requests.

[MCCY]

"It's not a hard thing to get right for 99% of users that aren't making 32BPM SloWave or Breakcore at 200BPM."

True. I can't wait for it to happen. The saving thing from Mobius is great, but too slow.

Is there a possibility to import multiple files at once? Just ha a case where accidently (should have been a bug in playtime) all importet files appeared in playtime at once. I would be allready wuite happy. Still like Mobius A LOT!

[MCCY]

Hm. Tried some things: I bet the biggest problem for tempo recognition will be reapers very slow recording button... It simply does not react immediately, otherwise I just would compose in realtime within the normal arrangement. If it would really start when hitting, tempocalculations and the first loop wouldn't be a promplem. Seems as if wav has to be recorded outside that limitations first and after that imported to Arrangement or Playtime.

Is there a way to make the recording react faster when hitting the record button?

[Taika-Kim]

I haven't installed 1.3 yet, but a few days ago this happened again:

The files were in alphabetical order before, and one time without explanation they were jumbled like this. No other instance uses the same files...
They used to be
a1 c1
a2 c2
a3 c3
a4 c4
b1 d1
b2 d2
b3 d3
b4 d4, etc

http://s21.postimg.org/r7g4vy2w3/reaper.jpg (http://postimg.org/image/r7g4vy2w3/)

[Taika-Kim]

Might it have an effect, that the MIDI files referenced are not in the project directory anymore, they reside only inside the project?

I saved the preset with the correct ordering from a backup, and loading that in the latest version of the project resulted in a correct ordering, apart from three slots that were empty for some reason.