Rayzoon Technologies LLC

[non_drummer]

I'm not clear on this. If I'm creating a song with JS and then save it as a 'project' in my host (I'm using Reaper for now), I can come back later and open that project up and it's got everything in place. Time sig. changes, tempo changes, etc. If I instead save that same song in JS and then open it later, everything will look correct in JS, but Reaper will open defaulted to 4/4 time and 120 bpm, and playing back the song things will go downhill almost immediately.

So what are the instances where you'd want to save the song one way vs. the other? I know very little about this stuff, but just trying to look at it logically I would say that as long as you're never going to switch hosts, it would make sense to save the song to the host program. I don't know why, but I'm assuming that one host can't read another host program's saved projects, so if I decided to use Sonar I'd have no way to open any of my Reaper project files. Is that true?

Since I don't know enough about this stuff, I've been saving to both Reaper and JS, but I'd like to understand things a little more.

[Azimuth]

If you save the Reaper project, all of your song info is saved in the project and then reloaded correctly when opened again in Reaper. If you save the song in Jamstix, all time signature and other data is saved within the .j2d file and then could be sent to someone to be used in any host. All they would have to do is insert corresponding time sig indicators in whichever DAW they use.

It is also good the have a backup of your song in .j2d format in case you need to recover it in the future.

[non_drummer]

Wow, I actually got something right the first time (although I hadn't thought of sending a song to someone else so they could open it regardless of the host they were using).

Thanks.