AZSlow

Accessibility => Sibiac => Topic started by: azslow3 on July 03, 2017, 05:10:08 PM

Title: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on July 03, 2017, 05:10:08 PM
Sibiac is a set of accessible overlays for not accessible programs and plug-ins. That allows control such programs as accessible. More about Sibiac. (http://www.azslow.com/index.php?topic=437.0;imode)

Note: Wiki (https://reaperaccessibility.com/index.php/SIBIAC_add_on_for_NVDA) is simpler to read and understand then this site. The difference is like between well written book and pure technical specification.

Installation instructions. (http://www.azslow.com/index.php?topic=428.0;imode)

Currently supported programs:
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on November 21, 2018, 05:32:14 PM
Change log:
23.05.22 - 023p2b8
  NVDA 2022.1 support

19.02.20 - 0.23
  NVDA 2019.3 support

21.02.18 - 0.22p1
  Fix: not English usernames 

24.12.18 - 0.22
  New: EZ Drummer, Howard Benson, NadIR

28.11.18 - 0.21b3
  New: Melodyne shortcut preferences

26.11.18 - 0.21b1
  New: bridged plug-ins support in REAPER
  New: mic settings in Addictive Drums 2

23.11.18 - 0.2014
  New: SynthMaster player

20.11.18 - 0.20b3
  New: preset loading for Sforzando and VCSO2

19.11.18 - 0.20b2
  New: really complete operations in EZMix 2

18.11.18 - 0.20b1
  New: complete operations in EZMix 2
  Change: Sibiac tries automatically maximize FX window

13.11.18 - 0.19b3
  Change: EZMix 2 and GTune are using NVDA text instead of OCR

12.11.18 - 0.19b2p1
  Fix: favorites adding announcement in EZMix 2
  Fix: demo mode handling in EZMix 2 

11.11.18 - 0.19b2
  Fix: OSARA audition during working inside Sibiac overlays

10.11.18 - 0.18b5
  Fix: arrows in Zampler modulation table
  New: EZMix 2

5.11.18 - 0.18b4
  Change: Melodyne, Main mode added
  Fix: buttons in Melodyne Shortcut preferences
  Fix: Tools in Melodyne Essencial
  New: Spanish localization in Melodyne
  New: Synapse audio Zampler VST in REAPER

4.11.18 - 0.18b3
  Fix: false warning when the interface really on the screen
  Fix: amplitude editing in Melodyne

3.11.18 - 0.18b2
  Fix: bug in text editing controls
  Change: names are changed to standard for Melodyne
  Change: tool parameters are now after Edit virtual control
  New: audition for direct switching tools by shortcuts
  New: pitch modulation, pitch drift, time and attack speed tools
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: Outsidepro on December 12, 2018, 06:42:32 PM
Before I should start my message, i would wanted apologize if my message has been written to wrong topic. I just not found appropriate topic so i've decided write here.

Before i want say thank you for great delopment for producers who needs to get accessibility in VSTS! That's really great idea, realisation, and performance! It's also allows to avoid use JFW with NKPro scripts where too much many key commands and slow performance vs SIBIAC works fast, accuracy and proposes the pseudo-interface. Thank you!

I might wanted to propose you to participate in development for. I am programming a little, also I have the friend wwho is programming too and he makes it better then me. Also he loves explore new synths, plugins and etc. He uses Reaper. We can help SIBIAC to get support new plugins and synths. We've wrote some stufs for simple access to some plugins and we want to move these to SIBIAC. But now it has a few difficult problems:
1. You've removed the sibiac.exe utility that might help us to provide develop a new plugins. Also there's no guides to use it and add new coordinates and data. May you publish it here in appropriate topic with short help for?
2. At last version SIBIAC got splited code with main implementations and plugins implementations, but it's still needs to be imported into appModule file... I know Python bad but i think it wold be realised as dynamic import from plugins folder maybe?
3. May we contact via some methods to to discuss about?


Thank you for response in advance!
And excuse me if my english is bad, my native language russian. :)
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: Grisha on May 25, 2019, 01:21:18 PM
Hello Aleksey! I want to make the request about kontakt5 or kontakt6. is it possibly to make it more accessible through Sibiac? I use golden cursor for adding instruments and libraries to kontakt. it would more comfortable to use Sibiac instead golden cursor. Thanks for this great accessible addon!
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on May 25, 2019, 02:42:51 PM
For Kontakt there is Kontakt Access from access4music. In addition all NKS keybaords support accessible operations now. I do not say Sibiac will never support Kontakt,
but for sure that is not going to happened soon.

Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: Druify on December 10, 2019, 09:33:46 PM
Hello,

are you planning to upgrade Sibiac for NVDA 2019.3? I started to enjoy its funcitonality, but it is incompatible with Python 3 and NVDA.

Best wishes,
Druify
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on December 11, 2019, 12:23:13 AM
I will check tomorrow.

EDIT: 2019.3 is not yet ready, but thank you for making me aware. I will try to find time and update SIBIAC before it is released next year.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: Tomecki on February 10, 2020, 03:04:00 PM
Today NV Access released NVDA 2019.3.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: Outsidepro on February 10, 2020, 06:51:07 PM
I've got last NVDA release too and SIBIAC did not compatible with. We will waiting new version! :(
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on February 19, 2020, 11:03:45 PM
Update version is uploaded.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: Outsidepro on March 12, 2020, 07:39:40 AM
Oh, i've just forgot to tell you my thank! :) Excuse me!

Also, I may show you a plugin which needs be accessible and it can be usefull for any sound producer which works at home studio and have no monitor acoustic system... I'm talking about RealPhones plugin by DSoniq https://www.dsoniq.com/ (https://www.dsoniq.com/) May you explore that?
Thanks in advance! :)
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: erion on March 22, 2020, 11:09:07 AM
Hello,

First of all, thank you very much for Sibiac, and for the new update for NVDA 2019.3.

I've encountered a bug in some applications, where the object nav (NVDA+numpad numbers) via the desktop keyboard layout exposes only one item.

You can verify this, for instance, in Native Access, where with Sibiac enabled, I only see a toolbar and the first item (a search box) in it, while with the add-on disabled, all the controls are visible as expected.

Could you please look into this?

Keep up the amazing work!

Erion
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: theslyprofessor on March 26, 2020, 04:19:05 AM
Hello,
I am teaching a student who is visually impaired. She uses Logic on her Mac but I want to teach her Melodyne. I heard that Melodyne has SIBIAC support. Does it work in Logic on Mac?

Thanks,
Nakul
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on March 28, 2020, 12:16:07 AM
Sorry, but SIBIAC works on Windows platform only.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: Outsidepro on May 10, 2020, 11:57:43 AM
I just wanna propose you to change the method of plugin definition from getting the plugin name from listview to real DLL name. When I'm working with hard projects my CPU has often overloaded, and NVDA cannot process the listview with the following log message:
ERROR - eventHandler.executeEvent (11:57:52.933) - MainThread (12688):
error executing event: gainFocus on <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x074A0EF0> with extra args of {}
Traceback (most recent call last):
  File "eventHandler.pyc", line 155, in executeEvent
  File "eventHandler.pyc", line 92, in __init__
  File "eventHandler.pyc", line 100, in next
  File "NVDAObjects\__init__.pyc", line 1102, in event_gainFocus
  File "NVDAObjects\behaviors.pyc", line 611, in reportFocus
  File "NVDAObjects\__init__.pyc", line 988, in reportFocus
  File "speech\__init__.pyc", line 469, in speakObject
  File "speech\__init__.pyc", line 506, in getObjectSpeech
  File "speech\__init__.pyc", line 377, in getObjectPropertiesSpeech
  File "baseObject.pyc", line 42, in __get__
  File "baseObject.pyc", line 145, in _getPropertyViaCache
  File "NVDAObjects\IAccessible\sysListView32.pyc", line 435, in _get_name
  File "NVDAObjects\IAccessible\sysListView32.pyc", line 359, in _getColumnLocation
  File "baseObject.pyc", line 42, in __get__
  File "baseObject.pyc", line 145, in _getPropertyViaCache
  File "NVDAObjects\IAccessible\sysListView32.pyc", line 222, in _get__columnOrderArray
  File "winKernel.pyc", line 212, in virtualAllocEx
OSError: [WinError 8] Недостаточно ресурсов памяти для обработки этой команды.
When this error has ocurred SIBIAC doesn't defines the plugin and doesn't activates there.
A few time past I had reported this bug to NVAccess but it is still didn't fixed. Perhaps I'd reported this in 2015th year. Seems this error cannot be fixed basically.
Unfortunately i don't know Python but a few time ago me and my friend have written the clicker in PureBasic. There we are used the WinAPI hooks for creating and destroying the windows in process. When new window has been created we get the process name of created window and load the appropriated file with the same name as process name who has created this window. It is works better because the DLL name not changeable instead of name from SysListWiev32 when i can rename it there.

Thanks in advance!
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on May 11, 2020, 03:02:29 PM
We have spotted the problem only last week. Thank you for the information it is not concrete system dependent and there is little chance it can be fixed in NVDA.

Unfortunately I do not know any method to get DLL name for a window. The process is REAPER, NVDA already use that to select overlay module. Embedded window
is created by some function within DLL, but I do not think Windows architecture supports such lookup. Most frameworks dynamically create Class names, so they are
all JUCExxx or Pluginxxx. That is why I use ListView for detection.

I will try to find some solution.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: Outsidepro on May 14, 2020, 11:07:11 AM
I have ready to share you the sourcecode of our clicker, but it written in Purebasic. But there is the solution of.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on May 14, 2020, 01:31:21 PM
Thanks, but for the reason I have mentioned before I doubt that approach will work in the REAPER FX window. This window is a container, it display interfaces from different plug-ins. The process is still REAPER. Finally some plug-ins, for example Waves, are loading throw one single shell DLL.

But can you write me the link of your bug report to NVDA? May be we can bump it.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: erion on May 15, 2020, 11:21:36 AM
Hello,

I just wanted to write a quick message to thank you for the new 0.23p1 update, which fixes my one object per window issue via NVDA object nav.

As always, thank you for your continuous support!
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: x0 on June 21, 2020, 02:11:58 AM
Hello. I am reporting a critical bug in the add-on that affets those of us using any NVDA releases other than the full ones. Back when I was on 2020.1 rc1 this happened, and also now I'm on 2020.2 beta 1 this happened. If the version info that you happen to be parsing from versionInfo.version string contains anything that cna't be converted to an integer, it will cause an import error of SIBIAC and effectively render the Reaper window unfocusable. I tried patching this with a try catch with a manual population of the list but then I started getting index errors. Just letting you know how you should be building the version info for NVDA so this will work, this is how add-ons are supposed to check version info. The versionInfo module has three attributes called version_year, version_major and version_minor. Those should be used in place of the list indexes. If you still want to build the list as simply [versionInfo.version_year, versionInfo.version_major, versionInfo.version_minor], there is one more thing you should look at in the compatibility if statement. When checking for version_year being 2019 and version_major being less than 3, you end up calling the wrong index for 2019. Following is the patch I made to lines 24 and 25 in AppModules/sibiac/__init__.py using the list creation pattern so not much else had to change. This lets it work as far as I've seen, it definitely isn't causing such propagated import errors that I can't focus the reaper window.
nvda_version = [versionInfo.version_year, versionInfo.version_major, versionInfo.version_minor]
if nvda_version[0] < 2019 or (nvda_version[0] == 2019 and nvda_version[1] < 3):

Best regards
x0
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on June 22, 2020, 11:04:39 AM
Thank you for reporting, it will be fixed in the next release (I will send you the link to test version in PM).
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: x0 on June 22, 2020, 05:12:57 PM
One more suggestion for the next release, though I'm not sure how hard this is to implement on your end. On platforms that have it, I.E. most versions of Windows 10, could you take advantage of the UWP OCR? It may yield better results and I think the overall processing time is less. Perhaps this could be implemented in a way that if it is available it would be used first which would then mean you don't have to have the sibiac_ocr add-on installed, but if it isn't then whatever failure you do when the OCR add-on isn't present still applies, for those on older versions of Windows.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on June 22, 2020, 05:59:50 PM
Current OCR is slow just because I use it very inefficient way. Changing that is long time in my list.
Is UWP OCR better for my purpose is an open question, I have not checked yet. Note that really bad results are coming from parsing very bad text, sometimes barely if at all readable for sighted users. In most plug-ins text is just historical part of the interface and the trend is making it smaller till no longer recognizable, just as a decoration. For example an older version of one plug-in I have overplayed still had text for banks, but newer version display pictures instead.
The trend is present for example in envelopes. Old plug-ins had Attack, Decay, Sustain  and Release controls, some without any resulting graphic. Then they have replaced all that with one graph of the envelope, with points movable by mouse. But in many cased there still was ADSR characters. These days some plug-in do not even mark the graph "Envelope", assuming everyone understand that by the graph form. 
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: x0 on June 27, 2020, 03:44:21 AM
Can anything be done to ad accessibility to Kontakt 6? I'd like to be able to access things like batch resave and load presets without paying for access4music scripts. I understand some stuff just won't work, like in-window browsers, but having access to batch resave and conversion of wav to ncw and stuff like that would be great. It's fine if it's just with Kontakt and not in Komplete Kontrol since you probably have no real way to tell what's loaded in Komplete Kontrol.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on June 28, 2020, 09:28:30 PM
I think access4music is the right way to organize things. I am not going to overlay plug-in for which payed scripts from access4music exist, sorry.
Title: Guitar Rig 6
Post by: michael.vogt on December 12, 2020, 05:06:05 PM
It is very helpfull to be able navigate through presets within guitar rig 5.  Within guitar rig 6 it is no longer possible. Very handy: within the stand alone version, I can select the categores, filter, search form, select presets, save and load presets - just with screenreader jaws. but in plugin instance, there is no longer any way to navigate through presets. Is there a chance that you can implement the navigation to select the categories and to select presets to be able using guitar rig 6?
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on December 12, 2020, 09:55:24 PM
Not within next weeks, sorry.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: nguyenvanthanhnghia on April 20, 2021, 01:43:15 PM
Hello. First of all I thank you for creating this amazing tool.
Are you planning to add Real Guitar by Music Lab to the list of accessible plug-ins? It is a great guitar vst
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on April 20, 2021, 04:18:24 PM
Hello. I don't have Real Guitar. And I am busy with other activities for more then a year, so there was no recent SIBIAC development.
Just checking the interface, I think it is possible to overlay it. I mean unlike some other plug-ins that is manageable. At the same time there was some announcement for JUCE framework accessibility and I guess Real Guitar interface is JUCE based.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: El Crack Loko on July 06, 2021, 11:17:51 PM
Hello. NVDA 2021.1 is here very soon, so SIBIAC will no longer be supported by NVDA because of Python dependency updates like WxPython 4.1.1. My question is if we will have some kind of update, for example, at the moment having the RC2 of NVDA 2021.1 I am unable to make use of SIBIAC; there is also the permanent message from SIBIAC saying that it is not able to read all the contents of the window. That always comes out, even if everything is well configured and there are no window overlays. I have seen various comrades on various computers; I don't know if it would be impolite of me to ask that if you don't have the corresponding time, you put the project free on JitHub, so that other programmers can also collaborate. In the end, you are the one who decides whether or not to approve such contributions from JitHub. A thousand apologies for the inconvenience, Friend Azlow, and sorry for my terrible English, I'm Latino jajajajaja, although that's no excuse for me to learn the language jaja.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on July 07, 2021, 09:32:52 AM
Hello. I will check the compatibility issue. Note that SIBIAC in most parts is GPL licensed software, so it can be modified by anyone independent from me. Also your English is good for me, since I am Russian. lol.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on July 07, 2021, 04:18:04 PM
I have quickly checked. For 2021.1 you need re-download SIBIAC OCR and use test version of SIBIC: https://www.azslow.com/index.php?action=downloads;sa=downfile&id=69
Both should report they are compatible with 2021.1 and so can be installed, no other changes so far.

I have just opened REAPER with EZDrummer and SIBIAC was still able to work with RC2, without changes in the source. So, if it does not work please provide more details with which software you try to use it.
For overlapped windows, so far every time I was checking remotely on someones computer there was external popup window or window was not sufficiently big to fit the whole content. Sorry, to fix something I have to reproduce that first. I can connect to you using your proffered method,  for checking warning issue Skype can be sufficient. For anything else I prefer remote control like TeamViewer or AnyDisk. Let me know in PM when and if you have time.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: El Crack Loko on August 23, 2021, 07:06:09 PM
All excellent, I am using Sibiac with NVDA 2021.1 Beta 1 and Windows 11. I only have one question and sorry if I ask it here since I did not find the edit box in the thread corresponding to the topic. It's about Addictive Drums. Where can I activate the battery caps? You know, those ornaments that Toms make. And why when I activate the preview of a Preset, it does not play with the one corresponding to the genre. Do I have to activate / deactivate something? The only way to play the new Preset as genre is, is by setting it to start with that Preset when the Plugin is opened, and then closing and opening Reaper. I'd appreciate a lot if you could help me, bro.
By the way, I had not taken the time to thank you enormously for the compatibility you made with NVDA 2021 and with the RC / Beta versions. I have heard that there was a modification of your plugin for the free Steven Slate Drums 5.5 Plugin. Why don't you implement that modification in your official plugin? Or where I could prove it, if you will let me know.
Take care brother, that you are well.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on September 10, 2021, 04:13:59 PM
Sorry, I probably have not understood most of your questions. AD supports up to 18 kit peaces. Last 3 are so called flexi, normally assigned to unusual sounds. AD interface has Beats and Gallery sections. These are not covered by SIBIAC, I guess that is the reason you can't change what is played by preview.
Steven Slate is not covered by SIBIAC. In fact there is other plugin which covers more plug-ins. For technical reason SIBIAC can't be used in parallel with other related NVDA plug-ins, so that other plug-in developer has incorporated SIBIAC in his own project. There is no concurrence nor conflicts, it is just forced solution till we find different approach. Follow RWP mailing list where you can download that plug-in, for some reason it has no own web site nor other web based fixed location I can reference here.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: El Crack Loko on March 27, 2022, 06:33:30 PM
Hello Friend how are you? Thanks for the information provided, in the end I never joined the RWP list since I am a Spanish speaker and my English proficiency is nil jajaja, so it would be a pain (whatever haha) to be translating all the messages all the time. weather. I want to apologize for coming here to ask you for things because NVDA or rather NV-Access again broke compatibility with all plugins in its version 2022.1 so all plugins were unusable. Dude, tell me if you can get Sibiac to keep working on this NVDA version, it's still in the Beta phase by the way. And also ask what happened to the development of Sibiac, my greatest wish, is that this complement does not die, please. IF you need any financial incentive to go ahead with this, or if you have to pay, please let me know to raise some money with some friends and send you for some beers or whatever you need, if you drink alcohol jajajaja. By the way, I just remembered that you are Russian. I don't want to get into the situation in the country but I just want to say, if you need anything, we are here to help with whatever we can. A hug from Ecuador🇪🇨 South America
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on March 27, 2022, 09:21:36 PM
Hello. I will check the compatibility with NVDA next days and I will let you know when SIBIAC is ready for it. For RWP, there are many people which use automatic translation there. Yes, from time to time that produce misunderstanding. But all members understand that and so that is never a problem. RWP is international,
For SIBIAC, the development is just paused. The problem is not money but time. I with Gerad have created solution for Behringer digital mixers, so they can be controlled convenient accessible way and also provide voice feedback when you operate the unit itself. I mean the community was always preferring analog mixers since digial mixers was not accessible. And so we have decided to do something in that direction, Gerad plays live and digital mixers has many advantages like quick scene changing and build-in effects. Using computer with an audio interface and throw the DAW monitoring on stage is an extra peace of real-time equipment which can fail, analog mixer with hardware effects is expensive, heavy and a bit outdated way. By the way, we was successful. Some aspects of particular devices are still not covered, but almost everything  for Behringer X18 and X32 Producer is covered.
I am still Russian citizen, but I live in Germany for more then two decades. And fortunately current situation does not hit me nor my family. But sure, mentally all that is hard to perceive.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: El Crack Loko on March 27, 2022, 11:43:30 PM
Thank you for responding to my message with everything I mentioned. I think that the RWP community is also a good way to find out about everything that is being developed for us around accessible music production, right? or they only make requests about Reaper, I mean, because of the RWP thing.
Forgive my ignorance, but when you refer to Behringer digital mixers, I know the brand by the way, they have been improving their Audio Interfaces lately, what do you mean specifically? to Plugins of emulations like those of the analog console SCL 4000? I mean, I would consider that a digital mixer, and I know that Behringer has good consoles. Or maybe it is that Behringer has released a digital console as such where it has its effects incorporated as usual in consoles.
I am glad that this Russian stupidity is not affecting you and your family, I am very sorry for the citizens who have to pay the piper for a human being who came out privileged with such power. Oh well. Let's hope this happens soon, a big hug. By the way, did you say Gerad? Another Russian developer?
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on March 28, 2022, 12:44:30 AM
Behringer is famous for developing cheap staff. They produce X32, which is related to Midas M32, but cheaper. Since then they have made smaller versions of X32 and even cheaper stage box format mixers, X12 to X18. The sound quality is not at the level of top devices, but it is better then in cheapest Xenyx analog mixers. The price is also in-between. These devices have everything on-board, including effects. There was already text based controlling solution, but we have developed user friendly solution which also provide speaking feedback from device.
RWP primary target is REAPER, but all other accessibility solutions are discussed there as well.
Gerad is and always was in US. I have started develop SIBIAC for him, at the beginning for Sonar, we have switched to REAPER later.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: clapmauricio on May 23, 2022, 12:41:39 PM
Hello, good morning here in Brazil!
I am a SIBIAC user and, now, I don't know how download a compatible version with NVDA 2022.1.
Can you help me?

Congratulations for your work, it is very important to me.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: El Crack Loko on May 23, 2022, 01:19:25 PM
Hi, friend. I'm not AzLow, but I hope my answer can help you. If it works for you, go to the path %appdata%\nvda\addons (you can do it by copying what I wrote in the run menu with Windows+R or by going to any folder in your file explorer, pressing F4, deleting what is there and pasting what I wrote and pressing enter)
In this path, look for the sibiac folder, enter and open the manifest.ini file
Change lastTestedNVDAVersion = "2021.1" to lastTestedNVDAVersion = "2022.1.0"
Do the same with sibiac_ocr. I hope I don't annoy developer AzLow with my unwelcome reply. Let's always remember to use the plugins from their official sources and if it is in our possibilities, support the economic development of our plugins to encourage the development of more tools for us as producers. Let us remember that, if things stop developing, we are the ones affected. I really feel sad that this project is not going ahead, but well. Here we follow, at the foot of the canyon, an Ecuadorian saying. Greetings to Brazil friend and namesake Mauricio. From Guayaquil, the pearl.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: clapmauricio on May 23, 2022, 04:31:31 PM
Thank you for your help. Now it works again.
I am here to help the comunity, too. Together, we can make the project alive. I am not talking about Sibiac only, but about all important tools.

Thank you again, El Crack Loco.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on May 23, 2022, 11:28:20 PM
I want to say several words why this project is a kind of frozen...
First of all, there is LBL. It is a project with similar approach and it is active.
Second, since I have a house I am in permanent renovation which I mostly do myself. And there is garden to organize. I have almost no experience in these activities, but I have a lot of fun doing that. I am programmer. While SIBIAC and my other projects  are my hobby, that is still programming. I think it is good to do something unrelated to primary activity, also from health perspective. Last years I start to notice that sitting up to 16 hours in front of monitor every day is not good.
Third. There are other projects and they periodically have priority. For example I think the first truly accessibly digital mixer solution is more important that one or two additional accessibly plug-ins.
Forth and probably most important. From the beginning on, I knew that SIBIAC approach in its current form is not really the way to go. It should be possible to recognize an interface preferably completely automatic and at minimum semi-automatic way. I mean any interface of any program. I am convinced that is possible. I also think that is the only safe way in general. It is impossible  convince all developers write accessible programs, that is not going to happened. In addition writing a program with modern interface which is good for sighted users and accessible at the same time is almost impossible. Standard accessibility APIs are disaster, the way screen readers use them is even worse. I try to move in the direction which I think has future, but that needs huge knowledge and experience in graphical recognition. I need to learn these topics before I can apply them. That takes time.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: clapmauricio on May 25, 2022, 12:45:05 PM
I wish the best for you. I can understand you and can imagine the dificults of a busy life.
Finally, I hope you be fine soon. Thank you for all, from a brazilian fan.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: samuraijack on May 25, 2022, 09:48:43 PM
Does anybody by chance have  a link to this LBL project? I can't seem to find it :)

Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: El Crack Loko on May 26, 2022, 12:10:30 AM
Hi, I can't find it either. I found something in groups.me, but no link to see what's new or something from the project
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: clapmauricio on May 26, 2022, 01:08:28 PM
lbl: http://reaperaccessible.fr/archives/LBL%20Add-On%20For%20NVDA.zip
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: El Crack Loko on May 26, 2022, 09:00:21 PM
Friend Brother; thank you very much for this. Do you know where I can read all about this LBL project? When was it created, who made it, any of its history? What does LBL mean? Etc. I would like to donate if possible and do tutorials on the Youtube channel of Accesible Music Production, the group where several Spanish-speaking blind producers meet and help each other, it's a great thing to have found this. As I read in the readme, is the latest version from February 6, 2022? But in the Google date.txt of Groups.me, it shows that its last modification was on May 22, 2022, what happens is that I can't find a link to download it from there. Thanks for the Reaper Accessible in French page, you can always learn something from other communities, too bad it has audio tutorials and they are in French, since I don't know the language.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: clapmauricio on May 28, 2022, 02:14:44 PM
Sorry, my friend. I don't have more informations about LBL...
Anyway, Sibiac has been updated.
Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: azslow3 on May 30, 2022, 09:18:54 AM
LBL supports several plug-ins when they are used in REAPER. So it is a project in the same direction as SIBIAC. For technical reasons LBL include SIBIAC but overlay some additional plug-ins. The list overlaps, some small overlays originally supported by SIBIAC work different way with LBL.

From my knowledge LBL is supervised by Lee. There is no dedicated web page, also for some reason Lee has difficulties with this forum. All questions about LBL can be asked in the RWP mailing list, new versions are announced in the list as well, with corresponding links. The first time the project was made public was around the end of 2020 and it is in continuous development.
I think authors of LBL know how to program in Python so the code is good written and organized.

Title: Re: Sibiac: Single Image Blob Interface Accessible Control
Post by: Druify on September 08, 2022, 09:05:12 PM
Hello,

thanks for the information about LBL. I understand that you choose other priorities.

However I discovered that SIBIAC is slowing down strongly when I use Reaper with Izotope VocalSynth2 VST3. That is accessible without SIBIAC, but somehow it seems to try doing OCR.

Now I'll try LBL.

My setup with Reaper in current version 6.67: SWS Extension, Reapack all repositories from reapack page, OSARA, some tools by Access4Music that use OCR as well and are only activated when I need them. Screenreader NVDA in current version.

Best regards,
Druify