326

(98 replies, posted in Development)

Nice, separators are in r648. I replaced the spaces with separators to squeeze a few more pixels to be useful. ;p



Another thing about the volume slider...

The volume now goes from 0% to around 400%.

Maybe it's just me, but isn't 400% a bit... overkill? I think 0-200% would make more sense for most people out there.

Also, the "snap" area around 100% volume is a little too big.

That combined with the fact that the range is 0-400% results in the following:

1) It's very difficult to adjust the volume in the "normal" range of 0-100% because the length of that range is now extremely short on the slider.

2) It's impossible to set the volume to anything between around 60% and 140% due to the "snap" area and the short length.

327

(10 replies, posted in Development)

328

(5 replies, posted in Features)

You usually can't "save" in other formats in most audio players. ("Save" probably isn't the right word; it's more likely "convert" or "export.")

You usually need audio editing software (such as Audacity), though iTunes happens to be able to convert from the formats it can play to MP3.


An M3U file is nothing more than a text file with a list of the location and filename of the songs.

329

(5 replies, posted in Features)

331

(98 replies, posted in Development)

Yeah, the dotted line.

I don't think it's been "discontinued," as it's still in most Apple apps. (One exception would be Safari, which does not even have space and flexible space.)

332

(98 replies, posted in Development)

Say, is there a reason that separators aren't available in the toolbar customization sheet?

I thought they came with standard toolbars by default.

M3U, you say?

That's what Winamp does, I believe.

#EXTM3U
#EXTINF:180,Artist Name - Song Name 1
filename1.mp3
#EXTINF:240,Artist Name - Song Name 1
filename1.mp3
#EXTINF:360,Artist Name - Song Name 2
subfolder\filename2.mp3

etc.

The first number is the song length in seconds.

Of course, Winamp only displays the time, artist metadata and title metadata (by default anyway) so it'd be a bit different in Cog's case.

Whoops, sorry 'bout that.

I remember that paragraph, but I guess I must've skipped over the line about not submitting bugs.


Well, OK, I'll make tickets for issues I find.

Well, perhaps not store it in a "permanent" way like iTunes or other library-based players do.

But rather perhaps "cache" it? (don't know if that's the right word)

For hundred- or thousand-song playlists, this could be a big improvement.

339

(98 replies, posted in Development)

340

(98 replies, posted in Development)

Uh... can't seem to get it running.

Bounces once in the Dock then stops. (If not kept in the Dock, it'd appear and disappear before it's even done appearing.)

Still occurs even after getting rid of the Cog folder in Application Support and both com.vspader.cog.plist and org.cogx.cog.plist.

Also tried trashing the Cog folder and org.cogx.cog folder in Caches.


So yeah, "Things are still EXTREMELY unstable" is pretty right on. ;p

341

(17 replies, posted in Development)

342

(6 replies, posted in Help)

That's copying. ;p

343

(6 replies, posted in Help)

344

(17 replies, posted in Development)

Uh... so if I think a certain issue should be fixed by 0.08, then I put "0.08" as the Milestone...

...but what do I put as the Version?

"0.07 (r635)"?

Or nothing? I'm guessing you only put Version for bugs? ('cause a bug would apply to such and such version, while feature requests have nothing to do with previously released versions?)

346

(11 replies, posted in Development)

348

(8 replies, posted in Archives)

349

(6 replies, posted in Features)

350

(17 replies, posted in Development)