X9 - File Drag in Bug - Service Pack 1

[jesario]

I have six .mp3 files on a separate drive. When I try to drag four of them to the timeline, I get the no symbol (crossed out circle) immediately after the processing bar disappears.

The files play fine in VLC. I edited four of them them in Audacity, two of them WILL appear on the timeline.

The oddest thing is , if I copy the files to my desktop, they WILL appear on the timeline when dragged in.

I had not seen this issue before, and have been using VS since Ulead VS11 and have made hundreds of videos.

I updated VSX9 to service pack 1 immediately before seeing the error.

[Ken Berry]

Hi Jesario -- welcome to the forum!

That sounds a bit strange. Normally any mp3 problem is caused by the codec used to make it, since VS over many versions has had difficulty with mp3 files made using the LAMEmp3 codec. We usually just suggest people use Audacity to convert them to standard .wav format. But this does not sound like your problem.

You say you drag and drop the mp3's. What happens when you right click in the timeline and choose Insert Audio, then navigate to the external drive to choose the clips to insert?

You also might want to try converting one of the mp3's to wav, leaving it on your external drive, and trying to drag it into the timeline.

Otherwise, all I can think of is to simply transfer them all to your desktop (or preferably a folder on your main C:\ drive) and insert from there if that works.

[jesario]

Ken,

Thanks for replying. I tried with the right click insert, and it posted an odd error message: "The parameter is incorrect." I hit OK and then it locked up, VS displaying only the progress bar incomplete at about 95%. I had to use Task Manager to end task.

It is a convenience issue for me, but seems to be looking like a bug. I started to wonder if it is a file lock issue or some other file system error.

I still have VSX7 installed on my machine. I tried and it also has the same issue, so not likely the update.

[jesario]

Same files do import fine by dragging them into Windows Movie Maker. If I copy and paste the file in the same directory and let Windows automatically numerate the file name - I am able to drag that file into the timeline.

[jesario]

I used Notepad++ file compare plugin, and the files match.

[jesario]

Here is a screenshot of the error. Anyway to get a full log of the error?

[Ken Berry]

That error message is pretty rare. We had reports of it in 2013, 2012 and 2008, though obviously with earlier versions of VS. And unfortunately we never found any specific reason as the error came with varying types of files. And when we obtained samples of those files, we could not replicate the error. The only workaround that I can see in those threads was to convert the files in question (all of which were video files; none were simply audio) to another format. Have you tried converting one or more of these mp3's to wav, as I suggested?

Incidentally, I have no trouble dragging and dropping my own mp3 files into the audio tracks of X9... so again I am unable to replicate your problem, at least with my own files.

[canuck]

Here is a screenshot of the error. Anyway to get a full log of the error?

Can you make the problem file available for a download by uploading it to some site such as DropBox?

[jesario]

I can provide the file, but I doubt it will be helpful. So far, I have discovered that to cut/move the file does NOT allow it to appear in the timeline. Renaming the file and moving the file are the only two things that I can change and still replicate the issue. Using IObit unlocker, I can see that the problem file is "unlocked."

Copying the file, even into the same directory, allows the file to work. Zipping the file, as I was planning to send it to you, allows the file to work so the error cannot be reproduced.

The best thing would be to get a log file or the errors with VS if there is such a function.

[jesario]

Anyone know if a program that can tell me all attributes of a file not related to the contents but what the file systems sees? Maybe something more in depth than a right-click properties, but cut from the same cloth.

[jesario]

I got the little bug. It is the file creation date. I used a program call BulkFileChanger. Changed the creation date to today and the file imports. I changed the creation date back to 1959 and I was able to reproduce the error. I am using a tape deck that has a USB port that sends analog tape converts it to mp3 automatically. http://www.ohm-electric.co.jp/product/c13/c1303/11602/ (sorry it is in Japanese). It has no OS inside, so the MFG set the file creation date to an arbitrary one. If VS is using .NET framework, then it could stem from there.

[asik1]

Good tip Jesario, form the nirsoft site we can learn:
"If you set a date prior to 01/01/1980, Windows Explorer will not display this date, due to a limitation originally created for old FAT systems. You can still watch an old file date using other file managers like 7-zip, using BulkFileChanger utility, or by right-clicking on the file and choosing 'Properties'. "
So it's OS thing and not VS, but on the other hand... why VS bother to check creation dates.

That site is full of handy little gems, I recommended here in the past WinCrashReport.

[jesario]

VS might be ordering files by creation date or querying it by default in some handler... that's my guess.