26

(108 replies, posted in Development)

27

(10 replies, posted in Development)

28

(4 replies, posted in Bugs)

In a few days, it'll be 2 years since 0.07's release, December 23, 2007. (Time flies, eh?)

Of course, many of use have been using the 0.08 nightly builds (for Leopard or newer) ever since they first came out.


However, I don't think a huge majority of the current Cog users are using them, unless:

-they felt adventurous and clicked "Development" instead of "Downloads" (the latter being what most typical users looking to try software would click)

-they passed by the forums and happened to stumble on one of the many threads where I shamelessly take every opportunity to tell people to try the 0.08 nightlies tongue


So yeah, for anybody who's using Leopard or newer, if they aren't using the 0.08 builds, I feel that they're really missing out on the past two years of awesome additions and improvements (courtesy of vspader and other contributors).


As such, I wanna suggest putting out a 0.08 'beta.'

Well, it may be nothing more than one of the recent nightly builds with the label 'beta,' but I feel this would make a big difference, especially if:

-the beta is featured prominently on the Cog site (and I think people are more likely to try out a beta rather than a 'scary' developmental/nightly build)

-the beta replaces 0.07 on all those software download sites (MacUpdate, VersionTracker, Apple Downloads, etc.)


I think the builds are pretty stable to be usable. (IMO, they have for a long time.)

I would just rather than when new users try out Cog, they get the best possible experience out of it, not the 2-year-old experience.


What dya think?

31

(1 replies, posted in Help)

32

(2 replies, posted in Help)

There's currently no way to edit the song metadata (such as ID3 tags for MP3s).

There have been suggestions to add this functionality, a while back.

And yes, in-line metadata editing would certainly be neat.

33

(19 replies, posted in General)

Ain't getting rid of iTunes or any of Apple's default apps problematic when you use Software Update?

34

(2 replies, posted in Help)

35

(8 replies, posted in Development)

Bump.


I still think this is a good idea, especially since development seems to be rather slow in recent months.


How about it, vspader? (if you're alive at all)

36

(10 replies, posted in General)

37

(108 replies, posted in Development)

38

(20 replies, posted in Features)

^

Hmm...

Yeah, would Highly Experimental be a viable option?

The HE plugin is what I used in Winamp to play PSF/miniPSF/PSF2/miniPSF2 files.

40

(6 replies, posted in Features)

41

(108 replies, posted in Development)

42

(108 replies, posted in Development)

43

(2 replies, posted in Bugs)

Well, as you said, it'd be too much to check every file in the playlist all the time.

I do believe though that when a song is played, it should be checked, so that Cog does not display erroneous information even as the user can clearly see the contrary. (i.e., song marked as missing when it is in fact available, or song not marked as missing when it is in fact missing)

44

(2 replies, posted in Bugs)

45

(2 replies, posted in Bugs)

46

(2 replies, posted in Bugs)

If a song is recognized as missing by Cog, it will be marked with an "X." Also, when a song is missing, there will be no Growl notification when Cog attempts to play it (and then skip it).


Bugs:

1) Songs that are not found will not immediately be marked as missing.

Say you add a file to Cog then delete that file. Then play that song in the playlist. It will be skipped, but it will not be marked with an "X". (And as it attempts to play it, there will still be a Growl notification.)

Only after a relaunch will Cog mark it with an "X".


2) Songs that were marked as missing will remain marked as missing even if found.

If a song is marked as missing, even if it is then made available again, it will still be marked as missing. (And there will be no Growl notification.)

Once again, it will require a relaunch for Cog to not see them as missing.

48

(6 replies, posted in Features)

Bump.

The default length of 2:30 still somewhat bugs me.

Every once in a while, I get a song that gets cut off during its 2nd loop, or worse, get cut off during its 1st loop.

I think 3:30-4:00 would be a bit better.

in r1919's changelog:
"Fix Growl so it only shows up on non-error tracks and display album art in the notification."'


But I still get a Growl notification even when a file isn't found.

It probably should be mentioned on the Development page that the nightly builds require 10.5 Leopard.

Ideally, there would be an explanation as to what's the difference between the Stable, Unstable and Nightly builds.