Search options (Page 1 of 2)

No, crash happens when I hit rename button.
As I said, typically when sub-directories loaded.
Not sure where "switching to next group of folders" came from.
Don't see that phrase in any of my posts; but it is sometimes true I'm doing multiple groups of files and that the first rename is OK but 2nd or 3rd crashes. Sometimes crashes right away though.
When I move to a new batch I'm just using the folder list pane.

The common theme I'm seeing is that sub-directories are loaded; sometimes with very large number of files (100's or 1000's).

Hi Remi,

Seems to happen mostly when subdirectories are loaded and renaming muliple files across several folders..
Note that Siren frequently does not correctly update current file list in the situation described; but that's been so for a while now; I resolve with a manual refresh; probably not related, but worth mentioning.

Last time I was working with 6 folders, 787 files. Subdirectories loaded. Filter: *\[*.jpg
Found 8 files to rename. Manually checked 4 of them. Renaming using %p1(s/(.*) \((.*)/\1/i).%e
Exception occurred right after I hit Rename button, but files were successfully renamed.

Time before that working with 10 folders, 1,332 files. Subdirectories loaded. No filter.
Renaming using %p1(7,15)(" - ","_")(" ","")_%N{3,0,-1}.%e
Exception occurred as above; about 2/3 of files successfully renamed.
After restarting and selecting the remaining files exception occurred again but all renamed.

Happens with or without filters

This is a new install on Windows 7. I got tired of wrestling with windows 10 and rebuilt my machine clean with 7.
Not sure what else to tell you.
Below are event logs from last three times.
Let me know what else to provide.

daffdaemon

Log Name:      Application
Source:        Application Error
Date:          12/3/2017 7:27:12 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      P580
Description:
Faulting application name: siren.exe, version: 3.1.4.0, time stamp: 0x52bda8ac
Faulting module name: ntdll.dll, version: 6.1.7601.23915, time stamp: 0x59b94a16
Exception code: 0xc0000005
Fault offset: 0x0002e43e
Faulting process id: 0x2778
Faulting application start time: 0x01d36c8afa8be40b
Faulting application path: C:\Program Files (x86)\Siren\siren.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: de5d4a62-d889-11e7-b496-e006e6bf4da0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-12-04T00:27:12.000000000Z" />
    <EventRecordID>8520</EventRecordID>
    <Channel>Application</Channel>
    <Computer>P580</Computer>
    <Security />
  </System>
  <EventData>
    <Data>siren.exe</Data>
    <Data>3.1.4.0</Data>
    <Data>52bda8ac</Data>
    <Data>ntdll.dll</Data>
    <Data>6.1.7601.23915</Data>
    <Data>59b94a16</Data>
    <Data>c0000005</Data>
    <Data>0002e43e</Data>
    <Data>2778</Data>
    <Data>01d36c8afa8be40b</Data>
    <Data>C:\Program Files (x86)\Siren\siren.exe</Data>
    <Data>C:\Windows\SysWOW64\ntdll.dll</Data>
    <Data>de5d4a62-d889-11e7-b496-e006e6bf4da0</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Application Error
Date:          12/3/2017 6:02:37 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      P580
Description:
Faulting application name: siren.exe, version: 3.1.4.0, time stamp: 0x52bda8ac
Faulting module name: siren.exe, version: 3.1.4.0, time stamp: 0x52bda8ac
Exception code: 0xc0000005
Fault offset: 0x0069eb14
Faulting process id: 0x1f7c
Faulting application start time: 0x01d36c8a77c62d2a
Faulting application path: C:\Program Files (x86)\Siren\siren.exe
Faulting module path: C:\Program Files (x86)\Siren\siren.exe
Report Id: 0da4f9cc-d87e-11e7-b496-e006e6bf4da0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-12-03T23:02:37.000000000Z" />
    <EventRecordID>8507</EventRecordID>
    <Channel>Application</Channel>
    <Computer>P580</Computer>
    <Security />
  </System>
  <EventData>
    <Data>siren.exe</Data>
    <Data>3.1.4.0</Data>
    <Data>52bda8ac</Data>
    <Data>siren.exe</Data>
    <Data>3.1.4.0</Data>
    <Data>52bda8ac</Data>
    <Data>c0000005</Data>
    <Data>0069eb14</Data>
    <Data>1f7c</Data>
    <Data>01d36c8a77c62d2a</Data>
    <Data>C:\Program Files (x86)\Siren\siren.exe</Data>
    <Data>C:\Program Files (x86)\Siren\siren.exe</Data>
    <Data>0da4f9cc-d87e-11e7-b496-e006e6bf4da0</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Application Error
Date:          12/3/2017 5:59:31 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      P580
Description:
Faulting application name: siren.exe, version: 3.1.4.0, time stamp: 0x52bda8ac
Faulting module name: siren.exe, version: 3.1.4.0, time stamp: 0x52bda8ac
Exception code: 0xc0000005
Fault offset: 0x0060d700
Faulting process id: 0x30b4
Faulting application start time: 0x01d36c842e4987fb
Faulting application path: C:\Program Files (x86)\Siren\siren.exe
Faulting module path: C:\Program Files (x86)\Siren\siren.exe
Report Id: 9ed19a20-d87d-11e7-b496-e006e6bf4da0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-12-03T22:59:31.000000000Z" />
    <EventRecordID>8505</EventRecordID>
    <Channel>Application</Channel>
    <Computer>P580</Computer>
    <Security />
  </System>
  <EventData>
    <Data>siren.exe</Data>
    <Data>3.1.4.0</Data>
    <Data>52bda8ac</Data>
    <Data>siren.exe</Data>
    <Data>3.1.4.0</Data>
    <Data>52bda8ac</Data>
    <Data>c0000005</Data>
    <Data>0060d700</Data>
    <Data>30b4</Data>
    <Data>01d36c842e4987fb</Data>
    <Data>C:\Program Files (x86)\Siren\siren.exe</Data>
    <Data>C:\Program Files (x86)\Siren\siren.exe</Data>
    <Data>9ed19a20-d87d-11e7-b496-e006e6bf4da0</Data>
  </EventData>
</Event>

Nevermind... *\[* works

A brief tutorial in use of \ and / would be helpful.

I am having another filter problem.
I want to rename a batch of covers each in a separate folder where the folder name is the same as the cover base name.
The filter *\MM2007* or *\\MM2007* should give me just the covers from 3 folders.
I'm getting, instead, all files from those three folders.
I admit I don't quite understand the usage here of the extra \.
But one way or another I should be filtering out any file that doesn't begin with MM2007.
What am I doing wrong?

That's good to hear.
BTW I have ver 3.14 which is still the latest issue, correct?

I just wanted to add a note here for those interested in this topic. While discussing another topic we came up with a solution that works pretty well here.
Example: I have a bunch of folders with non-descript names but the 1st file in each folder is a cover with a name in the form of "Date - Artist - Album.jpg"

step 1: for /D %i in (*) do @(dir /b /a-d /on "%i" > "%i\dirfiles.txt")   ;;run from cmd prompt OR
            cmd /C \"dir /b /a-d \"%f\" > \"%f\\dirfiles.txt\"\"                    ;;run on highlighted folders fom Siren Tools
step 2: %T{%fa(s/$/\\dirfiles.txt/),1};%b
step 3: for /D %i in (*) do @(del "%i\dirfiles.txt")          ;;run from cmd prompt OR
            cmd /C \"del \"%f\\dirfiles.txt\"\"                       ;; run on highlighted folders from Siren Tools

A variety of outcomes can be accomplished here by simple variations on the command parameters passed to the DIR command and by post-processing of the selected text line returned by %T

The renaming express is irrelevant. As soon as I try to open a folder containing the character  ⁄ [2044]; I get the error message.
I did just notice something peculiar though.
Folder is named "date - artist1 w⁄ artist2 - album (xN)"
But the error box message reads:
Impossible to access to "W\path\date - artist1 w\ artist2 - album (xN)"
The unicode character ⁄ [2044] has been changed to the ascii character \ [92]

I don't understand why you can't duplicate the error though.
I just copied the exact name as typed above and pasted to a new folder in My Documents, moved a couple of files into the folder, and then tried to open the folder with siren. Got the error immediately.

I am using Siren Ver 3.14 in Windows 8.1

Remi, Thanks, Works like a charm.

step 1, run from cmd prompt, creates numfiles.txt:
   for /D %i in (*) do @(dir /b /a-d "%i" | find  /c /v "" > "%i\numfiles.txt")

step 2, run in siren, rename Filename >> Filename (xN) where N = number of files.
Note: Have to subtract 1 for numfiles.txt or 2 if thumbs.db exists
  %b - %T{%fa(s/$/\\numfiles.txt/),1};%b[1,-1] (x%N{1,-1,-1})

step 3, run from cmd prompt, deletes numfiles.txt
  for /D %i in (*) do @(del "%i\numfiles.txt")

BTW: Sorry about misplacing the post. Yes, please, move the thread to proper place.