Re: [Cin] Problem solved: change audio device
пт, 25 окт. 2024 г., 18:02 Bulhwi Cha <[email protected]>:
On Thu Oct 24, 2024 at 10:44 PM KST, Andrew Randrianasulu wrote:
so, there is no audio with output device set to ALSA, same if set to Pulseaudio ?
When ALSA is selected as the audio driver, I have to change the device from "default" to the one I want to use, e.g. U22 XT USB #0 or Sink #780 (my Bluetooth speaker). Then, I can hear the audio.
PulseAudio also works fine.
Glad to hear!
Also, what kind of build error you have?
/usr/bin/ld: cannot find -lx264: No such file or directory collect2: error: ld returned 1 exit status
try to install x264?
while I think there should be way to reuse x264 build in thirdparty directory ....
I've installed it, but now I have other issues related to NVIDIA CUDA. See the log I attached to this email.
Do you have cuda SDK installed? may be whole file disappeared in new version? find /usr -name helper_cuda.h or may be in /opt if cuda installs there .... I think you can edit plugins/Makefile and comment out (with #) this line CUDA_OBJS := mandelcuda nbodycuda or look for adding --without-cuda to your ./configure
On Sat Oct 26, 2024 at 12:34 AM KST, Andrew Randrianasulu wrote:
Do you have cuda SDK installed? may be whole file disappeared in new version?
find /usr -name helper_cuda.h
or may be in /opt if cuda installs there ....
The helper_cuda.h file appears to have to do with cuda-samples[0].
I think you can edit plugins/Makefile and comment out (with #) this line
CUDA_OBJS := mandelcuda nbodycuda
or look for adding --without-cuda to your ./configure
I followed your suggestion and successfully built Cinelerra-GG, but it failed to run. See the log file I attached to this email. [0] https://github.com/NVIDIA/cuda-samples
пн, 28 окт. 2024 г., 10:17 Bulhwi Cha <[email protected]>:
On Sat Oct 26, 2024 at 12:34 AM KST, Andrew Randrianasulu wrote:
Do you have cuda SDK installed? may be whole file disappeared in new version?
find /usr -name helper_cuda.h
or may be in /opt if cuda installs there ....
The helper_cuda.h file appears to have to do with cuda-samples[0].
I think you can edit plugins/Makefile and comment out (with #) this line
CUDA_OBJS := mandelcuda nbodycuda
or look for adding --without-cuda to your ./configure
I followed your suggestion and successfully built Cinelerra-GG, but it failed to run. See the log file I attached to this email.
interesting. sorry for asking again, but did you build with system ffmpeg or with our 7.0? can I see configure line? right now you seem to install cingg system-wide, I usually build --with-single-user first. you also can try to figure out why your ffmpeg build (if you use internal ffmpeg) pick up and enables dnn external libraries. hopefully after you disable this feature cin will start. Alternatively, you can try to add all those new and failing filters to ffmpeg/plugins.opts and rerun make install . (commented filter names started with #)
пн, 28 окт. 2024 г., 10:29 Andrew Randrianasulu <[email protected]>:
пн, 28 окт. 2024 г., 10:17 Bulhwi Cha <[email protected]>:
On Sat Oct 26, 2024 at 12:34 AM KST, Andrew Randrianasulu wrote:
Do you have cuda SDK installed? may be whole file disappeared in new version?
find /usr -name helper_cuda.h
or may be in /opt if cuda installs there ....
The helper_cuda.h file appears to have to do with cuda-samples[0].
I think you can edit plugins/Makefile and comment out (with #) this line
CUDA_OBJS := mandelcuda nbodycuda
or look for adding --without-cuda to your ./configure
I followed your suggestion and successfully built Cinelerra-GG, but it failed to run. See the log file I attached to this email.
interesting.
sorry for asking again, but did you build with system ffmpeg or with our 7.0?
can I see configure line?
right now you seem to install cingg system-wide, I usually build --with-single-user first.
you also can try to figure out why your ffmpeg build (if you use internal ffmpeg) pick up and enables dnn external libraries.
hopefully after you disable this feature cin will start.
Alternatively, you can try to add all those new and failing filters to ffmpeg/plugins.opts and rerun make install . (commented filter names started with #)
update: strange, for example dnn_* filters already in plugin.opts file, commented out. so may be make install failed for some reason ?
On Mon Oct 28, 2024 at 4:29 PM KST, Andrew Randrianasulu wrote:
interesting.
sorry for asking again, but did you build with system ffmpeg or with our 7.0?
I built it with FFmpeg 7.0 in the thirdparty directory.
can I see configure line?
right now you seem to install cingg system-wide, I usually build --with-single-user first.
I've just tried to build and run it but to no avail. ./autogen.sh ./configure --prefix=/usr/local --with-single-user make 2>&1 | tee log make install
you also can try to figure out why your ffmpeg build (if you use internal ffmpeg) pick up and enables dnn external libraries.
hopefully after you disable this feature cin will start.
Alternatively, you can try to add all those new and failing filters to ffmpeg/plugins.opts and rerun make install . (commented filter names started with #)
On Mon Oct 28, 2024 at 4:36 PM KST, Andrew Randrianasulu wrote:
update: strange, for example dnn_* filters already in plugin.opts file, commented out.
so may be make install failed for some reason ?
There was no error while running it. I'll use the AppImage instead! Thank you for helping me.
вт, 29 окт. 2024 г., 09:58 Bulhwi Cha <[email protected]>:
On Mon Oct 28, 2024 at 4:29 PM KST, Andrew Randrianasulu wrote:
interesting.
sorry for asking again, but did you build with system ffmpeg or with our 7.0?
I built it with FFmpeg 7.0 in the thirdparty directory.
can I see configure line?
right now you seem to install cingg system-wide, I usually build --with-single-user first.
I've just tried to build and run it but to no avail.
./autogen.sh ./configure --prefix=/usr/local --with-single-user make 2>&1 | tee log make install
I noticed in earlier attempt you build (apparently) for default system install yet launched cin from build directory ? may be launching cin instead of ./cin will improve things? Also, there is slackbuild somewhere in source tree ... I use custom modified slackbuild for patching things on the fly.
you also can try to figure out why your ffmpeg build (if you use internal ffmpeg) pick up and enables dnn external libraries.
hopefully after you disable this feature cin will start.
Alternatively, you can try to add all those new and failing filters to ffmpeg/plugins.opts and rerun make install . (commented filter names started with #)
On Mon Oct 28, 2024 at 4:36 PM KST, Andrew Randrianasulu wrote:
update: strange, for example dnn_* filters already in plugin.opts file, commented out.
so may be make install failed for some reason ?
There was no error while running it.
I'll use the AppImage instead! Thank you for helping me.
Well, as long as it works ....
On Tue Oct 29, 2024 at 4:11 PM KST, Andrew Randrianasulu wrote:
I noticed in earlier attempt you build (apparently) for default system install yet launched cin from build directory ?
may be launching cin instead of ./cin will improve things?
The result was the same.
Also, there is slackbuild somewhere in source tree ... I use custom modified slackbuild for patching things on the fly.
I'll try it next time I want to build Cinelerra-GG!
participants (2)
-
Andrew Randrianasulu -
Bulhwi Cha