Hello everyone! It is the first time that I am part of this list as I think everyone here does not know me, I should introduce myself. My name is Gabriel Benhur Schuck, I'm from Brazil and Counseling to join this list by Victor Tsaran to ask him to help solve a few problems I have with both scripts and sonar, as if they were in conflict. Still could not figure out what might be happening and, as Victor said, because a lot of hardware / software configurations that can be made, it is difficult to JSonar or other developers are able to determine what would be recommended. For this reason, I am asking for your help, as it has become a task of my day to day doing music production and the use of software that do not waste my time with interfaces unfriendly and inaccessible, such as Sonar. I was using version 6.0, and not be working with the asio of my external card, migrated to version 8.0. I downloaded all the scripts correct and I opted for automatic installation. Until then everything was working perfectly. But suddenly, I started having problems when playing virtual instruments in real-time execution. began the message sonar audio dropout. I did all the suggestions found in the program's help, but to no avail. I chose to reinstall the software and also the scripts, but I could not run the setup Wisard and activate the JSonar control surfaces properly. When I tried to re-enable the file before running Sonar Producer 8.0 accessibility mode.reg , said it was already active. In sonar, going into options and then click Control surfaces, appeared the JSonar active control surfaces. Plugins returned to work, but it did not take long for the performance of the sonar had before. Now, the current situation is as follows: When I open a new project in the application that generally has four blank tracks and you want to insert a VSTi plugin with the option insert> soft sint, the script does not follow this change and states that still has four tracks on the project, thus ignoring what had been added. This sometimes happens, sometimes not. When it happens, the plugin (any one that is) does not play. But when the script recognizes, then they usually work, although it is always necessary to manually adjust the output of a midi track to the plugin, which until then was done automatically. I'm using an Acer Aspire One netbook with Windows XP. Intel (r) Atom (tm) 1.60GHz with 2 GB ram, 160 gb hd and sound card usb PreSonus AudioBox. Jaws 12.0.1158. Maximum display resolution set to 100 X 600 pixels. 32-bit color quality. Obsefvação: The reason I made the migration to Sonar 8 was precisely because it offers better support for asio most boards that support this feature, as is the case of AudioBox. I tried to check out other versions, but can not work with the board in this mode and nothing worked to solve the problem. Moreover, if the script is presenting these strange behaviors with the sonar, it's impossible to know for sure if the JSonar Control Surface is set up correctly. I hope you can help me, because I had to use it much. Thanks, Gabriel
_______________________________________________ Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. Jsonar mailing list [email protected] http://jsonar.org/mailman/listinfo/jsonar_jsonar.org
