Recherche avancée

Sur d’autres sites (5436)

• Started Programming Young

  6 septembre 2011, par Multimedia Mike — Programming

  I have some of the strangest memories of my struggles to jump into computer programming.

  Back To BASIC
  I remember doing some Logo programming on Apple II computers at school in 5th grade (1987 timeframe). But that was mostly driving turtle graphics. Then I remember doing some TRS-80 BASIC in 7th grade, circa 1989. Emboldened by what very little I had learned in perhaps the week or 2 we took in a science class to do this, I tried a little GW-BASIC on my family’s “IBM-PC compatible” computer (they were still called that back then). I still remember what my first program consisted of. Even back then I was interested in manipulating graphics and color on a computer screen. Thus :

  10 color 1
  20 print "This is color 1"
  30 color 2
  40 print "This is color 2"
  ...
  

  And so on through 15 colors. Hey, it did the job– it demonstrated the 15 different colors you could set in text mode.

  What’s FOR For ?
  That 7th grade computer unit in science class wasn’t very thick on computer science details. I recall working with a lab partner to transcribe code listings into a computer (and also saving my work to a storage cassette). We also developed form processing programs that would print instructions to input text followed by an “INPUT I$” statement to obtain the user’s output.

  I remember there was some situation where we needed a brief delay between input and printing. The teacher told us to use a construct of the form :

  10 FOR I = 1 TO 20000
  20 NEXT I
  

  We had to calibrate the number based on our empirical assessment of how long it lasted but I recall that the number couldn’t be much higher than about 32000, for reasons that would become clearer much later.

  Imagine my confusion when I would read and try to comprehend BASIC program code I would find in magazines. I would of course see that FOR..NEXT construct all over the place but obviously not in the context of introducing deliberate execution delays. Indeed, my understanding of one of the fundamental building blocks of computer programming — iteration — was completely skewed because of this early lesson.

  Refactoring
  Somewhere along the line, I figured out that the FOR..NEXT could be used to do the same thing a bunch of times, possibly with different values. A few years after I had written that color program, I found it again and realized that I could write it as :

  10 for I = 1 to 15
  20 color I
  30 print I
  40 next I
  

  It still took me a few more years to sort out the meaning of WHILE..WEND, though.

• Node.js Child Process Issue with Args - Quotes Issue ?, FFMPEG issue ?

  7 septembre 2012, par Brad

  I need to be able to execute FFMPEG from my Node.js application. I believe this problem likely has to do with properly specifying command line arguments, and not specific to FFMPEG, but as I have been unable to narrow down the issue, I present my entire problem.

  I can execute the following command from the command prompt successfully :

  C:\Brad\ffmpeg.exe -f dshow -i audio="Microphone (SoundMAX Integrated" testaaa.mp3

  FFMPEG starts as expected, records audio from my audio device, and writes an MP3 file. Now, I try to do the same thing within my Node.js application :

  childProcess = child_process.spawn('C:\\Brad\\ffmpeg.exe', ['-f', 'dshow', '-i', 'audio="Microphone (SoundMAX Integrated"', 'testaaa.mp3']);
  
  childProcess.stderr.on('data', function (data) {
  
      console.log('StdioSource received data from STDERR: ' + data);
  
  });

  From within Node.js, FFMPEG fails ! The error is simply :

  [dshow @ 0000000001eded80] Could not find audio device.
  
  audio="Microphone (SoundMAX Integrated": Input/output error

  Thinking that maybe for some reason this was a weird permissions error, I decided to run FFMPEG with -list_devices true from within my Node application, and sure enough, the device in question is listed :

  [dshow @ 000000000228ecc0] DirectShow video devices
  
  [dshow @ 000000000228ecc0] Could not enumerate video devices.
  
  [dshow @ 000000000228ecc0] DirectShow audio devices
  
  [dshow @ 000000000228ecc0]  "Microphone (SoundMAX Integrated"

  Any thoughts as to why I cannot properly specify the audio input device in the arguments for FFMPEG, or why FFMPEG does not recognize my audio input device when running as a child process to Node.js ?

  Any hints would be most appreciated.

• Node.js Child Process Issue with Args - Quotes Issue ?, FFMPEG issue ?

  25 septembre 2017, par Brad

  I need to be able to execute FFMPEG from my Node.js application. I believe this problem likely has to do with properly specifying command line arguments, and not specific to FFMPEG, but as I have been unable to narrow down the issue, I present my entire problem.

  I can execute the following command from the command prompt successfully :

  C:\Brad\ffmpeg.exe -f dshow -i audio="Microphone (SoundMAX Integrated" testaaa.mp3

  FFMPEG starts as expected, records audio from my audio device, and writes an MP3 file. Now, I try to do the same thing within my Node.js application :

  childProcess = child_process.spawn('C:\\Brad\\ffmpeg.exe', ['-f', 'dshow', '-i', 'audio="Microphone (SoundMAX Integrated"', 'testaaa.mp3']);
  
  childProcess.stderr.on('data', function (data) {
  
      console.log('StdioSource received data from STDERR: ' + data);
  
  });

  From within Node.js, FFMPEG fails ! The error is simply :

  [dshow @ 0000000001eded80] Could not find audio device.
  
  audio="Microphone (SoundMAX Integrated": Input/output error

  Thinking that maybe for some reason this was a weird permissions error, I decided to run FFMPEG with -list_devices true from within my Node application, and sure enough, the device in question is listed :

  [dshow @ 000000000228ecc0] DirectShow video devices
  
  [dshow @ 000000000228ecc0] Could not enumerate video devices.
  
  [dshow @ 000000000228ecc0] DirectShow audio devices
  
  [dshow @ 000000000228ecc0]  "Microphone (SoundMAX Integrated"

  Any thoughts as to why I cannot properly specify the audio input device in the arguments for FFMPEG, or why FFMPEG does not recognize my audio input device when running as a child process to Node.js ?

  Any hints would be most appreciated.