Sound

Wow, that’s a lot of software! will have a look at it. I will come back about the drift. today I have to shoot (without bp-trx) thanks for your help bouke

Does anyone own a zoom f2 and can tell me if it records dual channel in 44.1kHz mode? According to the specs its only mono in 48khz, but maybe in 44.1 "44.1kHz/32-bit float, 48kHz/32-bit float Mono, BWF format supported" https://zoomcorp.com/en/gb/handheld-video-recorders/field-recorders/f2andf2-bt/ Does anyone own a device and can tell if its reliable??

Thanks for your help! i just tried it. Unfortunately theres only white noise in the rescued files, although it detects bitrate, channels and sample rate correctly.. About the drift: All the files I recovered in reaper have the exact same duration and metadata as the original files. So I really dont know why there is drift when syncing... I can only guess that the duration of the original files is already wrong. But the the bitrate is correct and the file size should be according to the duration..

Thanks! I ordered XTAR Prozessor Ladegerät für 8 x Li-Ion und NiMH Akkus in der Größe 18650, AA, AAA etc, universal und schnell, Modell: VC8. Hope it will show correct values as well. Isdt n24 looks great as well, until now I was charging with four eneloop chargers for 16 batteries but I could use even more. Although for the isdt they say it can drain the batteries totally out and damage them. Any experience with that?

With the sonys unfortunately the receivers last a little shorter - maybe because of the true diversity instead of antenna diversity. but I think I will rather swap batteries after six hours or so instead of reinstalling a power bank. according to the battery voltage chart the alkalines still have much more power remaining even when the voltage is very low. so when the battery indicator drops to soon on the nimh setting I guess the alkaline setting can be more accurate to see even low voltage indications.

So just use eneloop pro and don’t care about battery capacity anymore. at least for the transmitters Maybe like this?

Thanks a lot. Btw: the receivers turned off, but the transmitters are still running now… must be 12 hours at least on two as batteries.

Hi there, any recommendations for a good audio bag for zoom f6. I need a very lightweight bag and the ability to add four sony uwp-d audio receivers. I found the Orca OR-268 which is 550g and has a small pouch in the front for receivers. And the K-Tek KSF6, wich is 440 and should have some laces on the front and smaller ones on the sides, so I hope I could attach four receivers. Does anyone have experience with those or has any other idea?

How do you measure that? I like the batteries and usability of the deity connect as well and hope the corrupt file problem will be fixed soon. In the meantime I go back to sony and record in the mixer again, I think thats more reliable when its transmitting... Still, the battery runtime is great on the sonys. With two aa batteries that are quite old they are running for more than eight hours now, although the receivers should only run for six hours - even with alkaline batteries..

Yes, its no offset or delay, its a costant drift. So its getting bigger when TC values increase. When I dial in the starting timecode manually, the first minutes are i sing. Im not sure, but I had a few seconds drift after some time.. I guess after one or two hours.. Still after almost four days testing, I guess the problem only occurs when triggering the recording remotely. Maybe the solution would just be to map the shortcut on the device to put them to sleep mode instead of start and stop record... And I think it only occured after the first FW-updates..

I am using my Wireless Audio transmitters from Sony (UWP-D) mostly with NIMH-AA-Batteries. Right now I wanted to check my batteries and let them run in the transmitter to see how long they still last. Does anyone know a more elegant way to check the battery health? And: In the sony uwp-d I saw that the battery indicator dropped VERY quickly (after 1-2 hours) to display an empty battery, BUT the recorder keeps running on and on, so maybe the indicator is wrong which always made me switch batteries way too soon. I set the battery type in the menu to type2 for NIMH-batteries, but when I set it TYPE 1 (for LR6-Batteries), the readout shows still a bit more remaining capacity, so maybe the indicator is just more correct with this setting. My theory is that the NIMH-Batteries have gained so much capacity in the last years, that the indicator for NIMH is not correct anymore. I am using eneloop pro 2500mAh and IKEA Ladda 2450mAh - AA Batteries. Could it be, that the readout for LR6 is more correct for those new NIMH-Batteries? From the Sony UWP-D Manual: Setting the battery type (BATTERY) You can set the type of battery being used in order to provide a more accurate battery level indication. TYPE1: Recommended setting when using alkaline LR6 (size AA) batteries. Indicates the battery level based on the characteristics of new Sony alkaline LR6 (size AA) batteries. TYPE2: Recommended setting when using rechargeable nickel metal hydride batteries. TYPE3: Recommended setting when using lithium batteries.

