You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Possible new approach: use contextBridge (window.electronApi) to provide an alternate api so that the backend can talk "directly" with ffmpeg without using an express server. See discussion here https://signlanguaget-nfl9249.slack.com/archives/C05GD89Q13K/p1718242466793769]
Although users who simply use latest version of sltt-app should not encounter this error, it could happen if they also try to launch their old compressor installation that's also set to port 29678. So it's probably best to configure a different compressor port for sltt-app so it won't conflict even if they launch that one. It will also help reduce confusion of state issue if they are using the web app and sltt-app and performing compressor functions in both.
Suggestions:
In compressor\src\config.js
configure sltt-app compressor port at 29679 (i.e. 29678 + 1)
configure new /resources temp folder path (e.g. %TEMP%/sltt-app/compression-server/resources/ffmpeg-x64.exe) separate from sltt pwa temp folder (%TEMP%/compression-server/resources/ffmpeg-x64.exe) to allow for separate ffmpeg upgrade
configure new /videos temp folder based on a directory associated with the browser window that is using it (e.g. %TEMP%/sltt-app/compression-server/window-{id}/videos/ffmpeg-x64.exe) separate from sltt pwa temp folder (%TEMP%/compression-server/videos) to allow for multiple windows to do separate ffmpeg video functions
The text was updated successfully, but these errors were encountered:
[Possible new approach: use contextBridge (window.electronApi) to provide an alternate api so that the backend can talk "directly" with ffmpeg without using an express server. See discussion here https://signlanguaget-nfl9249.slack.com/archives/C05GD89Q13K/p1718242466793769]
Although users who simply use latest version of sltt-app should not encounter this error, it could happen if they also try to launch their old compressor installation that's also set to port 29678. So it's probably best to configure a different compressor port for sltt-app so it won't conflict even if they launch that one. It will also help reduce confusion of state issue if they are using the web app and sltt-app and performing compressor functions in both.
Suggestions:
In
compressor\src\config.js
29679
(i.e.29678
+1
)/resources
temp folder path (e.g.%TEMP%/sltt-app/compression-server/resources/ffmpeg-x64.exe
) separate from sltt pwa temp folder (%TEMP%/compression-server/resources/ffmpeg-x64.exe
) to allow for separate ffmpeg upgrade/videos
temp folder based on a directory associated with the browser window that is using it (e.g.%TEMP%/sltt-app/compression-server/window-{id}/videos/ffmpeg-x64.exe
) separate from sltt pwa temp folder (%TEMP%/compression-server/videos
) to allow for multiple windows to do separate ffmpeg video functionsThe text was updated successfully, but these errors were encountered: