Hi Alan, Sounds like a portaudio/sound card issue.
Couple of ideas: 1/ Try using the readme.txt option to compile various libraries (in particular PortAudio) from source. 2/ Do you get tx audio when you use an 8kHz 16 bit int wavefile for the audio source using the Tools - Start/Stop Play file from Mic In 3/ Can you use the Fedora FreeDV packages (see freedv.org)? Cheers, David On 12/05/17 07:08, Alan Beard wrote: > Hi guys, > > I've just downloaded *http://files.freedv.org/freedv/freedv-1.2.tar.xz* > > on my Fedora 23 Linux box where FreeDV used to work until ~6 months ago. > Hil VK2IUW and I had some QSOs over 10Km on 6m. > > This is the only thing I did to get it compiling and thus working: > > grep 3.0 CMakeLists.txt > set(WXCONFIG "/usr/bin/wx-config-3.0" CACHE FILEPATH "Location of > wx-config binary.") > set(WXRC "/usr/bin/wxrc-3.0" CACHE FILEPATH "Location of wxrc binary.") > set(WX_VERSION_MIN 3.0.0) > > *My problem: > Transmit mic in.* Nothing on the "Level" bar-graph or the oscilloscope > screen. > > "Pulseaudio" from desktop "Settings" shows my mic is working. > > I can make an RDP session available for your testing though RDP on Linux > doesn't give mic and speaker. > > 80 'cause a 73 won't do nothing useful here. > > Alan VK2ZIW > > On Tue, 9 May 2017 06:56:37 +0930, David Rowe wrote >> Thanks Sebastien and everyone else for their comments and >> suggestions. At this stage I've simply disabled writing to the log >> file. Richard is building a new package for you all to try on Win >> 10/64 bit systems. >> >> - David >> >> On 08/05/17 20:51, Sebastien F4GRX wrote: >> > Hello, >> > >> > that should be GetUserProfileDirectory: >> > >> > > https://msdn.microsoft.com/en-us/library/windows/desktop/bb762280(v=vs.85).aspx > >> > >> > the hToken parameter probably can be provided by > GetCurrentProcessToken: >> > >> > > https://msdn.microsoft.com/en-us/library/windows/desktop/mt643211(v=vs.85).aspx > >> > >> > Another solution based on SDD (stackoverflow driven development) is >> > SHGetFolderPath: >> > >> > > http://stackoverflow.com/questions/9542611/how-to-get-the-current-users-home-directory-in-windows > >> > >> > Sebastien >> > >> > On 06/05/2017 22:40, David Rowe wrote: >> >> Thanks Mathew - I wonder if there is a Win32 system call to return > that >> >> path. As well as debug/log information there are also times when the >> >> program records wave files, but the user gets a dialog box to choose >> >> record file locations. >> >> >> >> - David >> >> >> >> On 07/05/17 02:58, Matthew Pitts wrote: >> >>> Richard and David, >> >>> >> >>> >> >>> Windows versions, if installed in C:\Program Files\ (or C:\Program >> >>> Files(x86) for 32 bit versions on 64 Bit OS)) should write any needed >> >>> data to the C:\Users\<uesrname>\AppData\Roaming\FreeDV\ folder. > This has >> >>> actually been the preferred method since Windows XP, but has only > been >> >>> enforced since Windows 8, from what I understand. Doing it this way >> >>> avoids the privilege escalation that occurs when running the > software as >> >>> Administrator, which is just as dangerous (if not more so) than > running >> >>> applications as root user on Linux. >> >>> >> >>> >> >>> Matthew Pitts >> >>> >> >>> N8OHU >> >>> >> >>> >> >>> On 5/6/2017 7:35 AM, Richard Shaw wrote: >> >>>> On Sat, May 6, 2017 at 12:20 AM, David Rowe <da...@rowetel.com >> >>>> <mailto:da...@rowetel.com>> wrote: >> >>>> >> >>>> OK so maybe I need to make sure FreeDV isn't writing any data >> >>>> files, or >> >>>> if it does write them, they should go to c:\ or some other temp >> >>>> directory. I think I am just writing a log file as a debug > feature >> >>>> anyway, so it can be disabled. >> >>>> >> >>>> >> >>>> It also seem like maybe we should install to a different program > files >> >>>> directory on 64bit systems? If we can determine where that is, > then I >> >>>> should be able to adjust the settings for the NSIS installer. >> >>>> >> >>>> Thanks, >> >>>> Richard >> >>>> KF5OIM >> >>>> >> >>>> >> >>>> > ------------------------------------------------------------------------------ > >> >>>> Check out the vibrant tech community on one of the world's most >> >>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> >>>> >> >>>> >> >>>> _______________________________________________ >> >>>> Freetel-codec2 mailing list >> >>>> Freetel-codec2@lists.sourceforge.net >> >>>> https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >> >>> >> >>> >> >>> >> >>> > ------------------------------------------------------------------------------ > >> >>> Check out the vibrant tech community on one of the world's most >> >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> >>> >> >>> >> >>> >> >>> _______________________________________________ >> >>> Freetel-codec2 mailing list >> >>> Freetel-codec2@lists.sourceforge.net >> >>> https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >> >>> >> >> >> >> > ------------------------------------------------------------------------------ > >> >> Check out the vibrant tech community on one of the world's most >> >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> >> _______________________________________________ >> >> Freetel-codec2 mailing list >> >> Freetel-codec2@lists.sourceforge.net >> >> https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >> >> >> > >> > > ------------------------------------------------------------------------------ > >> > Check out the vibrant tech community on one of the world's most >> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> > _______________________________________________ >> > Freetel-codec2 mailing list >> > Freetel-codec2@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >> > >> >> > ------------------------------------------------------------------------------ > >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Freetel-codec2 mailing list >> Freetel-codec2@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > > > Alan > > Evil flourishes when good men do nothing. > Consider the Christmas child. > --------------------------------------------------------------------------- > Alan Beard Unix Support Technician from 1984 to today > 70 Wedmore Rd. Sun Solaris, AIX, HP/UX, Linux, SCO, MIPS > Emu Heights N.S.W. 2750 Routers, terminal servers, printers, terminals > etc.. > +61 2 47353013 (h) Support Programming, shell scripting, "C", > assembler > 0414 353013 (mobile) After uni, electronics tech > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Freetel-codec2 mailing list > Freetel-codec2@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
