Add new comment

Just finished trying out Traverso. It's not bad. It's not great, but it's not bad. There are a lot of similarities between Qtractor and Traverso, but many more differences. I really don't care whether a program is mouse oriented or keyboard oriented, as most DAWs should be both. I like keyboard commands for the speed, as it much faster generally then driving a mouse, on certain things. However, I know many people that would rather not ever touch their keyboard, which is fine too. That is why both methods should be present.

Likes: (not all "likes" listed here have been tested)
- The FFT Spectrum Analyzer and Correlation Meter are very nice. Not the best execution of the idea, but it's there, so it can only get better.
- ALT+dragging a clip to copy it.
- LV2 Plugin support (even though I know LV2 is a long way from finished)
- The project manager may be a nice idea, although I have not had the chance to really play with it.
- X key splits a clip object (T key please ;)
- Ability to burn a Redbook CD directly from the project.

Dislikes:
- I hate not having a dedicated mixer window. The sliders to the left of a track is fine, but a dedicated mixer is a must IMO.
- The program seems to have problems with JACK resulting in a segmentation fault when trying to connect (admittedly I'm using the CVS version, so this could be the problem.
- No internal MIDI tracks.
- No external MIDI control (at least that I could find)
- The program seems generally unstable. Just a simple operation like "Insert Silence" crashes it. Not sure why this is even there. If you clip is split, then pulled apart, you would have silence between the clips. Seems useless to me.
- I really miss the fade boxes on the corners of the clips, and it's a pain to drag the edges of a clip to crop it. (menu item...probably a keyboard command, but didn't find it. Qtractor is way better at this ;)

Overall, I think that Qtractor is superior to Traverso, and certainly much more stable. I have spent hours upon hours with Qtractor, and only about an hour with Traverso. Mainly because the CVS build of Traverso was so unstable, it was very unpleasant to use.

With that said, this is obviously not a very fair comparison, just the best I could do after a short test run of Traverso. :)

Considering Traverso has been in development much longer than Qtractor, and comparing the differences between them, I see Qtractor rapidly surpassing Traverso, in a short amount of time. :)

Lexridge