Also something for the wishlist: Is there any reason why having a keyswitch for 'bypass' should be a problem? It would be fantastic, because then in any given project a midi channel wouldn't have to be dedicated to, say, legato or repetition, but could also be used for normal samples...
[:)]
Just an idea,

Thanks,

Simon

Okay, I think I've installed it wrong. It (the Giga tool) didn't want to load the old Performance setting files, i.e. VL-14 Legato, etc.

So I trashed those, trashed the tool, downloaded the beta again, and unzipped it. Should I reinstall those files from the old versions?

Sorry if I'm being dense.

Simon ... nice idea !!! So you can alternate between samples (legato, non-legato).

Good [:D]

Hi all!

@Another User said:

It (the Giga tool) didn't want to load the old Performance setting files, i.e. VL-14 Legato, etc.

So I trashed those, trashed the tool, downloaded the beta again, and unzipped it. Should I reinstall those files from the old versions?

Nick, strange, very strange. Yes, please reinstall the "old" Tool Files. Should work.

Thanks a lot for the feedback, everyone!

Best, Paul

@Paul said:

That would only make sense for the Alternation Tool, because all other samples only work with the corresponding mode of the Performance Tool (playing Legatos and Repetitions without our Tool is not really satisfying, is it?

Hi Paul. No, I was thinking exactly the other way round: A channel set in the perf. tool for legato, in use for legato samples. And then you suddenly want 3 notes in the middle using non-legato patches, so you trigger the 'bypass' keyswitch (which you're going to add for us! [[;)]] ), change patch to the non-legato articulation you want, play the 3 notes, then switch back again and un-bypass. I know, lots of people avoid patch changes within channels. I like to use fewer channels so I can see what I'm doing, and add patch changes. For this way of working, a remote 'bypass' would be fantastic (and surely much easier to implement than midi-switching of mode...)

Anyway, that was my idea: to be able to temporarily bypass the legato or repetition modes, allowing you to use NON-lagato/repetition samples briefly on that channel.
Hope I've explained better...

Thanks,

Simon

Hi Simon!

Yep, I get your point.

Still, which non-legato/non-repetition notes do you want to play? there´s veryvery many single notes for each instrument.... We need more RAM!

Rest assured, we are thinking of a sollution (maybe all variations of long notes? or one variation of each duration recorded?).

This of course initiates a lot of work on GigaStudio and some consequences for each user: new mappings, new gig-files, more disk-space, less instruments loaded.....

Thanks for the input!

Best, Paul

@Paul said:

Still, which non-legato/non-repetition notes do you want to play? there´s veryvery many single notes for each instrument.... We need more RAM!

[*-)]

Hi Paul,

I actually just meant using the system as it stands now: On a typical setup I have maybe 30 articulations loaded in one machine. Perhaps 13 of these performance elements (rep. or leg). So just by programming patch changes into the sequencer for that channel, I can switch to, say, a number of cresc./dim/sfz or whatever articulations for that instrument. I want to be able to use those in the middle of an otherwise legato (or rep.) line, without the perf. tool 'getting in the way'. At the moment, the only solution is to use another midi channel and put these notes onto there.
So it really would be enough for bypass to be triggerable by a keyswitch. Nothing more for now! (oh, can 'bypass' and 'un-bypass' be different keyswitches, rather than a toggle? Could get in a mess otherwise if starting in the middle of a piece...).

Thanks for your help! [:D]

All the best,
Simon

Hi Paul,

I have noticed with my single computer setup, that the Performance Tool doesn't pass on tempo changes from my sequence.

I am running Gigastudio, Overture 3 and MidiYoke. With the Performance Tool closed, Overture executes the tempo changes, but with the Performance Tool open, it doesn't respond to them and uses the first tempo it comes across.

I'm running Win 98SE on a P4 2.66. If I run Overture from another computer, there is no problem, but this means I can't use MidiYoke which gives me access through Overture to 16X4 individual midi channels.

If I open Overture first after Gigastudio and then try and open the Performance Tool, Performance tool comes up with the error "MMSYSTEM004 - The specified device is in use etc".

This was the same for the earlier version of the Alternation Tool.

Any thoughts on how to deal with this?

Craig

duocart, although not familiar with overture i'm assuming your midi routing is: overture - midi yoke - performance tool - gigastudio.
the error message *The specified device is in use* usually comes up, if a midiport (physical or virtual) is already used by another application and is not a multi-client device, so probably the in-/out-settings are not correct.
also the performance tool not passing tempo changes is a hint more than one dedicated midi signal is passed over to the performance tool inport or to nemesysport.
having the performance tool in your chain, you should have midi out on the performance tool set to nemesysport and the respective inport in gigastudio set to none. performance tool midi in should use midi yoke out and overtures midi out to be routed to midi yoke. finally make sure, any midi in of overture does not listen to *wrong* or *all* midi ports available on the system (a loop my occure otherwise)
christian

@cm said:

finally make sure, any midi in of overture does not listen to *wrong* or *all* midi ports available on the system (a loop my occure otherwise)
christian

Thanks Christian. That did the trick. I limited the input ports in Overture to none and the output to only Midiyoke ports 1-4.

Craig

duoartc, is this Overture program the current iteration of the program Opcode released about 10 years ago? The one written by Don Williams, who also wrote Encore - which is essentially the same program?

Hi Nick,

It may well be but I don't know for sure. I use to have Encore (well still do) but then I got Cakewalk Overture which had all the same features as Encore but more, with better notation and sequencer features - graphical presentations of tempo's, velocities, volumes etc. Then it went from Cakewalk to Geniesoft who now market it.

It's very intuitive to use (unlike Finale IMO) but with sequencer features that Sibelius doesn't have. You can move the starts and finishes of notes within a chord without changing the notation. It's worth having a look at - http://www.geniesoft.com. You can download a demo.

Craig

Disclaimer: I haven't yet read the new help material with the tool. That being said, I noticed these things...

1) On Windows XP, using what my friends call the "bubble gum" (nice looking windows chrome), the window main content is cut off near the bottom. We have this same problem with software we develop at my office.

2) Small is nice, but in 1600 X 1200, it's hard to read some of the text.

3) I said I didn't read the manual (my fault), but it's hard to realize whats going on at first glance... less intuitive from the previous (albeit dumber) version.

Just my 3 cents.

@Another User said:

CRAIG: It's very intuitive to use (unlike Finale IMO) but with sequencer features that Sibelius doesn't have.

Hey Craig, there you are again taking those subtle digs at Sibelius, and rightfully so in the case of timing nuances. However, the fact is that Sibelius 3 now allows timing edits to individual notes, phrases, etc. as you have been accustomed to doing in Overture. So load that Sibelius demo that I believe is still sittiing on your harddisk and catapult yourself into the ultimate notation environment!

Cheers, Don

Hi Gungnir,

I have tried the Sibelius 3.0 demo but it freezes on my machine. Maybe it doesn't like Win 98SE. But have you tried the Overture 3.0 demo?

I think a keyswitch for the Performance Tool would be great - anything to minimise the number of midi tracks and get back to a conductor's score.

I guess though it's easier for a notation program to respond to a score marking "legato" to activate the legato tool in VSL rather than finding 'work arounds' eg keyswitches to turn the tools on or off in notation programs. The same for repetitions, up and down bows etc and different length notes. A smarter Notation program could choose which sample to use given it knows the tempo and whether the note is a sixteenth or a whole note, or whether it's repeated. You could put in a note template for different intrument articulations available. But then that would require two quite different companies coming together for the solution.

Craig

To add to the wishlist:

- When you select the Save option, do not ask again for the file name. This is why the Save As feature exists. So if the file has already been saved once, please only save it again instead of asking for the file name again.

Thanks,
Martin

Right on Martin - this gets irritating real fast. Good suggestion on the final copy.

Rob

I hope I didn't miss this but I'd love there to be a master reset button for all ports.

I'm getting a lot of hanging notes related to using the sustain pedal on legato instruments. The only thing that cures it once it gets going is to close the tool and reopen it completely.

Overall it's a wonderful improvment over the 'vintage' tool! [:)]

Hey folks,

Has anyone noticed an unwanted "slide" on certain notes using PerfLeg Strings f ? It sounds like an Irish whistle turn. I'm still using V.1 of the Performance tool. Is this a tool issue or a sample issue I wonder?

Any takers on that? I guess I'll see if the V.2 beta tool helps out.

It would be interesting to have everyone post known bad samples. I think we've all come across them.

With baited breath I wait to hear from my colleagues,

Dave Connor

Hey folks,

Has anyone noticed an unwanted "slide" on certain notes using VL-14 PerfLeg Strings f ? It sounds like an Irish whistle turn. I'm still using V.1 of the Performance tool. Is this a tool issue or a sample issue I wonder?

Any takers on that? I guess I'll see if the V.2 beta tool helps out.

It would be interesting to have everyone post known bad samples. I think we've all come across them.

With baited breath I wait to hear from my colleagues,

Dave Connor