1

(1 replies, posted in General)

Works in Sierra as well, and I think I used it in Mavericks a bit.

Not much to add but: hear hear!

3

(30 replies, posted in Development)

Really grateful for this reanimation! I finally updated to a MacBook Pro a few weeks ago, and one of my worries was that I'd have to find a new audio player.  It's great that such a terrific program has been rescued from being totally moribund.  (That's something that happens far too often -- it's been over a decade but I still remember SoundApp, and how the developer of that great little audio player abandoned it without any explanation.)

4

(1 replies, posted in Development)

I should've written this long ago, but: I agree!

I actually think this is a great idea, though since Cog hasn't seen any real development in months now (and no release in over two years), I don't know how much hope there is to see it implemented.  If I had any programming skills, I'd try, but...

6

(1 replies, posted in Help)

7

(10 replies, posted in Development)

I have to agree with Remain.  It's distinctively depressing to periodically go to the site for a well-loved app, and see no updates for years at a time.  (I remember doing that a decade ago with SoundApp, Cog's spiritual ancestor of sorts.)  The way the Cog site looks right now, it's easy to come away with the impression of yet another dead/abandoned project.

Even a small sign of life makes a big difference, and given how much has been done on 0.08, having a beta release would help to "keep the faith".  It might even bring in developers who can help keep things going, fix bugs, etc. until you have more time.

8

(2 replies, posted in Bugs)

Here's an excerpt from the log output, by the way:

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000008

Thread 0 Crashed:
0   ...rcompany.yourcocoaframework     0x01c142a4 gme_track_count + 0
1   ...yourcompany.yourcocoabundle     0x00634dcc +[GameContainer urlsForContainerURL:] + 132
2   org.cogx.cog                       0x00019f20 -[PlaylistLoader insertURLs:atIndex:sort:] + 800
3   org.cogx.cog                       0x0000391c -[PlaylistController tableView:acceptDrop:row:dropOperation:] + 560
4   com.apple.AppKit                   0x93b92870 -[NSTableView performDragOperation:] + 160
5   com.apple.AppKit                   0x939fef14 NSCoreDragReceiveProc + 864
6   com.apple.HIServices               0x9185bde8 DoDropMessage + 96
7   com.apple.HIServices               0x9185d28c CoreDragMessageHandler + 1332
8   com.apple.CoreFoundation           0x90826000 __CFMessagePortPerform + 304
9   com.apple.CoreFoundation           0x907ec568 __CFRunLoopDoSource1 + 152
10  com.apple.CoreFoundation           0x907dec80 __CFRunLoopRun + 1556
11  com.apple.CoreFoundation           0x907de2b0 CFRunLoopRunSpecific + 268
12  com.apple.HIToolbox                0x932bbb20 RunCurrentEventLoopInMode + 264
13  com.apple.HIToolbox                0x932bb1b4 ReceiveNextEventCommon + 380
14  com.apple.HIToolbox                0x932bb020 BlockUntilNextEventMatchingListInMode + 96
15  com.apple.AppKit                   0x937a0734 _DPSNextEvent + 384
16  com.apple.AppKit                   0x937a03f8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
17  com.apple.AppKit                   0x9379c93c -[NSApplication run] + 472
18  com.apple.AppKit                   0x9388d458 NSApplicationMain + 452
19  org.cogx.cog                       0x00002564 _start + 760
20  org.cogx.cog                       0x00002268 start + 48

9

(2 replies, posted in Bugs)

10

(3 replies, posted in Features)

12

(1 replies, posted in Bugs)

I have a set of MP3s (encoded by iTunes 1.1, I believe) whose tags Cog won't read, though other programs will (iTunes, MacAmp Lite).  Opening one of them up in a hex editor, I noticed that the header is much longer than in other MP3s encoded with the same program:

ID3......zTENC.......iTunes v1.1COM ...h...engiTunNORM. 00000223 000001AD 00000CC1 00000974 0003D0D5 0003D0D5 000070D5 0000797B 0000EA77 0003D090.TIT2.......Fade Into You.TALB.......So Tonight That I Might See.TRCK.......1/10.TYER.......1993.COMM...1...eng.Mazzy Star is: David Roback & Hope Sandoval.TPE1.......Mazzy Star

By contrast, here are two that do work:

ID3......"TEN....iTunes v1.1TT2....LentoTP1....Henryk G.reckiTAL..,.Symphony No. 3 (Jerzy Swoboda/Katowice SPO)TRK....1/3.
ID3......]TT2....One Of These DaysTP1....Pink FloydTAL....MeddleTCO....(17)TEN....iTunes v1.1TRK....1/6TYE....1971

Is it the additional junk in the header that's causing the problem?  If so, can Cog handle it more gracefully?

I'm still using 0.07r909, but unless there's been a change in the tag-reading code, this problem should apply to 0.08/Leopard too.

