Unfortunatelly I did not receive my Muse yet, so I cannot test it, but based on what I have read: Yes, I believe that you need to add the --dsp parameter to the command line to get those algorithms pre-processed data, like bellow:
muse-io --device <DEVICE_NAME> --osc osc.udp://localhost:5000 --preset 14 --dsp (note: --device <DEVICE_NAME> is not needed if you have not changed the bluetooth name of your Muse.
Once you get muse-io connected to your Muse, it will start broadcasting data to your own computer (localhost = IP 127.0.0.1) on port 5000, according to what is defined in preset 14.
Then you can use any of the tools already released to see all the data it’s sending, either as pure text screen dump, or in a graph (using muse-lab).
oscdump is one of these tools (screen dump) - try oppening another command prompt window and type:
to see all data, or if you want to filter just some data (like alpha or beta …) try:
oscdump 5000 | grep /muse/dsp/elements/alpha
(or /muse/dsp/bandpowers/alpha case OSC Paths versrion 3.4.0 was not yet released)
muse-player is another command line tool that accepts different tyes of INPUTS and OUTPUTS (I believe that if you type only muse-player it will list all parameters accepted and their syntax).
but, give also a try to muse-lab and you shoud see graph plots of the data you select (muse-lab is a java app, just double-clik it), check its tutorial at:
https://sites.google.com/a/interaxon.ca/muse-developer-site/muselab/tutorial (it may be a bit outdated, but the basic functionallity should be the same)
Let us know what you get, ok ?