similar to: git clone failed

(Resending in plain text.) Using git-2.28.0, I can't seem to clone the official repo: ... warning: object c53598453ebdbbd8b8f05eed412484ad7f4d1c26: missingTaggerEntry: invalid format - expected 'tagger' line warning: object 8478c2d69b2a0722957916689f8e3bf0053a7448: missingTaggerEntry: invalid format - expected 'tagger' line warning: object

(Already noting the posts that say this is not available) Are you willing to deal with "non authoritative" answers in your query? If so, you can write some scripts that talk CGI to a commercial music vendor. I use a (no longer available) MP3 tagger called "MP3 Internet Renamer". It would go out and request a web page from the "All Music Guide" (

Is there any good tagger for CentOS 6? -- _ ?v? /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

I'd search freshmeat/sourceforge/cpan before doing anything... there might already be a library or package for general-purpose web-grepping.. If not you can probably use a "HTML to ascii" converter (or some Perl/awk tag strip construct) which will reduce fluff in the pages. I find it easier to throw away data I know I _don't_ want first (though, if I knew regular expressions

I hope I am not too far of topic. I have hacked FLAC support into rip, a command line (perl based) CD ripper/encoder/tagger. http://sourceforge.net/projects/rip/ The maintainer is checking over the patch and should get back to me next week. Shall I: 1. Go away and leave this list alone 2. Come back and tell you if/when the patch is approved 3. Explain what I am on about 4. Send the patch

Hi All, Software patents suck but but unfortunately for speech, MP3 (also still patented until end of next year) also sucks - for html5 audio served to iPhones where Safari doesn't support Ogg Opus and where bandwidth may be limited, AAC is a very attractive option. I have an AAC encoding solution for Linux but I don't have a way to tag them. Anyone know of Linux command-line tagger

Ok so I can use any ID3v2 or v1 tagger (say the perl one) for FLAC files and things will be kosher? I'd LOVE to be able roll my own tagging scheme like you can in Vorbis and I don't mind doing some code either..I wasn't aware that FLAC was able to do that..or at least I didn't userstand how to do that. I guess that is where you register for your own developer ID eh? Josh

Hello all, I'm committing the heinous crime of posting before I've been on a list for very long, and I apologize in advance. I don't know how often this comes up and if it has recently if someone will just point me to an archive where this discussion has already happened, I'll shut up. I've got an MP3 tagger (QTagger) that I released a while back. I'm trying to

Hi! Useful advice, thanks! Actually I had been using foobar2000 to recode, because it just makes it so easy to convert multiple files while keeping the metadata (I confess, I'm a "tagger"). But it's easy to miss some encoder option when being presented some default suggestions in a dialog form... Apart form that I always had the impression that Opus could be quite smart

David K. Gasaway wrote: > Daniel Aleksandersen wrote: >> On Monday 17. September 2007 07:47:19 David K. Gasaway wrote: >>> Even today, I use my own "metadata format" -- essentially a superset of >>> vorbis comments. There is one file per release, even with a multi-disc >>> release. As a final part of the ripping process, I apply this metadata

On Thu, Mar 14, 2002 at 10:26:45AM -0700, Chris Hirsch wrote: > So there are no command line options like in oggenc to do artist and > misc tags? Sure if you've got a solution that I don't have to do from > scratch then post away! :-) the patch is located below. i have already submitted it to the author. http://www.bagu.org/flac.html i have also made a utility to calculate

--- Dax Kelson <dax@gurulabs.com> wrote: > Goals: > > 1. Store meta data > 2. Be able to recreate and burn bit-for-bit accurate audio CDs from > archive. > 3. Be able to "generate" lossy format files (OggVorbis,MP3,etc) with > meta info intact when needed. > 4. One file per song. > 5. Files playable in XMMS and WinAMP3. > > Questions: > Q1. OGG

I'm working on creating a OGG file tagger using BCB6 and I have come across a series of link-errors when attempting to compile: [Linker Error] Unresolved external '_ov_open' referenced from C:\PROJECECT\MAIN.OBJ There one for _ov_comment, _ov_info, and a couple others as well. I thought I'd already included all of the required libraries into the correct file-- and have

--- "Oskar L." <oskar@rbgi.net> wrote: > I am having a lot of problems with tagging FLAC-files. I edited the > tags > in XMMS (in Linux) using the FLAC plugin, version 1.1.o. Playback > worked > fine with that setup, but when I played the files on my other > computer, > again with XMMS, but with version 1.1.1 of the FLAC plugin, the ä and > ö > characters

Adam Rosi-Kessel wrote, on 6/19/2009 3:56 PM: > Conrad Parker wrote, on 6/18/2009 3:15 PM: >> Hopefully at some point the vorbis data in the file becomes valid. >> Perhaps we just need to know the original encoding settings to create >> a new file with valid codebooks and splice them together: oggz-dump -r >> should be ok for that, just take the first 3 packets of the

Just finally getting around to this :-) I've never used abcde...looks like it'll be a winner in my book....just to understand...your patch (which does tagging) is against the original and only FLAC patch that enables abcde to do flac which is v1.9.9 and the newest is 2.0.3? or do I just patch your new patch against 2.03? Yeah I know I should just try it (and I'm sure I will) I

Some suggestions for the recommendations on http://reactor-core.org/ogg-tag-recommendations.html: Add in a table of contents. Please. Rename the title to "Vorbis-style Comment Field Recommendations" (change capitalization to taste) to reflect that FLACs and Speex files could be tagged according to this recommendation. Do note that not just Ogg (or, for that matter, .ogg) files can use

>I don't mind (and approve of) the idea of reusing as much of proven >standards as we can. But putting it in a Vorbis comment will in fact >piss off people who then can't play the file. It's not as much a >qestion of displaying the tag as text (although that is a concern) >it's that most hardware players that only have 10-20kB available for >stream buffering

I mentioned sub-tagging in an earlier post. Here's a more in-depth mail on what i thought of. One of the debates going on here are whether ARTIST is worthy of life. Another is whether the average user will bother filling in the detailed info Jonathan wants. Of course, all tags are optional, but nevertheless we should have a tagging-system that pleases _the_users_, that is, everybody: 1.

heyas- I believe there is a need for a standard vorbis comment field to encode "Total Number of Tracks (on a CD)". Why we need this -------------------- - Existing Vorbis programs already implement this, inconsistently, and hence don't interoperate. These seems the key reason to me. - MP3s include this - Some software (e.g., iTunes) uses this information, e.g., to display