Glenn Stanton

meaning using MIDI to create the new track, then trigger the arming and begin record? maybe using a MIDI controller to perform the steps in conjunction with some form of macro tool?

1 hour ago, RICHARD HUTCHINS said:

I see a long dotted line with 76 bpm throughout.

to me, that would seem to indicate you only have a single tempo - 76BPM. as David mentioned, you need to drag the edge of the clip to the next full measure (in the examples) to see the "cut". one good way to land on the beat is to set your snap to 1/4. for measures, setting it to 1 or 1/2 will make landing there easier.

is this one of those "audio-to-USB" cables for $5 on Amazon? one option might be to spend a bit more and a get a decent <$100 audio interface. 

that said

• check the device
• check the drivers
• see if a line-level input signal can drive it vs a guitar (which is a very low level signal).

14 hours ago, John Vere said:

Note this is the last time I will post this video 

it's almost like you'd want a sticky thread "Read/Watch This First" thingie to post links (with descriptions) of your videos 

as part of the install process - did you select the cakewalk content / demo installation? if not, go ahead and run that. if you did, check in the content folder:

C:\Cakewalk Content\Demo Projects

there is a text section in the beginning of the strum-it.cal file which might be what you're looking for?

per this old thread: http://forum.cakewalk.com/Strum-it-cal-m1432672.aspx

Quote

;;  Strum-It.CAL, written 1991 by Douglas L. Fetter [UID 5476]
;;;
;;  This CAL routine was written to alter chords entered in Step Record mode,
;;  to give them a strummed or arpeggio effect (as for guitar, harp, piano).
;;  A special feature of this Strum-It.CAL routine is that it will actually
;;  sort the notes occurring at the same event time so that when played back
;;  they will be in proper arpeggio low note to high note order. But this low
;;  to high note order is not a restriction, this CAL routine allows the user
;;  to specify a strum that goes instead from high note to low note; or even
;;  an alternating low to high on the 1st chord, high to low 2nd chord, low
;;  to high 3rd chord, etc. as is sometimes played on a guitar or similar
;;  strummed string instrument.
;;;
;;  The user will first be requested to enter the number of ticks to be used
;;  to separate the notes occurring at the same event time to produce a strum
;;  effect. The value a user enters is dependent upon both the tempo of the
;;  piece as well as the number of ticks per quarter note as specified in
;;  the timebase setting. (Experiment with a small section until the desired
;;  strum effect is achieved.)
;;;
;;  Next the user is requested to enter a value which represents the order in
;;  which the strummed notes are to be played (low to high, high to low, or
;;  an alternating order which starts out with a low to high strum first).
;;;
;;  The CAL routine then scans through the note events of the selected track,
;;  looking for those notes which occur at the exact same times. The routine
;;  saves these events in internal buffer space and deletes them from the
;;  track. When a note event of a later time is found, the stored notes are
;;  inserted back into the track in the requested low to high or high to low
;;  order with the start times of these stored chord notes progressively
;;  advanced by the tick value specified by the user. Then, since shifting
;;  notes later in time may cause them to overlap with other notes later in
;;  the track, the durations of each of the shifted notes is reduced by the
;;  number of ticks by which it has been advanced in the creation of this
;;  strum effect.
;;;
;;  (Example specifying Tick Value = 8, and Low to High Order:
;;         ------- Before -------          ------- After --------
;;           Time    Key Vel  Dur            Time    Key Vel  Dur
;;         2:01:000  E 5  64  119          2:01:000  C 5  64  119
;;         2:01:000  C 5  64  119          2:01:008  E 5  64  111
;;         2:01:000  A#5  64  119          2:01:016  F 5  64  103
;;         2:01:000  F 5  64  119          2:01:024  A#5  64   95
;;;
;;  Chords of up to 6 notes can be handled by this CAL routine. If more than
;;  6 notes are found occurring at the same event time, a message will appear
;;  in the bottom status line indicating the Measure:Beat:Tick time where the
;;  more than 6 notes occurs. To abort the process after this error, the user
;;  hits ESC and then uses the Cakewalk Edit UNDO function to get back to the
;;  original unaltered state. However, by hitting any key other than ESC, the
;;  CAL routine will continue to normal completion. At the location where the
;;  more than 6 notes were detected, the first 6 notes found will be properly
;;  sorted & arpeggiated; the additional note(s) found at the same time will
;;  be left unaltered in time and duration.
;;;
;;  USER WARNINGS:
;;   1) As there is considerable processing performed while running this CAL
;;      routine, it runs quite slowly. Therefore, the user is advised to
;;      work first with a small section of a track while adjusting to get a
;;      separating tick value that gives the desired strumming effect.
;;   2) Since the note durations are adjusted downward to compensate for the
;;      the shift of notes later in time, the user must be careful that the
;;      initial note values are long enough such that when reduced they do
;;      not go down to zero or below (which result in note durations which
;;      wrap around the maximum duration value 65535).
;;   3) The user should only run this CAL routine on a single track at a time
;;      since it cannot detect notes at the same time in another track & the
;;      last note events in one track will be inserted back into a subsequent
;;      marked track, which can eventually cause an execution error.
;;;
; ***************************************************************************
; * This CAL routine is pushing the maximum size limitations which Cakewalk *
; * Pro will allow; if the body portion is increased by 30 or more characters
; * it will cause a "Source line/expression too long" ERROR. For this reason*
; * the following executable routine does not make use of longer, meaningful*
; * variable names and the code is not formatted into an indented structure *
; * nor contain comments that would aid readability. For this reason I have *
; * included STRUM-IT.TXT which is this very same CAL routine but with full *
; * variable names, in a readable structure, & including comments. However, *
; * the larger amount of text that this creates will not permit the version *
; * of this CAL routine in STRUM-IT.TXT to be executed.                     *
; ***************************************************************************

