Import Flac files often end in error: Data too large for variable. Set the TFDParam.Size to a greater value

English mAirList 6.x
1

2021-09-27 18_23_30-Window
Uploading FLAC files often result in an error. Is there a fix for this other then re-editting all the flacs?

Thanks in advance.

2

I discoved that in these files there are TRAKTOR4 tags. Removing this tag value solves it for now, but it would be nice if there is another solution than erasing the TRAKTOR4 tags in FLAC files.

3

It happens also with other fields not only the TRACTOR4 field, so it seems structural. @Torben, do you any suggestions?

Thanks in advance

4

Is this an MSSQL database? The value column of the item_attributes table is limited to 4000 unicode characters (8002 bytes including the terminator) in order to have it indexed for fast search. This is a technical limitation of MSSQL.

Which FLAC/Vorbis field does Tractor put this stuff anyway?

Can you upload a sample file here? Nextcloud

5

First of all thanks for the feedback. It indeed is a MS SQL database. Traktor adds a Traktor4 field with a value but I noticed that it also can occur in other situations when information is retrieved like for example from discogs this problem can occur.

I can imagine that it also will occur when lyrics are added.

I have uploaded a sample track with a screenshot of the tag.

Would it help to change the item_attributes value field from nvarchar(4000) to nvarchar(max)? Where would performance weaken?

6

You cannot filter for attribute values in the DB app anymore, or it would become very slow, similar to a search through the entire library. And you will get SQL errors on future schema updates, as the SQL index cannot be updated/created.

If you feel like you’re an MSSQL export enough (I am not) to play around with it, feel free to do so. Just don’t forget your backup :wink: