Effetti in mode setup kurzweil pc3x

demel 14-07-15 15.29
salve ragazzi cerco di essere chiaro sul problema che mi assilla
Allora in pratica ho creato un setup sul mio pc3 con 8 zone ad ognuna delle quali ho assegnato un suono ed un channelmidi diverso ora però succede che fino al channelmidi 6 gli effetti suoi suoni li sento mentre dal cannel7 in poi non riesco più a sentire gli effetti
qualcuno di buona volontà??? sto impazzendoemo
cecchino 14-07-15 15.46
Hai semplicemente esaurito il numero massimo di slot (16) disponibili per gli effetti.
La PC3 dà quindi priorità ai program sui canali MIDi a numero più basso.
Soluzioni? prova ad usare effetti meno ingordi, oppure sacrifica i suoni dove gli effetti sono meno importanti assegnando loro dei canali MIDI più alti (non c'è bisogno di scambiare o spostare le zone, basta operare nella schermata principale del setup edit).
Edited 14 Lug. 2015 13:47
demel 14-07-15 16.09
si sputtana tutto :( se muovo i channel
ora si sta presentando un problema ancor più rompi scatole
in questo setup ho 3 riff che partono in automatico su 3 tasti della tastiera configurati tutti a 104 bpm uno di questi riff ha come effetto un tremolo che nel momento in cui faccio partire gli altri 2 riff premendo i rispettivi tasti si sfalsa non andando più a bpm
obiwan 14-07-15 16.35
Senza bisogno di cambiare canali midi puoi andare nella pagina effetti e mettere "N" in quelli che non reputi necessari. Oltrettuto se ci sono effetti in comune puoi disattivarli nella stessa pagina e fare un override nella pagina AUX FX mandando l'effetto desiderato solo nei canali che t'interessano. Ti consiglio anche di usare l'override quando hai un reverbero particolarmente "avido" di risorse. Meglio utilizzare il "sax chamber" o il "medium hall" che utilizzano un solo dsp. Riguardo il riff, se non ricordo male ci dovrebbe essere una funzione "sync to" o qualcosa del genere.
Tutto questo nella PC3K...magari nella X cambia qualcosa?! emo
Edited 14 Lug. 2015 14:37
demel 14-07-15 16.42
problema effetti risolto!!! un thanks per entrambi!!! per quanto riguarda il sync qualcuno ha avuto il mio stesso problema e sa come risolvere?
obiwan 14-07-15 17.23
emo

Non ho mai usato i riff... hai dato un'occhiata al manuale? Nella pagina 7-60 del manuale della K ne parla. Dovrebbe parlarne anche nella X suppongo emo
obiwan 14-07-15 17.26
SyncZone
The SyncZone parameter determines which zone a riff will sync to. You can choose to sync to a
riff or arpeggio in a specific zone by setting SyncZone to Riff 1–16 or Arp1‐16, and the current
riff will always sync to the riff or arpeggio in the set zone. For example, if you have a drum riff
in zone 1 and a bass riff in zone 2, you may always want the bass riff in zone 2 to sync to the
drum riff in zone 1. In this case you would set the bass riff SyncZone to Riff 1.
You may want to have a little more freedom and not be tied to the drum riff as the main
“timekeeper.” Maybe you want to start with the bass riff and have the drum riff start later. In
this case you would set SyncZone to FirstRiff.Av. With this setting, the riff will look for the first
available riff to sync to. So if both the drum riff and the bass riff have this parameter set to
FirstRiff.Av., the riff that is started first will be the master. If the bass riff starts first, the drum
riff will see that as the first available riff to sync to and will do so. If the drum riff is started first,
the bass riff will see that as the first available riff to sync to and will do so. This can be very
handy if you have multiple riffs and want to do some live remixing; you could have the drums
drop out, and—as long is there is a riff playing—they will sync back up when triggered again.
You can also choose FirstArp.Av., which behaves the same way as FirstRiff.Av., but makes your
riff look for the first available arpeggiator to sync to. A setting of Main Seq. will sync the riff to
the song currently loaded in Song mode. You can select a song in Song mode, then play it from
setup mode with the front panel Play/Pause button. (Doing this temporarily replaces the programs
in your setup’s zones with the program used for each channel in the song, so it’s best to make a setup that
uses the same programs as your song on the same MIDI channels. If you plan on syncing riffs with a
song, it may be easier to start by creating a setup, then recording the setup into a song. See Recording A
Setup To Song Mode on page 7‐69 for details.) A setting of First Avail. will sync the riff to the first
available riff, arpeggiator, or song from Song mode.
Note: If you have multiple riffs or arpeggiators already playing when using FirstRiff.Av., FirstArp.Av.,
or First Avail. for the current riff, the current riff will sync to the riff or arpeggiator of the lowest
numbered zone that has a riff or arpeggiator playing.
SyncType
The SyncType parameter allows you to choose how your riff will sync to other riffs,
arpeggiators, and Songs (depending on your settings made for the SyncZone parameter.) With
SyncType set to None, your riff will start playing as soon as it is triggered. It will not sync to
anything. With SyncType set to DownBeat, if there is already something playing to sync to, the
current riff will wait for the downbeat of the next measure before starting; so, you can trigger the
riff to start ahead of time, and have it start in sync at the downbeat of the next measure. If
Syncing to an arpeggiator, see Num Beats on page 7‐53 for details on changing when an arpeggiator’s
downbeat will occur. With SyncType set to AnyBeat, if there is already a something playing to
sync to, the riff will wait only until the next beat. Depending on when you trigger the riff, it will
sync up, but it may be on an upbeat or a downbeat.
obiwan 14-07-15 17.27
With SyncType set to DownBeatWait, the riff will wait for the downbeat of the next measure to
start. The difference from DownBeat is that if there is nothing playing to sync to, the riff will not
start. This can be useful if you want to start multiple riffs synced to one riff. You could have a
bass riff set to DownBeatWait, for instance, and trigger the riff while no other riffs are running.
As soon as you start another riff, the bass riff will start playing as well (provided that it is set to
sync to another riff or to the first available riff.) If another riff is already running,
DownBeatWait behaves just like DownBeat.
With SyncType set to AnyBeatWait, the riff will wait for the next beat to start. The difference
from AnyBeat is that if there is nothing playing to sync to, this riff will not start. This can be
useful if you want to start multiple riffs synced to one riff. You could have a bass riff set to
AnyBeatWait, for instance, and trigger the riff while no other riffs are running. As soon as you
start another riff, the bass riff will start playing as well (provided that it is set to sync to another
riff or the first available). If something is already playing to sync to, AnyBeatWait behaves just
like AnyBeat.
With SyncType set to Loop, if there is already a riff or song playing to sync to, the current riff
will wait for the playing riff or song to restart its loop (if it is looped) before starting (see
Loop on page 7‐59 for looping riffs, and Loop on page 12‐11 for looping songs.) This way you can
trigger the riff to start ahead of time, and have it start in sync at the start of the playing riff or
song’s loop.
With SyncType set to Stop, if there is already something playing to sync to, the current riff will
wait for what is playing to stop before starting. This way you can trigger the riff to start ahead of
time, and have it start in sync at the release (stopping) of the riff, arpeggiator, or song that you
are syncing to.
obiwan 14-07-15 17.27
With SyncType set to StartWait, if there is nothing playing to sync to, the current riff will wait
for something it can sync to to begin playing first before starting. This is similar to
DownBeatWait, but it will only trigger the riff the first time that whatever it is syncing to starts.
This way you can trigger the riff to start ahead of time, and have it start in sync at the start of the
riff, arpeggiator, or song that you are syncing to. If you stop the riff and try to start it again while
the thing you are syncing to is already playing, StartWait will not start the riff.
With SyncType set to LoopWait, if there is already a riff or song playing to sync to, the current
riff will wait for the playing riff or song to restart its loop (if it is looped) before starting (see
Loop on page 7‐59 for looping riffs, and Loop on page 12‐11 for looping songs.) This way you can
trigger the riff to start ahead of time, and have it start in sync at the start of the playing riff or
song’s loop. The difference from Loop is that if there is nothing playing to sync to, the riff will
not start. If the riff or song that you are syncing to is already running, LoopWait behaves just
like Loop.
With SyncType set to StopWait, if there is already something playing to sync to, the current riff
will wait for what is playing to stop before starting. This way you can trigger the riff to start
ahead of time, and have it start in sync at the release (stopping) of the riff, arpeggiator, or song
that you are syncing to. The difference from Stop is that if there is nothing playing to sync to, the
riff will not start. This can be useful if you want to get your riff ready to sync before you start
whatever you are syncing it to. If the riff or song that you are syncing to is already running,
StopWait behaves just like Stop.