Topics

Hi--

I got a new GC100 the other day, with firmware version 3.0.  I plugged the unit in, verified that it got an IP via DHCP, but when I reset it to factory defaults and press "Add GC100," I get a failure message.  Something must have changed in the new firmware version.  My prime suspect is that the default is now to enable DHCP.  This is the mode it reverts to when it's factory reset (I'm guessing, as that is how it's shipped from the factory).  Does anyone know how the detection script works?

Zaerc?

Thanks,
-Pete

Hey guys--

I noticed that the CD ripping script, ripDiskWrapper.sh, is not using the quality settings set in the web admin when ripping CDs.  These settings affect MP3 and OGG encoding quality.  Currently, the arguments to the encoders are hard-coded in the script.  While the encoding type is passed in as an argument to the script, the quality subsettings are not.

I just wanted to point this out so someone doesn't rip an entire collection at a quality level that they didn't want.

I've filed a mantis report here:
http://mantis.linuxmce.org/view.php?id=3637

In the meantime, the way to correct it on your system is to modify ripDiskWrapper.sh to hard-code your desired bitrate/Bitrate arguments for lame and ogg

For mp3s: modify the following line in ripDiskWrapper.sh

            OutputFile='>(lame -h --tt "$FileName" --ta "$DARTIST" --tl "$DALBUM" --tn "$TrackNumber" --ty "$CDYEAR" --tg "$CDGENRE" - "$Dir/$FileName.'"$FinalExt"'.in-progress")' # encoder


