Include Speaker and Subject in CMD arguments
Sermon Recorder is a program for recording sermons or anything else.
Brought to you by:
manolo0815
Menu
▾
▴
#25 Include Speaker and Subject in CMD arguments
Hello,
I'm a happy SermonRecorder user but I have a doubt about the commandline execution feature.
It seems I can't pass Speaker (%S) and Subject (%T) as command line argument, which would be really confortable to perform decisions in the script based on those values.
For now I work-arounded this by extracting the information from the path of a "fake" WAV recording I delete in the script itself, but of course this isn't the best solution.
What about allowing to pass these values to che cmd?
Thanks!
For my understanding, these parameters were all available to be passed into the cmd. At least, that was working when I last tested it...
I'll check that again and let you know...
Hello Matthias,
thanks for your answer. In my tests, %S and %T don't seem to be accepted as command line parameters (it passes litterally "%S" and "%T" if I put them). In the help tooltip, only recorded file paths are in fact listed.
Thanks
In fact, this is currently not possible, but surely a reasonable feature!
I'll add all of the common parameters for the comand line call as well...
Stay tuned!
Will you try this 0.8.3.Release candidate?
Should be working now...
Last edit: Matthias 2018-12-20
Hello,
thanks for your rapid fix.
Unfortunately I can't run this version (see screenshots).
I tried to delete AppData\Local\SermonRecorder but I get the same result.
This happens only when I have my USB soundcard set as default in Windows. It runs normally if I detach the USB soundcard, or if I set the internal one as default in Windows settings. It the latter case, it also correctly detects the USB soundcard. This seems to be a regression, because I used the latest stable version with the USB card set as default, without any issue.
Thanks!
Last edit: AleRinaldi 2018-12-20
Some more info:
if I start the software with the main soundcard as Windows default, and then I select the secondary one from settings, I need to restart the software to apply the settings. After I restart it, I get the
Error: BASS_ERROR_ALREADYmessage. After that, by the way, the software runs and correctly uses the USB soundcard.For what concerns the original issues, it's fixed: the %S and %T parameters are correctly passed to CMD, and I see from the tooltip that there also are all the parameters I can use in the file name, which is awesome! So, if you prefer, I can move the regression to a new issue and close that one...
Thanks!
Really strange. First of all, I can't reproduce the problem with an additional USB Sound Card which I still have at hand. The combination of hipsets surely is not the same, but...
Anyway, I can start SR and change the inputs - no problem.
Thanks for the screenshots!
I think I know where the failue is issued, but I don't know why. Somehow, the failure message looks kind of distorted compared to what I usually see as failure message. The problem is that an object is referenced which is not pointing to an object or so? And why is this message in italian, if the rest of the program is running in english?
So, I neither have an idea why this is happening, nor what the error message really means!
The only thing that makes sense is that after such a failure, the failure reaction is not quite robust, which means that SR will be partially crashed. :-(
During the fix, I also updated to the newest bass dlls, maybe this makes any difference?
In order to exclude this, would you please help me? Attached, you find the dlls used in 0.8.2, which seemed to be working fine or your system. Would you please try to exchange the files one by one? Note: Please make backup copies instead of overwriting.
The most interesting one in this case is the bass.dll. However, it might be that the new bass.net.dll is not compatible with the old bass.dll or any of them.
So, please play around with these dlls. Maybe you find a configuration in which these failures don't appear any more?
The SermonRecorder.exe is also featured in the zip. You can also try to use this version. It should make more sure where the failure happens...
Dear AleRinaldi,
did you have a try with the files above or should I just release the new version with the possible bug you are experiencing?
Hello Matthias,
sorry for the late answer but I got access just today to the system I experience the issue on.
Sadly, the results aren't good: if I replace everything but bass.net.dll, I get the same behaviour (error on startup and accessing the config form). If I replace bass.net.dll the exe won't run, no matter what else I replace: the process just starts and stops after a few seconds without any message.
I fear I can't fix this issue in remote. :-/
Hi,
I can try to reproduce the issue on a PC I can give you access to, if you
are willing to try a remote debug
Last edit: AleRinaldi 2019-01-28
Sorry for the late answer.
After I found one of my coputers to have a very similar problem, I were in contact with the developer of the BASS library, which I am using.
To male a long story short, on my "bad" machine, it had to do with the setting "Windows - Settings - Data security settings - Microphone - "Allow apps to access the microphone". (Sorry for the bad german - english translation! :-)
Please check if that switch is set to on. Else, also SR is unable to access the mic.
for some reason, SR doesn't appear on the list below the switch. I don't know why.