Looking for maintainers #82
Comments
|
Mathew,
I would be willing to oversee the project if you like, I do have a separate branch I maintain, with additional components like an AAC Encoder we paid for directly to IAN (Bass Developer). My company is in contact and does contract IAN for additions to his engine.
Dustin Bond
Senior Application Developer
RCS / IHeartMedia
www.rcsworks.com<http://www.rcsworks.com>
www.iheartmedia.com
From: Mathew Sachin <[email protected]>
Sent: Monday, July 27, 2020 9:30 PM
To: ManagedBass/ManagedBass <[email protected]>
Cc: Dustin Bond <[email protected]>; Mention <[email protected]>
Subject: [ManagedBass/ManagedBass] Looking for maintainers (#82)
The main use for ManagedBass for me was within a screen recording program I made. Eventually, it shifted to use NAudio to be completely open-source and because it had to run only on Windows. BASS is really great for multi-platform use.
But, I had many bad experiences (not related to BASS) in that screen recording program like people just blatantly copying it and selling it as their own on Microsoft Store and reporting those apps doesn't help. As a result, I've kind of grown frustrated of Windows and .NET as platforms to develop for and I'm shifting to other platforms like Android.
I would like to leave the project in the hands of people who continue to use it actively. Since ManagedBass is just a wrapper library, not much of an effort should be required for maintenance.
Particularly, I'd like if people who have already contributed to the repo could take up the ownership like @olitee<https://github.com/olitee> @RCSDustinBond<https://github.com/RCSDustinBond>
and the folks from osu!.
I don't really feel good leaving my projects like this, but, it's not much use to keep it stale when I'm not motivated enough to work on it 😢.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#82>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIW3H6ZE4W67HLUNJ3UTBIDR5ZH5HANCNFSM4PKCSGGQ>.
|
|
@RCSDustinBond That's really nice to hear. I have sent you an invite to add as a Member to the ManagedBass GitHub organization. After you accept, I'll convert you to an Owner. |
|
@RCSDustinBond I think NuGet has changed how permissions work for organizations a bit. To give you access to the NuGet packages, I need to know your NuGet username. |
|
Hi @MathewSachin, thanks for the callout. I think @RCSDustinBond is clearly better positioned to maintain this library day-to-day. My interest in this library is limited to a number of personal audio playback projects, that often need to sit on the back burner while I do the day job. Happy to stay involved though. |
|
@MathewSachin - sorry to hear about your bad experiences. Thank you for making this project, and for all of the support you provided me in the early days. I know I haven't been involved in a while, since my project basically reached steady-state and didn't require any further development or updates. I know my project would not have been possible with out you and your efforts. Be well, and feel free to reach out if you ever need anything. |
|
@MathewSachin - I created a new account on Nuget, Dustin.Bond ([email protected]) ... |
|
What's a status of this issue? |
|
@MathewSachin , @DustinBond - Is this project still being maintained? Having some issues with a device, could really use a bit of assistance. |
|
We use ManagedBass for Clone Hero as well, so if needed could also potentially help out with maintenance. I've just submitted a pr #87 for a bug i found today while converting some of our sound effects to use Opus. |
|
Hi @DustinBond / @MathewSachin, Do you have any plans for updating the nuget packages for this library? I'd be happy to assist in setting up an automated build/release process if you want? I'm conscious that the current v3.0.0 nuget packages have some versioning issues, and have not been updated for almost 18 months - and that ParkSquare has recently forked this repo as 'BassSharp' (https://github.com/parksquare/BassSharp) to fix this issue. While I'm tempted to switch to using the BassSharp nuget packages for my own projects, I feel it makes sense the solve the problem at the source - particularly since this repo has an established userbase and is relatively active. Any thoughts? :) |
|
Automated releases would be great! I personally didn't have any important projects depending on ManagedBass/BASS now, so the packages were left stale... |
|
I've added a GitHub Actions secret: |
|
As a heads up when releasing a new version: #93 may be regressing behaviour (we can't compile for iOS currently). Haven't investigated in detail yet. |
Would it be possible to add package(s) that also include the native bass.dll and/or other required libraries, similar to how Emgu.CV packages the required openCV libraries for various operating systems? I think having the runtimes avaialable via NuGet as well would be incredibly useful. |
|
@d8ahazard I can think of a number of pros and cons for this approach. The most obvious problem being how to intelligently handle switching between 32/64 bit versions of the libraries at compile time. I'd also have to check with Un4Seen - as I'm pretty sure the licencing for those DLLs doesn't allow us to distribute them as part of a library. Their licence specifically states: "Please note the products must be end-user products, eg. not components But I could reach out to Ian in the forums there for clarification. |
|
I've sent him an invite 👍 |
|
@DustinBond @MathewSachin Thanks for the invite. I've setup a pair of github Actions: One to act as a build-test (replacing appveyor), and the other to build, package and publish the nuget packages. All of this is currently on I'm thinking the best way of handling the nuget packages will be via the repository's Releases feature. So creating a release with a tag using semantic versioning (e.g. v.3.0.1, etc) will trigger the action to create and publish the nuget packages. This approach also supports prerelease versions (e.g. v3.0.1-prerelease, or v3.0.1-beta) which could be handy. It gives us complete control over the releases - rather than simply firing out a new package when the master branch changes. Are you both OK with that approach? |
|
Yes, sounds perfect to me. |
Yeah, that would be awesome. Heck, maybe Un4Seen would be open to creating nuget package(s) directly...which would alleviate any issues with licensing. In regards to handling the binaries at runtime...I think the solution would be to just emulate what EMGU.CV is doing for their runtime libraries, which handles this exact situation: |
|
@d8ahazard I like this idea, but I think it needs opening up for investigation and discussion. Could you create a new issue for this, as it's a little lost in this maintainers thread. |
|
For those interested, v3.1.0 of the ManagedBass nuget packages have now been released: |
|
I'm not sure that including the unmanaged DLLs is a good idea, because you do not know which DLLs the application wants to include or not. Here's my solution, I created a project with all the DLLs, and I simply reference the BassDlls project to get all the DLLs for the desired platform. There's another BassEncDlls project for when I need to encode. |
The main use for ManagedBass for me was within a screen recording program I made. Eventually, it shifted to use NAudio to be completely open-source and because it had to run only on Windows. BASS is really great for multi-platform use.
But, I had many bad experiences (not related to BASS) in that screen recording program like people just blatantly copying it and selling it as their own on Microsoft Store and reporting those apps doesn't help. As a result, I've kind of grown frustrated of Windows and .NET as platforms to develop for and I'm shifting to other platforms like Android.
I would like to leave the project in the hands of people who continue to use it actively. Since ManagedBass is just a wrapper library, not much of an effort should be required for maintenance.
Particularly, I'd like if people who have already contributed to the repo could take up the ownership like @olitee @RCSDustinBond
and the folks from osu!.
I don't really feel good leaving my projects like this, but, it's not much use to keep it stale when I'm not motivated enough to work on it 😢.
The text was updated successfully, but these errors were encountered: