Reason Document - Song Position

Have an urge to learn, or a calling to teach? Want to share some useful Youtube videos? Do it here!
avasopht
Competition Winner
Posts: 3932
Joined: 16 Jan 2015

20 Jun 2015

I'm down for that (time permitting).

distrakt
Posts: 12
Joined: 11 Jun 2016

14 Jan 2022

Hello from the future of 2022!
I was delighted that when I googled for "34953.3.1.127" that this conversation is what came up, for the only hit. Because I left Reason running overnight, and that's where the transport stopped in the morning.

Yes, Reason uses 15360 PPQ parts per quarter note. (You learn this developing rack extensions.)

(34953 * 4 + 3 + 1/16 + (127/240)/16) * 15360 = 2147559868

That's just a smidge past 2^31=0x7FFFFFFFF=2147483648. Why it should stop there instead of some other nearby 2^31 I dont know. I was running at an odd tempo (213.123bpm) but got same result.

Anyway. Yay google.

User avatar
ScuzzyEye
Moderator
Posts: 1402
Joined: 15 Jan 2015
Contact:

14 Jan 2022

distrakt wrote:
14 Jan 2022
Hello from the future of 2022!
Ha! This was a great thread. I miss Raveshaper's wild MIDI experiments.

If I had know what 2022 would be like, I would have valued each subtick along the way a bit more. :)

djsmex
Posts: 248
Joined: 23 Aug 2016

30 Mar 2022

Just found this thread and I've been working through a similar line of thought. What I found interesting is the remote item for song time (H:M:S.ms) has the exact same range as the bars/beats/ticks item, that is talked about here.
The other thing I notist was changing the tempo seems to affect both values in how they relate to bars/beats/ticks and H:M:S.ms. I suspect the range value is arbitary in that the max song length may relate to tempo or the remote range is limited and may not go up to the max song length.
This seems a little like the ssl track limit of 64 with a max start from track of 128 via remote. However, it is possible to have 256 or more tracks. Again I haven't tested this extensively and assume the track limit may relate to the system running reason.
I'm using web tech: WebMidi.js, jQuery, speech API, bootstrap with loopmidi, Remote LUA codecs and have a speaking ReDrum controller here:
https://www.nostex.co.uk/ReDrum/
One thing I had to work round was the 8bit value being sent in 7bit sysex message data, so needed to convert in the LUA codec. I think I managed this and had the output set as text sysex value and just converted to decimal in js.
Although my aim is a little different as I am looking to improve accessibility for blind reason users, cue points or song markers is one feature I was looking to do as well.
If you'd like to share each others work or collabrate on a project, please feel free to get in touch.
You can view source of the above web page, to see the js code I've used, download the lua codec etc.
best, john

djsmex
Posts: 248
Joined: 23 Aug 2016

02 Apr 2022

Check out my short video of my web app and song markers / cue points

Post Reply
  • Information
  • Who is online

    Users browsing this forum: No registered users and 9 guests