Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disc compression support #1584

Closed
strich opened this issue Jan 28, 2024 · 5 comments
Closed

Disc compression support #1584

strich opened this issue Jan 28, 2024 · 5 comments
Labels
enhancement New feature or request

Comments

@strich
Copy link

strich commented Jan 28, 2024

Feature Request

There have been a few issues raised over the years about providing any kind of compassion in to of the images be it CHD or some other format, and it seemed some consensus was being found but seemingly no further progress and all previous issues locked for comment.
#238
#129

Is there a plan to progress this?

Alternatives

No response

Additional Context

No response

@strich strich added the enhancement New feature or request label Jan 28, 2024
@mborgerson
Copy link
Member

Afaik nobody is working on this feature. There are a number of higher priority tasks. Issue was locked because the conversation was not very productive, and as I mentioned in the comments general chat about the topic is welcome on Discord instead. If you are very motivated and want to work on the feature and suggest a patch, you are welcome to. If you want to chat about it with others, join Discord.

@strich
Copy link
Author

strich commented Jan 29, 2024

Wait why are you pushing discussions off GitHub? You need to be keeping these issues open so others can understand the status of features and potentially contribute. The previous issue you closed was actually reaching consensus and was productive but now no one can help move it along and the whole conversation has to start again in an issue like this.
This is very weird behavior for a repo on GitHub.

Ime5 of the main things that needs determining is whether the maintainers will even accept a CHD solution. Will they?

@brad86m
Copy link

brad86m commented Jul 3, 2024

A simple "We're not implementing the request" would be far better than "maybe, maybe not" each time someone asks. It's a much wanted feature, and not being able to discuss it is not a great look.

@abbotadmin
Copy link

A simple "We're not implementing the request" would be far better than "maybe, maybe not" each time someone asks. It's a much wanted feature, and not being able to discuss it is not a great look.

It's quite clear the maintainer has some bias against CHD support that they don't care to defend as they've done everything they can to close or lock any threads about it. Anyone who would consider wanting to contribute this should probably look at another project to support sadly. :/

@iamdark24
Copy link

A simple "We're not implementing the request" would be far better than "maybe, maybe not" each time someone asks. It's a much wanted feature, and not being able to discuss it is not a great look.

No and maybe are different though. No means it not ever going to be on the radar while maybe means it carries a chance that it could make it to a roadmap. Just because something is a popular request doesn’t mean it’s on the roadmap as there are currently larger issues to investigate. I would love to see progress on audio issues before something like this, but that’s just me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants