GigaStudio 3.2 is AVAILABLE!

[Larry Seyer]

TASCAM released an update for GigaStudio today (version 3.2). If you haven't updated your GigaStudio yet, go to the download site (http://www.tascamgiga.com/downloads.html) and install it.


We've been using it here for a while now... Works great!


Here are the Changes in v3.20 (this is from the Changes PDF file on the TASCAM site):


New Features
GigaViolin Support
Version 3.20 or higher is required to load and play the GigaViolin .gig instrument.
Improved Efficiency with 24-bit Instruments
Changes have been made to the sampler engine providing for 20% - 35% more efficiency, depending on the extent of filter usage (DEF & PRF included) in the 24-bit instruments being played. The following table illustrates the amount of efficiency improvement from previous versions of GS3 based on a 124 voice benchmark project:
Instruments Played CPU Reduction
Non filtered 35%
50/50 filtered 27%
All filtered 20%
Note: These numbers do not reflect convolution or mixer overhead. They represent an expected improvement in the core sampler engine.
Export Mapped Instruments to Text
By selecting View > "Bank/Patch Manager" or Right-Mouse-Clicking in the loaded instrument pane and selecting "Bank/Patch Manager", you'll see an "Export Patches to File" button, which outputs a tab delimited file with (bank, patch, instrument name) info for each mapped instrument suitable to be dropped into a DAW for bank/patch assignments.
A check box next to the button labeled "Port/Channel Detail" changes the exported data to show (bank, patch, port, channel, instrument number, instrument name, and instrument gig file) for each mapped instrument. The data is tab delimited suitable for import into a spreadsheet.
This allows documenting performance configurations.


Main App Maintenance Items


Incorrect dependencies between Envelope 1 and Envelope 2 which could cause incorrect decays have been corrected.
Rare instances of GigaStudio crashing when rendering GigaPulse through groups have been fixed.
Previously the ?Rebuild this folder recursively? function in the Quick Sound database would not rebuild all the folders within the selected folder. This has been fixed and status indication has been added.
Rare instances of instruments linked on Multi-Ports with release triggers having their releases get terminated prematurely, and possibly causing a pop, have been fixed.
Rare instances of a scroll bar in the MIDI Mixer not appearing when it should, have been fixed.
Possible causes of noise burst with some instruments have been reduced.
Possible causes of instability have been reduced
MIDI and iMIDI handling has been improved
DEF and PRF handling have been improved
The QuickSound database has been enhanced for stability Known Issue:
All PRF instruments on a stack will inherit the default Portamento time of the most recently instrument loaded, regardless of their independent values on initialization.

Enjoy!


Webmaster
LearnGigaStudio.com

[GigaUser NYC]

Cool! Thanks!

I wonder, can you tell me, did they do any work on the ability to swap instruments, or change their order, in stack?

As it stands, each new instrument is added to the bottom of a stack, and there is no way to re-order them. This is problematic when you have a key switching scheme set up in a stack, and you can't swap the instument that you have mapped to C#.

If you delete the old C# instrument, everyone moves up, and the D instrument is now on C#, with the new instument on the last key.

Any info or help is VERY appreciated!

Thanks!

[Gary]

Hello,

I'd appreciate your confirmation/correction to the following: I've always treated updates to Giga 3.x as "incremental." That is, if it becomes necessary to reinstall the entire Giga product on a computer unit, reinstall the base version (3.0) first, then install each update in the order it was released. Correct?

Consequently, with regard to installing update 3.2, simply download and execute it without uninstalling any prior Giga update releases, correct?

Thanks.

Gary

[Larry Seyer]

Cool! Thanks!

I wonder, can you tell me, did they do any work on the ability to swap instruments, or change their order, in stack?

As it stands, each new instrument is added to the bottom of a stack, and there is no way to re-order them. This is problematic when you have a key switching scheme set up in a stack, and you can't swap the instument that you have mapped to C#.

If you delete the old C# instrument, everyone moves up, and the D instrument is now on C#, with the new instument on the last key.

Any info or help is VERY appreciated!

Thanks!

I don't think the stack ordering has been worked on yet... but I think it's on the todo list... I don't really know what is on that list however...

Best to you!

Larry

[Larry Seyer]

Hello,

I'd appreciate your confirmation/correction to the following: I've always treated updates to Giga 3.x as "incremental." That is, if it becomes necessary to reinstall the entire Giga product on a computer unit, reinstall the base version (3.0) first, then install each update in the order it was released. Correct?

Consequently, with regard to installing update 3.2, simply download and execute it without uninstalling any prior Giga update releases, correct?

Thanks.

Gary


Gary,

