I'd like to know what is the actual resolution per quarter note when recording in Notion... maybe an admin?
I ask this because I'm under the impression that when recording in realtime, especially at low speed, the result is rather rhythmically deformed. This affects rapid passages most, as is to be expected.
- It is currently Fri Jun 20, 2025 6:02 pm • All times are UTC - 5 hours [ DST ]
Attention:
Welcome to the old forum. While it is no longer updated, there is a wealth of information here that you may search and learn from.
To partake in the current forum discussion, please visit https://forums.presonus.com
Notion's resolution
5 posts
• Page 1 of 1
Re: Notion's resolution
robsogge wrote:I'd like to know what is the actual resolution per quarter note when recording in Notion... maybe an admin?
I ask this because I'm under the impression that when recording in realtime, especially at low speed, the result is rather rhythmically deformed. This affects rapid passages most, as is to be expected.
Are you referring to the way the MIDI input is quantized? If so the quantization is relative to the tempo you're recording at....the click should represent the quarter note.
-
Admin - Site Admin
- Posts: 1006
- Joined: Mon May 11, 2009 7:12 pm
Re: Notion's resolution
I mean ticks per quarter note... or, as wikipedia puts it:
PPQ (Pulses Per Quarter note) is the smallest unit of time used for sequencing note and automation events in the MIDI standard. Most MIDI sequencers allow the number of PPQ to be varied for more or less temporal resolution depending on the needs of the performer.
If there are too few PPQ any performance recorded into the MIDI sequencer may sound artificial (being quantised by the Pulse rate) or lose subtle variations in timing that gives music a 'human' feeling. Generally 96 PPQ is sufficient to capture enough temporal variation. Although some musicians like to work with PPQs around 960 or more.
PPQ (Pulses Per Quarter note) is the smallest unit of time used for sequencing note and automation events in the MIDI standard. Most MIDI sequencers allow the number of PPQ to be varied for more or less temporal resolution depending on the needs of the performer.
If there are too few PPQ any performance recorded into the MIDI sequencer may sound artificial (being quantised by the Pulse rate) or lose subtle variations in timing that gives music a 'human' feeling. Generally 96 PPQ is sufficient to capture enough temporal variation. Although some musicians like to work with PPQs around 960 or more.
- robsogge
- Posts: 76
- Joined: Tue Aug 16, 2011 6:08 pm
Re: Notion's resolution
robsogge wrote:I mean ticks per quarter note... or, as wikipedia puts it:
PPQ (Pulses Per Quarter note) is the smallest unit of time used for sequencing note and automation events in the MIDI standard. Most MIDI sequencers allow the number of PPQ to be varied for more or less temporal resolution depending on the needs of the performer.
If there are too few PPQ any performance recorded into the MIDI sequencer may sound artificial (being quantised by the Pulse rate) or lose subtle variations in timing that gives music a 'human' feeling. Generally 96 PPQ is sufficient to capture enough temporal variation. Although some musicians like to work with PPQs around 960 or more.
This actually might fall into the category of "can not disclose" due to level of development and our sample playback engine. I'll check with the developers and see if I can get an answer for you....
-Kyle
-
Admin - Site Admin
- Posts: 1006
- Joined: Mon May 11, 2009 7:12 pm
Re: Notion's resolution
Thank you, Kyle!
It just seemed a legit question to me, but the mysterious paths of development... it does have an importance though, because it defines the level of accuracy of a realtime recording...
EDIT- then again, realtime recording might not have been a primary consideration when the program was developed...but I believe it could make an already excellent application a better one. I also wish there was a way to disable the interpreter when recording in realtime, as it can really give unpredictable results.
It just seemed a legit question to me, but the mysterious paths of development... it does have an importance though, because it defines the level of accuracy of a realtime recording...
EDIT- then again, realtime recording might not have been a primary consideration when the program was developed...but I believe it could make an already excellent application a better one. I also wish there was a way to disable the interpreter when recording in realtime, as it can really give unpredictable results.
- robsogge
- Posts: 76
- Joined: Tue Aug 16, 2011 6:08 pm
5 posts
• Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 32 guests