uTool says “error” when exporting *any* multitrack song with MIDI

Hi damianpowell,

Please tell me your uTool version and your computer OS.
If you are using older version please update to 2.0.055 we had resolved some similar issue with this release.

I’m experiencing same problem after updating uTool to version 2.0.055..
Exactly same symptoms as described by OP.
Previous version worked ok (I think it was 2.0.34 beta)

Have you been able to replicate problem and working on solution?
Thanks

I have the same problem. Win 10 and V2.0.055

If I go to the song menue and delete the (none existing) midifile it works. But there is no way to see when this happens. It affects a song by chance.

Other issues:
If I do “New Multitrack Song) and drag the whole punch of tracks from left to the right the tracks are resorted in alphabeticle order. So I had to drag track for track. Timeconsuming and annoying.

Tracks exported in quick-mode will be never compared about older and newer tracks. If the track is on the export-disk nothing happens in quick-mode. It seems that only none-existing tracks will be exported to the disk.
If you did not use “Force Overwrite” you had to check every single tracks version bevor your gig.
It is a very simple process for every newbie-programmer to apply this funktion. In uTool this did not work since the very first version.

[quote=”Laszlo” post=3010]Hi,

In quick export mode if the song(s) already exist on your drive only the settings file(s) [mixer parameters etc] and the playlist (if exist) transferred to the drive.
if the song does not exist on the drive wav + set file copied to the drive.
Using force overwrite mode it will overwrite all content incl wav .set, playlist on your drive. [/quote]

Yes, I know. But it is not a big deal to make it more useable.
If I have changed one (existing) track I have to “Force” export all songs. It needs hours.
In windows and linux/mac there are functions to compare the files and upload the new ones, the changed ones and remove the deleted ones. Thats build in functions. Why uTool did not use this?
It is very confusing to see after export in quick mode all tracks are still in the same version and nothing tells me that there is a difference between local and exported tracks. I could not know wich ones are changed by other persons but I allways want to have the actual versions on my disk I use on gigs.

[quote=”Laszlo” post=3010]Does the left side has different order?[/quote]

Yes. The Tracks are numbered (1-16 for example). And so the no 11 comes after no 1 and so on. The tracks shoul be draged and droped as listed in the left window. Thats why they are (channel-) numbered – in my case.

[quote=”Laszlo” post=3010]So your song has no midi? How do you delete the none existing midifile?[/quote]

It seems a little bit weired, I know. Sometimes a song wich never has had a midifile but in quick mode has an error sign (no midi file).
If I go to the song and klick the trashcan nothing happens but the error sign in quick mode was not shown any more.
I recognized this after changing from 44.1 to 48kHz. After this change NO midifile was able to export in quick mode.
And some of the songs without midifile got the same error.

[quote=”Laszlo” post=3013]

This is not that easy as sounds. Using your computer you have the files on your internal drive. Easy and fast to compare to files which are the same and located in internal drive.

Using uTool you have a source (mono) files on your computer and you have a ready made content on the USB drive which can be mono wav files (LP-16) or multichannel wav files (uTrack24 and uTrack-X32) then you need to compare those files to the source mono files. Open each file from the USB drive then extract them to mono and compare to the local files on your computer. Believe me that will be also time consuming process.

Edit:
In the meantime I had talk with the developer. That issue can be solved easily if the uTool use the timestamp provided by settings file. So once you change the wav files in your source (uTool) it will check the timestamp provided by the song on your USB drive if the two does not matching the song will be overwritten.
We going to implement this in the coming uTool version[/quote]

Thanks! Thats good news.

[quote=”Laszlo” post=3013]If your songs named properly like 01; 02; 03 …. 10; 11; 12 you will have no problem with the order.[/quote]

I cannot always dictate how they are had to be named and I have tons of tracks they are named since years in the same way.
Most of them are named for example like S3_4 Bass – Title – 01 (left) and so on.
In our workflow this names have special meanings (in other applications too). S=stereo, 3_4= channels left/right etc.
So it would be easier if uTool did not sort on its own meaning.

[quote=”Laszlo” post=3013]To be honest you are the first person who report that issue if the song has no midi file. We need to take a look that issue. But it happens randomly I assume difficult to reproduce (and fix) this issue[/quote]

Maybe one of the reason is in case of changing from 44.1 to 48kHz. After this every song (with “old 44.1” midifile) has an error sign for midi. But not only songs they had midifiles bevor. Songs without midifiles too.
I had not seen any way to retrace this. It comes on different songs but not very often. If I “deleted the non existing midifile” this song never had a error again.
It seems that if an error is shown on a song WITH a midi file and I export a song without midifile in the same session then this song shows an error too.
Somtimes after ending a session and restart uTool the error was not shown again.
But, as said above – I cannot retrace.
Bevor changing sample rates I never noticed this. If I work only with the “new” 48kHz songs the failure did not come along.