Ubuntu Studio and Jack issues

Help
Stef
2009-07-25
2013-05-23
  • Stef
    Stef
    2009-07-25

    Hi,

    after a while i switched to the 32bit Version of Ubuntu Studio, but i have now some issues regarding Jack and Bristol (0.40.3, compiled from scratch) working together on a ICE1712 chipset of a Terratec DMX6Fire. Jack comes up by using qjackctl, connects fine, then shows this:

    bla@noname:~/bri2/bristol-0.40.5/bristol$ startBristol -jack -pro52
    jackstats found -rate -count
    checking availability of TCP port 5028
    using port 5028
    generate bandwidth limited waveforms(31, 12)
    spawning midi thread
    rescheduled thread: 50
    parent going into idle loop
    Init waiting for midi thread OK status
    Fixing samplerate at 0
    midi sequencer: bristol
    Opened listening control socket: 5028
    midiOpen: 5028(100)
    Client ID = 130
    Queue ID = 1
    Registered 130 0
    Device name "bristol" did not parse, defaults 128.0
    Got midi thread OK status
    bristol version 0.40.5
    connected to :0.0
    display is 2560 by 1024 pixels
    Window is w 2560, h 1024, d 24, 0 0 0
    Using DirectColor display
    Initialise the prophet52 link to bristol: 23882e0
    hostname is localhost, bristol
    TCP port: 5028
    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
    bristolAudioOpen(plughw:0,0, 44100, 0, 1a00008)
    audioOpen(539f7100, 0, 1024): plughw:0,0
    opening device plughw:0,0, flags 0000000d
    open playback on plughw:0,0, pre 8
    Error opening PCM device plughw:0,0
    Problem opening audio device plughw:0,0, exiting audio thread
    could not get thread schedule
    audio thread failed: exiting.
    parent exiting
    return - no data in buffer for 0
    cleanupBrighton(0)
    cleared sigpipe handler
    cleanupBrighton(0)
    midi write error, fd 4, size 1
    return - no data in buffer for 0
    socket closed
    request acked: -1
    bla@noname:~/bri2/bristol-0.40.5/bristol$ startBristol -jack -pro52
    jackstats found -rate 44100 -count 1024
    checking availability of TCP port 5028
    using port 5028
    generate bandwidth limited waveforms(31, 12)
    spawning midi thread
    rescheduled thread: 50
    parent going into idle loop
    Init waiting for midi thread OK status
    Fixing samplerate at 44100
    midi sequencer: bristol
    Opened listening control socket: 5028
    midiOpen: 5028(100)
    Client ID = 130
    Queue ID = 1
    Registered 130 0
    Device name "bristol" did not parse, defaults 128.0
    Got midi thread OK status
    bristol version 0.40.5
    connected to :0.0
    display is 2560 by 1024 pixels
    Window is w 2560, h 1024, d 24, 0 0 0
    Using DirectColor display
    Initialise the prophet52 link to bristol: c882e0
    hostname is localhost, bristol
    TCP port: 5028
    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
    rescheduled thread: 75
    init waiting for audio thread OK status
    registering jack interface: bristol
    unknown option character l
    jackdmp 1.9.2
    Copyright 2001-2005 Paul Davis and others.
    Copyright 2004-2008 Grame.
    jackdmp comes with ABSOLUTELY NO WARRANTY
    This is free software, and you are welcome to redistribute it
    under certain conditions; see the file COPYING for details
    JACK server starting in non-realtime mode
    creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
    Using ALSA driver ICE1712 running on TerraTec DMX6Fire at 0xbf00, irq 18
    the playback device "hw:0" is already in use. Please stop the application using it and run JACK again
    Midi read retry (25263)
    init waiting for audio thread OK status
    Midi read retry (25263)
    init waiting for audio thread OK status
    Midi read retry (25263)
    return - no data in buffer for 0
    cleanupBrighton(0)
    init waiting for audio thread OK status
    Midi read retry (25263)
    init waiting for audio thread OK status
    Midi read retry (25263)
    init waiting for audio thread OK status
    Midi read retry (25263)
    return - no data in buffer for 0
    socket closed
    request acked: -1
    init waiting for audio thread OK status
    unknown option character l
    jackdmp 1.9.2
    Copyright 2001-2005 Paul Davis and others.
    Copyright 2004-2008 Grame.
    jackdmp comes with ABSOLUTELY NO WARRANTY
    This is free software, and you are welcome to redistribute it
    under certain conditions; see the file COPYING for details
    JACK server starting in non-realtime mode
    creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
    Using ALSA driver ICE1712 running on TerraTec DMX6Fire at 0xbf00, irq 18
    the playback device "hw:0" is already in use. Please stop the application using it and run JACK again
    init waiting for audio thread OK status
    init waiting for audio thread OK status
    init waiting for audio thread OK status
    init waiting for audio thread OK status
    failed to receive audio thread OK, exiting

    Brtstol works fine when unsing only ALSA. It doesn't matter if jackd has been started with qjackctl or started by bristol; the result is the same. Without jackd running over qjackctl, Bristol/Brighton seems here trying to start two jackd sessions and the second one -seems- to make Bristol/Brighton crash.

    Many geetings
    Stefan

     
    • Stef
      Stef
      2009-07-25

      Btw, Forget the first try, the second oen is the "troublemaker". Is there no "Edit-"possibility in Sourceforge-Forums?

      Greetings
      Stef

       
    • Stef
      Stef
      2009-07-25

      "unknown option character l "

      Proably also a problem?

      Stef

       
    • Andrew C
      Andrew C
      2009-07-26

      Hey Stefan,

      I think the problem might be that the StartBristol app calls different start up options to jackd, not jackdmp (It might be....) and that's where the Unknown character option comes from. I might check in the StartBristol script and see if there is such weirdness going on.. But to my mind, it seems a tad unlikely.... But it might just explain why two instances of jackdmp are started. But I've no idea why that'd cause bristol to crash.

      But you're able to get Bristol working when running jackd via qjackctl?

      Andrew.

       
    • Nick Copeland
      Nick Copeland
      2009-07-26

      Hi Stef,

      From the second startup:

      ... debug...
      registering jack interface: bristol
      unknown option character l
      jackdmp 1.9.2
      Copyright 2001-2005 Paul Davis and others.
      Copyright 2004-2008 Grame.
      jackdmp comes with ABSOLUTELY NO WARRANTY
      This is free software, and you are welcome to redistribute it
      under certain conditions; see the file COPYING for details
      JACK server starting in non-realtime mode
      creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
      Using ALSA driver ICE1712 running on TerraTec DMX6Fire at 0xbf00, irq 18
      the playback device "hw:0" is already in use. Please stop the application using it and run JACK again
      ...debug...

      The report here (from Jack) is that the audio device is in use. That option error message could be related but I am not sure why. All of the startup for jackd is done in the Jack library, bristol just requests a connection then the library should try and connect to the current one, if that fails it should start one. I have no direct control over this however perhaps that 'option' is misdirecting the API. The call is use is the following:

      jack_client_open("bristol", 0, NULL)

      The string bristol is the default '-audiodev' for the jack connection, you could try other values admittedly however I cannot see where the API gets the 'l' to complain about, after the call to open the connection all I do is get parameters from the process, I do not set anything else.

      Another oddity is that another program that I call 'jackstats' could connect - it came back and reported me the sampling rate and period size.

      nick

       
    • Nick Copeland
      Nick Copeland
      2009-07-26

      Could this be some wierdness from qjackctl? If you saved a .jackdrc then perhaps it has a spurious option in it. Just a thought.

      nick

       
    • Stef
      Stef
      2009-07-26

      Hi,

      could be easy: Bristol works with the Version  of Jack 0.116 and not with Jack2. Thats the issue.

      Many greetings
      Stef

       
    • Nick Copeland
      Nick Copeland
      2009-07-26

      Hi Stef,

      OK. Did you actually test bristol with jack 0.116? If this is the issue then I will have a look at testing with Jack2 here. Andrew - is this what you meant when talking about jackdmp or is that just another version (multithreaded version) of the engine?

      Regards, nick

       
    • Stef
      Stef
      2009-07-26

      Hi Nick,

      exactly. I forgot that i have Jack2 installed, now i removed it, compiled 0.116 and it works fine.

      Greetings
      Stef

       
    • Andrew C
      Andrew C
      2009-07-27

      Hmmm..

      I might be wrong, but the output from stefan's system says:

      jackdmp 1.9.2
      Copyright 2001-2005 Paul Davis and others.
      Copyright 2004-2008 Grame.
      jackdmp comes with ABSOLUTELY NO WARRANTY
      This is free software, and you are welcome to redistribute it
      under certain conditions; see the file COPYING for details

      Which, I'm assuming is jackdmp, not Jack2.
      Unless of course, stefan has both jackdmp and jack2 installed? Or the two branches of code merged together at some point? I'm just speculating here....

      Andrew.

       
      • Colin Fletcher
        Colin Fletcher
        2009-07-30

        http://jackaudio.org/ says: "Future JACK2 will be based on C++ jackdmp code base. Jack 1.9.2 is the "renaming" of jackdmp...".

        So yes, jackdmp 1.9.2 is (a pre-release of) jack2, which will presumably reach version 2.0.0 at some point.

        Colin.