Re: [Rosegarden-user] ROSEGARDEN 15.12 RELEASED
On Fri, 1 Jan 2016, Ted Felix wrote: > On 01/01/2016 06:15 PM, Holger Marzen wrote: > >>> Unfortunately Rosegarden still crashes when trying to open a file. It > >>> crashes before opening the file dialog. > > > > #14 0x7f811c8f9e6e in > > Rosegarden::RosegardenApplication::notify(QObject*, QEvent*) () > > at > > /home/hm/src/rosegarden/rosegarden-14436.bad/src/gui/application/RosegardenApplication.cpp:135 > >Rebuild all? > >Strange problems like this can be caused by a messed up build. I was > having some really weird problems a few days ago. A reboot and rebuild > cleared them up. > >If you haven't tried that, it might be worth a shot. The full > procedure might be something like: > > 1. Reboot. > 2. Grab a new copy of the source. > 3. Build and test. Same effect. I chatted with FalkTX, maintainer of KXStudio, and he had a similar effect. Rosegarden didn't crash when opening the file dialog but freezed. I'll ask him if he's still encountering that freeze. -- ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] ROSEGARDEN 15.12 RELEASED
On 01/01/2016 10:26 PM, Ted Felix wrote: > But you could just try deleting your build directory, then going > through the build steps again. That might be enough. If that doesn't work, then I just don't see any way to make progress on this one. It's way not crashing in our code. -- D. Michael McIntyre -- ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] ROSEGARDEN 15.12 RELEASED
On 01/01/2016 06:15 PM, Holger Marzen wrote: >>> Unfortunately Rosegarden still crashes when trying to open a file. It >>> crashes before opening the file dialog. > > #14 0x7f811c8f9e6e in Rosegarden::RosegardenApplication::notify(QObject*, > QEvent*) () > at > /home/hm/src/rosegarden/rosegarden-14436.bad/src/gui/application/RosegardenApplication.cpp:135 Rebuild all? Strange problems like this can be caused by a messed up build. I was having some really weird problems a few days ago. A reboot and rebuild cleared them up. If you haven't tried that, it might be worth a shot. The full procedure might be something like: 1. Reboot. 2. Grab a new copy of the source. 3. Build and test. But you could just try deleting your build directory, then going through the build steps again. That might be enough. Ted. -- ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] ROSEGARDEN 15.12 RELEASED
On Fri, 1 Jan 2016, D. Michael McIntyre wrote: > On 01/01/2016 05:41 PM, Holger Marzen wrote: > > > Unfortunately Rosegarden still crashes when trying to open a file. It > > crashes before opening the file dialog. > > Stack trace? #0 0x7f8114121ee8 in xmlParserInputBufferCreateFilename () from /usr/lib/x86_64-linux-gnu/libxml2.so.2 #1 0x7f81141a77c5 in xmlNewTextReaderFilename () from /usr/lib/x86_64-linux-gnu/libxml2.so.2 #2 0x7f8109b61470 in ?? () from /usr/lib/x86_64-linux-gnu/libgnomevfs-2.so.0 #3 0x7f8109b61862 in gnome_vfs_mime_get_value () from /usr/lib/x86_64-linux-gnu/libgnomevfs-2.so.0 #4 0x7f810a6d2085 in gnome_icon_lookup () from /usr/lib/x86_64-linux-gnu/libgnomeui-2.so.0 #5 0x7f810a6d261d in gnome_icon_lookup_sync () from /usr/lib/x86_64-linux-gnu/libgnomeui-2.so.0 #6 0x7f811b702120 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #7 0x7f811b9314dd in QFileIconProvider::icon(QFileInfo const&) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #8 0x7f811b871a84 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #9 0x7f811b86adc8 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #10 0x7f811c000446 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7f811b86399e in QFileSystemModel::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #12 0x7f811b369894 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x7f811b36e713 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #14 0x7f811c8f9e6e in Rosegarden::RosegardenApplication::notify(QObject*, QEvent*) () at /home/hm/src/rosegarden/rosegarden-14436.bad/src/gui/application/RosegardenApplication.cpp:135 #15 0x7f811bfe6e9c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #16 0x7f811bfeac6a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #17 0x7f811c015f93 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x7f8117d58d13 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f8117d59060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f8117d59124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f811c0163bf in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x7f811b411d9e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #23 0x7f811bfe5c82 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #24 0x7f811bfe5ed7 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #25 0x7f811b8399b6 in QDialog::exec() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #26 0x7f811c6f1eba in Rosegarden::FileDialog::getOpenFileName(QWidget*, QString const&, QString const&, QString const&, QString*, QFlags) () at /home/hm/src/rosegarden/rosegarden-14436.bad/src/gui/widgets/FileDialog.cpp:131 #27 0x7f811c91c72f in Rosegarden::RosegardenMainWindow::slotFileOpen() () at /home/hm/src/rosegarden/rosegarden-14436.bad/src/gui/application/RosegardenMainWindow.cpp:1999 #28 0x7f811cc0e07d in Rosegarden::RosegardenMainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /home/hm/src/rosegarden/rosegarden-14436.bad/build/src/moc_RosegardenMainWindow.cpp:499 #29 0x7f811bffb281 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #30 0x7f811b363132 in QAction::triggered(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #31 0x7f811b36331f in QAction::activate(QAction::ActionEvent) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #32 0x7f811b738dca in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #33 0x7f811b73907c in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #34 0x7f811b7f665a in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #35 0x7f811b3ba144 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #36 0x7f811b369894 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #37 0x7f811b36f0bf in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #38 0x7f811c8f9e6e in Rosegarden::RosegardenApplication::notify(QObject*, QEvent*) () at /home/hm/src/rosegarden/rosegarden-14436.bad/src/gui/application/RosegardenApplication.cpp:135 #39 0x7f811bfe6e9c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #40 0x7f811b36a862 in QApplication
Re: [Rosegarden-user] ROSEGARDEN 15.12 RELEASED
On 01/01/2016 05:41 PM, Holger Marzen wrote: > Unfortunately Rosegarden still crashes when trying to open a file. It > crashes before opening the file dialog. Stack trace? -- D. Michael McIntyre -- ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] ROSEGARDEN 15.12 RELEASED
On Fri, 1 Jan 2016, D. Michael McIntyre wrote: > On 01/01/2016 03:06 PM, Holger Marzen wrote: > > > On my Xubuntu 12.10 LTS I have to tweak CMakeLists.txt: > > - change cmake_minimum_required to (VERSION 2.8.7) > >Is that high required version really neccessary? > > Setting the cmake minimum version was a trade-off between supporting old > distros and features that were painful to avoid. I don't remember the > details, but there was an elaborate discussion over a couple of weeks > where I pushed to get this set lower and lower, and David reworked > things at my request. He was a very good sport about this, but I could > only push the founder of KDE so far in support of obsolete technology. > > The bright side is that obtaining new versions of CMake for old distros > is rather easy. Go to https://cmake.org/download/ and if you grab an > appropriate pre-compiled binary for your architecture, it should work > fine. If not, it's much easier to compile than Rosegarden. I used to > have to do this myself, years ago. In the end, I remembered that > precedent from the past, and felt better about requiring such a recent > CMake version. Yep, was no big thing and works now without any tweaks in CMakeLists.txt. Unfortunately Rosegarden still crashes when trying to open a file. It crashes before opening the file dialog. -- ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] ROSEGARDEN 15.12 RELEASED
On 01/01/2016 03:06 PM, Holger Marzen wrote: > On my Xubuntu 12.10 LTS I have to tweak CMakeLists.txt: > - change cmake_minimum_required to (VERSION 2.8.7) >Is that high required version really neccessary? Setting the cmake minimum version was a trade-off between supporting old distros and features that were painful to avoid. I don't remember the details, but there was an elaborate discussion over a couple of weeks where I pushed to get this set lower and lower, and David reworked things at my request. He was a very good sport about this, but I could only push the founder of KDE so far in support of obsolete technology. The bright side is that obtaining new versions of CMake for old distros is rather easy. Go to https://cmake.org/download/ and if you grab an appropriate pre-compiled binary for your architecture, it should work fine. If not, it's much easier to compile than Rosegarden. I used to have to do this myself, years ago. In the end, I remembered that precedent from the past, and felt better about requiring such a recent CMake version. I should have mentioned something about this in the release note, but I simply forgot this was going to be an issue. -- D. Michael McIntyre -- ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] ROSEGARDEN 15.12 RELEASED
On Fri, 1 Jan 2016, Abrolag wrote: > On Thu, 31 Dec 2015 09:32:09 -0500 > "D. Michael McIntyre" wrote: > > > == ROSEGARDEN 15.12, codename "Peace" RELEASED == > > > > The Rosegarden team is pleased to announce the release of version 15.12 > > of Rosegarden, an audio and MIDI sequencer and musical notation editor > > for Linux. > > > > http://www.rosegardenmusic.com/ > > > > Rosegarden rounds out 2015 with a new CMake build system and several bug > > fixes contributed by David Faure of KDE. The new build system preserves > > the best features of the previous system, while adding out-of-source > > builds, and the ability to compile with Qt 4 or Qt 5. (Qt 5 builds are > > functional, but do have some problems. We encourage you to give a Qt 5 > > build a try and report bugs, but package maintainers and production > > users should stick with Qt 4 for the time being.) > > Thanks for the New Year's present. I shall unwrap it soon :) On my Xubuntu 12.10 LTS I have to tweak CMakeLists.txt: - change cmake_minimum_required to (VERSION 2.8.7) Is that high required version really neccessary? - set(USE_QT4 true) It doesn't detect that I don't have qt5 But all this tweaking doesn't help. When I open the file dialog Rosegarden crashed. -- ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] ROSEGARDEN 15.12 RELEASED
On Thu, 31 Dec 2015 09:32:09 -0500 "D. Michael McIntyre" wrote: > == ROSEGARDEN 15.12, codename "Peace" RELEASED == > > The Rosegarden team is pleased to announce the release of version 15.12 > of Rosegarden, an audio and MIDI sequencer and musical notation editor > for Linux. > > http://www.rosegardenmusic.com/ > > Rosegarden rounds out 2015 with a new CMake build system and several bug > fixes contributed by David Faure of KDE. The new build system preserves > the best features of the previous system, while adding out-of-source > builds, and the ability to compile with Qt 4 or Qt 5. (Qt 5 builds are > functional, but do have some problems. We encourage you to give a Qt 5 > build a try and report bugs, but package maintainers and production > users should stick with Qt 4 for the time being.) Thanks for the New Year's present. I shall unwrap it soon :) -- W J G -- ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
[Rosegarden-user] ROSEGARDEN 15.12 RELEASED
== ROSEGARDEN 15.12, codename "Peace" RELEASED == The Rosegarden team is pleased to announce the release of version 15.12 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. http://www.rosegardenmusic.com/ Rosegarden rounds out 2015 with a new CMake build system and several bug fixes contributed by David Faure of KDE. The new build system preserves the best features of the previous system, while adding out-of-source builds, and the ability to compile with Qt 4 or Qt 5. (Qt 5 builds are functional, but do have some problems. We encourage you to give a Qt 5 build a try and report bugs, but package maintainers and production users should stick with Qt 4 for the time being.) Beyond ironing the kinks out of the new build system, Ted was hard at work sorting out bugs, Yves added a new pop-up notes feature that allows you to include explanatory text inside your compositions, and Michael cobbled together a way to fake acciaccatura, by allowing you to put a tremolo slash on a grace note in order to have LilyPond produce acciaccatura rather than appoggiatura. = Bug Fixes = * Fix minor compile issue affecting several distros (patch backported as 15.10.1 release) * Fix random dropped legato notes with softsynths (patch backported as 15.10.2 release) * Fix crash #1459: Using a null pointer when trying to write MIDI instrument in a LilyPond file from a RG file where instrument is not defined * Fix bug #1457: Repeating segments with volta are always exported to LilyPond unfolded when using multiple voices on the same track * Finish off #1455 involving repeats and LilyPond * Fix LilyPond export crash with very old files that date from when compositions had no verse property * Display the link Id after the label of the linked segment on the composition view. This helps to identify the linked segments (the texture is not always very visible) and to know at which other segments a segment is linked * Add a modified version of examples/lilypond-alternative-endings.rg usable to test #1457 fix * RG_WARNING is now a suitable replacement for std::cerr everywhere it occurs in the code * MidiFile: Simplify zero-length track handling * CMI: Improve recording performance * Fix bug #1458. The LilyPond exporter no longer exports redundant key signatures * Fix bug #1461. The document properties segment summary table is populated correctly * Fix bug #1462. There is no longer a crash when the document properties dialog is open while changing documents, and it is no longer possible to open more than one document properties editor * Same modifications on the configuration dialog as those done on the document properties dialog * Fix Song Position Pointer rounding error (bug #1100) * Fix bug #1463. Composition additional headers no longer broken * Force building all before install * Add memory to text input dialog * Fix bug #1465. Remove the output of "\ottava" in handleStartingPostEvents() in LilyPond export * Fix crashes when closing the configuration dialog or the document configuration dialog with environment variable QT_FATAL_WARNINGS set to 1 * Fix MIDI sync off by 1 issue * LilyPondExporter: fix bug #1466, single note should never be beamed. * Don't export beams on notes that can't actually have beams * Fix #1468: the verse count was not kept up to date * Clean garbage from double click bar selection in notation editor * LilyPondExporter: a rest at the beginning of a beam group shouldn't be beamed, to match the on-screen rendering * HeadersConfigurationPage: don't add empty rows to m_metadata for headers shown above the table. * Don't mark the document as modified every time you print via LilyPond * Turn lilypond autobeam off when "Export beamings" is checked * LilyPondExporter: Grace notes are not beamed, but shouldn't break the beaming group * LilyPondExporter: rework algorithm for exporting groups (beams and tuplets) * Fix bug #1469: Repeat with volta are now correctly export to LilyPond when the last volta is longer than the repeat segment or not synchronous on the different tracks * LilyPond: Fix the wrong detection of a repetition when a segment is linked to some other segment outside of the supposed repeat sequence * Fix resource leak in AlsaDriver code * Use jack_port_get_latency_range() instead of the deprecated jack_port_get_total_latency() * Fix some reports + tune euclidian algo * Fix missing controllers when switching ports (#1374) * Fix Manage Controllers update bug: Changes to controllers are now reflected in the UI when the Manage Controllers dialog is dismissed * Fix SysEx corruption (#1477) * Fix the worst part of #1450 with several improvements to segment canvas mouse handling = New Features = * Add details box to LilyPond export failure dialog, showing you LilyPond errors within Rosegarden
