Existing users, 
FStream
Listen to and record web radio.
Version: 1.4.4
Interesting
Feedback Type: Review
Contributed by: trillionandtwo Monday, July 10 2006 @ 04:19 AM PDT
Product Platform: MacOSX
Used Product For: Less than a month
Recommend Product: YES
This app looked like the perfect application for my needs. I was just looking for a small footprint, lightweight no-nonsense stream player and FStream came up in my search. Bingo. I love the lightweight GUI and the basic concept of quick and easy access to a few stream bookmarks. Perfect. Too bad this application pegs one CPU on my macbook pro to 100% and keeps it there the whole time. iTunes, in contrast never takes more than 14% when streaming the same source. Importantly, FStream only reequired 4.2% CPU when streaming a standard internet radio site, so I believe this is only an issue for users wanting to stream from a nicecast server. Otherwise, this software magnificent! Would like to request the developer to provide a little more click surface to the menu button. It's pretty small and should probably be side-by-side with the volume button.
Overall Rating:
Ease of Use:
Support:
Features:
Quality / Stability:
Price:
Comments
Interesting - trillionandtwo
Well Done - the improvements in the last version are fantastic!I can now enjoy seamless, no-hassle streamed content at home on broadband or on the road when my macbook pro is connected via blue-tooth to my mobile telephone.
I believe that streaming content is the next mp3. There is amazing content out there and FStream is one of the few applications that give you the flexibility to accommodate just about any Internet connection with a no-nonsense, lightweight approach to getting the job done.
Now that the core is stable and reliable, I would love to see subtle improvements to the interface (mentioned in previous post). It would be great if you can make your application “skinnable”. Either way, I would be happy to contribute. I have experience in GUI design and would be pleased to get involved at any level.
Regards,
Bryan
Monday, October 16 2006 @ 01:38 AM PDT
Interesting - Avérous
Thank for your comment.For the CPU issue, I know : when FMod (the audio engine of FStream) "buffering" a web radio, he take 100% of the CPU (I don't know why currently). If FMod can't maintain a buffer to 99%, he continue a "hight buffering" (or something like that) and play at the same moment. That why for radio like Nicecast where FMod can't maintain a buffer to 99% (why, I don't know also), FStream take 100% of the processor. The current soluce is to set FStream in pause, wait to have a buffer to 99% and set FStream in play mode.
For the button on the right, yes why not bigger buttons...
Sunday, July 16 2006 @ 11:18 AM PDT
Interesting - Avérous
Thank for your comment.For the CPU issue, I know : when FMod (the audio engine of FStream) "buffering" a web radio, he take 100% of the CPU (I don't know why currently). If FMod can't maintain a buffer to 99%, he continue a "hight buffering" (or something like that) and play at the same moment. That why for radio like Nicecast where FMod can't maintain a buffer to 99% (why, I don't know also), FStream take 100% of the processor. The current soluce is to set FStream in pause, wait to have a buffer to 99% and set FStream in play mode.
For the button on the right, yes why not bigger buttons...
Sunday, July 16 2006 @ 11:21 AM PDT
Interesting - Avérous
Thank for your comment.For the CPU issue, I know : when FMod (the audio engine of FStream) "buffering" a web radio, he take 100% of the CPU (I don't know why currently). If FMod can't maintain a buffer to 99%, he continue a "hight buffering" (or something like that) and play at the same moment. That why for radio like Nicecast where FMod can't maintain a buffer to 99% (why, I don't know also), FStream take 100% of the processor. The current soluce is to set FStream in pause, wait to have a buffer to 99% and set FStream in play mode.
For the button on the right, yes why not bigger buttons...
Sunday, July 16 2006 @ 11:23 AM PDT
Interesting - Avérous
Thank for your comment.For the CPU issue, I know : when FMod (the audio engine of FStream) "buffering" a web radio, he take 100% of the CPU (I don't know why currently). If FMod can't maintain a buffer to 99%, he continue a "hight buffering" (or something like that) and play at the same moment. That why for radio like Nicecast where FMod can't maintain a buffer to 99% (why, I don't know also), FStream take 100% of the processor. The current soluce is to set FStream in pause, wait to have a buffer to 99% and set FStream in play mode.
For the button on the right, yes why not bigger buttons...
Sunday, July 16 2006 @ 11:29 AM PDT
Interesting - Avérous
Thank for your comment.For the CPU issue, I know : when FMod (the audio engine of FStream) "buffering" a web radio, he take 100% of the CPU (I don't know why currently). If FMod can't maintain a buffer to 99%, he continue a "hight buffering" (or something like that) and play at the same moment. That why for radio like Nicecast where FMod can't maintain a buffer to 99% (why, I don't know also), FStream take 100% of the processor. The current soluce is to set FStream in pause, wait to have a buffer to 99% and set FStream in play mode.
For the button on the right, yes why not bigger buttons...
Tuesday, July 18 2006 @ 05:18 AM PDT
Interesting - Avérous
Thank for your comment.For the CPU issue, I know : when FMod (the audio engine of FStream) "buffering" a web radio, he take 100% of the CPU (I don't know why currently). If FMod can't maintain a buffer to 99%, he continue a "hight buffering" (or something like that) and play at the same moment. That why for radio like Nicecast where FMod can't maintain a buffer to 99% (why, I don't know also), FStream take 100% of the processor. The current soluce is to set FStream in pause, wait to have a buffer to 99% and set FStream in play mode.
For the button on the right, yes why not bigger buttons...
Tuesday, July 18 2006 @ 05:22 AM PDT
Interesting - Avérous
Thank for your comment.For the CPU issue, I know : when FMod (the audio engine of FStream) "buffering" a web radio, he take 100% of the CPU (I don't know why currently). If FMod can't maintain a buffer to 99%, he continue a "hight buffering" (or something like that) and play at the same moment. That why for radio like Nicecast where FMod can't maintain a buffer to 99% (why, I don't know also), FStream take 100% of the processor. The current soluce is to set FStream in pause, wait to have a buffer to 99% and set FStream in play mode.
For the button on the right, yes why not bigger buttons...
Reply to This
Sunday, July 16 2006 @ 11:03 AM PDT