Although capture set in alsamixer, precord records nothing at all, but this tool works well in lucid and racy.
I think the problem is not Precord, but Slacko.

Obviously, XVIDCAP does not record too. I was trying precord to test.
I test Precord 8.0.3 with Lucid 5.2.8 and I come back to inform you.
Precord runs on Slacko 5.3.3 XFCE : 2014 with specific version for Slacko

Have a nice week-end

814.jpg

Description

Settings by default

Filesize

53.72 KB

Viewed

244 Time(s)

Last edited by Pelo on Sat 05 Apr 2014, 04:30; edited 2 times in total

That post was really about problems with flash, nevertheless your problem in Slacko may also be something to do with the wrong sound module or modules being detected and loaded by Slacko. I'm just curious if you could try these commands from that link post whilst in Slacko and then try Precord there again. Easiest way to set up Precord, after trying the commands from that link, is to press the Mixer button in Precord big GUI and make sure you have the Capture control turned high in Retrovol and have your Mic selected and Mic boost selected and also select and turn up PCM and the Master volume. All going well, the alsa VU rxvt display will verify that your Mic is working (or not). Glad to hear things are fine in your Lucid (Macpup) installation at least though.

On my old machine at home, Wary actually gave the least problems with alsa sound, but Slacko worked well for me after running the commands given in the above link. I imagine it all depends on your machine's hardware and most people probably have alsa sound detected correctly by Slacko and working without issue.

I actually used Slacko-5.3.3 for most of the development work in the most recent Precord release, and I'm using Slacko at the moment and Precord is working fine on my machine. I also have Lucid 5.2.8 and Wary 5.3 on this same machine, and I use them all pretty much equally and also for testing Precord.

EDIT: I forgot to suggest you first try simply re-initialising alsa on your Slacko system by running the command alsaconf from a console. Precord is, I'm sure you understand, just a frontend for controlling primarily the alsa sound processes arecord and aplay as well as ffmpeg. Precord won't work if your soundcard isn't being detected correctly such that the underlying alsa system is working. And the mixer controls also have to be set up correctly before recording.

Precord Version 8.0.4 released. Download from first post in this thread.

Tested on Slacko-5.3.3, Lupu-5.2.8 and Wary 5.3 (I'm currently downloading Precise to try it there too - should be fine...)

No further features planned for the moment. Just bug fixing this one. Been significant changes with this "final" so all testing and bug reports appreciated. No bugs known as yet... NOTE WELL:

Definitely remove all traces of previous precord versions before installing this. Once you remove previous installation using petget package manager you must also delete the hidden config file /root/.precord or the new precord won't start. This version has new variables which aren't in the previous config file. If ever precord fails to start just delete that config directory and the new config directory will auto rebuild next time you run precord after which all should be fine..._________________DebianDog on githubSomeOfMyWork: weX, scrox, Precord, Premote, fokSyfEyeR, xhippo-mod, flite_hts_pet

Version 8.0.5 released: More logical drag and drop facility:
File entry takes precedence over Directory entry on filepath decision. Tidied up some of the code. NOTE WELL:

Definitely remove all traces of previous precord versions before installing this. Once you remove previous installation using petget package manager you must also delete the hidden config file /root/.precord or the new precord won't start. This version has new variables which aren't in the previous config file. If ever precord fails to start just delete that config directory and the new config directory will auto rebuild next time you run precord after which all should be fine..._________________DebianDog on githubSomeOfMyWork: weX, scrox, Precord, Premote, fokSyfEyeR, xhippo-mod, flite_hts_pet

Racy 5.3 comes with Precord preinstalled, so removing it before installing a newer version isn't really an option. Apparently the newer version installed over the older one without any problem. I played around with it a bit last night. Good job!

@L18L: thanks for that. I hadn't tested that the gettexts all worked. I had already almost completed version 8.0.6 (for other reasons) so I modified the helptext so that it can now be internationalised too.

Version 8.0.6: Rearranged the small GUI such that the rec/play buttons come first. That way the small GUI can be dragged part way off the right hand side of the screen and still be operatable.
Fixed helpsetup for internationalisation (thanks L18L for the pointer).

To take up the least real estate possible, when in small GUI mode you can now drag precord off the right hand screen edge so only rec, pause and stop buttons are visible. Only occupies around 100pixels wide that way. I often right click its menu bar and put precord as Layer Top, when browsing or using it to record skype conversations. Hence my wish to minimise the screen realestate needed for operation. For example, note that Precord is simply the three buttons at the very top right of the screen capture at the foot of this post:

NOTE WELL:

To be sure the new version will start, prior to installation you should definitely delete any pre-existing hidden config file /root/.precord (glad it ran okay for you anyway Flash). This version has new variables which aren't in the config file of some earlier versions. If ever precord fails to start just delete that config directory and the new config directory will auto rebuild next time you run precord after which all should be fine...

Translatable strings should be limited to one paragraph; don't let a single message be longer than ten lines. The reason is that when the translatable string changes, the translator is faced with the task of updating the entire translated string. Maybe only a single word will have changed in the English string, but the translator doesn't see that (with the current translation tools), therefore she has to proofread the entire message.

Many GNU programs have a ‘--help’ output that extends over several screen pages. It is a courtesy towards the translators to split such a message into several ones of five to ten lines each.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum