Jump to content

fgoodman

  • Posts

    16
  • Joined

  • Last visited

  • Country

    country-ZZ

Retained

  • Member Title
    Newbie
  1. To set this up, I suppose one needs a "spare" display and keyboard, and afterwards one can run it by screen sharing?
  2. Can someone explain how to use the menu item "Check file with AccurateRip" in XLD? The existence of the menu item suggests that it should be possible to check previously ripped files against the AR database, but I have not found any circumstance under which the menu item is actually active. Thanks for your help. Note: the author of XLD explained this to me, as follows: "You should open .cue with a single image file to activate the item."
  3. aiff is uncompressed, flac is compressed. Both should work fine. flac is lossless compressed, so has absolutely the equivalent information as aiff. Since flac is compressed, it has the advantage of requiring less storage space and allowing faster communication from computer to transporter. The latter is an issue for some people using wireless communication, who find that their wireless can't keep up, so the music pauses or stutters. It is certainly important to get the ripping done properly to begin with. You can find discussions about this, and software recommendations, on this forum and elsewhere. You could try re-ripping a few albums using the current best ripping software, to aiff or flac, and compare the sound with your old rips. You can also freely convert back and forth between aiff and flac without introducing errors or loss of information and test your preference for the audio format.
  4. I downloaded the program from http://puddletag.sourceforge.net/. The version number is 0.9.2. It wouldn't be a bad idea to display the version number somewhere in the program. By the way, the first time(s) I started the program, it took a very long time to come to life. I thought that would be an impediment to using the program. But now it comes up immediately. Thanks for the hard work you have put into this program.
  5. Sorry, I don't know what I did exactly to crash the program. I was fooling around, as one does with a new program whose mode of operation one doesn't already understand. When I read error messages in the terminal window saying explicitly that puddletag doesn't support unicode, I interpreted them as meaning that puddletag doesn't support unicode. I only discovered afterwards by more fooling around that puddletag does support unicode. It's a nice program, and certain to get even better. I tried out the latest puddletag. I think LANG is already set to en_US.UTF-8 in OS X by default. I think it is can be tricky to support unicode across different OS's, so it is a credit to you that this works.
  6. I think I was wrong about unicode. I managed to crash the program, and I saw some error message about not supporting unicode. But in fact, I was able to open files with unicode tags, and they displayed correctly. This looks like a nice program, but in an early stage of development.
  7. Puddletag doesn't support unicode! That's a deal breaker for now, as my music titles are full of umlauts and accents. Anyway thanks again to wgscott for the instructions posted here, and for personal help with the installation, and I look forward to a future umlaut capable version.
  8. I re-installed QT4 (4.6.2) from the site pointed to in your instructions rather than 4.6.3 from the nokia site; re-installed pyqt4 from a fresh download; re-installed puddletag. Now it runs! Puddletag hangs forever on startup, but finally comes to life. (Maybe it's scanning the file system, since it seems to comes up with a complete file tree of the startup drive.) What I learned: use the version of QT4 pointed to in the instructions here. Moreover, I think one has to use the cocoa version rather than the carbon version.
  9. I found the file with the wrong architecture: [imac:QtGui.framework/Versions/4] fgoodman% file * Headers: directory QtGui: Mach-O universal binary with 2 architectures QtGui (for architecture i386): Mach-O dynamically linked shared library i386 QtGui (for architecture ppc): Mach-O dynamically linked shared library ppc Resources: directory I guess this came from the QT4 installation. I used 4.6.3 from the nokia QT site.
  10. The mystery remains. I got the same results as you on architectures, and the same error message as before: [imac:~] fgoodman% cd /Library/Python/2.6/site-packages [imac:Python/2.6/site-packages] fgoodman% file *.so sip.so: Mach-O 64-bit bundle x86_64 [imac:Python/2.6/site-packages] fgoodman% cd Py* [imac:2.6/site-packages/PyQt4] fgoodman% file *.so Qt.so: Mach-O 64-bit bundle x86_64 QtAssistant.so: Mach-O 64-bit bundle x86_64 QtCore.so: Mach-O 64-bit bundle x86_64 QtDesigner.so: Mach-O 64-bit bundle x86_64 QtGui.so: Mach-O 64-bit bundle x86_64 QtHelp.so: Mach-O 64-bit bundle x86_64 QtMultimedia.so: Mach-O 64-bit bundle x86_64 QtNetwork.so: Mach-O 64-bit bundle x86_64 QtOpenGL.so: Mach-O 64-bit bundle x86_64 QtScript.so: Mach-O 64-bit bundle x86_64 QtScriptTools.so: Mach-O 64-bit bundle x86_64 QtSql.so: Mach-O 64-bit bundle x86_64 QtSvg.so: Mach-O 64-bit bundle x86_64 QtTest.so: Mach-O 64-bit bundle x86_64 QtWebKit.so: Mach-O 64-bit bundle x86_64 QtXml.so: Mach-O 64-bit bundle x86_64 QtXmlPatterns.so: Mach-O 64-bit bundle x86_64 phonon.so: Mach-O 64-bit bundle x86_64 [imac:2.6/site-packages/PyQt4] fgoodman% file /usr/bin/python /usr/bin/python: Mach-O universal binary with 3 architectures /usr/bin/python (for architecture x86_64): Mach-O 64-bit executable x86_64 /usr/bin/python (for architecture i386): Mach-O executable i386 /usr/bin/python (for architecture ppc7400): Mach-O executable ppc [imac:2.6/site-packages/PyQt4] fgoodman% fink remove python Password: Information about 3640 packages read in 3 seconds. WARNING: python is not installed, skipping. Nothing removed [imac:2.6/site-packages/PyQt4] fgoodman% puddletag Traceback (most recent call last): File "/usr/local/bin/puddletag", line 55, in from PyQt4.QtGui import QApplication, QFont, QPixmap, QSplashScreen, QIcon ImportError: /Library/Frameworks/QtGui.framework/Versions/4/QtGui: no appropriate 64-bit architecture (see "man python" for running in 32-bit mode) [imac:2.6/site-packages/PyQt4] fgoodman%
  11. I reinstalled some things and now I get a more promising error message: Traceback (most recent call last): File "/usr/local/bin/puddletag", line 55, in from PyQt4.QtGui import QApplication, QFont, QPixmap, QSplashScreen, QIcon ImportError: /Library/Frameworks/QtGui.framework/Versions/4/QtGui: no appropriate 64-bit architecture (see "man python" for running in 32-bit mode) So the problem is 32 bit versus 64 bit execution. I tried forcing 32 bit execution, but then got a different complaint about wrong architecture. I have sip vs. 4.10.3 QT4 vs. 4.6.3 pyqt 4.7.4 I am using os x 10.6.6
  12. You are welcome. It's best to stay with flac. Transporter handles flac natively.
  13. I have all that stuff, and I tried invoking puddletag as you suggested, with the same result. For good measure, I also copied all that stuff into /System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python2.6/site-packages Thanks for your help!
  14. Thanks, good idea. But that's not it. No relevant stuff is in /System/Library... (or in /sw/lib/python2.6) and it seems all the installed stuff landed in /Library/Python/2.6/site-packages. Maybe I somehow grabbed the wrong version of something.
  15. Install Squeezebox Server on the new mac. Put all your flac files under one directory (the Squeezebox music folder). Set this on the basic settings page of Squeezebox Server. Scan with Squeezebox server. Continue to use Squeezebox server as before the move to mac. Other details: give your mac a fixed IP address. If you have a wired connection mac to router, this is done under apple menu --> system preferences --> network --> ethernet Also in the same place, choose advanced and then ethernet again, and then set your ethernet parameters to manual, 100base TX or 1000baseT, full duplex. Unfortunately, you have to do this each time you reboot; the machine defaults to choosing ethernet parameters automatically. This is a detail you won't see anywhere, but it solved a communication glitch for me between mac and transporter. Another detail: the squeezebox developers pretty much expect the music files to be on a disc formatted to a native format of the machine begin used. I.E. if your files are on a Windows formatted usb drive, mac will be perfectly happy with that, I think, but Squeezebox Server may not be. The unhappiness of Squeezebox server may be expressed by misreading unicode file names and tags.
×
×
  • Create New...