• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Recording in Jamkazam- Need Help
#1
We are a small chamber choir trying to record our sessions. 2 situations I need help with.

1. 4 people on the recording. 3 out of the 4 tracks recorded successfully with a full take. The last person track however only recorded 29 seconds of the take. What happened? How do I fix this for the future?

2. Tried to record in another session. There were 11 in the session. When trying to record it said that there was another session processing and I could not record. What does that mean if no one else was recording and nothing had been recorded that day at all. 

Thanks!
  Reply
#2
(10-05-2020, 09:57 PM)bstantonChoirSchool Wrote: We are a small chamber choir trying to record our sessions. 2 situations I need help with.

1. 4 people on the recording. 3 out of the 4 tracks recorded successfully with a full take. The last person track however only recorded 29 seconds of the take. What happened? How do I fix this for the future?

2. Tried to record in another session. There were 11 in the session. When trying to record it said that there was another session processing and I could not record. What does that mean if no one else was recording and nothing had been recorded that day at all. 

Thanks!
We've had awful experiences with recording in JamKazam. But what we HAVE figured out is that we can each start up an app like QuickTime and each record ourselves on our own computers as we play together. Then we pop all those recordings into Audacity, line them up (don't forget to have everyone include an audible count-in on their recording to make it easy to line up), and mix as you please. Recordings made like this are much better than what we get from JamKazam directly because we have total control over the inputs. Setting recording levels in JamKazam never works as we expect it to, and mostly we end up with tracks that peak out.

"Another session processing" usually means that something you previously recorded got "stuck" before it finished processing. That could have been just a software error, or it could have been because you closed the app before the processing was finished. Probably best to leave it open after you record even if you aren't in a session to avoid that problem. Remember, this is all "free" and sometimes there just isn't enough processing power to deal with all the requests in a timely fa$on :-)

Cindy Harris
Pittsburgh, PA
  Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)