26

(5 replies, posted in Bugs)

goodness, i really have to stop procrastinating and get out of the house. but anyway, i am assuming you are using leopard. the culprit is not just appfresh, if you browse around the apple support forums and others, you'll notice that many sparkle applications cause this issue. on leopard there was a change to how the launchservices database works, along with being moved to a different location, it apparently does not update/refresh too often, so when one moves an older version of an application to the trash and places a new version in the original location, launchservices will store the newer version's information in its database atop of the old version, causing the "open with" menu to become cluttered with duplicates of the offending applications. the fix is simple;

launch terminal, paste the following text into it and hit enter;

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user

then log out and log back in, now the issue should be resolved.

doing that in the latest release absolutely fixed the issue. kudos!

before i pass out for the night, i would just like to notify you that r856 still exhibits the issue we have been discussing.

i am not sure, but i would imagine it would. i also tested an earlier 0.08 nightly, and... same deal. but i'll try out the 0.07 stable on my leopard box in a bit anyway, and let you know how it turns out.

36

(98 replies, posted in Development)

"just open it if it was opened." certainly seems to make the most sense.

37

(98 replies, posted in Development)

wow! we have a playlist queue, customizable toolbar, spotlight search panel, multiple repeat modes and finally... a stop button hot-key. i just wanted to say 0.08 is getting significantly more polished and functional with every build. cog seems destined to fill the void that players like whamb and audion once did.

spader, i just checked those mp3s under the latest 0.08 nightly and the bit rate is detected just fine. on the other hand, i just checked the file information of the mp3s in a little app called mediainfo mac, and apparently the mp3s were encoded using variable bit rate, so the constant bit rate bug in the latest unstable 0.07 build would appear to be separate from the issue i have been experiencing, which is, the bit rate of the aforementioned files are displayed as "0" on the info drawer.

i haven't tested any cbr encoded mp3 files on any 0.08 builds, i will let you know when i do though. question; is the reading/display of bitrate for cbr mp3 files disabled in the "official" 0.07 release as well?

40

(6 replies, posted in Development)

greetings andr

it does seem to be fixed, kudos!

on leopard 10.5.2 the latest cog nightly displays a long negative number string (i.e. -2756402) as the bitrate for all file types it would normally read correctly in previous releases in the info drawer.  don't have any logs handy as i am typing this from my tiger box, but this problem occurred with every file i tried (all ogg and mp3 files).

p.s. this was observed on an intel core2duo macbook.

...does this mean us translators should be prepared to work on/update our localizations soon?

that's right. to make a long story short, i went a little mac nuts and got two shiny new macbooks, one for my folks, one for myself. both have leopard installed (rather re-installed, as i wanted to remove all that trial software and some system-wide localizations), and i tried out the latest cog nightly on both machines, everything was running smoothly until i attempted to enable the hebrew localization (by disabling the rest, i also tried a little utility called langswitch) either way in both cases, cog crashed when trying to run using said localization. i don't have the crash logs handy, but the only way cog would run after the crash, would be to disable all the localizations, except for the english one. i don't know if the other translations have been effected, but thought i would report this issue. otherwise cog seems to run nicely. both macbooks have essentially the same configuration, 2.2 GHz core 2 duo processors etc... so i don't think the issue is with the system(s). alrights.

47

(98 replies, posted in Development)

fair enough. hopefully by then i'll have some money rolling in and i can get one of those sweet new 17" macbook pros to try it out on ;]

none at all. isn't this supposed to be a functional feature now?

50

(39 replies, posted in Development)

the most recent toolbar ui cog mock-up, looks really sweet. i hope you release a build the moment you have it all compiled. nice stuff.