;Prolog
;
(do
 (int E 0)            ; EventCnt ; used to provide processing status
 (int C 0)            ; NoteCnt  ; count of notes of 1 chord held in buffers
 (dword T 4294967295) ; NoteTime ; time value of notes being held in buffers
 (dword U)            ; EvntTime ; time of next note event to be processed
 (int M)              ; Measure  ; measure of next note event for error msg
 (int B)              ; Beat     ; beat of next note event for error msg
 (int I)              ; Tick     ; tick of next note event for error msg
 (int D 10)           ; Delta    ; ticks entered by user for note separation
 (int O 0)            ; Offset   ; accumlative delta for chord note separation
 (int H 0)            ; HowStrum ; user enters how strum is to be performed
 (int S)              ; StrumDir ; 0=> Low Note to High, 1=> High Note to Low
 (int X)              ; NextChn  ; channel of next note being processed
 (int Y)              ; ChnBuf1  ; note channel buffer #1 (lowest note)
 (int Z)              ; ChnBuf2  ; note channel buffer #2
 (int a)              ; ChnBuf3  ; note channel buffer #3
 (int b)              ; ChnBuf4  ; note channel buffer #4
 (int c)              ; ChnBuf5  ; note channel buffer #5
 (int d)              ; ChnBuf6  ; note channel buffer #6 (highest note)
 (int e)              ; NextKey  ; key of next note being processed
 (int f)              ; KeyBuf1  ; note key buffer #1 (lowest note)
 (int g)              ; KeyBuf2  ; note key buffer #2
 (int h)              ; KeyBuf3  ; note key buffer #3
 (int i)              ; KeyBuf4  ; note key buffer #4
 (int j)              ; KeyBuf5  ; note key buffer #5
 (int k)              ; KeyBuf6  ; note key buffer #6 (highest note)
 (int l)              ; NextVel  ; velocity of next note being processed
 (int m)              ; VelBuf1  ; note velocity buffer #1 (lowest note)
 (int n)              ; VelBuf2  ; note velocity buffer #2
 (int o)              ; VelBuf3  ; note velocity buffer #3
 (int p)              ; VelBuf4  ; note velocity buffer #4
 (int q)              ; VelBuf5  ; note velocity buffer #5
 (int r)              ; VelBuf6  ; note velocity buffer #6 (highest note)
 (int s)              ; NextDur  ; duration of next note being processed
 (int t)              ; DurBuf1  ; note duration buffer #1 (lowest note)
 (int u)              ; DurBuf2  ; note duration buffer #2
 (int v)              ; DurBuf3  ; note duration buffer #3
 (int x)              ; DurBuf4  ; note duration buffer #4
 (int y)              ; DurBuf5  ; note duration buffer #5
 (int z)              ; DurBuf6  ; note duration buffer #6 (highest note)

 (getInt D "How many ticks should be used to separate strummed notes?" 1 100)
 (getInt H "Direction: 0 => Low to High, 1 => High to Low, 2 => Alternate" 0 2)

check your tempo map - is it a consistent tempo? 

hmmm, and yet many people can record and play back in the app. so first things first:

1) you have the INPUT and OUTPUT settings in your device configuration set up:

• a) input source
• b) output target
• maybe start with WASAPI SHARED if your IO unit supports it.

2) open a demo project and play it. any audio? no? repeat step 1.

• this should be the fastest way to test  your audio output
• troubleshooting - make sure your Windows OS sound settings and the CbB sound settings are using the same sample rate. e.g. if you're using 44.1K in the OS, and 48K in the DAW, you're likely not going to hear it, or hear it the way you should.

agreed. i haven't played with the Studio One implementation, and i think MIDI changes made from the chord track makes sense. not sure how well chord changes in audio work out though. even using Melodyne directly to tweak (acoustic guitar) for example, switch a chord from D major to D minor or adding a note (C Major to C add9 for example) might not work as well.

you could do the same with Melodyne essential - drag the clip to the time bar so it has the timing info, then set it as a Melodyne region which then displays the chords and while you cannot edit polyphonic info, you can export it as MIDI.

