24 Dec
2010
24 Dec
'10
10:40 a.m.
Excerpts from Robert Jonsson's message of 2010-12-23 18:10:35 +0100:
Ok, never heard of it, and I'm not sure just 'part' is obvious.
Apparently I never got this far before. I found it quite confusing I
must say.
Worse though is that new input tracks are muted by default (took me a
while to figure out why I couldn't record anything despite proper
routing) and that you have to constantly re-arm everything (wav tracks
at least).
sf is horrible, a few lines on the wiki would be far better than this
horrible generic page.
Another thing I've noticed just now, apparently muse wrote a bunch of
wav and .wca files to the build directory (I might have run it from
there). I never told it to save anything and just using the cwd as a
dump isn't a good idea imho.
Anyway, I wish you good luck with muse and a nice holiday,
Philipp
Hello Philipp,
2010/12/23 Philipp Überbacher <hollunder(a)lavabit.com>
Thanks to someone on your channel muse builds after modifying
trunk/muse2/muse/midiedit/CMakeLists.txt to:
target_link_libraries (
midiedit
${QT_LIBRARIES}
al
icons
widgets
ctrl
)
ctrl needed to be added.
Hi there,
I tried building muse to give it a spin today, but the build failed:
Linking CXX shared library libmuse_core.so
midiedit/libmuse_midiedit.so: undefined reference to
make: *** [all] Error 2
Aborting...
Hmm, no idea why this happens for you. Perhaps Orcan has some idea? Anyway,
upfront a couple of questions/suggestions.
website:
- Part Import/Export <- what does this refer to?
Midi-parts are xml based and can be stored and retrieved from disk. This
gives the possibility to produce a library of parts. Creating a public
library of parts (mainly for drums) has been discussed. - Several
types of audio tracks
* Audio inputs
* Audio outputs
* Wave tracks <- those sound weird, I hope I don't need to
They are regular tracks where you can put/record wave-parts, if you tried
older versions of MusE this is nothing new. - the
following link (found here:
http://muse-sequencer.org/index.php/Download) is more distracting than
anything:
http://sourceforge.net/scm/?type=svn&group_id=93414
Too much information? It's the standard sourceforge page, though you may be
right, we should probably rework that in the wiki. building:
you seem to have switched to cmake but half way it seems. The build
instructions are rather weird and unusual for cmake.
creating build, cd'ing there and invoking cmake .. is not how it's
usually done.
Usually you configure using 'ccmake .' when you build manually or
-DCMAKE_BLA (which you do use) for automatic building.
A DESTDIR is a good thing to have since often enough software
is build in a chroot and hence "make install" as root will fail if it
tries to install into the real /usr.
I'm not convinced there is a usual way. Though you are right we are
beginners with cmake and it can probably be improved.
ccmake is just a curses frontend is it not? You can try to convince me but
instinctively I think we should steer clear of gui tools for building.
Well, I'm looking forward to using a
hopefully improved muse :)
Thank you, we will try to improve the build and get it compiling on all
systems we can :)
Regards,
Robert