• Register
  • Help
Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Topic: GS3 BUG: Program Changes in midi

Share/Bookmark
  1. #1

    GS3 BUG: Program Changes in midi

    Posted this first at the vsl gigastudio forum, then remembered that the more official forum seemed to be here. So here is a duplicate:

    Gigastudio 3 advances 'program change' midi events in the data stream, and causes failure of patch changes where there is a bank change involved. See the following data as read (1) from the source, Sonar 3 PE; (2) in the middle, by midimon and (3) at the destination, using gs3 midi monitor. Note the Program changes get out of order!!!

    SONAR 3 PE TRACK 3 CONFIGURED FOR BANK 0, PROGRAM 1 Channel 1 100BPM
    3 00:00:04:24 3:01:001 1 Patch Change(Controller 32) Bank 2 Patch 3
    3 00:00:04:24 3:01:020 1 Note C5 100 2
    3 00:00:07:06 4:01:001 1 Patch Change(Controller 32) Bank 4 Patch 5
    3 00:00:07:10 4:01:020 1 Note Db5 101 2

    RECORDED BY MIDIMON (first three events added by sonar on start)
    0 | B0 00 00 | Control Change | Channel 0 | Number 0 | Value 0
    0 | B0 20 00 | Control Change | Channel 0 | Number 32 | Value 0
    0 | C0 01 | Program Change | Channel 0 | Number 1 |

    0 | B0 20 02 | Control Change | Channel 0 | Number 32 | Value 2
    0 | C0 03 | Program Change | Channel 0 | Number 3 |
    0 | 90 3C 64 | Note On | Channel 0 | Pitch 60 | Velocity 100
    0 | 90 3C 00 | Note On | Channel 0 | Pitch 60 | Velocity 0

    0 | B0 20 04 | Control Change | Channel 0 | Number 32 | Value 4
    0 | C0 05 | Program Change | Channel 0 | Number 5 |
    0 | 90 3D 65 | Note On | Channel 0 | Pitch 61 | Velocity 101
    0 | 90 3D 00 | Note On | Channel 0 | Pitch 61 | Velocity 0

    RECORDED BY GIGASTUDIO 3

    Time
    Stamp Port Chan Event Data 1 Data 2 Flags
    ================================================== ============================================
    13048 0 0 Program Change 1 0 0x0
    13051 0 0 Controller Change 0 Bank Select (0) 0 0x0
    13051 0 0 Controller Change 32 LSB for Values 0 (32) 0 0x0

    17849 0 0 Program Change 3 0 0x0
    17852 0 0 Controller Change 32 LSB for Values 0 (32) 2 0x0
    17864 0 0 Note On C4 100 (velocity) 0x0
    17887 0 0 Note On C4 0 (velocity) 0x0

    20247 0 0 Program Change 5 0 0x0
    20250 0 0 Controller Change 32 LSB for Values 0 (32) 4 0x0
    20377 0 0 Note On C#4 101 (velocity) 0x0
    20400 0 0 Note On C#4 0 (velocity) 0x0

  2. #2

    Re: GS3 BUG: Program Changes in midi

    I have duplicated these results exactly using Digital Performer as the external source, MidiOx on the GS3 computer to monitor the raw data stream, and the GS3 Midi Monitor.

    GS3 is not processing the Program Change correctly.

  3. #3

    Re: GS3 BUG: Program Changes in midi

    I would suggest submitting this to Tascam US Tech support, so it can get on an official "bug list".

  4. #4

    Re: GS3 BUG: Program Changes in midi

    The good news is that this should be simple for the developers to fix. Unlike system issues, this is very deterministic.

  5. #5

    Re: GS3 BUG: Program Changes in midi

    This might be too basic, but any chance that this is a messed up setting in the new Imidi Rules filter section? I know that there is an 'ignore program change' filter, but it doesn't sound like that would exactly explain the behavior you are seeing.

    Just grabbing at staws here...

  6. #6

    Re: GS3 BUG: Program Changes in midi

    Has anyone reported this to Tascam? or have any workarounds? This problem is making my scores (played back from Sibelius) completely unuseable!

    Seems like I have no choice but to revert back to 2.5 until they produce a fix - so it would be good to know if anyone has spoken to Tascam about this one and whether it's likely to be in the first round of bugfixes.

  7. #7

    Re: GS3 BUG: Program Changes in midi

    There is no known email for support, though I've seen a couple of queries about it on this forum. So, no, I have not reported it. It's possible that custser@tascam.com might work (used for registration), or this sales email at teac.com: AV-TSC-IP-Sales@teac.com (used for cd keys).

    One workaround is to divide each line into several channels, one per articulation. It makes for a very ugly looking setup, but works to keep the sounds correct.

    If you need to apply some effects in gigastudio, the 'groups' work fine in the mixer section as a way to re-group sounds and apply a similar reverb or other effect to all the articulations for an instrument.

    I do really hope they fix this one, since I have a big collection of older works that all rely on patch and bank changes in the midi files!!

  8. #8

    Re: GS3 BUG: Program Changes in midi

    Quote Originally Posted by gugliel
    I do really hope they fix this one..
    I think you will have to call them to report this.

  9. #9

    Re: GS3 BUG: Program Changes in midi

    Have now reported this to Tascam.

    Mike.

  10. #10

    Re: GS3 BUG: Program Changes in midi

    Do we know if this issue was fixed in the 3.03 release? I'm still getting instances of GS3 3.03 ignoring program changes and I'm wondering whether it's just the way I'm sending the MIDI messages or is the bug still there.

Go Back to forum

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •