sjoens

Good idea.  My graphics are the same as yours David.  My troubles are on Windows 10.  The only workaround so far is to leave them open in Multidock or minimize the windows when not in use.

Strangely SQ80 v1.5 worked fine on Windows 11 until I updated it to v1.6.  Now CbB won't even scan it.  I've abandoned the Windows 11 machine for DAW use but will check if going back to v1.5 fixes that issue.

Arturia's CZ V and SQ80 V plugins are crashing/closing CbB when their GUI windows are closed.

Currently getting help from Arturia but so far nothing has worked to fix it.

Tried un/reinstalling removing all registry entries. Running installers and standalone as Administrator. Refreshing the data caches.

Windows 10 22H2, CbB 2023.09

Anyone else have trouble with Arturia?

Makes sense.

4 hours ago, sjoens said:

Seems like a long standing issue from Sonar days, so probably never figure it out.

But I did.  I'm an idiot!

Project tempo is 170 bpm.  Clip is a 4 beat ride cymbal struck every 1/2 beat - that's why it shrank 1/2 size.  When tempo is set to 85 bpm, G-CL maintains length as it should.  So 100% my fault.  For some reason I thought G-CL honored a clip's length regardless of content. 

As you were...

Seems like a long standing issue from Sonar days, so probably never figure it out.

Just started using Groove-Clip Looping and ran into this clip shrinking "bug" today.  It shrinks to half the length when Groove-clipping it, so...

1) Slip-stretch clip 200%
2) Create groove clip loop, which shrinks it back to original size
3) Slip-stretch clip to desired length
4) Bounce to clips and hope there's little quality degradation

Tried the Loop Construction suggestions but found it to be quite buggy as well.

14 hours ago, Promidi said:

(do
    (int count 0)
    (int Alt_velocity 100)
    (getInt Alt_velocity "Please enter velocity for every alternative note" 1 127)
    (forEachEvent
        (if (== Event.Kind NOTE)
            (do
                (if (== (% count 2) 0) (= Note.Vel Alt_velocity))
                (++ count))))
);end do

This works for single non-stacked notes but not when notes are stacked vertically at the same time stamp.

What I get:
c3    1-120    2-120    3-120    4-120
b2    1-100    2-100    3-100    4-100

What I want:
c3    1-120    2-100    3-120    4-100
b2    1-120    2-100    3-120    4-100
What line can I add to affect this outcome?  Or will I need to process the lines separately?

2 minutes ago, David Baay said:

Or you could make a short Groove Clip consisting of just 2 or 4 of the events and roll it out as needed.

This was my next option but a CAL script would be easier after the fact.

1 hour ago, Promidi said:

Your question should not be “Is there a CAL script that..........”, but rather, “Can a CAL script be written that..........”

 I was sure one could be written but wanted to know if one already existed.  If not, I would have asked how to make one, tho I have no clue how to read/write CAL.

Also seems like one of the MFX should do this but apparently not.

FWIW, I have a huge collection of CAL from Mudgel and others, but some don't work right or at all.

Hey thanks Promidi, will check it out.

Is there one to alternate every other note by the same value?

i.e.  100 - 120 - 100 - 120 - 100 - 120... 

Thanks for the "Like" Patrick but after carefully reading thru every post I'm removing my links in case these weren't intended for public consumption.  I found them searching the web.

21 hours ago, George S said:

how to show separate MIDI and audio tracks for an instrument?

2 ways with Instrument tracks.  1.Using Inspector > MIDI button as Outrage said, or 2. Right-click Instrument track and select Split Instrument Track.
#2 is reversible by selecting both tracks and right-clicking Make Instrument Track.

Otherwise, when inserting a new soft synth:

1. Click Insert > Soft Synth...

2. Deselect Simple Instrument Track

3. Select MIDI Source

No cc's or pedal.  This was during live playing, I think Ample Sound guitar.

