sharke
Max Output Level: 0 dBFS
- Total Posts : 13933
- Joined: 2012/08/03 00:13:00
- Location: NYC
- Status: offline
Reaper's M:B:T resolution of sample values different to Sonar's?
I have both DAW's set side by side with 16th note snapping enabled in each. My cursor is 1/16th note before measure 353.
In both Sonar and Reaper, this position is given as 33786000 samples.
But if I switch the units to M:B:T, Sonar shows 352:04:720 while Reaper shows 352:04:75
I know it's a very small difference, but what is the reason for it? I see that Sonar shows the "T" part to 3 digits while Reaper only has 2 (is there a way to change this in Reaper?) but even so, there is no reason why Reaper couldn't show 352:04:72 to match Sonar here. Or is Sonar wrong?
JamesWindows 10, Sonar SPlat (64-bit), Intel i7-4930K, 32GB RAM, RME Babyface, AKAI MPK Mini, Roland A-800 Pro, Focusrite VRM Box, Komplete 10 Ultimate, 2012 American Telecaster!
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
.
post edited by mister happy - 2018/02/22 11:04:27
|
BobF
Max Output Level: 0 dBFS
- Total Posts : 8124
- Joined: 2003/11/05 18:43:11
- Location: Missouri - USA
- Status: offline
Re: Reaper's M:B:T resolution of sample values different to Sonar's?
2018/02/20 19:56:04
(permalink)
It looks like the ticks portion of play cursor position display is 1000ths in Reaper, giving you 0, 250, 500 and 750 for the beginning of each 16th note. My ppq is set to 960 and changing 480 doesn't change the play cursor position display. I can't find a setting anywhere that changes this for the transport play cursor position. There is however, an option for the MIDI editor ruler:  I'm guessing your SONAR project is set to 960 ppq and that SONAR's positon ticks are based on ppq. This will give 0, 240, 480 and 720 for the start of each 16th note. I wouldn't say either is right or wrong. To me, the song position ticks matching MIDI ppq is meaningless in mixed audio/midi projects. But 1000 ticks per 1/4 doesn't make sense for midi either.
Bob -- Angels are crying because truth has died ...Illegitimi non carborundum --Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64 Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s Waves Gold/IKM Max/Nomad Factory IS3/K11U
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
.
post edited by mister happy - 2018/02/22 11:05:19
|
BobF
Max Output Level: 0 dBFS
- Total Posts : 8124
- Joined: 2003/11/05 18:43:11
- Location: Missouri - USA
- Status: offline
Re: Reaper's M:B:T resolution of sample values different to Sonar's?
2018/02/20 21:32:31
(permalink)
mister happy
^ You see where you can choose to view?:
Measures.beats
Measures.beats.100ths
Measures.beats.Ticks
100/100ths = 1 beat.
75/100ths = 0.75 of a beat
You can select the number of Ticks per beat in Preferences. The default is 960.
720/960 = 0.75 of a beat ^
Yes, I see. I posted it  Note that this option is specific to the MIDI editor ruler, NOT the Transport Play Cursor Position
Bob -- Angels are crying because truth has died ...Illegitimi non carborundum --Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64 Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s Waves Gold/IKM Max/Nomad Factory IS3/K11U
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
.
post edited by mister happy - 2018/02/22 12:47:13
|
BobF
Max Output Level: 0 dBFS
- Total Posts : 8124
- Joined: 2003/11/05 18:43:11
- Location: Missouri - USA
- Status: offline
Re: Reaper's M:B:T resolution of sample values different to Sonar's?
2018/02/20 22:30:44
(permalink)
I think we're saying the same thing
Bob -- Angels are crying because truth has died ...Illegitimi non carborundum --Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64 Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s Waves Gold/IKM Max/Nomad Factory IS3/K11U
|
Jeff Evans
Max Output Level: -24 dBFS
- Total Posts : 5139
- Joined: 2009/04/13 18:20:16
- Location: Ballarat, Australia
- Status: offline
Re: Reaper's M:B:T resolution of sample values different to Sonar's?
2018/02/20 23:11:06
(permalink)
It does not really matter that much. For example Studio One's internal midi resolution is way higher than both of these programs mentioned here.
There are only two things you need to be concerned about:
1 That the program you are using will quantise material perfectly if its needed.
2 That the program, when quantising is switched off in fact records very faithfully the timing you put in at the time. Either against the click or not and that includes all subtle human timing. (Studio One excels at this BTW) I am also referring to a very good player here, not an average player.
If your program can do both of those things you are basically set.
Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4 - iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface Poor minds talk about people, average minds talk about events, great minds talk about ideas -Eleanor Roosevelt
|
BobF
Max Output Level: 0 dBFS
- Total Posts : 8124
- Joined: 2003/11/05 18:43:11
- Location: Missouri - USA
- Status: offline
Re: Reaper's M:B:T resolution of sample values different to Sonar's?
2018/02/21 00:26:50
(permalink)
It matters if you want to understand the difference(s) between tools you're using
Bob -- Angels are crying because truth has died ...Illegitimi non carborundum --Studio One Pro / i7-6700@3.80GHZ, 32GB Win 10 Pro x64 Roland FA06, LX61+, Fishman Tripleplay, FaderPort, US-16x08 + ARC2.5/Event PS8s Waves Gold/IKM Max/Nomad Factory IS3/K11U
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
.
post edited by mister happy - 2018/02/22 12:48:04
|
sharke
Max Output Level: 0 dBFS
- Total Posts : 13933
- Joined: 2012/08/03 00:13:00
- Location: NYC
- Status: offline
Re: Reaper's M:B:T resolution of sample values different to Sonar's?
2018/02/21 04:20:02
(permalink)
I have the ticks/quarter note set to 960 in both programs.
JamesWindows 10, Sonar SPlat (64-bit), Intel i7-4930K, 32GB RAM, RME Babyface, AKAI MPK Mini, Roland A-800 Pro, Focusrite VRM Box, Komplete 10 Ultimate, 2012 American Telecaster!
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
.
post edited by mister happy - 2018/02/22 12:48:39
|
azslow3
Max Output Level: -42.5 dBFS
- Total Posts : 3297
- Joined: 2012/06/22 19:27:51
- Location: Germany
- Status: offline
Re: Reaper's M:B:T resolution of sample values different to Sonar's?
2018/02/21 10:24:40
(permalink)
Jeff Evans
It does not really matter that much. For example Studio One's internal midi resolution is way higher than both of these programs mentioned here.
Is Studio One internal MIDI resolution specified in MHz?
2 That the program, when quantising is switched off in fact records very faithfully the timing you put in at the time. Either against the click or not and that includes all subtle human timing. (Studio One excels at this BTW) I am also referring to a very good player here, not an average player.
I guess platinum MIDI cable for $500 is required to catch that subtle human timing. All other MIDI cables are physically unable transmit information with 960 ppq precision  For the topic. I think Reaper shows beats as a "float" number, not the number of ticks. Since it is possible to have different tpq items inside one project, I do not see other logical solution. Sonar always use fixed point ticks at 960 tpq (so the resolution is, 1/65536 of one tick at 960 tpq) for MIDI timing. Reaper does not support "subticks". But support much higher tpq then 960 and so can achieve the same precision.
Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc. www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
|
Jeff Evans
Max Output Level: -24 dBFS
- Total Posts : 5139
- Joined: 2009/04/13 18:20:16
- Location: Ballarat, Australia
- Status: offline
Re: Reaper's M:B:T resolution of sample values different to Sonar's?
2018/02/21 11:14:03
(permalink)
This might help: http://answers.presonus.com/6747/shortest-midi-quantization-in-studio-one This is about external synths too BTW. Sonar's midi timing becomes poor when the audio side of the program is under heavy load. You may not hear this with one synth playing (and the the audio load is not maxed out) but when there are many synths playing and the parts are fast and complex (and the audio is under heavy load) it certainly becomes noticeable. It seems Sonar's midi timing is somehow related to the audio side of the program. I am not certain as to the reasons why but I have heard it. As a drummer one is super sensitive to timing issues. Other Sonar users have agreed with me on this as well. Not so in Studio One. My midi interface is running on USB but on its own PCI USB card so there is nothing else going on. Midi timing is relentless and super tight even under heavy audio load. With many synths playing out over multiple midi ports. Sonar is way behind in this regard. Most wont hear this because you need quite a few hardware synths in order to experience it and many don't own enough to put this under test. Quite a few have shifted over to Studio One because of its midi timing. It was one of the main reasons I actually switched. The gapless engine also allows you to jump midi tracks on the fly while in record (and looping) and add new midi data into the track you land on. Sonar cannot cope with this at all. It simply falls over. For me this is quite a revelation. Being able to add new material to existing parts. There are many areas where Studio One excels midi wise. Haven't tested Reaper though. It would have to match this at least in both of these areas.
Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4 - iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface Poor minds talk about people, average minds talk about events, great minds talk about ideas -Eleanor Roosevelt
|
azslow3
Max Output Level: -42.5 dBFS
- Total Posts : 3297
- Joined: 2012/06/22 19:27:51
- Location: Germany
- Status: offline
Re: Reaper's M:B:T resolution of sample values different to Sonar's?
2018/02/21 13:08:48
(permalink)
Jeff Evans
Haven't tested Reaper though. It would have to match this at least in both of these areas.
The problem is... this thread is a question about Reaper 
Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc. www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
|