Vienna Symphonic Library Forum
Forum Statistics

194,096 users have contributed to 42,911 threads and 257,915 posts.

In the past 24 hours, we have 6 new thread(s), 21 new post(s) and 80 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Interesting DP Problem

  • Interesting DP Problem

    D
    D
    I have never seen this happen so I'm guessing it's a VI issue but don't really know: when I select some midi tracks (5 string tracks in this case) and click to open the quickscribe window to compare the midi parts with the score on paper, DP quits.

    Has anyone else experienced this?

    Thanks
  • M
    M
    hi dave - what dp version? i can't test on the vi's specifically but if it's dp5, i can try to duplicate this with other items. just started working with it today and all the gigastudio tracks were ok. actually never opened quickscribe come to think of it. i'll do it tomorrow and report back...
  • D
    D
    Hi Martin,

    Still running 4.6.1 but may make the switch soon after more reports on stability and features. I suspect the VI's because I don't remember it ever happening in any version of Performer. In fact I just used Quickscibe very consistently as I had to deliver a midi file to a copyist for a live orchestra date. There were no VI's running however. It could be a memory issue as I've got only 100 megs of ram left out of 4.5 gigs and the notation display may just be too much. In fact maybe I just answered my own question. Be nice to hear from others.

    Let me know if DP5 is a major improvement in your opinion.
  • M
    M
    definantly no problems with quickscribe in 4.6. i actually use it as my main notation program unless parts need to be extracted or something needs to go to a publisher. it could be hitting the memory limits as you say, but i have no way to check on the vi's for you.

    just started playing with dp5 yesterday and for me, the track folders were enough to justify the upgrade. i like to work with templates so being able to collapse sections really helps with screen real estate. really didn't get a chance to play with much else yet but the whole thing appears to be another step forward in making it all work well. oh yeah, the new instruments aren't much, especially if you have others so perhaps other motivations might be a better guide if you're thinking in that direction.
  • D
    D
    I opened 1 track in quickscibe with no problem but the program quit at 5 so maybe I'm just that close with ram. I'll have to run tests and see. I'm sure it's fine with just midi tracks and no VI's but we'll see.

    Track folders is exactly what I have wanted the most in DP. What's ironic is that I'm thinking I won't have anywhere near the tracks now with VI's and all the articulations basically on one track. Couldn't say but I think I'm done with 30 to 60 strings tracks now (not to mention other groups.) There's no easy way in any case.
  • M
    M
    last edited
    last edited

    @dpcon said:

    I have never seen this happen so I'm guessing it's a VI issue but don't really know: when I select some midi tracks (5 string tracks in this case) and click to open the quickscribe window to compare the midi parts with the score on paper, DP quits.

    Has anyone else experienced this?

    Thanks


    I recorded 5 tracks with chamber strings and selected all tracks later, clicked to open quickscribe and it worked fine.

    Maya
  • J
    J
    last edited
    last edited

    @dpcon said:

    I have never seen this happen so I'm guessing it's a VI issue but don't really know: when I select some midi tracks (5 string tracks in this case) and click to open the quickscribe window to compare the midi parts with the score on paper, DP quits.

    Has anyone else experienced this?

    Thanks


    Actually, I've had this problem a lot in the past-- less so of late. I'm not *entirely* sure what solves it, but for a while it had something to do with Consolidated Wndows and opening various edit windows. Depending upon how much RAM you have loaded, the process of generating the graphics may just spike the RAM usage for long enough to cause the crash.

    One thing you may want to do (if you haven't already) is to disable Widgets and iSight. Also, disable Consol. Windows if you have less than 3 GB RAM. I've ordered an additional 4GB (for 8GB total) RAM, which I understand helps a variety of issues. I did notice that the DP quit problem didn't happen so much when I went from 2.5 GB to 4.5 GB. I'm hoping that going full wack will eliminate the issue altogether.

    Curious-- are you using DP5? I'm eager to hear about how Vi works with this... I'm holding on to DP 4.6x for a while longer...
  • D
    D
    Still using DP 4.6.1. Now that V.I. 1.05 is out with memory sharing I will duplicate the problem (choose multiple tracks in quickscribe) and see if DP crashes. The only duplicate instances are Violins for 1st and 2nd's. It appears it's giving me another 100 megs of ram. I have 4.5 gigs now but need to get at least 2 more gigs. I'm convinced that will help because I'm just too close using all but 200 megs.
  • J
    J
    Someone suggested thinning out the fonts menu-- disabling or removing those fonts which are hardly or never used, such as dingbats, foreign language fonts, etc. This may speed up the process of QuickScribe finding fonts and redrawing the screens in time.

    Another consideration is to get a faster display card. I have a G5 2.5 dual which came with a NVIDIA GeForce FX 5200 Ultra AGP card. I'm considering replacing it with at least a Radeon 9800 Pro or the Radeon X800 XT Pro. Someone suggested that my FX 5200 was choking, especially when recording with the QuickScribe window open at the same time. From time to time I do get error messages when running the hardware diagnostics from the OSX install disc, but these errors are intermittent. Very confusing at times, so I've been slow to throw money at the symptoms before fully understanding the real problem. That X800 is going for about $400+; good cash which could be used towards more Extended Edition licenses. It all adds up so quickly.

    If you use your computer for different purposes, a lot of the DAW customization can be more easily managed by making different setups under different user names. This way, you can work with video and graphics editing with one user name setup loaded with all the fonts and features required for that process, then you can use the other setup for DAW-only projects.

    I've not tried this just yet because 1) I'm about 2500 miles away from home at the moment, 2) I may only be on the verge of needing dual user config, and 3) I haven't wanted to reconfigure everything in the middle of a ton of current projects. However, I'm even more convinced that adding more RAM will solve about 75% of what ails my DAW setup. I'm getting the RAM next week, but will probably spend a good part of July totally rethinking my setup before installing the second half of the VI Cube.