 |
Hmmmm, a little bit of initial mystery -- maybe it was an unseen control character in the original filename. |
 |
Only re-opening to update on what happened with the static build. I tried re-running one of the original files and it did give me the file name and path of the file it couldn't read. The path and name was correct, so it should have worked. However, I decided to start clean and built a new batch render XML once again. I followed the same steps and the process worked. I tried on another system by copying all the assets and EDLs and it also worked there. I'm not sure why the originals didn't work at this point, but since it is working now, I have to assume there may have been something wrong with the original path or filename that I just couldn't see. Perhaps fallout of my first attempt just entering the file name with no full path to it. The bug can be closed. Thank you very much for your help. I had a very busy week last week and didn't have time to test until last night. |
|
|
Am marking as resolved until further information is available -- hoping that the fix for actually showing the filename with the problem may have provided enough to proceed. |
|
|
I've downloaded the static build and will experiment with it this week as time allows. Based on what you said about the full path, I am going to try more carefully building a new batch render XML. I will let you know what I find a little later in the week. Thank you for your fast response! |
|
|
I probably did not make the last note clear; in the case where I got an immediate failure, it was the filename of the XML file I typed in that ended up with the not found message. I did not get any error or warning when the filename inside of the XML was incorrect. A test static tar for Ubuntu 18 which has the bug fix in to replace "null" with the file name is at the following location: https://www.cinelerra-gg.org/download/testing/cinelerra-5.1-ub18-x86_64-static.txz Here is the README.txt to add it to your system: To use the single user builds, download the tarball and unpack as indicated: cd /path mkdir cin cd cin tar -xJf /src/path/cinelerra-5.1-*.txz # as shown in ./tars for distro |
|
|
When I tried one of your xml files, I forgot to put in the full path of where I had downloaded that file and got the error "EDL (null) not found". With the bug fix in on my laptop, I now get the error "EDL (ep11.xml) not found". We will create a static tar Ubuntu 18.04 test build tomorrow and let you know the location. BUT please check again that the path name is included with the file name. |
|
|
The Ep11-Ep15 XML files are the EDLs for a source video called Test.mkv. The 11-16.xml file is the batch render list. All files including Test.mkv live in my home directory: /home/deckard. I checked the XML files to see if they have any incorrect paths, but everything looked OK. Just as a test, I copied the files to another system that has the "Cinelerra 5.1 - built: Jan 30 2018 08:42:4" build on it. This system is an older Ubuntu 14.04 system. I still encountered the NULL error. As an experiment, I tried renaming the EDLs to all lower case and updating the paths in all the files. They loaded correctly on my older test system, but even with the case changed, the batch render still failed with the NULL error. I'm working as the user 'deckard' on both the current Ubuntu 18.04 system and my test Ubuntu 14.04 system, so owner:group and perm should not be an issue. If you don't see anything glaring in the XML files, I would be interested in testing a static build on my Ubuntu 18.04 system to see what the file name that is failing might be. Please let me know how to proceed. |
|
|
11-16.xml (11,324 bytes) ep11.xml (36,829 bytes) ep12.xml (36,828 bytes) ep13.xml (36,829 bytes) ep14.xml (36,829 bytes) ep15.xml (36,828 bytes) |
|
|
GG can not reproduce this error. In looking at the code the only way to get the "EDL (filename) not found" message is if the program is either unable to open or read the file. HOWEVER, he did find a bug where the "filename" should not be "NULL" but should be the user-supplied filename. If you would like him to build a test version for your distro -- he only builds static tars for testing - let us know which O/S distro and version number you use. This bug fix will NOT fix whatever problem you are having but it should identify which filename is causing the problem. After that if no solution found, if you upload the xml files which cause a problem we can test that here. |
|
|
I have not been able to duplicate YET, but will try tomorrow. |
- Anonymous
