Build failure

MusE is a DAW for Linux with both MIDI and Audio editing. https://muse-sequencer.github.io

Moderators: MattKingUSA, khz, spamatica

Post Reply
folderol
Established Member
Posts: 2069
Joined: Mon Sep 28, 2015 8:06 pm
Location: Here, of course!
Has thanked: 224 times
Been thanked: 400 times
Contact:

Build failure

Post by folderol »

I just pulled muse from git today and got the error message below using the reccommended build instructions.
-------------------------------
[ 80%] Building CXX object muse/CMakeFiles/core.dir/app.o
In file included from /home/will/Software/muse/muse3/muse/app.cpp:91:0:
/home/will/Software/muse/muse3/muse/components/shortcutconfig.h: In member function ‘void MusEGui::ShortcutConfig::updateSCListView()’:
/home/will/Software/muse/muse3/muse/components/shortcutconfig.h:71:68: error: ‘textFilter’ was not declared in this scope
void updateSCListView() { updateSCListView(current_category, textFilter->text()); }
^~~~~~~~~~
muse/CMakeFiles/core.dir/build.make:412: recipe for target 'muse/CMakeFiles/core.dir/app.o' failed
The Yoshimi guy {apparently now an 'elderly'}
Tim E. Real
Established Member
Posts: 660
Joined: Sat Sep 15, 2012 12:36 am
Has thanked: 36 times
Been thanked: 105 times

Re: Build failure

Post by Tim E. Real »

Hm, textFilter is simply a line edit widget in the shortcut configuration dialog.
Should not be any trouble there. I have not seen any trouble.
Robert made some changes in that section recently.

Are you building from scratch or pulling to update an existing build?
Sometimes it is best if an existing build directory is wiped clean from scratch otherwise sometimes the build can become confused.

Are you building by running the simple './compile_muse.sh', or by following the more complete instructions in README?

Also there is a slight ambiguity in the README build instructions:

Code: Select all

- To compile MusE, run the following commands from the 
         top level directory where the source code was unpacked
         (the directory where THIS README FILE is found):
Those instructions were written before another top 'top-level' directory was added
and everything else moved below into a sub-directory.
So it should say something like:

Code: Select all

- To compile MusE, run the following commands from
         the directory where THIS README FILE is found:
folderol
Established Member
Posts: 2069
Joined: Mon Sep 28, 2015 8:06 pm
Location: Here, of course!
Has thanked: 224 times
Been thanked: 400 times
Contact:

Re: Build failure

Post by folderol »

This has unfortunately gone from bad to worse.
Clearing out the build directory resulted in the next build attempt complaining of missing files, so I cleared out the lot and fetched a new git copy. this then seemed to build without problems.
However attempting run it produced a brief flash on the main window, then nothing. At the same time qjackctl reported several hundred Xruns.
call it from a terminal window gave a complaint that it was looking for version 3.2 of the default template but 3.1 was installed.
clearing out both 3.1 and 3.0 from usr/share and trying to run again enabled it to start sometimes, but it was extremely flaky and would fall over at the slightest thing.
If I have qjackctl running, each time I get the same extreme number of Xruns.
Curiously, re-installing results in it once more creating version 3.1 of the default template.

No other audio stuff seem to have any issues at all, including the 'other' sequencers. Even Carla behaves properly, and I've found that can be quite fussy sometimes.

At this point I give up!

Running on a quad core Intel, with devuan ascii2
The Yoshimi guy {apparently now an 'elderly'}
Tim E. Real
Established Member
Posts: 660
Joined: Sat Sep 15, 2012 12:36 am
Has thanked: 36 times
Been thanked: 105 times

Re: Build failure

Post by Tim E. Real »

it was looking for version 3.2 of the default template but 3.1 was installed
OK thanks. Usually that's nothing to worry about, simply saying that the templates, or your song files, will be upgraded.
But in this case it appears that the installation did not go well, since the newer 3.2 templates should have been installed
and it should not have complained about old templates lying around.
Possibly it ended up with two installations? One in /usr and one in /usr/local? Check and clean if required.

