+38Hi all.
I’ve encountered a strange issue, when I made a small workspace to help me encode and decode strings on the fly.
Apparently you can’t a TextEncoder and a TextDecoder in the same workspace at the same time !??
What kind of dark magic is yielding this error ?
I even made each of the two transformer into separate custom transformers, but the error was the same.
In 2025.2 beta
It should absolutely be possible to have both at the same time.
Can you show us how they are configured.
+45So it works if you take the TextDecoder out?
How is the parameter for encoding type set up?
I can use both in 2024.1 and 2025.1
+45It looks like both the TextEncoder and TextDecoder are new versions in 2025.2 so could be an issue. 2025.1 has TextDecoder Version 1 and TexEncoder Version 2
+38It looks like both the TextEncoder and TextDecoder are new versions in 2025.2 so could be an issue. 2025.1 has TextDecoder Version 1 and TexEncoder Version 2
I originally made it in 2020.2, but upgraded them to 2025.2 to be sure. So no, unless only an intermediate version works.
+45Edit: found the settings
I only get the error if i leave the Encoding Type parameter blank…
It looks like the TextEncoder is trying to do something with that parameter so the workspace fails if it is not set even if the tester would stop anything reaching the transformer
