Closed Dr-LKMJ closed 8 years ago
I'll look into it in the morning. I'll have to see if there's an issue with those specific names or something more general. At first glance, it looks like a configuration error. can you force a recheck on the torrent to see if the files were actually moved? If they have, you can safely delete the originals, otherwise, try to use FileBot history and click the revert button to make the torrent point to the originals.
Where we're the original files downloaded to?
They were moved and I was able to delete the originals without any problems...but I have almost a Terabyte of files waiting to be downloaded and hate to have to do this for the next 100 or 150 torrents...Originally the files were downloaded to D:\Downloads.
M.
Sent from my iPad
On Jul 21, 2016, at 3:11 AM, Jared Anderson notifications@github.com<mailto:notifications@github.com> wrote:
I'll look into it in the morning. I'll have to see if there's an issue with those specific names or something more general. At first glance, it looks like a configuration error. can you force a recheck on the torrent to see if the files were actually moved? If they have, you can safely delete the originals, otherwise, try to use FileBot history and click the revert button to make the torrent point to the originals.
Where we're the original files downloaded to?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3Agithub.com_Laharah_deluge-2DFileBotTool_issues_5-23issuecomment-2D234212660&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=YLAgp1qL3XnO8BL6s-0SP3W5KCO5TpLh6z1FU5nOBc8&s=et_iTkB5WvOIX0aKtcCF5F61NxDGmuU-uI0lFwOJoUU&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3Agithub.com_notifications_unsubscribe-2Dauth_ATn45d6cf7ApPhU2ZDwAqQfkcKiRC8xmks5qX0WygaJpZM4JRojy&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=YLAgp1qL3XnO8BL6s-0SP3W5KCO5TpLh6z1FU5nOBc8&s=E-Mb4ziW5knjNDz9zfF7N2AZ0TSm3mWBHc1a81xYjQM&e=.
Are all renames having this issue, or is this a one time occurrence?
I'd be great if the plugin had any options for enabling debug logging so we can see the filebot command and the console output.
It actually does log those things to the deluge logs, you'll have to run deluge with the debug logging flag:
http://dev.deluge-torrent.org/wiki/Troubleshooting#WindowsSpecificLogging
They all are (now) but I don't know why or what happened to change things. I'm off to bed though it's almost 4am here on PST.
Sent from my iPad
On Jul 21, 2016, at 3:34 AM, Jared Anderson notifications@github.com<mailto:notifications@github.com> wrote:
Are all renames having this issue, or is this a one time occurrence?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3Agithub.com_Laharah_deluge-2DFileBotTool_issues_5-23issuecomment-2D234217241&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=VbeKg1SHWDDJEAM0B5DOW4zULNNeKKOjhlc6s_XJAIw&s=8EAKnjQKOn1PvHajE-JBjrihnr33117XZ82QTg8CLW0&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3Agithub.com_notifications_unsubscribe-2Dauth_ATn45cHTipqxmeBGgy4mOaoumiwaoqBtks5qX0sJgaJpZM4JRojy&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=VbeKg1SHWDDJEAM0B5DOW4zULNNeKKOjhlc6s_XJAIw&s=1TihZnedrXl-YRfPi-_01eE2VEchcH6yP_0Lb8lCw_c&e=.
Alright, then @Latinkidmj just has to run deluge with the debug logging flag and see what the filebot command/output says.
When I open the cli and type "%ProgramFiles%\Deluge\deluge-debug.exe" -L error -l "%UserProfile%\Desktop\deluge.log" I get an error message saying “System cannot find the path”?
From: Reinhard Pointner [mailto:notifications@github.com] Sent: Thursday, July 21, 2016 8:41 AM To: Laharah/deluge-FileBotTool deluge-FileBotTool@noreply.github.com Cc: Johnson, Michael,Jr mjohnso9@wsu.edu; Mention mention@noreply.github.com Subject: Re: [Laharah/deluge-FileBotTool] Plugin Problem (#5)
Alright, then @Latinkidmjhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Latinkidmj&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=ltOcbmBq3g1hoCbTJB65IUUIsXhcovahQVt_IGnxmAM&s=A93ASb0KKjBfLv5VXn8uwbYpt9QlU9-IKoUqCk8CnB8&e= just has to run deluge with the debug logging flag and see what the filebot command/output says.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Laharah_deluge-2DFileBotTool_issues_5-23issuecomment-2D234293785&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=ltOcbmBq3g1hoCbTJB65IUUIsXhcovahQVt_IGnxmAM&s=o2mgKJwy9E_uZlAI-Hkh0etU4Vc3pIkOoaqdD-YxfTc&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ATn45Y-2Dgt3L-2DCkP8LfYqQPyoyFKm38rGks5qX5L4gaJpZM4JRojy&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=ltOcbmBq3g1hoCbTJB65IUUIsXhcovahQVt_IGnxmAM&s=UMxTmULTF89kg86aRDiht6DYjL0bLTgyu36Ox6FGhSA&e=.
When I run "%ProgramFiles%\Deluge\deluge-debug.exe" -L error -l "%UserProfile%\Desktop\deluge.log" from the command prompt, I get an error saying “The system cannot find the path”. I’m assuming this is how one runs the filebot with logging enabled?
From: Jared Anderson [mailto:notifications@github.com] Sent: Thursday, July 21, 2016 3:49 AM To: Laharah/deluge-FileBotTool deluge-FileBotTool@noreply.github.com Cc: Johnson, Michael,Jr mjohnso9@wsu.edu; Author author@noreply.github.com Subject: Re: [Laharah/deluge-FileBotTool] Plugin Problem (#5)
It actually does log those things to the deluge logs, you'll have to run deluge with the debug logging flag:
http://dev.deluge-torrent.org/wiki/Troubleshooting#WindowsSpecificLogging
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Laharah_deluge-2DFileBotTool_issues_5-23issuecomment-2D234220137&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=5JJPRuajUkOD1LBgfkr0QUIoaeBbSlnR6FsnQPXKsJg&s=fe0SCzhtH_MkNqzjfsbwcDne88Itp_k1sXKBSBn8hEE&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ATn45Y41B4UIMM0rTS7Vqcd-5FhVpQ0b7Vks5qX06qgaJpZM4JRojy&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=5JJPRuajUkOD1LBgfkr0QUIoaeBbSlnR6FsnQPXKsJg&s=woI90oApzGjpF-akDQzyn87zXpZHN44cHUYg4GdvghY&e=.
So I'm still at a loss as to how I should proceed?
try opening cmd, navigating to the deluge folder, and running deluge-debug.exe -L debug -l deluge.log
. Then run the rename and return the log here.
I can't seem to replicate the bug, so until I have a log of it happening I can't do much but keep an eye out for what may have caused it.
I rant the commend that you specified and it appeared to work as Deluge was already open and seeding and came to the front of everything I had open on the desktop at the time. However I didn’t SEE anything different? How can I rename the file when I don’t know where it is much less attach it? A little clarification on this step would be helpful.
From: Jared Anderson [mailto:notifications@github.com] Sent: Friday, July 22, 2016 3:27 PM To: Laharah/deluge-FileBotTool deluge-FileBotTool@noreply.github.com Cc: Johnson, Michael,Jr mjohnso9@wsu.edu; Mention mention@noreply.github.com Subject: Re: [Laharah/deluge-FileBotTool] Plugin Problem (#5)
try opening cmd, navigating to the deluge folder, and running deluge-debug.exe -L debug -l deluge.log. Then run the rename and return the log here.
I can't seem to replicate the bug, so until I have a log of it happening I can't do much but keep an eye out for what may have caused it.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3Agithub.com_Laharah_deluge-2DFileBotTool_issues_5-23issuecomment-2D234672068&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=1qYwk_pk73oLYV3bS0rUIo0d73w_QDXLOTNj8eHPg50&s=CfAYlMK0Bl_xBVazbHX_PYK63TrzjctW_SQhvbBMt8A&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3Agithub.com_notifications_unsubscribe-2Dauth_ATn45Wx0ZcEpxtDaBZz5VM8dJW7QUrgdks5qYUOegaJpZM4JRojy&d=CwMCaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=-04qmZHJsyu58K91Kc6hgA&m=1qYwk_pk73oLYV3bS0rUIo0d73w_QDXLOTNj8eHPg50&s=cu0Tg6Ztu3C6gTHilXRlEiKAa6XYpG5ee07rGWG2g0I&e=.
You have to quit deluge and make sure it isn't running in your tray, then run the commands I gave you. Then once you've tried the rename and replicated the issue, send the new deluge.log
file that should be in the deluge folder next to the deluge.exe
Microsoft Windows Version 10.0.10586 2015 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd..
C:\Windows>cd..
C:>dir Volume in drive C has no label. Volume Serial Number is 063C-D240
Directory of C:\
06/30/2016 11:06 PM
C:>cd Program Files (x86)
C:\Program Files (x86)>deluge-debug.exe -L debug -l deluge.log 'deluge-debug.exe' is not recognized as an internal or external command, operable program or batch file.
C:\Program Files (x86)>cd Deluge
C:\Program Files (x86)\Deluge>deluge-debug.exe -L debug -l deluge.log
Traceback (most recent call last):
File "
C:\Program Files (x86)\Deluge>
I just ran the command that you gave me and listed above is the results. I'm afraid I can't find a "deluge.log" file anywhere on my system.
it seems you don't have permission to write to the programfiles\deluge folder. You'll have to either run the cmd window as administrator, or put the path of a folder you can write to in front of deluge.log .
ex: deluge-debug.exe -L debug -l C:\Users\USERNAME\Desktop\deluge.log
Well it appears that the plugin won't work at ALL now in Deluge :( It just hangs while "thinking"...attached is the deluge.log file. deluge.docx
UPDATE: Filebot's Plugin appears to be working again. I've since switched out a buggy hard drive and it's working now, albeit with a slight change to the original problem. Everything has been renames and relocated EXCEPT the original file folder which refuses to be renamed while all Season Folders still appear renamed (folders that I don't kneed) and of course the files themselves are renamed perfectly as well.
So I STILL wish to get rid of the folders by season convention and just have one folder with the title of the series with ALL the .mkv files in it (also properly reneamed). Can you help?
if you press the format expression
link in the rename window, it'll bring you to http://www.filebot.net/naming.html where you can get info about how to craft a format expression to your liking. Something like {n}/{n} - {S00E00}
should work, just set output to where you want the show's folder saved to.
I'm going to mark this as closed since it seems to have been a hardware error. Feel free to re-open if you can replicate the bug on the new drive.
Hello. I'm having a problem. Here is the explanation. The expression that I'm using is this: {n}/{n} Season {s}/{n} S{s.pad(2)}E{e.pad(2)} - {t} and it should move the correctly renamed files and folder to D:\TV. Unfortunately, it seems to be doing the following:
It will move the original files and original folder to D:\TV as indicated in the video clip above. But it will also correctly create a properly renamed folder and files into the same location on D:\TV as indicated in the video clip above. Unfortunately it also adds an extra subfolder for some reason I've yet to comprehend. I do not need either the extra subfolder OR the original files and folders after the torrent is downloaded and correctly renamed and relocated to D:\TV. Can you help?!