I really like the new Aeon Beta but I can't get any custom themes to work. Played around with them for a few hours and all I get is a black screen. I tried including/excluding the custom A and B categories and selecting or not selecting custom maps and colors within them, but I get nothing no matter which way I try it.
One thing that is confusing is the two sets of 'similar' custom categories and their relation to the plus and minus options. Sometimes it seems like Category A on the bottom controls category A on top, but sometimes not, and I am unsure of the purpose of that relationship to begin with?
Also sometimes the menu buttons don't respond to mouse clicks for 5-10 seconds at a time and eventually they work again.
Can't get Aeon Beta Custom Theme to Show Something
Moderators: BTT, andy55, b.dwall, juxtiphi
In our current beta, in the theme editor, the categories on top represent scenes, and the categories on the bottom of the list represent colormaps - this will be labeled properly in future versions.
Note that in the theme editor, you can only include/exclude/disregard 'categories' - these categories can be edited in the scenes/colormaps menus.
If everything appears black, it may be that you have no colormaps active. Press 'v' to switch verbose mode, press 'u' to reload current configs, and it should show you the scene/colormap it is reloading. If it shows colormap: (Black), and you can't switch colormaps with Q/W, you need to select a colormap category in your custom theme.
Hope that helps!
Note that in the theme editor, you can only include/exclude/disregard 'categories' - these categories can be edited in the scenes/colormaps menus.
If everything appears black, it may be that you have no colormaps active. Press 'v' to switch verbose mode, press 'u' to reload current configs, and it should show you the scene/colormap it is reloading. If it shows colormap: (Black), and you can't switch colormaps with Q/W, you need to select a colormap category in your custom theme.
Hope that helps!
Hello datdude
In Windows XP:- Program Files\SoundSpectrum\Aeon\Home\ColorMaps. You can simply delete any ColorMap that is not to your liking.
You can also delete any Scenes not to your liking, to do this you need to Edit Home/Library/SceneData.py - search for the scenes you don't want and put a # in front of them to comment them out. (Info from M2C)
Regards BTT
In Windows XP:- Program Files\SoundSpectrum\Aeon\Home\ColorMaps. You can simply delete any ColorMap that is not to your liking.
You can also delete any Scenes not to your liking, to do this you need to Edit Home/Library/SceneData.py - search for the scenes you don't want and put a # in front of them to comment them out. (Info from M2C)
Regards BTT
2 scenes can't be removed
It looks like there are 2 scenes that are hard coded in and can't be removed at the moment. They are Hello World (small plain cube) and Audio Display (beat detect).
These are not listed in the scenedata.py file. Is there any other way to remove these? I'm assuming they will be removed once the beta goes live?
Thanks
These are not listed in the scenedata.py file. Is there any other way to remove these? I'm assuming they will be removed once the beta goes live?
Thanks
I actually like the Audio Display one. Hope it stays around for the final.
About the custom themes thing. If you set the startup theme to a custom theme exit the menu and go back to see what the startup theme is you will see its set to "-" instead of custom 1 or 2. Its like it does not want to be set to a custom theme and if its like that then you get the black screen.
From what I can tell you can only load your custom theme but not have it as the startup theme. I bet they are aware of this and are working on it.
I will be emailing them about this later tonight as well.
About the custom themes thing. If you set the startup theme to a custom theme exit the menu and go back to see what the startup theme is you will see its set to "-" instead of custom 1 or 2. Its like it does not want to be set to a custom theme and if its like that then you get the black screen.
From what I can tell you can only load your custom theme but not have it as the startup theme. I bet they are aware of this and are working on it.
I will be emailing them about this later tonight as well.
-
Tex Pepper
- Posts: 2
- Joined: Tue Oct 30, 2012 10:37 pm
Themes
I am seeing similar problems, but not *quite* those described here. When I set up a Custom Theme and set that as the Startup Theme, I get a rotating field of stars for one slideshow interval, then black henceforth.
Presets
Presets in this new version of Aeon do not 'hold.' In the previous version a preset's scenes and colourmaps held until explicitly changed by the user. Now, the preset holds for the duration of the current slideshow interval only; after that the current Theme takes over. In light of Aeon's new Themes capability are Presets even relevant? But read on...
Design Suggestion
Aeon's Presets are easy to set up and use. They're simple and intuitive - and familiar. Functionally speaking, Aeon's new Themes are not all that different in what they do, really. That Include/Exclude/Disregard feature is a bit confusing at first, true, and the apparent replication of existing categories below the main list far more so, but apart from that Themes are essentially Named Presets, yes? Why not then simply extend the existing (and debugged) Presets paradigm instead of adding a totally new, separate (and admittedly rather redundant) feature? Presets used to work. I'd add named presets and drop Themes entirely. Less is More.
I am seeing similar problems, but not *quite* those described here. When I set up a Custom Theme and set that as the Startup Theme, I get a rotating field of stars for one slideshow interval, then black henceforth.
Presets
Presets in this new version of Aeon do not 'hold.' In the previous version a preset's scenes and colourmaps held until explicitly changed by the user. Now, the preset holds for the duration of the current slideshow interval only; after that the current Theme takes over. In light of Aeon's new Themes capability are Presets even relevant? But read on...
Design Suggestion
Aeon's Presets are easy to set up and use. They're simple and intuitive - and familiar. Functionally speaking, Aeon's new Themes are not all that different in what they do, really. That Include/Exclude/Disregard feature is a bit confusing at first, true, and the apparent replication of existing categories below the main list far more so, but apart from that Themes are essentially Named Presets, yes? Why not then simply extend the existing (and debugged) Presets paradigm instead of adding a totally new, separate (and admittedly rather redundant) feature? Presets used to work. I'd add named presets and drop Themes entirely. Less is More.
-----