Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S&M Resources - Auto saved tempalte contents doesn't sync to tempo #552

Closed
Jeff0S opened this issue Jul 8, 2014 · 5 comments
Closed

S&M Resources - Auto saved tempalte contents doesn't sync to tempo #552

Jeff0S opened this issue Jul 8, 2014 · 5 comments

Comments

@Jeff0S
Copy link
Member

Jeff0S commented Jul 8, 2014

From doba...@gmail.com on February 19, 2013 20:30:51

What steps will reproduce the problem? Create any MIDI or Audio clip on a track, and click Auto save template in Resources window. Change BPM. Reload template. Template items will not be time aligned.
The problem must be in the saving portion of the code, cause if i save a template manually in reaper, and load it form the Resources window, it keeps the time syncronisation. What is the expected output? What do you see instead? Loaded items from templates should lock to current tempo/grid/location.

What version of SWS extension are you using? (Extensions -> About SWS...)
2.3.0 #13 What is your Reaper version number and CPU architecture (e.g. Reaper 3.75 x64)? Reaper 4.32 x64 (using the 32 bit version of Reaper) What operating system are you running? (e.g. Windows XP/7, OSX 10.5.8 etc, 64bit?)

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

@Jeff0S
Copy link
Member Author

Jeff0S commented Jul 8, 2014

From doba...@gmail.com on February 19, 2013 11:32:47

What operating system are you running? (e.g. Windows XP/7, OSX 10.5.8 etc,
64bit?)

Win7 x64

@Jeff0S
Copy link
Member Author

Jeff0S commented Jul 8, 2014

From jeffos...@gmail.com on February 20, 2013 13:37:21

thanks for the very clear report!
you right! some info is missing in "auto-saved" template files: items' beat positions.
this might be a bug in the API (?) but it can probably be handled on our end...

Status: Investigating
Owner: jeffos...@gmail.com

@Jeff0S
Copy link
Member Author

Jeff0S commented Jul 8, 2014

From jeffos...@gmail.com on April 11, 2013 11:13:43

fix coming soon ( r1051 )

Status: Fixed

@Jeff0S
Copy link
Member Author

Jeff0S commented Jul 8, 2014

From doba...@gmail.com on April 11, 2013 11:14:48

Thank you!

@Jeff0S
Copy link
Member Author

Jeff0S commented Jul 8, 2014

From jeffos...@gmail.com on April 26, 2013 07:47:29

this was not said in the v2.3.0 #16 whatsnew, but the fix was in there!
(I'll update this whatsnew soon..)

@Jeff0S Jeff0S closed this as completed Jul 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant