XM32 series never supported mp3 They list only files with .wav extension, thus not showing the other formats.
It has been a request since a long time, and is one of the most voted feature on the feedback Trello board (https://trello.com/b/Pky6BO3J) So I would say that it will have to be implemented at some point, but it hasn't been decided when yet... Hopeully soon :) Best regards
Hi Oskar, it has been reported several times and we found a way to correct this This is linked to the fader models being different throughout the m32 product range It will be handled better in the upcoming 4.02 update In the meantime, I recommend sticking with slow faders on m32 range (I would recommend always staying with slow faders anyway ;) ) Patience, will be fixed soon :)
Hi Doc :) Your issue sounds like you have a problem with the USB drive, please reformat to fat32 and try again There were indeed issues with 4.00, but none related to the USB recorder to my memory You should still update to 4.01 that fixes quite a lot of bugs :) Hope this will help with your problem ... Best regards
Hi Gary Thanks for the videos, its a good help :) After a talk with the mastemind behind the x32 series, I got more insight to the problem. At some point in production time, the model of the faders got changed, and they had way different motor/friction characteristics. This created two possible faderboard firmwares for the M32(R) series, as some had the old faderboards, some had the newer ones. This had to be corrected and handled on the fw side. At the time, everyone had fast faders still. But : The old faders had troubles with the newer faderboard fw, causing dropouts, and the fader was just stopping midway; The new ones had also issues with the old faderboard fw, causing those noisy oscillation. The solution was to slow down all the faderboards to have less troubles.
Now that everyone complained about the "forced" slow faders (it always kinda was, but a workaround existed), we decided to put back those old faderboard fw back. To him, this should have never been an option, at least not named like that (thus the "V1 faders" in fw 4.00).
I agree that this should be more precise, I think Midas will do some official statement soon. I will do my best to try to minimize the issue. Meanwhile I guess you should stick to slow faders indeed...
Hope this helped clarify the fadergate :) Best regards
The big bug you mentionned is not a bug, fast faders have always induced this "afterspin" sound. This is due to the faster speed of the faders, somehow overshooting the target position and fine tuning the end position for a short period of time. As this fine tuning also has the faster speed, it induces this little noise.
The FW 3.07 that had Fast Faders has the exact same speed, and the exact same little afterspin sound.
On the other hand, the sound of the fader sliding is way louder If this little sound worries you, I suggest you stick to the slower fader speed
I hope this helped clarify the root of the sound
Thanks for reaching out :)
I suggest you use the Routing PLAY/REC function on the Routing Input screen : - Set your regular input banks depending on what you want to record when you're in REC mode - Now turn 6th encoder to select PLAY and push - You now have a 2nd set of input routing where all the sources are replaced by the output from Ableton (by default the PLAY routing is set to Cards)
DCA are not really channels BUS and MATRIX cannot be reassigned to get card returns So you have to use regular channels / aux to get audio back from Ableton.
I suggest you watch a couple tutorial videos about the Routing capabilities of the M/X32 series
Hope this helped Best regards
Did you update the FW of your stageboxes ? You might want to try to update the mixer as well ... Be sure to have made a backup of all the internal data first (export all presets in library channel-fx-routing, export a show file, take note of your preferences/ip adress...)
Hope this will help Best regards
You mentionned that you were using the "1 to 1 routing", but the issue we found wasn't happenning when User In or Out banks were being sent to the AES port, problem occured only with regular banks. So it might be that your setup should actually work... Again, you need to activate HA remote on the AES port you will be controlled from (careful, this will overwrite your gains) in your case, on the Rack. Else you wont be able to set gains of the Monitor desk from FOH.
Latest version for S32 is 1.7 http://downloads.music-group.com/software/behringer/S32/S32_Firmware_Update_1.7.zip Best regards
The HA remote was indeed the feature you were looking for, as it must be enabled to allow the FOH to control the Monitor desk's preamps. Only the preamps forwarded to the AES port are made available for remote control.
There is indeed a bug with the HA remote control on FW 4.00 :
When you forward local AND remote headamps, the second banks are not controllable.
For example in your setup, on the rack: Local Ins 1-16 to AES A out 1-16 + AES B In 1-16 to AES A out 17-32, the AES B preamps wont be available... But if you're using User IN or OUT banks with the same preamps assigned, everything works fine.
This will be solved in the 4.01 version that should be released in a couple days
Thanks for reaching out, I hope this helped