I'd suggest wiping out $HOME/.config/MusE/Muse.cfg and possibly MusE-qt.conf,
and deleting the build directory and trying again.

Finally, one possible reason for the program hanging up is Pulse interfering with Jack.
For example on my distro, by default when I attempted to run Jack while Pulse was already running, MusE would hang.
Then I opened the Pulse control panel and made sure the Jack device is the first priority device.
Now I can run Jack and Pulse, and MusE does not hang no matter what audio driver MusE ends up choosing.

Try to post some output, might give me some clues.
Use "muse3 -D" for debugging output.
Also try eliminating various startup options one by one (see "muse3 -h" for help) such as
-L (no LASH, if built with LASH support),
-a (no audio, dummy driver only),
or the various plugin support disabling options like -pNI2
Or, working backwards from minimal support, try "muse3 -DaLpNI2" and reintroduce each flag one at a time.

Thanks.
folderol
Established Member
Posts: 2069
Joined: Mon Sep 28, 2015 8:06 pm
Location: Here, of course!
Has thanked: 224 times
Been thanked: 400 times
Contact:

Re: Build failure

Post by folderol »

It's screwing up with jackd. I'm using jackd2 version 1.9.10

As I said before all my other software runs under jack without problems. pulseaudio is not relevant I have the server completely disabled (with predudice!)

Incidentally, having a system monitor up, shows jackd being started then almost immediately, while muse is still apparently initialising. Also, if running with jackd started by qjackctl muse shuts jackd down leaving qjackctl hanging.

On very rare occasions I can get it to run and as it starts there is the entry below

Setting project path to /home/will/MusE
`��P�UStarting in LV2 plugin mode

Whenever I've seen something like this it usually turns out to be a memory allocation error.

I've shown the reports from just before the errors show up.


JACK: buffersize changed 64
Audio::seek already at frame:0
graph_callback()
MusE: STARTING Heartbeat timer
MusE::seqStart: getting audio driver MusEGlobal::realTimePriority:90
graph_callback()
Audio::seek already at frame:0
starting with template /usr/local/share/muse-3.1/templates/default.med
Thread <Prefetch, id 0x7fbdf94e6700> has SCHED_FIFO priority 85
JackEngine::XRun: client = MusE was not finished, state = Running
JackAudioDriver::ProcessGraphAsyncMaster: Process error
MusE: STOPPING Heartbeat timer
JackPosixProcessSync::LockedTimedWait error usec = 26660 err = Connection timed out
JackEngine::ClientDeactivate wait error ref = 2 name = MusE
cannot deactivate client
Song::clear
setRecord recordflag =0 f(record state)=0 autoRecEnable=1
JACK: buffersize changed 64
JackPosixProcessSync::LockedTimedWait error usec = 26660 err = Connection timed out
JackEngine::ClientActivate wait error ref = 2 name = MusE
JACK: cannot activate client
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot read socket fd = 15 err = Connection reset by peer
Could not read notification result
ClientNotify fails name = MusE notification = 18 val1 = 0 val2 = 0
Cannot write socket fd = 15 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = MusE notification = 18 val1 = 1 val2 = 0
Cannot write socket fd = 15 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = MusE notification = 4 val1 = 0 val2 = 0
Cannot write socket fd = 15 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = MusE notification = 3 val1 = 0 val2 = 0
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = MusE was not finished, state = Triggered
JackAudioDriver::ProcessGraphAsyncMaster: Process error
Cannot write socket fd = 15 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = MusE notification = 10 val1 = 13 val2 = 0
Cannot write socket fd = 15 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = MusE notification = 10 val1 = 14 val2 = 0
Cannot write socket fd = 15 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = MusE notification = 10 val1 = 13 val2 = 0
Cannot write socket fd = 15 err = Broken pipe
CheckRes error
Could not write notification
ClientNotify fails name = MusE notification = 10 val1 = 14 val2 = 0
Unknown error...
terminate called after throwing an instance of 'Jack::JackTemporaryException'
what():
The Yoshimi guy {apparently now an 'elderly'}
Post Reply