Encoding lossy as mp3 fails

[Oblique]

I want to encode my FLAC files to mp3. I've set it up like this:
- Re-encode Lossy As: mp3 (Lame)
- Mode: Variable Bit Rate (VBR)

Right column: Copy 1:1 Audio Tracks Which Are: mp3 (only)

File Naming: Sub Path\Source Filename


Under 'Audio Types' I only have FLAC and mp3 checked.

This results in zero (lossy) tracks being encoded. The log says this:

Sync started on Monday, 26 August 2019, 11:03:41 to foobar2000 on Xiaomi Mi 9 SE
Sync incomplete.
 2 tracks, 2 tracks requiring syncing
 0 bytes synchronized
  Storing /_H/Hellfish - Black Death/Hellfish - Black Death - 01 Doctor Beak.mp3
  Unable to store /_H/Hellfish - Black Death/Hellfish - Black Death - 01 Doctor Beak.mp3
Sync incomplete.

Any idea what could be going wrong here?

Thanks in advance

[PeterP]

Re: Encoding lossy as mp3 fails

Thanks for the bug report.

Please get the latest foobar2000 mobile beta-

https://www.foobar2000.org/test-android

It introduces extensive debug logging of TuneFUSION operations, which should indicate in what way it failed.

Then, follow instructions from here to get the full telemetry-

https://forum.dbpoweramp.com/showthread.php?43801-How-to-Retrieve-debug-logs-from-TuneFUSION

[Oblique]

Re: Encoding lossy as mp3 fails

Thanks for the reply! Unfortunately I can't test this anymore since the trial has expired. I would buy the software after I know it works properly if you understand what I mean

[schmidj]

Re: Encoding lossy as mp3 fails

Peter,
Did you get the second log set I emailed you on August 5th? I'm not sure my email is getting through.

[PeterP]

Re: Encoding lossy as mp3 fails

( Replied in private message with new instructions, to both )

[Oblique]

Re: Encoding lossy as mp3 fails

Thanks for the PM Peter, things work (much better) now with the foobar mobile beta version and the info you send me through PM.

Only really weird thing now is that when I manually want to start a sync the program instantly shuts down. When opened again it says it synced successfully. So only when there are changes detected (?) or with 'When to Sync' (currently set to 'Re-sync Every: 6 hours') option under 'Advanced Sync Options' it will sync it seems.

Here's the TuneFusion log:

Sync started on Saturday, 31 August 2019, 11:28:39 to foobar2000 on Xiaomi MI 5s

Sync started on Saturday, 31 August 2019, 11:32:06 to foobar2000 on Xiaomi MI 5s
 Library contains 162 tracks, 162 tracks requiring syncing
 Device has 72,06 GB free space, 0 bytes already synchronized
  Storing /_A/America - * 1973 Horse With No Name (1973)/01. A Horse With No Name.mp3
..................................................................................... (all the other tracks)
  Storing /_S/Syl Kougaï - Twinkling One (*T01) 2013/01. Twinkling Two.mp3
  Transfer error: Data stream timeout
  Unable to store /_S/Syl Kougaï - Twinkling One (*T01) 2013/01. Twinkling Two.mp3
Sync incomplete.

Sync started on Saturday, 31 August 2019, 11:36:52 to foobar2000 on Xiaomi MI 5s
Sync incomplete.

Sync started on Saturday, 31 August 2019, 12:07:03 to foobar2000 on Xiaomi MI 5s

Sync started on Saturday, 31 August 2019, 12:07:34 to foobar2000 on Xiaomi MI 5s
 Library contains 159 tracks, 50 tracks requiring syncing
 Device has 71,22 GB free space, 281,67 MB already synchronized
  Storing /_Techno, House, Minimal (Dance)/Belief Defect - Decadent Yet Depraved (RM 178) 2017/01. Unnatural Instinct.mp3
......................................................................................................................... (all the other tracks)
  Storing /Somatic Responses - Circumflex (1999) [FLAC]/01 Umbrella.mp3
Successfully completed in 2 minutes 27 seconds

Sync started on Saturday, 31 August 2019, 12:12:08 to foobar2000 on Xiaomi MI 5s

So in the first run it ran into an error:
Transfer error: Data stream timeout
Unable to store "..."

And when you see:
Sync started on Saturday, 31 August 2019, 12:07:03 to foobar2000 on Xiaomi MI 5s

Sync started on Saturday, 31 August 2019, 12:07:34 to foobar2000 on Xiaomi MI 5s

I means that after the first run of '31 August 2019, 12:07:03' the program just instantly shuts down, but does report a successful sync. And when I open the software again it will actually run '31 August 2019, 12:07:34' and perform the actions without shutting down.

I'm on my old phone now btw, because I don't use the Playstore anymore. So I couldn't download the beta version of the foobar app on my new phone. But on my old phone I can't retrieve the foobar mobile logs, which DID work on my new phone. I saved the logs on my old phone, but when I connect my old phone to my PC and browse that folder it's empty. While on my phone it clearly shows the logs...

[Spoon]

Re: Encoding lossy as mp3 fails

Look in Event Viewer >> Applications

does it show that TuneFusion is crashing?

[Oblique]

Re: Encoding lossy as mp3 fails

It seems so yes:

Fault bucket 1504646245640172192, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: TuneFUSION.exe
P2: 1.2.0.2
P3: 5d4d82cc
P4: COMCTL32.dll
P5: 6.10.17763.592
P6: 754444f2
P7: c0000005
P8: 00000000000e25b8
P9: 
P10:

[Spoon]

Re: Encoding lossy as mp3 fails

What version Windows do you have? 32 or 64 bit?

[Oblique]

Re: Encoding lossy as mp3 fails

64 bit

[Spoon]

Re: Encoding lossy as mp3 fails

Windows 10?

[Oblique]

Re: Encoding lossy as mp3 fails

Yes Windows 10, sorry

[Spoon]

Re: Encoding lossy as mp3 fails

Please follow these steps:

1) Close TuneFunsion (right click on icon on tray >> quit tunefusion)
2) Download and unzip:

https://www.dbpoweramp.com/beta/TuneFUSION.zip

Copy TuneFUSION.exe to C:\Program Files\TuneFUSION\
(overwriting the existing)

3) Set your system up to give out details of the crash:

https://forum.dbpoweramp.com/showthread.php?30856-Setting-up-system-for-crash-dumping

4) Run TuneFUSION, when crashes email us the files created as documented in step 3.

[Oblique]

Re: Encoding lossy as mp3 fails

I've send you a pm!

[Oblique]

Re: Encoding lossy as mp3 fails

btw I want to ask a question about the (automatic) file naming option, can I do that here or should I start a new thread?