You'll want to change the line that begins with "OutputFile='>(lame "
and add your quality settings there.  For example, add "-b bitrate"  where bitrate is your desired bitrate.  You could also add "-V"  for VBR encoding.

Similarly, modify the following line for .ogg encoding

            OutputFile='>(oggenc -Q --artist "$DARTIST" --album "$DALBUM" --date "$CDYEAR" --genre "$CDGENRE" --tracknum "$TrackNumber" -o "$Dir/$FileName.'"$FinalExt"'.in-progress" -)' # encoder

You'll want to change the line that begins with "OutputFile='>(oggenc"
and add your quality settings there.  For example, add "-q quality"  where quality is your desired quality level, -1 to 10.

Note that until the fix is added to LMCE, you'll have to check this script after updates (or lock the script file).

I haven't verified my arguments to the encoders, so you may want to verify that those are correct on a disk or two before ripping your entire collection.

-Pete

Hi gang--

I've got a fairly stable initial Insteon plug-in developed, and I'd like some way of capturing and versioning my setup.  If I understand correctly, Pluto is using sqlcvs to version the sql db where things like commands, templates, etc. are kept.  For peace of mind, I'd like to capture this working system before I break it with further development.  I'd like to use a local repository until the development setup for the main distribution is established.  My question is: has anyone here used sqlcvs?  The wiki information doesn't quite contain practical instructions for how to use it with pluto/LMCE, and I'd rather not waste a bunch of time figuring it out if someone can explain it to me in a few simple steps.

Thanks for the help.
-Pete

Hi--

I sent this question to the Pluto ZWave developer because it's a Z-wave question, but it might be generic enough that someone else here can answer:

Thank you for your help with this.  I've been moving forward with
creating the Insteon interface.  One issue that I am unclear about is
the mechanism for a lighting device (i.e a #38 Dimmable Switch) to
create, say a Zwave job, when it receives a message from DCERouter.

For example, on the lights page of the control html page, It has 'ON'
'OFF' and '50%'.   If i understand correctly, these send a DCE Message
to the light device.  How does the light device then trigger the
creation of a Zwave Job?

Thank you for your help

I was looking at the fiire.com page today and noticed that they are selling the Intermatic HA22 Z-wave adapter.  I didn't think this was compatible with LMCE.  Is that now the case?  I didn't see any recent changes to the Zwave source, so I don't think so, but maybe they know something I don't

OC Automation (http://www.ocautomation.com) had some in stock as of about a week ago.  I was able to get one from them and they seem to have a a few more in stock.  They show the ZCS000 on their website as well.  This might be the last of them until the replacements come out.  When I talked with ACT(Homepro) last, they were through Beta on their replacement units (ZCU101 and ZCS101), and they were taking wholesale pre-orders, but they didn't have a ship date.  My guess would be mid Q4 of this year.  Again I don't think there are any guarantees that they will work right off the bat.

Hope this helps.

-Pete

http://smart-home-blog.com/archives/656

From the smart-home-blog, an excellent site with some very neat Pluto development/useful feature explanation.  I believe this is applicable to LinuxMCE, but I haven't tried it yet.

Does anyone have a list of the IP phones that LinuxMCE will automatically recognize (by MAC address) and configure?  I know Cisco phones work.  Any others?

thanks,
-Pete

Note-- Cross posted in the developer's forum

Hey everyone--
I was kind of annoyed that when LinuxMCE ripped CDs, it wouldn't embed any information on the title, album, etc in the files themselves, instead using the .id3 files in the directories and the database.  That's great for LinuxMCE, but if I'm going to rip all my CDs, I want to have the information in the files themselves for flexibility.

I was able to get LinuxMCE to embed Artist/Album/Track/Genre/Date information into the music files when ripping a CD.  You can now see the information on the Squeezebox when playing back ripped files from the core.  After digging around inside LinuxMCE, I've modified the shell file that performs the ripping.

So far I've got it working for the Ogg and Flac encoders.  I hope to get it working for WAV and MP3 files shortly.

I'd appreciate it if anyone was interested in trying it out and letting me know how it works for them.  I'm not a scripting expert by any means, so any input would be appreciated.  I don't think this is the ideal solution, as it requires another CDDB lookup in addition to the one perfomed by UpdateMedia, but it works for now while I try to understand exactly the process the Pluto gang put in place for ripping a CD.  I hope to move on to getting Pluto to work with a more modern (6.5.x) version of Slimserver next.

The attached file goes in your /usr/pluto/bin directory.  Please remember to save the existing ripDiskWrapper.sh to a different name first, so you can go back if it gets screwy.

Thanks everyone,
-PeteK

Hi-

I'd like to use LinuxMCE to rip my CDs to flac.  I tried a few, and it looks like LinuxMCE uses the ripDiskWrapper.sh script to manage the ripping and encoding of CD audio. From digging into this file, it looks like it calls cdparanoia and pipes the output directly to the chosen encoder (in my case the flac encoder).  Unfortunately, this method doesn't tag the files with artist, album information, etc. LinuxMCE obviously does access cddb to get the information to generate file names and to load the database. I would like to use that information to tag the  files as well.  This would avoid having to re-rip if I wanted to reload LinuxMCE or use the files elsewhere.

I was wondering if anyone understands and could explain the exact sequence of events in getting CD information.  I was thinking of using a tool like xmcd to get cddb information, but I would like to use the same source of information that is used for populating the database. I'll keep digging until I can understand it, but I'd appreciate any advice.

Thanks!

-Pete

I'm having a problem getting my MD (nforce 2 chipset, Athlon xp 2500+) to recognize CD and DVDs inserted into its DVDRW drive.  If I put the disc into the drive on the core/hybrid, it functions correctly, identifying the disc, pulling down track listings, etc.  However, when I put a CD into the MD, the orbitor displays ("//dev/cdrom/1) in the upper left blue title bar, and a listing of the track files on the cd is presented on the screen ("Unknown Disc 1", "Unknown Disc 2", etc. The MD begins playing the first track of the CD. Track time is displayed in the upper right corner of the screen. Pressing the eject button to remove the cd removes the track files, track time and path display, but instead puts the text ".0x" in the blue title bar box immediately to the left of where the track time was displayed.

If anyone with more experience has an idea of what to start looking for in the logs (I assume dcerouter messages), I'll get cracking on this.

I also would like to thank Paul for getting this fork going.  The Pluto guys have put together a really amazing base to start from.  I hope that with the community support LMCE is building, we can create something even better.