no. If you do that, then nobody is even going to have any idea if they are going to clip or not. Then you have more people going elsewhere for their scripts.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Victor Tsaran Sent: Sunday, August 08, 2010 7:37 PM To: JSonar -- JAWS Scripts for Sonar discussion list Subject: Re: [Jsonar] About the next version of JSonar Hi Nicki, I just fixed the track selection issue. I am not sure what to do about peak meters because we have not reliable way of making sure consistent reading. I am thinking that perhaps we should eliminate this function altogether since it is so unreliable. What do you all think? On 8/8/2010 2:11 PM, Nicki D wrote: > Hi Vic and all, > I don't know if anybody else is experiencing any or all of these but > this is what I have been going through lately-- > > 1. There seems to be stability issues with selecting tracks. When I > am on a track and wish to select it, I press "ctrl+comma". More times > than not Jsonar will say "not selected" I try repeatedly and I > continue to hear "not selected" I maximize the windows (both parent > and child), move the cursor up and down to different tracks and come > back to the current track and/or sometimes left and right to different > columns before I finally get to select the current track and hear > Jsonar say "selected". Now I am thinking ok the track is now selected > but when I try to confirm this by doing "ctrl+shift+comma" it is a > different track that was selected and by that time, the current track > has shifted to a different track. For example, I would be on track 19 > and wish to select track 19. At the end of all this process, even > though I read the current track with "insert+up arrow" to confirm the > track I am on before selecting it, somehow things get shifted and I > end up selecting track 2. So it has been a constant struggle to select > tracks. I don't remember things happening like this before. 2. When I > try to open the track property dialog so that I can assign > bank/patch/browse for patches, etc, I will for instance place myself > in the patch column and press the "application" key on the PC > keyboard. I will arrow to track property menu item and press "enter" > on it. More times than not I will instead end up in the select color > dialog box and not where the other things, e.g. bank select, etc, are. > I have to repeat this process twice or more before I can get lucky and > be placed in the tracks property box. 3. The peak meter say key > "alt+m" more times than not will read the first track rather than read > the peak value when I am preparing to record by arming a track and > trying to adjust levels. It'll sometime read the peak value but you > just don't know when it'll decide to read it. > > Are there workaround techniques for these issues that I am not aware > of? > > Despite all that, JSonar is still an extremely great product and > thanks for the great work to you Vic and the entire dev team. > > Thx, > > Nicki D > > > > _______________________________________________ > 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 > -- ------------------------------------------------------------------------ Check out my new album on iTunes at http://ax.itunes.apple.com/us/artist/victor-tsaran/id344507896 ------------------------------------------------------------------------ _______________________________________________ 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 _______________________________________________ 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
