[Feature Request] GUI

[Lebon14]

Hi.

Yes, I know. N00bs, including me (also allergic to CLI), needs its GUI. I'm trying to use cyanrip for the first time on a disc that gave me issues and... my head hurt just tagging the files. I hate automatic lookups for anything (and the disc is not in MusicBrainz anyway).

Please consider a GUI, at least for Windows where most common folks are. It also help folks like me that are more visual and less "imagine what I wrote down".

I understand that might not be in immediate plans as I would understand that you'd like to get the basic software running.
As I tried tagging with everything in one line... I got a "01 - Unknown track.flac" file despite having wrote -t 1=title="Unshakeable":...

Thank you for considering.

[cyanreg]

I won't object to this being added. The code is already almost modular to make cyanrip a library, which a GUI application could use.
But I'm far too busy to write one, and I've not got a Windows machine anyway.

Maybe a text file like #58 suggested would be an easier, much faster and simpler to implement for now.

[Lebon14]

Maybe a text file like #58 suggested would be an easier, much faster and simpler to implement for now.

It would help tremendously, yes.
Hopefully someone comes along with a Windows machine (and Mac) can help you make it.
In fact, all the arguments I passed absolutely failed. Shows how much I suck at CLI. -_- (Now kudos for not making the command fail outright though lol)

[TomTinking]

My 10p. This CLi works great. All other rippers failed me. I use MB Picard for tagging and storing my music.
So this tool grabs CDs in a format, with enough info that then I use Picard to do the heavy lifting, additional tagging etc work flow.
I just start it from a folder on my PC with ' cyanrip -s 0 -Q' then I pick up the results in Picard which has plenty UI to do your tagging and renaming.
So Gui not needed. IMO

[Lebon14]

So Gui not needed. IMO

That's because you are able to remember command-lines that can cover a whole screen. If you don't want automatic MusicBrainz lookup like me (f*** auto-tagging) and want to do the basic tagging at ripping time (so it shows up in the log and CUE files), you are looking at a command-line that's almost novel level. Not only that, you might make mistake in the syntax and, since I've last touched it, cyanrip didn't even throw an error and all files were untagged despite my best efforts.

Also, it would significantly open up the usabilility (as I'm allergic to CLI) and for those that look for an alternative to closed-source EAC or paid-software like dbPowerAmp CD Ripper (does not make logs that private trackers like) that accurately extract CDs. I don't want to be ripping CDs to become a chore and bang my head why the f*** my log score is 50% (if you are in private trackers, you know what that means).

This opinion is incredibly self-centered just because you don't need it that the project shouldn't have it. There are plenty of examples of software that both have a CLI and GUI versions and you are just free to use either (or both). Yes, it needs dev time and complexity but, at the same time, that's what open source projects are for: so other people can chime in and, if one per miracle understands the plight of GUI lovers like me (I'm a visual type), that they're free to make a GUI. I'm no developper - so I can't do that.

Regardless, even if cyanrip had a GUI right now - or at least a much easier way to feed data into it without dealing with a novel length argument - it still has issues with gap handling (as I understand it) and error correction. So, I'm staying on EAC for the time being (man, I just wish XLD had a Windows port...)

[TomTinking]

Think you need to calm down a little sir.

1. Its an opinion - and I am as you are entitled to it.
2. Its open source provided for free.. and its a great little tool, that's how I see it. Not a complete solution.
3. If you are allergic to CLI, don't freaking use a tool that's built that way day 1.. ?
4. Its my opinion, I'll leave it to the developer to figure out what he/she wants to do.
5. I built a simple bash script around this tool that suited my needs with 4 menu options. First time I built one actually not really much of a developer, i just figure stuff out. Have done for 30 years ...