When I start Playtime, Reaper is starting too. But when I stop playing Playtime, the playback of Reaper is still going on and never stops again. Is this the normal behavior?
I have a 10 channel track that I would like to record into using playtime. I have set the input to 10 channel so if I record in the normal fashion I get a 10 channel file.
I would like to create a live recorded loop with a 10 channel file and would expect the file to be generated when recording using playtime to be 10 channels, however when I record using playtime the file is only two channels.
Is it possible to get a 10 channel file recorded using playtime?
(Sidenote, I am looking at playtime because of abletons lack of surround capabilities.)
Write Mode Problem with MIDI toggle off - Playtime as an Instrument
Hi Ben,
At times I am using Playtime slots to act like an instrument / sampler. I have audio clips with MIDI toggle mode set to off and - typically - play start time and play stop time set to immediately (note: I can reproduce the problem whenever MIDI toggle is off regardless of start/top times, however it is more pronounced when start/stop times are set to immediately).
While I am just triggering the clips via MIDI everything works as expected. Even very short triggers like stuttering a vocal clip or finger drumming style play work. I use a Launchpad Pro as MIDI controller to Playtime. Of course I can also record the MIDI input and play everything afterwards, still no problem.
When using Playtime's Write Mode to actually "stamp" the clips on the corresponding tracks I get timing problems: Sometimes clips from the same slot overlap in time which creates multiple takes. Since I have just one pad to trigger one clip that should of course never happen (I cannot logically have one pad on and off at the same time or on "multiple times"). Also, sometimes Playtime accidentally writes the entire clip although I released the pad already. All of this happens only if I very rapidly tap on the pad. It seems that Write Mode causes Playtime to become quite inaccurate in terms of sensing MIDI events in time and writing them onto the track at exactly those times. This is weird because without Write it is perfectly precise. Possibly also linked to Reaper's API you are using for writing clips...
I had the suspicion that maybe the sluggishness tolerance had something to do with this behavior but even setting it to 0 did not help.
Do you have any idea what the cause could be and if there is any remedy?
As always - thank you for your consideration and creating this fabulous tool!
Hmm... I'm thinking its from the fact that the whole clips/items are repeated when they play, instead of their lengths being elongated and thus looped overtime.
I think that changing that could maybe fix that problem.
Apologize if this has been covered already but... can Playtime "midi-learn" scroll up/down and left/right? I have a Launchpad and want the up/down arrows, and left/right arrows (top left of the Launchpad) to scroll through the clips/scenes (rows and columns) and have all the lights match wherever I am, much in the same way Ableton does.
I am running the latest version of Playtime, and Reaper... bought Playtime a few years ago (at version 1.0 I think)... just got around to messing with it again.
Thanks everyone!
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Apologize if this has been covered already but... can Playtime "midi-learn" scroll up/down and left/right? I have a Launchpad and want the up/down arrows, and left/right arrows (top left of the Launchpad) to scroll through the clips/scenes (rows and columns) and have all the lights match wherever I am, much in the same way Ableton does.
I am running the latest version of Playtime, and Reaper... bought Playtime a few years ago (at version 1.0 I think)... just got around to messing with it again.
Thanks everyone!
This is exactly what I want too (except, that I'm using other footswitches & don't need lights)!!!
I'm so curious, if my new prototype footswitch will work with playtime. I decided to do it chromatically not the ableton way, because I like the Idea of a MIDI bass pedal too :-)
I tried to set up Playtime again, now using my chromatical Footswitch, which seemed to work nice, until I found, that presets are messed up randomly so I can't save my settings for MIDI controlling :-(
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. Please check it out and let me know what you think. Would appreciate any feedback
as stated in the main post it is a very handy overview of certain sections of all of your tracks. They can be immediately played and thus randomly combined to grant a vast variety of your songs. The structure is not necessarily fixed with your arrangement anymore and so gives you a great opportunity for eg. live performing - streching / remixing your songs.
@helgoboss
You sir are going to be my hero for ages!! This is what I always waited for in Reaper! Thanks so much!!
When I start Playtime, Reaper is starting too. But when I stop playing Playtime, the playback of Reaper is still going on and never stops again. Is this the normal behavior?
This is normal behavior (Playtime needs a continuously running transport).
Quote:
Originally Posted by Thor
Hi all.
I have a 10 channel track that I would like to record into using playtime. I have set the input to 10 channel so if I record in the normal fashion I get a 10 channel file.
I would like to create a live recorded loop with a 10 channel file and would expect the file to be generated when recording using playtime to be 10 channels, however when I record using playtime the file is only two channels.
Is it possible to get a 10 channel file recorded using playtime?
(Sidenote, I am looking at playtime because of abletons lack of surround capabilities.)
Thank you!
Right now, recording from inputs offer up to 2 channels. Recording from track offers up to 8 channels. I created a ticket for that.
Quote:
Originally Posted by brummbear
Hi Ben,
At times I am using Playtime slots to act like an instrument / sampler. I have audio clips with MIDI toggle mode set to off and - typically - play start time and play stop time set to immediately (note: I can reproduce the problem whenever MIDI toggle is off regardless of start/top times, however it is more pronounced when start/stop times are set to immediately).
While I am just triggering the clips via MIDI everything works as expected. Even very short triggers like stuttering a vocal clip or finger drumming style play work. I use a Launchpad Pro as MIDI controller to Playtime. Of course I can also record the MIDI input and play everything afterwards, still no problem.
When using Playtime's Write Mode to actually "stamp" the clips on the corresponding tracks I get timing problems: Sometimes clips from the same slot overlap in time which creates multiple takes. Since I have just one pad to trigger one clip that should of course never happen (I cannot logically have one pad on and off at the same time or on "multiple times"). Also, sometimes Playtime accidentally writes the entire clip although I released the pad already. All of this happens only if I very rapidly tap on the pad. It seems that Write Mode causes Playtime to become quite inaccurate in terms of sensing MIDI events in time and writing them onto the track at exactly those times. This is weird because without Write it is perfectly precise. Possibly also linked to Reaper's API you are using for writing clips...
I had the suspicion that maybe the sluggishness tolerance had something to do with this behavior but even setting it to 0 did not help.
Do you have any idea what the cause could be and if there is any remedy?
Actually I would have also suspected the sluggishness tolerance. But yes, it must be something else then. I'll have a look. Ticket 269.
Quote:
Originally Posted by themixtape
Apologize if this has been covered already but... can Playtime "midi-learn" scroll up/down and left/right? I have a Launchpad and want the up/down arrows, and left/right arrows (top left of the Launchpad) to scroll through the clips/scenes (rows and columns) and have all the lights match wherever I am, much in the same way Ableton does.
I am running the latest version of Playtime, and Reaper... bought Playtime a few years ago (at version 1.0 I think)... just got around to messing with it again.
Thanks everyone!
Should be already possible with the normal Launchpad and more than 8x8 slots by selecting "Launchpad" as controller. Doesn't this work?
Quote:
Originally Posted by MCCY
I tried to set up Playtime again, now using my chromatical Footswitch, which seemed to work nice, until I found, that presets are messed up randomly so I can't save my settings for MIDI controlling :-(
Do you use Playtime in combination with ReaLearn? Or normal REAPER automation? How and when does it get messed up?
Quote:
Originally Posted by gwok
Hi,
I've was running 1.12.- and now 1.12.1, and in both the "Play clips with arrangement" does not seem to be working. Is anyone else experiencing this?
I am on
Reaper 5.4 64bit
osx 10.9.5
cheers
edit: found it, was the preference VST>Don't flush plugins on stop/reset
Oh, interesting find! I'll try to automatically enable this whenever Playtime is active.
When using Playtime's Write Mode to actually "stamp" the clips on the corresponding tracks I get timing problems: Sometimes clips from the same slot overlap in time which creates multiple takes. Since I have just one pad to trigger one clip that should of course never happen (I cannot logically have one pad on and off at the same time or on "multiple times"). Also, sometimes Playtime accidentally writes the entire clip although I released the pad already. All of this happens only if I very rapidly tap on the pad. It seems that Write Mode causes Playtime to become quite inaccurate in terms of sensing MIDI events in time and writing them onto the track at exactly those times. This is weird because without Write it is perfectly precise. Possibly also linked to Reaper's API you are using for writing clips...
Hi brummbear. I know what causes this: Whenever Playtime stops an audio clip immediately, it actually doesn't stop it immediately but adds 100ms more so the item fade-out can be applied by REAPER. Without this fade-out, you would most likely hear a click in live-playing. This fade-out is applied no matter if write mode is on or off.
So yes, this can definitely cause multiple overlapping items on several lanes! But it should not create multiple takes of one item. And it should not affect timing - the clip start and end times should be exactly the same as without write mode.
Now some questions:
1. In your case, was it really creating multiple takes? Or just overlapping items?
2. Does this really cause timing issues or were you just surprised by the fact that things overlap?
What I could do in case of such a quick repetition within the 100ms phase: Just writing the items side-by-side without any gap inbetween. But I don't want to invest time into that unless I know the current solution causes issues.
Hi brummbear. I know what causes this: Whenever Playtime stops an audio clip immediately, it actually doesn't stop it immediately but adds 100ms more so the item fade-out can be applied by REAPER. Without this fade-out, you would most likely hear a click in live-playing. This fade-out is applied no matter if write mode is on or off.
So yes, this can definitely cause multiple overlapping items on several lanes! But it should not create multiple takes of one item. And it should not affect timing - the clip start and end times should be exactly the same as without write mode.
Now some questions:
1. In your case, was it really creating multiple takes? Or just overlapping items?
2. Does this really cause timing issues or were you just surprised by the fact that things overlap?
What I could do in case of such a quick repetition within the 100ms phase: Just writing the items side-by-side without any gap inbetween. But I don't want to invest time into that unless I know the current solution causes issues.
Hi Ben,
Thanks for looking deeper into this!
1. You are right: It's overlapping items, not takes.
2. It does create timing issues because Playtime writes items that should not be there. I did a quick test to reconfirm this. As you can see in the attached screenshot multiple overlapping items were written. The full loops (upper 3 long items) should not be there since I released the pad. The "stairs" of short items are OK. The overlap between the last two short items can be explained by the 100ms rule that you described above.
I also confirmed that this ONLY happens if using Playtime's Write mode. Without Write there is no issue, i.e realtime play works just fine. Same if just recording the MIDI events and then letting Playtime create the items on the fly during playback or rendering does not cause problems. The issue is with writing items.
In a subsequent test I also recorded the MIDI input coming from Launchapd. Just to be safe I also set the sluggishness tolerance to 0ms in Playtime. My observations for Write mode were as follows:
a) MIDI events were correctly recorded, no overlapping issues here.
b) The lag between MIDI event (Note ON) and Playtime writing the item on the timeline was constantly 20ms. Seems pretty long, but acceptable.
c) The length of the item written by Playtime is always = length(MIDI note) + 200ms. E.g. MIDI note = 50ms => item written = 250ms, MIDI note = 500ms => item written = 700ms etc.
I found the last point interesting as I was expecting from your description the item to be just 100ms longer than the MIDI event.
Finally I also did a render from the MIDI events. The lag of 20ms and length +200ms were just like with items in write mode. No issue with overlaps as in write mode.
Hi Ben, I use your Playtime by some months and it works good.
I have a question, it's possible to change the slots dimensions ? I just started to use reaper on a touchscreen laptop, so i use all the features by pressing the screen without interfaces like launchpad,push,ecc
I think it's a awesome improvement if i could change the measures of the slots (
height and width), and to hide the trigger button on the right of the slots.
Moreover, i guess if it's a difficult improvement to insert some button on the interface for the basic operation about slots, ex. UNDO, REDO, RECORD MODE, ecc..
to avoid the necessity of open the menu on slots by right-clicking
I am not sure if i know how to do this ..
1. I am keen on using PTime for MIDI clips. Is there an way to input quantize
while recording midi ?
2.Is there a way to drop Vsti for a certain group row right from the helgoboss UI ?
I think it would be great it the Playtime website contained a separate, easy to find section with "certified" (verified) controllers. It is not clear now if e.g. Launchpad MkII, Pro, Behringer CMD Touch TC64 and some Akai models would work properly.
Hi Ben,
Thanks for looking deeper into this!
1. You are right: It's overlapping items, not takes.
2. It does create timing issues because Playtime writes items that should not be there. I did a quick test to reconfirm this. As you can see in the attached screenshot multiple overlapping items were written. The full loops (upper 3 long items) should not be there since I released the pad. The "stairs" of short items are OK. The overlap between the last two short items can be explained by the 100ms rule that you described above.
I also confirmed that this ONLY happens if using Playtime's Write mode. Without Write there is no issue, i.e realtime play works just fine. Same if just recording the MIDI events and then letting Playtime create the items on the fly during playback or rendering does not cause problems. The issue is with writing items.
In a subsequent test I also recorded the MIDI input coming from Launchapd. Just to be safe I also set the sluggishness tolerance to 0ms in Playtime. My observations for Write mode were as follows:
a) MIDI events were correctly recorded, no overlapping issues here.
b) The lag between MIDI event (Note ON) and Playtime writing the item on the timeline was constantly 20ms. Seems pretty long, but acceptable.
c) The length of the item written by Playtime is always = length(MIDI note) + 200ms. E.g. MIDI note = 50ms => item written = 250ms, MIDI note = 500ms => item written = 700ms etc.
I found the last point interesting as I was expecting from your description the item to be just 100ms longer than the MIDI event.
Finally I also did a render from the MIDI events. The lag of 20ms and length +200ms were just like with items in write mode. No issue with overlaps as in write mode.
Man i reported this a long time ago, glad you have been able to post it better than i could, because everybody just said that "It never happens to me" when i posted it hahaha, hope this gets fixed, finger drumming in to a track is terrible in playtime for me.
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
I do not know where to post bug report, as i did it on bitbucket and no answer for 3 months.
Basically, latest versions of Playtime (and ReaLearn!) is not loading at all... Just getting the same message as on a screenshot in attachment.
Made a "portable" clean install of Reaper to check if something wrong with my installation - same stuff, same message. I use OS X 10.9.5, latest Reaper version and latest SWS.
Version 1.11 works, but i cannot have it docked, Reaper crashes...
I found an issue with the APC Mini - presumably this would be the same issue with the APC 40.
What's happening is that whenever a clip is deleted or when a clip is moved from one cell to another the light for the button is not turning off.
I put a MIDI monitor on it and saw this:
0: 80 1B 00 [Note Off] chan 1 note 27
It looks like what is happening is that a Note Off is being used instead of a Note On with a velocity of zero. I realize by convention they are treated the same butfor the APC Mini it has to be an actual Note On message.
I wrote a JS script to be able to turn off all the lights (then essentially Playtime resets), but it would nice to not have to do this step.
Also clicking the broom does the same thing, sending out a bunch of Note Off messages instead of Note Ons
Awesome, thanks!!!! I haven't even tried it yet but that should work perfectly, I'm doing something similar in the JSFX I wrote to manually set light colors. Not sure why I didn't think of doing it this way, but I am very very appreciative that you did, this is gonna be great!
Awesome, thanks!!!! I haven't even tried it yet but that should work perfectly, I'm doing something similar in the JSFX I wrote to manually set light colors. Not sure why I didn't think of doing it this way, but I am very very appreciative that you did, this is gonna be great!
EDIT: Works perfectly, thanks again.
You're welcome.
I've attached the APC mini config. Put the json file in
Mac OS X: /Users/USER_NAME/Library/Application Support/Playtime/controllers
If you attempt to use playtime as a looper, turn off Smooth Seeking (Options/Smooth Seeking) as it causes glitches. It may cause problems elsewhere but I've only had Playtime for a couple of days.
Thought I should report this as I couldn't find it in the docs or this thread.
How to reproduce:
Turn on Smooth Seeking
Auto-play recorded clips = On
Select clip
Detect tempo from recording
record a couple of bars
There's a glitch before the clip loops as it should
Hi, if using Playtime with the default Launchpad control settings, using the arrow keys navigates the grid beyong the 8x8 but do the light on the launchpad correspond to the new grid position in Playtime please?
Also, I see on the bitbucket there are plans for Launchpad pro support - any idea of a timeframe and will this include corresponding clip colour feedback on LPP?
Thx in advance.
Unfortunately not. And no session overview mode unfortunately. The lights on my APCmini don't update. They're hard wired to the 8x8 grid. I assume it's the same for a launchpad.
LPP might work out the box, and if it doesn't, it's quite easy to make your own controller map, with feedback.
However, I have found that you can switch between playtime instances (on separate tracks - they seem to conflict if they're on the same track) and update control surfaces by clicking on the sweeping brush icon. Though I don't think that's possible without using a mouse.
What I'm looking for is an all-in-one-box editor and play-on play-off button-actuated clip player. I may have as many as 40 play-on/off live cues for live awards presentations. A hardware box that works is called Instant Replay.
But the editing in no way rivals a DAW like Reaper.
Function would be simply: import audio to the reaper track, edit, eq and level adjust. Then assign this clip to a button on the screen. (Also, assigning to hardware buttons for live is always better if possible.)
How to trigger them so they lock and loop? When I trigger a 20 second clip, unless i hold the midi key, it stops to the beat.... any help would be greatly appreciated!
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Hi Ben,
First of all, thanks so much for your hard work on this project!
As a blind creator, I would love to be able to use Playtime.
I use Reaper with the addition of an extension called Osara and it gives blind users access with a screen reader, and the ability to use most functions in Reaper.
I know that there are many of us who would like the ability to launch clips ETC.
I would personally love to use reaper and PlayTime as a live looper and play clips and loops along with my live playing.
anyway, I just wanted to mention that there are a few of us interested, and exploring PlayTime to see what suggestions we can make to make it possible for us to use PlayTime.
interacting with PlayTime from outside the playtime window
Hi folks,
@PitchSlap and @Helgoboss,
@PitchSlap, I would really love to use Playtime as a live looper. How are you efforts coming on this front?
I happen to be blind. I can use Reaper just fine with my screen reader, but the Playtime window is unaccessible with the extention that makes Reaper accessible.
However, since so many aspects of PT are able to be controlled by midi, I think it could be possible to use without interacting with the interface at this point.
Pitchslap, have you been able to improve the midi learn functions for Playtime from outside of Playtime? How is this done? Can i set up a button to select and activate a slot, record in to that slot, play and stop that slot?
I am really excited about using Playtime because I love using Reaper.