Major detuning/CPU consumption bug?

Help
Andrew C
2009-07-26
2013-05-23
  • Andrew C
    Andrew C
    2009-07-26

    Hey Nick,

    Is it normal for preset 7 on the mini to sound so incredibly detuned and to ramp up the CPU when it's being used excessively?

    Also, are all of the pro52's presets supposed to sound really detuned?

    Andrew.

     
    • Nick Copeland
      Nick Copeland
      2009-07-26

      Might have to look at that one. In fact all the mini memories have a bit too much gain (easy to fix) so I will review them.

      Not sure about the pro52 - need to review it and don't have time right now. You might want to see if the envelope is being used to modulate the oscillator - that can give a lot of detune. The envelope is touch responsive so if you use it to drive either osc or filter cutoff you get odd results. I was considering removing this touch sensitivity, I don't think the original had a touch responsive filter envelope, just touch sensitive amp envelope.

      regards, nick.

      regards, nick.

       
      • Andrew C
        Andrew C
        2009-07-26

        Also, the stratus and trilogy fails to load:

        jackstats found -rate 48000 -count 256
        checking availability of TCP port 5028
        port looked busy, trying 5029
        using port 5029
        generate bandwidth limited waveforms(31, 12)
        spawning midi thread
        Fixing samplerate at 48000
        midi sequencer: bristol
        Opened listening control socket: 5029
        midiOpen: 5029(100)
        Client ID = 131
        Queue ID = 1
        Registered 131 0
        Device name "bristol" did not parse, defaults 128.0
        rescheduled thread: 50
        parent going into idle loop
        Got midi thread OK status
        bristol version 0.40.5
        connected to :0.0
        display is 1680 by 1050 pixels
        Window is w 1680, h 1050, d 24, 0 0 0
        Using DirectColor display
        Initialise the strilogy link to bristol: 81393d0
        Initialise the strilogy synth circuits
        hostname is localhost, bristol
        TCP port: 5029
        Accepted connection from 0 (3) onto 2 (5)
        Connected to the bristol control socket: 4
        bristolengine already active
        created 32 voices: allocated 6 to synth
                sid is 0
        spawning audio thread
        registering jack interface: bristol
        rescheduled thread: 75
        init waiting for audio thread OK status
        initialising trilogy synth
        No private microtonal mapping for trilogy
        veloc first 0.00 last 1.00
        Initialise the strilogy organ divider circuits
        hostname is System1337, bristol
        TCP port: 5029
        Accepted connection from 0 (3) onto 3 (8)
        Connected to the bristol control socket: 5
        return - no data in buffer for 2
        Last open conn, exiting
        /usr/local/bin/startBristol: line 361:  5501 Segmentation fault      brighton $args -engine -port ${PORT}

        So does the Vox300 (not the vox):
        jackstats found -rate 48000 -count 256
        checking availability of TCP port 5028
        port looked busy, trying 5029
        using port 5029
        generate bandwidth limited waveforms(31, 12)
        spawning midi thread
        Fixing samplerate at 48000
        midi sequencer: bristol
        Opened listening control socket: 5029
        midiOpen: 5029(100)
        Client ID = 131
        Queue ID = 1
        Registered 131 0
        Device name "bristol" did not parse, defaults 128.0
        rescheduled thread: 50
        parent going into idle loop
        Got midi thread OK status
        bristol version 0.40.5
        connected to :0.0
        display is 1680 by 1050 pixels
        Window is w 1680, h 1050, d 24, 0 0 0
        Using DirectColor display
        Initialise the voxM2 link to bristol: 81393d0
        hostname is localhost, bristol
        TCP port: 5029
        Accepted connection from 0 (3) onto 2 (5)
        Connected to the bristol control socket: 4
        bristolengine already active
        created 32 voices: allocated 32 to synth
                sid is 0
        spawning audio thread
        registering jack interface: bristol
        rescheduled thread: 75
        init waiting for audio thread OK status
        initialising vox sound
        128 frequency mappings: 8.175879 12658.227539, 0.174419 270.042175
        micro first 0.174419 last 270.042175 (vox)
        veloc first 1.00 last 1.00
        hostname is System1337, bristol
        TCP port: 5029
        Accepted connection from 0 (3) onto 3 (8)
        Connected to the bristol control socket: 5
        return - no data in buffer for 2
        Last open conn, exiting
        /usr/local/bin/startBristol: line 361:  5906 Segmentation fault      brighton $args -engine -port ${PORT}

        Andrew.

         
    • Andrew C
      Andrew C
      2009-07-26

      I know this is digressing away from the thread, but I tested the stratus, trilogy and VoxM2 in 0.40.4, and they work fine. It definatly seems to be a bug in the latest release.

      Andrew.

       
    • Nick Copeland
      Nick Copeland
      2009-07-26

      Hi Andrew,

      I can reproduce the seg fault. Will get you a fix asap. Thanks for the report - I did not have any idea there were issues here. Perhaps I should work on some SQA testing procedures - run through at least every emulator start/stop against a single engine that already has some other emulators loaded. Will look into it.

      nick.

       
    • Nick Copeland
      Nick Copeland
      2009-07-26

      Hi Andrew,

      You can find a file in http:/bristol.sf.net/files/interface.c that needs to go into libbristolmidi to fix the crash. I will probably open a bug against it since it needs to be tested for distributed solutions such as the one you and Lars have been asking about. The crash was due to a null pointer where I needed a hostname - I defaulted it to localhost which will work 90% of the time, just that it might fail if distributed as the second synth will not connect to the remote host.

      Nick.

       
    • Andrew C
      Andrew C
      2009-07-27

      Also, FWIW, I didn't have any other bristol engines running when I attempted to start the emulators.

      I.e, I attempted to start one single emulator and engine and then that segfaulted, at which point I tried a few other emulators.

      Andrew.