<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[[SOLVED] Input Parser size limit?]]></title><description><![CDATA[<p>Hi, I'm wrangling a large amount of text from an API URL <a href="http://api.smartcitizen.me/devices/1616">http://api.smartcitizen.me/devices/1616</a></p>
<p>via: Get URL text &gt; input parser</p>
<p>I'm about halfway through and it has just given up on a virtually identical section to what was processed correctly above.</p>
<p>Is there a maximum size limit of field limit for the Input Parser? I've searched the manual and the forum...</p>
<p>Thanks,</p>
<p>Rob</p>
<p><img src="/assets/uploads/files/1584800252870-screenshot-2020-03-21-at-14.08.40.png" /><img src="/assets/uploads/files/1584800253346-screenshot-2020-03-21-at-14.08.49.png" /><img src="/assets/uploads/files/1584800253950-screenshot-2020-03-21-at-14.09.37.png" /></p>]]></description><link>https://community.troikatronix.com/topic/6500/solved-input-parser-size-limit</link><generator>RSS for Node</generator><lastBuildDate>Sun, 10 May 2026 23:49:34 GMT</lastBuildDate><atom:link href="https://community.troikatronix.com/topic/6500.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 21 Mar 2020 14:17:50 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Mon, 23 Mar 2020 21:01:25 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2">@mark</a> said:</p>
<blockquote>Get the new JSON Parser Actor</blockquote>
<p> Hi Mark,</p><p>That is remarkable - I am spinning!! <br /></p><p>Best wishes</p><p>Russell</p>]]></description><link>https://community.troikatronix.com/post/40109</link><guid isPermaLink="true">https://community.troikatronix.com/post/40109</guid><dc:creator><![CDATA[bonemap]]></dc:creator><pubDate>Mon, 23 Mar 2020 21:01:25 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Mon, 23 Mar 2020 16:49:54 GMT]]></title><description><![CDATA[<p>@robhblack and <a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/205">@bonemap</a></p><p>I've just made your life a lot easier.</p><p>Get the new <a href="https://community.troikatronix.com/topic/6503/json-parser-actor-for-macos-and-windows-public-beta">JSON Parser Actor</a></p><p>Best Wishes,<br />Mark</p>]]></description><link>https://community.troikatronix.com/post/40100</link><guid isPermaLink="true">https://community.troikatronix.com/post/40100</guid><dc:creator><![CDATA[mark]]></dc:creator><pubDate>Mon, 23 Mar 2020 16:49:54 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Mon, 23 Mar 2020 06:17:23 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2"><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2">@mark</a></a> said:</p>
<blockquote> this will allow you to improve you parsing</blockquote>
<p> Hi <a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2"><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2">@mark</a></a> </p>
<p>Yes it will allow some improvement. That is a much appreciated insight. I did attempt something like that but will definitely give it another go.</p>
<p>best wishes</p>
<p>Russell</p>]]></description><link>https://community.troikatronix.com/post/40088</link><guid isPermaLink="true">https://community.troikatronix.com/post/40088</guid><dc:creator><![CDATA[bonemap]]></dc:creator><pubDate>Mon, 23 Mar 2020 06:17:23 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Mon, 23 Mar 2020 05:54:33 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/205">@bonemap</a> said:</p>
<blockquote>I did have one issue: I was unable to parse the ° degree symbol (shift-option-8) Isadora hard crashed most times I tried to include the symbol in the character-set range.</blockquote>
<p> Yes, this is no going to work because this actor is not really unicode savvy. (It converts all strings to UTF-8, and the ° symbol ends up being more than one byte long in that reprepsentation. So you can't actually include it in the character set you're using inside of the square brackets (i.e., [-\" a-z _ A-Z 0-9:\[\&rsqb;&rsqb; )</p>
<p>But I feel in general that the technique you're using to skip a fixed number of bytes is maybe not the best way to do it. It would be better to parse for the label and then the data after it. Take a look at the simplified example file below:</p>
<p>This is the input string</p>
<p>{"description":"Temperature","unit":"ºC"}</p>
<p>Here is the parsing code with comments (which cannot of course be included in the real parsing string.)</p>
<pre>
"{" -- skip the starting bracket
"\"description\":" -- skip text "description":
"\"" -- skip opening double quote
desc : string=[^\"] -- accept all characters until the next double quote and output that string to the desc output
"\"" -- skip ending double quote
"," -- skip comma
"\"unit\":" -- skip text "unit:"
"\"" -- skip opening double quote
unit : string=[^\"] -- accept all characters until the next double quote and output that string to the unit output
"\"" -- skip ending double quote
"}" -- skip ending bracket</pre>
<p>as you can see, this correctly grabs "°C" because it is not depending on matching particular characters like a-z, etc.</p>
<p>You could write this even more elegantly as follows</p>
<pre>
"{"
"\"" [^\"] "\":" -- skip any text in the form "xxx":
"\"" desc : string=[^\"] "\"" -- grab a parameter in the form "xxx" and output as desc
"," -- skip a comma
"\"" [^\"] "\":" -- skip any text in the form "xxx":
"\"" unit : string=[^\"] "\""-- grab a parameter in the form "xxx" and output as unit
"}"
</pre>
<p>Maybe this will allow you to improve you parsing and grab the stuff you need.</p>
<p>Best Wishes,<br />Mark</p>
<p><a href="/assets/uploads/files/1584942872145-parsing-suggestion.izz">parsing-suggestion.izz</a><br /></p>]]></description><link>https://community.troikatronix.com/post/40087</link><guid isPermaLink="true">https://community.troikatronix.com/post/40087</guid><dc:creator><![CDATA[mark]]></dc:creator><pubDate>Mon, 23 Mar 2020 05:54:33 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Mon, 23 Mar 2020 05:29:26 GMT]]></title><description><![CDATA[<p>@robhblack said:</p>
<blockquote>the degree symbol is not posing a problem</blockquote>
<p> It could be the cause of my ° symbol issue is that my keyboard is set to 'Australian'? I tried your string but still not parsing it. </p><p>I have also put together a 'dynamic data' demonstration patch that uses open data from the World Bank: <a href="/assets/uploads/files/1584924688343-dynamicdata.zip">DynamicData.zip</a></p>
<p>best wishes</p>
<p>Russell</p>]]></description><link>https://community.troikatronix.com/post/40084</link><guid isPermaLink="true">https://community.troikatronix.com/post/40084</guid><dc:creator><![CDATA[bonemap]]></dc:creator><pubDate>Mon, 23 Mar 2020 05:29:26 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Sun, 22 Mar 2020 22:39:21 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/205">@bonemap</a> Thanks, this is what I came up with, the degree symbol is not posing a problem albeit my iMac has pretty much latest MacOS. Your version is more elegant with less redundancies. My plan was to torture test with a few different sensor networks (some have soil sensors etc so would need a javascript logic based interpreter to grab additional individual component sensors. <a href="/assets/uploads/files/1584916703557-currentcitizen.izz">currentcitizen.izz</a></p>]]></description><link>https://community.troikatronix.com/post/40082</link><guid isPermaLink="true">https://community.troikatronix.com/post/40082</guid><dc:creator><![CDATA[photogramdude]]></dc:creator><pubDate>Sun, 22 Mar 2020 22:39:21 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Sun, 22 Mar 2020 22:23:45 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2"><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2">@mark</a></a> said:</p>
<blockquote>I hope it helps.</blockquote>
<p> Thanks <a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2"><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2">@mark</a></a> </p><p>I was able to get the new module to parse the data to the last line. I am using Mac OS Mojave and Isadora 3.07 stable. <br />I did have one issue: I was unable to parse the ° degree symbol (shift-option-8) Isadora hard crashed most times I tried to include the symbol in the character-set range.</p><p>I have marked the data and string in red on this test patch: <a href="/assets/uploads/files/1584915804769-smartcitizenparse_degreesymbol.izz">smartcitizenParse_degreeSymbol.izz</a></p><p>I have a Mac OS Catalina machine arriving in a couple of days, I might be onto other things by then otherwise I will try the new Text Parser there as well.<br /></p><p>Best Wishes</p><p>Russell</p>]]></description><link>https://community.troikatronix.com/post/40081</link><guid isPermaLink="true">https://community.troikatronix.com/post/40081</guid><dc:creator><![CDATA[bonemap]]></dc:creator><pubDate>Sun, 22 Mar 2020 22:23:45 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Sun, 22 Mar 2020 18:29:46 GMT]]></title><description><![CDATA[<p><a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2">@mark</a> said:</p>
<blockquote>Manually Installing a Plugin</blockquote>
<p> IT WORKS!!!</p><p>Much appreciated, I'll dive back into this tomorrow and share progress.</p>]]></description><link>https://community.troikatronix.com/post/40080</link><guid isPermaLink="true">https://community.troikatronix.com/post/40080</guid><dc:creator><![CDATA[photogramdude]]></dc:creator><pubDate>Sun, 22 Mar 2020 18:29:46 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Sun, 22 Mar 2020 17:51:02 GMT]]></title><description><![CDATA[<p>Dear All,</p><p>So I recompiled the Text Parser to have a buffer of 256K instead of 2k. It solves your problem. But the issue on MacOS is, if you install it, the "code signature" of the app will become invalid and -- depending on the version of macOS you're running -- it might not allow Isadora to run. On Windows, it should not be an issue.</p><p>So, attached you will find the Mac and Windows plugins in a .zip file. Follow the instructions about <a href="https://support.troikatronix.com/support/solutions/articles/13000014943-isadora-1-2-installing-an-isadora-plugin-manually">Manually Installing a Plugin</a> which say Isadora 1 + 2, but are valid for Isadora 3 too. </p><p><a href="/assets/uploads/files/1584899238381-text-parser.zip">Text Parser.zip</a></p><p>If the operating system refuses to launch Isadora after installing the plugin, re-install Isadora using the standard installer.</p><p>I hope it helps.</p><p>Best Wishes,</p><p>Mark</p><p></p>]]></description><link>https://community.troikatronix.com/post/40079</link><guid isPermaLink="true">https://community.troikatronix.com/post/40079</guid><dc:creator><![CDATA[mark]]></dc:creator><pubDate>Sun, 22 Mar 2020 17:51:02 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Sun, 22 Mar 2020 12:11:34 GMT]]></title><description><![CDATA[<p>@robhblack</p><p>We will have to make a feature request for this.</p><p>Best wishes</p><p>Russell</p>]]></description><link>https://community.troikatronix.com/post/40075</link><guid isPermaLink="true">https://community.troikatronix.com/post/40075</guid><dc:creator><![CDATA[bonemap]]></dc:creator><pubDate>Sun, 22 Mar 2020 12:11:34 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Sun, 22 Mar 2020 11:53:06 GMT]]></title><description><![CDATA[<p>Just checked, the input runs dry after 2048 characters or 2K. So it would be amazing if this limit could shift upwards in a future release ;)</p>]]></description><link>https://community.troikatronix.com/post/40074</link><guid isPermaLink="true">https://community.troikatronix.com/post/40074</guid><dc:creator><![CDATA[photogramdude]]></dc:creator><pubDate>Sun, 22 Mar 2020 11:53:06 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Sun, 22 Mar 2020 10:02:48 GMT]]></title><description><![CDATA[<p>Hi Russell, yesterday I used the Hello OSC method from DusX which I got installed on my Mac OK, could see cabin pressure on my browser but Isadora itself steadfastly refused to pick up the input, rage quit after a few hours!</p><p>We're looking at Node Red.</p><p>I'm using a Mac, was wondering about making some of the fields more agnostic (was trying to strictly typecast so that variable data input eg null values using 2 bytes instead of 3 because no quotes doesn't make it fall over.</p><p>The documentation is simultaneously expansive but I must admit to struggling!</p><p>I'll look into the JSON method after trying to restore some sanity, but if I break the back of this it's massive since APIs have always been this monolithic terrifying concept for me!</p><p>Best,</p><p>R</p>]]></description><link>https://community.troikatronix.com/post/40072</link><guid isPermaLink="true">https://community.troikatronix.com/post/40072</guid><dc:creator><![CDATA[photogramdude]]></dc:creator><pubDate>Sun, 22 Mar 2020 10:02:48 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Sun, 22 Mar 2020 09:58:33 GMT]]></title><description><![CDATA[<p>Hi Rob,</p>
<p>I believe there is an alternative using json data and the Isadora javascript actor to parse the data stream into the patch. I am not able to advise you on the json method. unfortunately I am not proficient enough and am still learning.</p>
<p>When working with the data I did have n issue with parsing the degree symbol for a temperature field. I see from your screen grab that your field with the degree symbol has parsed OK. I am wondering why that is. Are you using a Mac or PC? I can’t think of why I couldn’t get that to work.</p>
<p>Best wishes</p>
<p>Russell </p>]]></description><link>https://community.troikatronix.com/post/40071</link><guid isPermaLink="true">https://community.troikatronix.com/post/40071</guid><dc:creator><![CDATA[bonemap]]></dc:creator><pubDate>Sun, 22 Mar 2020 09:58:33 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Sun, 22 Mar 2020 09:25:10 GMT]]></title><description><![CDATA[<p>Hi,</p><p>Yeah Smart Citizen have sensors all over the world, and we want to tell the story of air pollution and biometrics (maybe with Cycling '74 MAX &gt; Apple Watch) parsed input in a nice visual way.</p><p>Thanks for this huge contribution, I think logic would dictate Isadora Input Parser is setting an arbitrary KB limit on the length of the text field it parses. I can see that it all comes in, but then it falls over! I guess there could be a dev option to increase this?</p><p>In the meantime the workaround is to cleave the input in two somehow?</p><p>Cheers for this big help,</p><p>Rob</p>]]></description><link>https://community.troikatronix.com/post/40070</link><guid isPermaLink="true">https://community.troikatronix.com/post/40070</guid><dc:creator><![CDATA[photogramdude]]></dc:creator><pubDate>Sun, 22 Mar 2020 09:25:10 GMT</pubDate></item><item><title><![CDATA[Reply to [SOLVED] Input Parser size limit? on Sun, 22 Mar 2020 08:00:44 GMT]]></title><description><![CDATA[<p>@robhblack said:</p>
<blockquote>it has just given up on a virtually identical section</blockquote>
<p> Hi Rob,</p>
<p>SmartCitizen looks very interesting thanks for introducing it here<img class="emojione" src="https://cdn.jsdelivr.net/emojione/assets/png/263a.png?v=2.2.7" alt="☺" style="cursor:pointer" /></p>
<p>If there is a limitation only <a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/2">@mark</a> or <a class="plugin-mentions-user plugin-mentions-a" href="https://community.troikatronix.com/uid/124">@DusX</a> will have the answer to enlighten us.<br /></p>
<p>EDIT: I had a go at parsing the data but could not get any further than the same point indicated in your screen grab. Patch 3.07 attached: <a href="/assets/uploads/files/1584855537228-smartcitizenparse.izz">SmartcitizenParse.izz</a></p>
<p>Best Wishes</p>
<p>Russell</p>]]></description><link>https://community.troikatronix.com/post/40068</link><guid isPermaLink="true">https://community.troikatronix.com/post/40068</guid><dc:creator><![CDATA[bonemap]]></dc:creator><pubDate>Sun, 22 Mar 2020 08:00:44 GMT</pubDate></item></channel></rss>