SlowPlayRate Bug(s)

[NextLevel]

Devs,

First part of bug:
When I set the psminv= to 0.00050000 in reaper.ini and then also set REAPER's PlayRate to the same and start playback from 0:00.000 the start time jumps to
-0:00.038 then it takes a few seconds before the playcursor shows up.

Second part of bug:
If you notice in the licecap, the fader is moving before the playcursor and when the playcursor becomes visable it jumps ahead to about 0:00.006 and as it loops you'll notice the envelope slider is not in sync with what is drawn in the lane.


--------^^^--------The above issue has been fixed--------^^^-------- as of v5.20beta6--------

Here is another little inconsistency:
In this licecap I'm using alt/shift/ctrl/shift+ctrl each with a single mousewheel up/down click first over the fader then over the value field. The expected behavior for the fader should be that of the value field.




Justin,

I sent you a pm back in December that listed some other issues related to the psminv and psmaxv settings of the reaper.ini. If you did'nt get it or can't find it, I can resend it?

It would be so awesome if these issues could be fixed. If any of this needs clarifying or you need any more info please let me know.

Thank you

[Dstruct]

Which REAPER version?

[NextLevel]

The latest beta, on Windows Vista

[ivansc]

O.P.: Just being nosey, but WHY are you playing stuff back at 0.0005 of normal playrate in the first place? Seems like an odd thing to do, so I would love an explanation.

[NextLevel]

Originally Posted by ivansc

WHY are you playing stuff back at 0.0005 of normal playrate in the first place?

Sound design, alot of vst/vsti's sync parts of their algorithms to the playrate. I also use playrates in the 100's or even 1000's range. Some pretty cool sounds can be found in this way. Then I record short snippets of these sounds and load them into a sampler and use them as instruments.

[ivansc]

Aha! Thanks for the explanation.
You learn something new every day - even at my age!

[Justin]

I have some fixes for these in the works, but they are in a section of code that I hesitate to touch much, so they will come after 5.20.

In the interim: you can disable "use audio driver reported latency" in preferences/recording, and make sure the latency values are all set to 0, and it should behave more like you expect.

[NextLevel]

Great news, thank you so much Justin.

I can imagine that section of code can be tricky to deal with, just because so much else relies on it and making changes could cause problems to arise in other areas, let's hope that is not the case. Anyway, when the fixes arrive I'll be sure to test really well and let you know if I discover any issues.

Thanks!

[NextLevel]

Originally Posted by NextLevel

Devs,

Here is another little inconsistency:
In this licecap I'm using alt/shift/ctrl/shift+ctrl each with a single mousewheel up/down click first over the fader then over the value field. The expected behavior for the fader should be that of the value field.




Justin,

I sent you a pm back in December that listed some other issues related to the psminv and psmaxv settings of the reaper.ini. If you did'nt get it or can't find it, I can resend it?

It would be so awesome if these issues could be fixed. If any of this needs clarifying or you need any more info please let me know.

Thank you

Originally Posted by Justin

I have some fixes for these in the works, but they are in a section of code that I hesitate to touch much, so they will come after 5.20.

Justin,

Are these fixes still forthcoming?

I just ran into another roadblock, I was planning on writing a script that would open a gui showing the PlayRate and BPM of each currently open project tab and allow adjusting of each one without having to switch tabs. Looking through the api I don't see anyway of accomplishing this. Would you be willing to add Get/Set_Project_PlayRate() & Get/Set_Project_BPM()?

Thank You

[Justin]

Originally Posted by NextLevel

Are these fixes still forthcoming?

They are in 5.21+

I just ran into another roadblock, I was planning on writing a script that would open a gui showing the PlayRate and BPM of each currently open project tab and allow adjusting of each one without having to switch tabs. Looking through the api I don't see anyway of accomplishing this. Would you be willing to add Get/Set_Project_PlayRate() & Get/Set_Project_BPM()?

Let me look at that

[NextLevel]

Originally Posted by Justin

They are in 5.21+

I know the two issues that I listed as "First part of bug" & "Second part of bug" in the first post of this thread have been fixed, however the one in the lice cap of the PlayRate slider regarding the mousewheel is still present.

The other issues, in that pm I mentioned are also still present as of 5.27pre2.
Here is a copy of that pm just in case.

"I often use the master playrate as a sound creation tool and while hacking around the reaper.ini discovered that it's possible to set the playrate to much higher/slower rates than reaper defaults to. I found that I can get some really interesting sounds out of various VST/VSTi using playrates in the 10's, 100's or even 1000's range.

Now, on to the issue(s), listed in order of importance.

So what I fist do is either hack the reaper.ini or a project file and change the PLAYRATE entry to 100 for example. Then when I open the project the playrate slider range goes upto 100, but...

1) When using OSC message /playrate/raw and sending a value above 4.0 it results in the playrate being set to 4.0. Sending a value below 0.25 results in playrate being set to 0.25.

2) When entering rates into the playrate text box, anything above 10.0 seems to audibly start over from 1.0.., so (11.0 = 1.0, 12.0 = 2.0, etc.) However, using the playrate slider results in the correct audible outcome.

So you know how you can right click the slider and select different ranges?
Well what would be awesome is if there was an option in this dropdown titled "Custom" which sets the range and rate of change based on what the user sets it to in either the reaper.ini or project file. What I refer to as "rate of change" would be the amount that the value increases/decreases by with each mousewheel click or when dragging the slider.

3) There are issues with the master playrate envelope aswell.
You can manually edit a project file to have envelope rates above 4.0,
but visually the envelope is not correct and adjusting a point that is above 4.0 results in it being set to 4.0."

[NextLevel]

Originally Posted by Justin

Let me look at that

Thank you

[NextLevel]

Originally Posted by NextLevel

Justin,

I just ran into another roadblock, I was planning on writing a script that would open a gui showing the PlayRate and BPM of each currently open project tab and allow adjusting of each one without having to switch tabs. Looking through the api I don't see anyway of accomplishing this. Would you be willing to add Get/Set_Project_PlayRate() & Get/Set_Project_BPM()?

Thank You

Originally Posted by Justin

Let me look at that

Was just wondering if you ever looked into it?
I've got my script ready to go, was just hoping that you'd be able to add the requested api.

If you do add those to the api could you please allow for PlayRates in the range of 0.0005 for the low end and maybe somewhere between 1,000-10,000 for the high end? It would definitely put a huge one of these on my face.

Thank you

[NextLevel]

bump

[NextLevel]

Justin,

Sorry to be so persistent, but I could really use API commands for setting the playrate and tempo of a specific loaded project.

We already have Master_GetPlayRate(ReaProject project).
What I would like is Master_SetPlayRate(ReaProject project)
as well as these two;
Master_GetTempo(ReaProject project)
Master_SetTempo(ReaProject project)

You said you would look into this back in October, so I was wondering if these are going to be added to the API or not?

Thank you