# \[X\] Incorrect Tools behavior

**URL:** https://community.mp3tag.de/t/x-incorrect-tools-behavior/17932
**Category:** No Bugs
**Created:** [May 9, 2016, 5:16pm UTC](https://community.mp3tag.de/t/x-incorrect-tools-behavior/17932 "2016-05-09T17:16:37Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![Zerow](https://community.mp3tag.de/user_avatar/community.mp3tag.de/zerow/32/11379_2.png) [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [May 31, 2016, 12:36pm UTC](https://community.mp3tag.de/t/x-incorrect-tools-behavior/17932/7 "2016-05-31T12:36:21Z")

</div>

> [@zerow](#):
>
> But how is this whole process suppose to work?  
> [...]

> [@ryerman](#):
>
> Go to Options \> Messages.  
> Make sure "at exporting tags" has a check-mark.  
> This causes a message to be displayed after exporting which asks: "Display Export file now?"  
> If you answer "Yes", the LOF file will be opened by its default application, which is Audacity.

After creating first LOF file, I opened it Notepad to check what exactly was written in it; and associated that format with Notepad

So after re-associating LOFs with Audacity, whole process doesn't differ that much from using a Tools- only two additional [closely places on screen] clicks are required, the rest is automated and no additional external elements are required [like a BAT]

So your workaround is very neat, thank you very much for this solution

> [@ryerman](#):
>
> BTW, this is how scripts can be executed.  
> More information: [passing multiple selected items to external tool](https://community.mp3tag.de/t/16451/4)

> [@zerow](#):
>
> [...]  
> But that this say to us, that this bug is the fault of Audacity?  
> [...]

> [@ryerman](#):
>
> What bug? I don't see a bug in Audacity or Mp3tag.

I was referring to that queued choking on larger files in Audacity. Here it is again:

> [@zerow](#):
>
> [...]  
> Also: when there are more files that take more space on a hard drive [and so the overall loading process is prolonged], sometimes I get for example a mix up like  
> **first instance - with 1 file  
> second instance - with 3 files  
> third instance - with 2 files**  
> [...]

> [@zerow](#):
>
> [...]  
> If I load 5 files that are 10 minutes long, here's what happens: all are started but then stopped near the beginning of the loading process [which I can see on a progress bar], with only one file being loaded to the end; and then second one and third one. And I get 2 instances- because length [size] of each of them was very similar
> 
> If I load files of different length, varying for example from few seconds do 10 minutes, that I get all that crazy behavior. Because some files are loaded fast enough [to get separate instance] while others get caught in a traffic jam and as a result get mixed with others

In the thread that you evoked [[passing multiple selected items to external tool](https://community.mp3tag.de/t/16451/4)], there is a statement

> [@passing multiple selected items to external tool](https://community.mp3tag.de/t/passing-multiple-selected-items-to-external-tool/16451/4):
>
> [...]  
> Sometimes, checking "for all selected files" causes an application to open once, with all files.  
> But sometimes it results in multiple instances opening, one for each file.
> 
> A way to overcome this limitation is to use what might be called "Export Tools". (my words)  
> Forum member DetlevD has pioneered this approach  
> [...]

So is it a limitation or is it a bug?

And does it have something to do with that multiple instances choking behavior I just quoted?

I'm asking because my problem with Mp3tag-Audaciity communication comes down to this: one file = no problem; more files = possible problem

> [@ryerman](#):
>
> If we could find a way to write the short file paths (also called 8.3 or DOS) to a LOF file, the file path character restriction would be overcome.  
> Audacity shows the long file names, even when given the short path.

And that is way over may head

> [@ryerman](#):
>
> I have tried methods using DOS and VBS, but have found failures in each.  
> Maybe I'll try again.

If you have time and will to do so, then please do

---

_[View the full topic](https://community.mp3tag.de/t/x-incorrect-tools-behavior/17932)._