From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-05-22 02:14:30
|
All: I've started trying out the version of Rosegarden distributed with Lubuntu 12.04, and encountered a problem. I think the crash has already generated a bug-report, but with this e-mail, I'm hoping to give you a heads-up of the problem, and fill in a few more details. I was trying to record simultaneously from two tracks of my MIDI keyboard, with MIDI channel 2 going to track 2 (specified by the "Recording filters" in the Special Parameters pane). Similarly, MIDI channel 3 was going to track 3 (again specifying that track and channel in the recording filters). Track 2 was explicitly assigned to MIDI channel 2, and Track 3 was explicitly assigned to MIDI channel 3. It recorded them simultaneously okay, though both instruments had the sound of the selected track (2)'s instrument (one can always hope for better, but not necessarily expect it). The problem was at the end of the recording, when I clicked the stop-button. At that point, it crashed. I said a few choice words, then decided to record the two tracks separately. But at the end of the recording (I think of the 1st track separately, but it might have been the 2nd), it crashed again, in the same manner. I tried another test (the particulars of which I can't remember), but this time, instead of crashing at the end, it froze-up, and I couldn't terminate it, even with the "End Process" option you get after multiple clicks on the "Close Window" button. I rebooted into my Lubuntu 11.10 partition, and tried the same thing, which worked without any problems (in Rosegarden 11.06). So it does seem to be a problem with the newer version of Rosegarden. -- Sincerely, Aere |
From: Brett M. <idr...@gm...> - 2012-05-22 02:24:43
|
On Mon, May 21, 2012 at 10:14 PM, Aere Greenway <Ae...@dv...>wrote: > ** > All: > > I rebooted into my Lubuntu 11.10 partition, and tried the same thing, > which worked without any problems (in Rosegarden 11.06). So it does seem > to be a problem with the newer version of Rosegarden. > > You might consider upgrading to Rosegarden 12.04 (not to be confused with Ubuntu 12.04), I found the 11.11.42 version to be pretty unstable also (I got random crashes editing CC data) -- Brett W. McCoy -- http://www.brettwmccoy.com ------------------------------------------------------------------------ "In the rhythm of music a secret is hidden; If I were to divulge it, it would overturn the world." -- Jelaleddin Rumi |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-05-22 02:46:01
|
Brett: I am developing MIDI courseware (making use of Rosegarden), so for that, I am pretty dependent on what is in the Linux distributions' repositories. Ubuntu 12.04 is one of the most popular Linux distrubutions, and Ubuntu 12.04 is a long-term-support release. I hope we aren't stuck with an unstable version of Rosegarden for 3 years... - Aere On Mon, 2012-05-21 at 22:24 -0400, Brett McCoy wrote: > On Mon, May 21, 2012 at 10:14 PM, Aere Greenway > <Ae...@dv...> wrote: > > All: > > I rebooted into my Lubuntu 11.10 partition, and tried the same > thing, which worked without any problems (in Rosegarden > 11.06). So it does seem to be a problem with the newer > version of Rosegarden. > > > > > You might consider upgrading to Rosegarden 12.04 (not to be confused > with Ubuntu 12.04), I found the 11.11.42 version to be pretty unstable > also (I got random crashes editing CC data) > > > > -- > Brett W. McCoy -- http://www.brettwmccoy.com > ------------------------------------------------------------------------ > "In the rhythm of music a secret is hidden; If I were to divulge it, > it would overturn the world." > -- Jelaleddin Rumi -- Sincerely, Aere |
From: Brett M. <idr...@gm...> - 2012-05-22 02:50:24
|
On Mon, May 21, 2012 at 10:45 PM, Aere Greenway <Ae...@dv...>wrote: > ** > Brett: > > I am developing MIDI courseware (making use of Rosegarden), so for that, I > am pretty dependent on what is in the Linux distributions' repositories. > Ubuntu 12.04 is one of the most popular Linux distrubutions, and Ubuntu > 12.04 is a long-term-support release. > > I hope we aren't stuck with an unstable version of Rosegarden for 3 > years... > Well, let's hope Ubuntu updates their packages once we get Rosegarden stable... or at least someone creates PPAs for Ubuntu... Please file bug reports on anything you find! -- Brett W. McCoy -- http://www.brettwmccoy.com ------------------------------------------------------------------------ "In the rhythm of music a secret is hidden; If I were to divulge it, it would overturn the world." -- Jelaleddin Rumi |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-05-22 02:59:41
|
Brett: I have an automated installation procedure, so I could deal with using a PPA. I have been using one for Qsynth (in the Ubuntu 11.10 release). Unfortunately, they didn't bother to release the fix in what went out with Ubuntu 12.04 LTS, so I really am stuck there... - Aere On Mon, 2012-05-21 at 22:49 -0400, Brett McCoy wrote: > On Mon, May 21, 2012 at 10:45 PM, Aere Greenway > <Ae...@dv...> wrote: > > Brett: > > I am developing MIDI courseware (making use of Rosegarden), so > for that, I am pretty dependent on what is in the Linux > distributions' repositories. Ubuntu 12.04 is one of the most > popular Linux distrubutions, and Ubuntu 12.04 is a > long-term-support release. > > I hope we aren't stuck with an unstable version of Rosegarden > for 3 years... > > > > Well, let's hope Ubuntu updates their packages once we get Rosegarden > stable... or at least someone creates PPAs for Ubuntu... > > Please file bug reports on anything you find! > > > > -- > Brett W. McCoy -- http://www.brettwmccoy.com > ------------------------------------------------------------------------ > "In the rhythm of music a secret is hidden; If I were to divulge it, > it would overturn the world." > -- Jelaleddin Rumi -- Sincerely, Aere |
From: Tom B. (Tehom) <te...@pa...> - 2012-05-22 16:41:51
|
> All: > > I've started trying out the version of Rosegarden distributed with > Lubuntu 12.04, and encountered a problem. I think the crash has already > generated a bug-report, but with this e-mail, I'm hoping to give you a > heads-up of the problem, and fill in a few more details. So that's Lubuntu 12.04, released two weeks before our 12.04, and it has Rosegarden 11.11.42. I highlight this because our playthru code and some sequencer/driver co-ordination did change in Rosegarden 12.04 (my responsibility). But you're experiencing that on 11.11.42 I can't reproduce it. My keyboard only sends on one channel and I don't get a crash. I know you said you couldn't easily upgrade, and I don't want to hold out too much hope that distantly-related changes somehow fixed it. But if you find you can upgrade, please let us know how it goes. And thank you for the bug report. Tom Breton (Tehom) |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-05-22 17:54:53
|
Tom: In many cases, people can (from their synthesizer) send on two channels at once - they just don't realize it. If your synthesizer has the capability of doing a "split keyboard", which means designating part of the keyboard for one instrument, and the other part for another instrument, it has the capability of sending on two MIDI channels at the same time. There is probably another part of the MIDI setup where you designate the two MIDI channels used for each part of a split-keyboard. My old Roland D20 synthesizer can even do a keyboard split. My newer Yamaha S90-ES can do it, but it's has to do with setting up a custom voice. You could also test it by running vkeybd (the old virtual MIDI keyboard), along with VMPK. Use both of them (rather than two instances of either) so you can tell them apart. When you click the "Manage MIDI Devices" toolbar button in Rosegarden, you will see the two virtual keyboard MIDI input devices. Both virtual keyboards have a way of specifying which MIDI channel they send on. One other piece of information that might be helpful, is that I was using qjackctl, and qsynth (for the sound generation). I don't know if that affected it. I will run the same test using just my Soundblaster card (with its emu10k1 synthesizers) and see if that makes a difference, letting you know if it does. - Aere On Tue, 2012-05-22 at 12:41 -0400, Tom Breton (Tehom) wrote: > > All: > > > > I've started trying out the version of Rosegarden distributed with > > Lubuntu 12.04, and encountered a problem. I think the crash has already > > generated a bug-report, but with this e-mail, I'm hoping to give you a > > heads-up of the problem, and fill in a few more details. > > So that's Lubuntu 12.04, released two weeks before our 12.04, and it has > Rosegarden 11.11.42. I highlight this because our playthru code and some > sequencer/driver co-ordination did change in Rosegarden 12.04 (my > responsibility). But you're experiencing that on 11.11.42 > > I can't reproduce it. My keyboard only sends on one channel and I don't > get a crash. > > I know you said you couldn't easily upgrade, and I don't want to hold out > too much hope that distantly-related changes somehow fixed it. But if you > find you can upgrade, please let us know how it goes. And thank you for > the bug report. > > Tom Breton (Tehom) > > -- Sincerely, Aere |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-05-22 19:09:22
|
Tom: I just tried it without using qjackctl or qsynth. For sound generation, I used only my Soundblaster card (emu10k1). I used my keyboard, recording on the two MIDI channels simultaneously (this time 5, and 6), and it seemed to go well while recording the piece. I saw the note-lines appearing in the segments of both tracks, simultaneously. I finished playing the piece, and the position-line in the segments pane was still moving. I then clicked the "stop" (the filled-in square) toolbar button of the Rosegarden window, and the Rosegarden window immediately disappeared (I assume from the crash). It doesn't bring up the bug-report dialog now because I have already reported the crash. - Aere On Tue, 2012-05-22 at 11:54 -0600, Aere Greenway wrote: > Tom: > > In many cases, people can (from their synthesizer) send on two > channels at once - they just don't realize it. > > If your synthesizer has the capability of doing a "split keyboard", > which means designating part of the keyboard for one instrument, and > the other part for another instrument, it has the capability of > sending on two MIDI channels at the same time. > > There is probably another part of the MIDI setup where you designate > the two MIDI channels used for each part of a split-keyboard. My old > Roland D20 synthesizer can even do a keyboard split. My newer Yamaha > S90-ES can do it, but it's has to do with setting up a custom voice. > > You could also test it by running vkeybd (the old virtual MIDI > keyboard), along with VMPK. Use both of them (rather than two > instances of either) so you can tell them apart. > > When you click the "Manage MIDI Devices" toolbar button in Rosegarden, > you will see the two virtual keyboard MIDI input devices. Both > virtual keyboards have a way of specifying which MIDI channel they > send on. > > One other piece of information that might be helpful, is that I was > using qjackctl, and qsynth (for the sound generation). I don't know > if that affected it. I will run the same test using just my > Soundblaster card (with its emu10k1 synthesizers) and see if that > makes a difference, letting you know if it does. > > - Aere > > > On Tue, 2012-05-22 at 12:41 -0400, Tom Breton (Tehom) wrote: > > > > All: > > > > > > I've started trying out the version of Rosegarden distributed with > > > Lubuntu 12.04, and encountered a problem. I think the crash has already > > > generated a bug-report, but with this e-mail, I'm hoping to give you a > > > heads-up of the problem, and fill in a few more details. > > > > So that's Lubuntu 12.04, released two weeks before our 12.04, and it has > > Rosegarden 11.11.42. I highlight this because our playthru code and some > > sequencer/driver co-ordination did change in Rosegarden 12.04 (my > > responsibility). But you're experiencing that on 11.11.42 > > > > I can't reproduce it. My keyboard only sends on one channel and I don't > > get a crash. > > > > I know you said you couldn't easily upgrade, and I don't want to hold out > > too much hope that distantly-related changes somehow fixed it. But if you > > find you can upgrade, please let us know how it goes. And thank you for > > the bug report. > > > > Tom Breton (Tehom) > > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel > > > -- Sincerely, Aere |
From: Ted F. <te...@te...> - 2012-06-05 14:51:49
|
On 5/22/2012 3:09 PM, Aere Greenway wrote: > I then clicked the "stop" (the filled-in square) toolbar button of the > Rosegarden window, and the Rosegarden window immediately disappeared > (I assume from the crash). I cannot get two MIDI keyboards to crash rg. Here are the steps I took: 1. Launch jack and fluidsynth from the command line. See "My Audio Script" at http://tedfelix.com/linux/linux-midi.html. 2. Connect Akai LPK25 MIDI keyboard to USB (fixed on MIDI channel 1). 3. Launch vmpk and set to channel 2. 4. Launch rg. 5. Make sure both MIDI keyboards are in Studio > Manage MIDI Devices. 6. Arm tracks 1 and 2. 7. Press record. 8. Play on both keyboards. 9. Stop. I tested the above on 11.06, 11.11.42, and the latest svn. Ubuntu 12.04 64-bit. No crashes. The MIDI events go to both tracks (which seems slightly useless, but is the same for all versions tested). Sounds like you might have a bad library. Are there any steps I may have missed? Ted. |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-06-05 18:27:26
|
Ted: It sounds like the devices you set up for testing this should be sufficient for testing this particular problem. As for the library used, I do not build Rosegarden, but simply use what comes from the distribution when you download Rosegarden from the repository. Your statement that the same thing went to both tracks (seeming slightly useless) suggests that you did not set up the recording filters (so that one input device goes to one track, and the other input device goes to the other track). It is true that input from either keyboard goes to the selected track while not recording, but while recording, if the recording filters are set up right, only the MIDI signals from one device goes to one of the tracks, and only the MIDI signals from the other device goes to the other track. My suspicion is that the problem is related to using the MIDI recording filters, rather than just the use of two input devices. The recording filters worked properly for me on the prior release, and from the notes appearing in the two tracks' segments, it appeared to be working properly on the current version of Rosegarden during the actual recording, but it crashed at the very end, when I stopped the recording process. There is one other minor difference between what the two of us used, in that I am using the 32-bit OS and applications. The main reason this capability is useful to me, is with the MIDI device I am using, I have a way of playing chords with one hand, and the melody with the other hand. If you put the chords and melody on the same track, when the melody hits a note of the chord, it shuts off that note of the chord when you release the melody note. Also, where they are on different tracks, I can use different instruments (and loudness settings) for the chords. Other possible differences, is that my device uses Java MIDI/sound interfaces, going through an M-Audio 2x2 USB MIDI interface. My MIDI device is also one of my own creation, so is is suspect as well. But it works fine on the prior level of Rosegarden, which is why I am approaching it as a bug in the particular Rosegarden release paired with Ubuntu 12.04 LTS. Could you please try your test again, setting up the recording filters on the two tracks of Rosegarden, so that the input of one device goes only to one track, and the input of the other device goes only to the other track (during recording)? I think the problem is related to using the recording filters (with the two input devices). If that doesn't reproduce the problem, let me know, and I will do more investigation to try to better narrow-down the source of the problem. I could certainly run Rosegarden from a terminal, so that I could retrieve diagnostic information at the time of the crash. Thanks, Aere On Tue, 2012-06-05 at 10:51 -0400, Ted Felix wrote: > On 5/22/2012 3:09 PM, Aere Greenway wrote: > > I then clicked the "stop" (the filled-in square) toolbar button of the > > Rosegarden window, and the Rosegarden window immediately disappeared > > (I assume from the crash). > > I cannot get two MIDI keyboards to crash rg. Here are the steps I took: > > 1. Launch jack and fluidsynth from the command line. > See "My Audio Script" at http://tedfelix.com/linux/linux-midi.html. > 2. Connect Akai LPK25 MIDI keyboard to USB (fixed on MIDI channel 1). > 3. Launch vmpk and set to channel 2. > 4. Launch rg. > 5. Make sure both MIDI keyboards are in Studio > Manage MIDI Devices. > 6. Arm tracks 1 and 2. > 7. Press record. > 8. Play on both keyboards. > 9. Stop. > > I tested the above on 11.06, 11.11.42, and the latest svn. Ubuntu > 12.04 64-bit. No crashes. The MIDI events go to both tracks (which > seems slightly useless, but is the same for all versions tested). > > Sounds like you might have a bad library. Are there any steps I may > have missed? > > Ted. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel -- Sincerely, Aere |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-06-09 17:24:36
|
Ted: I had additional information on the Rosegarden crash, but my reply with the information included two '.rg' attachments. In case the reply got filtered-out because of the attachments, here is the information without the attachments: I re-ran my test, with Rosegarden running in a terminal so I could collect diagnostic information. The results were much the same as before, except that when I stopped the recording (this time by pressing the Play button, rather than clicking the Stop button), Rosegarden (in the terminal session) went into a loop outputting the following text: WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at 107520 (split duration 960), ignoring remainder WARNING: This is probably a bug; fix required WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 892 at 107520 (split duration 960), ignoring remainder WARNING: This is probably a bug; fix required WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at 107520 (split duration 960), ignoring remainder WARNING: This is probably a bug; fix required WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 892 at 107520 (split duration 960), ignoring remainder WARNING: This is probably a bug; fix required WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at 107520 (split duration 960), ignoring remainder WARNING: This is probably a bug; fix required WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 892 at 107520 (split duration 960), ignoring remainder WARNING: This is probably a bug; fix required WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at 107520 (split duration 960), ignoring remainder WARNING: This is probably a bug; fix required WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 892 at 107520 (split duration 960), ignoring remainder WARNING: This is probably a bug; fix required WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at 107520 (split duration 960), ignoring remainder WARNING: This is probably a bug; fix required WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 892 at 107520 (split duration 960), ignoring remainder WARNING: This is probably a bug; fix required WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for event of duration 896 at ^C aere@aere-Dell-DE051:~$ It did this for a very long time, and I finally terminated it via a control-C sequence. In looking at the diagnostic information, I wondered if perhaps it might have something to do with the chord at the end of the piece being held (at least some notes of the chord) for a very long time (while other notes of the chord switch between major/minor 3rd and major/minor 7th. So I recorded once, stopping playing before the very long held-out notes. It actually succeeded in recording that once, but subsequent attempts (again stopping playing early) failed the same way as before. So I have only that one successful short recording on the 11.11.42 version of Rosegarden. I have attached that recording, which may be of limited value, since the recording filters do not get saved in the file (I wish they were saved in the file - it would save me time setting it up for subsequent recording). I have also attached the version of the piece I recorded on the earlier version of Rosegarden, which has been quantized and edited so that it prints out properly. Given the editing and quantization, it may not be that useful, but is is what I played when recording, and it was originally successfully recorded on the earlier version of Rosegarden. It is possible my MIDI software is doing something wrong (I have no clue of what), but it records fine on the prior version of Rosegarden. - Aere On Tue, 2012-06-05 at 10:51 -0400, Ted Felix wrote: > On 5/22/2012 3:09 PM, Aere Greenway wrote: > > I then clicked the "stop" (the filled-in square) toolbar button of the > > Rosegarden window, and the Rosegarden window immediately disappeared > > (I assume from the crash). > > I cannot get two MIDI keyboards to crash rg. Here are the steps I took: > > 1. Launch jack and fluidsynth from the command line. > See "My Audio Script" at http://tedfelix.com/linux/linux-midi.html. > 2. Connect Akai LPK25 MIDI keyboard to USB (fixed on MIDI channel 1). > 3. Launch vmpk and set to channel 2. > 4. Launch rg. > 5. Make sure both MIDI keyboards are in Studio > Manage MIDI Devices. > 6. Arm tracks 1 and 2. > 7. Press record. > 8. Play on both keyboards. > 9. Stop. > > I tested the above on 11.06, 11.11.42, and the latest svn. Ubuntu > 12.04 64-bit. No crashes. The MIDI events go to both tracks (which > seems slightly useless, but is the same for all versions tested). > > Sounds like you might have a bad library. Are there any steps I may > have missed? > > Ted. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel -- Sincerely, Aere |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-06-05 21:04:47
|
Ted, and all: In loading and playing the demo-piece (recorded on the prior version of Rosegarden), it reminded me of another problem I have been noticing in the newer level (11.11.42). I have an audio-track associated with it (included in the sequence from the "rosegarden" directory, but not included in the prior e-mail's attachment). In verifying that my compositions carry-forward to the new level of Rosegarden, I find that the first 14 measures (approximately) of each audio track have no visible wave-form in the audio track, though it plays perfectly. It appears to be a problem in the display of the audio track (and that same problem was evident in the demo-piece). I observed this behavior in all of my pieces (from the prior level of Rosegarden) that included an audio track, on every audio track (where multiple audio tracks are included). - Aere On Tue, 2012-06-05 at 10:51 -0400, Ted Felix wrote: > On 5/22/2012 3:09 PM, Aere Greenway wrote: > > I then clicked the "stop" (the filled-in square) toolbar button of the > > Rosegarden window, and the Rosegarden window immediately disappeared > > (I assume from the crash). > > I cannot get two MIDI keyboards to crash rg. Here are the steps I took: > > 1. Launch jack and fluidsynth from the command line. > See "My Audio Script" at http://tedfelix.com/linux/linux-midi.html. > 2. Connect Akai LPK25 MIDI keyboard to USB (fixed on MIDI channel 1). > 3. Launch vmpk and set to channel 2. > 4. Launch rg. > 5. Make sure both MIDI keyboards are in Studio > Manage MIDI Devices. > 6. Arm tracks 1 and 2. > 7. Press record. > 8. Play on both keyboards. > 9. Stop. > > I tested the above on 11.06, 11.11.42, and the latest svn. Ubuntu > 12.04 64-bit. No crashes. The MIDI events go to both tracks (which > seems slightly useless, but is the same for all versions tested). > > Sounds like you might have a bad library. Are there any steps I may > have missed? > > Ted. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel -- Sincerely, Aere |
From: Tom B. (Tehom) <te...@pa...> - 2012-06-08 16:19:46
|
> In verifying that my compositions carry-forward to the new level of > Rosegarden, I find that the first 14 measures (approximately) of each > audio track have no visible wave-form in the audio track, though it > plays perfectly. It appears to be a problem in the display of the audio > track (and that same problem was evident in the demo-piece). Yes. That bug has been noticed before, and I see it too. IMO it's not a high priority bug, though I have to admit it's unnerving the first time one sees it. Tom Breton (Tehom) |
From: D. M. M. <mic...@ro...> - 2012-06-09 09:53:15
|
On Friday, June 08, 2012, Tom Breton (Tehom) wrote: > > the first 14 measures (approximately) of each audio track have no visible > > wave-form in the audio track, > Yes. That bug has been noticed before, and I see it too. This bug still existed in 12.04, but Chris Cannam is supposed to have fixed it in SVN. I haven't tested it yet. -- D. Michael McIntyre |
From: Tom B. (Tehom) <te...@pa...> - 2012-06-09 20:07:02
|
> This bug still existed in 12.04, but Chris Cannam is supposed to have > fixed it > in SVN. I haven't tested it yet. He seems to have succeeded. I just had a look, and it's displaying the audio preview fine, including the first measures. Good going, Chris! Tom Breton (Tehom) |
From: Ted F. <te...@te...> - 2012-06-11 03:01:15
|
On 6/5/2012 4:41 PM, Aere Greenway wrote: > WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for > event of duration 896 at 107520 (split duration 960), ignoring remainder > WARNING: This is probably a bug; fix required Boy, that looks familiar. I've been in that code and fixed something like that. Anyway, I'm still looking at your problem, but a bit swamped right now. I'll get back to this hopefully in a week or so. I did play with the recording filters (which had no effect, still no crash for me) and I have a response that I need to forward to you (don't have email on my Linux machine, so it gets complicated). Stay tuned.... Ted. |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-06-11 17:08:37
|
Ted: Thanks for the response, and for trying the additional test. I will do more testing to narrow down the problem. >From the error message, it may have something to do with how long chord-notes can be held. With the use of a sustained voice (string ensemble 1), pressing the key to switch from major-7th to minor 7th, only the 3rd and the 7th are changed by the software, and the other notes of the chord are held out for what can be a really long time. Regardless, it causes no problem to Qsynth, the emu10k1 hardware synthesizer, a Yamaha S90-ES, another Yamaha synthesizer (I forget the designation), or a Roland D20. - Aere On Sun, 2012-06-10 at 23:01 -0400, Ted Felix wrote: > On 6/5/2012 4:41 PM, Aere Greenway wrote: > > WARNING: SegmentNotationHelper::makeNoteViable(): No valid split for > > event of duration 896 at 107520 (split duration 960), ignoring remainder > > WARNING: This is probably a bug; fix required > > Boy, that looks familiar. I've been in that code and fixed something > like that. Anyway, I'm still looking at your problem, but a bit swamped > right now. I'll get back to this hopefully in a week or so. I did play > with the recording filters (which had no effect, still no crash for me) > and I have a response that I need to forward to you (don't have email on > my Linux machine, so it gets complicated). Stay tuned.... > > Ted. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel -- Sincerely, Aere |
From: Ted F. <te...@te...> - 2012-06-13 21:43:23
|
On 6/13/2012 1:27 PM, Aere Greenway wrote: > I have come up with a way for you to reproduce the problem on your > system. Wow. Thanks for all this. I'll see if I can squeeze some time in on this soon. That repeating error message was related to the quantizer getting confused with notes of certain durations. (At least the last time I worked on it, this is what the issue was.) So I think the quantizer is a bit fragile and may be the culprit here. Here's my email that I drafted a while ago detailing the tests that I performed. No crash, but I did verify the problem with recording multiple channels and hearing the wrong instruments: ================ While testing with two keyboards on different channels, I was able to verify one of Aere's observations. In rg 11.11.42, if you have two keyboards, each set to a different channel, and recording on different tracks. And if you have a different instrument on each track (e.g. piano and organ), you will hear a different instrument from each keyboard *while recording*. While in "stop" mode, you will hear the instrument of the currently selected track for both keyboards. Fast-forward to the latest svn, and the behavior is different while recording. Instead of each keyboard playing its track's instrument, they both play the currently selected instrument (like when stopped). Here are the steps to reproduce for those with only a single hardware MIDI keyboard: 1. Launch jack and fluidsynth. (I use a script that I wrote for this. See "My Audio Script" at http://tedfelix.com/linux/linux-midi.html) 2. Connect hardware MIDI keyboard as usual. Set it for MIDI channel 1. 3. Launch vmpk (the software MIDI keyboard) and set to channel 2. 4. Launch rg. 5. Make sure both MIDI keyboards are in Studio > Manage MIDI Devices. 6. In the "Recording Filters" in the Track Parameters box, set track 1 to record from channel 1 and track 2 from channel 2. 7. Set instrument 2 to an organ to make it obviously different from the piano in track 1. 8. Arm tracks 1 and 2. 9. Press record. 10. Play on both keyboards. With 11.11.42, the hardware keyboard on channel 1 will make piano sounds. The software keyboard on channel 2 will make organ sounds. With the latest svn, both keyboards sound like either piano or organ depending on which track is currently selected. Seems to me that the old behavior is more useful and we should try and get it back. ================ Additionally, when recording to two channels, notes were dropped on channel 2. This sounds similar to what you were describing. I think we've got three or four rather serious bugs to track down. I'll move these to the top of my list for when I have some time. We should probably open some bug reports to track these. Feel free to do that if you want. If Tom has some time, he should be able to fix the problem with multiple channels all making the same sound when recording. Although it might be a bit tricky. Ted. |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-06-15 04:26:08
|
Ted and all: Good news! The problem where Rosegarden hangs at the end of recording the demo-piece from my MIDI device under development appears to be caused by something I was doing wrong in sending on the MIDI channel. In the Java Sound (MIDI) documentation, in doing a "send" on the MIDI receiver device, a time-stamp is specified. I was just getting the system time in milliseconds for this time-stamp, but according to the details of the specification, it should be in microseconds, and not only that, it also needs to be relative to when the MIDI device was opened. The specification also states that if you don't use timestamps, to specify a -1L (which is what I ultimately changed the code to do). It turned out that my incorrect use of timestamps was preventing my device from working with the Java-Sound synthesizer. When I finally realized this was the cause, and fixed it, I decided to try recording on two tracks in Rosegarden again, since this could affect it. When I tried it (three times), it succeeded all 3 times (it didn't hang when I stopped recording). There is still the problem of the wrong instruments sounding during the recording, and on one of the recordings it missed at least one note-off event on the chords track. I can work-around the problem of the wrong instruments sounding during the recording by turning off MIDI-thru routing in Rosegarden, and routing the MIDI signals from my device (using qjackctl) also to qsynth. That way, I can hear what I'm playing (with the right instruments). I noticed an additional piece of information regarding the wrong instruments sounding during the recording. The first track (for the melody) was correctly using the oboe sound I had specified for it. The 2nd track (for recording the chords MIDI channel) was set to "String Ensemble 1", but the instrument that was sounding for that track was a piano (and neither of the tracks I used were set to any sort of piano sound). But I am convinced the change on my side has fixed the hang at the end of recording on two tracks simultaneously. I am sorry that my mistake has caused you to spend time looking at this, but it did expose other problems that still can cause difficulties for people using multiple (or split) keyboards. - Aere On Wed, 2012-06-13 at 17:43 -0400, Ted Felix wrote: > On 6/13/2012 1:27 PM, Aere Greenway wrote: > > > I have come up with a way for you to reproduce the problem on your > > system. > > > Wow. Thanks for all this. I'll see if I can squeeze some time in > on this soon. That repeating error message was related to the > quantizer getting confused with notes of certain durations. (At least > the last time I worked on it, this is what the issue was.) So I think > the quantizer is a bit fragile and may be the culprit here. > > Here's my email that I drafted a while ago detailing the tests that > I performed. No crash, but I did verify the problem with recording > multiple channels and hearing the wrong instruments: > > ================ > While testing with two keyboards on different channels, I was able to > verify one of Aere's observations. In rg 11.11.42, if you have two > keyboards, each set to a different channel, and recording on different > tracks. And if you have a different instrument on each track (e.g. > piano and organ), you will hear a different instrument from each > keyboard *while recording*. While in "stop" mode, you will hear the > instrument of the currently selected track for both keyboards. > > Fast-forward to the latest svn, and the behavior is different while > recording. Instead of each keyboard playing its track's instrument, > they both play the currently selected instrument (like when stopped). > > Here are the steps to reproduce for those with only a single hardware > MIDI keyboard: > > 1. Launch jack and fluidsynth. (I use a script that I wrote for > this. > See "My Audio Script" at > http://tedfelix.com/linux/linux-midi.html) > 2. Connect hardware MIDI keyboard as usual. Set it for MIDI channel > 1. > 3. Launch vmpk (the software MIDI keyboard) and set to channel 2. > 4. Launch rg. > 5. Make sure both MIDI keyboards are in Studio > Manage MIDI Devices. > 6. In the "Recording Filters" in the Track Parameters box, set track > 1 > to record from channel 1 and track 2 from channel 2. > 7. Set instrument 2 to an organ to make it obviously different from > the piano in track 1. > 8. Arm tracks 1 and 2. > 9. Press record. > 10. Play on both keyboards. > > With 11.11.42, the hardware keyboard on channel 1 will make piano > sounds. The software keyboard on channel 2 will make organ sounds. > With the latest svn, both keyboards sound like either piano or organ > depending on which track is currently selected. > > Seems to me that the old behavior is more useful and we should try and > get it back. > ================ > > Additionally, when recording to two channels, notes were dropped on > channel 2. This sounds similar to what you were describing. > > I think we've got three or four rather serious bugs to track down. > I'll move these to the top of my list for when I have some time. We > should probably open some bug reports to track these. Feel free to do > that if you want. > > If Tom has some time, he should be able to fix the problem with > multiple channels all making the same sound when recording. Although > it might be a bit tricky. > > Ted. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ Rosegarden-devel mailing list Ros...@li... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel -- Sincerely, Aere |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-06-15 15:54:33
|
Ted and all: Unfortunately, I am the bearer of bad news this morning. I was not comfortable with changing my device not to use timestamps being the answer. In particular, why would it record successfully (using the bad timestamps) when I recorded into a single track, rather than into two tracks simultaneously? So just to be sure, I repeated my test this morning, and to my dismay, it failed two out of two times. The failure experienced was hanging when the Stop button was pressed, as before. So the problem still remains, and the way of duplicating the problem I sent you earlier will still work. I don't know why it works sometimes, and fails other times. It may be the result of missing a note-off event in the recording process, which happens only some of the time. This behavior could explain why I wrongly concluded that the problem was not in the earlier version of Rosegarden. - Aere On Wed, 2012-06-13 at 17:43 -0400, Ted Felix wrote: > On 6/13/2012 1:27 PM, Aere Greenway wrote: > > > I have come up with a way for you to reproduce the problem on your > > system. > > > Wow. Thanks for all this. I'll see if I can squeeze some time in > on this soon. That repeating error message was related to the > quantizer getting confused with notes of certain durations. (At least > the last time I worked on it, this is what the issue was.) So I think > the quantizer is a bit fragile and may be the culprit here. > > Here's my email that I drafted a while ago detailing the tests that > I performed. No crash, but I did verify the problem with recording > multiple channels and hearing the wrong instruments: > > ================ > While testing with two keyboards on different channels, I was able to > verify one of Aere's observations. In rg 11.11.42, if you have two > keyboards, each set to a different channel, and recording on different > tracks. And if you have a different instrument on each track (e.g. > piano and organ), you will hear a different instrument from each > keyboard *while recording*. While in "stop" mode, you will hear the > instrument of the currently selected track for both keyboards. > > Fast-forward to the latest svn, and the behavior is different while > recording. Instead of each keyboard playing its track's instrument, > they both play the currently selected instrument (like when stopped). > > Here are the steps to reproduce for those with only a single hardware > MIDI keyboard: > > 1. Launch jack and fluidsynth. (I use a script that I wrote for > this. > See "My Audio Script" at > http://tedfelix.com/linux/linux-midi.html) > 2. Connect hardware MIDI keyboard as usual. Set it for MIDI channel > 1. > 3. Launch vmpk (the software MIDI keyboard) and set to channel 2. > 4. Launch rg. > 5. Make sure both MIDI keyboards are in Studio > Manage MIDI Devices. > 6. In the "Recording Filters" in the Track Parameters box, set track > 1 > to record from channel 1 and track 2 from channel 2. > 7. Set instrument 2 to an organ to make it obviously different from > the piano in track 1. > 8. Arm tracks 1 and 2. > 9. Press record. > 10. Play on both keyboards. > > With 11.11.42, the hardware keyboard on channel 1 will make piano > sounds. The software keyboard on channel 2 will make organ sounds. > With the latest svn, both keyboards sound like either piano or organ > depending on which track is currently selected. > > Seems to me that the old behavior is more useful and we should try and > get it back. > ================ > > Additionally, when recording to two channels, notes were dropped on > channel 2. This sounds similar to what you were describing. > > I think we've got three or four rather serious bugs to track down. > I'll move these to the top of my list for when I have some time. We > should probably open some bug reports to track these. Feel free to do > that if you want. > > If Tom has some time, he should be able to fix the problem with > multiple channels all making the same sound when recording. Although > it might be a bit tricky. > > Ted. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ Rosegarden-devel mailing list Ros...@li... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel -- Sincerely, Aere |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-06-17 04:04:58
|
Ted & all: I noticed one further thing about this problem. Today, I was recording a longer demo-piece with my MIDI device, using the work-around of recording both channels to the same track (and later splitting the segment by source channel). In one of those recording sessions, Rosegarden froze-up when I hit the Stop button at the end of recording, the same way it has been doing when recording to two tracks simultaneously. It only failed that one time, but it did fail once that same way. - Aere On Wed, 2012-06-13 at 17:43 -0400, Ted Felix wrote: > On 6/13/2012 1:27 PM, Aere Greenway wrote: > > > I have come up with a way for you to reproduce the problem on your > > system. > > > Wow. Thanks for all this. I'll see if I can squeeze some time in > on this soon. That repeating error message was related to the > quantizer getting confused with notes of certain durations. (At least > the last time I worked on it, this is what the issue was.) So I think > the quantizer is a bit fragile and may be the culprit here. > > Here's my email that I drafted a while ago detailing the tests that > I performed. No crash, but I did verify the problem with recording > multiple channels and hearing the wrong instruments: > > ================ > While testing with two keyboards on different channels, I was able to > verify one of Aere's observations. In rg 11.11.42, if you have two > keyboards, each set to a different channel, and recording on different > tracks. And if you have a different instrument on each track (e.g. > piano and organ), you will hear a different instrument from each > keyboard *while recording*. While in "stop" mode, you will hear the > instrument of the currently selected track for both keyboards. > > Fast-forward to the latest svn, and the behavior is different while > recording. Instead of each keyboard playing its track's instrument, > they both play the currently selected instrument (like when stopped). > > Here are the steps to reproduce for those with only a single hardware > MIDI keyboard: > > 1. Launch jack and fluidsynth. (I use a script that I wrote for > this. > See "My Audio Script" at > http://tedfelix.com/linux/linux-midi.html) > 2. Connect hardware MIDI keyboard as usual. Set it for MIDI channel > 1. > 3. Launch vmpk (the software MIDI keyboard) and set to channel 2. > 4. Launch rg. > 5. Make sure both MIDI keyboards are in Studio > Manage MIDI Devices. > 6. In the "Recording Filters" in the Track Parameters box, set track > 1 > to record from channel 1 and track 2 from channel 2. > 7. Set instrument 2 to an organ to make it obviously different from > the piano in track 1. > 8. Arm tracks 1 and 2. > 9. Press record. > 10. Play on both keyboards. > > With 11.11.42, the hardware keyboard on channel 1 will make piano > sounds. The software keyboard on channel 2 will make organ sounds. > With the latest svn, both keyboards sound like either piano or organ > depending on which track is currently selected. > > Seems to me that the old behavior is more useful and we should try and > get it back. > ================ > > Additionally, when recording to two channels, notes were dropped on > channel 2. This sounds similar to what you were describing. > > I think we've got three or four rather serious bugs to track down. > I'll move these to the top of my list for when I have some time. We > should probably open some bug reports to track these. Feel free to do > that if you want. > > If Tom has some time, he should be able to fix the problem with > multiple channels all making the same sound when recording. Although > it might be a bit tricky. > > Ted. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ Rosegarden-devel mailing list Ros...@li... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel -- Sincerely, Aere |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-06-14 20:41:37
|
Ted: I would be happy to file the bug reports, except that I have been unable to figure out how to do it. I encountered a serious problem in the upgrade of Lubuntu 11.10 to 12.04, and have just spent a frustrating two hours trying (in vain) to figure out how to report the bug. In the end, the best I could do is post a question on the Ubuntu forum. For the crash of a component, the process appears to be simple. But if there is no crash, there appears to be no way to report the problem. At least, I could not find a way to report the problem in over 2 hours of work trying to find out how to do it. If I, as an experienced Linux user cannot figure out how to report a bug, I wonder how it must seem for a new Linux user. - Aere On Wed, 2012-06-13 at 17:43 -0400, Ted Felix wrote: > On 6/13/2012 1:27 PM, Aere Greenway wrote: > > > I have come up with a way for you to reproduce the problem on your > > system. > > > Wow. Thanks for all this. I'll see if I can squeeze some time in > on this soon. That repeating error message was related to the > quantizer getting confused with notes of certain durations. (At least > the last time I worked on it, this is what the issue was.) So I think > the quantizer is a bit fragile and may be the culprit here. > > Here's my email that I drafted a while ago detailing the tests that > I performed. No crash, but I did verify the problem with recording > multiple channels and hearing the wrong instruments: > > ================ > While testing with two keyboards on different channels, I was able to > verify one of Aere's observations. In rg 11.11.42, if you have two > keyboards, each set to a different channel, and recording on different > tracks. And if you have a different instrument on each track (e.g. > piano and organ), you will hear a different instrument from each > keyboard *while recording*. While in "stop" mode, you will hear the > instrument of the currently selected track for both keyboards. > > Fast-forward to the latest svn, and the behavior is different while > recording. Instead of each keyboard playing its track's instrument, > they both play the currently selected instrument (like when stopped). > > Here are the steps to reproduce for those with only a single hardware > MIDI keyboard: > > 1. Launch jack and fluidsynth. (I use a script that I wrote for > this. > See "My Audio Script" at > http://tedfelix.com/linux/linux-midi.html) > 2. Connect hardware MIDI keyboard as usual. Set it for MIDI channel > 1. > 3. Launch vmpk (the software MIDI keyboard) and set to channel 2. > 4. Launch rg. > 5. Make sure both MIDI keyboards are in Studio > Manage MIDI Devices. > 6. In the "Recording Filters" in the Track Parameters box, set track > 1 > to record from channel 1 and track 2 from channel 2. > 7. Set instrument 2 to an organ to make it obviously different from > the piano in track 1. > 8. Arm tracks 1 and 2. > 9. Press record. > 10. Play on both keyboards. > > With 11.11.42, the hardware keyboard on channel 1 will make piano > sounds. The software keyboard on channel 2 will make organ sounds. > With the latest svn, both keyboards sound like either piano or organ > depending on which track is currently selected. > > Seems to me that the old behavior is more useful and we should try and > get it back. > ================ > > Additionally, when recording to two channels, notes were dropped on > channel 2. This sounds similar to what you were describing. > > I think we've got three or four rather serious bugs to track down. > I'll move these to the top of my list for when I have some time. We > should probably open some bug reports to track these. Feel free to do > that if you want. > > If Tom has some time, he should be able to fix the problem with > multiple channels all making the same sound when recording. Although > it might be a bit tricky. > > Ted. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ Rosegarden-devel mailing list Ros...@li... - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel -- Sincerely, Aere |
From: Ted F. <te...@te...> - 2012-06-20 13:45:06
|
> I would be happy to file the bug reports, except that I have been unable to figure out how to do it. The best place to file bug reports for any piece of software is "upstream". IOW, the developer's website. Bug reports with distros (like lubuntu) tend to get ignored, especially for fringe applications like rosegarden. So, feel free to open a bug report here: http://sourceforge.net/tracker/?group_id=4932&atid=104932 Click on "Add New" near the top. Be sure to create a sourceforge account if you don't have one. It's a bit easier for me to work with bug reports than with the mailing list. So this will help me with gathering info and working on the bug. I'm really busy right now and have very little time for rg (actually doing music for a change, yay!), but I have been trying to analyze this stream of posts on the mailing list, and I'm almost done and ready to start trying to reproduce. The endless loop problem is (in my limited experience) related to the duration of notes and what the notation quantizer is trying to turn them into. So, as you suspect, the problem is indeed in some way related to note duration. In the past, I have been able to reproduce these sorts of issues by importing a carefully crafted MIDI file. So, after analyzing the problem, I should be able to create a MIDI file that on import will cause the problem. Both MIDI import and MIDI recording go through the notation quantizer. This is my suspicion at this point. Hoping to get some time to work on this. Much more fun than the notification stuff I've been working on. Ted. |
From: Ted F. <te...@te...> - 2012-06-22 14:26:36
|
On 6/20/2012 9:44 AM, Ted Felix wrote: > This is my suspicion at this point. Hoping to get some time to work on > this. Ok, finally got some time to look at this. I was unable to reproduce the hang. I suspect that this was fixed back in January. We might be able to work on getting that patch into Ubuntu. In the meantime, can you grab the 12.04 source, build it, and retest? That should fix the hang. Let me know if you need any help getting it built and running it. My process for doing this is on the wiki: http://www.rosegardenmusic.com/wiki/dev:eclipse That gets the latest svn, but you can expand the tarball and start with "Get Dependencies". When you get to "Install Eclipse", stop and type "./rosegarden" to run what you built. Let me know if you need any help and I can walk you through the process. We've still got some more bugs you've identified to work on, so if we can get you running the latest (from svn), we can collaborate on getting them fixed. Then we can look into either a PPA for you, or sending patches to Ubuntu which should work their way into lubuntu. Ted. |
From: Aere G. <Aere@Dvorak-Keyboards.com> - 2012-06-22 17:04:30
|
Ted: Thank you so very much for looking at this! I will attempt to install the latest Rosegarden source and build it. By the way, I already have Eclipse (that's my main Java development environment), and I (yesterday) installed the capability of doing C/C++ into it (because I need to develop a Java Native Interface to interface my MIDI creation with ALSA software devices (the hardware devices already work with no help from a JNI)). I am currently in the middle of something, but I will get to this new task within a week. - Aere On Fri, 2012-06-22 at 10:26 -0400, Ted Felix wrote: > On 6/20/2012 9:44 AM, Ted Felix wrote: > > This is my suspicion at this point. Hoping to get some time to work on > > this. > > Ok, finally got some time to look at this. I was unable to reproduce > the hang. I suspect that this was fixed back in January. We might be > able to work on getting that patch into Ubuntu. In the meantime, can > you grab the 12.04 source, build it, and retest? That should fix the > hang. Let me know if you need any help getting it built and running > it. My process for doing this is on the wiki: > > http://www.rosegardenmusic.com/wiki/dev:eclipse > > That gets the latest svn, but you can expand the tarball and start > with "Get Dependencies". When you get to "Install Eclipse", stop and > type "./rosegarden" to run what you built. > > Let me know if you need any help and I can walk you through the > process. We've still got some more bugs you've identified to work on, > so if we can get you running the latest (from svn), we can collaborate > on getting them fixed. Then we can look into either a PPA for you, or > sending patches to Ubuntu which should work their way into lubuntu. > > Ted. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Rosegarden-devel mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel -- Sincerely, Aere |