WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Asunder scm Bug Feedback  (Read 1198 times)

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Asunder scm Bug Feedback
« on: March 13, 2012, 06:39:52 AM »
Ripping
Rip to wav
Successfully rips to wav file
Rip to mp3
Fails to create mp3

Load local lame.tcz via AppBrowser

Rip to mp3
Successfully rips to mp3 file

It seems that the scm cannot find/use lame

Edit - Omitted the following

Error on Startup
When starting via the terminal
Code: [Select]
asunder

(asunder:1765): Gtk-WARNING **: Could not find the icon 'drive-removable-media'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
        http://icon-theme.freedesktop.org/releases


Lockup
During every test session, but after differernt periods of use, the app will lock and also present blank areas of the app window, requiring to be xkilled.  No error messages are received.
   
   
« Last Edit: March 13, 2012, 06:58:47 AM by SamK »

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7071
Re: Asunder scm Bug Feedback
« Reply #1 on: March 13, 2012, 04:25:19 PM »
It works here for me creating mp3's, I remember working on this issue this week, perhaps the extension needs updating.  My md5 of my asunder.scm is this:

37aa8b50fb12c0cf6a23ce8e98b121d0  asunder.scm

That hicolor icon warning is very common for gtk2 apps, and all the asunder icons seem to be working.  I have not seen any lockups though.

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Re: Asunder scm Bug Feedback
« Reply #2 on: March 14, 2012, 07:46:25 AM »
It works here for me creating mp3's, I remember working on this issue this week, perhaps the extension needs updating.  My md5 of my asunder.scm is this:

37aa8b50fb12c0cf6a23ce8e98b121d0  asunder.scm

I have not seen any lockups though.
Your and my md5s match.


Locking
The reported of locking was incorrect.  It turns out that Asunder was running extremely slowly, taking minutes to complete simple tasks such as ticking/unticking a CD track or opening the preferences menu.  This was eventually monitored using top.  While Asunder was slow running the CPU cycles were consistently below 5% and RAM consistenly had in excess of 800MB available.  It is only Asunder that runs slowly.  Other apps can be used as usual without any reduction in response time during an Asunder go-slow.


Ripping
Although it is not practical to use the scm presently the following tests were conducted without loading lame.tcz
Rip to wav=OK
Rip/encode to flac=OK
Rip/encode to ogg=OK
Rip/encode to mp3=Fail

Re-rip/encode same files to mp3 after loading lame.tcz
Results:
Rip/encode to mp3=OK
   

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7071
Re: Asunder scm Bug Feedback
« Reply #3 on: March 14, 2012, 10:04:14 AM »
Ok, I did not have lame installed and it still worked, but I will retest.

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Re: Asunder scm Bug Feedback
« Reply #4 on: April 23, 2012, 12:58:37 AM »
Any news on this?

The symptoms are consistently observed in the following test environment
onboot.lst
Code: [Select]
Xvesa.tcz
Xprogs.tcz
kmaps.tcz
jwm.tcz

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7071
Re: Asunder scm Bug Feedback
« Reply #5 on: April 23, 2012, 05:38:22 AM »
Still works here.  Here is my contents of /usr/local/tce.installed used testing both ripperx and asunder:

Code: [Select]
Xlibs            expat2           icewm            portmap
Xorg-7.6-lib     fltk-1.10        imlib            tcp_wrappers
Xprogs           fontconfig       libiconv         wbar
Xvesa            glib1            ncurses          zsync
bash             graphics-libs-1  ncurses-common
dropbear         gtk1             nfs-utils


Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Re: Asunder scm Bug Feedback
« Reply #6 on: April 23, 2012, 11:20:44 AM »
OK, lets temporarily put this on hold and try to troubleshoot ripperX then return to this.
   

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7071
Re: Asunder scm Bug Feedback
« Reply #7 on: April 25, 2012, 02:50:27 PM »
Asunder is also looking for ncurses installed in a usual system path, just like ripperx. 

I will rebuild asunder from scratch when I get the opportunity, though we may be facing a situation of depending on a system path install of a package, which the scm format does not allow depending on in  a .dep file.   

But if ncurses can be installed into /usr/local instead of /usr, then it reasons that there is a way to install it into /apps/PKGNAME. 


Online gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 3337
Re: Asunder scm Bug Feedback
« Reply #8 on: April 25, 2012, 02:59:13 PM »
Maybe static linking would be a simpler solution.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7071
Re: Asunder scm Bug Feedback
« Reply #9 on: April 25, 2012, 04:08:19 PM »
Yeah, I think that somehow ncurses-dev.tcz was installed when building this and ripperx, so it is perhaps looking to a hard coded path.

In future builds, I will try static linking of ncurses to see if that solves the issue.  It would only cost a little space, but if it saves headaches it would be worth it.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7071
Re: Asunder scm Bug Feedback
« Reply #10 on: April 26, 2012, 05:54:22 PM »
Ok, what happened is that the system ncurses contains more libs than the version in the self contained extension, and they were linked when building lame.

I copied the missing libs to asunder and it is working, I will do the same with ripperx.

My TC time has been very sparse for the last month, as I would have normally been able to solve this kind of simple thing a lot sooner. 

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Re: Asunder scm Bug Feedback
« Reply #11 on: April 26, 2012, 11:37:30 PM »
I copied the missing libs to asunder and it is working...
Unfortunately I cannot test it. The scm had been deleted and had to be downloaded again which consistently produces the following:
Code: [Select]
ls -1l asunder.scm*
-rw-r--r--    1         0 Apr 27 07:30 asunder.scm
-rw-r--r--    1        10 Apr 27 07:30 asunder.scm.dep
-rw-r--r--    1        46 Apr 27 07:30 asunder.scm.md5.txt

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 7071
Re: Asunder scm Bug Feedback
« Reply #12 on: April 27, 2012, 06:21:34 AM »
On the server, both the size of the scm and the check of it's md5sum come out right, I don't know what could be the issue, and it is the same case with ripperx.

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Re: Asunder scm Bug Feedback
« Reply #13 on: April 28, 2012, 02:31:46 AM »
...I don't know what could be the issue...
I tracked the the matter down to a lack of space on the small flash drive used during testing.  Deleting all the wav files left over from previous tests resolved the problem.

Reporting success
Asunder now works as expected successfully ripping to wav, flac, mp3 and ogg.