Is there anyone here, who owns a Deity Connect Deluxe kit and could try if the same problem shows up? Best with the newest firmware 1.3. Is seems to show up only so far when you trigger record through the receiver. I started recording on both transmitters at the same time by long pushing the up and down arrows on the receiver, then I let the recording run for some time. (maybe best over an hour at least) Then I stopped recording through the receiver and immediately startet it again and let it run for some time.. Most corrupt files are at least 500 mb. Would be great to know if its a faulty unit or a fw problem. Maybe with those settings: Mode: TX+Rec Input Type: Mono Low Cut: 40 Hz Limiter: on Fre Boost off RF Power Auto

Is there anyone here, who owns a Deity Connect Deluxe kit and could try if the same problem shows up? Best with the newest firmware 1.3. Is seems to show up only so far when you trigger record through the receiver. I started recording on both transmitters at the same time by long pushing the up and down arrows on the receiver, then I let the recording run for some time. (maybe best over an hour at least) Then I stopped recording through the receiver and immediately startet it again and let it run for some time.. Most corrupt files are at least 500 mb. Would be great to know if its a faulty unit or a fw problem. I will post this in the Bp-Trx Group as well. Maybe with those settings: Mode: TX+Rec Input Type: Mono Low Cut: 40 Hz Limiter: on Fre Boost off RF Power Auto

I just received my zoom f6 and tried out if the timecode is accurate. I jammed the timecode to an ultrasync one and connted the USO to a sony a7 iii. Then I synced with tentacle sync studio as always. With the mixpre 10 ii, everything was perfectly fine, but now the audio recorder is half a frame too late. Does anyone have the same problem? Has timecode been accurate? I dont think this can be corrected in the settings, does it? I can just set a delay in ms for the audio output, when the audio is to fast, but i would need a timecode shift setting. btw: theres only an xlr mic connected to the zoom f6, and the camera has an external mic as well. its strange that the camera is quicker in capturing sound than the audio recorder.

Is seems like DF / NDF from the delay you are talking about.. Although I am recording in 25p, so there should be no DF or NDF...

Thanks a lot bouke!!! Do you know how to fix the drift problem easily. I hope there is a chance to keep using deity when there is an easy way to recover those files quickly.. with reaper it’s quite easy to fix the files but not the drift.

Anyway the problem from this topic wasn’t an issue to me anymore. I guess it was fixed in a firmware update as well.

They said it must be the sandisk card because all recording problems have been reported with these cards. So I had to get Samsung cards, and it’s exactly the same. Haven’t received an answer so far. Sounded like they don’t know another solution. I think the problem shows more frequently when you record a long take, about an hour and than stop and immediately start recording remotely via the receiver. Like the Transmitter has no time to write the data in the recorded file. But i am not sure.

I used a mixpre 10 ii extensively with a sony camera. But I set it as the master clock, fed the tc out to an ultra sync one via Bnc which gets synced constantly to the uso on the camera. That worked perfectly. I guess the internal clock alone should be fine, too.

I tried Samsung Evo cards now, exactly the same problem. The first file I recorded is already corrupt.

Hi Bouke, thanks again for your help!! We canceled the project now, so no worries - I dont need the footage anymore. But If you know a good workaround if it happens again, let me know!

Thanks! You know what you are talking about! But sounds a little complicated to me. How do you know, where the drift is going? And how can I remove the speed? I sent you the files By the way, i just checked: I can recreate the problem, when I pull out the card while recording. Exactly the same then: Large file with zero duration. Maybe the contacts of the internal sd card reader loose contact after some time. In the first weeks I had no problems at all with the same micro sd card. (sandisk extreme).

And thanks for the help again!! How can I send it?

I can fix the file, but there is audio drift. Do you think you can fix it without drift?

thanks again! Reaper batch conversion works and can even keep the timecode. Still the massive audio drift remains. But at least I dont have to dial in the timecodes manually and conversion is much quicker as with vlc - where i have to convert file by file.