601

(2 replies, posted in General)

I'm not sure. Any loose networking cables?

602

(8 replies, posted in General)

Thanks, I'll look into it a little more when I get some time. They might not be the same process. I believe Finder calls openFile(s), whereas the dock icon calls a completely different delegate method, so it may be possible to fix one without it affecting the other.

604

(1 replies, posted in Squashed Bugs)

605

(8 replies, posted in General)

I believe this is proper OS X behavior. When clicking on the dock icon, it will make the application active, but will not unminimize the window for you.

606

(7 replies, posted in Development)

I work on Cog rather sporadically. I do work on it when I can (and feel) like it. The result being a month-long gap of inactivity followed by a month of me working on Cog every free moment I get.

Cog's development has been getting a little more organized with the last release. The feature wishlist helped a lot with that. I'd like to continue this trend and organize things a bit better.

I've been thinking about Cog's development cycle. It's a bit long, and I'd rather it not be a year for 0.07 to come out. The main reason for the length is that I like to pack in enough new stuff to make the release warranted, and the fact that making a release is quite a bit of work in itself; bugs should be minimal, localizations should be in place, things can't be half-complete...all that fun stuff.

So, I've been thinking of trying for more frequent releases. The downside is less features per release, but I think that's ok. Instead of waiting 1 year for butter churning, coffee making, self-awareness, and the like, you wait a month for just coffee making. 0.07 had quite a few new features, maybe too many.

So, basically, I'd need to cut down the feature list for 0.07 to something more manageable. I'm thinking code clean up (for playback and file drawer mainly), cue sheet support, multi-track support (containers with more than one track), MOD support (along with all it's cousins), and a couple of new preferences (the clear playlist/start playing ones). Maybe less?

What do you think? Discussion could still be carried on for the other features, similar to the 0.07 wishlist (but not really relegated to a wishlist anymore, since we have a separate forum). It would be nice to not change the interface during a release too, because that spares me from the pain of localizations smile

Like I said, it depends on how easy it is to write AudioUnits. I have yet to look into it. Effects are likely not a part of 0.07.

It's the same reason I don't use Quicktime Components for my decoder plugins. Quicktime components are a major pain to write.

I'd like Cog to be easy to extend, which includes using Cocoa for the plugin APIs.

If you could email me the tests, I can check it out: cog (at) vspader dot com

I'm in the same situation. I have audio files spread across a few different machines that are all networked together.

There was a suggestion to make clicking on the header for the file drawer would toggle between some pre-selected directories. I like that idea, and I might go with that. I don't know if it's a 0.07 thing or not though (Check the list smile).

As far as artwork goes, its on the list too. There likely wont be a fullscreen mode at the moment though.

The chain is currently:
source->decoder->converter->output

Both converter and output are CoreAudio. I have looked into AudioUnits yes, but I don't know if I want to make them a replacement for effects plugins or if there will be an seperate effects plugin system and have some kind of AudioUnit effects plugin that can load audio units.

Quicktime isn't used anywhere at the moment. In the future, I plan on making a decoder that used the audio extraction Quicktime API's. I don't plan on quicktime becoming an integral part of Cog.

I've been thinking about it a little. I haven't looked into how easy it is to create audio unit effects yet. One of the reasons Cog has input plugins is becasue the Quicktime component system has a notoriously bad API.

613

(3 replies, posted in Features)

24bit flac should be working. If it isn't, that's a bug.

614

(24 replies, posted in Squashed Bugs)

That is abnormally high. Definitely sounds like a memory leak. Any specific file types you were using?

Well, "deleting old playlist entries on program start" actually wasn't.

616

(22 replies, posted in Archives)

617

(18 replies, posted in Features)

618

(5 replies, posted in Archives)

Thanks. It's added now.

Regarding the RSS thing, you could technically use the appcast to get a feed about releases, but for news it'll be a bit before I have time to develop anything for the website.

It's possible there was an m3u or pls in the directory that Cog picked up on.

Haha. Good idea. smile

621

(2 replies, posted in Archives)

Done. I'll start using it by moving this post smile

622

(7 replies, posted in Features)

I was considering ripping it out for the release, but figured something is better than nothing.

Hmm...any ideas on how an error message would manifest? I'd prefer to avoid alerts, and it'd be nice to have something that could be used for other errors too.

623

(45 replies, posted in Development)

I hate skins.
Still, I've been thinking of a way to support interface plugins. It's possible. I did a little work for the lamip project on this getting the basic stuff up and running where it'd pick the interface plugin to load on startup. It's definitely a down-the-road thing though.

Any updates on this? I'm assuming the nightly fixed it?

625

(7 replies, posted in Features)

Well, reading the mime-types is basically it. Dunno if it's a 0.07 thing or not though. It's a close call. If anything, it's definitely 0.08.