On 04/18/2013 04:47 AM, Ted Felix wrote:
On 04/18/2013 01:30 AM, Aere Greenway wrote:Unfortunately, I was not able to build Rosegarden from the latest source.src/gui/seqmanager/AudioSegmentMapper.cpp:144:1: internal compiler error: Segmentation faultUsually this is due to the automake stuff being out of sync. Did you do a full rebuild starting from make distclean?$ make distclean $ sh ./bootstrap.sh $ ./configure --enable-debug Note that ./configure needs either --with-qtlibdir=/usr/lib/i386-linux-gnu or --with-qtlibdir=/usr/lib/x86_64-linux-gnu based on which Ubuntu you are using, 32-bit or 64-bit. The exact steps are on that wiki page. http://www.rosegardenmusic.com/wiki/dev:eclipse Ted.
Ted:First thing this morning, on first turning on my machine, I retried the build. It's a 32-bit machine, running an Ubuntu (Unity desktop, unfortunately) partition.
One thing to take note of, when I get the source from Subversion, the "make distclean" step always fails (I don't remember the text of the error). I have been assuming that since nothing was built yet, it didn't matter.
This morning, I did the "make distclean", followed by the steps beyond it. This time the "make distclean" did not generate an error - probably because it had something to clean up.
It made it about 40 minutes into the build, and got another of those errors it suggests is a hardware problem.
But I did the "make" command again, and it eventually made it all the way to the end, and the link succeeded this time.
On testing it, I had a few mis-steps getting it to work. My MIDI device needs to connect to something, or it won't attempt to send MIDI. But I didn't want it going in-parallel to the emu10k1, along with Rosegarden's output. I initially connected it to Rosegarden's input port, which worked initially. Somewhere into it, it stopped making any sound.
I restarted both Rosegarden and my application.I finally connected my device to the Soundblaster card's MIDI interface (which isn't connected to anything), which satisfied my device, yet didn't produce audible output.
I then setup the newly-generated Rosegarden with a recording filter (channel 1 = melody, channel 2 = chords). I also used Rosegarden to connect to my device.
I noticed that while I just played the device, any notes I played (whether chords or melody) played with whatever was specified (in Rosegarden) for the selected track.
Then I recorded, and it sounded like what it was supposed to do, with Oboe for the melody, and String Ensemble 1 for the chords. My performance was not so good, but I was just trying to test.
I know when I played it back the first time, everything sounded fine. But after saving it (I think that was all I did), the first 16 measures ended up with chord-notes that mysteriously stop playing. I have no idea what caused that.
But everything beyond measure 16 is what I played. I have attached the '.rg' files.So to make double sure, I set up a new file, this time recording with French Horn (melody), and String Ensemble 1 (chords).
Other than a less-than-stellar performance on my part, everything recorded fine (hearing the two distinct instruments), and the playback was fine as well.
So it appears your fix works. I don't know what happened to the first part of the first piece. Maybe that was some other problem...
-- Sincerely, Aere
Test-Multi-Device-Record.rg
Description: audio/rosegarden
Test-Multi-Device-Record-2.rg
Description: audio/rosegarden
------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
