antico
04-22-2009, 10:05
Hello
I do not yet own any Cowon player, but am considering the D2 (or D2+) or S9.
My main usage, initially at least, would be listening to music rather than watching videos, so probably the D2/D2+ makes more sense; it is cheaper, more compact, and has SDHD memory card expansion. I intend to listen to FLAC files, which are 300-400MB each in size per CD album, so the built-in 16GB memory will not go far.
But the S9 is an attractive machine with a lovely looking AMOLED display, sound quality reputed to be equal to that of the D2+, and equally impressive battery life (even though the S9 screen is larger, the AMOLED is apparently more efficient than LCD.)
An additional attraction of the S9, from what I have read, is that each screen of its its GUI is a fully customizable Flash (.swf) file, which raises many interesting possibilities. If it had an SDHD expansion slot like the D2 then I would definitely go for the S9.
I have downloaded and examined briefly various S9 GUI Flash source (.FLA) files - including the set produced by Raymond Glover (http://www.cynosura.eu/), reverse-engineered from the default S9 firmware. I have also looked at the PDF document from http://www.cowonglobal.com, S9_Flash_FSCommand_guide_1.0EN.PDF, which describes a Flash/ActionScript FSCommand style of application programming interface (API) for interacting with the S9 firmware and hence with many of the machine's controls and settings. This seems to allow for fairly extensive customizations of the S9; modifying some of its GUI functionality, perhaps, rather than just its appearance.
As I am a programmer with some Flash 7 / ActionScript 2 experience from a few years ago (but not yet any experience of producing Flash Lite applets for mobile devices) the apparently open nature of the S9 user/programming interfaces is enticing to me.
What of the D2/D2+? When I look in these forums for the customization possibilities of the D2, they seem to amount to much less; the D2 GUI is not so open and flexible, if I have read things correctly. I take it that not all D2 screens are customizable, that tweaks are limited to changing the icons in the main menu screen and the appearance (and functionality?) of the musc player screen - themes and skins.
One can also load Flash applets onto the D2 to run - such as games, puzzles, calculators. But I presume - correct me if I am wrong - that these .SWF applet files are self-contained and do not interact with the machine's music or video playing controls or settings.
Is the new D2+ any different in this respect? Are there more Flash customization possibilities than on the D2; perhaps something approaching that on the S9? Does the D2+ expose its controls (such as button actions and events) and settings to an ActionScript API (FSCommand type of function) like the S9 does? If so, I would be more inclined to purchase the D2+, both for affordable listening pleasure and as a Flash Lite experimental testbed. Otherwise I may go for the S9 and try and work out some other way to get around its limited on-board memory.
Any replies that shed light are welcome!
Thanks in advance, from Mark
I do not yet own any Cowon player, but am considering the D2 (or D2+) or S9.
My main usage, initially at least, would be listening to music rather than watching videos, so probably the D2/D2+ makes more sense; it is cheaper, more compact, and has SDHD memory card expansion. I intend to listen to FLAC files, which are 300-400MB each in size per CD album, so the built-in 16GB memory will not go far.
But the S9 is an attractive machine with a lovely looking AMOLED display, sound quality reputed to be equal to that of the D2+, and equally impressive battery life (even though the S9 screen is larger, the AMOLED is apparently more efficient than LCD.)
An additional attraction of the S9, from what I have read, is that each screen of its its GUI is a fully customizable Flash (.swf) file, which raises many interesting possibilities. If it had an SDHD expansion slot like the D2 then I would definitely go for the S9.
I have downloaded and examined briefly various S9 GUI Flash source (.FLA) files - including the set produced by Raymond Glover (http://www.cynosura.eu/), reverse-engineered from the default S9 firmware. I have also looked at the PDF document from http://www.cowonglobal.com, S9_Flash_FSCommand_guide_1.0EN.PDF, which describes a Flash/ActionScript FSCommand style of application programming interface (API) for interacting with the S9 firmware and hence with many of the machine's controls and settings. This seems to allow for fairly extensive customizations of the S9; modifying some of its GUI functionality, perhaps, rather than just its appearance.
As I am a programmer with some Flash 7 / ActionScript 2 experience from a few years ago (but not yet any experience of producing Flash Lite applets for mobile devices) the apparently open nature of the S9 user/programming interfaces is enticing to me.
What of the D2/D2+? When I look in these forums for the customization possibilities of the D2, they seem to amount to much less; the D2 GUI is not so open and flexible, if I have read things correctly. I take it that not all D2 screens are customizable, that tweaks are limited to changing the icons in the main menu screen and the appearance (and functionality?) of the musc player screen - themes and skins.
One can also load Flash applets onto the D2 to run - such as games, puzzles, calculators. But I presume - correct me if I am wrong - that these .SWF applet files are self-contained and do not interact with the machine's music or video playing controls or settings.
Is the new D2+ any different in this respect? Are there more Flash customization possibilities than on the D2; perhaps something approaching that on the S9? Does the D2+ expose its controls (such as button actions and events) and settings to an ActionScript API (FSCommand type of function) like the S9 does? If so, I would be more inclined to purchase the D2+, both for affordable listening pleasure and as a Flash Lite experimental testbed. Otherwise I may go for the S9 and try and work out some other way to get around its limited on-board memory.
Any replies that shed light are welcome!
Thanks in advance, from Mark