9 minutes ago, Jeremy Landig said:

Hm.  I bought Sonar 5, 6, 7, 8, 9, X1, X2, and X3. 

Can people like me be grandfathered into the new Sonar?  Please?

i would be surprised if they didn't offer a loyalty pricing but doubt a freebie as the monies for those versions mainly went to Gibson.

maybe something like "Bandlab Studio"?

1 hour ago, John Vere said:

Produce a FREE version of Cakewalk with adds that pop up every 5 minutes just like 90% of the free Apps and delivery services do. 

don't be ridiculous - free products have the adverts running continously which then expand (top, bottom sides) over whatever you're trying to work with for 10 seconds plus include playing audio and video snippets. preferably with adverts targeting your specifics - so old males - ED formulas, cremation services, cruises, and the latest Microsoft / Apple news.

so, using the smart tool you're seeing this icon on the edge of the clip you're trying to extend?

in this example, it was a single measure using Step Sequencer to create the MIDI and then groove loop it then stretch using smart tool. so far, i have not be able to reproduce this issue - in existing or new projects.

i just leave the spyware in place. what happens to their mental state while listening to my sh*t is not my fault. 🤪

so, just pick up your acoustic guitar or sit at the acoustic piano and use your phone recorder. last i heard, there are several artists with platinum selling songs who did just that. boom! simple create music. Cakewalk provides creative tools but it's set into an engineering framework to handle electronic creation, recording, and manipulation. this thus shifts from merely performing live on an acoustic instrument(s), to orchestrating many things into a recording (or live performance for those daring enough). far from trivial or even simple. but the 7 P's still apply to all things.

this is the MIDI groove clip edit in the inspector that David is mentioning

yes MIDI doesn't need it - you just need to make sure your notes are within the boundary and trim the clip to the number of bars. in my MIDI clip, the notes are random, but the clip was 4 measures (via trimming) and so the groove clipping worked just fine.

that's the challenge for vector graphics - how many little lines make up a circle? and the more lines the more CPU/GPU intensive its gets. same for scalable fonts etc. so with bit images you have options to offload the display and a defined size and processing needs -- but on a 4K display, what worked in 1920x1080 is now hard to read, and scaling, well, oops - not so great. 

not a fan of the flat look but ok, my next monitor will likely be either 4K or 8K so it will help, and many apps and plugins are going that as reginaldStjohn noted, so i'll learn to use the flat views, and likely have to convince my spouse to let me get an 16ch SSL controller so i don't hurt my eyes due to blurry vectors or high contrast or ... 🙂 LOL

the groove looping requires it to know the number of beats for the duration of the clip - and sometimes it guesses incorrectly. so you edit the clip and set the specific number of beats. this also implies your clip is generally set to line up properly with the snap setting to make it more repeatable.

e.g. if i have a clip 4 measures long in 4/4, my clip needs to have 16 beats. regardless of the # of instrument events.

this generally works for MIDI as well. however there is no "loop construction" like an audio track has.

3 minutes ago, Nikita Kapernaumov said:

i already have a 64bit computer  with ryzen cpu, 32gb.    sonar 4 is a 32bit daw it can only use one core and 1 or 2 GB, i forgot.   canbt work with vst3.   cant work wth any Kontakt libraries since  they are all for kontakt 6 and kontakt 6 is vst3

ok, gotcha, sounds you need a theme updated with some graphics potentially to get the sharp note edges in CbB. my impression was you only has a 32-bit machine and somehow were worried going to 64-bit CbB (or Sonar) was not possible.

i think SteveC and billp have the right ideas. you might just edit the note images yourself to get the sharper edges. there is a theme editor for CbB.

1 hour ago, Nikita Kapernaumov said:

 i'm still limited with 32-bit  facilities.  Somebody please help me .  I could pay money for reprogramming the new interface to look as  Sonar-4.

so, why not keep using the SONAR 4? perhaps you could use the money you would spend on "reprogramming" to buy a 64-bit computer?

i usually select the MIDI track, not the output track. example: if i have 4 or 5 instruments in Kontakt, i solo whichever MIDI track is driving that instrument, and while all the outputs now show up as "soloed", only the one instrument is active because the MIDI track is the only one soloed.

then again, there is a function for "exclusive solo" which may behave differently in your scenario. https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Playback.16.html or "solo override" https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Playback.17.html

good call. for some reason i didn't search the Korg.ins, just looked at the top bunch of rows and figured it was generic... 

7 minutes ago, User 905133 said:

I have the old Korg.ins file(2011) on my BU HDD.  It has the basic instrument definition for the KORG 05R/W as follows:

I was under the impression the old ins files were still available from the Cakewalk site. I can't imagine that Korg *.ins files are not available.  Or is someone looking for a Korg 2024 file?

John was looking for the Korg 05R/W INS file which i believe is different than the overall Korg INS file.