You can subscribe to this list here.
2003 |
Jan
|
Feb
(8) |
Mar
(3) |
Apr
|
May
(2) |
Jun
(8) |
Jul
(4) |
Aug
(12) |
Sep
(11) |
Oct
|
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(3) |
Feb
(3) |
Mar
(2) |
Apr
(17) |
May
(8) |
Jun
(6) |
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(5) |
Nov
(10) |
Dec
(5) |
2005 |
Jan
(4) |
Feb
|
Mar
(1) |
Apr
(23) |
May
(10) |
Jun
(3) |
Jul
(3) |
Aug
(10) |
Sep
|
Oct
(7) |
Nov
(8) |
Dec
|
2006 |
Jan
(5) |
Feb
(5) |
Mar
(11) |
Apr
(1) |
May
(3) |
Jun
|
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
(9) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(5) |
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
(4) |
Nov
(3) |
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(4) |
Nov
(2) |
Dec
|
2011 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
(15) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
(7) |
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(12) |
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: John C. <ci...@pu...> - 2021-03-09 07:14:57
|
I have been using the gwc cleanup 2021 version all evening with no issues, and listening with ALSA (finally!) I will continue using this version unless you want feedback on your update version instead. Happy to have it working again and better with Alsa. Cheers, John On 3/8/21 5:16 PM, John Cirillo wrote: > OK, I figured out why no Alsa. Even though my Alsa system is > apparently working fine, I noticed when running ./configure on gwc > that when it came to the check for Alsa, it said no. It always said > this, so I didn't put 2+2 together until now that it was trying to > tell me there won't be any Alsa support. I guess every version I > compiled was without Alsa support. I figured out that it wanted the > libasound2.dev package installed. Once I did that, the ./configure > says Alsa yes. And now once I recompiled, when I run gwc, I can put > hw:0,1 and it appears to be working fine. So the question now is, > which version should I be running? I have the sourceforge 0.22-4 and > now your newer branch, and Jeff's new branch too. I may as well use > the latest so I can help test it. And since my old 0.21-18 doesn't > support ALSA either, I guess I won't use it too much. I like that I > can have another app open that might use audio, and still use gwc. > > Thanks for helping me get this solved. Had no idea that a missing > library was killing the use of Alsa. > > John > > On 3/8/21 3:00 PM, Alister Hood wrote: >> If you're really getting ""failed to open OSS audio device ..." when >> you tried to build with the alsa backend it means you didn't run >> `make clean`. Unfortunately it is essential when changing backend. >> >> On Tue, 9 Mar 2021, 07:50 John Cirillo, <jo...@in... >> <mailto:jo...@in...>> wrote: >> >> Some progress and success today. And it may have been a poor >> choice of OSS emulation on my part that caused this. >> It appears that the osspd modules for simulating oss with alsa >> was causing the frozen cursor issue. After removing osspd and >> installing oss-compat, all is back as it was. Cursor works >> fine. I think I changed this about a month ago, not knowing >> which one was right, but didn't use GWC afterward so didn't know >> I broke it. >> There are several choices to get oss compatibility, and that is >> the problem I had. Before this, I used to have to modprobe >> snd-pcm-oss to get a /dev/dsp but now alsa supplies up to three >> different ways to get /dev/dsp. I chose the wrong one. I can >> live with this, as I have been all along but it would be nicer if >> I could get GWC to work with ALSA. >> >> I have never found the correct ALSA syntax to put in the audio >> device bar (in place of /dev/dsp). I know that my sound card is >> an Ensoniq AudioPCI (Cirrus Logic CS4297A rev 4) also known as >> ES1371. When I looked to see how Audacity calls this card, they >> put the entire name of the card and then at the end in >> parenthesis it says (hw:0,1). So I've tried putting those >> numbers in the audio device bar of GWC, and every other choice >> from hw:0,0 to 2,2 and plughw:0,0 to 2,2, also things like >> default, front, rear, and whatever else aplay -L listed as >> devices. So far, no luck. It always posts an error message >> "failed to open OSS audio device ..." >> Alsa would be better because as it is, if I use any other sound >> device at the same time as using GWC with /dev/dsp, the other >> device blocks gwc (such as using netflix on firefox). If you >> have any suggestions to get Alsa syntax correct on the GWC >> settings bar that would be great, but otherwise I can live with >> oss-compat. I have never liked Pulseaudio. For some reason >> it breaks KMIX and there's no way to select the desired input >> channel. Pulse's own mixer panel does not work for me. It says >> I selected line in, for example, but no sound is heard. So I >> always disable Pulse and use Alsa. >> >> Hope I was not too wordy. I can summarize if needed. I don't >> like leaving out what might be a crucial piece of info. >> Thanks, >> >> John >> >> On 3/8/21 3:13 AM, Alister Hood wrote: >>> If audio playback works in other programs, sure, maybe something >>> could be tweaked on your system to make it work, but it may well >>> indicate something that should be fixed in GWC too. >>> I'm pretty confident it will be audio related, not graphics, so >>> there's a pretty good chance it will work fine if you try >>> compiling with a different audio backend. The default is alsa - >>> run `make clean` first and configure with --disable-alsa to use >>> oss, and --enable-pa to use pulseaudio. >>> >>> >>> On Mon, 8 Mar 2021 at 20:18, John Cirillo >>> <jo...@in... <mailto:jo...@in...>> wrote: >>> >>> Follow-up note. I downloaded both your update and Jeff's on >>> github, built both versions. They both compiled fine and >>> ran. Audio works, if that was ever an issue. But the cursor >>> is still frozen. If I don't highlight an area, there is no >>> apparent cursor. If I highlight some data, the cursor >>> appears on the left, and just as I hit play, you can see the >>> cursor start moving and then stop. The music continues to play. >>> I don't think this is a GWC problem but a symptom of >>> something else. I am going to go about my business trying >>> other programs in the next day or so, and see if there are >>> any other weird video issues. >>> If it was a system update, it might go away with the next >>> update and we'll never know what it was. If I get desperate >>> I may try reinstalling Buster from the latest release, or >>> reinstalling my earlier iso to see if the problem goes >>> away. Very strange. >>> >>> On 3/8/21 2:00 AM, John Cirillo wrote: >>>> Hello Alister, >>>> Wonderful to know you're still out there. The list has been >>>> very quiet. >>>> >>>> My latest install of Buster was probably done in December >>>> of 2020. I had been running Jessie up until then, but >>>> finally it had to go. >>>> I normally use either the "GTK Wave Cleaner" package >>>> provided by Debian 10 (version 22 with no suffix shown) or >>>> my still-favorite version of 0.21-18. Last time I used >>>> either was about a month ago and things seemed normal. >>>> I didn't use it again until yesterday and that was when I >>>> noticed this oddity. Everything seems to work, but the >>>> scrolling cursor bar doesn't appear or if/when I highlight >>>> an area and hit play, the bar stays at the beginning of the >>>> highlight area. I did a full reboot to make sure nothing >>>> was locked up, which didn't help. I downloaded the latest >>>> version from sourceforge (0.22-4) and it compiled fine. I >>>> ran that version too, and it also has this cursor problem. >>>> So the same issue exists whether using 0.21-18, 0.22, or >>>> 0.22-4. Something changed within the last few weeks but >>>> what? Video driver? I am using Nouveau. I always use >>>> Nouveau as long as it plays nice with Netflix. I had the >>>> proprietary Nvidia drivers a few years ago but there was >>>> some issue and I went back to the free Nouveau package. >>>> >>>> I just now fired up Audacity to test it, and the cursor >>>> moves OK on that one. I know it's apples to oranges but it >>>> was easy to try. I don't prefer Audacity for anything >>>> besides recording. >>>> So that's where I am with this. I don't think the issue is >>>> with GWC at all, but something changed in a system file >>>> that doesn't play nicely with that cursor. >>>> >>>> I am willing to try the 2021 cleanup version to see what >>>> happens. >>>> >>>> >>>> On 3/8/21 1:27 AM, Alister Hood wrote: >>>>> Hi John, >>>>> There are certainly still people using gwc, and there has >>>>> even been a small burst of development recently (no >>>>> release yet). No, the mailing list hasn't moved. >>>>> >>>>> Are you running the gwc package Debian provides for >>>>> Buster? I see Buster was updated recently, so I guess >>>>> that is when your problem started? >>>>> >>>>> Are you able to compile from source instead? I doubt the >>>>> latest release will behave any differently, but Jeff has a >>>>> go at reworking the playback code this year, so I'd be >>>>> interested to know whether the master branch on github >>>>> (where I have merged the first half of his work), or >>>>> Jeff's working branch at >>>>> https://github.com/weltyj/gwc/tree/gwc_cleanup_2021 >>>>> <https://github.com/weltyj/gwc/tree/gwc_cleanup_2021> >>>>> behave better. In the systems I test on they have fixed >>>>> various issues like this. But unfortunately someone else >>>>> reported at https://github.com/AlisterH/gwc/issues/24 >>>>> <https://github.com/AlisterH/gwc/issues/24> that they >>>>> break playback on his system. >>>>> >>>>> Regards, >>>>> Alister >>>>> >>>>> On Mon, 8 Mar 2021 at 19:01, John Cirillo >>>>> <jo...@in... >>>>> <mailto:jo...@in...>> wrote: >>>>> >>>>> Is this still the mailing list for Gnome Wave Cleaner, >>>>> or has it moved >>>>> and I missed it? >>>>> I've been using it all along but now am having issues >>>>> with the cursor >>>>> not moving along with the music playing. >>>>> Debian Buster 64 bit. >>>>> >>>>> Thanks! >>>>> >>>>> >>>>> _______________________________________________ >>>>> Gwc-general mailing list >>>>> Gwc...@li... >>>>> <mailto:Gwc...@li...> >>>>> https://lists.sourceforge.net/lists/listinfo/gwc-general >>>>> <https://lists.sourceforge.net/lists/listinfo/gwc-general> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Gwc-general mailing list >>>>> Gwc...@li... <mailto:Gwc...@li...> >>>>> https://lists.sourceforge.net/lists/listinfo/gwc-general <https://lists.sourceforge.net/lists/listinfo/gwc-general> >>>> >>> >> > > > > _______________________________________________ > Gwc-general mailing list > Gwc...@li... > https://lists.sourceforge.net/lists/listinfo/gwc-general |
From: John C. <ci...@pu...> - 2021-03-08 22:50:21
|
OK, I figured out why no Alsa. Even though my Alsa system is apparently working fine, I noticed when running ./configure on gwc that when it came to the check for Alsa, it said no. It always said this, so I didn't put 2+2 together until now that it was trying to tell me there won't be any Alsa support. I guess every version I compiled was without Alsa support. I figured out that it wanted the libasound2.dev package installed. Once I did that, the ./configure says Alsa yes. And now once I recompiled, when I run gwc, I can put hw:0,1 and it appears to be working fine. So the question now is, which version should I be running? I have the sourceforge 0.22-4 and now your newer branch, and Jeff's new branch too. I may as well use the latest so I can help test it. And since my old 0.21-18 doesn't support ALSA either, I guess I won't use it too much. I like that I can have another app open that might use audio, and still use gwc. Thanks for helping me get this solved. Had no idea that a missing library was killing the use of Alsa. John On 3/8/21 3:00 PM, Alister Hood wrote: > If you're really getting ""failed to open OSS audio device ..." when > you tried to build with the alsa backend it means you didn't run `make > clean`. Unfortunately it is essential when changing backend. > > On Tue, 9 Mar 2021, 07:50 John Cirillo, <jo...@in... > <mailto:jo...@in...>> wrote: > > Some progress and success today. And it may have been a poor > choice of OSS emulation on my part that caused this. > It appears that the osspd modules for simulating oss with alsa was > causing the frozen cursor issue. After removing osspd and > installing oss-compat, all is back as it was. Cursor works fine. > I think I changed this about a month ago, not knowing which one > was right, but didn't use GWC afterward so didn't know I broke it. > There are several choices to get oss compatibility, and that is > the problem I had. Before this, I used to have to modprobe > snd-pcm-oss to get a /dev/dsp but now alsa supplies up to three > different ways to get /dev/dsp. I chose the wrong one. I can > live with this, as I have been all along but it would be nicer if > I could get GWC to work with ALSA. > > I have never found the correct ALSA syntax to put in the audio > device bar (in place of /dev/dsp). I know that my sound card is > an Ensoniq AudioPCI (Cirrus Logic CS4297A rev 4) also known as > ES1371. When I looked to see how Audacity calls this card, they > put the entire name of the card and then at the end in > parenthesis it says (hw:0,1). So I've tried putting those numbers > in the audio device bar of GWC, and every other choice from hw:0,0 > to 2,2 and plughw:0,0 to 2,2, also things like default, front, > rear, and whatever else aplay -L listed as devices. So far, no > luck. It always posts an error message "failed to open OSS audio > device ..." > Alsa would be better because as it is, if I use any other sound > device at the same time as using GWC with /dev/dsp, the other > device blocks gwc (such as using netflix on firefox). If you have > any suggestions to get Alsa syntax correct on the GWC settings bar > that would be great, but otherwise I can live with oss-compat. I > have never liked Pulseaudio. For some reason it breaks KMIX and > there's no way to select the desired input channel. Pulse's own > mixer panel does not work for me. It says I selected line in, for > example, but no sound is heard. So I always disable Pulse and use > Alsa. > > Hope I was not too wordy. I can summarize if needed. I don't > like leaving out what might be a crucial piece of info. > Thanks, > > John > > On 3/8/21 3:13 AM, Alister Hood wrote: >> If audio playback works in other programs, sure, maybe something >> could be tweaked on your system to make it work, but it may well >> indicate something that should be fixed in GWC too. >> I'm pretty confident it will be audio related, not graphics, so >> there's a pretty good chance it will work fine if you try >> compiling with a different audio backend. The default is alsa - >> run `make clean` first and configure with --disable-alsa to use >> oss, and --enable-pa to use pulseaudio. >> >> >> On Mon, 8 Mar 2021 at 20:18, John Cirillo >> <jo...@in... <mailto:jo...@in...>> wrote: >> >> Follow-up note. I downloaded both your update and Jeff's on >> github, built both versions. They both compiled fine and >> ran. Audio works, if that was ever an issue. But the cursor >> is still frozen. If I don't highlight an area, there is no >> apparent cursor. If I highlight some data, the cursor >> appears on the left, and just as I hit play, you can see the >> cursor start moving and then stop. The music continues to play. >> I don't think this is a GWC problem but a symptom of >> something else. I am going to go about my business trying >> other programs in the next day or so, and see if there are >> any other weird video issues. >> If it was a system update, it might go away with the next >> update and we'll never know what it was. If I get desperate >> I may try reinstalling Buster from the latest release, or >> reinstalling my earlier iso to see if the problem goes >> away. Very strange. >> >> On 3/8/21 2:00 AM, John Cirillo wrote: >>> Hello Alister, >>> Wonderful to know you're still out there. The list has been >>> very quiet. >>> >>> My latest install of Buster was probably done in December of >>> 2020. I had been running Jessie up until then, but finally >>> it had to go. >>> I normally use either the "GTK Wave Cleaner" package >>> provided by Debian 10 (version 22 with no suffix shown) or >>> my still-favorite version of 0.21-18. Last time I used >>> either was about a month ago and things seemed normal. >>> I didn't use it again until yesterday and that was when I >>> noticed this oddity. Everything seems to work, but the >>> scrolling cursor bar doesn't appear or if/when I highlight >>> an area and hit play, the bar stays at the beginning of the >>> highlight area. I did a full reboot to make sure nothing >>> was locked up, which didn't help. I downloaded the latest >>> version from sourceforge (0.22-4) and it compiled fine. I >>> ran that version too, and it also has this cursor problem. >>> So the same issue exists whether using 0.21-18, 0.22, or >>> 0.22-4. Something changed within the last few weeks but >>> what? Video driver? I am using Nouveau. I always use >>> Nouveau as long as it plays nice with Netflix. I had the >>> proprietary Nvidia drivers a few years ago but there was >>> some issue and I went back to the free Nouveau package. >>> >>> I just now fired up Audacity to test it, and the cursor >>> moves OK on that one. I know it's apples to oranges but it >>> was easy to try. I don't prefer Audacity for anything >>> besides recording. >>> So that's where I am with this. I don't think the issue is >>> with GWC at all, but something changed in a system file that >>> doesn't play nicely with that cursor. >>> >>> I am willing to try the 2021 cleanup version to see what >>> happens. >>> >>> >>> On 3/8/21 1:27 AM, Alister Hood wrote: >>>> Hi John, >>>> There are certainly still people using gwc, and there has >>>> even been a small burst of development recently (no release >>>> yet). No, the mailing list hasn't moved. >>>> >>>> Are you running the gwc package Debian provides for >>>> Buster? I see Buster was updated recently, so I guess that >>>> is when your problem started? >>>> >>>> Are you able to compile from source instead? I doubt the >>>> latest release will behave any differently, but Jeff has a >>>> go at reworking the playback code this year, so I'd be >>>> interested to know whether the master branch on github >>>> (where I have merged the first half of his work), or Jeff's >>>> working branch at >>>> https://github.com/weltyj/gwc/tree/gwc_cleanup_2021 >>>> <https://github.com/weltyj/gwc/tree/gwc_cleanup_2021> >>>> behave better. In the systems I test on they have fixed >>>> various issues like this. But unfortunately someone else >>>> reported at https://github.com/AlisterH/gwc/issues/24 >>>> <https://github.com/AlisterH/gwc/issues/24> that they break >>>> playback on his system. >>>> >>>> Regards, >>>> Alister >>>> >>>> On Mon, 8 Mar 2021 at 19:01, John Cirillo >>>> <jo...@in... >>>> <mailto:jo...@in...>> wrote: >>>> >>>> Is this still the mailing list for Gnome Wave Cleaner, >>>> or has it moved >>>> and I missed it? >>>> I've been using it all along but now am having issues >>>> with the cursor >>>> not moving along with the music playing. >>>> Debian Buster 64 bit. >>>> >>>> Thanks! >>>> >>>> >>>> _______________________________________________ >>>> Gwc-general mailing list >>>> Gwc...@li... >>>> <mailto:Gwc...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/gwc-general >>>> <https://lists.sourceforge.net/lists/listinfo/gwc-general> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Gwc-general mailing list >>>> Gwc...@li... <mailto:Gwc...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/gwc-general <https://lists.sourceforge.net/lists/listinfo/gwc-general> >>> >> > |
From: Alister H. <ali...@gm...> - 2021-03-08 20:01:15
|
If you're really getting ""failed to open OSS audio device ..." when you tried to build with the alsa backend it means you didn't run `make clean`. Unfortunately it is essential when changing backend. On Tue, 9 Mar 2021, 07:50 John Cirillo, <jo...@in...> wrote: > Some progress and success today. And it may have been a poor choice of > OSS emulation on my part that caused this. > It appears that the osspd modules for simulating oss with alsa was causing > the frozen cursor issue. After removing osspd and installing oss-compat, > all is back as it was. Cursor works fine. I think I changed this about a > month ago, not knowing which one was right, but didn't use GWC afterward so > didn't know I broke it. > There are several choices to get oss compatibility, and that is the > problem I had. Before this, I used to have to modprobe snd-pcm-oss to get > a /dev/dsp but now alsa supplies up to three different ways to get > /dev/dsp. I chose the wrong one. I can live with this, as I have been > all along but it would be nicer if I could get GWC to work with ALSA. > > I have never found the correct ALSA syntax to put in the audio device bar > (in place of /dev/dsp). I know that my sound card is an Ensoniq AudioPCI > (Cirrus Logic CS4297A rev 4) also known as ES1371. When I looked to see > how Audacity calls this card, they put the entire name of the card and then > at the end in parenthesis it says (hw:0,1). So I've tried putting those > numbers in the audio device bar of GWC, and every other choice from hw:0,0 > to 2,2 and plughw:0,0 to 2,2, also things like default, front, rear, and > whatever else aplay -L listed as devices. So far, no luck. It always > posts an error message "failed to open OSS audio device ..." > Alsa would be better because as it is, if I use any other sound device at > the same time as using GWC with /dev/dsp, the other device blocks gwc (such > as using netflix on firefox). If you have any suggestions to get Alsa > syntax correct on the GWC settings bar that would be great, but otherwise I > can live with oss-compat. I have never liked Pulseaudio. For some > reason it breaks KMIX and there's no way to select the desired input > channel. Pulse's own mixer panel does not work for me. It says I selected > line in, for example, but no sound is heard. So I always disable Pulse and > use Alsa. > > Hope I was not too wordy. I can summarize if needed. I don't like > leaving out what might be a crucial piece of info. > Thanks, > > John > > On 3/8/21 3:13 AM, Alister Hood wrote: > > If audio playback works in other programs, sure, maybe something could be > tweaked on your system to make it work, but it may well indicate something > that should be fixed in GWC too. > I'm pretty confident it will be audio related, not graphics, so there's a > pretty good chance it will work fine if you try compiling with a different > audio backend. The default is alsa - run `make clean` first and configure > with --disable-alsa to use oss, and --enable-pa to use pulseaudio. > > > On Mon, 8 Mar 2021 at 20:18, John Cirillo <jo...@in...> > wrote: > >> Follow-up note. I downloaded both your update and Jeff's on github, >> built both versions. They both compiled fine and ran. Audio works, if >> that was ever an issue. But the cursor is still frozen. If I don't >> highlight an area, there is no apparent cursor. If I highlight some data, >> the cursor appears on the left, and just as I hit play, you can see the >> cursor start moving and then stop. The music continues to play. >> I don't think this is a GWC problem but a symptom of something else. I >> am going to go about my business trying other programs in the next day or >> so, and see if there are any other weird video issues. >> If it was a system update, it might go away with the next update and >> we'll never know what it was. If I get desperate I may try reinstalling >> Buster from the latest release, or reinstalling my earlier iso to see if >> the problem goes away. Very strange. >> >> On 3/8/21 2:00 AM, John Cirillo wrote: >> >> Hello Alister, >> Wonderful to know you're still out there. The list has been very quiet. >> >> My latest install of Buster was probably done in December of 2020. I had >> been running Jessie up until then, but finally it had to go. >> I normally use either the "GTK Wave Cleaner" package provided by Debian >> 10 (version 22 with no suffix shown) or my still-favorite version of >> 0.21-18. Last time I used either was about a month ago and things seemed >> normal. >> I didn't use it again until yesterday and that was when I noticed this >> oddity. Everything seems to work, but the scrolling cursor bar doesn't >> appear or if/when I highlight an area and hit play, the bar stays at the >> beginning of the highlight area. I did a full reboot to make sure nothing >> was locked up, which didn't help. I downloaded the latest version from >> sourceforge (0.22-4) and it compiled fine. I ran that version too, and it >> also has this cursor problem. So the same issue exists whether using >> 0.21-18, 0.22, or 0.22-4. Something changed within the last few weeks but >> what? Video driver? I am using Nouveau. I always use Nouveau as long as >> it plays nice with Netflix. I had the proprietary Nvidia drivers a few >> years ago but there was some issue and I went back to the free Nouveau >> package. >> >> I just now fired up Audacity to test it, and the cursor moves OK on that >> one. I know it's apples to oranges but it was easy to try. I don't prefer >> Audacity for anything besides recording. >> So that's where I am with this. I don't think the issue is with GWC at >> all, but something changed in a system file that doesn't play nicely with >> that cursor. >> >> I am willing to try the 2021 cleanup version to see what happens. >> >> >> On 3/8/21 1:27 AM, Alister Hood wrote: >> >> Hi John, >> There are certainly still people using gwc, and there has even been a >> small burst of development recently (no release yet). No, the mailing list >> hasn't moved. >> >> Are you running the gwc package Debian provides for Buster? I see Buster >> was updated recently, so I guess that is when your problem started? >> >> Are you able to compile from source instead? I doubt the latest release >> will behave any differently, but Jeff has a go at reworking the playback >> code this year, so I'd be interested to know whether the master branch on >> github (where I have merged the first half of his work), or Jeff's working >> branch at https://github.com/weltyj/gwc/tree/gwc_cleanup_2021 behave >> better. In the systems I test on they have fixed various issues like >> this. But unfortunately someone else reported at >> https://github.com/AlisterH/gwc/issues/24 that they break playback on >> his system. >> >> Regards, >> Alister >> >> On Mon, 8 Mar 2021 at 19:01, John Cirillo <jo...@in...> >> wrote: >> >>> Is this still the mailing list for Gnome Wave Cleaner, or has it moved >>> and I missed it? >>> I've been using it all along but now am having issues with the cursor >>> not moving along with the music playing. >>> Debian Buster 64 bit. >>> >>> Thanks! >>> >>> >>> _______________________________________________ >>> Gwc-general mailing list >>> Gwc...@li... >>> https://lists.sourceforge.net/lists/listinfo/gwc-general >>> >> >> >> _______________________________________________ >> Gwc-general mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/gwc-general >> >> >> >> > |
From: John C. <jo...@in...> - 2021-03-08 18:50:38
|
Some progress and success today. And it may have been a poor choice of OSS emulation on my part that caused this. It appears that the osspd modules for simulating oss with alsa was causing the frozen cursor issue. After removing osspd and installing oss-compat, all is back as it was. Cursor works fine. I think I changed this about a month ago, not knowing which one was right, but didn't use GWC afterward so didn't know I broke it. There are several choices to get oss compatibility, and that is the problem I had. Before this, I used to have to modprobe snd-pcm-oss to get a /dev/dsp but now alsa supplies up to three different ways to get /dev/dsp. I chose the wrong one. I can live with this, as I have been all along but it would be nicer if I could get GWC to work with ALSA. I have never found the correct ALSA syntax to put in the audio device bar (in place of /dev/dsp). I know that my sound card is an Ensoniq AudioPCI (Cirrus Logic CS4297A rev 4) also known as ES1371. When I looked to see how Audacity calls this card, they put the entire name of the card and then at the end in parenthesis it says (hw:0,1). So I've tried putting those numbers in the audio device bar of GWC, and every other choice from hw:0,0 to 2,2 and plughw:0,0 to 2,2, also things like default, front, rear, and whatever else aplay -L listed as devices. So far, no luck. It always posts an error message "failed to open OSS audio device ..." Alsa would be better because as it is, if I use any other sound device at the same time as using GWC with /dev/dsp, the other device blocks gwc (such as using netflix on firefox). If you have any suggestions to get Alsa syntax correct on the GWC settings bar that would be great, but otherwise I can live with oss-compat. I have never liked Pulseaudio. For some reason it breaks KMIX and there's no way to select the desired input channel. Pulse's own mixer panel does not work for me. It says I selected line in, for example, but no sound is heard. So I always disable Pulse and use Alsa. Hope I was not too wordy. I can summarize if needed. I don't like leaving out what might be a crucial piece of info. Thanks, John On 3/8/21 3:13 AM, Alister Hood wrote: > If audio playback works in other programs, sure, maybe something > could be tweaked on your system to make it work, but it may well > indicate something that should be fixed in GWC too. > I'm pretty confident it will be audio related, not graphics, so > there's a pretty good chance it will work fine if you try compiling > with a different audio backend. The default is alsa - run `make > clean` first and configure with --disable-alsa to use oss, and > --enable-pa to use pulseaudio. > > > On Mon, 8 Mar 2021 at 20:18, John Cirillo <jo...@in... > <mailto:jo...@in...>> wrote: > > Follow-up note. I downloaded both your update and Jeff's on > github, built both versions. They both compiled fine and ran. > Audio works, if that was ever an issue. But the cursor is still > frozen. If I don't highlight an area, there is no apparent > cursor. If I highlight some data, the cursor appears on the left, > and just as I hit play, you can see the cursor start moving and > then stop. The music continues to play. > I don't think this is a GWC problem but a symptom of something > else. I am going to go about my business trying other programs in > the next day or so, and see if there are any other weird video > issues. > If it was a system update, it might go away with the next update > and we'll never know what it was. If I get desperate I may try > reinstalling Buster from the latest release, or reinstalling my > earlier iso to see if the problem goes away. Very strange. > > On 3/8/21 2:00 AM, John Cirillo wrote: >> Hello Alister, >> Wonderful to know you're still out there. The list has been very >> quiet. >> >> My latest install of Buster was probably done in December of >> 2020. I had been running Jessie up until then, but finally it >> had to go. >> I normally use either the "GTK Wave Cleaner" package provided by >> Debian 10 (version 22 with no suffix shown) or my still-favorite >> version of 0.21-18. Last time I used either was about a month >> ago and things seemed normal. >> I didn't use it again until yesterday and that was when I noticed >> this oddity. Everything seems to work, but the scrolling cursor >> bar doesn't appear or if/when I highlight an area and hit play, >> the bar stays at the beginning of the highlight area. I did a >> full reboot to make sure nothing was locked up, which didn't >> help. I downloaded the latest version from sourceforge >> (0.22-4) and it compiled fine. I ran that version too, and it >> also has this cursor problem. So the same issue exists whether >> using 0.21-18, 0.22, or 0.22-4. Something changed within the >> last few weeks but what? Video driver? I am using Nouveau. I >> always use Nouveau as long as it plays nice with Netflix. I had >> the proprietary Nvidia drivers a few years ago but there was some >> issue and I went back to the free Nouveau package. >> >> I just now fired up Audacity to test it, and the cursor moves OK >> on that one. I know it's apples to oranges but it was easy to >> try. I don't prefer Audacity for anything besides recording. >> So that's where I am with this. I don't think the issue is with >> GWC at all, but something changed in a system file that doesn't >> play nicely with that cursor. >> >> I am willing to try the 2021 cleanup version to see what happens. >> >> >> On 3/8/21 1:27 AM, Alister Hood wrote: >>> Hi John, >>> There are certainly still people using gwc, and there has even >>> been a small burst of development recently (no release yet). >>> No, the mailing list hasn't moved. >>> >>> Are you running the gwc package Debian provides for Buster? I >>> see Buster was updated recently, so I guess that is when your >>> problem started? >>> >>> Are you able to compile from source instead? I doubt the latest >>> release will behave any differently, but Jeff has a go at >>> reworking the playback code this year, so I'd be interested to >>> know whether the master branch on github (where I have merged >>> the first half of his work), or Jeff's working branch at >>> https://github.com/weltyj/gwc/tree/gwc_cleanup_2021 >>> <https://github.com/weltyj/gwc/tree/gwc_cleanup_2021> behave >>> better. In the systems I test on they have fixed various issues >>> like this. But unfortunately someone else reported at >>> https://github.com/AlisterH/gwc/issues/24 >>> <https://github.com/AlisterH/gwc/issues/24> that they break >>> playback on his system. >>> >>> Regards, >>> Alister >>> >>> On Mon, 8 Mar 2021 at 19:01, John Cirillo >>> <jo...@in... <mailto:jo...@in...>> wrote: >>> >>> Is this still the mailing list for Gnome Wave Cleaner, or >>> has it moved >>> and I missed it? >>> I've been using it all along but now am having issues with >>> the cursor >>> not moving along with the music playing. >>> Debian Buster 64 bit. >>> >>> Thanks! >>> >>> >>> _______________________________________________ >>> Gwc-general mailing list >>> Gwc...@li... >>> <mailto:Gwc...@li...> >>> https://lists.sourceforge.net/lists/listinfo/gwc-general >>> <https://lists.sourceforge.net/lists/listinfo/gwc-general> >>> >>> >>> >>> _______________________________________________ >>> Gwc-general mailing list >>> Gwc...@li... <mailto:Gwc...@li...> >>> https://lists.sourceforge.net/lists/listinfo/gwc-general <https://lists.sourceforge.net/lists/listinfo/gwc-general> >> > |
From: John C. <ci...@pu...> - 2021-03-08 09:33:11
|
Hello Alister, Wonderful to know you're still out there. The list has been very quiet. My latest install of Buster was probably done in December of 2020. I had been running Jessie up until then, but finally it had to go. I normally use either the "GTK Wave Cleaner" package provided by Debian 10 (version 22 with no suffix shown) or my still-favorite version of 0.21-18. Last time I used either was about a month ago and things seemed normal. I didn't use it again until yesterday and that was when I noticed this oddity. Everything seems to work, but the scrolling cursor bar doesn't appear or if/when I highlight an area and hit play, the bar stays at the beginning of the highlight area. I did a full reboot to make sure nothing was locked up, which didn't help. I downloaded the latest version from sourceforge (0.22-4) and it compiled fine. I ran that version too, and it also has this cursor problem. So the same issue exists whether using 0.21-18, 0.22, or 0.22-4. Something changed within the last few weeks but what? Video driver? I am using Nouveau. I always use Nouveau as long as it plays nice with Netflix. I had the proprietary Nvidia drivers a few years ago but there was some issue and I went back to the free Nouveau package. I just now fired up Audacity to test it, and the cursor moves OK on that one. I know it's apples to oranges but it was easy to try. I don't prefer Audacity for anything besides recording. So that's where I am with this. I don't think the issue is with GWC at all, but something changed in a system file that doesn't play nicely with that cursor. I am willing to try the 2021 cleanup version to see what happens. On 3/8/21 1:27 AM, Alister Hood wrote: > Hi John, > There are certainly still people using gwc, and there has even been a > small burst of development recently (no release yet). No, the mailing > list hasn't moved. > > Are you running the gwc package Debian provides for Buster? I see > Buster was updated recently, so I guess that is when your problem started? > > Are you able to compile from source instead? I doubt the latest > release will behave any differently, but Jeff has a go at reworking > the playback code this year, so I'd be interested to know whether the > master branch on github (where I have merged the first half of his > work), or Jeff's working branch at > https://github.com/weltyj/gwc/tree/gwc_cleanup_2021 > <https://github.com/weltyj/gwc/tree/gwc_cleanup_2021> behave better. > In the systems I test on they have fixed various issues like this. > But unfortunately someone else reported at > https://github.com/AlisterH/gwc/issues/24 > <https://github.com/AlisterH/gwc/issues/24> that they break playback > on his system. > > Regards, > Alister > > On Mon, 8 Mar 2021 at 19:01, John Cirillo <jo...@in... > <mailto:jo...@in...>> wrote: > > Is this still the mailing list for Gnome Wave Cleaner, or has it > moved > and I missed it? > I've been using it all along but now am having issues with the cursor > not moving along with the music playing. > Debian Buster 64 bit. > > Thanks! > > > _______________________________________________ > Gwc-general mailing list > Gwc...@li... > <mailto:Gwc...@li...> > https://lists.sourceforge.net/lists/listinfo/gwc-general > <https://lists.sourceforge.net/lists/listinfo/gwc-general> > > > > _______________________________________________ > Gwc-general mailing list > Gwc...@li... > https://lists.sourceforge.net/lists/listinfo/gwc-general |
From: Alister H. <ali...@gm...> - 2021-03-08 08:14:16
|
If audio playback works in other programs, sure, maybe something could be tweaked on your system to make it work, but it may well indicate something that should be fixed in GWC too. I'm pretty confident it will be audio related, not graphics, so there's a pretty good chance it will work fine if you try compiling with a different audio backend. The default is alsa - run `make clean` first and configure with --disable-alsa to use oss, and --enable-pa to use pulseaudio. On Mon, 8 Mar 2021 at 20:18, John Cirillo <jo...@in...> wrote: > Follow-up note. I downloaded both your update and Jeff's on github, built > both versions. They both compiled fine and ran. Audio works, if that was > ever an issue. But the cursor is still frozen. If I don't highlight an > area, there is no apparent cursor. If I highlight some data, the cursor > appears on the left, and just as I hit play, you can see the cursor start > moving and then stop. The music continues to play. > I don't think this is a GWC problem but a symptom of something else. I am > going to go about my business trying other programs in the next day or so, > and see if there are any other weird video issues. > If it was a system update, it might go away with the next update and we'll > never know what it was. If I get desperate I may try reinstalling Buster > from the latest release, or reinstalling my earlier iso to see if the > problem goes away. Very strange. > > On 3/8/21 2:00 AM, John Cirillo wrote: > > Hello Alister, > Wonderful to know you're still out there. The list has been very quiet. > > My latest install of Buster was probably done in December of 2020. I had > been running Jessie up until then, but finally it had to go. > I normally use either the "GTK Wave Cleaner" package provided by Debian 10 > (version 22 with no suffix shown) or my still-favorite version of 0.21-18. > Last time I used either was about a month ago and things seemed normal. > I didn't use it again until yesterday and that was when I noticed this > oddity. Everything seems to work, but the scrolling cursor bar doesn't > appear or if/when I highlight an area and hit play, the bar stays at the > beginning of the highlight area. I did a full reboot to make sure nothing > was locked up, which didn't help. I downloaded the latest version from > sourceforge (0.22-4) and it compiled fine. I ran that version too, and it > also has this cursor problem. So the same issue exists whether using > 0.21-18, 0.22, or 0.22-4. Something changed within the last few weeks but > what? Video driver? I am using Nouveau. I always use Nouveau as long as > it plays nice with Netflix. I had the proprietary Nvidia drivers a few > years ago but there was some issue and I went back to the free Nouveau > package. > > I just now fired up Audacity to test it, and the cursor moves OK on that > one. I know it's apples to oranges but it was easy to try. I don't prefer > Audacity for anything besides recording. > So that's where I am with this. I don't think the issue is with GWC at > all, but something changed in a system file that doesn't play nicely with > that cursor. > > I am willing to try the 2021 cleanup version to see what happens. > > > On 3/8/21 1:27 AM, Alister Hood wrote: > > Hi John, > There are certainly still people using gwc, and there has even been a > small burst of development recently (no release yet). No, the mailing list > hasn't moved. > > Are you running the gwc package Debian provides for Buster? I see Buster > was updated recently, so I guess that is when your problem started? > > Are you able to compile from source instead? I doubt the latest release > will behave any differently, but Jeff has a go at reworking the playback > code this year, so I'd be interested to know whether the master branch on > github (where I have merged the first half of his work), or Jeff's working > branch at https://github.com/weltyj/gwc/tree/gwc_cleanup_2021 behave > better. In the systems I test on they have fixed various issues like > this. But unfortunately someone else reported at > https://github.com/AlisterH/gwc/issues/24 that they break playback on his > system. > > Regards, > Alister > > On Mon, 8 Mar 2021 at 19:01, John Cirillo <jo...@in...> > wrote: > >> Is this still the mailing list for Gnome Wave Cleaner, or has it moved >> and I missed it? >> I've been using it all along but now am having issues with the cursor >> not moving along with the music playing. >> Debian Buster 64 bit. >> >> Thanks! >> >> >> _______________________________________________ >> Gwc-general mailing list >> Gwc...@li... >> https://lists.sourceforge.net/lists/listinfo/gwc-general >> > > > _______________________________________________ > Gwc-general mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/gwc-general > > > > |
From: John C. <jo...@in...> - 2021-03-08 07:18:40
|
Follow-up note. I downloaded both your update and Jeff's on github, built both versions. They both compiled fine and ran. Audio works, if that was ever an issue. But the cursor is still frozen. If I don't highlight an area, there is no apparent cursor. If I highlight some data, the cursor appears on the left, and just as I hit play, you can see the cursor start moving and then stop. The music continues to play. I don't think this is a GWC problem but a symptom of something else. I am going to go about my business trying other programs in the next day or so, and see if there are any other weird video issues. If it was a system update, it might go away with the next update and we'll never know what it was. If I get desperate I may try reinstalling Buster from the latest release, or reinstalling my earlier iso to see if the problem goes away. Very strange. On 3/8/21 2:00 AM, John Cirillo wrote: > Hello Alister, > Wonderful to know you're still out there. The list has been very quiet. > > My latest install of Buster was probably done in December of 2020. I > had been running Jessie up until then, but finally it had to go. > I normally use either the "GTK Wave Cleaner" package provided by > Debian 10 (version 22 with no suffix shown) or my still-favorite > version of 0.21-18. Last time I used either was about a month ago and > things seemed normal. > I didn't use it again until yesterday and that was when I noticed this > oddity. Everything seems to work, but the scrolling cursor bar > doesn't appear or if/when I highlight an area and hit play, the bar > stays at the beginning of the highlight area. I did a full reboot to > make sure nothing was locked up, which didn't help. I downloaded > the latest version from sourceforge (0.22-4) and it compiled fine. I > ran that version too, and it also has this cursor problem. So the > same issue exists whether using 0.21-18, 0.22, or 0.22-4. Something > changed within the last few weeks but what? Video driver? I am using > Nouveau. I always use Nouveau as long as it plays nice with > Netflix. I had the proprietary Nvidia drivers a few years ago but > there was some issue and I went back to the free Nouveau package. > > I just now fired up Audacity to test it, and the cursor moves OK on > that one. I know it's apples to oranges but it was easy to try. I > don't prefer Audacity for anything besides recording. > So that's where I am with this. I don't think the issue is with GWC > at all, but something changed in a system file that doesn't play > nicely with that cursor. > > I am willing to try the 2021 cleanup version to see what happens. > > > On 3/8/21 1:27 AM, Alister Hood wrote: >> Hi John, >> There are certainly still people using gwc, and there has even been a >> small burst of development recently (no release yet). No, the >> mailing list hasn't moved. >> >> Are you running the gwc package Debian provides for Buster? I see >> Buster was updated recently, so I guess that is when your problem >> started? >> >> Are you able to compile from source instead? I doubt the latest >> release will behave any differently, but Jeff has a go at reworking >> the playback code this year, so I'd be interested to know whether the >> master branch on github (where I have merged the first half of his >> work), or Jeff's working branch at >> https://github.com/weltyj/gwc/tree/gwc_cleanup_2021 >> <https://github.com/weltyj/gwc/tree/gwc_cleanup_2021> behave better. >> In the systems I test on they have fixed various issues like this. >> But unfortunately someone else reported at >> https://github.com/AlisterH/gwc/issues/24 >> <https://github.com/AlisterH/gwc/issues/24> that they break playback >> on his system. >> >> Regards, >> Alister >> >> On Mon, 8 Mar 2021 at 19:01, John Cirillo <jo...@in... >> <mailto:jo...@in...>> wrote: >> >> Is this still the mailing list for Gnome Wave Cleaner, or has it >> moved >> and I missed it? >> I've been using it all along but now am having issues with the >> cursor >> not moving along with the music playing. >> Debian Buster 64 bit. >> >> Thanks! >> >> >> _______________________________________________ >> Gwc-general mailing list >> Gwc...@li... >> <mailto:Gwc...@li...> >> https://lists.sourceforge.net/lists/listinfo/gwc-general >> <https://lists.sourceforge.net/lists/listinfo/gwc-general> >> >> >> >> _______________________________________________ >> Gwc-general mailing list >> Gwc...@li... >> https://lists.sourceforge.net/lists/listinfo/gwc-general > |
From: Alister H. <ali...@gm...> - 2021-03-08 06:28:19
|
Hi John, There are certainly still people using gwc, and there has even been a small burst of development recently (no release yet). No, the mailing list hasn't moved. Are you running the gwc package Debian provides for Buster? I see Buster was updated recently, so I guess that is when your problem started? Are you able to compile from source instead? I doubt the latest release will behave any differently, but Jeff has a go at reworking the playback code this year, so I'd be interested to know whether the master branch on github (where I have merged the first half of his work), or Jeff's working branch at https://github.com/weltyj/gwc/tree/gwc_cleanup_2021 behave better. In the systems I test on they have fixed various issues like this. But unfortunately someone else reported at https://github.com/AlisterH/gwc/issues/24 that they break playback on his system. Regards, Alister On Mon, 8 Mar 2021 at 19:01, John Cirillo <jo...@in...> wrote: > Is this still the mailing list for Gnome Wave Cleaner, or has it moved > and I missed it? > I've been using it all along but now am having issues with the cursor > not moving along with the music playing. > Debian Buster 64 bit. > > Thanks! > > > _______________________________________________ > Gwc-general mailing list > Gwc...@li... > https://lists.sourceforge.net/lists/listinfo/gwc-general > |
From: John C. <jo...@in...> - 2021-03-08 06:01:26
|
Is this still the mailing list for Gnome Wave Cleaner, or has it moved and I missed it? I've been using it all along but now am having issues with the cursor not moving along with the music playing. Debian Buster 64 bit. Thanks! |
From: Alister H. <ali...@gm...> - 2018-09-18 08:48:36
|
Hi everyone, I know this conversation is very old, but for the record, I have today pushed a fix in master (https://github.com/AlisterH/gwc) for mono files playing at 2x speed when using the pulseaudio backend. Hopefully this was the problem Tom encountered, and there isn't a separate issue causing 2x playback. I believe all three linux backends (oss, alsa and pulseaudio) are working reasonably reliably now. However, I have only tested the pulseaudio backend in Ubuntu on WSL (Windows Subsystem for Linux), not on an actual Linux system. If there are others using the pulseaudio backend I'd appreciate it if they can test this latest change to make sure it doesn't break anything. Thanks. On Fri, 13 May 2016 at 00:08, Alister Hood <ali...@gm...> wrote: > Hi Tom, > GWC can be compiled to use either alsa, pulseaudio, or OSS. I'm guessing > your GWC is compiled to use pulseaudio - is that right? I had the same > problem when I tried it with pulseaudio, but I didn't have the motivation > to pursue it further as I don't want pulseaudio anyway. Unfortunately > there are also nasty problems when using the alsa support (at least one of > which appears to be a regression of a very old bug) - I did spend quite a > bit of time trying to work out how to debug these, but it was over my head. > I can't remember if these issues have been reported in official channels, > but II wrote about them for future reference at > https://github.com/AlisterH/gwc/issues/1 and for now I am using the OSS > support and aoss, so I'd suggest trying that if no one can help. > > Regards, > Alister > On 12/05/2016 2:14 AM, "tom" <tom...@gm...> wrote: > >> GWC is playing loaded wave files at or near twice the normal speed. When >> launching from the command line I see the following warning messages: >> >> (process:3107): GLib-GObject-WARNING **: Attempt to add property >> GnomeProgram::sm-connect after class was initialised >> >> (process:3107): GLib-GObject-WARNING **: Attempt to add property >> GnomeProgram::show-crash-dialog after class was initialised >> >> (process:3107): GLib-GObject-WARNING **: Attempt to add property >> GnomeProgram::display after class was initialised >> >> (process:3107): GLib-GObject-WARNING **: Attempt to add property >> GnomeProgram::default-icon after class was initialised >> libsndfile Version: libsndfile-1.0.25 1 0 25. >> >> I don't know if these relate to the problem. >> >> I I used Audacity to convert one file to halfspeed which then played >> normally in GWC. GWC did an excellent jog de-clicking and de-noising the >> file, so if i could solve this playback problim I would be very happy. >> >> I'm running Ubuntu 14.04 on a Dell Inspiron Mini 10v. >> >> >> ------------------------------------------------------------------------------ >> Mobile security can be enabling, not merely restricting. Employees who >> bring their own devices (BYOD) to work are irked by the imposition of MDM >> restrictions. Mobile Device Manager Plus allows you to control only the >> apps on BYO-devices by containerizing them, leaving personal data >> untouched! >> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j >> _______________________________________________ >> Gwc-general mailing list >> Gwc...@li... >> https://lists.sourceforge.net/lists/listinfo/gwc-general >> >> |
From: Alister H. <ali...@gm...> - 2018-09-18 08:45:21
|
Hi, not sure how many people we still have here, but just a heads up for those who haven't already noticed: I released a new version last year with many bugfixes and removing the dependencies on old gnome libraries. I'm afraid I never got around to sorting out how to post to gwc-announce, and I see that some prominent distros have not updated - if you use one of these please tell your maintainer there is a new version available. At the time Jeff Welty indicated he hadn't used gwc for several years, so for now I'm "maintaining" the project - don't expect significant enhancements from me, but I'll be grateful for patches etc that others might produce. Also, note that I produced a package for OSX, if anyone wants to test on a Mac. One person reported playback issues, particularly that play needs to be clicked many times before it will work. I only have a virtual machine for testing, not a real Mac, but I'd be interested to know whether everyone has the playback issues. Thanks, Alister |
From: jeff w. <we...@to...> - 2018-04-28 21:33:45
|
hi Gwc https://bit.ly/2KmFHsP jeff welty |
From: Alister H. <ali...@gm...> - 2016-05-12 12:08:06
|
Hi Tom, GWC can be compiled to use either alsa, pulseaudio, or OSS. I'm guessing your GWC is compiled to use pulseaudio - is that right? I had the same problem when I tried it with pulseaudio, but I didn't have the motivation to pursue it further as I don't want pulseaudio anyway. Unfortunately there are also nasty problems when using the alsa support (at least one of which appears to be a regression of a very old bug) - I did spend quite a bit of time trying to work out how to debug these, but it was over my head. I can't remember if these issues have been reported in official channels, but II wrote about them for future reference at https://github.com/AlisterH/gwc/issues/1 and for now I am using the OSS support and aoss, so I'd suggest trying that if no one can help. Regards, Alister On 12/05/2016 2:14 AM, "tom" <tom...@gm...> wrote: > GWC is playing loaded wave files at or near twice the normal speed. When > launching from the command line I see the following warning messages: > > (process:3107): GLib-GObject-WARNING **: Attempt to add property > GnomeProgram::sm-connect after class was initialised > > (process:3107): GLib-GObject-WARNING **: Attempt to add property > GnomeProgram::show-crash-dialog after class was initialised > > (process:3107): GLib-GObject-WARNING **: Attempt to add property > GnomeProgram::display after class was initialised > > (process:3107): GLib-GObject-WARNING **: Attempt to add property > GnomeProgram::default-icon after class was initialised > libsndfile Version: libsndfile-1.0.25 1 0 25. > > I don't know if these relate to the problem. > > I I used Audacity to convert one file to halfspeed which then played > normally in GWC. GWC did an excellent jog de-clicking and de-noising the > file, so if i could solve this playback problim I would be very happy. > > I'm running Ubuntu 14.04 on a Dell Inspiron Mini 10v. > > > ------------------------------------------------------------------------------ > Mobile security can be enabling, not merely restricting. Employees who > bring their own devices (BYOD) to work are irked by the imposition of MDM > restrictions. Mobile Device Manager Plus allows you to control only the > apps on BYO-devices by containerizing them, leaving personal data > untouched! > https://ad.doubleclick.net/ddm/clk/304595813;131938128;j > _______________________________________________ > Gwc-general mailing list > Gwc...@li... > https://lists.sourceforge.net/lists/listinfo/gwc-general > > |
From: jeff w. <we...@ya...> - 2016-05-11 19:26:04
|
I don't have time to check into this specifically right now. I suspect the problem is your wav file has the wrong frequency in the header. So if the actual sample rate is 22.05 khz, but the wave header says it's a 44.1 khz sample rate, then GWC is going to play it at twice the speed that sounds correct. But if you are playing it with audacity and it sounds correct, it may be some other issue. I do seriously doubt it's a problem with GWC though. It would be the first ever and a lot of people have been using it for more than a decade. Hopefully that gives you an avenue to check for an issue. If it's not an incorrect header it'll take some digging to figure it out. I'll be out of town until May 30. There are others on the mail list that may have ideas too. Please give me a reminder email about how it turned out or if it's still a problem on May 30. Good luck!Jeff From: tom <tom...@gm...> To: gwc...@li... Sent: Wednesday, May 11, 2016 7:13 AM Subject: [Gwc-general] Playback speed problems GWC is playing loaded wave files at or near twice the normal speed. When launching from the command line I see the following warning messages: (process:3107): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised (process:3107): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised (process:3107): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised (process:3107): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised libsndfile Version: libsndfile-1.0.25 1 0 25. I don't know if these relate to the problem. I I used Audacity to convert one file to halfspeed which then played normally in GWC. GWC did an excellent jog de-clicking and de-noising the file, so if i could solve this playback problim I would be very happy. I'm running Ubuntu 14.04 on a Dell Inspiron Mini 10v. ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Gwc-general mailing list Gwc...@li... https://lists.sourceforge.net/lists/listinfo/gwc-general |
From: tom <tom...@gm...> - 2016-05-11 14:13:55
|
GWC is playing loaded wave files at or near twice the normal speed. When launching from the command line I see the following warning messages: (process:3107): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised (process:3107): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised (process:3107): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised (process:3107): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised libsndfile Version: libsndfile-1.0.25 1 0 25. I don't know if these relate to the problem. I I used Audacity to convert one file to halfspeed which then played normally in GWC. GWC did an excellent jog de-clicking and de-noising the file, so if i could solve this playback problim I would be very happy. I'm running Ubuntu 14.04 on a Dell Inspiron Mini 10v. |
From: jeff w. <we...@ya...> - 2014-09-26 22:19:36
|
Hi all, I just had a chance to take a brief look at the email chain. FWIW, I have never really used the encoding options in GWC. Although I understand the "coolness" factor, and understand the utility of the function, I think it is probably not something GWC should be doing -- you'll be forced to recompile gwc every time lame, or the oggenc options change. Alister, thanks for taking this on -- any time someone helps somebody else it's good! Also, FWIW, if I want to encode, I output a cdrdao.toc file, and have a perl script that reads that file and pushes the appropriate portions of the wavfile into lame with all the nifty track numbers, track names, artist info etc stored in mp3 tags. If someone was interested in making the perl script more "production", rather than the hack that it is, I'd be happy to share. I'll be out of email touch for a few days. Cheers,Jeff From: John Cirillo <jo...@in...> To: Alister Hood <ali...@gm...> Cc: gwc...@li... Sent: Thursday, September 25, 2014 11:01 PM Subject: Re: [Gwc-general] Encoding to MP3 problem, byte swapping occurs Hi Alister, I compiled the version called gwc-master that I downloaded from github. I confirmed that the filename is populated into the 'encode as' window now, both on regular mp3 and simple mp3. I think a little bug has slipped in however. The first few seconds of the song are cut off. It's not consistent and sometimes it is several seconds, other times less than that. This happens both in regular encode to mp3 and simple encode. I tried encoding with ogg as well and there is no cutoff- the entire song got encoded. I hate it when these kinds of problems sneak in. I hope you don't spend all day trying to find this unexpected thing. THanks, John On 09/26/2014 12:06 AM, Alister Hood wrote: > Yes: https://github.com/AlisterH/gwc > > > On 26/09/2014, John Cirillo <jo...@in...> wrote: >> On 09/25/2014 11:44 PM, Alister Hood wrote: >>> Hi John, >>> >>> On 26/09/2014, John Cirillo <jo...@in...> wrote: >>> ... >>>> I did try the git version of gwc 0.21-19 that Alister posted >>>> on Sept. 24, 2014, and it works. All of the above >>>> observations are based on the compile of that git version. >>>> It basically works fine, except that when using either of >>>> the encode to mp3 functions, there is no filename in the >>>> "encode to filename" box. It has to be manually typed. The >>>> stock version did pre-populate the filename as in previous >>>> versions, which I prefer. >>> Thanks for reporting that. I have actually fixed it in the meantime! >>> >>> >> Is it up on github already? I can try it. >> Would you mind re-posting the link? >> Thanks, >> John >> >> > ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Gwc-general mailing list Gwc...@li... https://lists.sourceforge.net/lists/listinfo/gwc-general |
From: John C. <jo...@in...> - 2014-09-26 06:01:45
|
Hi Alister, I compiled the version called gwc-master that I downloaded from github. I confirmed that the filename is populated into the 'encode as' window now, both on regular mp3 and simple mp3. I think a little bug has slipped in however. The first few seconds of the song are cut off. It's not consistent and sometimes it is several seconds, other times less than that. This happens both in regular encode to mp3 and simple encode. I tried encoding with ogg as well and there is no cutoff- the entire song got encoded. I hate it when these kinds of problems sneak in. I hope you don't spend all day trying to find this unexpected thing. THanks, John On 09/26/2014 12:06 AM, Alister Hood wrote: > Yes: https://github.com/AlisterH/gwc > > > On 26/09/2014, John Cirillo <jo...@in...> wrote: >> On 09/25/2014 11:44 PM, Alister Hood wrote: >>> Hi John, >>> >>> On 26/09/2014, John Cirillo <jo...@in...> wrote: >>> ... >>>> I did try the git version of gwc 0.21-19 that Alister posted >>>> on Sept. 24, 2014, and it works. All of the above >>>> observations are based on the compile of that git version. >>>> It basically works fine, except that when using either of >>>> the encode to mp3 functions, there is no filename in the >>>> "encode to filename" box. It has to be manually typed. The >>>> stock version did pre-populate the filename as in previous >>>> versions, which I prefer. >>> Thanks for reporting that. I have actually fixed it in the meantime! >>> >>> >> Is it up on github already? I can try it. >> Would you mind re-posting the link? >> Thanks, >> John >> >> > |
From: Alister H. <ali...@gm...> - 2014-09-26 04:06:25
|
Yes: https://github.com/AlisterH/gwc On 26/09/2014, John Cirillo <jo...@in...> wrote: > On 09/25/2014 11:44 PM, Alister Hood wrote: >> Hi John, >> >> On 26/09/2014, John Cirillo <jo...@in...> wrote: >> ... >>> I did try the git version of gwc 0.21-19 that Alister posted >>> on Sept. 24, 2014, and it works. All of the above >>> observations are based on the compile of that git version. >>> It basically works fine, except that when using either of >>> the encode to mp3 functions, there is no filename in the >>> "encode to filename" box. It has to be manually typed. The >>> stock version did pre-populate the filename as in previous >>> versions, which I prefer. >> Thanks for reporting that. I have actually fixed it in the meantime! >> >> > Is it up on github already? I can try it. > Would you mind re-posting the link? > Thanks, > John > > |
From: John C. <jo...@in...> - 2014-09-26 03:59:24
|
On 09/25/2014 11:44 PM, Alister Hood wrote: > Hi John, > > On 26/09/2014, John Cirillo <jo...@in...> wrote: > ... >> I did try the git version of gwc 0.21-19 that Alister posted >> on Sept. 24, 2014, and it works. All of the above >> observations are based on the compile of that git version. >> It basically works fine, except that when using either of >> the encode to mp3 functions, there is no filename in the >> "encode to filename" box. It has to be manually typed. The >> stock version did pre-populate the filename as in previous >> versions, which I prefer. > Thanks for reporting that. I have actually fixed it in the meantime! > > Is it up on github already? I can try it. Would you mind re-posting the link? Thanks, John |
From: Alister H. <ali...@gm...> - 2014-09-26 03:44:40
|
Hi John, On 26/09/2014, John Cirillo <jo...@in...> wrote: ... > I did try the git version of gwc 0.21-19 that Alister posted > on Sept. 24, 2014, and it works. All of the above > observations are based on the compile of that git version. > It basically works fine, except that when using either of > the encode to mp3 functions, there is no filename in the > "encode to filename" box. It has to be manually typed. The > stock version did pre-populate the filename as in previous > versions, which I prefer. Thanks for reporting that. I have actually fixed it in the meantime! |
From: John C. <jo...@in...> - 2014-09-26 03:22:38
|
Alister, I'm guessing that the lame encoding in gwc has had a problem for some time now. Don't know if it is a problem for everyone, but it is for every install I have done. I also remember seeing that hiss problem reported in a Debian bug report a while back. I don't think they knew what caused it or how to fix it so it is still broken in the pre-packaged gwc on the Debian repository. I just installed gwc 0.21.18 on a new install of Debian Jessie on my laptop and before adding your correction to encode.c, I had the same hiss on encoded mp3 files as on my other systems. Removing the -x byteswap switch corrected it. A long time ago, maybe 10 years, some program I was using had an extra line in the mp3 config menu where you could pass extra command line switches to lame. I don't remember what program it was, but that could be a solution for gwc in case someone needed a byteswap or some other extra feature. I really wish some other gwc users would chime in here and let us know if gwc encodes to mp3 properly for them, and what version of lame they are using. It may be that it's time to remove the -x switch from the encoding process, or find an easy way for them to turn it on or off. I confirmed that when using the simple mp3 encode in gwc 0.21-19, the artist and track name entered on the track name dialog box end up in the id3 tag. I guess this would be useful for some people. I usually encode the file(s) and then use easytag to populate the id3 tags. There is a lot more info that I usually include, such as album name, year, composer, label, etc so it is not necessary for gwc to have this feature. I noticed I can just click cancel and it moves on to the encode process, but as mentioned before, it leaves a gray box on the screen and no progress dialog. I saw the settings you mentioned in the simple mp3 settings menu where one could put the artist and track name, but they aren't working yet... Not sure if this is an efficient place to put that info, especially if it persists into the next session. For me, no id3 tag stuff is needed at all. When I click on encode, it should pick up the name of the loaded wav file and change the suffix to mp3 or ogg, and I can tweak the name in the encode as dialog box if needed. I realized after I posted last night that there's no way that the sound card could be related to the byte swapping, since everything we're doing here is in software. The sound card merely plays the result. So everyone, please ignore my mention of the sound card. It has nothing to do with how lame encodes the wav file. I did try the git version of gwc 0.21-19 that Alister posted on Sept. 24, 2014, and it works. All of the above observations are based on the compile of that git version. It basically works fine, except that when using either of the encode to mp3 functions, there is no filename in the "encode to filename" box. It has to be manually typed. The stock version did pre-populate the filename as in previous versions, which I prefer. I haven't tried all of the encode possibilities, but for me the extra new track name dialog box is not what I wanted. Others may like it. Regards, John On 09/25/2014 03:44 AM, Alister Hood wrote: > Hi again, > > > John Cirillo wrote, On 25/09/14 15:40: >> Alister, >> >> Thanks for the patches. I tried the first one on my >> present home install of 0.21-11 (still using the old lame >> 3.97) and confirmed that now the mp3 files become >> byte-swapped. >> I installed the latest lame 3.99.5 and confirmed that the >> mp3 files are encoded correctly. This is a great relief, >> now I no longer have to keep using that old lame version. >> I'm not sure exactly why this byte swap code was added, >> but it might have been to correct something in the older >> lame versions. I do remember that everything worked fine >> until lame got upgraded to 3.98. I seem to remember that >> some changes were made to the syntax of the command line >> options starting with lame 3.98, so maybe that had >> something to do with it. > There is this in the LAME changelog, although x86 > processors are little endian, so it seems unlikely to me > that this is the change (not that I know anything...): > > > LAME 3.98 beta 8 April 13 2008 > > * > o ... > o fix for some endianess problem on big-endian machines > >> But it's still odd that no one else has complained about >> the hiss noise problem in these last five years or so. > I imagine it is due to these factors: > - Not many people use gwc regularly. > - A lot of them probably don't export because they process > an entire side of an LP in one go, and then use other > software to split it into tracks, because GWC isn't the > best tool for that. > - Some probably export only to ogg. > - Some probably found that this feature was broken, but > didn't report it (notice the lack of reports in the last > 19 months about the export feature freezing gwc!). > - Some probably followed the workaround you posted and > installed an older LAME. > :) >> Does that mean that on some systems gwc and the new lame >> manage to produce a correct mp3 anyway? > Good question. >> I wonder if it's sound card related. I don't have time >> to experiment with this too much but I know my home and >> work machines both use an Ensoniq ES1371. So if the >> problem is not present for most users, it would not be >> prudent to remove that byte swap code in the main gwc >> distribution. More needs to be learned about what's >> happening. I'm on an i386 architecture so I don't have >> native byte swapping, so that's not it. Hmm... >> >> I went ahead and made the three changes you recommend in >> 0.21-19 and so far so good. It didn't freeze up on me >> and encoded a usable mp3 file. >> There is something new in 0.21-19 that I'm not sure I >> understand. After I get the "encode to filename" dialog >> and click OK, I get another box that says to enter the >> track name. I didn't know what to put so I just put the >> number 1 and it took it, but the box didn't completely >> clear and there is no encoding progress bar. >> I don't know what it did with that track name? It didn't >> end up in the id3 tag info. > Good spotting. If you use the "Simple encode selection as > mp3" it ends up in the id3 tag. I hadn't got around to > comparing the "old" and "new" encode functions yet to look > for any other differences like this - I'll do so now. > If you're building and using your own copy of gwc anyway, > would you mind using my version on github, instead of just > this patch? I believe it is less buggy, but testing is > good! BTW I haven't had a chance to attempt the last > changes needed to finish porting to plain gtk, but > hopefully I will soon. >> Thanks again, I'm now using the latest lame with no issues. >> >> John > > Thanks, > Alister |
From: Alister H. <ali...@gm...> - 2014-09-25 10:08:52
|
Alister Hood wrote, On 25/09/14 19:44: > Hi again, > > > John Cirillo wrote, On 25/09/14 15:40: >> ... >> There is something new in 0.21-19 that I'm not sure I understand. >> After I get the "encode to filename" dialog and click OK, I get >> another box that says to enter the track name. I didn't know what to >> put so I just put the number 1 and it took it, but the box didn't >> completely clear and there is no encoding progress bar. >> I don't know what it did with that track name? It didn't end up in >> the id3 tag info. > Good spotting. If you use the "Simple encode selection as mp3" it > ends up in the id3 tag. I hadn't got around to comparing the "old" > and "new" encode functions yet to look for any other differences like > this - I'll do so now. > If you're building and using your own copy of gwc anyway, would you > mind using my version on github, instead of just this patch? I believe > it is less buggy, but testing is good! BTW I haven't had a chance to > attempt the last changes needed to finish porting to plain gtk, but > hopefully I will soon. It turns out that the track name was simply unimplemented for "Save selection as..." (not surprisingly, given that "Save selection as..." wasn't working at all in 0.21-19). It was an easy fix though. But I found the fix for "Save selection as..." using the "new" start_encode() function is also easy - it just needed this line copied into the right place where the mp3 and ogg options are set: options[optcnt] = pipe_name ; /* named pipe */ |
From: Alister H. <ali...@gm...> - 2014-09-25 07:44:42
|
Hi again, John Cirillo wrote, On 25/09/14 15:40: > Alister, > > Thanks for the patches. I tried the first one on my present home > install of 0.21-11 (still using the old lame 3.97) and confirmed that > now the mp3 files become byte-swapped. > I installed the latest lame 3.99.5 and confirmed that the mp3 files > are encoded correctly. This is a great relief, now I no longer have > to keep using that old lame version. > I'm not sure exactly why this byte swap code was added, but it might > have been to correct something in the older lame versions. I do > remember that everything worked fine until lame got upgraded to 3.98. > I seem to remember that some changes were made to the syntax of the > command line options starting with lame 3.98, so maybe that had > something to do with it. There is this in the LAME changelog, although x86 processors are little endian, so it seems unlikely to me that this is the change (not that I know anything...): LAME 3.98 beta 8 April 13 2008 * o ... o fix for some endianess problem on big-endian machines > But it's still odd that no one else has complained about the hiss > noise problem in these last five years or so. I imagine it is due to these factors: - Not many people use gwc regularly. - A lot of them probably don't export because they process an entire side of an LP in one go, and then use other software to split it into tracks, because GWC isn't the best tool for that. - Some probably export only to ogg. - Some probably found that this feature was broken, but didn't report it (notice the lack of reports in the last 19 months about the export feature freezing gwc!). - Some probably followed the workaround you posted and installed an older LAME. :) > Does that mean that on some systems gwc and the new lame manage to > produce a correct mp3 anyway? Good question. > I wonder if it's sound card related. I don't have time to experiment > with this too much but I know my home and work machines both use an > Ensoniq ES1371. So if the problem is not present for most users, it > would not be prudent to remove that byte swap code in the main gwc > distribution. More needs to be learned about what's happening. I'm on > an i386 architecture so I don't have native byte swapping, so that's > not it. Hmm... > > I went ahead and made the three changes you recommend in 0.21-19 and > so far so good. It didn't freeze up on me and encoded a usable mp3 file. > There is something new in 0.21-19 that I'm not sure I understand. > After I get the "encode to filename" dialog and click OK, I get > another box that says to enter the track name. I didn't know what to > put so I just put the number 1 and it took it, but the box didn't > completely clear and there is no encoding progress bar. > I don't know what it did with that track name? It didn't end up in > the id3 tag info. Good spotting. If you use the "Simple encode selection as mp3" it ends up in the id3 tag. I hadn't got around to comparing the "old" and "new" encode functions yet to look for any other differences like this - I'll do so now. If you're building and using your own copy of gwc anyway, would you mind using my version on github, instead of just this patch? I believe it is less buggy, but testing is good! BTW I haven't had a chance to attempt the last changes needed to finish porting to plain gtk, but hopefully I will soon. > Thanks again, I'm now using the latest lame with no issues. > > John Thanks, Alister |
From: John C. <jo...@in...> - 2014-09-25 03:40:36
|
Alister, Thanks for the patches. I tried the first one on my present home install of 0.21-11 (still using the old lame 3.97) and confirmed that now the mp3 files become byte-swapped. I installed the latest lame 3.99.5 and confirmed that the mp3 files are encoded correctly. This is a great relief, now I no longer have to keep using that old lame version. I'm not sure exactly why this byte swap code was added, but it might have been to correct something in the older lame versions. I do remember that everything worked fine until lame got upgraded to 3.98. I seem to remember that some changes were made to the syntax of the command line options starting with lame 3.98, so maybe that had something to do with it. But it's still odd that no one else has complained about the hiss noise problem in these last five years or so. Does that mean that on some systems gwc and the new lame manage to produce a correct mp3 anyway? I wonder if it's sound card related. I don't have time to experiment with this too much but I know my home and work machines both use an Ensoniq ES1371. So if the problem is not present for most users, it would not be prudent to remove that byte swap code in the main gwc distribution. More needs to be learned about what's happening. I'm on an i386 architecture so I don't have native byte swapping, so that's not it. Hmm... I went ahead and made the three changes you recommend in 0.21-19 and so far so good. It didn't freeze up on me and encoded a usable mp3 file. There is something new in 0.21-19 that I'm not sure I understand. After I get the "encode to filename" dialog and click OK, I get another box that says to enter the track name. I didn't know what to put so I just put the number 1 and it took it, but the box didn't completely clear and there is no encoding progress bar. I don't know what it did with that track name? It didn't end up in the id3 tag info. Thanks again, I'm now using the latest lame with no issues. John On 09/24/2014 08:39 PM, Alister Hood wrote: > OK, > (1) if you want a fixed build of a version which is > producing static, you can just rebuild after deleting this > from encode.c: > > optcnt++; > > options[optcnt] = "-x"; /* Swap bytes */ > > But I guess this option must have been added because > someone actually needed it... I wonder if it is machine > specific and can be tested for at compile time, or if it > is audio file specific? > > (2) in 0.21-19 if you rename the start_encode_old() > function to start_encode(), and rename the start_encode() > function to start_encode_new_disabled(), then "Encode > Selection As..." will work. > But again, based on the changelog I guess the new function > must be needed on some systems: > > > GWC Changelog > > 0.21-19 > > ... > > BUGFIX: Encoding to ogg or mp3 has always been broken, > can only encode to once during GWC session. Fixed by > using named pipe > > The "old" function works fine on my system - I can encode > more than once during a GWC session. For the "Simple > encode..." feature to still work with it I also had to > remove this line: > > options[optcnt] = pipe_name ; /* named pipe */ > > These changes and also a fix for "Simple encode..."ing > mono files are in my git version: > https://github.com/AlisterH/gwc/commit/47f7397e6ab6971aed348494b6a5afcd3001d990 > > Regards, > Alister > > Alister Hood wrote, On 24/09/14 12:01: >> Hi John, >> >> I've found the current version of gwc (I'm not sure about >> old ones) freezes if I try to "Encode Selection As..." >> mp3 or ogg, but "Simple encode selection as mp3" works fine. >> FWIW I currently have lame 3.99.5 >> >> John Cirillo wrote, On 24/09/14 03:47: >>> I just installed gwc on my work computer and when I go >>> to encode to mp3, I see a message in the command line that: >>> Assuming raw pcm input file : Forcing byte-swapping >>> As a result the mp3 is garbage, just a loud hiss. >>> I remember that this started happening long ago at home, >>> and has persisted ever since then, persisting through >>> complete reinstalls. It is not dependent on the version >>> of gwc. >>> I am currently at 0.21.18 at work because 0.21.19 >>> freezes when I try to save anything. >>> At home I think I'm using 0.21.05. >>> I seem to remember having reported this problem before, >>> and so far the only solution has been to uninstall lame >>> and force an install of lame 3.97 which I kept from my >>> old Squeeze install (or before). >>> The newer lames work fine when encoding a .wav from >>> command line but from gwc this byte-swapping happens. >>> Is there something I can do, maybe something I can set >>> in gwc? >>> I can't believe I'm the only one who has encountered >>> this. Happens consistently on three computers (work, >>> home, and laptop). I think it started happening on or >>> after Squeeze. I've gone through Wheezy and now at >>> Jessie with the same problem. Installing lame 3.97 >>> seems the only solution. I don't understand. >>> >>> Thanks, >>> John Cirillo > |
From: Alister H. <ali...@gm...> - 2014-09-25 00:39:36
|
OK, (1) if you want a fixed build of a version which is producing static, you can just rebuild after deleting this from encode.c: optcnt++; options[optcnt] = "-x"; /* Swap bytes */ But I guess this option must have been added because someone actually needed it... I wonder if it is machine specific and can be tested for at compile time, or if it is audio file specific? (2) in 0.21-19 if you rename the start_encode_old() function to start_encode(), and rename the start_encode() function to start_encode_new_disabled(), then "Encode Selection As..." will work. But again, based on the changelog I guess the new function must be needed on some systems: > GWC Changelog > 0.21-19 > ... > BUGFIX: Encoding to ogg or mp3 has always been broken, can only encode to once during GWC session. Fixed by using named pipe The "old" function works fine on my system - I can encode more than once during a GWC session. For the "Simple encode..." feature to still work with it I also had to remove this line: options[optcnt] = pipe_name ; /* named pipe */ These changes and also a fix for "Simple encode..."ing mono files are in my git version: https://github.com/AlisterH/gwc/commit/47f7397e6ab6971aed348494b6a5afcd3001d990 Regards, Alister Alister Hood wrote, On 24/09/14 12:01: > Hi John, > > I've found the current version of gwc (I'm not sure about old ones) > freezes if I try to "Encode Selection As..." mp3 or ogg, but "Simple > encode selection as mp3" works fine. > FWIW I currently have lame 3.99.5 > > John Cirillo wrote, On 24/09/14 03:47: >> I just installed gwc on my work computer and when I go to encode to >> mp3, I see a message in the command line that: >> Assuming raw pcm input file : Forcing byte-swapping >> As a result the mp3 is garbage, just a loud hiss. >> I remember that this started happening long ago at home, and has >> persisted ever since then, persisting through complete reinstalls. >> It is not dependent on the version of gwc. >> I am currently at 0.21.18 at work because 0.21.19 freezes when I try >> to save anything. >> At home I think I'm using 0.21.05. >> I seem to remember having reported this problem before, and so far >> the only solution has been to uninstall lame and force an install of >> lame 3.97 which I kept from my old Squeeze install (or before). >> The newer lames work fine when encoding a .wav from command line but >> from gwc this byte-swapping happens. >> Is there something I can do, maybe something I can set in gwc? >> I can't believe I'm the only one who has encountered this. Happens >> consistently on three computers (work, home, and laptop). I think it >> started happening on or after Squeeze. I've gone through Wheezy and >> now at Jessie with the same problem. Installing lame 3.97 seems the >> only solution. I don't understand. >> >> Thanks, >> John Cirillo |