I never uninstall and re-install (unless told to do so by TASCAM or as a last resort and all else fails).

When doing an update, I simply install the patch and move on.

At least, that is what I do and it has worked fine so far.

Best to you!

Larry

[GigaUser NYC]

I don't think the stack ordering has been worked on yet... but I think it's on the todo list...

If its on the to do list, then I don't mind doing it the long way around for now. As long as I know it WILL be fixed, I can go ahead with my scheme for full and lite instruments.

If it will never be fixed, then I would structure things another way, doing more in the instrument, and less with key stacking. It seems obvious and simple enough though, that i had already sort of taken it on faith that it would get dealt with. Your answer helps to strengthen my "faith" in this system, so I'll continue with it.

I have a problem saying it should be "fixed" too, because nothing in the manual promises or describes this feature, so I guess technically, its not a bug, but a feature request - best expressed as a question, rather than asking for a "fix". I don't want to seem demanding when I'm actually asking for a favor?

Also, another poster asked: "Consequently, with regard to installing update 3.2, simply download and execute it without uninstalling any prior Giga update releases, correct?"

And I think what he was asking was, if you have version 3.0, can you install ONLY the 3.2 patch and still get the benefits of the 3.10 and 3.12 patches, or do you have to install each, in order? My guess is that when updating from any earlier 3.x version, the latest 3.2 patch alone will contain everything you need.

Can you confirm?

Thanks again for all your time here.

[Larry Seyer]

If its on the to do list, then I don't mind doing it the long way around for now. As long as I know it WILL be fixed, I can go ahead with my scheme for full and lite instruments.

If it will never be fixed, then I would structure things another way, doing more in the instrument, and less with key stacking. It seems obvious and simple enough though, that i had already sort of taken it on faith that it would get dealt with. Your answer helps to strengthen my "faith" in this system, so I'll continue with it.

I have a problem saying it should be "fixed" too, because nothing in the manual promises or describes this feature, so I guess technically, its not a bug, but a feature request - best expressed as a question, rather than asking for a "fix". I don't want to seem demanding when I'm actually asking for a favor?

Also, another poster asked: "Consequently, with regard to installing update 3.2, simply download and execute it without uninstalling any prior Giga update releases, correct?"

And I think what he was asking was, if you have version 3.0, can you install ONLY the 3.2 patch and still get the benefits of the 3.10 and 3.12 patches, or do you have to install each, in order? My guess is that when updating from any earlier 3.x version, the latest 3.2 patch alone will contain everything you need.

Can you confirm?

Thanks again for all your time here.


As far as I know, the 3.2 patch updates ALL versions of GS3 to current...

I do not go through any special process of 3.04 to 3.12 to 3.2... I simply run the updater and be done with it.

Best to you!

Larry

[GigaUser NYC]

As far as I know, the 3.2 patch updates ALL versions of GS3 to current...

I do not go through any special process of 3.04 to 3.12 to 3.2... I simply run the updater and be done with it.

Of course you are right. I upgraded my 3.12 to 3.2 yesterday. The first clue was the file's name which included the text "any_to_320" that's a pretty good clue that "any" version will be updated to 3.20.

The installer itself was a little scary. it said 3.1 updater everywhere - leaving me worrying whether this was the 3.10 upgrade. I suppose that they mean updater FROM 3.1, which I guess includes my 3.12, but since they had just told me it was an updater from "any" the description was confusing. If it said 3.2, it would have been clearer.

3.20 is running well and stable, and I'm already SO damn happy for the quicksound changes. The recursive folder rebuild is well well appreciated for all the time it saves me. Not having to look at all capitals in the quicksound box is nice too!

There are still some bugs, and feature requests on my list. I'll bring another out in a different thread soon. Meanwhile, bravo for 3.2 - a free upgrade, and progress on lots of little things that keep GS3 from being perfect. Great! Thanks!

[james a vogts]

I have not been able to use my chorus from Blue Tubes till now. I used SFP FX instead. My reason for upgrading to GS3 was to take some of the load off of my DSP's. They are needed for John Bowens synths. Now I can use Blue Tubes, and it saves the NFX properly also. I only need the autopan NFX for my Scarbee Rhodes. I still use my Lexicon PCM70, and PCM41 with my DAW and just love the effects in SFP and Blue Tubes. I am almost w/o hardware now!!

JV

[alanb]

TASCAM released an update for GigaStudio today (version 3.2). If you haven't updated your GigaStudio yet, go to the download site (http://www.tascamgiga.com/downloads.html) and install it.


We've been using it here for a while now... Works great!

Have you experienced any change -- positive or negative -- in your total Tested Memory Available for Instrument Loading since making the change from v3.12 to v3.20?