MP3Car.com - View Single Post

sivart321 · 11-19-2006, 11:04 PM

Quote: Originally Posted by RPM_VR4

2) Progress bar. Trying to hold a button for FF and then having it go way too slow for music and way too fast for videos sucks! The progress bar allows me to see my progress through a song (so I can easily tell when the song is about to end) and to jump instantly to any point in the song with a single click. Please put this on your to-do list David.

3) Horrible support for embedding apps. I really want SKINbedder built in to CF. RR doesn't have this either, but at least it can easily make a skin that sends hot-key without having to code a plug-in.

4) Milk-Drop. You need to support WinAmp vis plugins or take the open-source from milk-drop and make that native. If I can't have MilkDrop then I might as well have no visualization at all.

5) Ton's of useful features: GAS Price Finder, Vehicle Maintenance Log, Draw, Calculator, Weather with cool full-screen maps, GPS Speed/Heading/Next-Turn on main-title bar, etc.

6) Reliability. RR has tons of problems when it is not configured perfectly. It is very difficult to debug all the many problems you are bound to encounter and find a work-around for each one. That said, once you have something working, it seems to work reliably. CF on the other hand likes to randomly display LOADING for a long time, or take a really long time to start up after re-boot, or run a 1 FPS for 10 seconds, or totally lock-up/exit. The problem is it's random, not reproducible, so I can't debug it.

...I look forward to a future release.

I agree with alot of this...

These things are just some of the reasons why paying for CF down the road scares me. At this point, David is having a hard enough time getting a solid release that doesn't give its users headaches. What is worse, is the speed (or lack therof) that he releases updates and new features. To be competetive (with so many other FREE options) the timeliness of things needs to be improved. We need to see that the core usability issues are being solved quickly, and that he actually is able to work on those advanced features and plug-ins that truly WILL bring some main stream appeal.

I am not sure how he can do this, but it needs to happen. There is alot of potential with CF with it's superior look and feel... the problems (to me) are all related to speed, functionality, and reliability/buginess. I don't know if he needs more people to help code, or if he needs to opensource some stuff to allow others to help speed up the process... I just think something needs to be changed to really prove this product is worth peoples time and money.

I hope my concerns are clear and constructive... I do not mean to bash your methods or your product at all...

11-19-2006, 11:04 PM	#4
sivart321 Variable Bitrate sivart321's CarPC Specs Join Date: Mar 2005 Location: Pomona, CA Vehicle: 1990 VW Corrado Posts: 445 My Photos: ()	Quote: Originally Posted by RPM_VR4 2) Progress bar. Trying to hold a button for FF and then having it go way too slow for music and way too fast for videos sucks! The progress bar allows me to see my progress through a song (so I can easily tell when the song is about to end) and to jump instantly to any point in the song with a single click. Please put this on your to-do list David. 3) Horrible support for embedding apps. I really want SKINbedder built in to CF. RR doesn't have this either, but at least it can easily make a skin that sends hot-key without having to code a plug-in. 4) Milk-Drop. You need to support WinAmp vis plugins or take the open-source from milk-drop and make that native. If I can't have MilkDrop then I might as well have no visualization at all. 5) Ton's of useful features: GAS Price Finder, Vehicle Maintenance Log, Draw, Calculator, Weather with cool full-screen maps, GPS Speed/Heading/Next-Turn on main-title bar, etc. 6) Reliability. RR has tons of problems when it is not configured perfectly. It is very difficult to debug all the many problems you are bound to encounter and find a work-around for each one. That said, once you have something working, it seems to work reliably. CF on the other hand likes to randomly display LOADING for a long time, or take a really long time to start up after re-boot, or run a 1 FPS for 10 seconds, or totally lock-up/exit. The problem is it's random, not reproducible, so I can't debug it. ...I look forward to a future release. I agree with alot of this... These things are just some of the reasons why paying for CF down the road scares me. At this point, David is having a hard enough time getting a solid release that doesn't give its users headaches. What is worse, is the speed (or lack therof) that he releases updates and new features. To be competetive (with so many other FREE options) the timeliness of things needs to be improved. We need to see that the core usability issues are being solved quickly, and that he actually is able to work on those advanced features and plug-ins that truly WILL bring some main stream appeal. I am not sure how he can do this, but it needs to happen. There is alot of potential with CF with it's superior look and feel... the problems (to me) are all related to speed, functionality, and reliability/buginess. I don't know if he needs more people to help code, or if he needs to opensource some stuff to allow others to help speed up the process... I just think something needs to be changed to really prove this product is worth peoples time and money. I hope my concerns are clear and constructive... I do not mean to bash your methods or your product at all...