Slow quick scribe redraw in dp 7.12

[musicman11159]

I am having a great deal of trouble wi extremely slow step record entry in quick scribe. 

When the full score is open I may wait up to 15 ( or more!) seconds for notes to appear although I hear them immediately. If I change note values with the keypad before they show up on the screen the values change and I have to start over again. If I limit the number of staves I am seeing I have no problems.


The current project has 
-buffer set at 512 - If I set the buffer lower the audio cracks and cuts out on playback
-60 MIDI tracks, 8 aux and 8 audio tracks
- UltraLite-mk3 Hybrid intrerface
- Accessing virtual instruments through bidule with 8 bidules accessing 
  16 instances of Play and Kontakt 
- It is a full orchestra score.
- The keyboard is a CME80 and is connected to the ultralight through the MIDI input
- The ultralight is connected to the mac pro via USB  

[MIDI Life Crisis]

You don't say what machine you are using, but regardless, 60 tracks of an orchestral score is NOT what Quickscribe was designed to handle.

You need a notation program to see and work with a score that size. DP is simply not designed to do that. It's called Quickscribe for a reason. Quick and dirty, relatively simple notation.

That is normal operation for the program.

[musicman11159]

Mac system
Mac pro
Quad core 2.66GHz
10G ram

I know others with similar set ups that are not having the same issue but we cannot seem to get to the solution.

I send the final product to Sibelius for notation.

[MIDI Life Crisis]

All I can offer is to look at the file for you if you are comfortable sending. It's good to know you'll be using a pro notation program on that large a score...

PM me if you want to send me the file.

[bradswan]

Slow scroll, zoom, edge edit, slower in general with 7.12.

[MIDI Life Crisis]

Got the score from the o/p and opened it in DP 7.12 on my lowly G5 Dual 2.0; OS X.5.8; 4 GB RAM.

Opened very fast. I got a "processing window" for Quickscribe at first for about 6 seconds and then the score opened in QS very quickly to the horn section. I selected all tracks on the left and they opened in about 2 seconds or less - nearly immediately. Hit play. Scrolled fine. Paged down while playing back and a little hiccup but redraws were pretty fast overall. Jumped to measure 20 in the control panel and locating to the measure in QS was too fast for me to even see.

I see the o/p is using Plogue Bidule as I do. The only thing I can think of is I was not running any VIs, but given his machine, I wouldn't expect that to be an issue. I am on a PPC so there may be an Intel thing going on, but as far as drawing the score, it was about as fast to draw as I expect in Finale (I'm on version 2011).

I'm using the digital monitor outs to a 19" Viewsonic LCD. My video card is an ATI Radeon 9600 @ a resolution of 1280 x 1024 @ 60 Hz and color depth of 32 bit.

I did not output to and VI or MIDI module.

[musicman11159]

I agree with your assessment, however, I am having trouble with step record. The notes show up quite a bit later than the audio when i step record through my MIDI keyboard when all staves are selected in quickscribe.

Were you able to try that?

[MIDI Life Crisis]

Actually, no. I have never used step record and have already deleted your file. There would be a bit of a learning curve for me using that method of entry and I'd probably end up beating up my Mac if I even tried

Anyone else use step record willing to give it a shot? Fernando?

[Frodo]

Mac system
Mac pro
Quad core 2.66GHz
10G ram

Currently, anything above 4GB or so would be of little (or no) consequence unless there were standalone VIs running outside of that 4GB. I must say that 10GB RAM should offer plenty of headroom for functions such as those going in OSX, leaving a full 4GB of memory available for DP to do its 4GB thing.

It could be Virtual Memory writing data that links MIDI notes with sample data which causes the delay. It could also be that some Virtual Instruments are not 100% compliant with OSX version above Tiger. Not everything I have which works in Tiger works as well in Snow Leopard, and I suspect that it's due to the Cocoa vs Carbon graphics standards.

All that said, I must agree with MLC that QuickScribe may not be the best choice for notation or for users in expectation of a high-end solution for notation.

I score large orchestral scores in DP and port SMFs into Finale all the time. I'll use QS on a limited basis and only a select number of tracks at a time, especially when there are lots of VIs running. My templates tend to be 30-ish tracks, so having the VIs run well is what takes priority.

When using QS, it may help to use it in a window of its own and to close other windows which likely compete with CPU resource priorities.

[Timeline]

A work around may be to downgrade OS 10 to 10.5.8.

I find waveform redraws are better speed wise but don't know why. I have two HD's, one with 10.5.8 and one with 10.6.4 and I still have to go back to 10.5.8 to make things smooth on this point. DOn't see why Quickscribe should be any different.

[MIDI Life Crisis]

That's would explain why I got better performance.

[FMiguelez]

Anyone else use step record willing to give it a shot? Fernando?

I'd gladly give it a shot, but I don't use step-record either
I don't think I've ever used it...

But I've never experienced a sluggish QS, even with many tracks.
Maybe the fact that most of my VIs are on the slave computers has helped my computer behave properly. Otherwise I'm certian it would be slooooooow.

[MIDI Life Crisis]

... never mind ...

[James Steele]

"What's all this about saving Soviet jewelry?"

That was such a great bit. It's a shame that except for a few occasional bright talents that have passed through and moved on, SNL has pretty much never come close to being as funny as it was in those earlier years.