[Jsonar] OK, decision-making crunch time.

[HF]

Chris

HSC is very frustrating and there is a bit of a learning curve to be had here. They are not as straightforward as you might hope. I am using them with CT and so that might account why they are failing for me. But they are indeed suppose to work with CT. So you have to devote some time in order to make them work for you. I have yet to make an HSC set work for me in CT, but that is just my own experience. Phil who is the main creator of most of these sets I'm sure will answer all of your questions. I presume that there are others out here that have been able to use them successfully. Don't know anyone else besides Phil that all of the HSC sets work for. If they are working for folks, no one is saying so. Phil should be able to answer better than I if they work with CT or not. They have not for me as of yet. I'm sure that this will change in the future. 

Last time I used JSonar, there was no facilities for manipulating clips or selecting them. You were just regulated to selecting by just the from and through times. This is going to become more important when you have to actually edit multiple clips at once for example a multi-tracked multiple microphoneed 
drum set. There was also no support for AudioSnap as of yet. Scrubbing at sample level and dealing with zero crossings were easier to do in CT, not sure that you can do this in JSonar. Somebody please chime in here and let us know if this is possible. 

JSonar has stereo meters and CT does not.
JSonar uses native Sonar keystrokes. 

Work flow is subjective since I'm sure that certain things work faster in JSonar depending on what you are doing and vice versa. I won't state some of the obvious things for you since I'm sure you already know. Money, manuals etc.

Both are valuable and you might find that at a certain point you might wind up using them both. As for a machine, talk to folks who bought DAWS and there experiences with them albeit Dancing Dots or Sweetwater.

Hope this helps

HF
----- Original Message ----- 
  From: Christopher Bartlett 
  To: jsonar at jsonar.org 
  Sent: Thursday, December 04, 2008 3:22 AM
  Subject: [Jsonar] OK, decision-making crunch time.


  I have had one of those wonderful serendipitous windfalls that will allow me to purchase a dedicated DAW.  The major decision I have left to make is whether to make CakeTalking or Jsonar my access method of choice.  I've had a fair amount of experience with CT and played a bit with Jsonar a couple of years back.  Based on what I saw then and what I've read by following this list, it seems that Jsonar is a viable competitor to CT for those who are fairly knowledgeable about recording and digital processing, among which number I think I can classify myself.  

   

  But now that it has come time to make the final drop-dead decision, I do have several comparison questions.  My areas of concern are plug-ins, clip editing and access to Sonar 8.  I know that there has been some heroic work creating hot spot sets for many of the plug-ins that Sonar can use.  Do these hot spot sets provide as easy access as the scripting that has gone into CT?  The last time I seriously tried to use hot spots, I found the experience tantalizing and frustrating, and it got in the way of my work flow.  On the other hand, it sure looks like you guys respond far quicker to changing circumstances and that both the Jsonar scripts and the hot spot sets continue improving.  So for those who use Jsonar on a regular basis with the plug-ins and HSC, does the work flow really flow as smoothly?

   

  I haven't followed the detailed discussions about clip manipulation or the like with any concentration, so what is the state of play in Jsonar land where clips are concerned?

   

  And how stands access to Sonar 8?  Do we yet have access to any of the cool new features?

   

  Finally, what are areas where Jsonar does not provide access yet, or provides only partial access?

   

  One may ask why I can't do both?  The answer is simple; I'd rather spend time making music than keeping up on two semi-divergent development streams.  If Jsonar is as viable as I think it might be, it would be worth the learning curve time to get firmly on its development track and stay there.  It's not only a matter of cost; I'd want to make donations to the Jsonar development effort and to Phil for all the hot spot work if I'm going to use them; that seems only fair.  If I'm going the Jsonar route, then I'll go through Sweetwater or some place like that for my work station, whereas if I'm going the CT route, I'd use Dancing Dots.  So this is my dilemma, and I'd really appreciate feedback.

   

                  Chris Bartlett

   



------------------------------------------------------------------------------


  _______________________________________________
  Jsonar mailing list
  Jsonar at jsonar.org
  http://jsonar.org/mailman/listinfo/jsonar_jsonar.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jsonar.org/pipermail/jsonar_jsonar.org/attachments/20081204/8dded3b6/attachment.html>