When my hardware synth gets stuck I usually have to cycle it's power.

Sometimes.  I had one that kept getting stuck as I was playing it so I kept hitting reset and then resetting the volume levels.

Never mind.  I had Disable Input Monitoring During Playback checked in Preferences. 

I can use Input Echo to hear guitar thru a plugin when Transport is stopped or recording, but not during playback.  As soon as I hit Play, the FX goes away.  Is there any way to hear the FX when Transport is playing?

I started using an older vsti from the 1990s that had quite the delay from key strike to sound until I set it to 500.

1 hour ago, User 905133 said:

I just tested this and successfully assigned a slider on my usb keyboard to the Input Gain knob on a MIDI track/channel strip. It also moved the horizontal vel+/vel- slider in the track header.

Just wondering how you did this as the Gain knob & TV Vel+ slider can't be selected for Write-to automation.

According to the reference manual pg 321, the MIDI channel strip top "Gain" knob (same as the TV Vel+ slider) controls velocity offset for that track - but AFAIK can't be automated.  @User 905133 can you describe steps for doing it?

Adjusting the note velocity (Vel+)
Each MIDI note event has a velocity, which represents how fast the key was struck when the track was recorded. On playback, the velocity offset parameter adjusts the velocity data for all notes in the track by the designated amount. The value can range from -127 to 127. The effect of changing velocities depends on the synthesizer. Some synthesizers do not respond to velocity information. For others, the effect varies depending on the sound or patch you have chosen. Normally, higher velocities result in louder and/or brighter-sounding notes. This parameter does not affect the velocity that is stored for each note event. When the clip is displayed in other views, like the Piano Roll  View, Staff view, or Event List view, you will see the original velocities as they are stored in the file. You can edit the velocity values in those views, or use the Process > Scale Velocity or Process > Find/Change command. Velocity is different from volume in that it is an attribute of each event, rather than a controller that affects an entire MIDI channel. Here’s an example of where this distinction might be important. Suppose you have several tracks containing different drum parts. All of these parts would probably be assigned to MIDI channel 10 (that’s the default channel for percussion in General MIDI). If you change the volume setting for any track that uses channel 10, all the different drum parts—regardless of what track they’re in—would be affected. If you change the note velocity for one drum track, it will be the only one whose volume is affected.
To set the velocity offset for a track
1. Open the Track Inspector or Console view.
2. Select the track you want to edit.
3. Adjust the Vel+ knob at the top of the channel strip.

However, Gain can be automated per clip by right-clicking the Clips button.  Even so, the knobs & sliders don't move so there's no visual que it's happening.
Wonder if that's a bug or an oversight?

I've always wondered why converting stereo to mono increases volume.  Seems to me the process should maintain total output level.  As is, another editing step is required to bring it down if it's too much.

Thanks guys.  I struggled with this yesterday for awhile.  I can't preproduce it without a stuck note so won't know if it was a glitch until I get another one.

11 hours ago, OutrageProductions said:

Check the setting in <Preferences><Project><MIDI><Zero Controllers When Play Stops>

Do you mean check to see, or √?  It was checked so I unchecked it to see if makes a difference, although I hope not as I need it checked for PRV controllers.

Edit:

No hardware controllers here.  I guess the MIDI fader is Volume, not velocity, but I've always viewed it as a master velocity fader as "volume" is controlled by the softsynth or outboard synth volume fader.  Note that MIDI track Gain knobs do go from -127 to +127 and reset to -0-.

I've noticed when a stuck note requires a reset via the Control Bar Reset button, ALL MIDI track velocity faders default to 101 regardless of fader position, requiring them to be manually reset as well.

You may also be able to "replace" the plugin by right-clicking the synth's icon.  Even replacing it with the same one may help.

Home 23H2 build 22631.2861,  but it's been a nightmare since new.

Thanks for the tips guys.  I just migrated my DAW back to the Windows 10 laptop.  I will never again use Win11 for it.