Replaced an obscure error message with a note that Windows Media player is required, added a “Maximize Values” option to the context menu of the minute view along with a “Split Stages” option to split stage data into Awake, REM, Light, Deep and Sleep, and flipped the icons for plug-outs.
lucidcode
Lucid Scribe App lucid dreaming tools Lightened Dream journal for lucid dreamers Halographs dream detection devices Lucid Scribe biofeedback software Lucid Scribe Database open dream research Discord Server research & dev updatesPopular Posts
NeuroSky ThinkGear EEG 0.9.6 (53)
NeuroSky ThinkGear EEG 1.0.9 (35)
Lucid Scribe 1.3.7 (19)
Zeo 0.9.0 (19)
Categories
- Hacking (13)
- Security (3)
- Hardware (12)
- Halograph EEG (1)
- Halograph EOG (8)
- Halograph FM (1)
- Halovision INSPEC (4)
- Research (16)
- Software (279)
- Lightened Dream (28)
- Lucid Scribe (68)
- Lucid Scribe Android (9)
- FILD (4)
- Halovision (2)
- ThinkGear EEG (3)
- Lucid Scribe App (4)
- Lucid Scribe Plugins (173)
- BrainFlow (2)
- Emotiv EPOC (1)
- Halovision (47)
- Hypnodyne ZMax (1)
- InteraXon Muse EEG (6)
- Keyboard (3)
- LightStone IOM (12)
- lucidcode Halograph FM (6)
- Mattel Mindflex (5)
- Microphone (2)
- Milliseconds (3)
- Mouse FIELD (12)
- Muse (2)
- NeuroSky ThinkGear EEG (31)
- OCZ NIA (2)
- OpenBCI (2)
- OpenEEG (14)
- Ping (1)
- Pranayama (6)
- tACS (8)
- TCMP (8)
- tDCS (8)
- TI EZ430 Chronos (3)
- Zeo EEG (13)
- Lucid Scribe Plugouts (7)
- Arduino (1)
- Screen LED (1)
- Yocto PowerRelay (5)
- Hacking (13)
Since this version I get an error message when I select the log from November 22nd:
‘.’, hexadecimal value 0x00, is an invalid character. Line 73, position 94513
After clicking OK the right part of the window stays empty. Other days display without an error. Hours an minutes work also for the 22nd. This was the day when I had a lot of Audio and Arduino triggers from testing. Other than that I don’t see a difference. It’s not important, just noticed this and it worked before.
Sorry for posting so many things that don’t work. But I think Lucid Scribe can only become better from it. 🙂 I really appreciate your effort and time in making this and support.
It is a pleasure. Thanks for all the testing!
There might be an invalid character in one of the hour files from the 22nd. Maybe from an audio track name… You might be able to see it if you open the LSD files from the 22nd in Notepad++ and scroll to the comments section at the end.
If any of them start with <?xml – that might also be a problem.
Thanks! It looks good in the screenshot. How did your dream go?
The Maximize Values option is useful. I think it should be disabled by default. But it doesn’t seem to do anything for the raw data (at least not NeuroSky RAW).
I can’t find the Split Stages option ^^. Where is it supposed to be?
BTW: Is it normal that the program constantly uses 17 to 54 % of my CPU or is it just me? I find the fan noise a bit annoying sometimes. I have a i7 4700HQ, 2.4 GHz, but it’s always clocked at 3 to 3.3 GHz when Lucid Scribe is running.
Thanks. I might disable it by default and make it persistent. That is an old recording from here: http://lsdbase.org/2014/11/04/electrically-vivd/. I wasn’t actually dreaming at that point, but had been lying still for 30 minutes after WBTB. I did have some very vivid dreams maybe an hour after that dosage though.
The Split Stages option only appears for Zeo data that has the Stage channel when right-clicking on on the chart in the minute view.
If you disable the RAW channel, the CPU usage should go down a lot. You can also right-click on the icon in the system tray and uncheck Animate Icon to save a few cycles.
Ah, that makes sense.
Disabling the raw channel and animate icon doesn’t lower the CPU usage (at least not noticably).
Move the slider on the current view to 10% and enable only the EEG and REM channels. Then right-click on the icon in the system tray and make sure that the overclock value is set to 100. You could set it to anything greater than 100 to slow it down – that should help with the CPU, but then you might start losing too much resolution.
The NeuroSky RAW channel runs on its own “track” as it has much more data per second. I think the Maximize is ignoring it for now… will have another look.