MP3 ripper/encoder for Sparc/Solaris ?
k77...@my-deja.com
Does anyone have a pointer to an MP3
ripper/encoder software specifically
for Sparc/Solaris
thanks,
Kevin Nolan
Sent via Deja.com http://www.deja.com/
Before you buy.
Adam Stein
k77...@my-deja.com writes:
> Hi,
>
> Does anyone have a pointer to an MP3
> ripper/encoder software specifically
> for Sparc/Solaris
Have a look at:
http://www.csh.rit.edu/~adam/bookmarks/Software/Audio/MPEG_3/
for links I have.
--
Adam Stein @ Xerox Corporation Email: ad...@scan.mc.xerox.com
Disclaimer: Any/All views expressed
here have been proved to be my own. [http://www.csh.rit.edu/~adam/]
Joerg Schilling
Adam Stein <ad...@scan.mc.xerox.com> wrote:
>In article <8eg58t$32s$1...@nnrp1.deja.com>,
> k77...@my-deja.com writes:
>> Hi,
>>
>> Does anyone have a pointer to an MP3
>> ripper/encoder software specifically
>> for Sparc/Solaris
>
>Have a look at:
>
> http://www.csh.rit.edu/~adam/bookmarks/Software/Audio/MPEG_3/
It does not list any usefull ripper, it only lists encoders.
The best available ripper for Solaris is cdda2wav (part of the
cdrtools package).
ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schi...@fokus.gmd.de (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
enkidu
> k77...@my-deja.com writes:
> > Hi,
> >
> > Does anyone have a pointer to an MP3
> > ripper/encoder software specifically
> > for Sparc/Solaris
Here's an encoder I like : http://bladeenc.mp3.no
get the sources (v 0.92) and compile.
Jörg schilling already pointed to cdda2wav ...
Adam Stein
j...@cs.tu-berlin.de (Joerg Schilling) writes:
> In article <8ekdih$4a5$1...@news.wrc.xerox.com>,
> Adam Stein <ad...@scan.mc.xerox.com> wrote:
>> k77...@my-deja.com writes:
>>> Hi,
>>>
>>> Does anyone have a pointer to an MP3
>>> ripper/encoder software specifically
>>> for Sparc/Solaris
>>
>>
>> http://www.csh.rit.edu/~adam/bookmarks/Software/Audio/MPEG_3/
>
> It does not list any usefull ripper, it only lists encoders.
You are right, I forgot to list rippers:
http://www.csh.rit.edu/~adam/bookmarks/Software/Devices/CDROM/Rippers/
Joerg Schilling
enkidu <enkidu.R...@NOSPAMACCEPTED.excite.com> wrote:
>> In article <8eg58t$32s$1...@nnrp1.deja.com>,
>> k77...@my-deja.com writes:
>> > Hi,
>> >
>> > Does anyone have a pointer to an MP3
>> > ripper/encoder software specifically
>> > for Sparc/Solaris
>
>get the sources (v 0.92) and compile.
>
>Jörg schilling already pointed to cdda2wav ...
The next version of cdda2wav will include mp3 support.
Joerg Schilling
Adam Stein <ad...@scan.mc.xerox.com> wrote:
>In article <8eg58t$32s$1...@nnrp1.deja.com>,
> k77...@my-deja.com writes:
>> Hi,
>>
>> Does anyone have a pointer to an MP3
>> ripper/encoder software specifically
>> for Sparc/Solaris
>
This link leads to:
1) CDparanoia -> Nonportable (runs only on Linux)
2) Galette -> Uses ioctl's to extract audio
and for this reason will most
likely not support all drives.
I can only recommend to use cdda2wav (from the cdrecord packet).
Jeff D. Roesner
cdda2wav works great but since my last hardware and OS upgrade it's not
working so well. I changed my SCSI adapter from an Adaptec 2940UW to a
2940U2W and my OS from Solaris 8 EA (Intel) to Solaris 8 FCS.
I installed the scg driver (the 2.6 beta version) and it appears to attach
okay, as there is a /dev/scg0 listed and pointing to a place in the /devices
directory tree. I feel that scg is working properly. The only two devices
I have on my SCSI controller are my Toshiba CD-ROM on the Ultra segment and
the hard drive on the Ultra2 segment.
When I try to run cdda2wav I get:
this is neither a scsi cdrom nor a worm device
When I run cdrecord -scanbus it produces
# cdrecord -scanbus
Cdrecord 1.8.1 (i386-pc-solaris2.8) Copyright (C) 1995-2000 J÷rg Schilling
Using libscg version 'schily-0.1'
scsibus0:
0,0,0 0) 'IBM ' 'DNES-309170W ' 'SA30' Disk
0,1,0 1) '' '' '' NON CCS Disk
0,2,0 2) '' '' '' NON CCS Disk
0,3,0 3) '' '' '' NON CCS Disk
0,4,0 4) '' '' '' NON CCS Disk
0,5,0 5) '' '' '' NON CCS Disk
0,6,0 6) 'IBM ' 'DNES-309170W ' 'SA30' Disk
0,7,0 7) HOST ADAPTOR
For some reason it's seeing the hard drive in two places and no CD-ROM.
I'm out of ideas as to what to do about this.
Joerg Schilling
Jeff D. Roesner <je...@warsawcoil.com> wrote:
>> I can only recommend to use cdda2wav (from the cdrecord packet).
>
>cdda2wav works great but since my last hardware and OS upgrade it's not
>working so well. I changed my SCSI adapter from an Adaptec 2940UW to a
>2940U2W and my OS from Solaris 8 EA (Intel) to Solaris 8 FCS.
>
>I installed the scg driver (the 2.6 beta version) and it appears to attach
>okay, as there is a /dev/scg0 listed and pointing to a place in the /devices
>directory tree. I feel that scg is working properly. The only two devices
>I have on my SCSI controller are my Toshiba CD-ROM on the Ultra segment and
>the hard drive on the Ultra2 segment.
>
>When I try to run cdda2wav I get:
>
>this is neither a scsi cdrom nor a worm device
>
>When I run cdrecord -scanbus it produces
>
># cdrecord -scanbus
>Cdrecord 1.8.1 (i386-pc-solaris2.8) Copyright (C) 1995-2000 J÷rg Schilling
>Using libscg version 'schily-0.1'
>scsibus0:
> 0,0,0 0) 'IBM ' 'DNES-309170W ' 'SA30' Disk
> 0,1,0 1) '' '' '' NON CCS Disk
> 0,2,0 2) '' '' '' NON CCS Disk
> 0,3,0 3) '' '' '' NON CCS Disk
> 0,4,0 4) '' '' '' NON CCS Disk
> 0,5,0 5) '' '' '' NON CCS Disk
> 0,6,0 6) 'IBM ' 'DNES-309170W ' 'SA30' Disk
The problem is that Sun is not using their own official internal data
structures anymore in the SCSI driver subsystem for newer Adaptec hardware.
I am now no more able to access other targets than the target that the
device unit registered to. I would be forced to rewrite the scg driver.
There are two workarounds:
1) Use Symbuios Hardware
2) Edit /kernel/drv/scg.conf to point to the CD-writer
Jeff D. Roesner
> structures anymore in the SCSI driver subsystem for newer Adaptec
hardware.
>
> I am now no more able to access other targets than the target that the
> device unit registered to. I would be forced to rewrite the scg driver.
>
> There are two workarounds:
>
> 1) Use Symbuios Hardware
>
> 2) Edit /kernel/drv/scg.conf to point to the CD-writer
I changed the scg.conf to point to target 6 and when I run cdda2wav I get:
2 aurora /home/jroesner % cdda2wav
cdda2wav: No such file or directory. Cannot open SCSI driver.
open(0,6,0) in file interface.c, line 491
On SunOS/Solaris make sure you have Joerg Schillings scg SCSI driver
installed.
Probably you did not define your SCSI device.
You can scan the SCSI bus(es) with 'cdrecord -scanbus'.
Set the CDDA_DEVICE environment variable or use the -D option.
You can also define the default device in the Makefile.
Doing a cdrecord -scanbus yields:
# cdrecord -scanbus
Cdrecord 1.8.1 (i386-pc-solaris2.8) Copyright (C) 1995-2000 Jörg Schilling
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are
root.
I don't think I can get a Symbios card as I was already in hot water with my
fiancee for getting the new Adaptec card. I'm sure asking you to rewrite
scg would be a bit much, but I have a feeling that I won't be the only one
asking.
Thanks for the help on this, it's good to know it's not my fault it doesn't
work.
Joerg Schilling
You need to reboot after this change. If you have luck, it is OK to
modunload the scg driver.....
Bruce Adler
"Joerg Schilling" <j...@cs.tu-berlin.de> wrote in message news:8eru2s$6ht$1...@news.cs.tu-berlin.de...
>>In article <8eroi8$107i$1...@nix2.kconline.com>,> ...
>> cdda2wav works great but since my last hardware and OS upgrade it's not
>> working so well. I changed my SCSI adapter from an Adaptec 2940UW to a
>> 2940U2W and my OS from Solaris 8 EA (Intel) to Solaris 8 FCS
> ...
> The problem is that Sun is not using their own official internal data
> structures anymore in the SCSI driver subsystem for newer Adaptec hardware.
I wrote those IA HBA drivers and I assure you that there are no such
"official internal data structures". When I wrote those IA HBA drivers
I had information about every internal data structure, all the kernel
sources, access to every relevant internal Sun document, and access to
every SCSI expert within Sun, so I think I would have know about any
such "official" data structures or interfaces.
The *only* relevant or official data structures and documents, for writing
any HBA driver for *any* SunOS 5.x release, are all "PUBLIC" and are all
at the level of at least "STABLE". There are some "deprecated" official
interfaces but as far as I know no official SunOS 5.x HBA interface has
ever been removed so the current DDI docs and the WDD contain everything
that's relevant (of course now that I've said that some code lawyer
will point out some obscure useless interface that I've forgetten about
that got deleted from the Solaris DDI six years ago).
Any internal, non-public, unofficial 15-year-old notes or documents that
someone within Sun wrote based on the old SunOs 4.x driver interfaces and
data structures (but never got officially approved by Sun's PSARC committee,
and therefore should never have released to anyone), are irrelevant. The
fact that some of the older HBA drivers are able to tolerate an obsolete
undocumented target driver bus scanning hack from the non-public SunOS 4.x
interfaces is also irrelevant. The fact that some particular version of a
Symbios driver might still tolerate that hack *today* is also irrelevant
and futhermore there's absolutely no guarantee that the very next version
of the same driver will continue to tolerate such a hack.
The fact that you wrote a target driver (based on some unofficial,
nonpublic interfaces) which doesn't work with some of the newer IA HBA
drivers is unfortunate (you have my sympathies) but it's not due to any
problem in the HBA drivers. It's just not reasonable to expect that some
undocumented hack that worked fifteen years ago will be guaranteed to
work on every future release (especially when such an interface would
pretty much force the HBA driver writer to either implement a memory
leak or always statically allocate all data structures for all possible
target driver instances).
> I am now no more able to access other targets than the target that the
> device unit registered to. I would be forced to rewrite the scg driver.
I believe there are trivial ways to implement your scg driver and
library to perform the "scanbus" function without relying on unofficial
obsolete hacks and without forcing any HBA driver to support any
undocumented interfaces. You basically have to move some of the logic
out of the scg target driver into your scg library (which coincidentally
greatly simplifies the code).