Ken J
Max Output Level: -87 dBFS
- Total Posts : 163
- Joined: 2005/07/31 16:51:07
- Status: offline
Input Quantization
I have X2 Essentials and am going through my e-version of Sonar X2 Power, trying each and everything as I come to it. I am up to the section on input quantizing which could be of use to me. However, I don't get the same result as in the book. I have set the Inspector Input Quantize resolution to a quarter note value and clicked on the input quantize button to turn it blue, then, with the metronome running simply plunked out a C scale, then hit Alt6. The resulting "music" shows 6 normal quarter notes but both quarter notes on beat 4 are tied across the bar line to a sixteenth note in the next bar. I can select the scale and run the normal quantize and everything then shows as quarter notes. Any idea on what I am doing wrong?
|
garrigus
Max Output Level: 0 dBFS
- Total Posts : 8599
- Joined: 2003/11/05 17:23:21
- Location: www.garrigus.com
- Status: offline
Re: Input Quantization
2013/07/29 19:51:20
(permalink)
|
Ken J
Max Output Level: -87 dBFS
- Total Posts : 163
- Joined: 2005/07/31 16:51:07
- Status: offline
Re: Input Quantization
2013/07/29 20:06:46
(permalink)
I've tried the same simple experiment with increasingly shorter resolution settings and I get more quarter notes as I set the resolution lower. But it looks like it won't be of much use to me. I use quantization of finished clips extensively and thought this might be a time saver. And, FYI, this is the 3rd or 4th Sonar Power book I have bought. I learn so much from them.
|
garrigus
Max Output Level: 0 dBFS
- Total Posts : 8599
- Joined: 2003/11/05 17:23:21
- Location: www.garrigus.com
- Status: offline
Re: Input Quantization
2013/07/29 20:14:02
(permalink)
|
Ken J
Max Output Level: -87 dBFS
- Total Posts : 163
- Joined: 2005/07/31 16:51:07
- Status: offline
Re: Input Quantization
2013/07/29 20:16:49
(permalink)
About Sonar says "SONAR X2 Essential (X2 build 306) - x64"
|
MarioD
Max Output Level: -72 dBFS
- Total Posts : 901
- Joined: 2006/04/15 15:59:50
- Status: offline
Re: Input Quantization
2013/07/29 20:51:15
(permalink)
Hi Ken, I just tried your C scale experiment here with Sonar X2a Pro and all worked fine. The only difference is that I hit enter when I finished recording. I don’t know if that makes a difference or not but you may want to try it.
The reason people say the vinyl sounds better is because the music was better. Sonar Platinum, Intel i7 –2600 CPU @ 3.2 GHz, 16 GB ram, 2x2TB internal drives and 1 1TB internal drive, Radeon HD 5570 video card, HP 25" monitor, Roland Octa Capture, MOTU Midi Express 128, Win 10 Pro www.soundcloud.com/Mario_Guitar
|
garrigus
Max Output Level: 0 dBFS
- Total Posts : 8599
- Joined: 2003/11/05 17:23:21
- Location: www.garrigus.com
- Status: offline
Re: Input Quantization
2013/07/29 20:53:05
(permalink)
|
Ken J
Max Output Level: -87 dBFS
- Total Posts : 163
- Joined: 2005/07/31 16:51:07
- Status: offline
Re: Input Quantization
2013/07/29 20:56:19
(permalink)
Mario, I tried that without success. I am currently downloading EssentialX2aPatch.exe. We'll see if that works.
|
Ken J
Max Output Level: -87 dBFS
- Total Posts : 163
- Joined: 2005/07/31 16:51:07
- Status: offline
Re: Input Quantization
2013/07/29 23:10:22
(permalink)
I now have the update to Sonar X2a but the problem persists. Maybe Essentials just didn't think input quantization was an essential feature so they left it out.
|
icontakt
Max Output Level: -32.5 dBFS
- Total Posts : 4266
- Joined: 2012/03/04 08:18:02
- Location: Tokyo
- Status: offline
Re: Input Quantization
2013/07/30 01:48:42
(permalink)
Are you sure you are recording on the right track? Input Quantize is a per-track setting so you might have enabled it on a different track. The feature works absolutely fine in my X2a Essential.
Tak T. Primary Laptop: Core i7-4710MQ CPU, 16GB RAM, 7200RPM HDD, Windows 7 Home Premium OS (Japanese) x64 SP1Secondary Laptop: Core2 Duo CPU, 8GB RAM, 7200RPM HDD, Windows 7 Professional OS (Japanese) x64 SP1Audio Interface: iD14 (ASIO)Keyboard Controller/MIDI Interface: A-800PRODAW: SONAR Platinum x64 (latest update installed)
|
Ken J
Max Output Level: -87 dBFS
- Total Posts : 163
- Joined: 2005/07/31 16:51:07
- Status: offline
Re: Input Quantization
2013/07/30 12:42:02
(permalink)
To reduce things to their simplest, I started a new project with just 1 midi track and did the "1 C scale" experiment. Same result as previously. I tried to paste a screen dump so you could see what I see but haven't done one before and can't figure out how to do it.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Input Quantization
2013/07/30 15:03:27
(permalink)
I suspect the issue is that Input Quantizing does not quantize durations - only start times. Duration quantizing, which you probably have enabled by default in your quantize dialog, is often needed to get notation to display as expected, though the Fill/Trim Durations options in the Staff View may help in some cases. The latter is preferable in terms of audible results, since duration quantizing can really take the life out of a live performance - much more so than quantizing start times. I usually make muted copies of tracks to quantize for notation display and printing purposes without affecting the sound of the live tracks.
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
|
Ken J
Max Output Level: -87 dBFS
- Total Posts : 163
- Joined: 2005/07/31 16:51:07
- Status: offline
Re: Input Quantization
2013/07/30 16:15:21
(permalink)
This has been an interesting learning experience. When I did this simple experiment and couldn't get the input quantization to function the way the Garrigus book said it should, I wondered what the actual note start times and durations were. So I right clicked on the notes in the staff view and, instead of what I had been used to seeing in the "Time" box (measures/beats/ticks), the entries were the time values. I searched around trying to figure out what I had done to change the time readings (without success) so I posted a new note to this forum. Scott Garrigus came to the rescue and explained to go to preferences/display and uncheck the box marked "Display all times as SMPTE" which I did. I then tried doing the simple scale thing again with the input quantization on and (TRUMPET FANFARE) it worked as advertised. (Scott: did you realize that's how things work? Put it in the next edition.  )
|
garrigus
Max Output Level: 0 dBFS
- Total Posts : 8599
- Joined: 2003/11/05 17:23:21
- Location: www.garrigus.com
- Status: offline
Re: Input Quantization
2013/07/30 16:58:59
(permalink)
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Input Quantization
2013/07/30 18:55:11
(permalink)
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
|