Ok, got it. Qt requires a display of course... this helps: export QT_QPA_PLATFORM=offscreen
R On Wed, 1 Feb 2023 at 15:47, Richard Bown <r...@xyglo.com> wrote: > Thanks all for the feedback - very useful and it's been a nice trip down > memory lane hearing thoughts and opinions and putting this presentation > together. > > While preparing I've also been trying to get a code coverage number out of > Rosegarden - however when I try to 'make test' I get all ten tests failing. > Has anyone (Ted perhaps?) run these recently and got passing results? I'm > wondering if it's something to do with the build config as I've been > playing about with CMakeLists.txt (in my own fork) and I'm doing this under > Ubuntu/Github Actions rather than locally. > > Thanks, > Richard > > On Sun, 22 Jan 2023 at 03:00, <r...@hydrophones.com> wrote: > >> Hi all, >> >> My company has been using Rosegarden almost since the beginning. In the >> early days we helped with various aspects of its development as well as to >> Linux sound (ALSA, Jack, Netjack) in general. >> >> Lately we haven't been compiling and running the most recent version as >> the last few times we tried doing that we hit "dependency hell". Flatpak >> versions would definitely help keep Linux users up to date. That and >> keeping dependencies down or perhaps including them with the source code. >> >> We run several Linux clusters, all centered around powerful (thousands of >> cores) machines running various semi-recent versions of Pop!_OS Linux. The >> smaller older Linux (non Pop!_OS) machines are mostly in the clusters >> providing legacy audio and media creation interfaces. The clusters can be >> coupled for even more computing and channel counts across multiple rooms >> should that be necessary. >> >> Our present workflow pipeline is now mostly starting with AI assisted >> composition (which may have several stages). Once we have a few candidate >> compositions (as MIDI files) we bring them into Rosegarden for >> orchestration and perhaps some rearrangement. If we are going for a full >> multichannel version we'll even record individual tracks in Rosegarden. >> >> The recorded (as 24 bit 88.2 kHz flac) files are usually then brought into >> Audacity for minor editing, effects, and mixing. Those outputs (stereo, >> 5.1, and 7.1) are supplied to the final customers. Multiplexing in a >> standard format with video is normally done with FFMPEG at the command >> line level as most video editors do not do this consistently correctly >> (i.e. prone to reversions). >> >> The present version of Rosegarden does pretty much everything we need in >> the context of what we use it for. We are thankful to all the developers >> and maintainers. >> >> You can hear some examples of what we have done on our companies websites: >> >> http://finevenuemusic.com >> >> and >> >> http://www.hydrophones.com >> >> There is a directory with a variety of sound and video examples: >> >> http://www.hydrophones.com/public >> >> Some of that stuff dates from way back when electronic music synthesis was >> still a bit of a novelty. Most of the sound files are open standard .ogg >> files which are known to play on open standard players and Android >> devices. >> >> The latest Chromium browsers can also play all the files. If you are set >> up for Surround Sound there are some multichannel immersive audio and >> video files in there also (suffixes such as ac3 and 7p1aac.mp4). The >> Chromium browser can play those also as can some Internet connected "Home >> Theatre" systems. >> >> Moving onto more recent material that we are still shopping around we >> have in >> subdirectory: >> >> http://www.hydrophones.com/public/EOY2022-Experiments/ >> >> two other subdirectories: >> >> http://www.hydrophones.com/public/EOY2022-Experiments/New-Analog-Patches/ >> >> and >> >> http://www.hydrophones.com/public/EOY2022-Experiments/RTX1-sketch-series/ >> >> All works on those sites are: >> >> >> >> Attribution-NonCommercial >> CC BY-NC >> >> Enjoy! >> >> Regards, >> >> Richard A. Marschall, Ph.D. >> >> >> >> >> >> > Send Rosegarden-devel mailing list submissions to >> > rosegarden-devel@lists.sourceforge.net >> > To subscribe or unsubscribe via the World Wide Web, visit >> > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel >> > or, via email, send a message with subject or body 'help' to >> > rosegarden-devel-requ...@lists.sourceforge.net >> > You can reach the person managing the list at >> > rosegarden-devel-ow...@lists.sourceforge.net >> > When replying, please edit your Subject line so it is more specific than >> "Re: Contents of Rosegarden-devel digest..." >> > Today's Topics: >> > 1. Re: rosegarden presentation at FOSDEM (mark_at_yahoo) >> > ---------------------------------------------------------------------- >> Message: 1 >> > Date: Fri, 20 Jan 2023 14:33:36 -0800 >> > From: mark_at_yahoo <markr...@yahoo.com> >> > To: rosegarden-devel@lists.sourceforge.net >> > Subject: Re: [Rosegarden-devel] rosegarden presentation at FOSDEM >> Message-ID: <45956e4f-9163-5496-893c-e04d21a4f...@yahoo.com> >> > Content-Type: text/plain; charset=utf-8; format=flowed >> > On 1/12/23 2:45 AM, Richard Bown wrote: >> >> Consequently, I am reaching out to see if there are any stories or >> feelings >> >> you have around using and/or contributing to Rosegarden that you feel >> are >> >> vital and worth sharing. I would love to hear them. Feel free to email >> me >> >> if you don't want to share on the list. >> > I haven't seen any replies on this list to your post -- hopefully you >> received some privately and they were helpful in preparing your >> > presentation. In any case, I'm going to add my opinions (publicly) here. >> I'd be very interested in hearing your analysis of the issues >> > surrounding open source software, particularly Rosegarden with its very >> unique 30 year history. I'm unfortunately not in a position to travel 1/3 >> the way around the globe to attend FOSDEM (though it would make a nice >> vacation!), so if your session becomes available online after the fact >> please post any links to it here. >> > The current problem with Rosegarden -- and I do claim it is a problem -- >> is that development contributions have slowed to a crawl. Not counting me >> (and it's debatable whether I count) there are only a handful of >> (semi-)active developers. In addition, Ted is the single point gating >> decisions on if and when merge requests make it into the codebase, and the >> amount of time and energy he can devote to that Herculean task is limited >> -- understandably so given his long history with and immense contributions >> to the project. Maybe you could "come out of retirement" and lend a hand. >> ;) ;) ;) >> > None of this matters if one considers Rosegarden to be feature complete >> and its internal architecture and implementation without need of >> improvement. I respectfully disagree on both points. But, yes, if that's >> the conclusion then it's appropriate that Rosegarden "ride off into the >> sunset" with only occasional/minor bug fixes and maintenance releases. (In >> that regard Ted has done an exemplary job ensuring the code is stable and >> crash-free.) >> > The "elephant in the room" here is Musescore. It's a very different kind >> of open-source project, with (as I understand it) a full-time paid >> professional staff and a large number of additional voluntary >> > contributors. In many ways I don't think open-source projects >> > can/do/should compete with each other. But, again in my estimation, >> Musescore has moved far beyond Rosegarden, and consequently has a user >> base that's orders of magnitude larger. Yes, the fact that it's >> > cross-platform, particularly to the Mac (music production is Apple's >> final monopoly, having lost desktop publishing and photo editing a long >> time ago) is a large factor in that. >> > What does that have to do with the current subject? Only in relation to >> my claim that if Rosegarden stays in stasis, its use in and benefits to >> the community will predictably dwindle over time. That's what I perceive >> is happening now: There's a small group of active users, and Rosegarden >> exists as kind of a "cosa nostra"/"our thing"/in-group club for them. >> Which would be fine except that I think it has a lot more to offer, to >> more people, than that. >> > I posted here (and you replied on the thread) regarding my fork of the >> project. I refer back to that now as my "story and feelings" for >> possible inclusion as a small datapoint in your talk. In any case, I hope >> things go well at the conference, and again ask for a link if/when your >> presentation becomes virtually available. >> > P.S.: I have an upcoming bug fix and new features commit to the fork >> nearing completion, and (sigh!) another semi-major new feature planned >> after that. Someday I'm going to get off this merry-go-round. ;) >> ------------------------------ >> > ------------------------------ >> > Subject: Digest Footer >> > _______________________________________________ >> > Rosegarden-devel mailing list >> > Rosegarden-devel@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel >> > ------------------------------ >> > End of Rosegarden-devel Digest, Vol 169, Issue 2 >> > ************************************************ >> >> >> >> >> >> >> >> >> _______________________________________________ >> Rosegarden-devel mailing list >> Rosegarden-devel@lists.sourceforge.net - use the link below to >> unsubscribe >> https://lists.sourceforge.net/lists/listinfo/rosegarden-devel >> >
_______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
