|
Soundscape Editor Commands - Summary of Keyboard & Mouse
Shortcuts
|
|
HDR1, SS32/REd & Mixtreme EPP Mixer Channels - Equal Power Panning explained
|
|
|
|
EDITOR: Keyboard Stop & Play keys cease responding – this may be because of a
‘feature’ of the Timeworks CompressorX plugin – when this plugin
graphic window is ‘in focus’, the
keyboard UP and DOWN keys control the last parameter slider you touched for
fine control. To regain Stop & Play function make
another Editor window active, or close Timeworks CompressorX
graphic window.
|
|
SEARCH & Wildcards
|
|
Why is sample rate sometimes red?
|
|
HDR1 & SS32/REd - Saving your Work
& Settings - What is Saved with Arrangement,
Mixer and |Settings|Save Settings
|
|
HDR1 & SS32/REd - Multiple &
Separate Editor Instances - If you have 2 or more Units, you can run them
simultaneously as separate instances e.g. run 3 units HDR1 in 12trks/16bit mode
(=36tracks), and 1 unit HDR1 in 6trks/24bit mode, OR run all units completely
separate for disk-disk copy (on each unit) and Defragging.
|
|
Suddenly No Analog Sound in/out ? -
HDR1, HDR1+ & R.Ed/SS32
|
|
Semaphore Errors at Startup? - HDR1,
HDR1+ & R.Ed/SS32
|
|
Using SS32/REd
& Mixtreme @ fs=96kHz:- how to setup.
Currently, the 96KHz option on Mixtreme is only
intended for users that connect it to a R.Ed. The
only way it works is to slave Mixtreme to Superclock + TDIFA or B. Superclock
must be derived from R.Ed/SS32., which means R.Ed/SS32 Settings|SyncOut
= Superclock.
|
|
Shrink Takes Tip:
Shrink takes will not break files up if the slice removed between wanted
material is too small: The smallest entity on a disk is a sector, which
contains 512 bytes, or 256 samples in case of 16-bit samples. Since the criterium that SS uses is that no Hard Disk sector can
belong to more than one Take, and that it does not make sense to split a Take
in two if no entire sectors in between can be freed, the amount you have to take out to split a Take in
two is between 256 and 511 samples, depending on the split
point's physical position on the disk in relation to the sector boundaries,
but regardless of the Take size.
|
|
Notes & Tips
for SS32/REd:
Editor:
-
Maximum size per SDisk is = 1 Terrabyte.
This only counts for newly formatted SDisks V5.1
onwards.
(Max Formatted sDisk size is
137GB up to V5.0)
-
Maximum number of Parts per arrangement is 16384 (V3.7 onwards)
- SFiles-per-SDisk limit 65536, (instead of 32768, only for
SDisks formatted V3.8 onwards).
- Maximum
Single Filesize on SDisk
is 4GB = 4096MB = 4194304.51 KB = 4294967817 bytes.
- Max
record times: (= max filesize @ 16bit and 24bit)
table
|
Samplerate
|
16bit
|
24bit
|
|
22050Hz
|
27:03:08:16
|
18:02:07:17
|
|
32000Hz
|
18:38:26:21
|
12:25:39:06
|
|
44100Hz
|
13:31:34:07
|
09:01:03:21
|
|
48000Hz
|
12:25:37:22
|
08:17:06:04
|
|
88200Hz
|
06:45:47:03
|
04:30:31:23
|
|
96000Hz
|
06:12:48:22
|
04:08:33:02
|
Max
Size .WAV (or BWF) file you can export to Windows from Soundscape: 2.1GB.
However some Windows Editors will not save files this large.
___________________________________________________________________________________________
OMF Export:
- Only
Takes residing on Virtual Tracks 1-128 are included.
-
Stereo takes are exported as Mono L & R soundfiles.
-
Muted Parts are not considered as Active Parts; if you want to export Muted
Parts, select "Export all parts...."
-
Filenames/Partnames can be up to 53 characters
long. If exporting to MAC, best to limit all names to 25 characters.
OMF Import:
- takes are put in arr on Virtual
Tracks 1-128.
-
Soundscape outputs are automatically assigned to parts residing on Virtual
Tracks 1-32, remaining parts are assigned mute.
-
Sometimes Imports from Digital Performer to SS reads the first 127 tracks.
- Filenames/Partnames can be up to 53 characters long. If importing
from MAC, you may only get 31 characters.
___________________________________________________________________________________________
ProTools Import/Export:
- Only
Parts residing on first 64 virtual tracks of SS Arr
are considered for Export.
- SS
Part Volume is exported as PT Autom, if option
enabled.
- SS Arr must be flattened before export.
- All
Filenames AND Partnames are best kept under 25 characters.
Although Mac filenames are permitted to 31 characters, Soundscape limits to
25 to reserve space for number and extension. SS Export will strip spaces
from longer filenames to preserve first 25 characters.
|
|
Re-name Mixer Inputs/Outputs:
Although never documented, there is currently a way to rename all the
inputs/outputs/busses in SSHDR1/R.Ed/SS32 mixers, by adding i/o 'alias' lines
to the corresponding ssEditor INI file, under the [MixWnd]
section.
This is an example of such i/o 'alias' lines:
Inp1 alias 00000N3884D1B=RODE NT2;Rode
Inp2 alias 00000N3884D1B=NEUMANN TLM103;Neum
Out31 alias 00000N3884D1B=MAIN;Main
Out32 alias 00000N3884D1B=MAIN (R);Main (R)
Bus25 alias 00000N3884D1B=REVERB;Rvb
Bus26 alias 00000N3884D1B=REVERB (R);Rvb (R)
This is the syntax:
<Inp1..28, Out1..32, Bus1..32> alias <SS Unit serial
number>=<alias for normal mixer view>;<optional alias for small
mixer view>
The reason why this has not been documented is that SS haven't found the time
yet to make a user interface for this, so that you don't have to edit the INI
files yourself. However you can already do it like described above if you
want...
Note: if you do make these changes, the above lines refer to a single i/o
entity. Therefore naming may become confusing when selecting
input/output/buss routing on mixer channel that have multiple i/o routing
possibilities. Also long names may not fit in the channel strip. The letters
in brackets (R) are part of the name.
|
|
WVF File Path...changing the default: Waveforms are stored by default
in C:\Soundscape\Wvf folder.
When creating your own shortcuts to start Editor, make sure the "Start
In:" property of any corresponding Soundscape shortcut is set to
"C:\Soundscape". This way the WVF files will be stored in
"C:\Soundscape\Wvf".
If the above is set correctly, but you want to store the WVF files in a different folder,
you can add a line to the corresponding Editor INI file under the [MainWnd]
section that specifies the new WVF path: e.g.
[MainWnd]
Iffv=IFFV1.3
WvFormFilePath=C:\Test1\Test2\
.....(Note that
there needs to be a terminating "\" specified) will store all WVF
files in "C:\Test1\Test2\" provided that this folder exists, so be
sure to also make these folders.
|
|
Finding a
"lost" window: If for some reason the SS window (eg Arr, Mix, SFileMgr, MarkerDir, Buffer, SDisks, AVI, BigTime) you
require does not appear because it's position has possibly been moved or
saved off-screen, you can use the Windows built-in key commands to get it
back in view:
First, click on the Soundscape Editor Title Bar as a starting point, then
type the hot-key for the required window (If you don't know the hot-key, just
select from the View Menu) to make that window become the "focus",
even if it's not visible.
Then type ALT SPACEBAR (hold ALT while tapping the spacebar once), then
release ALT and type M.
The focused Window will now be subject to vertical and lateral movement by
your keyboard's arrow keys.
Move the Window into view via the arrow keys, and press ENTER.
Then you can re-size & place your Window where you want it and press Preferences|Save Settings - all subsequent windows will
start at current positions.(( Excepting Mix, where the mixer position is
saved with the mixer file. You should re-save mixer (possibly use another
name). If you press Preferences|Save Settings all
subsequent New Mixers will start at current position.))
|
|
TDIF RIBBON CABLES &
Y-Split/Daisy-Chain Loop LEADS - Diagrams to make your own TDIF-TDIF and Y-Split Ribbon Cable leads.
|
|
TDIF - TDIF Lead - Screened Pair Cable - With a bit of mind bending you
can also make y-leads with 4-pair
Screened Multicore Cable .... eg Mogami 3162 8-scr-pr Digital
Cable. Use screened cables for long runs. I found this cable type works ok
for up to 15 metres in most instances, although I have had problems
specifically with Tascam DA88 with screened cables
4m long, - but not with later models eg DA98/38/78.
|
|
Mixtreme MIDI - Connections and ribbon cable
modification.
|
|
Cable Select for Hard Drives: - There is a mod you can easily
make (with care) to HDR1's
so that you can set all your drives to CSEL (CS), and then any drive can be
put in any slot:- (R.Ed is usually factory made to
use CS disks).
|
|
Power On Reset Mod for HDR1 / HDR1+.
- If there is a 'Hardware not present' message when starting the software but
eventually the software starts and runs normally, this can be caused by a
reset problem.
|
|
R.Ed/SS32 & V3.5(or
later) startup: "Soundscape 1 hardware properties are not compatible - [DSP MASK
= 002301, SIMMS = 770001]" - you may get this rather cryptic error message when
starting EditorV3.5(or later). This error message in fact means that the
memory test on the second memory SIMM module in your R.Ed
failed, either because it is not present, defective, or because it is not
properly inserted.
This second SIMM module is used from V3.5 (required for crossfade
functionality) and therefore the memory test was introduced from this version
on.
If you feel confident enough: open the R.Ed case
and check the SIMM memory module which is closest to the rear panel. Remove
it and reseat it in the socket.
If that doesn’t correct the problem, you may have a bad SIMM—here
are the specifications for a replacement:
- SIMMS must be 16MByte, FP (fast page) or EDO,
60ns access time or less, no parity.
- There is an additional requirement, which is more difficult to check: the
"page-size" must be 2k.
Somewhat older SIMMS (with 8 chips on them) usually are 2k. Some newer SIMMS
(with fewer chips on them) have 4k pages and cannot be used.
There's probably no harm in trying out a few 16Mbyte SIMMS, e.g. taken from
an old motherboard. The memory test at the startup of the v3.5 editor
software will show if it's ok or not.
|
|
SS32/REd EPP Host Interface: For REd/SS32 ONLY
- Diagram (NOT SSHDR1+, which requires a cable containing active electronic
components - available from your Dealer/Distributor).
|
|
SS32/REd and Word/Super-clock:
handy hints
|
|
New PCI Interface
Card, Get error message: "Soundscape 1:SSAC2 hardware error!" ??
There is the possibility, with some of the early REd
units, that the host card needs to be modified to work with the PCI interface.
There are two ways to tell if you need this mod.
1. Hook it up to a PCI interface. If you get an error stating:
"Soundscape 1:SSAC2 hardware error!", you will need the mod or a
new host card.
2. Open the unit and look at the Host interface card (this is not
recommended. ESD sensitive components present. Proceed at your own risk) The
resistor at R3 must be 820r if it is not you will need the mod or a new Host
interface.
If you suspect you need either the mod or a replacement card: For
international customers this would be done through your dealer as with any
other repair.
|
|
FAST AVMaster
stuff
|
|
Mixtreme
Freezing, odd behaviour & VIA Chipsets - (see also http://www.soundscape-digital.com/Support/Faq/TechNotes/0018/ )
The problem seems to lie in the combination of VIA chipsets and older Mixtreme cards. Seems the older serial # cards lock up or
virtually have no intercourse with the external Tdif
device.
Some history from Dirk:
"When we designed Mixtreme,
the Motorola DSP chip had a known error. The PCI clock input of the DSP was
out of spec. Motorola even documented a work-around in the form of a small
PLL chip, capable of buffering the PCI clock line without causing delay. The Mixtreme was designed to include this chip right from the
start. When we finally got to the release we were informed that on some
systems the PLL caused problems. We didn't trust this solution completely so
we tried several systems ourselves without a PLL fitted and all worked very
well. Also, boards from competitors using the same DSP (Echo and Sonorus) didn't use this PLL. There wasn't even any room
on their boards. So we faced a dilemma and decided not to fit these PLL's on the initial batch. Then came the famous VIA
chipset and it turned out that many problems could be solved by using the
PLL. VIA seems to be very sensitive to the high capacitance of the PCI clock pin.
Unfortunately, some of the chipset revisions have other quirks too.
If we suspect that the missing PLL is causing problems, we ask to return the
board and we fit one free of charge. There is one side-effect on this PLL
though, "Spread Spectrum" clocking should be disabled in the BIOS
because such a clock signal won't pass through the PLL correctly."
How to tell if your Mixtreme has PLL
fitted: look between the PCI edge connector and the nearest very
large chip (U1) for a marking 'U2'
- if only a tiny resistor here across 2 pins of U2 (R69), and 6 bare pads,
then no PLL present.
- if there is a 8-pin small chip here, then the PLL
present.
|
|
One Sample for
Nothing?
Have you ever noticed all sfiles Takes
recorded with the R Loc defining the end are always made 1 sample longer than
the Part shown in the arr? This has to be so, so
that when L<>R recordings are made with the length specified by
locators (eg some smpte
rates, Bar/Counts etc snapping, which could conceivably not translate to
mathematically exact samples - the maths of
that....another time) the sfile is made up to the
next sample longer. Subsequent copies or looping to similar snapping
parameters then has no gaps. The consequences of this are:
Snap=OFF: an sfile dragged into
the arr will be 1 sample longer than the original
shown Record Take, regardless of where or how (ie
to Loc) it is placed in the arr.
Snap=Active (any setting): an sfile
dragged into the arr will be 1 sample longer than the
original shown Record Take, UNLESS it is dragged exactly to the start or end
of any (does not have to be original) Take in the arr
which happens to be 1 sample shorter than the dragged-in file:- THEN the
dragged-in part will be 1 sample shorter.
|
|
When formatting a SDisk does
it remap bad blocks? I encouter a status error
on one of my drives at a certain adress. Maybe that
after a good format that adress will be avoided. If
soundscape formats a harddrive
(not the quick but the slow format) does it remap any bad blocks?
- No, it is the drive itself that normally does this. However, this really
slows down the disk performance. I would recommand
to replace a disk as soon as it starts to show bad sectors.
|
|
Some Arrangements created with SS32/REd will not
open when exported to HDR1(+):. - Most
likely this is because the SSHDR1 Editor version (V3.6.1?) doesn't understand
the newer arrangefile format generated by R.Ed Editor V3.7.x. This can happen in case you used
certain V3.7 features that V3.6.1 doesn't have, e.g. multiple 'active' Parts
assigned to the same output positioned on the same time zone.
|
|
Black toolbar and tape
transport? - Editor V3.8
(and later) XP Visual Style - This is a common problem, very easy to
solve.
- Install the latest drivers for your Graphics Card.
- or - rightclick on a desktop and
than select: Properties|Settings|Colour Quality
...... set to “Highest(32bit)”.
- or - rightclick
on a desktop and than select: Properties|Settings|Advanced|Troubleshoot......
move the "Hardware Acceleration" slider one tab to the left.
- or - do the following:
start>programs>Soundscape>right-click soundscape
editor(1 unit)>properties>compability
>then check "run this program in compability
mode for win98/me"
- or - in case you prefer the 'older' W98 visual style, you can
force the Editor program to use the Win98 bitmaps instead of the
smooth-transparent XP bitmaps, in case you are running XP. This can be done
by adding '-b98' to the command line that specifies the editor program, just
before the INI file is specified.
e.g. in case of a default installation with 1 unit, change the 'Target'
command line in the 'Properties' page of the Soundscape shortcut that
launches the Editor as follows:
"C:\Program Files\Soundscape\Editor\Version 3.8\SrEditor.exe -b98
SSEditor1.ini"
|
|
Inactive! message
in the mixer window caption bar.... undocumented feature SS32/REd
EditorV4.0 onwards:
If you want to re-activate the mixer again without changing the mixer, doubleclick on the mixer window caption bar.
This command can be used to reactivate a mixer that has been built inactive.
In some cases however, due to a warning, after clicking
OK, it is more likely that the user first changes the mixer load or routing,
to prevent the warning from appearing again.
|
|
Playing
more than 32 tracks at once: SS32 & REd.
|
|
VST & VSTi Streaming Error Messages:
There are 2 error messages existing that are related to
using VST plug-ins in ssEditor:
1/. "Mixer streaming channel count overflow!" message shows up in
case other applications (e.g. Cubase, Cakewalk
etc...) or the SS mixer has already eaten all available streams. In this
case, something else must already have taken all streams...The SS mixer that
you are trying to insert VST plug-ins into already has referenced all
available streams, or plug-in requires more streams than currently available.
Note that it is enough to 'eat' a stream for the SS mixer by just referring
to it by an Input or Output element.
Also, some VST's can invisibly eat more streams
than you intend... e.g. Voxengo Pristine Space,
where, although you may only be using it as stereo, can be internally set (in
it's Set In/Out config) so it grabs up to 8 streams
per instance!
2/. "VST plug-ins: native mixer elements processing
overload!" message is displayed in case the PC CPU cannot cope with the
required native processing for the currently used VST plug-ins. In addition,
the VST plug-in little windows in the mixer will turn red. In this case, try
increasing the native streaming buffer size, reduce the VST plug-in load, or
increase you PC CPU speed.
|
|
HOW AUTOSAVE WORKS:
(Editor V4.2 onwards-)
- Auto save arr/mix option added.
(See Settings|Preferences|General|Auto save
time...)
When an auto save time value is entered, every time this
value is elapsed and arrangement or mixer changes occurred in between, an
AUTOSAVE.ARR and/or AUTOSAVE.MIX file is created or updated in the PC disk
its corresponding Arr and Mix folders. (Default:
C:\Soundscape\Arr and C:\Soundscape\Mix\R.Ed)
This implies that the AUTOSAVE.ARR and/or AUTOSAVE.MIX
file is placed in the folders according to start-up .ini
file instruction, which was set last time Editor’s Save Settings was
used.
BTW, the exact (default) ini
file entries are:
MixFilePath=C:\Soundscape\Mix\
ArrFilePath=C:\Soundscape\Arr\R.Ed\
However, there is a dynamic feature to consider:
If, subsequently, during a current instance of Editor, a
MIX and/or ARR is opened from, or saved to, different PC folders than those
specified in the starting .ini file, the AUTOSAVE
files are then placed in these new folders; these locations continue to be
used until changed. Then, if you Save Settings, these new locations will be
written to the ini file, and used next time Editor
is started. If you don't Save Settings, the original specified locations will
be used next time Editor starts.
To locate the Autosave files, use Explorer Search for
Autosave.*
- wherever you prefer to manually Save your Mix/Arr (i.e. SDisk or PC disk), a backup is saved on the PC somewhere,
more or less up-to-date, should Editor or the PC have some unexpected
trouble, and you hadn't saved.
|
|
ASIO DRIVER: using SS Driver V4.2.5.1
or later, with external applications such as Melodyne, there may be
problems with the application acquiring ALL available ASIO streams…..
If VST and/or native tracks are used then this won't succeed because those
internal streams can't be used by ASIO. E.g. You may get a message "asio can't be used, direct-x driver has been
selected" when opening Melodyne” because
it wants to grab ALL the 'internal' streams, and can't because you used some
for Native tracks or VST's; this fix gets around
this, and forces Melodyne to use just the ASIO
streams you specify in the registry:-
[[ NOTE: Melodyne
V3.2.1.3 onwards no longer monopolizes all ASIO I/Os, so you can allow Melodyne to share an audio interface with other suitably
equipped programs.]]
There's an undocumented feature of the ASIO driver. If you
start RegEdit.exe and navigate to "HKLM\Software\Asio\Soundscape
ASIO", you will find a key for every application that used ASIO before.
You can restrict the streams that the application sees by creating 2 values,
"InputMap" for the recording streams, and
"OutputMap" for the playback streams. The
value type should be either a DWORD or BINARY. REG_DOWRD is the easiest to
use but is limited to mask only 31 streams, if set to FFFFFFFF then it
defaults to all streams. The value is actually a bit mask with a 1 for an
enabled stream and then converted to hexadecimal.
So, the following entries will limit ASIO for a specific application to the
first 16 streams:
InputMap REG_DWORD FFFF or REG_BINARY FF FF
OutputMap REG_DWORD FFFF or REG_BINARY FF FF
for 2 I/O's, streams 1&2, this would be 11 binary or
‘3’ Hex, or ‘3’ Decimal:
InputMap REG_DWORD 3 or REG_BINARY 3
OutputMap REG_DWORD 3 or REG_BINARY 3
For instance:
If you want streams 1&2 only, this is 11 binary, or '3'
Hex or ‘3’ Decimal.
If you want streams 3&4 only, this is 1100 binary, or
'C' Hex or '12' Decimal.
If you want streams 1-4 inclusive, this is 1111 binary, or
‘F’ hex or ‘15’ Decimal.
If you want streams 5&6 only, this is 110000 binary,
or ‘30’ Hex, or ‘48’ Decimal.
If you want streams 1-6 inclusive, this is 111111 binary,
or ‘3F’ Hex, or ‘63’ Decimal.
Hint: you can
use the Windows calculator in advanced mode to convert binary to hex or
decimal.
Example:
- Windows START | Run and type in ‘regedit’
- Go to HKey_Local_Machine\Software\Asio\Soundscape ASIO\Melodyne
- Right Click in Right pane, select New DWORD Value.
- Name this ‘InputMap’
- Right Click InputMap, and
select Modify; popup will ask for Value data (Hex by default) – enter
required Hex value as above, or switch Base to Decimal, and enter required
Decimal value. OK.
- Repeat above for ‘OutputMap’
|
|
Editor Installation
fails: Windows reports “The parameter is incorrect”
When trying to install Editor, run Setup.exe, you get
error message "The parameter is incorrect" and installation fails.
This is a 'feature' of the self-extractor utility - Very likely you are too
deep down the Windows Folder structure; put the files higher up the tree,
e.g. in C:\SoundscapeTemp\ Soundscape Editor V5.0\disk1
|
|
How to convert a
complete SS Arr to another Samplerate:
1. Load the SS Arr into CuiBono EDLConvert or SSL ProConvert.
2. Convert the Arr to Vegas Text arrangement
(*_cvVegas.txt file) (this is timebased and not samplebased!!) - quit EDLConvert/ProConvert.
3. Batch convert the new takes in the new Vegas folder to new required samplerate using AWaveAudio, SoundForge, Wavelab or similar.
I'd suggest using the BWF option (if available) so 'birth time stamps' are
not lost.
4. Replace the "old" files in the folder where the *_cvVegas.txt
file is with the new batch-converted ones.
5. Re-open the *_cvVegas.txt arrangement in EDLConvert/ProConvert
and convert to SS Arr.
6. bingo!!!
Note: this is particularly fast & easy if the SS Arr resides on a Native SDisk. Faster
still if EDLConvert-iSD version or ProConvert is used, as the arrangement can be read and
re-written to the sDisk without the need to export
Soundscape ARR to/from PC drive.
Works same for changing bit-rate. Remember though that
increasing bit-depth of the file gains nothing, and if reducing bit-depth the
program you use for conversion should be capable of some type of dither,
rather than just truncating the unused bits.
|
|
Does Sony VEGAS PRO support OMF?
Q: I have a VEGAS
project; does Vegas support OMF – how can I
open the project in SS?
A: No, Vegas does not
support OMF, however there is a way:
Assume you are using latest Vegas Pro 8.0b (Build 217) or higher.
You need SSL ProConvert V5 (= build 5.0.774) or
higher.
You MUST make sure ALL files in Vegas session are SAME samplerate
and file-type (eg .wav) (but can be mixed
bitrates), and are Mono or Stereo (ProConvert at
this time does not support multichannel .wav files - i.e. those with more
than 2 channels embedded).
As Vegas can use files all over the PC it's running on, it's best to organize
things so all used sound files reside in one Folder, possibly on an external
drive that you can take away; this is easy:
- In Vegas, do a File| "Save As" specifying a New Folder (e.g. on
your desired external drive) - save as 'Vegas Project File (*.veg)' and MAKE SURE you tick the option "Copy Media
with project", and select 'Copy Source media' NOT 'Create trimmed copies
of source media' in the popup, unless you only desire trimmed copies (with
handles).
- Next, in Vegas's Explorer, navigate to this New
Folder, and open the *.veg you just saved. This
forces Vegas to use just the files in the New Folder.
Once the above *.veg is open you need to make a
session that ProConvert can read:
- In Vegas, do a File| "Save As" and select 'Save as type:' =
"EDL Text File (*.txt)" - save in same New Folder.
Now you can open the above saved (Vegas).txt file in ProConvert
and magically turn it into a Soundscape Arr.
**********************************************************************************
Alternative to saving as Vegas TXT, you can use Vegas XML export script -
find that in Tools | Scripting | Export XML - this also opens in ProConvert.
Do NOT attempt to use Vegas's EDL script - this
only considers uppermost track of the Vegas session for export.
**********************************************************************************
Note: if writing session directly to SS Native sDisk
using ProConvert -
Vegas allows Stereo files on one track therefore 16 Stereo Tracks in Vegas =
32 Mono Tracks in Soundscape.
ProConvert makes 2 Mono Tracks out of Stereo
Tracks, consequently:-
If your track count exceeds 32 mono (or 16 stereo) tracks in Vegas, you will
need to let ProConvert 'see' two sDisks
If your track count exceeds 64 mono (or 32 stereo) tracks in Vegas, you will
need to let ProConvert 'see' three sDisks....
|
|
Parts won’t
Stereo or Multi-channel Link anymore
Stereo & Multi-channel linking follows the same rules:
Parts in Arr must start at same time, be same length,
reside on adjacent Virtual Tracks, on same Unit, and in same Layer.
Probably what you are having trouble with is the layer condition, possibly
because some other parts overlapped; currently there's no Tool to change
Layer - but there is a workaround:
Save your Arr; then select & Save the
troublesome parts as a mini-arr; open that, locate
the parts, copy them to some other tracks (i.e. make a "temporary
pile"), then drop another copy on top of the temporary pile so you have
created some parts which overlap; then use Flatten Arr
(Ctrl+Shift+K); This should re-set the parts all to
Layer 0, and you can now Stereo or Multi-channel link the Parts.. Then delete
the parts in the “temporary pile”, and save the mini-arr.
Then re-open your original Arr, delete the parts
which won't link (i.e. the parts you saved to the mini-arr)
and Ctrl-Drag the mini-arr in.
|