#SunRize
13 messages in this thread
Fred,
Yes, you should read the manual.
As far a partitioning the drive, I have yet to crash it in about a year's worth
of use. If all the rest of the stuff is replacable, don't worry about it now if
you'll wind up having to do it all over again when you get your new drive. (but
don't point a finger at me if it crashes!!<g>).
As far as setting up directories for tracks, that is unnecessary. All you need
is a directory for all the sound samples.
If you want to change the speed of the playback, you can adjust the rate:
higher=faster.
For video work, I find that sampling at the 32000 rate works fine. This gives
you a frequency response up to 16 khz (notice the math). This is better than
most linear audio. You can sample higher of course, but it eats up more hard
drive space.
Most one hour wedding videos I do use about 300-400 megs if its mono. I just
finished a Stereo 5 track 52 minute video that used about 700 megs.
By the way I have a new sideline…editing music for ice skaters. If there's a
rink near you, check it out !
Also, those problems you've been having about keeping multiple sources in
sync…. just digitize them, and you can doo whatever you need to.
Regards, Gary
Gary,
I hope you don't mind my jumping into your thread on the Studio 16
software. I hve been using V. 3.0 of the Studio 16 software and an AD516
card to digitize audio for some vacaction videos that I put together for
fun using the Toaster 4000. For the most part, I have found 3.0 Studio 16
to be an easy to use and reliable program. However, in digitizing and
working with some 900 MB of files for my last 1 h 15 min video, I found
that the software frequently crased and locked up my Amiga when doing a
destructive edit in the editor. It is often valuable to be able to do
destructive edits to remove dead periods at the beginning and end of an
audio clip, as well as to occasionally remove mistakes within the audio
clip itself. About half the time that I attempt to do a destructive edit
the computer will lock up. I called SunRize about this, and they said
"Yes, we know we have aproblem with the editor, but we have not been able
to solve it." I am curious whether you or others have experienced these
crashes with destructive edits. If it is pertinent, I am using the AD516
in an Amiga 2000 with 18 MB of memory, a GVP 040 accelerator, and a
Micropolis 1.7 GB HD.
Tom
Tom, I have been using what will probably be version 3.01, and it seems less
prone to crashing.
In any event, you may not even need to do destructive edits in the first place.
Just delete what you don't want in Editor, and it will stay that way…even
without "making changes permanent".
Remember too that when you ask Studio 16 to make destructive changes, it first
creates a new file THEN deletes the old one, so you'd better have enough drive
space to hold both at the same time.
Regards, Gary
Gary,
Thanks for the reply. Yes, I realize that you don't have to do
destructive edits and that deletions can be done without making the
changes permanent. However, most of my videos are about 1.5 hr long, and
I use both narration tracks, background music, and occasionally the
existing sound on the original video footage. Thus even my 1.7 GB
Micropolis can be pushed for enough space, and I hate to have useless
audio using up some of my precious disk space. I look forward to
receiving v. 3.01 in the hopes that this problem with the editor, which
existed in version 2.0 as well may finally have ben addressed.
Tom
Tom, What rate are you sampling at? I find 32000 quite sufficient for video
work. Regards, Gary
Gary,
i agree. For my video work I never sample higher than 32K. The resulting
frequency range is more than adequate for the AFM Hi-Fi recording used on
my decks. Gary, what hard drive are you using with Studio 16? I have
found the Micropolis 2117 AV drive to work very well, although I have
never attempted to play back more than six tracks at once. Also, did you
use the Big Blocks routine provided by SunRize to optimize your disk for
Studio 16? So far, since I have had no problems playing back up to six
tracks simultaneously, I have not bothered to reformat my 2117 using the
Big Blocks program.
Tom
I am using the same drive. Big blocks seems to help run things like editing
functionfaster. Regards, Gary
Gary,
SunRIze published an 'alert' to everyone that BigBlocks had some bad
problems due to some incompatibility with some low level software of the OS>
They had advised not using it. It is possible that this is old news that is
rendered moot by a later release, but I hadn't hear anything to this effect.
Might want to call them about the BigBlocks status.
wmc – via Autopilot!
Wayne, When did you hear about the problem with Big Blocks? I am a beta tester
for SunRize, and have not heard about it. Regards, Gary
>> I am a beta tester for SunRize, and have not heard about it.
Well, that explains it! They expected you to find it yourself. <g>
– Jim, on AutoPilot!
Gary,
It was shortly after the 3.0 release – like within 2-3 weeks. In fact I
just found it – a Post card they sent to me with the warning on 7 Feb 94.
It talks about a prblem with the FS that BigBlocks interfaces with and that
CBM is working on the fix to the FS (heh, heh, little peice of history
here…)
wmc – via Autopilot!
Tom,
For those kinds of cuts, just mark the range in the editor and hit right Amiga
+ D and they will be gone. Never had a crash doing this. After you are
finished editing the sample, do a Make Permanent.
Glenn
Glenn,
Thanks for the advice, but that is essentially what I have been doing.
Amiga + D is just a non-destructive edit. Choosing Make Permanent then
makes it a destructive edit. I agree that for some reason making the
deletion i na non-destructive fashion followed by Make Permanent (i.e., a
destructive edit) does cause fewer crashes than simply initially making a
destructive edit, but even with this method I have had Studio 16 crash a
number of times.
Tom