Recent

Author Topic: Complex package installation problem  (Read 4475 times)

wp

  • Hero Member
  • *****
  • Posts: 12305
Re: Complex package installation problem
« Reply #15 on: March 27, 2024, 10:00:44 am »
I agree with TRon, LazAudioPlayer cannot be compiled, neither by a recent Laz/FPC, nor by Laz 1.4.4, the oldest one that I still have. I guess from the age of the project, a pre-version-1.0 Lazarus might work. Then, having a starting point, it would be required to slowly move forward to newer versions and the adapt the sources. But this is a lot of work... With the current versions there are too many dependencies and there are changes at numerous places.

It's a pity that an interesting project is lost...
« Last Edit: March 27, 2024, 10:14:21 am by wp »

cdbc

  • Hero Member
  • *****
  • Posts: 1499
    • http://www.cdbc.dk
Re: Complex package installation problem
« Reply #16 on: March 27, 2024, 10:57:38 am »
Hi
It's not entirely lost, I've got a fork of it, on my local machine and have been addressing some issues, as time has permitted.
Conceptually I like it, but there are __many__ issues  %)
Regards Benny
If it ain't broke, don't fix it ;)
PCLinuxOS(rolling release) 64bit -> KDE5 -> FPC 3.2.2 -> Lazarus 2.2.6 up until Jan 2024 from then on it's: KDE5/QT5 -> FPC 3.3.1 -> Lazarus 3.0

wp

  • Hero Member
  • *****
  • Posts: 12305
Re: Complex package installation problem
« Reply #17 on: March 27, 2024, 11:38:02 am »
Would you like to publish it? GitHub? Or send me a PM link to a private cloud with the source, and I could put it on CCR if it is in some acceptable state.

cdbc

  • Hero Member
  • *****
  • Posts: 1499
    • http://www.cdbc.dk
Re: Complex package installation problem
« Reply #18 on: March 27, 2024, 02:51:49 pm »
Hi wp
Right now its state is a 'right mess'.
To begin with I wanted to use it for wav -> mp3 conversion, then I encountered it many flaws and I started analyzing its parts...
I found out that the wavereader is sort of ok, needs a bit of love though, before it's ready to be released in the wild...
The import of the lame-library is done so that, it can only read 16bit signed waveforms(and I've got practically none of those), furthermore it can only handle 128kbit mp3 :-(
I started to refactor / extend the import code as I can test it against the wavereading component...
That's where I left it, due to time constraints...
I'd rather not share anything yet  :)
Regards Benny
If it ain't broke, don't fix it ;)
PCLinuxOS(rolling release) 64bit -> KDE5 -> FPC 3.2.2 -> Lazarus 2.2.6 up until Jan 2024 from then on it's: KDE5/QT5 -> FPC 3.3.1 -> Lazarus 3.0

wp

  • Hero Member
  • *****
  • Posts: 12305
Re: Complex package installation problem
« Reply #19 on: March 27, 2024, 05:22:52 pm »
OK.

dsiders

  • Hero Member
  • *****
  • Posts: 1218
Re: Complex package installation problem
« Reply #20 on: March 27, 2024, 07:13:24 pm »
So, in summary. Instead of blaming Lazarus... stop using that broken package.
Preview Lazarus 3.99 documentation at: https://dsiders.gitlab.io/lazdocsnext

cdbc

  • Hero Member
  • *****
  • Posts: 1499
    • http://www.cdbc.dk
Re: Complex package installation problem
« Reply #21 on: March 27, 2024, 07:37:15 pm »
Hi
@wp: This fork https://github.com/MageSlayer/acs was forked a couple of months ago... You could have a 'Looksee'...
...and the original is here https://github.com/serbod/acs
Regards Benny
« Last Edit: March 27, 2024, 07:40:11 pm by cdbc »
If it ain't broke, don't fix it ;)
PCLinuxOS(rolling release) 64bit -> KDE5 -> FPC 3.2.2 -> Lazarus 2.2.6 up until Jan 2024 from then on it's: KDE5/QT5 -> FPC 3.3.1 -> Lazarus 3.0

wp

  • Hero Member
  • *****
  • Posts: 12305
Re: Complex package installation problem
« Reply #22 on: March 27, 2024, 10:47:45 pm »
I see these are links to acs, but I was thinking of the LazAudioPlayer. When even acs is in such a bad shape it does not make any sense trying to revive LazAudioPlayer.

JonBondy

  • New Member
  • *
  • Posts: 24
Re: Complex package installation problem
« Reply #23 on: March 28, 2024, 12:48:28 pm »
Thanks to everyone who is helping me!

I am relieved to learn that what I was trying to do is basically impossible, so I will move on to another audio player.

I deleted the OPM directory tree, uninstalled Lazarus, and installed a single instance of the 64-bit Lazarus.

I looked at Tools, Examples, and found nothing useful, so I used OPM to install ACS.  When I looked again at Tools, Examples, there still were no audio examples.  I then drilled down into the OPM directory tree and found "Player", which compiles, but does not work (has bugs). Progress.

Thanks, again!

Jon

wp

  • Hero Member
  • *****
  • Posts: 12305
Re: Complex package installation problem
« Reply #24 on: March 28, 2024, 12:56:43 pm »
Tested yesterday that the UOS package (available in OPM) is working. Based on that and the sample projects provided you can try to create your favourite UOS audio player. If you have problems, ask here, the author of the package can be seen here in the forum occasionally.

parcel

  • Full Member
  • ***
  • Posts: 143
Re: Complex package installation problem
« Reply #25 on: March 28, 2024, 01:48:04 pm »

JonBondy

  • New Member
  • *
  • Posts: 24
Re: Complex package installation problem
« Reply #26 on: March 28, 2024, 02:46:19 pm »
The UOS player compiles after correcting for a missing USES statement, but 1) it always opens with a big black form behind the actual program, almost as if it ran a DOS window from which it then ran the actual program; and B) it ALWAYS asks where the libraries are, which is pretty annoying.  But it works.

The OvoPlayer causes an exception in the IDE and has so many missing pieces that I gave up.

Jon

wp

  • Hero Member
  • *****
  • Posts: 12305
Re: Complex package installation problem
« Reply #27 on: March 28, 2024, 03:38:16 pm »
The UOS player compiles after correcting for a missing USES statement, but 1) it always opens with a big black form behind the actual program, almost as if it ran a DOS window from which it then ran the actual program
Checked the "simpleplayer". The black form behind the program is a console window usually meant to catch debug output. It has nothing todo with running an external program. Go to "Project options" > "Compiler options" > "Config and target" and check "Win32 gui application" to remove the console window.

it ALWAYS asks where the libraries are, which is pretty annoying.
This is just a matter of these demo projects. You certainly can write code where loading of the needed libraries is done automatically, but then you must provide the correct paths to the dlls; the way it is done in the demos is to give to user a chance go specify the paths individually. Study the code in the demo and you'll find out.

 

TinyPortal © 2005-2018