Jump to content

JoeGBradford

Members
  • Posts

    1,394
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by JoeGBradford

  1. My Zampler VST and presets are on an external SSD attached over USB 3. Union with which I have the same problem is a VST3 and so on my system drive in the default VST3 location - though I need to check where the presets for that are located when I am on the PC again tonight or tomorrow in case that is the issue if the samples are stored within the preset

    I have just been scrolling through presets on Voltage Modular and no problems with that - though I understand that is probably emulation based rather than sample based

  2. 15 hours ago, scook said:

    Have you tried lowering the buffer size? Sometimes extreme settings high or low can be a problem.

     

    I tried this today but the same thing occurred - played a few different patches then stuttering started. As before if I changed focus away from CbB to Chrome and then went back to CbB and played the same patch again the stuttering didn't happen. Also if I turned the audio engine off and back on again, then play my controller keyboard, the stuttering stops - which will work as a temporary fix but a bit of a pain

    Another strange thing is that although the current Engine Load shown in the performance module stays within sensible figures changing patches causes the max Engine Load to rise up to over 1,000 percent - even when the patch changed to still plays fine

  3. Thanks - I ran Latency Mon whilst playing different patches with Zampler and this was the result - apart from first couple of sections I am afraid I do not know what any of it means so would appreciate advice. I seem to remember when I tried task manager I couldn't look at it whilst in CbB but will try it again

     

    CONCLUSION
    _________________________________________________________________________________________________________
    Your system appears to be suitable for handling real-time audio and other tasks without dropouts. 
    LatencyMon has been analyzing your system for  0:03:28  (h:mm:ss) on all processors.


    _________________________________________________________________________________________________________
    SYSTEM INFORMATION
    _________________________________________________________________________________________________________
    Computer name:                                        JOE-PC
    OS version:                                           Windows 10 , 10.0, build: 18363 (x64)
    Hardware:                                             ASUSTeK Computer INC., P8Z68-V LE
    CPU:                                                  GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
    Logical processors:                                   4
    Processor groups:                                     1
    RAM:                                                  8172 MB total


    _________________________________________________________________________________________________________
    CPU SPEED
    _________________________________________________________________________________________________________
    Reported CPU speed:                                   3311 MHz

    Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

    WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature. 

    _________________________________________________________________________________________________________
    MEASURED INTERRUPT TO USER PROCESS LATENCIES
    _________________________________________________________________________________________________________
    The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

    Highest measured interrupt to process latency (µs):   319.60
    Average measured interrupt to process latency (µs):   5.353070

    Highest measured interrupt to DPC latency (µs):       313.30
    Average measured interrupt to DPC latency (µs):       1.594756


    _________________________________________________________________________________________________________
     REPORTED ISRs
    _________________________________________________________________________________________________________
    Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

    Highest ISR routine execution time (µs):              155.443371
    Driver with highest ISR routine execution time:       dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

    Highest reported total ISR routine time (%):          0.093462
    Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

    Total time spent in ISRs (%)                          0.102324

    ISR count (execution time <250 µs):                   43400
    ISR count (execution time 250-500 µs):                0
    ISR count (execution time 500-999 µs):                0
    ISR count (execution time 1000-1999 µs):              0
    ISR count (execution time 2000-3999 µs):              0
    ISR count (execution time >=4000 µs):                 0


    _________________________________________________________________________________________________________
    REPORTED DPCs
    _________________________________________________________________________________________________________
    DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

    Highest DPC routine execution time (µs):              619.970704
    Driver with highest DPC routine execution time:       ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

    Highest reported total DPC routine time (%):          0.058823
    Driver with highest DPC total execution time:         rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

    Total time spent in DPCs (%)                          0.234657

    DPC count (execution time <250 µs):                   564512
    DPC count (execution time 250-500 µs):                0
    DPC count (execution time 500-999 µs):                3
    DPC count (execution time 1000-1999 µs):              0
    DPC count (execution time 2000-3999 µs):              0
    DPC count (execution time >=4000 µs):                 0


    _________________________________________________________________________________________________________
     REPORTED HARD PAGEFAULTS
    _________________________________________________________________________________________________________
    Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

    NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

    Process with highest pagefault count:                 dropbox.exe

    Total number of hard pagefaults                       3060
    Hard pagefault count of hardest hit process:          2644
    Number of processes hit:                              29


    _________________________________________________________________________________________________________
     PER CPU DATA
    _________________________________________________________________________________________________________
    CPU 0 Interrupt cycle time (s):                       7.942864
    CPU 0 ISR highest execution time (µs):                155.443371
    CPU 0 ISR total execution time (s):                   0.850463
    CPU 0 ISR count:                                      43301
    CPU 0 DPC highest execution time (µs):                310.951072
    CPU 0 DPC total execution time (s):                   1.614055
    CPU 0 DPC count:                                      425836
    _________________________________________________________________________________________________________
    CPU 1 Interrupt cycle time (s):                       4.920021
    CPU 1 ISR highest execution time (µs):                59.606463
    CPU 1 ISR total execution time (s):                   0.000941
    CPU 1 ISR count:                                      99
    CPU 1 DPC highest execution time (µs):                203.456660
    CPU 1 DPC total execution time (s):                   0.024941
    CPU 1 DPC count:                                      3152
    _________________________________________________________________________________________________________
    CPU 2 Interrupt cycle time (s):                       7.101523
    CPU 2 ISR highest execution time (µs):                0.0
    CPU 2 ISR total execution time (s):                   0.0
    CPU 2 ISR count:                                      0
    CPU 2 DPC highest execution time (µs):                619.970704
    CPU 2 DPC total execution time (s):                   0.292943
    CPU 2 DPC count:                                      133004
    _________________________________________________________________________________________________________
    CPU 3 Interrupt cycle time (s):                       3.623097
    CPU 3 ISR highest execution time (µs):                0.0
    CPU 3 ISR total execution time (s):                   0.0
    CPU 3 ISR count:                                      0
    CPU 3 DPC highest execution time (µs):                121.637874
    CPU 3 DPC total execution time (s):                   0.020560
    CPU 3 DPC count:                                      2523
    _________________________________________________________________________________________________________
     

  4. Hi all

    This is an issue I first encountered when using the new presets I bought for Union synth but is now also happening in Zampler that I have just got some free presets for via Beat magazine.

    After auditioning several patches I get a stuttering in CbB - close down CbB and open up again all is fine until I have scrolled through a few more patches then the stuttering starts. I've checked buffer size and processor load and all is fine there - as I say it only happens with some synths - it has occurred with Sampletank 3 previously but ST 4 has been fine. 

    I'm on latest versions of CbB and Win 10. Using Thread Scheduling Config 2 i5 quad core CPU and 8 Gb of RAM. VST's are on an external SSD connected via USB 3.1. Using ASIO 4 All with onboard sound card (which has been fine for years though I know some people don't like it!) 

    Any ideas? It's a bit frustrating having to close CbB down every few minutes when I use these synths! There maybe others with the problem but most I use have been absoultely fine

  5. 36 minutes ago, Fleer said:

    The guy in the vid asks you to subscribe to his channel. 

    I don't think that is compulsory to win the prize (I could be wrong) but it obviously makes it easier to flag up when the winners are to be announced

    Anyway I'm subscribed to Mike's channel as his CbB tutorials are the best I've come across and he seems like a genuinely nice guy! I've learned loads of stuff from him

    • Like 1
  6. On 5/8/2020 at 4:32 AM, Matthew Sorrels said:

    So watching the videos it looks like they have set it up so that if you load a project made with the Pro or Core BBCSO and only have Discover it will still work.  You'll see the "Pro/Core" articulation and it will actually play back.  But substitute with the closest match for the version of BBCSO you have.  Which explains why I could see the articulations in Discover mode and they actually worked.  Which means the stripped down template may actually be better since it will put the drum parts on their own tracks, even for Discover users.  Which is maybe easier to use than having to remember/look up/find by hunting which key is which of the drum articulations.

    Of course this also means you could just use the Pro template as is.  Everything will work, it just won't sound the same.  Definitely an interesting feature.  Should make it nice for students and teachers.

    I still think the pricing is a bit crazy on this, even the sale price feels off to me.  If the sale prices they have now were the normal prices and they had sale pricing on top of that I'd say it was about right.  It will be interesting to see if they put it on sale more in the future.

     

    Thanks so much for putting together the template Matthew. I have just opened it and all seemed ok - I just had to edit my midi input for each track. Saved so much work! As you say all the different articulations are there but they just play the most appropriate sound in Discover.  Could you tell me what the Print tracks are please?

    It will be interesting to do a direct comparison with projects where I have used Miroslav Philharmonik and Garritan. I would imagine though that the most successful approach might be to use elements from each library. After a couple of initial run through of the sounds the strings and percussion in Discover appear to be the strongest elements with the woodwinds being the weakest 

  7. I've been looking into disabling this too as I occasionally get a failed boot up with a black screen and cursor - I understand that this is a possible fix as it is possibly interfering with my graphics driver - though it has only been happening for a few months and usually occirs if I have been using the other profile on my PC and switch back to my main one. It always restarts ok when I force a restart but a bit of a pain. Interesting it only takes a second or so longer to boot if you disable it

×
×
  • Create New...