Hi Slau, Thanks a lot for that tip, there is also such an option in the Edit menu of TextEdit, so I've properly changed them both. ;)
Best, John André On 10 Jan 2020, at 00:46, Slau Halatyn <[email protected]> wrote: Hi John, What's important is that they are not smart quotes but straight quotes. This option is under the Keyboard pane of System Preferences in the Text tab. Uncheck "Use Smart Quotes and Dashes" and make sure straight quotes are selected from the pop-up menu. I think in the demo mp3 for Plug-in Views, I mention cutting the first line from the pasted text to use in the naming of the document. At any rate, the first line of the text file would start with: {"View etc. Glad it's working for you. Slau > On Jan 9, 2020, at 5:54 PM, John André Lium-Netland <[email protected] > <mailto:[email protected]>> wrote: > > Hi Slau, > > Problem solved! Quite strange in fact, but as soon as I started to edit > existing text in a working plugin view, each quote on the same line turned > into a double quotation mark. Not sure if this happens because I use > TextEdit, even though I make sure the document is plain text with > command-shift-T before saving it. Anyways, those double quotation marks made > it impossible to use the documents as plugin views. As soon as those were > fixed, the plugin views worked as a charm in Pro Tools! I suspect this is one > of the Smart features of TextEdit, that I can turn off, I’ll look into that > now. Also, I found that even though the template adds the name of the plugin > in the top line of the document, you’ll have to remove this line to make the > document work. > > Best, > John André > > > > On 08 Jan 2020, at 21:57, Slau Halatyn <[email protected] > <mailto:[email protected]>> wrote: > > Hi John, > The default unicode works fine for me. Keep in mind that JASON text files are > extremely unforgiving with formatting and characters. There might be > something else going on. If you have trouble getting it to work, feel free to > send the text file to me and I can proof-read it. > Slau > > >> On Jan 8, 2020, at 1:57 PM, John André Lium-Netland <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Jimmy and Slau, >> >> Thanks for the feedback! I’ve started to experiment with this, and found >> that using TextEdit when crating the documents won’t work unless you choose >> to save the plain text document as Unicode UTF 16. The default setting of >> Unicode UTF 8 resulted in files that didn’t work as plugin views. Next >> challenge is that even though I create each line with all the correct >> characters, I still have problems, but I’ll keep on experimenting until it >> works. ;) I see that this not will work well with menues like those in >> Kontakt and Komplete Kontrol, since it’s not easy to know if the menu is >> open or not, but for simple pressing of buttons or to enter text values in >> text boxes, it will work just fine for now. For menues like those in Wave >> plugins, where VoiceOver read the content as soon as the menu is triggered, >> it will also work fine. Of course, I’ll install VOCR 2.0 when I have a newer >> OS sometime in the near future, since it’s a better solution as far as I >> understand. >> >> Best, >> John André >> >> On 08 Jan 2020, at 19:36, Slau Halatyn <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi John, >> >> Jimmy's response is correct but I'm just addressing the second part of your >> message regarding other applications. The plug-in views are specifically >> meant to work within the Plug-in window. The views are specific to the names >> of the plug-ins loaded and whose name appears in the title of the window. I >> think we toyed around with the idea of having it work in other windows but >> that opens a can of worms with a lot of potential issues so we shelved it >> for now. HTH, >> Slau >> >> >>> On Jan 7, 2020, at 1:39 PM, John André Lium-Netland <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi, >>> >>> 1) In the demo for the Plugin View feature of Flo Tools, Slau mentions a >>> macro for KM that will enable you to built a template that makes it easier >>> to build plugin views. I’ve looked through the whole dropbox folder, but >>> found no such macro. Does anyone have this macro? >>> >>> 2) I think I once heard that the plugin view feature also can be used in >>> other windows in PT or with other apps, is this correct? >>> >>> Thanks, >>> John André >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Pro Tools Accessibility" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected] >>> <mailto:[email protected]>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/ptaccess/3BE75F0F-D855-41F5-8543-CD255BF91D28%40a-pro-studio.no >>> >>> <https://groups.google.com/d/msgid/ptaccess/3BE75F0F-D855-41F5-8543-CD255BF91D28%40a-pro-studio.no>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] >> <mailto:[email protected]>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ptaccess/FB7CEF15-5007-410F-B81A-5A3E503BA7FB%40gmail.com >> >> <https://groups.google.com/d/msgid/ptaccess/FB7CEF15-5007-410F-B81A-5A3E503BA7FB%40gmail.com?utm_medium=email&utm_source=footer>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] >> <mailto:[email protected]>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ptaccess/692C017C-6066-4BB2-894B-5EBDDE64DD8C%40a-pro-studio.no >> >> <https://groups.google.com/d/msgid/ptaccess/692C017C-6066-4BB2-894B-5EBDDE64DD8C%40a-pro-studio.no?utm_medium=email&utm_source=footer>. > > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ptaccess/9B6954B4-782A-464E-B35B-6389D8B9DCDB%40gmail.com > > <https://groups.google.com/d/msgid/ptaccess/9B6954B4-782A-464E-B35B-6389D8B9DCDB%40gmail.com?utm_medium=email&utm_source=footer>. > > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ptaccess/7B380149-4998-4B12-8E34-5C5033FCF369%40a-pro-studio.no > > <https://groups.google.com/d/msgid/ptaccess/7B380149-4998-4B12-8E34-5C5033FCF369%40a-pro-studio.no?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/E84C71A3-BF8C-4477-8542-90FC5B87B04C%40gmail.com <https://groups.google.com/d/msgid/ptaccess/E84C71A3-BF8C-4477-8542-90FC5B87B04C%40gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/E8D611DE-5DF2-4102-995E-B39B0689A10B%40a-pro-studio.no.
