RE: is there anything a PTR1 can do not available on PTR2
- From: "Judy W" <judyw@xxxxxxxxxxxxx>
- To: <ptr1-users@xxxxxxxxxxxxx>
- Date: Thu, 12 Oct 2006 14:48:23 -0500
The manual isn't good and that's not just my opinion. I have heard that from
someone in support. The translation from Japanese wasn't done well.
I have never used the software because I'm not interested in creating daisy.
I just want to pull the mp3 in to sound forge or studio recorder.
Judy
-----Original Message-----
From: ptr1-users-bounce@xxxxxxxxxxxxx
[mailto:ptr1-users-bounce@xxxxxxxxxxxxx]On Behalf Of Rays home
Sent: Thursday, October 12, 2006 1:58 PM
To: ptr1-users@xxxxxxxxxxxxx
Subject: RE: is there anything a PTR1 can do not available on PTR2
Must say I find what I'm hearing about the PRS software
facinating. What has just been said sounds a bit like Sound
Forges ability to chop a file up into regions by detecting
silences and thresholds, and of course these regions can be
saved as files. Am I getting the drift here?
On David's quesitons, I just wonder, how good is the manual
for the PTR2 and the associated software? Unfortunately I've
not found the money to subscribe to Brian Hartgen's Infotech
just yet, otherwise I might know better.
Maybe in the meantime I should go and look at the web site.
If anyone does have comments re. the manual and any tutorials,
I'd like to hear.
Thanks.
Ray.
Hello,
Completely agree with the thoughts below.
Just want to make sure that people know about the editing
capabilities in the PRS. I find the audio editing by splitting
phrases, and then cut and paste of phrases very powerful. For
example, the speaker coughs; you can get the cough into a
separate phrase and then just delete it. Of course, that cough
is not really gone until you create the distribution copy or
do an audio export.
Best George
-----Original Message----- From:
ptr1-users-bounce@xxxxxxxxxxxxx
[mailto:ptr1-users-bounce@xxxxxxxxxxxxx] On Behalf Of
Cuthbertson, Jamie Sent: there anything a PTR1 can do not
available on PTR2
Daveed, Basically forget using the page and group
settings if you don't want to make use of them within a
DAISY end product. Stick entirely to using the heading key to
mark locations of interest. Once you've finished your
recording on the PTR2, finalise the CD and import the DAISY
title into the PRS software. Your heading markers will be
used to determine the sections in the imported DAISY title.
Next edit all the audio in whatever way best suits your
purposes for the programme you are creating. Once all
editing is complete, use the "Audio Export" feature to
generate a different DAISY title in which the chunks of
audio, that relate to each section, will be reorganised so
that you end up with a unique audio file for each section.
You can then access the audio files and use them in other
editing software if required, in the knowledge that the audio
has been tidied up to be how you want it. Hope this
helps.
Jamie
-----Original Message----- From:
ptr1-users-bounce@xxxxxxxxxxxxx
[mailto:ptr1-users-bounce@xxxxxxxxxxxxx] On Behalf Of Daveed
Mandell Sent: Tue, 10 October 2006 14:58 To:
ptr1-users@xxxxxxxxxxxxx Subject: Re: is there anything a
PTR1 can do not available on PTR2
So, what do I do, Michael, with files I've recorded on the
PTR2 where I've marked various headings and pages, to
indicate possible sound bites? Must I then use the PRS to
find and isolate them, and then move to Sound Forge? I still
haven't received an answer to my basic quewstion from anyone
here, even though I think I understand the overall picutre
somewhat better. I'm on tight deadlines and don't have lots
of time to pla around with all kinds of software. So what's
the procedure these possible cuts and isolate them? I assume
I should forget about using the Page or Group keys on the
PTR2, since since using the PRS Audio Export probably won't
help me find those marks; but I assume also that when using
the Heading Key on the PTR2, and then the PRS Audio Export,
I'll end up with separate audio files for each section. So
far, niether IRTI in the US, nor Plextor Japan, hasn't
assisted me. Plextor USA a\has washed its hand entirely of
the Plextalk products. I urge people in the USA to contact
Plextor USA's public relations outlet asking Plesxtor to
actively support their Plextalk products. It is
unbelieveable to me that Plextor would decide to provide
absolutely no support whatsoever for their own products. A
--DaveedInterested persons should write \ marcom@xxxxxxxxxxx
-- t 10:44 PM 10/6/2006, you wrote: Daveed, you wrote:
Sorry, I didn't make it clear that I would be pressing the
Heading Key at various times to mark passages of a
particular speaker for use as sound bites in my radio news
reports. I would not be using the PRS at all.
If you just press the heading key, the Plextalks will not
create a new audio file in DAISY recordings.
Without the PRS, you cannot convert the markers, which are set
by pressing the heading key into beginnings of new audio
files. One can do that with the PRS, by using the Audio
Export function from the tools menu. With this function, one
can create audio files, which truly reflect all the inserts,
overwrites, heading markers etc. of a DAISY recording. If you
move the recording to a pC, it is no problem to use the PRS
for that.The PTR2 is a great tool for blind radio journalists.
I know some, who use the Plextalk regularly.
For me, the most important thing in a firmware update would
be a better way to fast forward and rewind. This doesn't work
as well as it does on say the new Edirol R-09.
<*** Michael Lang ***>
---------------------------------------------------------------------------
To leave the list at any time, please write to
<ptr1-users-request@xxxxxxxxxxxxx> with unsubscribe ptr1-users in the
subject or the body. The list home page is at
<//www.freelists.org/list/ptr1-users/>.
---------------------------------------------------------------------------
To leave the list at any time, please write to
<ptr1-users-request@xxxxxxxxxxxxx> with unsubscribe ptr1-users in the subject
or the body. The list home page is at
<//www.freelists.org/list/ptr1-users/>.
Other related posts:
