Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the method of removing spikes on AutoDecoder #4

Open
electricalgorithm opened this issue Aug 25, 2023 · 0 comments
Open

Change the method of removing spikes on AutoDecoder #4

electricalgorithm opened this issue Aug 25, 2023 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@electricalgorithm
Copy link
Owner

AutoDecoder works on the principle by substracting the average of the signal from itself. Since encoder puts the secret images on top of the frequency magnitude within an offset, this method works as expected. However, it is easily seen that it is not a bulletproof and causes some problems.

Bug Description: After choosing a carrier image at X size in vertical, and configuring the secret images above or equal to (X-300) size, it causes some pixels to be eliminated on the decoding side.

Ideas to Solve: There must be a statistical mathematics where we can eliminate these big spikes on the edges. Maybe after using fftshift, this spikes will be collected on the middle. We can apply a low-pass filter to eliminate them, but need to control the change in secret images' magnitudes.

@electricalgorithm electricalgorithm added bug Something isn't working enhancement New feature or request labels Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant