Jamstix 3 RC1 - Now Available

[Ralph @ Rayzoon]

[b:6b01e26824]R Green[/b:6b01e26824]: you must be looking at an older manual. The one that comes with A11 has:

- the typo fixed
- middle 8 in the song builder section
- rudiment generator on page 38


[b:6b01e26824]Drk1:[/b:6b01e26824] yes, toggling the liveloop MIDI key is now pretty pointless because JS3 will jump to wherever the host is at that time. I'm thinking about changing this so the toggle affects the repetition behavior:

- toggle on: parts are repeated forever just as it is now
- toggle off: at next bar end (or part end?) JS3 will advance to the next part and then repeat them as specified in reps (i.e. normal arrangement play)

What do you think?

[drk1]

Yes I think that sounds fairly logical the only issue I can think off at the moment if you wanted to jump back to a previous part or even forward then with no midi key this wouldn't be possible however I'm not sure if you have ever intended JS to act in this way.

I have a couple of numbers in which I have say 3 or 4 parts which are variations of each other and with the midi keys I can then switch between them as the feeling takes me.

I'm sure there may be other ways of doing this sort of thing - just haven't thought of them yet.

I'll spend some more time on thinking about this.

thanks

[bakiki_]

Sorry if there is an obvious answer to this question. But where can I download the lastest J3 manual. I can't remember how I downloaded the first version weeks back. I can't see it when I download A11?

Thanks

[Ralph @ Rayzoon]

The manual is located in the \data\docs folder of the Beta Install.

[bakiki_]

Thank you


I've just started playing with the rudiment tool and I love it. It opens so much more intentional creative direction. However I do think that adding a drop down list for the sequences is a must. However, it would work better if you could just type out a list on a notepad document then access it through the drop down.... That way it gives us an option to create a personal library of options that we don't have to keep pasting in each time....

If anyone agrees please back me up here.....

[lucky]

Hi there,

not been active here for a long time due to other priorities. But picked up on Jamstix again and tried the betas of Jamstix 3. The latest beta 11 causes Cubase SL2 (I know, it’s sad) to hang while loading Cubase. The previous betas didn't have this problem, but beta 11 stalls loading of the program.

On a side note: I'm curious about the new styles and/or drummers. Any change there will be more Jazz, Funk & Jazz-rock stuff in there?

Call me lazy, but I sure would love to see more 'lock & load' songs for some straight (live loop) jamming. There are already so many styles, drummers and options, that as a bass player I feel a bit lost. Which style to which drummer and with what variations?! This might sound spoiled, as you give us so much, but I just want to pick up my bass, start jamstix and jam.

Maybe like a jam pack, consisting of a couple of songs of a particular style, e.g. funk, jazz, etc. Each song contains 3 parts that fit nicely together, either as a verse, chorus & bridge structure, or as 3 different flavors of a beat, e.g. basic, heavy & quite. Maybe as an add-on pack. Just a thought.

R, Lucky

[R Green]

Apologies for time waste, I used the link to the manual earlier in this thread so I could have a look at it during lunch. Suggest that link is disabled? Did not know it came with the installer - will use at home only from now on.

[BitFlipper]

[b:e56b50f85d]Please...[/b:e56b50f85d]

Can we get a true Undo/Redo function? The more new ways added to modify an existing composition in unexpected ways, the more a true Undo/Redo function is needed. The restore point functionality just doesn't cut it for this type of application.

Just two simple buttons: Undo | Redo. This will encourage [i:e56b50f85d]much more experimentation[/i:e56b50f85d] without the fear of losing a good composition.

[b:e56b50f85d]Please...[/b:e56b50f85d]

BTW, as someone that has been doing software development for almost 20 years, I have implemented quite a few Undo/Redo features myself. You just need to be able to capture the current state fully (including all control settings) into a memory snapshot (or save the last 10 to 100 [user selectable?] or so snapshots to disk if it is just too big), and store it using a stack algorithm. The theory is pretty simple, and in practice it is usually trivial to implement compared to most other features. So why exactly not do it for Jamstix then...?

I think this is one case where the developers miss the importance of a feature like this because running test cases, etc, you don't need an Undo/Redo feature. In real life use, you do.

[Ralph @ Rayzoon]

Undo/Redo is just not that easy. Saving the entire data state every time a dial is turned in the brain etc. would consume too much time, especially since GUI and audio thread (which both access the data) must be synchronized on multi-core systems, so you'd likely have audio dropouts as soon as the arrangement reaches a certain # of composed bars and you are using anything but high latencies.

The way I use JS, I always save in the host or save a restore point in JS before doing any 'experimentation'. Another option is the auto-save feature of JS.

Let me stress that I would love full Undo/Redo just as you do. I'm just pointing out the difficulties with its implementation in this specific environment.

[BitFlipper]

Undo/Redo is just not that easy. Saving the entire data state every time a dial is turned in the brain etc. would consume too much time, especially since GUI and audio thread (which both access the data) must be synchronized on multi-core systems, so you'd likely have audio dropouts as soon as the arrangement reaches a certain # of composed bars and you are using anything but high latencies.

The way I use JS, I always save in the host or save a restore point in JS before doing any 'experimentation'. Another option is the auto-save feature of JS.

Let me stress that I would love full Undo/Redo just as you do. I'm just pointing out the difficulties with its implementation in this specific environment.

Ralph,

An alternative way that will consume much less memory and CPU time would be to store just changes to individual controls. If the user makes a change to a control, it stores the control's ID, it's old value, and its new value. This is a bit more complex compared to the brute force snapshot method, and also more bug-prone. But given the constraints you list above, it might be the only way to do it.

But you would also need to save the song's state itself, which might not be possible to break down into smaller chunks as opposed to the full song snapshot at a time.

I believe there is a solution to this problem.