Actually, Drayon, I use audio-manipulation techniques all the time in my listening.  For example, I sometimes get recordings that are going at the wrong speed -- concert recordings, or my dad's old vinyl transfers before he adjusted the speed on his turntable -- and it's nice to be able to adjust that in real time, on the fly, without having to do a proper speed correction.  Another thing I like to do is sum tracks to out-of-phase mono, aka "karaoke mode", to see what hidden layers can be revealed in recordings I otherwise know well.  And I EQ stuff all the time, given that I listen to many recordings whose fidelity leaves a lot to be desired.  (All these functions are also useful for transcription purposes, too.)

Since I have a lot of stuff in FLAC, doing any of that in Logic or iTunes is out, not to mention the fact that the former takes aeons to boot and the latter is horrendous these days.  I've been using MacAmp Lite, which has all the functionality I mentioned above, but that's an old and mildly unstable program and I don't know if it even works with Leopard.  Audacity is buggy, and more importantly it's not playlist-based -- it has to import everything, which is annoying if you just want to quickly try a few things out.

I'd far rather use Cog for these tasks, if it were possible to do so without adding bloat -- and I get the impression that the amount of code needed to get Cog to interface with Audio Units would be relatively small, because you're not implementing that functionality yourself, just working with an already-existing API.

FWIW, this is coming from a recording engineer and classical musician/composer, and someone who thinks that "end users" are entirely free to "mutilate someone else's music" (!) however they want -- including mine!  I'm kind of bemused by your reverence for the recording/mixing/mastering process, as if end-user interference were a blasphemous idea.

Having seen the inner workings of that process, I assure you that these things aren't handed down on golden tablets from on high, and there have been some terrible decisions made in those booths, more than once.  (Too bad there isn't an "un-limiter/compressor" plug-in.)

No, it can be a lot of fun to do potentially-atrocious things to a recording, and occasionally I've come up with something transformative and beautiful, just by messing around with a half-dozen tracks in all kinds of ways.

Having said all that, I agree that there are higher priorities for Cog right now -- in particular, getting 0.08 out the door.  But I wouldn't pooh-pooh the idea of Audio Units;  assuming it doesn't slow Cog down, it only makes it a more valuable tool, specifically because it allows the end-user to use it in unanticipatable and surprising ways.

14

(2 replies, posted in Help)

This is only a guess, but it might have something to do with the fact that AIFF tags aren't completely standardized in the way that MP3 tags are.  I know that iTunes uses them, but I'm not sure whether it's using some weird-ish, non-standard format.  I suspect Cog may not support AIFF tags -- it's not mentioned on the features page.

One workaround would be to encode to FLAC rather than AIFF.  This format takes up less space (without sacrificing quality), but has a well-supported tagging system that's fully supported by Cog (and Max).  The only downside I can think of is that the iPod doesn't support FLAC, so you'd have to re-encode them as AIFF, WAV, or Apple Lossless for hi-fi portable listening.

15

(5 replies, posted in Development)

Fantastic, thanks so much!!  I've just downloaded the source from SVN and am building it now.  I'm looking forward to checking it out.

I'm particularly happy about this as I spent the better part of the last day or so mucking around with the code to try and implement the "Undo" function, and got absolutely nowhere.  The good news, however, is that it gave me a reason to get familiar with Subversion and XCode, so at least now I know how to check out and build the code.  Or at least I think I do:

svn co https://cogosx.svn.sourceforge.net/svnroot/cogosx/branches/cog-0.07/cog/ -r908

And then you just open up Cog.xcodeproj in Xcode and tell it to build, with the results showing up in /cog/build/Release.  Is that right?

EDIT:  Well, it must be right, because it worked!  The only funky thing I noticed is that when you undo a deletion, the track number ("#") gets messed up -- sometimes it shows up as zero, sometimes you get two of the same one.  But that's extremely minor, and goes away once you reboot Cog, or if you move the track in question to a different order in the playlist.

Thanks again, this'll be a great help.

I'm still hoping that some intrepid third party will backport some of the new features. (Whatever happened to Andre R., anyway?)

Really, the only things that are sorely needed are "Undo" and a working shuffle system (though 0.08 doesn't yet have that either, right?).  Without them, especially the latter, 0.07 feels sort of broken.

(I keep meaning to try to come to grips with the code so that I might work on this stuff myself, but it's a little overwhelming, given that I've never done any serious programming.)

18

(18 replies, posted in Features)

19

(18 replies, posted in Features)

Anything you can do would certainly be appreciated!

20

(18 replies, posted in Features)

21

(18 replies, posted in Features)

Yikes, I don't think so -- these are commercially sold discs by indie bands, and I'd rather not ruin them, visually speaking.

22

(18 replies, posted in Features)

23

(5 replies, posted in Bugs)

I hope this bug gets fixed soon, and that the fix gets backported to 0.07, as it's kind of a dealbreaker for many users.  After all, being able to load your playlist up with a thousand songs and get true shuffle play is one of the main reasons we use audio players to begin with, right?

FWIW, I get bitten by this bug a lot.

25

(15 replies, posted in Features)