Error Parsing Data, Invalid Exit

[arciisine]

Error Parsing Data, Invalid Exit

[pilotkid]

@arciisine I'm so sorry I left town for a few weeks and cannot test at the moment. Wednesday I should be in a town with more than 1 bar of 3g where I can login to my home rig and test it.

[pilotkid]

Absolutely Sincerely, Marcello Bachechi

…

On Mon, Jun 14, 2021 at 3:10 PM Timothy Soehnlin ***@***.***> wrote: Thanks for the feedback. I see two issues, primarily around scale, and escaping of spaces in folder names. The first issue will need to be handled in https://github.com/arciisine/win-info and https://github.com/arciisine/screen-recorder respectively. It will take me a few days to get this figured out. @pilotkid <https://github.com/pilotkid> Are you up for running some dev builds if I have any issues tracking down the problem? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQW5BLWW5BMCA34ARBVBDDTSZV3RANCNFSM46V6HWMQ> .

[arciisine]

Thanks for the feedback. I see two issues, primarily around scale, and escaping of spaces in folder names. The first issue will need to be handled in https://github.com/arciisine/win-info and https://github.com/arciisine/screen-recorder respectively. It will take me a few days to get this figured out.

@pilotkid Are you up for running some dev builds if I have any issues tracking down the problem?

[ws1088]

I got the same error. I am using Linux. How do I enter dev mode to help give me debug information?

[pilotkid]

1. Open your extensions folder 2. Open the extension in code 3. Start the debugger

On Sat, Jun 19, 2021 at 12:33 PM ws1088 ***@***.***> wrote: I got the same error. I am using Linux. How do I enter dev mode to help give me debug information? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQW5BPY73EGFVR5LRHVW4LTTTBFDANCNFSM46V6HWMQ> .

-- Sincerely, Marcello Bachechi

[arciisine]

I'm wondeirng if something has changed recently, as this seems like a lot of activity. I will have some time tomorrow and will get a build out then. I will just reply to this thread @pilotkid when the build is ready.

[arciisine]

@pilotkid
chronicler-0.1.12.zip

You will need to rename the extension to .vsix (github won't allow for vsix uploads) and then use the vscode command to manually install the vsix.

I believe I fixed both the win32 issues (spaces in filenames, and bad scale calculation).

[arciisine]

@pilotkid I actually delpoyed this version as it solved another ongoing bug. You should be able to just update this within vscodee now and verify the functionality.

[ws1088]

i am not as lucky. i install 0.1.12 on both linux and windows and both do not work. still "Error parsing data"

[arciisine]

@ws1088 Are you able to run a few debugging commands:
npx @arcsine/win-info and npx @arcsine/screen-recorder test.mp4? The output from these commands should help pinpoint where the issue is.

[pilotkid]

No luck. I am still getting an error.

"C:\Program Files (x86)\ffmpeg\bin\ffmpeg.exe" -threads 4 -r 10 -video_size 1920x1040 -offset_x 1372 -offset_y -1080 -f gdigrab -i desktop -preset ultrafast -crf 10 -pix_fmt yuvj444p -c:v libx264 -y  
C:\Developer\vscode-1625010034126.mp4
c:\Users\Marcello Bachechi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork.js:5
'""C:\Program' is not recognized as an internal or external command,
operable program or batch file.
node_modules/@arcsine/screen-recorder/lib/util.js:12
Invalid exit status: 1
c:\Users\Marcello Bachechi\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork.js:5

[arciisine]

@pilotkid Thanks for the response, can you run:
npx @arcsine/win-info and npx @arcsine/screen-recorder test.mp4 and post the output. The issue above about not handling spaces in the executable name was fixed. Also, can you verify what version of the plugin you are running?

[pilotkid]

Here you go!

{
  "title": "npm exec @arcsine/win-info",
  "id": 4656072,
  "owner": {
    "name": "powershell.exe",
    "processId": 13836,
    "path": "C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
  },
  "screens": [
    {
      "x": 0,
      "y": 0,
      "width": 2560,
      "height": 1400,
      "index": 0,
      "scale": {
        "x": 1,
        "y": 1
      }
    }
  ],
  "bounds": {
    "x": 2,
    "y": 31,
    "width": 2556,
    "height": 1396
  }
}

npx @arcsine/screen-recorder test.mp4
C:\Program Files (x86)\ffmpeg\bin\ffmpeg.exe -f dshow -list_devices true -i dummy
Invalid exit status: 1
C:\Program Files (x86)\ffmpeg\bin\ffmpeg.exe -threads 4 -video_size 1920x1040 -offset_x 1372 -offset_y -1080 -f gdigrab -i desktop -preset ultrafast -crf 10 -pix_fmt yuvj444p -c:v libx264 -y  test.mp4
Recording for 5 seconds...
ffmpeg version git-2020-08-31-4a11a6f Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 10.2.1 (GCC) 20200805
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libgsm --enable-librav1e --enable-libsvtav1 --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
libavutil      56. 58.100 / 56. 58.100
  libavcodec     58.101.101 / 58.101.101
  libavformat    58. 51.101 / 58. 51.101
  libavdevice    58. 11.101 / 58. 11.101
  libavfilter     7. 87.100 /  7. 87.100
  libswscale      5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc    55.  8.100 / 55.  8.100
[gdigrab @ 000002967478fe80] Capturing whole desktop as 1920x1040x32 at (1372,-1080)
[gdigrab @ 000002967478fe80] Stream #0: not enough frames to estimate rate; consider increasing probesize
Input #0, gdigrab, from 'desktop':
  Duration: N/A, start: 1625509770.897973, bitrate:
1915025 kb/s
    Stream #0:0: Video: bmp, bgra, 1920x1040, 1915025 kb/s, 29.97 fps, 1000k tbr, 1000k tbn, 1000k tbc
Stream mapping:
  Stream #0:0 -> #0:0 (bmp (native) -> h264 (libx264))
Press [q] to stop, [?] for help
[swscaler @ 00000296747e1540] deprecated pixel format used, make sure you did set range correctly
[libx264 @ 0000029674794700] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[libx264 @ 0000029674794700] profile High 4:4:4 Predictive, level 4.0, 4:4:4, 8-bit
[libx264 @ 0000029674794700] 264 - core 161 - H.264/MPEG-4 AVC codec - Copyleft 2003-2020 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=6 threads=24 lookahead_threads=4 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=10.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0
Output #0, mp4, to 'test.mp4':
  Metadata:
    encoder         : Lavf58.51.101
    Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuvj444p(pc), 1920x1040, q=-1--1, 29.97 fps, 30k tbn, 29.97 tbc
    Metadata:
      encoder         : Lavc58.101.101 libx264
    Side data:
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
frame=   17 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A dup=3 drop=0 speed=   0x
frame=   32 fps= 32 q=0.0 size=    1280kB time=00:00:00.20 bitrate=52369.7kbits/s dup=4 drop=0 speed=0.199x```

[arciisine]

@pilotkid Thanks for the response. This looks correct, and it looks like its producing the expected output (with the fixes I put in place). This leads me to believe you are on an outdated version of the plugin. Can you verify the version of the vscode plugin you are using, and share any relevant configuration from the workspace settings?

[pilotkid]

Sure thing. I am using 0.1.12. Can you tell me what would be relevant settings besides what I have attached?

Also just a heads up the image is broken on the listing:

[arciisine]

I'm looking at your original error, and I saw '""C:\Program' in the error message. Can you try removing the quotes (") from your ffmpeg-binary location. That may be interfering with the command line being built.

[pilotkid]

...

It worked.

Thank you for all of your help.

[arciisine]

Awesome, glad to hear!