I have the new X30 and I would like to know if the only way to switch on the audio recorder is to push (and keep pushed ) the button on the left. Is there any way via software? I need something does not need to be hold down.
Thanks
And if you'd rather record compressed MP3 files, a lot longer, Resco and Vito make shareware recorders and NoteM is free. If you pick the latter, do a search for my comments on Aximsite on setting up NoteM button mapping and bitrates. It's not entirely intuitive, but easy.
I use NoteM and like it much better than the native voice recorder. I mapped it to the recorder button and when you hit the button it opens NoteM and starts recording automatically. It basically looks like the built in recorder, but is more extensive and sounds much better. It also shows you how much you have recorded and how much recording time you have left. You can also set it up to save the files on your SD card, which is nice. Here is a link to download it:
quick question...can u use ur axim to record streaming music over the internet? if so, how?
if not...can it be done with a pc instead? please let me know what software u need for this...thanx.
40iPlay C/S comes with a few servers. One of those, 40iConS, can record shoutcast streams, in various ways:
Code:
G:\iconsrv>40icons /?
40iConSrv v6.4.30.51 Copyright (C)2004 Cornel Huth 40th.com
Use:
-p:# port [default is 4003 (must be an odd unless -npc )]
-hn:a srvr hostname [default is current hostname]
-ip:a.b.c.d server IP# [default is first found of hostname]
-af:a.b.c.d client IP# [accept/reset from only this client|subnet]
-ka:# alive checks [optional max allowed alive check failures]
-w: width [default is 80 cols, min=64 max=148]
-h: height [default is 43 rows, min=8]
-nr no recurse [default is to recurse dirs searched]
-yr yes recurse [to override any -nr in spec file]
-pr:# priority class [0=normal, 2=high; def=2]
-spec:a spec file [default is 40iConS.txt in server directory]
filemask file mask [def=from spec file; if mask end in .mp3]
-chunk:# send chunk KB [def=128 KB (recommended size is 128)
-uncmap:# fast local UNC [def=0 full UNC, =1 fast local UNC]
-slow:# slow cmd net [def=0 fast cmd check; min=2, max=5 times]
-oggx:# ogg load mode [def=0 implicit scan for .ogg; 1=explicit only]
-findany:# find any file [def=0 find known types only; 1=find any]
-tos:# send timeout [def=15 seconds; range 1 to 600 seconds]
-rstp:# reset on port [default is 4002 (port-1)]
-scon:# enable SC [def=1 allow SC; =0 disable SC]
-scss:# store stream [def=0 no SC stream store; =1 store stream]
-scex:# extract mp3s [def=0 no extraction; =1 extract, =2 per title]
-scto:# recv timeout [def=15 seconds; range 2 to 600 seconds]
-sctc:# connect timeout[def=10 seconds; range 2 to 600 seconds]
-scac:# auto-reconnect [def=5 seconds; 0=none; range 1-60; stand-alone]
-sccc:# clean cut [def=0 no clean cut; =1 clean ends between titles]
-scca:# clean cut axe [def=0 no finetune cc-axe; range -32768 to 32768]
-sccu:# clean cut use [def=0 no finetune cc-use; range -32768 to 32768]
-scob:# outbuff size [def is 256 KB; # is in KB, 64 to 16384 by 8]
-scwx:# wait times [def is 6 WAIT FOR DATAs; range 3-10, ea 6 secs]
-scmd:# use meta-data [def=1 use meta-data; =0 to not use it]
-scpb:a replay stream [a=filename of raw stream to playback]
-scurl:a stream source [a=URL to stream; default is to wait for iPlayC]
Examples:
C:\>40iCon -nr ;cmd line switches override spec file
C:\>40iCon -spec:myspecs.txt ;use this spec file instead of 40iConS.txt
C:\>40iCon -hn:mintlnx -findany:1
C:\>40iCon -ip:192.168.1.99 -p:4002 -rstp:4099 -w:64 -h:16
C:\>40iCon "e:/mp3/oldies/*.mp3" ;only bother with matching oldies files
--- 40iSrv server has replaced this console server ---
C:\>40iCon -scpb:stream.raw -scex:1 ;stand-alone stream playback & extract
17-Apr-2003
-----------
The LnD Initial load size (OPT panel) should be set to at least
128 KB for best results. Smaller sizes (96, 64, 32 KB) may not
produce results as good. Play won't sound until this initial
load size has been received.
11-Jan-2003
-----------
> -----Original Message-----
> Subject: How to use the DSK out
> I am trying the get the DSK output mode working. I have set the OUT to dsk
> or DSK. What happens is that a file is created in the iRadio86a directory.
> The file name is the IP adres from the stream which is playing. No file
> extension. The file stays empty. What am I doing wrong??
I never did stream recording that way, and apparently it doesn't work.
dsk/DSK OUT is for .raw or .mp3 (.ogg) input, not streams. But, what I
do to get streams to wave, or mp3, is this:
G:\iradio>40iradios -scurl:http://212.18.198.75:8000 -scss:1
In other words, the server is the recorder. This puts it in stand-alone
mode, which generates a .raw file, such as
01/10/2003 11:36a 1,000,117 20030110_113259a_212.18.198.75_8000_stream.raw
(Press alt-r to start -- read whatever's on the server's panel)
Now this .raw can be served (via the 40iradios.exe only) to an iRadio or
jRadio client (but not directly read from the client like an mp3) by
requesting the .raw like any other .mp3 file (i.e., use *.raw in the
editbox of the client, with NET ON since it has to come from the server).
You can write this .raw out using "dsk" or "DSK" from the client. Be sure
to switch to SEQ mode, or uncheck the .raw file and manually tap the filename
to start. The reason for this is so that it doesn't try to "play/write to wave"
again (it won't overwrite an existing file, but it will sit there in a loop
going over and over if the checkmark remains). It does this VERY FAST so it
all may look like a blur; it'll probably be finished by the time you look up.
So, that's one way to get a wave (result seen below)
01/10/2003 11:46a 9,105,452 20030110_113259a_212.18.198.75_8000_stream.wav
Anyway, instead of doing the dsk/DSK method, you can also extract an mp3
from the .raw file by doing this:
G:\iradio>40iradios -scpb:20030110_113259a_212.18.198.75_8000_stream.raw -scex:1
(press alt-r to start the extraction to mp3 and alt-x when it finishes)
This gets you an mp3 of the .raw contents.
01/10/2003 11:51a 983,040 20030110_115132a_.mp3
Once you get the mp3 you can then write it out as a wav from the client using
dsk|DSK OUT (OPTion/Sets panel).
There is an option to multi-extract, by title, but that tends to have a
lot of overlap (part of the end of one extraction really belongs to the
start of the next), especially with large meta-data streams (32 KB) and
slow bitrates. Ideally, a stream will be fast (256 kbps) and have a low
meta-data period (8192 bytes), which won't have more than 1/4 second
overlap. If you put it into a single wave you can use a wave editor and
fix it up probably more easily and more accurately than by using the
cleancut and finetune axe switches in the recorder (-sccc: and etc.).
Make sense? I think that covers what you asked about. The
direct-to-dsk/DSK from an active stream doesn't work. I'm not sure why
at this time but it just doesn't. Still, with the raw file you can
always go back and either play it directly, extract an mp3 from it,
and/or write a wave from it (all of these are covered above).
-scon:# enable SC [def=1 allow SC; =0 disable SC]
-scss:# store stream [def=0 no SC stream store; =1 store stream]
-scex:# extract mp3s [def=0 no extraction; =1 extract, =2 per title]
-scto:# recv timeout [def=5 seconds; range 2 to 600 seconds]
-scac:# auto-reconnect [def=5 seconds; 0=none; range 1-60; stand-alone]
-sccc:# clean cut [def=0 no clean cut; =1 clean ends between titles]
-scca:# clean cut axe [def=0 no finetune cc-axe; range -32768 to 32768]
-sccu:# clean cut use [def=0 no finetune cc-use; range -32768 to 32768]
-scob:# outbuff size [def is 64 KB; # is in KB, 16 to 131072 by 8]
-scmd:# use meta-data [def=1 use meta-data; =0 to not use it]
-scpb:a replay stream [a=filename of raw stream to playback]
-scurl:a stream source [a=URL to stream; default is to wait for iRadio]
- - - - - - - - - - - - -
To monitor a station use two iRadio servers, one to record (as above) and one to
serve a stream to a client. Use a different port for each server. For example,
use -p:4001 for the first server (recording, in stand-alone mode), and -p:4002 for
the second server (for monitoring, from the client):
G:\iradio>40iradios -p:4001 -scurl:http://212.18.198.75:8000 -scss:1
G:\iradio>40iradios -p:4002
Or -p:4002 for the first and -p:4001 for the second. The client needs to
connect to the non-recording server (so it can monitor), so in the client's
40iRadioN.txt file, the alternate server needs to be available. For example:
mint2k:4001 ;record server
mint2k:4002 ;monitor server
and from the NET panel pick the 4002 entry if the 4001 is busy recording.
Trying to start two iRadio servers with the same port causes a BIND error
and the second server's start fails to get going. Use -p:4002 or some other
free port. Of course, you'll need at least twice the bandwidth now, though
you could monitor on a lower bitrate stream, if the station broadcasts in
more than one bitrate, and record from a higher bitrate stream.
27-Jun-2003
-----------
When NET is ON, a playlist that contains
http://
is not sent to the server by filename, but instead is
read locally. Since these are not files, per se, but
more or less an instruction on where to get a file (the
shoutcast stream) there's no reason to have the iRadio
server have that same playlist. If the playlist is not
found locally (this is possible if you type/change the
filename from the editbox), the playlist's filename is
then sent to the iRadio server to see if it has a copy
available in its PL directory.
APPENDing a shoutcast playlist currently always sends
to the server. Use APPLY.
Still, as before, playlists that contain mp3, ogg, wav
filenames are sent to the server by filename only, not
the contents. When NET is off there's no point in
sending a playlist with http:// in it. When in doubt
as to what's happening, watch the server's console to
see what it's doing. UPDATE: 25-July-2003: if RC in the
NET panel is set to PL then the playlist contents are
sent to the server. See howto_setup_server.txt for this
date.
8-May-2003
----------
For shoutcast streams over broadband, I suggest the following
as a start:
1. In 40iradioS.txt, add
-scob:512 (or 256, or more; default is 128 KB)
2. Load'n'Decode initial load size to 128 KB.
3. Shoutcast CACHE to 64 Ks (or match the LnD's ILS in #2).
To get in shoutcast CACHE mode, NET must be ON, and
an http file must be in the list-view (http://...).
When in this mode an 's' follows the CACHE value,
such as "64 Ks".
For shoutcast streams over narrowband, you can get by with a smaller
output buffer. -scob:128 is pretty good; set the LnD ILS to 64 KB,
and the shoutcast CACHE to "64 Ks". A large CACHE size (like 256 KB)
will cause the initial play to be even more delayed.
If you have gaps in playback increase Ti to 2, or 4 if necessary.
Experiment to find what works best there.
If the play gets out of sync, stop play (closes the current stream)
and press play to take up a new stream. This may happen if the
shoutcast broadcaster disconnects his connections, then reconnects
them. You can also try pausing the client for a few seconds.
------------------------------------------------------------------
If you press STOP yet the server continues to stream (that happens
typically when you're streaming way over your available bandwidth)
send a remote reset by pressing the red circle R on the NET panel.
------------------------------------------------------------------
o Use 40iradios.exe v6.2 or later. Previous versions could disconnect
on less than ideal connections.
o A client STATUS of 10002:OutaRange is a recv timeout. Press STOP to
end the connection, or sit tight. 10001 is similar but a send timeout.
Increase the registry values for (default seconds shown)
torecv 5
tosend 5
torecvsc 5
tosendsc 5
if you don't want to see the OutaRange STATUS as often. Generally
it waits around until you abort the play (STOP), or if it tries
to play data that isn't there. It's possible that play will wrap
around and play already played data. Get more bandwidth.
o The server's OBK value is the bytes available (yet unread by the
client). Its max value is typically the output buffer size (def.
is 128 KB, use -scob:# to increase it), though can be a bit less.
You don't want too much buffered data around because it's possible
the shoutcast server will recognize this as a disconnect and wind
up disconnecting you. If the STATUS shows "outbuf full" for more
than, say, a minute you may get disconnected by the shoutcast server.
o The client CACHE used will be no more than half the server's out
buffer. For example, using -scob:256 limits the client's CACHE
to 128 KB (which can be seen in the MEM panel, under CACHE: 0.13 MB).
Using a smaller CACHE (64 Ks, for example) may improve performance.
o When starting a stream play, buffering takes place for several
seconds, based on the combined shoutcast CACHE size and the LnD
ILS value. The time at 512 combined KB is 12 seconds and down to
3 seconds at under 64 KB. 448 KB is 11 seconds, 352=9, 320=8,
288=7, 256=6, 128=5, 64=4. The more CACHE and LnD ILS the longer
it buffers (the server buffers; the client just waits). A countdown
timer is shown in the STAT/MEM panel, switching to the the server's
reported bandwidth rate (e.g. 250 kbps). Shoutcast servers may
burst the first 256 KB or so as fast as the bandwidth allows, but
thereafter generally serve at the file's average bitrate (such as
160 kbps), or slightly higher (hopefully not lower).
17-Apr-2003
-----------
The LnD Initial load size (OPT panel) should be set to at least
128 KB for best results. Smaller sizes (96, 64, 32 KB) may not
produce results as good. Play won't sound until this initial
load size has been received.
9-Jan-2003
----------
If you get a URL that looks like
http://64.236.34.141:80/stream/1018/~~~stream~~~.mp3
the /~~~stream~~~.mp3 stuff is a browser thing, totally unnecessary
except to wake up the browser. Remove the stuff after the /~~~, for
http://64.236.34.141:80/stream/1018 (remove the trailing slash)
On-demand play is supported by 40iRadioS.exe but this is not that case.
More notes:
You should set the LnD "Initial load" (see OPT panel) to at least 64 KB.
32 KB may not work well. The default is 128 KB. For higher bitrate streams
you may also consider increasing the server output buffer size, -scob:#.
The default is 64 KB. I use 128 KB (-scob:128). A larger output buffer
means a longer delay before the first sound is heard. A server status of
"OUTBUF FULL" is good; "WAITING FOR DATA" is not (it means your bandwidth is
too low for the stream).
If -scob:# is the default 64 KB then LnD should also be no more than 64,
at least on slow connections. With -scob:128, the LnD initial load size
can be 128 KB. With -scob:64 and the LnD initial at 128 KB you may
experience an unwanted pause at refills.
12-Dec-2002
-----------
Be sure the NET (in the [NET] panel) is set to ON before trying to
do a shoutcast stream.
15-Nov-2002
-----------
How to shoutcast
---------------------
1. Unpack the trial package into a temporary directory, say t_iradio/
D:\>unzip iradio_x86.zip -dt_iradio
---------------------
2. Check the switches
D:\t_iradio>40iradios -? (-help can also be used)
40iRadio Server v6.1.24.41 Copyright (C)2003 Cornel Huth 40th.com
-?<---what's that supposed to do? Use:
-p:# port [default is 4001]
-hn:a srvr hostname [default is current hostname]
-ip:a.b.c.d server IP# [default is first found of hostname]
-af:a.b.c.d client IP# [accept/reset from only this client|subnet]
-ka:# alive checks [optional max allowed alive check failures]
-w: width [default is 80 cols, min=64 max=148]
-h: height [default is 43 rows, min=8]
-nr no recurse [default is to recurse dirs searched]
-yr yes recurse [to override any -nr in spec file]
-pr:# priority class [0=normal, 2=high; def=2]
-spec:a spec file [default is 40iRadioS.txt in server directory]
-exe:a winamp path [sets RC winamp program location]
filemask file mask [def=from spec file; if mask end in .mp3]
-chunk:# send chunk KB [def=128 KB (recommended size is 128)
-uncmap:# fast local UNC [def=0 full UNC, =1 fast local UNC]
-slow:# slow cmd net [def=0 fast cmd check; min=2, max=5 times]
-oggx:# ogg load mode [def=0 implicit scan for .ogg; 1=explicit only]
-findany:# find any file [def=0 find known types only; 1=find any]
-tos:# send timeout [def=5 seconds; range 1 to 600 seconds]
-rstp:# reset on port [default is 4000]
-scon:# enable SC [def=1 allow SC; =0 disable SC]
-scss:# store stream [def=0 no SC stream store; =1 store stream]
-scex:# extract mp3s [def=0 no extraction; =1 extract, =2 per title]
-scto:# recv timeout [def=5 seconds; range 2 to 600 seconds]
-sctc:# connect timeout[def=10 seconds; range 2 to 600 seconds]
-scac:# auto-reconnect [def=5 seconds; 0=none; range 1-60; stand-alone]
-sccc:# clean cut [def=0 no clean cut; =1 clean ends between titles]
-scca:# clean cut axe [def=0 no finetune cc-axe; range -32768 to 32768]
-sccu:# clean cut use [def=0 no finetune cc-use; range -32768 to 32768]
-scob:# outbuff size [def is 256 KB; # is in KB, 64 to 16384 by 8]
-scwx:# wait times [def is 6 WAIT FOR DATAs; range 3-10, ea 6 secs]
-scmd:# use meta-data [def=1 use meta-data; =0 to not use it]
-scpb:a replay stream [a=filename of raw stream to playback]
-scurl:a stream source [a=URL to stream; default is to wait for iRadio]
Examples:
C:\>40iRadioS -nr ;cmd line switches override spec file
C:\>40iRadioS -spec:myspecs.txt ;use this spec file instead of 40iRadioS.txt
C:\>40iRadioS -hn:mintlnx -findany:1
C:\>40iRadioS -ip:192.168.1.99 -p:4002 -rstp:4099 -w:64 -h:16
C:\>40iRadioS "e:/mp3/oldies/*.mp3" ;only bother with matching oldies files
C:\>40iRadioS -exe:d:/winamp/winamp.exe
C:\>40iRadioS -oggx:1 ;find .ogg files only if .ext is .ogg
C:\>40iRadioS -scpb:stream.raw -scex:1 ;stand-alone stream playback & extract
----------------------
3. Edit 40iradioS.txt:
Change the line (near the bottom) from
e:\mp3\*.mp3
to where ever you have most of your mp3 files. This is the 40iradios.exe
spec file (also known as its configuration file). Any switches in this file
can still be overriden using command line switches.
If for some reason 40iradioS.exe doesn't start correctly, you may need
to use the -ip: switch to supply the actual interface your NIC is at.
ipconfig.exe can be run to find that out. Win9x may use something else.
Look for the IP# of your ethernet card.
Add any other switches you know of.
----------------------
4. Edit 40iradioN.txt:
Change the lines
mint2k:4001
sage:4001
to whatever your hostname that 40iradios.exe is about to be run on. You
can also use the IP#, as supplied in 40iradioS.txt. Be sure to include
the colon and port number after the host. 4001 is the default for the
40iradioS.exe server.
----------------------
At this point you can start 40iradioS.exe server and access it from
the 40iRadio.exe client. Shoutcast, too, even. Start it
D:\t_iradio>40iradios.exe (no switches for now)
and something like this appears:
SERVER IP PORT iRADIO
SAGE 192.168.1.2 4001 0.0.0.0
FILES MB SERVED MB STATUS
0 0.00 0 0.00 waiting
______________________________________________________________
% MB
use alt-x to exit iRadio Server
current dir: D:\t_iradio\
server path: D:\t_iradio\
defSpecFile: D:\t_iradio\40iRadioS.txt
slow cmd multiplier: 4 x 200ms
----------------------
Start the client:
D:\t_iradio>40iradio86a.exe (the Win32 desktop client)
A. Tap NET
B. Select the server if the one you want (assuming you set more than one in
40iradioN.txt) is not already listed
Server [mint2k:4001 ]
C. Tap OFF under NET (it changes to ON, and the server comes to life)
If it says, 10061:no server
make sure the Server [... ] hostname:port is correct. You can verify
it by looking at the console of the server: IP and port are listed.
If STILL not, then see if a reboot will fix up your IP numbers (who knows
what evil lurks in the ...)
D. The console on the server may look something like this
SERVER IP PORT iRADIO
SAGE 192.168.1.2 4001 192.168.1.2
FILES MB SERVED MB STATUS
2 10.47 0 0.00 READY
____________________________________________________________
% MB
filespec(s): e:/mp3/*.mp3
Connect: iRadio v2.30.43.215 mp3 wav ogg raw http
use alt-x to exit iRadio Server
current dir: D:\t_iradio\
server path: D:\t_iradio\
defSpecFile: D:\t_iradio\40iRadioS.txt
slow cmd multiplier: 4 x 200ms
Yes, there are indeed only two files in this filespec: within the
40iplayS.txt file I have the filespec, e:/mp3/*.mp3, and that's
why that filespec is shown above. I can replace that at any time
by sending a new spec from the iRadio client ([FS] editbox/APPLY),
such as e:\mp3\new\*.mp3, or where ever, whatever, I want to list.
Anyway, if that made any sense (it will eventually)... the client
shows these two files in its ListView. The MB column of the ListView
shows the filesize and location (5.2 MBn) where n stands for network.
Easy stuff.
------ SHOUTCAST stuff --------------------------------------
How about shoutcast? For a quickshot, press [FS] on the iRadio
client. In the file mask editbox enter
http://62.95.108.10:8010
and hit ENTER or press APPLY. The [FS] panel closes and you're
back at this ListView, with the above URL in the ListView, and
checked. To start streaming just press the play button. The
server console looks something like this:
SERVER IP PORT iRADIO
SAGE 192.168.1.2 4001 192.168.1.2
STREAM MB TITLES MB STATUS
0 0.00 0 0.00 READY
________________________________________________________________
% MB
Stream:connection closed
Connect failed: timed out (see -scto:#) (rc=10060)
Out buffer size: 128 KB
Connecting to: <http://62.95.108.10:8010>
using URL: http://62.95.108.10:8010
Connect: iRadio v2.30.43.215 mp3 wav ogg raw http
dir filespec(s): e:/mp3/*.mp3
...
slow cmd multiplier: 4 x 200ms
Whoops! Timed-out. This particular station is off the air.
Actually, I have no idea, but why try and figure it out with
serveral 100 stations out there. So, try another. If you
have a playlist with stations in it, the next station in the
list would automatically be tuned in. If you were in stand-
alone server mode, the same station would be retried, and
a new .raw save file would be started, if any. Since this
how-to isn't using a playlist, or stand-alone server mode, just
copy this URL below to the clipboard and paste it into the [FS]
editbox of the iRadio client, as you did above, and then press
ENTER or tap APPLY:
http://205.188.234.67:8000
And, while I'm sure you don't want to hear Jefferson Starship
doing "Built This City..." again, as you can see it comes in,
albeit at 56 kbps bitrate.
SERVER IP PORT iRADIO
SAGE 192.168.1.2 4001 192.168.1.2
STREAM MB TITLES MB STATUS
1 0.16 1 0.12 59 kbps 64
______________________________________________________________________________
% MB
0.1 no_title
[icy-br:56]
[icy-metaint:24576]
[icy-pub:1]
[Content-Type:audio/mpeg]
[icy-url:http://www.wolffm.com]
[icy-genre:pop rock 80s]
[icy-name:WOLF FM - The hottest mix of the 70s, 80s and today!]
[icy-notice2:SHOUTcast Distributed Network Audio Server/SolarisSparc v1.9.2]
[This stream requires <a href="http://40th.com/">40iRadio</a>]
[icy-notice1:]
[ICY 200 OK]
Connecting to: <http://205.188.234.67:8000>
using URL: http://205.188.234.67:8000
Connect: iRadio v2.30.43.215 mp3 wav ogg raw http
...
Some stations don't send out titles, even though they do the metadata
thing. If you save this to a .raw file you can later only extract it
as one big mp3 (or just replay it as a stream). If a station does
send titles you can extract as individual files, or as a single .mp3.
Above, in the console STATUS, the first value is the moving average
kbps, going back a few seconds, and the second value is the rate
of the most recently received block. The iRadio client shows the first
value in its STAT/MEM panel, to the right of the time bar, so you can
be in the South Lawn and still still how the server connection is going.
That's right, the client doesn't do any shoutcast work at all; as far
as it cares, it's just streaming from the server. All the shoutcast
work is done on the server machine -- much more efficient.
And it can do a few more things. Generally, the other server(s) (40iSrv) would typically be used instead of this (40iConS), but this is used for shoutcast recording/serving.
40th floor: sorry for my stupidity...but where can i get this program and step-by-step instructions cuz ur was confusing to me. and is this a free program? i prefer something free...thanx.
40th Floor is the developer of that application. He's regularly posted updates on his apparently multi-talented software on Brighthand, and most of those postings have been about as overwhelming/confusing as the above. My mind reels whenever I try to read that stuff. Far from intuitive, unless one is a major techie, and no, not free. Still, probably great software! I just don't have a clue how to begin using it.
For recording web streams there are a lot of free options on a PC, not so on a PPC. I like ASFRecorder on the PC for ASX/ASF/WMA stream recordings. Just paste in the address of a stream and start recording to a file on the desktop, in realtime. Works great with the current BBC releases of the new Hitchhiker's Guide series, for one example. The resulting files can be re-encoded using WMEncoder 7.1 or some other version, also free, to reduce file size/quality and save as a WMA or ASF file (the latter in WMEncoder 9), both playable in the PPC using WMP.
On the PPC, I have recorded RealOne RM streams using NoteM. It's possible, if not very pretty, to do this simply by playing around with speaker volume and microphone gain (the latter available in iPAQ and Dell devices, possibly others, in Settings | System) until I arrive at a reasonably listenable recording. Usually the Low bitrate (16kbps mono) is sufficient for this, and as such the MP3 files are very small even for long streams. Sometimes if I've wanted higher quality I've used a splitter plugged into the microphone jack on my iPAQ 3835, a part I had added by PocketPCTechs. I plug a mini-jack line into the headphone jack, the other end into one jack of the splitter. I plug a headset into the other jack of the splitter to enable monitoring the stream, so I know when it's done so as to stop NoteM. Since NoteM is mapped to a hardware button, in my case I use the iTask button on the iPAQ, it's easy to jump from RealOne Player (or from WMP or from GSPlayer for that matter, both of which are fine for different sorts of audio streams) back to NoteM to shut off recording, provided I don't map that same button to any function in any of the other players. Keeping that button assigned just in NoteM keeps things clean and simple, making it easy to have just second or two of trailing silence on recordings done this way.
On a PC for MP3 or M3U streams or some other types you may also use AudioGrabber, which is now completely free (he stopped charging for the full version this year!) and very easy to configure and use. No command line nonsense for all us amateurs. :)
Last edited by Gerard Samija; 10-19-04 at 06:39 PM.
I'm having trouble trying to put Note M on my PPC. I have WM2003, and as far as downloading goes, I'm at the beginner level.
This program looks appealing from reading your discussions. I'm looking for a better recorder for recording class lectures for myself and my daughter is a journalism major in college and looking to record conversations that she can play back slowly to type up quotes for news articles. Today she was asking me for an old fashioned large cassette recorder and a dictaphone machine for Christmas. Surely there's a better way these days? I don't think the mic system in the X5 would be enough to do the trick. Any thoughts?
The simplest way to install NoteM is using a CAB file, as supplied for both PPC2002 and WM2003 in the ZIP file on my webspace. Just unpack the ZIP, using anything you like (WinZip, PKZip, WinRAR, TotalCommander... lots of stuff available for PC, or Resco, PocketRAR, TotalCommanderCE or others on the PPC), place the relevant version of the CAB file in your device anywhere, and tap it. That's all. It will install, make a shortcut, and work. Then map it to a hardware button if you like using the Settings | Buttons applet, and set up recording functions to button mappings in the program itself.
NoteM must be installed to the default main memory location. It installs a database element, and as such a non-default installation can cause bad errors on soft resets.
As for the built-in X5 mic, I've found it really very good, if used carefully. I modify the microphone gain according to the recording situation, with more gain per a quieter, more distant source, and less for louder and closer sources. More noise comes with more gain, so that's a compromise you have to decide. Another important factor is the screen buzz with the X5 model. I don't know if other Dell models do this, but the X5 buzzes loudly at all backlight levels. However, turning the backlight off completely eliminates this problem in recordings. Either use the button-combination to toggle the backlight off, or press-and-hold the power button to shut it off, whichever you prefer. Then use NoteM without a screen light. This is often preferable anyway, for better battery life and for making less of a spectacle of your activity.
Great software and I'd recommend it to any true audiophile but could you please just link to your pages when you want to share that much info. This thread is one of the few I've had to scroll right in and it was all just wide black bars doubling the width of the page between your major points. It probably looks cool in a PC's browser but it's a pain in PIE
Don't Panic!
Bobby
__________________
Don't Panic!
Bobby
42 Soft-reset is our Friend To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.