reaper-oss / sws

The SWS extension is a collection of features that seamlessly integrate into REAPER, the Digital Audio Workstation (DAW) software by Cockos, Inc
https://www.sws-extension.org/
MIT License
456 stars 85 forks source link

Loop media file in selected tracks: custom sync #442

Open Jeff0S opened 10 years ago

Jeff0S commented 10 years ago

From pyt...@yahoo.com on January 04, 2012 20:20:04

Hey Guys, Happy New Year!!!

I found a small bug with the new "Loop media file in selected tracks(sync with next measure)" action. With the transport running execute the action then press stop on the transport. What happens is if your using an audio file as the media it continues to loop, which is expected, but at the beginning of each loop there is a spike/glitch in the audio until you press play again.

And here are some ideas that I think would make the sync actions super flexible. ;)

How about custom sync "Play media media file in selected tracks" as-well as "Loop media file in selected tracks" slon-n actions.

Ideally this would have an options dialog that could be called up within REAPER to set the actions up pre-execution, but if not/or in the mean time until the options dialog can be programmed it could be set up in the S&M.ini. Here are some examples using the .ini for setup.

S&M_LOOPMEDIA_SELTRACK_SYNC=2(1.000/1.500) ;Slot(1) would sync to next second, Slot(2) to next 1.5sec, etc.., S&M_LOOPMEDIA_SELTRACK_SYNC=10[1-5]1.000[6-10]2.000 ;Slots(1-5) sync to next sec., slots(6-10) sync to next 2sec.

Sync numbers could be prefaced with a letter to denote the sync format. Examp; f=frames m=measures s=samples t=exact time minuets/seconds/milsec. would not be prefaced they would just be setup like. Examp; (1:1.250) would = 1min.,1sec.,250milsec. (1.000) would = 1sec

Then here is another cool idea.., each number could also have a suffix Examp; r=retrigger ;Current playing media would be stopped and then retriggered from start of media c=complete ;Current playing media would play all the way through.
no suffix would = one-shot

So to clarify in this examp.

S&M_LOOPMEDIA_SELTRACK_SYNC=3(m1r/m1c/m2) ; Slot(1)would sync & retrigger from start of media on every measure Slot(2)would sync & continue until end of media and be triggered on every measure(if media was longer than one measure you would have overlapping instances playing) Slot(3)would sync & play only once(in this examp. that would be on measure 2)

A person could combine formats and trigger types in one option like;

S&M_LOOPMEDIA_SELTRACK_SYNC=71-3,4-7; In this examp. Slot(1)would sync and trigger on every measure(the entire media would play) Slot(2)would sync and retrigger from start of media every 2400 samples. Slot(3)would sync and play only once at time 1.3.3 Slots(4-7) would sync and and play only once 5secs form when it was triggered.

Let me know what you think?

Anton

Original issue: http://code.google.com/p/sws-extension/issues/detail?id=442

Jeff0S commented 10 years ago

From jeffos...@gmail.com on January 05, 2012 13:35:27

1) the "defect" MediaFileLockAudio=1? remember the compromize ( https://code.google.com/p/sws-extension/issues/detail?id=435 ) ?

2) the FR thoughtful! but a bit complicated to use.. but I see what you would like..

Jeff0S commented 10 years ago

From pyt...@yahoo.com on January 05, 2012 16:17:42

Oh.., yeah, the compromise. It's not really that big of problem anyway, so no need for a fix.

As far as the FR.., yeah I realize it seems a bit complicated. With an options dialog it would be a lot easier to grasp and setup, but I was just thinking in terms of doing it all from the .ini and being able to do it through only two actions(the Play media, and the Loop media).

How does this sound..., one time format(I think sec:millisec would work nice) and then three sets of slot-n actions? So it would be something like this. In the .ini there would be the time parameter.., examp. SyncTime=1.500. Then the three sets of actions that would use this parameter would be. 1)"Loop media file in selected tracks(sync with SyncTime)slot-n" 2)"Play media media file in selected tracks(sync with SyncTime)slot-n" 3)"Loop (retrigger)media file in selected tracks(sync with SyncTime)slot-n"

1&2 would work pretty much the same way the current sync to next measure actions but would sync to the SyncTime parameter value.

3 would restart the media according to the SyncTime even if the media is longer then the SyncTime value, so give a SyncTime=1.500 the media would start 1.5 seconds after the action was first executed and then retrigger every 1.5 seconds thereafter.

I think this would pretty much accomplish all of what I mentioned in the first post. Are you up for it? If not.., it's cool, I'll understand. :)

Jeff0S commented 10 years ago

From jeffos...@gmail.com on February 09, 2012 12:01:54

renamed/changed to FR since 1) is not a bug

about 2), the FR

Technically speaking only "measure customization" would be possible..

Owner: jeffos...@gmail.com
Labels: -Type-Defect Type-Enhancement

Jeff0S commented 10 years ago

From jeffos...@gmail.com on February 09, 2012 12:09:00

Summary: Loop media file in selected tracks: custom sync