simeon
Max Output Level: -81 dBFS
- Total Posts : 494
- Joined: 2003/11/04 14:15:33
- Location: Louisville, KY
- Status: offline
Solved: Changing MIDI timing resolution on existing projects
Is it possible to take a MIDI project that was initially recorded using 960 TPQ and change the timebase to 480 TPQ? I see the option in preferences under Clock but do not know if changing that and resaving the project will apply the change or if there is something else that is needed to change it in the project itself. It seems some keyboards are sensitive to the higher TPQ resolution and just trying to find a work around to see if reducing it makes a difference. Thanks,
post edited by simeon - 2012/10/16 13:19:38
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re:Changing MIDI timing resolution on existing projects
2012/10/16 10:47:05
(permalink)
You can change the MIDI clock resolution at any time, but it won't have any affect on playback or recording, only editing. SONAR actually always runs at 960 PPQ internally; changing the resolution only affects the precision with which events are located when moving them around.
EDIT: In any case, it seems unlikely to me that any synth would be sensitive to this, as the tick values are not actually passed with the data. They are only stored and used by the sequencer (SONAR in this case) to determine when the events are sent in absolute time.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
simeon
Max Output Level: -81 dBFS
- Total Posts : 494
- Joined: 2003/11/04 14:15:33
- Location: Louisville, KY
- Status: offline
Re:Changing MIDI timing resolution on existing projects
2012/10/16 10:58:00
(permalink)
Thanks, I am working with someone who is using a Yamaha MOX6 and when they try loading and playing back the MIDI file from me the keyboard locks up. They have a Roland keyboard and can play the file back just fine. I found a link explaining how to export MIDI files and they give an export resolution of 480 PPQ. Here is the link: MIDI File Export parameters It is referencing Cubase so I am not sure if there was a corresponding setting in SOANR.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re:Changing MIDI timing resolution on existing projects
2012/10/16 12:07:40
(permalink)
OK. I get it. I'm not sure whether the clock setting in SONAR affects export file resolution, but it might; worth a try. You can check by finding/creating an event that starts on an odd tick value (e.g. 483), and seeing if becomes even (482 or 484) after being exported at 480 PPQ and then re-imported and displayed at 960.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
simeon
Max Output Level: -81 dBFS
- Total Posts : 494
- Joined: 2003/11/04 14:15:33
- Location: Louisville, KY
- Status: offline
Re:Changing MIDI timing resolution on existing projects
2012/10/16 12:47:57
(permalink)
It adapts to whatever the Project settings are.
So I set the Project to 480PPQ
Create an event that lands on 479 ticks and saved and closed it.
I bring that file back in and change the PPQ to 960.
Now the resulting time reflects the additional PPQ resolution.
Which it probably should seeing that the Global Project clock setting was increased so it modified the values.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re:Changing MIDI timing resolution on existing projects
2012/10/16 13:03:37
(permalink)
You got that a little backwards. You need to start with the project at 960 PPQ, create an event with an odd tick value, and then switch to 480 PPQ and export. Starting with the project at 480 PPQ, 479 is equivalent to 958 at 960PPQ, and will already have been rounded so you won't be able to see the difference after export.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
simeon
Max Output Level: -81 dBFS
- Total Posts : 494
- Joined: 2003/11/04 14:15:33
- Location: Louisville, KY
- Status: offline
Re:Changing MIDI timing resolution on existing projects
2012/10/16 13:17:08
(permalink)
Got it!
When you open a project that was recorded at a higher PPQ (960 for example) you change the setting in the Project preferences - Clock. This will now be the PPQ resolution applied when the project is saved.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re:Changing MIDI timing resolution on existing projects
2012/10/16 13:23:52
(permalink)
Yes. I just checked it myself, and that is the case. EDIT: Actually., I need to correct that, because I misread your last post. Saving the project after lowering the PPQ resolution will not alter the stored resolution. If you restore it to 960 after re-opening, you will see the higher reoslution values come back. But exporting to MIDI will generate a MIDI file with the lower resolution, and the original resolution will be permanently lost. I would have corrected sooner, but my internet service went down moments after posted. 
post edited by brundlefly - 2012/10/16 14:04:20
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|