Existing users, log in.  New users, create a free account.  Lost password?

User Profile for doctor.lex

User Name doctor.lex

Member Since 2006-05-26

Total number of Feedback Posts: 8

Total number of comments: 1

Last 10 Feedback Posts by doctor.lex  [ Search for All ]

Audacity X 1.3.5 (Mac OS X)

Holy memory leaks Batman!  

After opening 2 small sound files in my fresh 1.3.5 install, I noticed increasing delays and hard disk activity each time I clicked the "play" button. Running 'top' in the terminal revealed that Audacity was already using an RSIZE of 2GB! When opening a 128KB mono WAV file, RSIZE goes up with about 120MB, and every time I click "Play", about 80MB goes down the drain. After a while the swapping becomes so excessive that the program becomes unusable. It seems that some very important free() or delete calls were forgotten in this version. I'm going back to 1.3.3 for the time being... [alert admin]

Post a comment | More Info

Saturday, May 10 2008 @ 05:45 AM PDT

0xED 1.0.6 (Mac OS X)

Find Previous (still) doesn't work properly  

The "Find previous" feature doesn't behave like it should. The author should look at how "Find Previous" behaves in TextEdit and make sure that 0xED behaves in exactly the same way. For instance, search for "string" in the following sentence: This is a string containing multiple instances of the word "string", and it's a pretty long string indeed. In TextEdit, move the cursor in between the "ng" of the last occurrence of "string" (or select the 'g'), and perform a Find Previous (FP). It will _not_ find this last occurrence (which makes sense because if the cursor is in it, the user will probably know it's there). 0xED however, will select this last occurrence no matter which byte of it is selected. And it's worse, when performing a subsequent FP, it will stick to this last occurrence. Apparently, FP in 0xED is implemented as a regular "Find forward", but with a decrementing position counter instead of an incrementing one. This would be OK if the starting position would not be the start of the current selection, but N bytes before it, where N = the length of the search string. For the rest, this editor has all the features I need. Keep up the good work! [alert admin]

Post a comment | More Info

Friday, November 16 2007 @ 05:31 AM PST

Barcode Generator 2.4a (Mac OS X)

Good  

This program works as expected, and offers a good deal of formatting options for various types of barcodes. Don't forget to download the free registration key at pro-barcode.com to get rid of the 'EVAL' letters. There are free OCR-A and OCR-B fonts on the web, so you can make the barcodes really standards-compliant. However, when decoding the datamatrix codes that this program produces, I often get incorrect results with longer strings. I'm not sure if this is due to errors in the decoder I'm using, or the encoder in this program. So you should verify this if you intend to use this program to generate datamatrix 2D-codes. [alert admin]

Post a comment | More Info  |  1 of 1 users found this helpful

Friday, May 11 2007 @ 08:32 AM PDT

ResKnife 0.6 b4 (Mac OS X)

Useful program, but this version isn't  

As an OS X Intel user, this is a lifesaver when it comes down to editing resource forks without paying ridiculous amounts of money for a commercial editor. The (t)rusty ResEdit requires Classic to run, which is impossible on an Intel Mac, and running ResEdit in an emulator like SheepShaver is a kludge. Unfortunately this version does't allow me to open anything else than .rsrc files, so it's back to 0.6b3 for me... P.S.: The nineties called, they want their proprietary compression format with non-backwards compatible version upgrades back. Please distribute the next version in a .dmg or .zip file. [alert admin]

Post a comment | More Info

Monday, April 23 2007 @ 07:25 PM PDT

macam 0.8.6 (Mac OS X)

It just works!  

I have some obscure kind of tiny webcam/camera combination (QP3 pen cam) with no hope of OS X support. But with macam, I just need to plug in the camera and it works flawlessly. It also allows me to download images from the camera's flash memory. The time lapse mode in this version is really cool, I'm making a movie of a plant growing at this very moment :) [alert admin]

Post a comment | More Info  |  2 of 2 users found this helpful

Wednesday, June 28 2006 @ 12:24 PM PDT

OSS 3D 1.51 (Mac OS X)

Awesome, but hogs CPU  

With this plug-in, you can turn cheapo speakers or headphones into professional sounding equipment. The only catch is that you either need to know a bit about what all the settings do and how you can use them to overcome the specific weaknesses of your equipment. So don't expect instant magic, but the presets can help you to get started. Of course there are limits to what this thing can do, I can make the speakers of my iBook sound better but there's no way of making them sound like studio monitors :) The only drawback is that this plug-in consumes a massive amount of CPU cycles, and it has gotten worse since previous versions. On my old 800MHz G3, iTunes' CPU usage jumps from 10% to 50% when OSS 3D is active (an older version 'only' used 38%). The developers say that this can be caused by the 'about' window, but during my test only the minimized iTunes window was visible. The weird thing is that I find reviews from G5 users with much faster machines, who also report 30% or more CPU usage. Clearly there is some room for optimization here... [alert admin]

Post a comment | More Info  |  0 of 2 users found this helpful

Saturday, May 27 2006 @ 01:00 PM PDT

DivX for Mac 6.5 (Mac OS X)

Not working at all  

On my iBook G3 this doesn't appear to work at all. The DivX player crashes upon launch, and I can't view any DivX movie in QT Player. I suppose nobody takes G3 users into consideration anymore. This aside, I'm not particularly fond of the move towards a standalone player, unless everything is still based on a QuickTime plugin, so I can still open DivX movies in other QT based applications. It appears that this is the case (if it would work), because QuickTime plugins are still installed. So I suppose the DivX player is just another QT frontend without a ridiculous full screen restriction. So if you have a fairly recent Mac this might be good. [alert admin]

Post a comment | More Info

Friday, May 26 2006 @ 08:36 AM PDT

MPlayer OS X 1.0pre8rc5 (Mac OS X)

Useless on a G3  

I have been using the previous version which whined about 'no Altivec' everytime I opened it, so I was glad to see this warning is gone in this version. However, all other functionality appears to have disappeared too. Nothing happens when I click the 'play' button or when I open a file. When I try to add something to the playlist, it crashes. I did some diagnostics by replacing the 'mplayer' and 'mplayer_noaltivec' binaries in the application package with bash scripts which dump their arguments in a file. They aren't even executed when a file is played or opened, only when adding something to the playlist. So when I say that 'nothing happens' when clicking 'Play', I really mean nothing. Assuming that the 'play' button would work, I still wouldn't have playback. When I run the 'mplayer_noaltivec' binary in the terminal, I get "dyld: incompatible cpu-subtype Trace/BPT trap" After replacing mplayer_noaltivec with a working self-compiled binary, adding stuff to the playlist still causes a crash, so this thing is broken beyond repair. I suppose I'll have to cope with the 'no altivec' warning until the first major revision of the MBP is available. I know the developer has no access to a G3, but that doesn't mean that other people with a G3 -- like me -- can beta test... [alert admin]

Read Comments (1) | More Info

Friday, May 26 2006 @ 06:27 AM PDT

Last 10 Comments by doctor.lex  [ Search for All ]

changes File Mappings  

Yes, this is awfully annoying. There are two ways to solve this: either you compress ResKnife into an archive every time you don't need it, or you modify the Info.plist inside the application bundle. You need to remove the second entry in "CFBundleDocumentTypes" (the one with '*' in "CFBundleTypeExtensions"). The easiest way to do this is by opening the plist file in Property List Editor. To make the changes work, you should simulate a 'reinstall'…

Original feedback item : Read More(1 words)

Tuesday, June 26 2007 @ 05:34 AM PDT