QuickScribe Rhythmic Display

Rick Cornish · Post by **Rick Cornish** » Wed Feb 21, 2018 1:38 pm

Hi.......
I read through a couple threads on this topic, but none were more recent than a few years ago, so I'll check in on this:

Is there a way to get QuickScribe to NOT display dotted-8th/16th rhythms as broken triplets? This is really annoying.

I've tried…
• Quantizing the notes on X|1|000 and X|1|360 (i.e. exactly on the downbeat and last 16th) and QS persists in labeling them as triplets.
• Setting the Snap to…" grid in the SE to 16th notes (Snap info is greyed out when the QS window is active)

Does anyone have any good news on this?

stubbsonic · Post by **stubbsonic** » Wed Feb 21, 2018 4:28 pm

It is weird that DP's notation engine sometimes has a mind of its own. I might have a rhythm that is not displaying correctly and I change something unrelated and it fixes it.

You might try nudging the 2nd note (the 16th) a little later until DP decides to show it differently. I never tried that, but it couldn't hurt.

Rick Cornish · Post by **Rick Cornish** » Thu Feb 22, 2018 10:54 am

stubbsonic wrote:You might try nudging the 2nd note (the 16th) a little later until DP decides to show it differently. I never tried that, but it couldn't hurt.

Thanks, Stubbsonic. I may try that, though I actually prefer the feel with the final 16th note slightly ahead.

I hit MOTU with a TechLink as well. We'll see what they have to say.

stubbsonic · Post by **stubbsonic** » Thu Feb 22, 2018 9:23 pm

Whenever I'm preparing tracks for notation, I USUALLY will copy a track and have one version for playback and one version for notation, that way I can have it the way I want to hear it, and another for how I want to see it.

For example, I'd rarely want to hear things quantized, especially note releases. But for notation, it just makes things look as they should.

buzzsmith · Post by **buzzsmith** » Fri Feb 23, 2018 6:04 am

On a related note...

I, too, generally do a lot of mock ups in DP using QuickScribe before transferring the data to Finale.
I heavily quantize, sometimes bar by bar, to make the transcription process easier for Finale.

I have noticed, however, that if I use "Smart Quantize" for attacks and releases sometimes the duration of random (apparently) notes is just one tick. Like 001.

Finale will ignore these notes and not translate them into its file.

I know that I can "Select All" within DP and QS and enter a minimum duration which helps but if I have 8ths, 16ths and some triplets it can be tricky.

If I'm missing something here, I'd be happy to hear of another workaround!

Thanks...

Buzzy

Sent from my iPad using Tapatalk

stubbsonic · Post by **stubbsonic** » Fri Feb 23, 2018 7:24 am

I never use Smart Quantize, and I don't know what advantages it offers, but it sounds like that's a pretty significant downside.

Rick Cornish · Post by **Rick Cornish** » Fri Feb 23, 2018 7:32 am

Thanks for the input, gents. All good stuff.

Just to bring focus to the discussion, I'm NOT asking how to export XML for good display in Finale or to re-jigger QuickScribe display for better printing direct from DP. I have a "Composing" window setup with a large QS window displaying the tracks for tonal instruments where I'd like to see a better musical representation of what I'm writing as I work.

Continuing to forge ahead...

Rick Cornish · Post by **Rick Cornish** » Fri Feb 23, 2018 11:27 am

Discovery: Looks like the note durations have more to do with how QS interprets MIDI data than I realized. If I quantize the durations, the notes display correctly.

buzzsmith · Post by **buzzsmith** » Fri Feb 23, 2018 1:44 pm

Rick Cornish wrote:Discovery: Looks like the note durations have more to do with how QS interprets MIDI data than I realized. If I quantize the durations, the notes display correctly.

I have found, at times, that even quantizing durations is still flaky.

Sometimes, it’s the note proceeding or the note after that messes with the algorithm.

Buzzy

(9.5 if the sig doesn’t display.)

tbrianmann · Post by **tbrianmann** » Tue Mar 13, 2018 1:20 pm

Yes to above. I have to quantize lengths of notes, to get a clean display. In polyphony, all the previous notes need to be quantized as well, an note hanging over from previous beat, will generate a separate voice type notation.

tbrianmann · Post by **tbrianmann** » Tue Mar 13, 2018 1:21 pm

On the subject of Rhythmic display, does anyone know how to display rhythm slashes in QS?

stubbsonic · Post by **stubbsonic** » Tue Mar 13, 2018 1:36 pm

You can't. When I've needed to display rhythms, I just use center line (B in treble clef). Otherwise, you need to export MIDI to a notation program.

I saw that Muse Score (free) allows you to import rhythms that are on that center line, and swap out the noteheads for rhythm slashes.

Rick Cornish · Post by **Rick Cornish** » Tue Mar 13, 2018 5:48 pm

An update for those following this topic:

I posted a MOTU TechLink and Magic Dave responded. After looking at my file, he concluded that DP’s transcription engine is preventing QuickScribe from correctly displaying dotted eighth/sixteenth rhythms and he was forwarding this info to the developers.

frankf · Post by **frankf** » Wed Mar 14, 2018 1:43 pm

tbrianmann wrote:On the subject of Rhythmic display, does anyone know how to display rhythm slashes in QS?

No go in QS, but with smaller ensembles and orchestrations, I print without articulation, dynamics, slashes and hand write them in. So much faster. Larger scores with many parts, it's port to a dedicated notation app.

Sent from my iPad using Tapatalk Pro

greg328 · Post by **greg328** » Sat Mar 24, 2018 5:45 am

My technique for more accurate Quickscribe rhythms is to manually quantize (100% strength) not only the problem measure, but the measures around it. This seems to correct any misinterpreted triplets into 8ths/16ths.
This without having to alter note length.

Greg

Sent from my iPod touch using Tapatalk

MOTUnation.com