Quick Bug Check

Author
emwhy
Max Output Level: -62 dBFS
  • Total Posts : 1402
  • Joined: 2006/01/03 15:09:02
  • Status: offline
2011/04/07 07:28:53 (permalink)

Quick Bug Check

If a few people could test this and report back, I'll submit it to the bakers:

1. Insert a soft synth

2. Using  the Inspector under the MIDI tab change the value of transpose (any value will do, I used an octave +12)

3. Play the synth back from your controller to make sure it has transposed.

4. Insert another synth

5. Go back to the first synth, play a few notes and you'll notice that even though it has been transposed, and the value reading in the inspector has not changed, it has now reverted back to its default value.

The above happens to me all the time.

System Specs:

Win 7 64 Ultimate
Sonar X1b (64)  incl Quick Fix
Edirol UA 101 
NVidia GT9500
Q6600 on a Gigabyte MB
8 Gigs Ramm

#1

5 Replies Related Threads

    subtlearts
    Max Output Level: -53.5 dBFS
    • Total Posts : 2200
    • Joined: 2006/01/10 05:59:21
    • Location: Berlin
    • Status: offline
    Re:Quick Bug Check 2011/04/07 07:59:44 (permalink)
    Doesn't seem to be happening here. Transpose persists (tbh I didn't even know it was there until now, so that was a happy discovery...) 

    XP sp3 32bit though, so a different platform. 

    tobias tinker 
    music is easy: just start with complete silence, and take away the parts you don't like!
    tobiastinker.com
    aeosrecords.com
    soundfascination.com
    Sonar Platinum, a bunch of other stuff...
    #2
    LANEY
    Max Output Level: -64 dBFS
    • Total Posts : 1350
    • Joined: 2010/12/11 20:27:13
    • Location: USA
    • Status: offline
    Re:Quick Bug Check 2011/04/07 08:46:56 (permalink)
    Sorry I just tried it and it worked with mine. Still stayed transposed.
    And I am using Win 7 64 bit with quick fix also.



    i7/16GB ram
    Win 7 x64
    SONAR Platinum Producer x64
    VS-700 C&R

    Octa-Capture and VS-100 for live recording
    #3
    emwhy
    Max Output Level: -62 dBFS
    • Total Posts : 1402
    • Joined: 2006/01/03 15:09:02
    • Status: offline
    Re:Quick Bug Check 2011/04/07 09:42:47 (permalink)
    I should add that I use a lot of bridged plug-ins (Bit Bridge and jBridge), that's why I am asking people to test this out.

    #4
    subtlearts
    Max Output Level: -53.5 dBFS
    • Total Posts : 2200
    • Joined: 2006/01/10 05:59:21
    • Location: Berlin
    • Status: offline
    Re:Quick Bug Check 2011/04/07 10:15:27 (permalink)
    Ah. I don't use any, so that might be part of the recipe. I'll let others check it out then... hope you track it down!

    tobias tinker 
    music is easy: just start with complete silence, and take away the parts you don't like!
    tobiastinker.com
    aeosrecords.com
    soundfascination.com
    Sonar Platinum, a bunch of other stuff...
    #5
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Quick Bug Check 2011/04/07 11:40:53 (permalink)

    I should add that I use a lot of bridged plug-ins (Bit Bridge and jBridge), that's why I am asking people to test this out.



    I am able to reproduce something like this with x64 synths alone, but I get the opposite effect you described. In my case, the MIDI tab for the previously inserted synth continued to show a transpose (a.k.a. Key Offset or Key+) value, but it had no effect on live input until the transport was started, after which the Offset would apply to live input as well as existing clips; cycling the audio engine was not sufficient; I had to hit play. Also, it seemed only to affect the last synth inserted, but I need to double-check that to make sure it's not synth-specific. 


    I also observed a few other buggy behaviors along the way (funny what you notice when you're really paying attention):


    1. When inserting a Simple Instrument track with Always Echo Current MIDI track disabled (usually the case for me), the Input is shown as 'None", and stays that way when Input Echo is enabled, but it is in fact receiving as Omni, and echoes MIDI input from all ports. In 8.5.3, It will insert with input set to None, but as soon as you enable Input Echo, it will change to Omni.


    2. When a soft synth is inserted as a Simple Instrument, and then the Instrument track is split to MIDI and Audio, the focus stays with the MIDI track, but the inspector shows the Audio track properties. Clicking on the MIDI track does not update the Inspector; you have to click on another track to switch the focus, and then back to the MIDI track. Also, when you've first split the track, the Inspector continues to show MIDI and Audio tabs at the bottom as though it is still an Instrument track, and that doesn't change until you switch focus to another track.


    3. Key Offset operates in real time on soft synth tracks, but not on MIDI echoed to hardware synths (i.e. physical MIDI ports). With physical output ports, the offset/transpose values is only applied to existing MIDI clips in the track. This behavior actually goes back to previous versions, and I thought it was WAD, until I noticed that soft synths work differently. I'll have to check how Vel+ works in this respect, 'cause I know Vel+ used to work in real time on physical MIDI outputs.


    4. With Always echo current MIDI track enabled, clicking on the Input Echo button on a MIDI/Instrument track that does not have focus moves focus to that track but does not force Input Echo on as it should; you have to click the button again to force it on. I believe that some other Input Echo status functionality fix was made in the Hotfix. Seems maybe they got something else wrong this time.









    post edited by brundlefly - 2011/04/07 11:46:03
    #6
    Jump to:
    © 2024 APG vNext Commercial Version 5.1