search

staxrip / staxrip

🎞 Video encoding GUI for Windows.
MIT License
2.16k stars 121 forks source link

Project file not found #835

Open jobrien2001 opened 2 years ago

jobrien2001 commented 2 years ago

Describe the bug loading a job from jobs list produces pop up error "project file not found"

Expected behavior job should load

How to reproduce the issue

  1. add job to jobs queue
  2. Click on Job added
  3. Select job and Click Load

image

Dendraspis commented 2 years ago

Please check this setting: Settings » System » Delete Temp Files ...seems you have (accidentally) enabled this feature. If it is Disabled check if the project file is still there.

jobrien2001 commented 2 years ago

Please check this setting: Settings » System » Delete Temp Files ...seems you have (accidentally) enabled this feature. If it is Disabled check if the project file is still there.

Hello,

Its disabled, also the file is there in "C:\ProgramData\StaxRip\Batch Projects\E--to encode- x265 2000 - test.mkv.srip"

Weird thing is the queue works just fine... i just cant load any jobs form the list to edit them.

Dendraspis commented 2 years ago

Here is a version that also shows the path of the project, that cannot be found. Please verify, that the path is correct...

StaxRip-v2.10.15-DEV.zip

jobrien2001 commented 2 years ago

Hello,

Upon loading The box now says project not found and the file name with missing extension and no path to file.

Dendraspis commented 2 years ago

Can you make a screenshot of the Jobs window? I need to see the whole row, means the given name/path ... of course you can black out critical names, but please don't touch all \ of the path, if it is a path. Can you tell me how the job was created? Normal single file load or a batch loading?

jobrien2001 commented 2 years ago

This was batch loaded, only file name with missing path & extension:

image

image

I hadnt tried single file until now, i can report that single file loads fine and displays full path on job list:

image

By the way this is using your dev exe

So something is going on with batch mode?

Dendraspis commented 2 years ago

Great, now I have an idea where to look at. Let's see if I can fix it....

Dendraspis commented 2 years ago

I have checked the issue and it seems that we have to deal with it. File Batch is handled in a special way and touching it would mean to change a lot of stuff. If you wanna change a specific job, you have to start (and stop) it to generate the project file. Once it is created, you can load, modify and (re-)add it, but don't forget to delete/uncheck the File Batch Job.

Personally I prefer to load each source file on its own, by hand or by command line or Powershell command/script, but depending on the source files and expectations, I have to create a new (start up) template.

Maybe one day somebody will change it, but not at the moment.....

therealt3nzin commented 2 years ago

The workaround for this particular issue should be to remove and "space" characters in the filepath of Stax & the working files. I ran across this issue myself in my own workflow, this is likely related to a Windows issue where the system doesn't pass "space" characters through correctly and serves an invalid pathname. This is especially prevalent when the Windows username has a "space" character in it causing all kinds of errors in even Windows system apps.

The file paths noted in jobrien2001's issue C:\ProgramData\StaxRip\Batch Projects\E--to encode- x265 2000 - test.mkv.srip & E:\to encode\aaaaa_temp\aaaaa_new.srip should be renamed to something along the lines of:

Currently, when doing batch jobs, I create a template without loading any files from the batch and then open a second Stax window to load the first batch job file to check for errors and make tweaks to the job and then input those changes back into the first window before closing the second Stax window and lastly save the changes to the template in the first window. Then you can safely run the batch job without concern for error.

Dendraspis commented 2 years ago

The workaround for this particular issue should be to remove and "space" characters in the filepath of Stax & the working files. [..] this is likely related to a Windows issue where the system doesn't pass "space" characters through correctly and serves an invalid pathname.

The file paths noted in jobrien2001's issue [..] should be renamed to something along the lines of:

Just to clarify: The resulting filename of a batch project file is set to be identifiable and unique to prevent duplicates, nothing more. All paths are (correctly) written inside those files.