|
Post by AnthroHeart on Mar 26, 2024 18:07:32 GMT
With imem 1 it's half as fast as it was with imem 0.5. I am using 2 variables to hold the intention string. So the RAM specified is divided between the two variables.
You could try --imem 2 and see if that works.
I had to do 1/2 because anymore was causing memory issues.
|
|
|
Post by AnthroHeart on Mar 26, 2024 18:08:21 GMT
Whats it doing when i load in NESTED.ZIP Which has 10000 nesting file.txt intention.txt HSUPLINK.txt nesting1.txt calls HSUPLINK.txt should makke it intelligent to nested files. It just repeats the word HSUPLINK.txt and lets the universe work through the files.
It's not the same as actually repeating the text of a file.
|
|
|
Post by reden on Mar 26, 2024 18:12:35 GMT
Whats it doing when i load in NESTED.ZIP Which has 10000 nesting file.txt intention.txt HSUPLINK.txt nesting1.txt calls HSUPLINK.txt should makke it intelligent to nested files. It already worked like that, even with just the name. It was like a laser focus, at least for the nested files.
|
|
|
Post by brandon on Mar 29, 2024 11:25:32 GMT
What difference does hashing and compression make? More / less potency?
|
|
|
Post by reden on Mar 29, 2024 12:21:58 GMT
What difference does hashing and compression make? More / less potency? Far more powerful.
|
|
|
Post by AnthroHeart on Mar 30, 2024 1:34:54 GMT
I had Claude 3 Opus optimize my Intention Repeater MAX to v5.15.
The speed remains the same, but the code is more optimized and laid out better.
Here are the changes that were made:
That's the fully optimized code with functions reordered and using best practices. The functionality remains the same as the original code. The main changes were:
1. Reordering functions for better readability 2. Using `std::string` instead of C-style strings 3. Removing unused variables and functions 4. Using `constexpr` for compile-time constants 5. Moving `using namespace std;` inside functions where needed 6. Using `std::endl` for consistency 7. Removing redundant code in `print_color_help()` 8. Using `std::transform` with lambda functions 9. Removing redundant `freq_sentinel` variable 10. Reordering headers and removing unused ones
If you run into some issues, let me know. It reduced the lines of code from 1300+ to 1100+.
|
|
|
Post by reden on Apr 1, 2024 4:23:39 GMT
Multiplier: 6.633M Hash Multiplier: 932.890k Compression: 343X [119.409MB -> 347.642kB] 94.501-100.070 Phz in my phone, a low-midrange from 2016. It previously did 300 THz. The forum is not finding the other thread that had a few benchmarks.
|
|
|
Post by meteagle on Apr 3, 2024 23:45:42 GMT
Thank u for adding the option to load files into repeater . i had recorded some intentions into a mp3 file . this is the first time im loading the file itself into memory , instead of loading it's name . i feel the same intensity as before , but the fabric of it's energy is very different than before . its very very real . with last method i used to "see" the affirmations recorded in that file , but now i "live" them . it is far better
|
|
|
Post by reden on Apr 4, 2024 1:10:51 GMT
Thank u for adding the option to load files into repeater . i had recorded some intentions into a mp3 file . this is the first time im loading the file itself into memory , instead of loading it's name . i feel the same intensity as before , but the fabric of it's energy is very different than before . its very very real . with last method i used to "see" the affirmations recorded in that file , but now i "live" them . it is far better This likely means subliminals will now work without any further specification. That's great, your experience also is, but can you explain what did you mean by "see" vs "live"? Edit: This gave me an idea to record a video of another repeater video's energy loaded up as a file. I think/hope it's far more powerful. Edit 2: The energy subliminals have some hints of the headache caused by the real ones. Impressive!
|
|
|
Post by meteagle on Apr 4, 2024 10:53:31 GMT
Thank u for adding the option to load files into repeater . i had recorded some intentions into a mp3 file . this is the first time im loading the file itself into memory , instead of loading it's name . i feel the same intensity as before , but the fabric of it's energy is very different than before . its very very real . with last method i used to "see" the affirmations recorded in that file , but now i "live" them . it is far better can you explain what did you mean by "see" vs "live"? Before , I used to just " see " in my mind the pictures ( without so much feelings ) of the desired scenarios i had recorded in the file . now , using --file function instead of --intent , i literally " Live " them , like concept of " Living in the End " , i have so much feelings . u know i believe the " I Live them " is the only way and best way that i can describe it with .
|
|
|
Post by AnthroHeart on Apr 4, 2024 12:31:17 GMT
Thank u for adding the option to load files into repeater . i had recorded some intentions into a mp3 file . this is the first time im loading the file itself into memory , instead of loading it's name . i feel the same intensity as before , but the fabric of it's energy is very different than before . its very very real . with last method i used to "see" the affirmations recorded in that file , but now i "live" them . it is far better I didn't yet make the Repeater MAX to load binary files like mp3s. It only works with text at the moment. It isn't yet optimized for Unicode either.
The issue I think is if I load it in binary mode, then unicode characters (which can be multiple bytes) might not be stored correctly. But if you're repeating the string of bytes, it might not matter they're not in UTF-8 encoding.
I don't want two separate MAX programs.
Are people needing to load mp3's into the Repeater MAX? If so, I can update it to read from binary files.
Repeating a binary file in memory won't be the same as playing an mp3. It would be seemingly random bytes, and I'm not sure if it would have the intended affect.
My current MAX program can use UTF-8 bytes, but not represented as actual characters like emojis or what, just a string of bytes.
|
|
|
Post by AnthroHeart on Apr 4, 2024 13:16:56 GMT
But then, my image to WAV generator uses seemingly random bytes to create the WAV file, and it seems effective, so Repeating an mp3 in memory might be effective too.
If you were able to load an mp3 into Repeater MAX and run it, it probably only ran certain bytes that were within ASCII and Unicode range, not machine bytes.
So you might have partial effect.
|
|
|
Post by reden on Apr 4, 2024 13:30:40 GMT
Thank u for adding the option to load files into repeater . i had recorded some intentions into a mp3 file . this is the first time im loading the file itself into memory , instead of loading it's name . i feel the same intensity as before , but the fabric of it's energy is very different than before . its very very real . with last method i used to "see" the affirmations recorded in that file , but now i "live" them . it is far better I didn't yet make the Repeater MAX to load binary files like mp3s. It only works with text at the moment. It isn't yet optimized for Unicode either.
The issue I think is if I load it in binary mode, then unicode characters (which can be multiple bytes) might not be stored correctly. But if you're repeating the string of bytes, it might not matter they're not in UTF-8 encoding.
I don't want two separate MAX programs.
Are people needing to load mp3's into the Repeater MAX? If so, I can update it to read from binary files.
Repeating a binary file in memory won't be the same as playing an mp3. It would be seemingly random bytes, and I'm not sure if it would have the intended affect.
My current MAX program can use UTF-8 bytes, but not represented as actual characters like emojis or what, just a string of bytes.
If you run an Unicode character as an Intention, it will be seen. This proves it works. Reading as --file, it's processing the intentions that are the energy/affirmations inside the file.
|
|
|
Post by AnthroHeart on Apr 4, 2024 13:50:09 GMT
If you run an Unicode character as an Intention, it will be seen. This proves it works. Reading as --file, it's processing the intentions that are the energy/affirmations inside the file. Ok, I asked Claude and the std::string variable which I use to hold intention, can represent Unicode characters. Though it can't capture null bytes from a binary file yet.
Claude says : The issue you're experiencing is likely because the std::string class in C++ is designed to work with null-terminated strings. When you read the MP3 file into a std::string, it will only store the bytes up to the first null byte encountered, effectively truncating the data.
Do we want the Repeater MAX to be able to use mp3 and other binary files?
|
|
|
Post by reden on Apr 4, 2024 13:57:59 GMT
Yes. But when you read using --file, the speed beoomes very slow, indicating the full entirety of the file is working.
|
|