Hi,
try (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll) my (advanced) crossfading plugin 'Continuator' with following features:
- threshold-controlled start of new track
- force current track to fade-out with desired rate
- disable crossfading for seamless track transitions (may not work with mp3, ogg and wav should be fine)
- force tracklength to be multiple of Audio CD blocksize (588 samples), useful for creation of gapless mix cds
enjoy!
it caused a crash within the first 5 songs i tried it on.
sounded great for those first 5 though
Crashed while testing..
between two songs that fade into eachother already. I didnt know it had fade dectection.. so i listened to it once thru with fade detection on.. then I went and turned it off.. went back to the first song.. skipped ahead so there were about 15 seconds left.. let it play.. it crashed in like 5 mins. All other options left default
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 00941C35h
Access violation, operation: read, address: 00000008h
Call path:
playback_core_i::g_thread_func=>playback_core_i::thread_func=>dsp::run
This is the first crash logged by this instance.
Code bytes (00941C35h):
00941BF5h: 43 DD 01 DC 8E 88 00 00 00 DC 04 10 DD 19 8B 86
00941C05h: E0 00 00 00 3B D8 72 DA FF 86 84 00 00 00 8B 86
00941C15h: 84 00 00 00 3B 86 90 00 00 00 75 44 83 86 80 00
00941C25h: 00 00 08 8D 86 80 00 00 00 8B 00 3B 46 78 74 30
00941C35h: DD 00 51 DC 0D 60 41 94 00 51 DD 1C 24 51 DD 05
00941C45h: 58 41 94 00 51 DD 1C 24 E8 76 18 00 00 8B 55 F8
00941C55h: DD 9E 88 00 00 00 83 C4 10 83 A6 84 00 00 00 00
00941C65h: FF 45 08 8B 4D 0C 39 4D 08 0F 8C 67 FF FF FF 8B
Stack (00E5FD00h):
00E5FCE0h: 80559E66 81B1FE50 00000246 804F520F
00E5FCF0h: 00000000 F4F1CD24 00000000 8186C4E4
00E5FD00h: 00000480 0106F830 00BE1DC8 02620F90
00E5FD10h: 000003DC 00E90020 00000000 00E5FD90
00E5FD20h: 00941505 0000008D 000000A4 0106F830
00E5FD30h: 00BE1DC8 004384A0 00000000 00000000
00E5FD40h: 00000002 00000002 00000002 00000002
00E5FD50h: 00000000 00000002 00000010 01072CF4
00E5FD60h: 0040AE4F 00E90020 00000000 3FF00000
00E5FD70h: 000018EF 00E90020 00000480 00164D48
00E5FD80h: 00000008 00E5FDBC 0006BAA8 00000000
00E5FD90h: 00E5FDBC 00942D2B 00000000 00BEBAB0
00E5FDA0h: 00000008 0040AA78 00E5FEF0 00C65314
00E5FDB0h: 00000000 00000002 00BEBAB0 00E5FE4C
00E5FDC0h: 0040A959 0000003C 00E5FEF0 00C65314
00E5FDD0h: 00000000 00E5FE00 00000000 00C8A598
00E5FDE0h: 00000004 00000003 00432ED3 00BEBAB0
00E5FDF0h: 00000030 00443B08 00000000 0106F830
00E5FE00h: E82D23BC 3FB40FE1 0109001F 00436B97
00E5FE10h: 03529A6F 44854B29 E1720CA7 15AD975E
Registers:
EAX: 00000008, EBX: 00000002, ECX: 02621868, EDX: 00E90020
ESI: 00BE1DC8, EDI: 00000480, EBP: 00E5FD1C, ESP: 00E5FD00
Crash location: "foo_dsp_continuator", loaded at 00940000h - 00948000h
Loaded modules:
foobar2000 loaded at 00400000h - 00451000h
ntdll loaded at 77F50000h - 77FF7000h
kernel32 loaded at 77E60000h - 77F46000h
USER32 loaded at 77D40000h - 77DCC000h
GDI32 loaded at 77C70000h - 77CB0000h
ADVAPI32 loaded at 77DD0000h - 77E5D000h
RPCRT4 loaded at 78000000h - 78086000h
ole32 loaded at 771B0000h - 772D1000h
COMCTL32 loaded at 71950000h - 71A34000h
msvcrt loaded at 77C10000h - 77C63000h
SHLWAPI loaded at 70A70000h - 70AD5000h
utf8api loaded at 10000000h - 1000D000h
comdlg32 loaded at 763B0000h - 763F5000h
SHELL32 loaded at 773D0000h - 77BC2000h
foo_albumlist loaded at 008D0000h - 008DA000h
foo_ape loaded at 008E0000h - 008FF000h
foo_burninate loaded at 00900000h - 0090B000h
VERSION loaded at 77C00000h - 77C07000h
foo_cdda loaded at 00910000h - 0091E000h
foo_console loaded at 00920000h - 00928000h
foo_diskwriter loaded at 00930000h - 0093E000h
foo_dsp_continuator loaded at 00940000h - 00948000h
foo_dsp_nogaps loaded at 00950000h - 00957000h
foo_freedb loaded at 00960000h - 0098E000h
WS2_32 loaded at 71AB0000h - 71AC5000h
WS2HELP loaded at 71AA0000h - 71AA8000h
foo_infobox loaded at 00990000h - 009A3000h
foo_input_std loaded at 009B0000h - 00A49000h
MSACM32 loaded at 77BE0000h - 77BF4000h
WINMM loaded at 76B40000h - 76B6C000h
serwvdrv loaded at 5CD70000h - 5CD77000h
umdmxfrm loaded at 5B0A0000h - 5B0A7000h
foo_lame loaded at 00AD0000h - 00AD9000h
foo_masstag loaded at 00AE0000h - 00AEF000h
foo_output_std loaded at 00AF0000h - 00AF9000h
foo_out_ks loaded at 00B00000h - 00B0B000h
SETUPAPI loaded at 76670000h - 76757000h
foo_rgscan loaded at 00B10000h - 00B1B000h
foo_shuffle loaded at 00B20000h - 00B2D000h
foo_syfm loaded at 00B30000h - 00B3A000h
MSVCR70 loaded at 7C000000h - 7C054000h
foo_text loaded at 00B50000h - 00B63000h
foo_ui_std loaded at 00B70000h - 00B87000h
foo_vis_manager loaded at 00B90000h - 00B98000h
foo_wma loaded at 00BA0000h - 00BB9000h
WMVCore loaded at 08530000h - 0872D000h
WMASF loaded at 07260000h - 07299000h
OLEAUT32 loaded at 77120000h - 771AB000h
uxtheme loaded at 5AD70000h - 5ADA4000h
ksuser loaded at 5EF80000h - 5EF84000h
events loaded at 01220000h - 01246000h
MSVCR71 loaded at 7C340000h - 7C396000h
imagehlp loaded at 76C90000h - 76CB2000h
DBGHELP loaded at 6D510000h - 6D58D000h
Stack dump analysis:
Address: 00941505h, location: "foo_dsp_continuator", loaded at 00940000h - 00948000h
Address: 004384A0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0040AE4Fh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00942D2Bh, location: "foo_dsp_continuator", loaded at 00940000h - 00948000h
Address: 0040AA78h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0040A959h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00432ED3h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00443B08h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00436B97h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0041FBCAh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0041FB95h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0041EFE2h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00438978h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389ECh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389E4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389D0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389E4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389D0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EECh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439ED8h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439F68h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EA8h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439ED0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EBCh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439ED0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EBCh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004392E4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004384A0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004384A0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EECh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439ED8h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00444A00h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0041F29Eh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 77E7D33Bh, location: "kernel32", loaded at 77E60000h - 77F46000h
Symbol: "RegisterWaitForInputIdle" (+00000043h)
Address: 77E94809h, location: "kernel32", loaded at 77E60000h - 77F46000h
Symbol: "SetThreadExecutionState" (+00000097h)
Address: 77E83DB8h, location: "kernel32", loaded at 77E60000h - 77F46000h
Symbol: "OpenConsoleW" (+00001966h)
Address: 0041F26Fh, location: "foobar2000", loaded at 00400000h - 00451000h
Version info:
foobar2000 v0.8 beta 8
UNICODE
Hi,
new version (0.1.2) uploaded (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll).
bye
this is awesome. Thank you Cpt. Footure!
version 0.1.2
crash happened when skipping forward 30 seconds near the end of the track (target-time was aprox 8secs before track-end).
Active DSPs: Gap-Killer->Continuator->convert to 4ch->foo_wider
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 00842C81h
Access violation, operation: read, address: FFFFFFF8h
Call path:
playback_core_i::g_thread_func=>playback_core_i::thread_func=>dsp::run
This is the first crash logged by this instance.
Code bytes (00842C81h):
00842C41h: C1 85 C0 89 45 FC 7D 02 33 C0 C1 E0 03 50 E8 FC
00842C51h: 08 00 00 8B D0 8B 46 04 59 89 55 0C 3B 45 08 74
00842C61h: 10 85 D2 74 04 DD 00 DD 1A 83 C2 08 83 C0 08 EB
00842C71h: EB 85 FF 8B C2 76 13 8B CF 85 C0 74 07 8B 5D 10
00842C81h: DD 03 DD 18 83 C0 08 49 75 EF 8B 46 08 8B CF C1
00842C91h: E1 03 39 45 08 8D 1C 11 89 45 10 74 1C 8B C3 2B
00842CA1h: C1 2B C2 03 45 08 85 DB 74 04 DD 00 DD 1B 83 C0
00842CB1h: 08 83 C3 08 3B 45 10 75 ED 8B 46 04 50 89 45 08
Stack (00EBFD38h):
00EBFD18h: BADF1D64 00EBFD14 00000000 82739720
00EBFD28h: 818ABD2C FFDFF848 1282ABB0 00000001
00EBFD38h: 00CB0988 00CB0918 01B152E0 00000001
00EBFD48h: 00EBFD94 008427A8 00000000 00C6FC90
00EBFD58h: FFFFFFF8 0084226A FFFFFFF8 00000000
00EBFD68h: 00CB0918 004384A0 E7D43D69 C054EC69
00EBFD78h: EB851EB8 3FCEB851 C5D3D942 C056B27F
00EBFD88h: 0000090E 00000000 00000000 00EBFDBC
00EBFD98h: 00842E37 00C5C5A0 00000004 0040A97A
00EBFDA8h: 00EBFEF0 00C5C644 00000001 00000001
00EBFDB8h: 00C5C5A0 00EBFE4C 0040A85B 0000003C
00EBFDC8h: 00EBFEF0 00C5C644 00000001 00EBFE00
00EBFDD8h: 00CA1120 00C5C3C0 00C6B614 00000004
00EBFDE8h: 00C6B614 00C5C5A0 00000040 00443B08
00EBFDF8h: 00000001 00002400 00000000 00000000
00EBFE08h: 0109001F 00000010 7F6BAF16 40A41B65
00EBFE18h: D69331BB 6F1CB1DE 00000010 10001DE2
00EBFE28h: 00C61010 10001E17 00000000 00EBFE54
00EBFE38h: 00436589 00436594 00000000 00C5C3C0
00EBFE48h: 0041E214 00EBFFA4 0041EFE4 00EBFEF0
Registers:
EAX: 00C6FC90, EBX: FFFFFFF8, ECX: 00000001, EDX: 00C6FC90
ESI: 00CB0988, EDI: 00000001, EBP: 00EBFD48, ESP: 00EBFD38
Crash location: "foo_dsp_continuator", loaded at 00840000h - 00848000h
Loaded modules:
foobar2000 loaded at 00400000h - 00451000h
ntdll loaded at 77880000h - 77901000h
KERNEL32 loaded at 77E70000h - 77F33000h
USER32 loaded at 77E00000h - 77E65000h
GDI32 loaded at 77F40000h - 77F7C000h
ole32 loaded at 77A40000h - 77B2C000h
RPCRT4 loaded at 77D20000h - 77D8E000h
ADVAPI32 loaded at 77DA0000h - 77DFD000h
COMCTL32 loaded at 77B40000h - 77BC9000h
utf8api loaded at 10000000h - 1000D000h
comdlg32 loaded at 76B00000h - 76B3E000h
SHLWAPI loaded at 77C60000h - 77CAA000h
SHELL32 loaded at 77580000h - 777CC000h
MSVCRT loaded at 78000000h - 78046000h
foo_ape loaded at 00800000h - 0081F000h
foo_cdda loaded at 00820000h - 0082E000h
foo_diskwriter loaded at 00830000h - 0083E000h
foo_dsp_continuator loaded at 00840000h - 00848000h
foo_dsp_crossfade loaded at 00850000h - 00857000h
foo_dsp_extra loaded at 00860000h - 00875000h
foo_dsp_nogaps loaded at 00880000h - 00887000h
foo_dsp_wider loaded at 00890000h - 00897000h
foo_flac loaded at 008A0000h - 008B6000h
foo_id3v2 loaded at 008C0000h - 008E6000h
MSVCP60 loaded at 780C0000h - 78121000h
foo_infobox loaded at 008F0000h - 00903000h
foo_input_std loaded at 00910000h - 009A9000h
MSACM32 loaded at 773E0000h - 773F3000h
WINMM loaded at 77540000h - 77571000h
foo_masstag loaded at 009B0000h - 009C0000h
foo_mod loaded at 009C0000h - 009C9000h
BASS loaded at 009D0000h - 00A2A000h
foo_osd loaded at 00A30000h - 00A3B000h
foo_output_std loaded at 00A40000h - 00A49000h
foo_out_dsound_ex loaded at 00A50000h - 00A59000h
DSOUND loaded at 51080000h - 510DA000h
VERSION loaded at 77810000h - 77817000h
LZ32 loaded at 75940000h - 75946000h
foo_read_http loaded at 00A70000h - 00A79000h
WS2_32 loaded at 74FA0000h - 74FB3000h
WS2HELP loaded at 74F90000h - 74F98000h
foo_rgscan loaded at 00A80000h - 00A8B000h
foo_sid loaded at 00A90000h - 00AD7000h
foo_ui_std loaded at 00AE0000h - 00AF7000h
foo_vis_manager loaded at 00B00000h - 00B08000h
foo_vorbisenc loaded at 00B10000h - 00C0A000h
foo_web loaded at 00C10000h - 00C28000h
wdmaud loaded at 77530000h - 77539000h
KsUser loaded at 5EF80000h - 5EF84000h
imagehlp loaded at 77910000h - 77933000h
DBGHELP loaded at 72970000h - 7299D000h
Stack dump analysis:
Address: 008427A8h, location: "foo_dsp_continuator", loaded at 00840000h - 00848000h
Address: 0084226Ah, location: "foo_dsp_continuator", loaded at 00840000h - 00848000h
Address: 004384A0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00842E37h, location: "foo_dsp_continuator", loaded at 00840000h - 00848000h
Address: 0040A97Ah, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0040A85Bh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00443B08h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 10001DE2h, location: "utf8api", loaded at 10000000h - 1000D000h
Symbol: "uCallStackTracker::uCallStackTracker" (+00000000h)
Address: 10001E17h, location: "utf8api", loaded at 10000000h - 1000D000h
Symbol: "uCallStackTracker::uCallStackTracker" (+00000035h)
Address: 00436589h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00436594h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0041E214h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0041EFE4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00438978h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389ECh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389E4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389D0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389E4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389D0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EECh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439ED8h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439F68h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EA8h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439ED0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EBCh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439ED0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EBCh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004392E4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004384A0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004384A0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EECh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439ED8h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00444A00h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0041F374h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 77E787DDh, location: "KERNEL32", loaded at 77E70000h - 77F33000h
Address: 77E91856h, location: "KERNEL32", loaded at 77E70000h - 77F33000h
Address: 77E7AE88h, location: "KERNEL32", loaded at 77E70000h - 77F33000h
Address: 0041F345h, location: "foobar2000", loaded at 00400000h - 00451000h
Version info:
foobar2000 v0.8 beta 9
UNICODE
is gap killer necessary if you are using continuator? doesn't continuator destroy all the gaps by its nature?
is gap killer necessary if you are using continuator?
no
doesn't continuator destroy all the gaps by its nature?
yes
the above crashlog isn't caused by gap killer.
I've removed the gap-killer, so my chain now looks like this:
Continuator->convert to 4ch->foo_wider
I got another crash by skipping to the end of the track via hotkey. The file was a mp3.
Also, i tried the same thing once with an XM-Module, and playback would hang in an endless-loop, repeatly playing the first second of the XM-Module over and over.
This plugin has severe problems with forward-skipping near the end of a track.
- Lyx
edit: excluding the frequent crashes and problems, the plugin works great. So when it becomes more stable and mature, it would probably be a plugin for me which i would use often.
Finally a crossfader that seems to work properly - except for the crashes when skipping to the end of file
Would be cool if you can fix that.
Tom.
Hi,
version 0.1.3 is available (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll). This should fix the skip-to-end crashes.
bye
Trully awesome.
Great job! Just what I needed.
Can you add gapless detection for FLAC files? Or also files in an MKA container? (MKA especially when played in order).
Also, maybe it is a good idea to let all files referenced by CUE sheets be gapless (when played in order).
That would be great.
There should be no difference regarding gapless-detection with any codec (lossy or lossless) which preserves the original length and starts/endings of the source file.
But if i find some time, i'll have a look at the gapless-detection anyway, because i'm not yet satisfied with it.
bye.
the plugin still has some problems on my system with beginnings tracks after crossfading, etc.
Song A would end, and right in the first seconds of track B, there would be some loud clicks/crackle. Only happens in about 5% of cases.
Output-Method DirectSound v2
DSP-Chain same as in my previous post. Foobar 0.8beta10. Never had such problems with Case's crossfader.
the plugin still has some problems on my system with beginnings tracks after crossfading, etc.
Song A would end, and right in the first seconds of track B, there would be some loud clicks/crackle. Only happens in about 3-4% of cases.
I've been having the same problem. (Thought it was only me!) I'm using Kernel Streaming. I've gone back to using Cpt. Footure's Gap Killer (Advanced) which does not have this problem.
Cpt. Footure, I hope you can fix this as I was loving this DSP but found the random loud crackling after track change annoying.
occasionally, while crossfading, i have 1/2 second of loud static blips. Its not reproducable, but it only happens when I'm using continuator. Has anybody else experienced this, or is it just me? I'm sorry to say i'm going to have to stop using continuator because of this, even though it was my favorite plugin.
occasionally, while crossfading, i have 1/2 second of loud static blips. Its not reproducable, but it only happens when I'm using continuator. Has anybody else experienced this, or is it just me? I'm sorry to say i'm going to have to stop using continuator because of this, even though it was my favorite plugin.
You have read the 2 previous posts, haven't you?
occasionally, while crossfading, i have 1/2 second of loud static blips. Its not reproducable, but it only happens when I'm using continuator. Has anybody else experienced this, or is it just me? I'm sorry to say i'm going to have to stop using continuator because of this, even though it was my favorite plugin.
You have read the 2 previous posts, haven't you?
oops. those posts were just added, so i did not see them. I'm using kernel streaming, resampler, crossfeed, continuator, volume control, and advanced limiter.
occasionally, while crossfading, i have 1/2 second of loud static blips. Its not reproducable, but it only happens when I'm using continuator. Has anybody else experienced this, or is it just me? I'm sorry to say i'm going to have to stop using continuator because of this, even though it was my favorite plugin.
Same here. Plus, occasionally, song A has a moment of silence right before crossfading. I checked if disabling DSP's (volume control and equalizer) helps two avoid this - unfortunatly it doesn't.
Strangly enough, the blips and the silence do NOT happen on every crossfade, only on 5-10 % of the crossfades.
Besides that, a really appreciated plug in.
Tom.
Plus, occasionally, song A has a moment of silence right before crossfading. I checked if disabling DSP's (volume control and equalizer) helps two avoid this - unfortunatly it doesn't.
same here - i thought it was a performance issue about my pc being too slow, obviously not.
Song A would end, and right in the first seconds of track B, there would be some loud clicks/crackle. Only happens in about 5% of cases.
Does it only happen if "Force fade-out to..." is enabled?
Same here. Plus, occasionally, song A has a moment of silence right before crossfading. I checked if disabling DSP's (volume control and equalizer) helps two avoid this - unfortunatly it doesn't.
Try to disable "Empty buffer up to overlap point...".
Song A would end, and right in the first seconds of track B, there would be some loud clicks/crackle. Only happens in about 5% of cases.
Does it only happen if "Force fade-out to..." is enabled?
Same here. Plus, occasionally, song A has a moment of silence right before crossfading. I checked if disabling DSP's (volume control and equalizer) helps two avoid this - unfortunatly it doesn't.
Try to disable "Empty buffer up to overlap point...".
"Empty buffer up to overlap point" is disabled by default (didn't touch a thing).
I checked what happens when I disable "Force fade-out to...": Dreadful, loud noise - no music.
Tom.
EDIT: It seems (30 minutes playing fine now) that disabling "Force track length to be integer multiple of Audio CD blocksize" seems to do the trick. Can anyone confirm?
Finding (really) stupid bug...
Banging head against wall...
Fixing bug...
Uploading new version (0.1.4)... (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll)
Enjoy!
what bug did this fix? did it fix the cracking/popping/static bug? i will test, of course. thanks Cpt. Footure!
Finding (really) stupid bug...
Banging head against wall...
Fixing bug...
Thanks Cpt. I've been running it for 8 hours now without a snap, crackle or pop!
O-Oh! I've just got this failure.txt (http://people.smartchat.net.au/~carlodim/failure.txt) & i noticed I'm getting this in the console:
INFO (CORE) : location: "file://E:\Lambchop\How I Quit Smoking\06. Suzieju.mpc" (0)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 16647 samples (377 ms) removed (from beginning)
Can this be correct?
Cool plugin ...
Cool plugin ...
thnx.
O-Oh! I've just got this failure.txt & i noticed I'm getting this in the console:
INFO (CORE) : location: "file://E:\Lambchop\How I Quit Smoking\06. Suzieju.mpc" (0)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 277536 samples (6293 ms) overlapped (from end)
INFO (foo_dsp_continuator) : 16647 samples (377 ms) removed (from beginning)
Can this be correct?
No, i fixed (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll) the bug and disabled all console writing in addition. Will anybody miss it?
Cpt. Footure, thank you for your Continuator!
Question, what is the function of "empty buffer up to overlap point of track change" ?
Question, what is the function of "empty buffer up to overlap point of track change" ?
if checked:
- reaching end of track
- search point/time where new track will start according to threshold setting
- flush/output internal buffer contents up to this point (this may need some megs of memory, depending on buffer size)
- start new track while fading out old
if unchecked:
- reaching end of track
- search point/time where new track will start according to threshold setting
- no buffer flushing
- start new track while fading out old
The resulting track changes will be where they belong if "empty buffer..." is checked, in contrast to sqrsoft's ACF. It is especially useful if used with the diskwriter to create an Audio CD with already faded tracks.
bye
hmm, i still get a short (0,3 - 0,7 sec.) "playback freeze", at the moment continuator kicks in at the end of a track..... hmm, lets say "max overlap length" is set to 8000, and the track is 4:00mins long.... then the skip would often happen at 3:52.
It seems that this only happens on my system, if the tracks are already gapless(not sure).
Settings:
max. overlap lengt: 8000
empty buffer: on/off (happens in both cases)
threshold: 13.0
force fade-out: on
fade-rate: 5.5
disable track overlapping if seamless...: on
force track length...: off
i will try to lower the cpu consumption on track changes, in the meantime try to enlarge the buffer length of your preferred output plugin.
you are probably right about cpu consumption, since at the point when the skips happen, cpu-usage spikes from 1% up to about 55% for a short moment.
Running foobar all the day, i can say that at least on with the albums i played today, it -only- happens, if the tracks are already seamless - if they are not and overlapping is used instead, then theres no problem.
Thanks for your work
- Lyx
new version (0.1.7) uploaded (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll) with reduced cpu consumption on track changes
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 008623CAh
Access violation, operation: read, address: 00CD8BE0h
Call path:
playback_core_i::g_thread_func=>playback_core_i::thread_func=>dsp::run
This is the first crash logged by this instance.
Code bytes (008623CAh):
0086238Ah: C8 C1 F9 03 8B 55 14 D1 EA 2B CF 3B CA 89 55 10
0086239Ah: 73 1D 8B 76 08 8B 4B 04 8D 3C F8 3B FE 0F 84 1E
008623AAh: 01 00 00 DD 07 DD 19 83 C1 08 83 C7 08 EB EC 8D
008623BAh: 04 F8 D9 EE 89 45 08 8D 1C D0 3B C3 74 0B D9 C0
008623CAh: DC 00 83 C0 08 DD D9 EB F1 83 65 FC 00 DD 55 F0
008623DAh: 89 55 F8 DF 6D F8 8B 4D 0C 8D 45 E8 50 DC 3D 80
008623EAh: 41 86 00 DD 55 F8 D9 C1 D8 C9 DD 5D E8 DD D8 DD
008623FAh: D8 E8 90 03 00 00 8B 45 14 03 F8 C1 E7 03 8B 46
Stack (04F0FD24h):
04F0FD04h: 000020D6 00000000 00000000 BAE46C48
04F0FD14h: BFE9E33B 817D708C 00000000 00000000
04F0FD24h: 00C17590 00C17540 00000000 04F0FD54
04F0FD34h: 00000000 00C17540 00000000 00C17590
04F0FD44h: 04F0FD94 04F0FD94 00861FC5 00CD8BE0
04F0FD54h: 00C175A0 00000005 0000000A 00000000
04F0FD64h: 00C17540 004384A0 00000004 47000000
04F0FD74h: 00000000 C0590000 42556EE8 3DDAADD3
04F0FD84h: 0001BA0E 00000000 C0590000 0043E6C8
04F0FD94h: 04F0FDBC 00862E30 021705B0 00000000
04F0FDA4h: 0040AAA7 04F0FEF0 00C4A35C 00000001
04F0FDB4h: 00000000 021705B0 04F0FE4C 0040A988
04F0FDC4h: 0000003C 04F0FEF0 00C4A35C 00000001
04F0FDD4h: 04F0FE00 00C2F5C8 00C0D980 00C6AFA4
04F0FDE4h: 00000003 00C6AFA4 021705B0 00000030
04F0FDF4h: 00443B28 00000000 00000728 00000000
04F0FE04h: 00000000 0109001F 00000010 7F6BAF16
04F0FE14h: 40A41B65 D69331BB 6F1CB1DE 00000010
04F0FE24h: 10001DE2 00C61020 10001E17 00000000
04F0FE34h: 04F0FE54 004365E9 004365F4 00000000
Registers:
EAX: 00CD8BE0, EBX: 00CD8C08, ECX: 000000D6, EDX: 00000005
ESI: 00C17590, EDI: FFFFFF7B, EBP: 04F0FD48, ESP: 04F0FD24
Crash location: "foo_dsp_continuator", loaded at 00860000h - 00868000h
Loaded modules:
foobar2000 loaded at 00400000h - 00451000h
ntdll loaded at 77880000h - 77901000h
KERNEL32 loaded at 77E70000h - 77F33000h
USER32 loaded at 77E00000h - 77E65000h
GDI32 loaded at 77F40000h - 77F7C000h
ole32 loaded at 77A40000h - 77B2C000h
RPCRT4 loaded at 77D20000h - 77D8E000h
ADVAPI32 loaded at 77DA0000h - 77DFD000h
COMCTL32 loaded at 77B40000h - 77BC9000h
utf8api loaded at 10000000h - 1000D000h
comdlg32 loaded at 76B00000h - 76B3E000h
SHLWAPI loaded at 77C60000h - 77CAA000h
SHELL32 loaded at 77580000h - 777CC000h
MSVCRT loaded at 78000000h - 78046000h
foo_ape loaded at 00800000h - 0081F000h
foo_cdda loaded at 00820000h - 0082E000h
foo_clienc loaded at 00830000h - 0083B000h
foo_diskwriter loaded at 00840000h - 00852000h
WINMM loaded at 77540000h - 77571000h
foo_dsp_continuator loaded at 00860000h - 00868000h
foo_dsp_extra loaded at 00870000h - 00885000h
foo_dsp_wider loaded at 00890000h - 00897000h
foo_flac loaded at 008A0000h - 008B6000h
foo_id3v2 loaded at 008C0000h - 008E6000h
MSVCP60 loaded at 780C0000h - 78121000h
foo_infobox loaded at 008F0000h - 00903000h
foo_input_std loaded at 00910000h - 009A9000h
MSACM32 loaded at 773E0000h - 773F3000h
foo_masstag loaded at 009B0000h - 009C0000h
foo_mod loaded at 009C0000h - 009C9000h
BASS loaded at 009D0000h - 00A2A000h
foo_osd loaded at 00A30000h - 00A3B000h
foo_out_dsound_ex loaded at 00A40000h - 00A49000h
DSOUND loaded at 51080000h - 510DA000h
VERSION loaded at 77810000h - 77817000h
LZ32 loaded at 75940000h - 75946000h
foo_playlistgen loaded at 00A60000h - 00A6B000h
foo_read_http loaded at 00A70000h - 00A79000h
WS2_32 loaded at 74FA0000h - 74FB3000h
WS2HELP loaded at 74F90000h - 74F98000h
foo_rgscan loaded at 00A80000h - 00A8B000h
foo_ui_std loaded at 00A90000h - 00AA7000h
foo_vis_manager loaded at 00AB0000h - 00AB8000h
foo_vorbisenc loaded at 00AC0000h - 00BBA000h
foo_web loaded at 00BC0000h - 00BD8000h
wdmaud loaded at 77530000h - 77539000h
KsUser loaded at 5EF80000h - 5EF84000h
imagehlp loaded at 77910000h - 77933000h
DBGHELP loaded at 72970000h - 7299D000h
Stack dump analysis:
Address: 00861FC5h, location: "foo_dsp_continuator", loaded at 00860000h - 00868000h
Address: 004384A0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0043E6C8h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00862E30h, location: "foo_dsp_continuator", loaded at 00860000h - 00868000h
Address: 0040AAA7h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0040A988h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00443B28h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 10001DE2h, location: "utf8api", loaded at 10000000h - 1000D000h
Symbol: "uCallStackTracker::uCallStackTracker" (+00000000h)
Address: 10001E17h, location: "utf8api", loaded at 10000000h - 1000D000h
Symbol: "uCallStackTracker::uCallStackTracker" (+00000035h)
Address: 004365E9h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004365F4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0041E3A1h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0041F171h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00438978h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389ECh, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389E4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389D0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389E4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004389D0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EF4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EE0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439F70h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EB0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439ED8h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EC4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439ED8h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EC4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004392E4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004384A0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 004384A0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EF4h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00439EE0h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 00444A00h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 0041F501h, location: "foobar2000", loaded at 00400000h - 00451000h
Address: 77E787DDh, location: "KERNEL32", loaded at 77E70000h - 77F33000h
Address: 77E91856h, location: "KERNEL32", loaded at 77E70000h - 77F33000h
Address: 77E7AE88h, location: "KERNEL32", loaded at 77E70000h - 77F33000h
Address: 0041F4D2h, location: "foobar2000", loaded at 00400000h - 00451000h
Version info:
foobar2000 v0.8
UNICODE
crash happened while playing albumgained MP3 VBR files
DSP-Chain: continuator->convert to 4ch->foo_wider
Win2k, DirectSound v2 Output
crash happened while playing albumgained MP3 VBR files
same procedure as in last reply:
new version (0.1.8) uploaded (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll)
works great now - thank you
Feature request:
Would it be possible to choose between overlapping-mode(as it is now) and old fashioned crossfading(difference to case's variant being that if seamless transition is detected, no crossfade happens - and of course the built-in gap-killer)? Maybe like a radio-knob switch in the pref-page.
- Lyx
Feature request:
Would it be possible to choose between overlapping-mode(as it is now) and old fashioned crossfading(difference to case's variant being that if seamless transition is detected, no crossfade happens - and of course the built-in gap-killer)?
Something like this (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll)?
Note: New checkbox in settings (Disable theshold...).
WONDERFUL!
Okay... I've been trying to write a crossfaded audio CD using foobar's audio CD writer and the continuator DSP.
I'm presently using the Continuator DSP and Advanced Limiter as DSPs, and I have the audio CD writer options set to use DSP, don't reset between tracks, use ReplayGain, and dither.
To test it all, I've been writing image files and mounting them in Daemon tools, then playing them through foobar.
I'm getting fade-out at the end of the tracks, but no crossfade.
Okay... I've been trying to write a crossfaded audio CD using foobar's audio CD writer and the continuator DSP.
I'm presently using the Continuator DSP and Advanced Limiter as DSPs, and I have the audio CD writer options set to use DSP, don't reset between tracks, use ReplayGain, and dither.
To test it all, I've been writing image files and mounting them in Daemon tools, then playing them through foobar.
I'm getting fade-out at the end of the tracks, but no crossfade.
I've been trying this too, but actually have been converting mpc-files to a single-file output, using only continuator as a dsp. Works very well, except for the very last track of the mix, which is cut off at the end. Found a work-around: I add a silent one-minute-mpc-track at the end of the playlist that I want to be a crossfaded mix, convert single-file-output, perfect mix as a result, last tracks does fade out now. I burn that to CD (with Feurio) and have a nice mix on CD (with one long track on it - must look for a way to have it split in songs again).
Tom.
[edit] grammar
Footure, I have tested your great plugin and tried to seamlessly playback with MP3, but failed. I know MP3 is not a naturally seamless format. If there's a way to make MP3s playback seamlessly, your plugin will be near perfect.
Regards,
Works very well, except for the very last track of the mix, which is cut off at the end.
This is the failure of the diskwriter. As i just discovered it doesn't send dsp::FLUSH on end-of-playback (ie. last track) if "don't reset dsp between tracks" is checked. As i rely on that flag, the end of the last track is cut off.
(with one long track on it - must look for a way to have it split in songs again)
Why don't you just use Convert->Run conversion? Make sure you check "Force track length..." in Continuator and burn the wavefiles without pauses between tracks.
(with one long track on it - must look for a way to have it split in songs again)
Why don't you just use Convert->Run conversion? Make sure you check "Force track length..." in Continuator and burn the wavefiles without pauses between tracks.
Thanks Cpt. Footure... seems the easy, natural solution... too blind to see that.
I'll use the simple "run conversion" next time I do a mix.
Fot the cut-off last track in the mix: the one-minute silent mpc-track as the last track of the mix does the trick.
Thanx for the Continuator, love it... no music without it here; using it on my radioshow for pre-produced mixes.
Tom.
Okay... I've been trying to write a crossfaded audio CD using foobar's audio CD writer and the continuator DSP.
.......
I'm getting fade-out at the end of the tracks, but no crossfade.
I had the same problem with foo_burminate.dll from
foobar installer.
i have re-download foo_burminate.dll from
http://foobar2000.org/components.html#foo_burninate (http://foobar2000.org/components.html#foo_burninate)
now work fineand the end of the last track is
NOT cut off.
i just ripped a seamless ambient album and encoded it with lame 3.96beta1 and 3.90.3. With both lame versions, at some trackchanges audible clicks happen. I guess thats a limitation of how mp3-encoding works.
Maybe a simple way for continuator to fix this could be to even if seamless transition is detected, a small amount of frames gets overlapped? Just an idea, i dont know if it would work.
- Lyx
Works very well, except for the very last track of the mix, which is cut off at the end.
This is the failure of the diskwriter. As i just discovered it doesn't send dsp::FLUSH on end-of-playback (ie. last track) if "don't reset dsp between tracks" is checked. As i rely on that flag, the end of the last track is cut off.
I found the bug in diskwriter.
@ zZzZzZz
line 1167 should read
if (!(b_dsp_noreset && file_ptr < files.get_count()-1))
@ all
Download the fixed diskwriter from here (http://www.ewetel.net/~axel.behrens2/foo_diskwriter.dll).
Would it be possible to define some menu-actions for enabling and disabling foo_dsp_continuator quickly? It doens't always detect seamless transitions with my MP3s, so I do want to disable this great plug-in once in a while.
um I think i have a bug to report:
if there is no next track (i.e. you're listening to the last track in a playlist - i don't use non-default play orders) there will be a skip near the end of the that track. presumably continuator is getting confused looking for a next track. can anyone else confirm? i'm pretty sure it happens every time here.
thanks, otherwise i've grown to love this plugin, cheers.
edit: i'm using continuator v0.1.8 and foobar v0.8 final.
edit2: after reading the post above, i don't think continuator ever detects gapless mp3s for me, it always crossfades, any ideas why? yes i have "disable overlapping..." selected. this is a different issue sorry.
@ CyberSnooP and Smiff
It doens't always detect seamless transitions with my MP3s
after reading the post above, i don't think continuator ever detects gapless mp3s for me, it always crossfades, any ideas why? yes i have "disable overlapping..." selected.
Detecting seamless transitions with mp3's is somewhat tricky, because the encoding and decoding process adds new signal samples (a gap) that destroy the seamless transition. You (i.e. me) have to guess where the original ending and starting points have been and then guess again if that was a seamless transition.
Anyway, i know there is room for improvement with my seamless transition detecting, but i don't have much time now, sorry.
@CyberSnooP
there will be a skip near the end of the that track
try a longer output buffer length (preferences->playback->output)
@ Lyx
Maybe a simple way for continuator to fix this could be to even if seamless transition is detected, a small amount of frames gets overlapped?
Yes, that could fix it, but again, no time yet.
Is it possible to make it crossfade when changing tracks manually?
not with foo-continuator - but with cpt footure's other plugin "directsound extended 2.5".
- Lyx
Okey, thanks for the quick answer
but with cpt footure's other plugin "directsound extended 2.5".[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=229234")
I woudn't call it 'my' plugin, since i only took v2.0 from the SDK and made some extensions.
[a href="http://www.ewetel.net/~axel.behrens2/foo_out_dsound_ex2.zip]download[/url]
Detecting seamless transitions with mp3's is somewhat tricky, because the encoding and decoding process adds new signal samples (a gap) that destroy the seamless transition.
[a href="index.php?act=findpost&pid=198393"][{POST_SNAPBACK}][/a]
You are referring to MP3 files which lack encoder delay/padding information, correct?
yup
Cpt.,
Great work--I've been looking for something like this for a while now.
3 Questions:
1. The last song in a playlist will end just a little early-especially noticable with a song that has a long fade out. I've tried increasing the buffer for the Wave Out output, but it still happens. Due to the drivers of the professional audio card I've got, Wave Out is the only output I can use. Any ideas?
2. No chance of making it fade-while-seek or fade on manual change within this plugin?
3. It sounds like the fade you've implemented is a linear fade. Any chance of having some control over that? I think long logarithmic fade is the most 'natural' sounding for most fades.
Many thanks on a great plugin.
ears
Hi,
sorry for the delay, i'm quite busy these days.
Q1:
I will fix this if i find some time.
Q2:
Sorry, no. This has to be covered by output plugins.
Q3:
Unless you don't check 'Force fade-out to desired fade rate', there is no fade at all. If checked, it is assured, that the ending track will fade with 'at least' the desired fade rate, which is in dB/sec and hence logarithmic. No correction is made if the ending tracks 'natural' fade is 'quicker'.
Bye.
Hi,
fixed the last-track-skipping-near-end-bug: download Continuator v0.2.2 (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll)
bye.
BTW: i can't edit my account information or add a new plugin on the third party plugins page. any action following a successful login seems to take me back to the login page. happens with Opera 7.5 and IE 6. any ideas? and yes, cookies are enabled.
Thanks for the update.
The new plugin is on the third party plugins page now.
It crashes very often between 2 tracks: the first is a vbr at 200kbps average, the 2nd a 40kbps cbr 22050Hz.
[span style='font-size:8pt;line-height:100%']Illegal operation:
Code: C0000005h, flags: 00000000h, address: 7800124Ch
Access violation, operation: read, address: 014BB000h
Call path:
playback_core_i::g_thread_func=>playback_core_i::thread_func=>dsp::run
This is the first crash logged by this instance.
Code bytes (7800124Ch):
7800120Ch: 78 8B C6 5F 5E C3 55 8B EC 57 56 8B 75 0C 8B 4D
7800121Ch: 10 8B 7D 08 8B C1 8B D1 03 C6 3B FE 76 08 3B F8
7800122Ch: 0F 82 65 20 01 00 F7 C7 03 00 00 00 75 1B C1 E9
7800123Ch: 02 83 E2 03 83 F9 08 73 07 FF 24 8D 44 13 00 78
7800124Ch: F3 A5 FF 24 95 68 13 00 78 8B C7 BA 03 00 00 00
7800125Ch: 83 E9 04 72 0C 83 E0 03 03 C8 FF 24 85 34 13 00
7800126Ch: 78 FF 24 8D 78 13 00 78 23 D1 8A 06 88 07 8A 46
7800127Ch: 01 C1 E9 02 88 47 01 83 C6 02 83 C7 02 83 F9 08
Stack (0365FD5Ch):
0365FD3Ch: 77883618 FFFFFFFF 0012F9E8 77E77738
0365FD4Ch: 00000000 00000003 780153F4 780050CF
0365FD5Ch: 0145C2D8 FFFCB749 0365FD94 009B1EAE
0365FD6Ch: 02813078 014B0FD0 FFE5BA48 0000002F
0365FD7Ch: 014C69E0 0145C2D8 02813078 014C69E0
0365FD8Ch: 014B0FD0 000348E6 0365FDB8 009B181C
0365FD9Ch: 014C69E0 00000000 014C69E0 0145C2D8
0365FDACh: 0142600C 00000001 00035D54 0365FDE4
0365FDBCh: 009B345D 00000000 01FB31E8 00000000
0365FDCCh: 0040ABB3 0365FEFC 014183CC 00000000
0365FDDCh: 00000000 01FB31E8 0365FE70 0040AA69
0365FDECh: 0000003C 0365FEFC 014183CC 00000000
0365FDFCh: 0365FE28 00000000 01426008 00000000
0365FE0Ch: 00000002 00000004 01FB31E8 00000020
0365FE1Ch: 00444904 00000000 0365FE44 00000000
0365FE2Ch: 00000000 0109001F 00005622 45BAE3C0
0365FE3Ch: 400810B1 E6C5ACBA A26BB0CE 00420EA6
0365FE4Ch: 01DA48D0 0000002F 00000001 00005622
0365FE5Ch: 0365FED8 0365FEFC 00420E71 0365FED8
0365FE6Ch: 00000000 0365FFA4 0042028A 0365FEFC
Registers:
EAX: 0130CA18, EBX: FFE5BA48, ECX: 3FF94686, EDX: 00000000
ESI: 014BB000, EDI: 0281D0A8, EBP: 0365FD64, ESP: 0365FD5C
Failed to get module/symbol info.
Version info:
foobar2000 v0.8.3
UNICODE
[/span]
Would it be possible to define some menu-actions for enabling and disabling foo_dsp_continuator quickly? It doens't always detect seamless transitions with my MP3s, so I do want to disable this great plug-in once in a while.
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=196249")
It crashes very often between 2 tracks: the first is a vbr at 200kbps average, the 2nd a 40kbps cbr 22050Hz.
[a href="index.php?act=findpost&pid=236223"][{POST_SNAPBACK}][/a]
Hi,
version 0.2.3 is [a href="http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll]uploaded[/url]:
- menu item added (Components -> Continuator -> Enabled)
- 'new-track-has-different-samplerate' bug fixed
Enjoy
Wow. This is a great plug-in. It was the thing that finally convinced me to make the switch from Winamp (and the great sqrsoft crossfader). Well done, Cpt. Footure.
Couple of suggestions for future development:
1. It's great that you've included the 'Disable fade if seamless join' feature. However, the only problem I have with this plug-in is when a track that is from a continuous (live or mix) album ends, the crowd (or whatever) cuts out hard at the end. Perhaps you could include an option for if the outgoing (and incoming) track has sound right up to the end, then do a forced fade on it from <specified> seconds out.
2. Ok, I'm getting really picky now, but it's worth a mention. I find the crossfading slightly annoying on tracks that have a really distinct sudden end. Musically speaking, the new track starts too soon. It needs a little 'breathing space'. Perhaps you could complicate the algorithm a little so that if the song has a large change in level right at the end (say, more than 10db drop within 1/2 second), then let the next track start a little bit (user specified) later.
Cheers. Loving foobar (and this plug-in of course)
Hi,
good to hear that i could help to save another soul
If one day i will find some time to continue the Continuator, your suggestions will be remembered.
Bye.
ps: Is there any interest in the source code, so that my lack of spare time doesn't matter anymore?
Great plugin! I'd like to see more updates to it.
I've been having a problem recently with it, where it sometimes crashes foobar2000 if I try to seek through a song alot. It rarely crashes if I just try to skip forward a few seconds, but if I make one big jump it seems to crash it.
BTW, is there any other similar crossfading plugin being developed?
Great plugin! I'd like to see more updates to it.
I've been having a problem recently with it, where it sometimes crashes foobar2000 if I try to seek through a song alot. It rarely crashes if I just try to skip forward a few seconds, but if I make one big jump it seems to crash it.
BTW, is there any other similar crossfading plugin being developed?
[a href="index.php?act=findpost&pid=260558"][{POST_SNAPBACK}][/a]
i love this plugin, but it does crash on seeking. any updates or bug fixes??
Great plugin! I'd like to see more updates to it.
I've been having a problem recently with it, where it sometimes crashes foobar2000 if I try to seek through a song alot. It rarely crashes if I just try to skip forward a few seconds, but if I make one big jump it seems to crash it.
BTW, is there any other similar crossfading plugin being developed?
[a href="index.php?act=findpost&pid=260558"][{POST_SNAPBACK}][/a]
i love this plugin, but it does crash on seeking. any updates or bug fixes??
[a href="index.php?act=findpost&pid=268298"][{POST_SNAPBACK}][/a]
I don't mean to pile on, but I've been having FB2K crashing problems with an instance I'm using to stream with Oddcast v.3.0.3 and I think I've narrowed down Continuator as the culprit, even though Oddcast is listed as the component that takes the exception. The combination causes intermittent crashes on song or playlist changes. I've been working with Oddsock to try to narrow this down, and created a bare FB2K instance to build up to try to isolate this. I've just removed the Continuator plugin from the mix to see if stability returns. If anyone would like more info (Cpt. Footure?), let me know.
First of all, great job, Cpt. Footure ! Your plugin is the element that made me definitely switch from Winamp to fb2k !!
aharden> I also broadcast with continuator enabled and had problems at the beginning. Now that I use this config
Please let us know if you can do it...
Regards.
aharden> I also broadcast with continuator enabled and had problems at the beginning. Now that I use this config
[..]
I have no crash problems. That probably means that the code in threshold control or fadeout rate control is involved in these crashes, but I don't know more than that.
Thanks for the reply. Disabling the threshold control is something I definitely haven't done, since (in my opinion) the plugin would be lobotomized as a result. The fact that the plugin is threshold-based (like the SQRSoft Winamp crossfader) is what's made it so appealing to me.
Since removing Continuator from the picture, I'm actually learning to appreciate the "Music Choice" vibe one gets from no crossfades. But I would enable it again in a heartbeat if the conflicts with Oddcast were ironed out.
Small request: The current command to enable this plug-in is a toggle. Could you make it so that it has a seperate 'enable' and 'disable' command, as this would make it easier to control via hotkeys and the command line?
Cheers,
C
Actually, having a toggle is easier for hotkeys, because that way you only need one key instead of two - but nothing against having the choice
- Lyx
Actually, having a toggle is easier for hotkeys, because that way you only need one key instead of two - but nothing against having the choice
[a href="index.php?act=findpost&pid=273113"][{POST_SNAPBACK}][/a]
Except when you forget what it was previously set on when you restart playback and you have to look up the menu to see. And when you have it setup to be triggered in conjunction with other settings (such as track gain vs album gain, or shuffle vs default), and it gets out of sync with how you want it to be. But you're right, having the option would be good.
Hi guys,
version 0.2.4 is uploaded (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll):
- added enable/disable menu items
- tried to lower system (cpu) resources on track changes to prevent crash when used together with oddcast (please try if that helps)
Enjoy
thanks for the update.
Here's an idea which i have been thinking about for a while: I'm using continuator or crossfader sometimes to quickly create mixes from submitted tracks. It would be great if continuator had 3 modes: punch-in (its main feature), full-overlap and crossfade. Then, it would be cool if one could give a track a CONTINUATOR-tag, which can have the value "punch", "overlap" or "crossfade". Before doing the transition to the next track, continuator woud check if the current file has a continuator-tag and if yes let the tag-value override the default-behaviour. So, if the current track would have a "crossfade"-value in the tag, then continuator would crossfade from the current into the next track.
This would be great for quickly creating mixes or amateur-DJing - but i dont know if you consider it in the scope of your plugin.
- Lyx
Heh, thanks for thinking about us again Cpt. Footure
The "toggle" menu item still a little check sign on it when the plugin is activated. It seems that you forgot to remove the "checkable" property on this one (the former "enable" menu item).
Speaking of amateur DJing, do you think it's possible to add an APPLY button, as I proposed in my last post ? That's because when I want to change a parameter value, I have to stop the playback for my change to take effect. It would be a real plus for live mixing to be able to change values while playing
Hi guys,
version 0.2.4 is uploaded (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll):
- added enable/disable menu items
- tried to lower system (cpu) resources on track changes to prevent crash when used together with oddcast (please try if that helps)
Enjoy
[a href="index.php?act=findpost&pid=294837"][{POST_SNAPBACK}][/a]
Thanks! I had problems with Continuator combined with Oddcast and removed it a while ago. I'll get the new version installed and let you know if the new version has resolved the problems I saw.
I cannot start fb2k with this. I'm on w2ksp4. See crash log below.
BTW, can you make it working with foo_skip? I posted a problem report here: http://www.hydrogenaudio.org/forums/index....ndpost&p=293635 (http://www.hydrogenaudio.org/forums/index.php?showtopic=30361&view=findpost&p=293635)
(foo_skip does skip a track if a tag is matching. But continuator does always start some milliseconds, depending on its configuration)
<snipped>, bug has been fixed, http://www.hydrogenaudio.org/forums/index.php?showtopic=18703&view=findpost&p=295179
Heh, thanks for thinking about us again Cpt. Footure
I've been thinking about 'you' all the time (well, almost).
The "toggle" menu item still a little check sign on it when the plugin is activated. It seems that you forgot to remove the "checkable" property on this one (the former "enable" menu item).
This check sign should indicate the current state.
Speaking of amateur DJing, do you think it's possible to add an APPLY button, as I proposed in my last post ? That's because when I want to change a parameter value, I have to stop the playback for my change to take effect. It would be a real plus for live mixing to be able to change values while playing
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=294867")
?
All settings except 'Maximum overlap length' are applyed instantly, ie. on next track change.
@squeller
bug fixed in version [a href="http://www.ewetel.net/~axel.behrens2\foo_dsp_continuator.dll]0.2.5[/url]
@lyx
I'll be thinking about your CONTINUATOR-tag suggestion.
@squeller
bug fixed in version 0.2.5 (http://www.ewetel.net/~axel.behrens2\foo_dsp_continuator.dll)
@lyx
I'll be thinking about your CONTINUATOR-tag suggestion.
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=295179")
Thanks cpt footure! Works fine. I know I'm pissing you off, but may I ask for you opinion on:
BTW, can you make it working with foo_skip? I posted a problem report here: [a href="http://www.hydrogenaudio.org/forums/index....ndpost&p=293635]http://www.hydrogenaudio.org/forums/index....ndpost&p=293635[/url]
(foo_skip does skip a track if a tag is matching. But continuator does always start some milliseconds, depending on its configuration)
?
@lyx: great suggestion
I know I'm pissing you off, but may I ask for you opinion on:
foo_skip
Don't worry, i'm great in ignoring irrelevant input .
But I will have a look at it.
Refined version of the continuator-tag proposal:
CONTINUATOR-tag value | Behaviour on transition to next track
-----------------------+-----------------------------------------
off | do nothing
gapkill | trim silence only
overlap | do simple overlapping without searching for a punch-in point
punchin | search for punch-in point and overlap there (continuator's main-feature)
crossfade | crossfade to next track
-----------------------+-----------------------------------------
Even cooler, but maybe too much work to implement: when using overlap or crossfade, then be able to specify the transition-length in the continuator tag(so, length of crossfade/overlapping) like for example "overlap,5000" would mean "do a 5seconds overlap at transition to next track".
Together with foo_quicktag(and maybe a continuator-column in one's formatting) this feature could be used on the fly easily :)
- Lyx
bug fixed in version 0.2.5 (http://www.ewetel.net/~axel.behrens2\foo_dsp_continuator.dll)
[a href="index.php?act=findpost&pid=295179"][{POST_SNAPBACK}][/a]
That link gives a 404
That link gives a 404
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=295255")
[a href="http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll]http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll[/url]
Speaking of amateur DJing, do you think it's possible to add an APPLY button, as I proposed in my last post ? That's because when I want to change a parameter value, I have to stop the playback for my change to take effect. It would be a real plus for live mixing to be able to change values while playing :cool:
[a href="index.php?act=findpost&pid=294867"][{POST_SNAPBACK}][/a]
?
All settings except 'Maximum overlap length' are applyed instantly, ie. on next track change.
Hehe ^^" I was actually requesting it because of that very setting, since I tend to play with overlapping tracks :b Can it be modified so that this one is updated as well ?
On the other hand, if you decide to follow what Lyx has just proposed, I'd be satisfied as well, since it allows even more on-the-fly tinkering with continuator ;)
I don't know what's up with my settings but my tracks don't crossfade. The end of the mp3 will fade, but at the end, the next song starts right in. The crossfader plugin that comes in the foobar iinstallation works fine.
Any clues?
Hi guys,
version 0.2.4 is uploaded (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll):
- added enable/disable menu items
[a href="index.php?act=findpost&pid=294837"][{POST_SNAPBACK}][/a]
Awesome. Thanks a bunch. That'll make my automation scripts much more useful.
(http://www.mundogasol.com/foro/banana.gif)
C
CONTINUATOR-tag value | Behaviour on transition to next track
-----------------------+-----------------------------------------
off | do nothing
gapkill | trim silence only
overlap | do simple overlapping without searching for a punch-in point
punchin | search for punch-in point and overlap there (continuator's main-feature)
crossfade | crossfade to next track
-----------------------+-----------------------------------------
Even cooler, but maybe too much work to implement: when using overlap or crossfade, then be able to specify the transition-length in the continuator tag(so, length of crossfade/overlapping) like for example "overlap,5000" would mean "do a 5seconds overlap at transition to next track".
We'd need a better foo_quicktag then...
The problem with foo_quicktag is, you will not be able to concatenate to your tag. (e.g. you can not add ",5000" to an existing "overlap")
I don't know what's up with my settings but my tracks don't crossfade. The end of the mp3 will fade, but at the end, the next song starts right in. The crossfader plugin that comes in the foobar iinstallation works fine.
Any clues?
[a href="index.php?act=findpost&pid=295363"][{POST_SNAPBACK}][/a]
Maybe it's a seamless transition? Or it's (falsely) detected as one. Did you try to uncheck 'Disable track overlapping...'? Or maybe your threshold setting was too low.
btw: At the moment Continuator does no fade-in. It just starts the new track at the point where the old track reaches a specific threshold.
Hehe ^^" I was actually requesting it because of that very setting, since I tend to play with overlapping tracks :b Can it be modified so that this one is updated as well ?
I'll see if i can do that.
Refined version of the continuator-tag proposal:
CONTINUATOR-tag value | Behaviour on transition to next track
-----------------------+-----------------------------------------
off | do nothing
gapkill | trim silence only
overlap | do simple overlapping without searching for a punch-in point
punchin | search for punch-in point and overlap there (continuator's main-feature)
crossfade | crossfade to next track
-----------------------+-----------------------------------------
Even cooler, but maybe too much work to implement: when using overlap or crossfade, then be able to specify the transition-length in the continuator tag(so, length of crossfade/overlapping) like for example "overlap,5000" would mean "do a 5seconds overlap at transition to next track".
Together with foo_quicktag(and maybe a continuator-column in one's formatting) this feature could be used on the fly easily
- Lyx
[a href="index.php?act=findpost&pid=295250"][{POST_SNAPBACK}][/a]
Good proposal, i'm pretty sure that i'll implement it sooner or later.
I know you all would prefer 'sooner', but please be patient.
btw: At the moment Continuator does no fade-in. It just starts the new track at the point where the old track reaches a specific threshold.
[a href="index.php?act=findpost&pid=295386"][{POST_SNAPBACK}][/a]
Oh. If thats the case, then the plugin works perfectly!
Thanks
We'd need a better foo_quicktag then...
The problem with foo_quicktag is, you will not be able to concatenate to your tag. (e.g. you can not add ",5000" to an existing "overlap")
[a href="index.php?act=findpost&pid=295384"][{POST_SNAPBACK}][/a]
Not necessary - you can just create submenus in quicktag to overwrite the previous tag-value completely:
mainmenu:
remove tag
off
trim silence
overlap
punch-in
crossfade
overlap and crossfade would have submenus with a selection of timespans... these submenu options would then just overwrite the previous value with i.e. "overlap,5000". So, i don't see any reason for concetanating values. From a coders POV it may be the more "clean" way to do it, but from a practical POV it is not necessary.
- Lyx
Not necessary - you can just create submenus in quicktag to overwrite the previous tag-value completely
true
Thanks cpt footure! Works fine. I know I'm pissing you off, but may I ask for you opinion on:
BTW, can you make it working with foo_skip? I posted a problem report here: http://www.hydrogenaudio.org/forums/index....ndpost&p=293635 (http://www.hydrogenaudio.org/forums/index....ndpost&p=293635)
(foo_skip does skip a track if a tag is matching. But continuator does always start some milliseconds, depending on its configuration)
?
[a href="index.php?act=findpost&pid=295184"][{POST_SNAPBACK}][/a]
Hi,
continuator is not to blame for this behaviour. The problem lies within the (crossfading?, maybe DirectSound v2.5? Shit, that's me also) output plugin. foo_skip seems to 'hit' the skip button just after a new track has started. I'm not sure if i can do anything about it.
I wonder if I'm the only one who's not attracted to fixed strings.
Why make it depend on a specific tag, and specific contents? It could be made configurable through TAGZ, which would be worth it, IMHO.
- Let the user choose if he wants %CONTINUATOR% or %FADING%
- Let the user choose what to check for. $right(%FADE LENGTH%,4)
I wonder if I'm the only one who's not attracted to fixed strings.
Why make it depend on a specific tag, and specific contents? It could be made configurable through TAGZ, which would be worth it, IMHO.
- Let the user choose if he wants %CONTINUATOR% or %FADING%
- Let the user choose what to check for. $right(%FADE LENGTH%,4)
[a href="index.php?act=findpost&pid=296784"][{POST_SNAPBACK}][/a]
Yeah cool - one more ambigious tag-standard, so that public formatting-strings cannot support such features. I on my side can say, that if the tag-name/value becomes configurable, then i (and probably every other public formatting-strings author) will not support it for obvious reasons - because we CANNOT.
Very bad idea IMHO.
- Lyx
/me shrugs.
You have the masstagger, so if you encounter tags you don't like, you can always change them your way.
Who cares if someone else's formatting doesn't support your tags? You? You are free to hack at the formatting, and you'll have the freedom of not being forced to change your tags.
Who cares if someone else's formatting doesn't support your tags? You? You are free to hack at the formatting, and you'll have the freedom of not being forced to change your tags.
[a href="index.php?act=findpost&pid=296801"][{POST_SNAPBACK}][/a]
FYI, there are many fb2k users, who do know almost nothing about TAGZ-hacking and rely on ready-for-use public formatting strings. There are also many people who aren't very familiar with the masstagger for the same reasons.
Not every fb2k-user is a programmer/scripter. Do you propose to not care about those? Also, even tagz-coders may prefer a situation where "it just works" instead of them having to hack the formatting, because of incompatibility caused by an ambigious tag-standard.
- Lyx
Customization is good, but it's important to have sane default values.
Formatting string coders can rely upon the default values of foo_dsp_continuator_tagz if they want.
I didn't say that everything should be barebone, with the burden of formatting being pushed on to potential newbies.
Customization is good, but it's important to have sane default values.
[a href="index.php?act=findpost&pid=296806"][{POST_SNAPBACK}][/a]
Can you name a situation, where your proposed customization is useful? Something which outweigths the mentioned disadvantages?
Also, making it configurable adds some more options to the continuator preferences. As mentioned somewhere else, every unneeded option is a flaw, not a feature - so is there some benefit which outweights the added complexity?
- Lyx
*sigh*
I don't want to use CONTINUATOR. I want to use FADING or something else which *I* think is approriate. I thought I'd already mentioned that TAGZ can be useful for me in this case.
You might have noticed before that I regard customizability as a strong bonus, not as a flaw. I don't think I'll change my mind any time soon.
I don't want to use CONTINUATOR. I want to use FADING or something else which *I* think is approriate.
[a href="index.php?act=findpost&pid=296808"][{POST_SNAPBACK}][/a]
In other words, you propose to make continuator-preferences more complex and introduce the risk of incompatibility, just because you or someone else may not like the NAME of the tag?
Sounds like it could be a better idea to discuss and agree on a tag-name which is okay to most instead.
- Lyx
"Come here. Knock knock."
"Who's there?"
"Control freak. Now you say, 'Control freak who?'"
Well, yes.
OK, so what will it be? CONTINUATOR_MODE CONTINUATOR_FADELENGTH, akin to REPLAYGAIN? FADING::MODE FADING::LENGTH, or CONTINUATOR.MODE CONTINUATOR.FADES making use of Vorbis comments?
"Come here. Knock knock."
"Who's there?"
"Control freak. Now you say, 'Control freak who?'"
Some control and "consensus" is necessary to allow interoperability and compatibility. You wouldn't be able to post on this forum, without an agreement how webpages are described. Replaygain would be very frustrating without an agreed scheme. People wouldn't be able to communicate efficiently without established languages. Playcounter isn't supported in most formatting-schemes because of its ambigious format. If all those folks involved in the mentioned agreements are control-freaks is a matter of opinion.
OK, so what will it be? CONTINUATOR_MODE CONTINUATOR_FADELENGTH, akin to REPLAYGAIN? FADING::MODE FADING::LENGTH, or CONTINUATOR.MODE CONTINUATOR.FADES making use of Vorbis comments?
[a href="index.php?act=findpost&pid=296817"][{POST_SNAPBACK}][/a]
Why create multiple tags for it? I mean, as shown in my proposal, one tag is enough to implement it. It could even be extended if necessary in the future, because the options are just seperated with commas - so as long as the order remains unchanged, it can be extended in the future.
- Lyx
You wouldn't be able to post on this forum, without an agreement how webpages are described.
Bad analogy. HTML is a machine language. Tags are for natural languages.
Playcounter isn't supported in most formatting-schemes because of its ambigious format.
Playcounter is probably unsupported because it's unpopular; plain and simple.
Why create multiple tags for it? I mean, as shown in my proposal, one tag is enough to implement it.[a href="index.php?act=findpost&pid=296821"][{POST_SNAPBACK}][/a]
To better describe the contents. Would you want your REPLAYGAIN tags to contain +11,0.49385930,+10,0.58303389? (edit: Plus, it will work nicely with foo_quicktag, I think.)
The principle here is, "One tag, for one thing." We want things to be userfriendly, and consistency is useful, isn't it?
PS. I was implying that *I* was a control freak when it comes to tagging.
In other words, you propose to make continuator-preferences more complex and introduce the risk of incompatibility, just because you or someone else may not like the NAME of the tag?[a href="index.php?act=findpost&pid=296813"][{POST_SNAPBACK}][/a]
Let's look at this again.
How bad is complexity? Unnecessary complexity is bad, I agree. Nevertheless, complexity can be ignored. If you don't understand it, you don't need to touch it. Everything in foobar2000 is pretty straight-forward, if you know what they mean, and nobody forces you to understand it.
Now, about the risk of incompatibility. How big is it?
If you assume that TAGZ writers will want to write for the largest audience, they'll write formatting for foo_dsp_continuator_tagz's default settings.
People who don't know how to use TAGZ will just use the defaults, and they'll be fine.
People who do know how to use TAGZ will be able to deal with incompatibilty. They have the tools, and they'll have the knowledge. So where's the risk?
In other words, you propose to make continuator-preferences more complex and introduce the risk of incompatibility, just because you or someone else may not like the NAME of the tag?[a href="index.php?act=findpost&pid=296813"][{POST_SNAPBACK}][/a]
Let's look at this again.
How bad is complexity? Unnecessary complexity is bad, I agree. Nevertheless, complexity can be ignored. If you don't understand it, you don't need to touch it. Everything in foobar2000 is pretty straight-forward, if you know what they mean, and nobody forces you to understand it.
Now, about the risk of incompatibility. How big is it?
If you assume that TAGZ writers will want to write for the largest audience, they'll write formatting for foo_dsp_continuator_tagz's default settings.
People who don't know how to use TAGZ will just use the defaults, and they'll be fine.
People who do know how to use TAGZ will be able to deal with incompatibilty. They have the tools, and they'll have the knowledge. So where's the risk?
[a href="index.php?act=findpost&pid=296992"][{POST_SNAPBACK}][/a]
Personally, if I were to choose between the formatting options, I would go with Lyx's option. It seems silly to have not one but multiple tags--and be continuously adding in new values as foo_continuator adds new functionalities. Keeping everything relevant to continuator inside one tag specifically designed *for* continuator makes much more sense than having 10 extra tags attached to each of thousands of mp3's to fill the required information for *one* plugin.
On a side note though, neither option really appeals to my personal collection. I'm one of those people who keeps the tags on my mp3s limited to:
artist;title;album;tracknumber;date;genre;album artist
What I would be very much interested in is some kind of designation for a particular playlist to be played in a particular way. IE, that mix playlist/tab you made for a party should be able to be set to "crossfade for 10 seconds" and any mp3s contained within would be played accordingly. While I see the reason and necessity for a tag designating the function of each mp3 as it's played, I think the *vast* majority of users would be much happier being able to create a playlist out of currently existing mp3s and play them in a specific manner without updating the actual tag-data of each mp3 (which may be singles from dozens of albums). Then, when I close foobar and open it up again another week, foobar still remembers how to crossfade for the playlist I've created. This is especially useful to those who play mp3's across a network and don't have write-access to write new tag data, but want to quickly and easily assemble playlists that continuate in a specific manner.
Hm. On second thought, if tag-reading is for quick mixes of small playlists, it won't matter what I put in the tags; I won't be keeping the tagz for long.
On a side note though, neither option really appeals to my personal collection. I'm one of those people who keeps the tags on my mp3s limited to:
artist;title;album;tracknumber;date;genre;album artist
What I would be very much interested in is some kind of designation for a particular playlist to be played in a particular way. IE, that mix playlist/tab you made for a party should be able to be set to "crossfade for 10 seconds" and any mp3s contained within would be played accordingly. While I see the reason and necessity for a tag designating the function of each mp3 as it's played, I think the *vast* majority of users would be much happier being able to create a playlist out of currently existing mp3s and play them in a specific manner without updating the actual tag-data of each mp3 (which may be singles from dozens of albums). Then, when I close foobar and open it up again another week, foobar still remembers how to crossfade for the playlist I've created. This is especially useful to those who play mp3's across a network and don't have write-access to write new tag data, but want to quickly and easily assemble playlists that continuate in a specific manner.
[a href="index.php?act=findpost&pid=296996"][{POST_SNAPBACK}][/a]
I agree, however, that info still needs to be stored somewhere. The playlist-files themselves obviously are a no-no for that purpose(to not break their format). DB-only entries would be nice, but fb2k doesn't support that yet. That leaves us either with a seperate config-file for continuator, or plain simple tags. Tags have the advantage, that a playlist-formatting can make use of that info (after all, when creating such a playlist which you describe, it would be useful to *see* which tracks have which settings.)
- Lyx
I agree, however, that info still needs to be stored somewhere. The playlist-files themselves obviously are a no-no for that purpose(to not break their format). DB-only entries would be nice, but fb2k doesn't support that yet. That leaves us either with a seperate config-file for continuator, or plain simple tags. Tags have the advantage, that a playlist-formatting can make use of that info (after all, when creating such a playlist which you describe, it would be useful to *see* which tracks have which settings.)
- Lyx
[a href="index.php?act=findpost&pid=297044"][{POST_SNAPBACK}][/a]
Not really; For example, all the configuration info for foo_pod is stored in foobar2000.cfg (iPod (foo_pod) for playlist name, how to send data, etc). All you'd need to do is maintain a small list of the current playlists and their behaviors, just slapped right into foobar2000.cfg and associated with foo_continuator
http://www.hydrogenaudio.org/forums/index....st=0&p=297717&# (http://www.hydrogenaudio.org/forums/index.php?showtopic=34030&st=0&p=297717&#)
Hi guys,
i've uploaded continuator version 0.3.0 (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll), which adds the following new features:
- control through CONTINUATOR tag (see below)
- additional delay dependant on speed of volume drop, to give tracks with sudden ends some 'air', before the next track starts (currently not configurable)
- new menu items 'Settings...' and 'Override settings by CONTINUATOR-tag'
CONTINUATOR tag:
i chose to support three tag values with optional parameter
tag value | description
---------------|------------------------------------------------------------------
overlap[,n] | track overlapping dependant on volume,
| optional parameter n: threshold, rms drop in dB (range 0-100)
|
crossfade[,t] | track crossfading,
| optional parameter t: time in ms (range 0-'Maximum overlap length')
|
off | do nothing
notes:
- if you omit the parameter, the value from the settings is used
- case doesn't matter
- crossfade curves are currently not configurable
examples:
gap killing:
overlap,60
normal operation:
overlap,6
overlap,12
10 sec crossfade:
crossfade,10000
Enjoy!
Excellent !! I'll play with that new version during my soon-to-come live broadcast and I'll send you my feedback...
Great, Cpt. Footure,
just one thing: The 'Toggle State' command item now doesn't show a checkbox next to it when it is used in a menu.
And one suggestion: Nice of you to implement the extra tag info, but I would strongly recommend that you concentrate on automated intelligence instead, as most of us have music libraries sufficiently large that the thought of manually tagging thousands of songs with crossfade data is unthinkable. IMHO, of course.
Cheers,
C
just one thing: The 'Toggle State' command item now doesn't show a checkbox next to it when it is used in a menu.
The checkmark is next to the current state instead.
And one suggestion: Nice of you to implement the extra tag info, but I would strongly recommend that you concentrate on automated intelligence instead, as most of us have music libraries sufficiently large that the thought of manually tagging thousands of songs with crossfade data is unthinkable. IMHO, of course.
I agree. Do you have any concrete suggestions as to where the intelligence should be amplified?
Bye
just one thing: The 'Toggle State' command item now doesn't show a checkbox next to it when it is used in a menu.
The checkmark is next to the current state instead.
Yeah, but I've just got a 'Toggle state' item in my systray menu, and now I can't tell at a glance whether it's enabled or not. Seems silly to add Enable/Disable menu items just for monitoring purposes.
And one suggestion: Nice of you to implement the extra tag info, but I would strongly recommend that you concentrate on automated intelligence instead, as most of us have music libraries sufficiently large that the thought of manually tagging thousands of songs with crossfade data is unthinkable. IMHO, of course.
I agree. Do you have any concrete suggestions as to where the intelligence should be amplified?
Basically, the only real problem I have is with tracks that come from live albums or continuous-flow compilations. Because they carry on loud all the way to the end, you get a really ugly sudden stop as the next track slams in. I think it would be good to have a way of automatically determining whether a track is still above the volume threshold within (say) a few ms of the end of the file, and in such cases force a fade out starting a pre-determined number of seconds before the end. The incoming track could then use this forced fade to determine its inpoint.
This would be my number 1 priority improvement.
Great plug-in though; good to know it's still in active development. Remember this was the plug-in that ultimately convinced to make the switch over from Winamp.
Take care,
C
Yeah, but I've just got a 'Toggle state' item in my systray menu, and now I can't tell at a glance whether it's enabled or not. Seems silly to add Enable/Disable menu items just for monitoring purposes.
I see, you'll get your checkmark back.
Basically, the only real problem I have is with tracks that come from live albums or continuous-flow compilations. Because they carry on loud all the way to the end, you get a really ugly sudden stop as the next track slams in. I think it would be good to have a way of automatically determining whether a track is still above the volume threshold within (say) a few ms of the end of the file, and in such cases force a fade out starting a pre-determined number of seconds before the end. The incoming track could then use this forced fade to determine its inpoint.
This would be my number 1 priority improvement.
Great plug-in though; good to know it's still in active development. Remember this was the plug-in that ultimately convinced to make the switch over from Winamp.
Ok, consider it done. We don't want to lose you again to 'The Dark Side'
Actually I did the broadcast in a hurry so I hadn't had the time to plan which tracks to play. I just used the standard behaviours, without the new tagging options. However, the plugin seems to be stabler than ever I'll let you know if I find something more to add !
Hi guys,
i've uploaded continuator version 0.3.5 (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll), which adds the following new features:
- the two modes overlap and crossfade are now selectable from the UI
- configurable fade-out and fade-in curves
- fade length independent from crossfade resp. overlap length
- option to apply fade-out only when there's audio up to the end of the track ie. when the rms level doesn't drop below the threshold setting
- toggle checkmark for Carlos
Enjoy!
Wow, this looks excellent, will test it soon, many thanks!
You're a legend, Cap.
Off to try it now...
Guys?
No bugs found?
No comments?
No suggestions?
Speechless regarding the extraordinary features and outstanding stability?
Or busy testing 0.9?
No bugs found. Completely satisfied with the current features. Waiting for the 0.9 SDK so that continuator can be compiled for 0.9.
:-)
- Lyx
Guys?
No bugs found?
No comments?
No suggestions?
Speechless regarding the extraordinary features and outstanding stability?
Or busy testing 0.9?
[a href="index.php?act=findpost&pid=317801"][{POST_SNAPBACK}][/a]
Yes
No bugs found
&
Speechless regarding the extraordinary features and outstanding stability
Guys?
No bugs found?
No comments?
No suggestions?
Speechless regarding the extraordinary features and outstanding stability?
[a href="index.php?act=findpost&pid=317801"][{POST_SNAPBACK}][/a]
It's working great, Cap. Just how I like it.
Cheers,
C
Hello,
I’m a french user
I use foo_dsp_continuator & channel_mixer (http://www.hydrogenaudio.org/forums/index.php?showtopic=29985), i have no problem with one or other separately. But with 2 together, after 1 or 2 song, the begin of next is with a delay, like a chorus, i have multiple departure of song. I have to stop and restart until the next bug.
After few more test, without channel_mixer i already have the bug.
Hello,
I’m a french user
I use foo_dsp_continuator & channel_mixer (http://www.hydrogenaudio.org/forums/index.php?showtopic=29985), i have no problem with one or other separately. But with 2 together, after 1 or 2 song, the begin of next is with a delay, like a chorus, i have multiple departure of song. I have to stop and restart until the next bug.
After few more test, without channel_mixer i already have the bug.
[a href="index.php?act=findpost&pid=317845"][{POST_SNAPBACK}][/a]
I have this exact same problem. The song will have a delay, but when the song is restart it's gone and it plays normally. Since I've disabled continuator (but kept channel_mixer on) I haven't experienced this problem again.
EDIT: Turns out I was using an older version. I've updated, now I'll see if the problem persists or if it's been fixed...
CptFooture: same here. Speechless, works without bugs, and no feature requests so far...
Wow, this plugin has come a long way. Is it possible to add a 'Fade on Stop', 'Fade on Seek' and 'Fade on Track Skip' like there is in the SQR crossfader for Winamp? If that happens, it looks like I'll finally get to use Continuator for my live gigs. Many thanks.
Wow, this plugin has come a long way. Is it possible to add a 'Fade on Stop', 'Fade on Seek' and 'Fade on Track Skip' like there is in the SQR crossfader for Winamp? If that happens, it looks like I'll finally get to use Continuator for my live gigs. Many thanks.
[a href="index.php?act=findpost&pid=318038"][{POST_SNAPBACK}][/a]
No, this is not the job of a DSP. What you are looking for is a modified output-plugin which does this. For foobar 0.8, such a plugin does exist (directsound 2.5/extended). For 0.9beta, there is no such plugin yet.
For 0.9beta, there is no such plugin yet.[a href="index.php?act=findpost&pid=318049"][{POST_SNAPBACK}][/a]
The output in 0.9 uses fading in the mentioned situations, though the fade length is rather short and not configurable.
Just in case anyone cares I updated to the latest version of continuator and I'm still getting that strange echo bug. Any ideas?
Just in case anyone cares I updated to the latest version of continuator and I'm still getting that strange echo bug. Any ideas?
[a href="index.php?act=findpost&pid=318123"][{POST_SNAPBACK}][/a]
Hi,
i can't reproduce this behavior. Can you give a more detailed description of your setup?
I'd like the following feature.
If somebody wants to crossfade some tracks in his playlist he would add something like crossfade://crossfade=2000 betwean this two tracks.
If he want to prevent two tracks from crossfading he adds crossfade://nocrossfade betwean this two tracks.
The dsp component will look for the next track in the playlist and if this is crossfade it would change the component behaviour. Otherwise the behaviour would remain default. Is it possible for dsp component to behave as described in fb2k v0.8 or v0.9?
No, DSPs have nothing to do with the playlist.
No, DSPs have nothing to do with the playlist.
[a href="index.php?act=findpost&pid=318989"][{POST_SNAPBACK}][/a]
Anyway storeing this info in s playlist is the right way...
Doesn't crossfade here. I looked at the settings & adjusted them, but still no crossfade. Am I doing anything wrong?
No bugs found?
[a href="index.php?act=findpost&pid=317801"][{POST_SNAPBACK}][/a]
Actually, I somehow managed to crash it 2 times at work. Gotta have a look if I still have the crash logs on monday...
No comments?
No suggestions?
Actually, a bit of basic documentation for the settings would be handy; just setting the mode to crossfade and setting the crossfade length doesn't really seem to work - does one have to change the fade-lengths accordingly, or what am I missing? How are the length settings linked together?
What do the checkboxes do exactly, and what size should the buffer size be? As big as the set crossfade time? Or can it be any value?
HEEELP!
Hey Cpt. footure. Theres a CPU problem.
It seems like the latest version turns out to be a cpu hog. I admit I have a slow Computer (Intel PIII/500/384MB/a fresh!W2Ksp4) but anyway: When double clicking a track, foobar cpu load jumps up to 80%. The mouse is "stuttering" then for a second or two. Without the continuator loaded, fb2k cpu load does only jump to 20-30% when changing track.
My settings:
Mode: Overlap
Buffer: 3000 ms
Threshold: 20
Fade out: S-curve ---
- only when audio
Length: 8000
Steepness: 0,5
Fade in: S-curve
Length: 2000
Steepness: 0,5
- Empty buffer up to...
- Disable track overlapping...
[ ] Adjust...
Hi guys,
i've uploaded continuator version 0.3.6 (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll), which should fix the fade-in-out-despite-seamless-transition-detected bug. Unfortunately i had to disable fade-out if seamless transitions shall be detected, because the fade-out has to happen before a decision about a seamless transition could be made.
bye
ps: The controls on the settings page already moved a little downwards to make some space for the presets feature, which is not ready yet.
Cpt. Footure,
EDIT: <snipped bug report, it does not work seemless if gap killer is above it in the dsp chain...>
It works fine now. The bug with seemless transition seems to be fixed. Will fade out be available again (when seemless trans is checked)?
EDIT2: Theres something wrong. When the plugins power switch is turned on, it does not play seemless, but it does fade. When power is turned off, the plugin still works (I can see this because if I change the buffer size, the playlist jumps to the next track exactly at the buffer time) and the tracks play with seemless transition.
I get confused.
I'm not sure if that's what you asked for, but fade-out is *only* disabled when 'Disable track overlapping...' is checked (as indicated by the greyed-out controls).
Cpt. Footure, did you read my edited post again? The plugin seems pretty buggy.
I'm not sure if that's what you asked for, but fade-out is *only* disabled when 'Disable track overlapping...' is checked (as indicated by the greyed-out controls).
Yes. BUT: This checkbox makes much sense (it's useless to fade withiin a live album e.g.) so it's probably mostly turned on. So but if it is checked and the plugin does not detect seemless transition, it will not fade out. A loss of functionality....
So but if it is checked and the plugin does not detect seemless transition, it will not fade out. A loss of functionality....
[a href="index.php?act=findpost&pid=327550"][{POST_SNAPBACK}][/a]
Unfortunately i had to disable fade-out if seamless transitions shall be detected, because the fade-out has to happen before a decision about a seamless transition could be made.
Thx Lyx for the quote. But as the plugin pre-reads according to its buffer settings, what does prevent it from deciding from the original material and then performing its fading/not fading action?
This appears to be a most powerful and felixible component for foobar. I am a recent convert from Winamp. It's cool to see something so powerful also be so supported- If more developers were like Cpt. Footure, there'd be a lot more killer software out there.
I promise I am not an idiot!
But for the life of me, I cannot get the continuator to crossfade. Crossfade implies that two songs are playing at once, as one ends and the next begins, correct?
Is there any documentation for this?
Are there presets available, or a list of "working" settings so I can test it out?
I have been testing with different continuator settings and a bunch of different mp3's for over an hour- I actually had it fading out at one point (can't figure out how to get back to that point) but still never got it to crossfade.
Any help would really be appreciated!
This appears to be a most powerful and felixible component for foobar. I am a recent convert from Winamp. It's cool to see something so powerful also be so supported- If more developers were like Cpt. Footure, there'd be a lot more killer software out there.
I promise I am not an idiot!
But for the life of me, I cannot get the continuator to crossfade. Crossfade implies that two songs are playing at once, as one ends and the next begins, correct?
Is there any documentation for this?
Are there presets available, or a list of "working" settings so I can test it out?
I have been testing with different continuator settings and a bunch of different mp3's for over an hour- I actually had it fading out at one point (can't figure out how to get back to that point) but still never got it to crossfade.
I'm somehow in the same position, with perhaps the exception that I'm really newbie at this (maybe continuator is too advanced for me?). So I second McPhatty's requests: a guide for dummies and some example configs.
Alessandro
PS: forgot to mention: also some notes about correct DSP chain and how replaygain affects continuator behaviour.
This appears to be a most powerful and felixible component for foobar. I am a recent convert from Winamp. It's cool to see something so powerful also be so supported- If more developers were like Cpt. Footure, there'd be a lot more killer software out there.
I promise I am not an idiot!
But for the life of me, I cannot get the continuator to crossfade. Crossfade implies that two songs are playing at once, as one ends and the next begins, correct?
Is there any documentation for this?
Are there presets available, or a list of "working" settings so I can test it out?
I have been testing with different continuator settings and a bunch of different mp3's for over an hour- I actually had it fading out at one point (can't figure out how to get back to that point) but still never got it to crossfade.
Any help would really be appreciated!
[a href="index.php?act=findpost&pid=327597"][{POST_SNAPBACK}][/a]
Hi,
currently there's no documentation, but if i will find some time...
Getting Continuator to do crossfading is actually pretty easy (at least from my point of view ):
use the following settings to overlap two tracks by 20 sec, ie. new track starts 20s before end of old track
mode: crossfade
buffer length: 20000
crossfade length: 20000
now you can configure the fading curves and lengths which are independent from the crossfade length, eg. for a 5s fade-out and a 10s fade-in with linear curves:
fade-out curve: linear
fade-out length: 5000
fade-in curve: linear
fade-in length: 10000
maybe a little 'visualization' will help :
time ->
-------------------------------------------------------| old track
|----------| fade-out
|------------------------------------------------------------ new track
|--------------------| fade-in
|--------------------------------------| crossfade
bye.
ps: as mentionend above i'm already working on a preset feature
Thx Lyx for the quote. But as the plugin pre-reads according to its buffer settings, what does prevent it from deciding from the original material and then performing its fading/not fading action?
[a href="index.php?act=findpost&pid=327566"][{POST_SNAPBACK}][/a]
Hi,
the problem is that you can only pre-read within one track and not across track boundaries. So you have to base your FADE-OUT decision on the material from the current track and you (me) only get to see the new track AFTER the old one has been processed.
Bye.
ps: right now i have decoupled the fade-out / fade-in lengths from the overlap length, before that i could only perform fading within the overlapping period. Maybe i can find a better way to handle it.
[removed]
Make sure that samplerates are identical - if necessary, add a resampler-DSP before continuator in the DSP-chain.
[removed]
foo_dsp_continuator doesn't work on my notebook. It has a freshly installed Windows2000sp4 and a fresh fb2k installation.
If I visit the continuator settings in preferences foobar crashes: "[Microsoft Visual C++ runtime library] Abnormal program termination"
I used the dependency walker to see if all dlls are there. Yes. All modules are found (esp. msvcr71.dll and msvcp71.dll)
I have no idea why it doesn't work.
Cpt. Footure, do you want port continuator to 0.9?
Is anyone working on porting continuator to .9? G-Lite did a great job porting track info and album art pannel. Perhaps somone could solicit his assistance?
I too would love to see this one ported. I may be willing to contribute a small donation or bounty to the one who does it. I'll try to get ahold of Cpt. Footure first, since he's the one whe rightfully deserves it.
I too would love to see this one ported. I may be willing to contribute a small donation or bounty to the one who does it. I'll try to get ahold of Cpt. Footure first, since he's the one whe rightfully deserves it.
I'll add my two cents!
I too would love to see this one ported. I may be willing to contribute a small donation or bounty to the one who does it. I'll try to get ahold of Cpt. Footure first, since he's the one whe rightfully deserves it.
I'll add my two cents!
Same here! This is the single one component whose non-existence keeps me from uninstalling foobar2k 0.8.3
Hi guys,
believe me, i'm really willing to port continuator to 0.9, it's just that i don't have time to do it. I don't even know how much work it would be, as i didn't have a look at the 0.9 SDK yet. I already offered to release the source code a (long) while ago but there seemed to be no interest back then. But i think now it's different and i'll upload the sources during this week.
bye.
Hi guys,
believe me, i'm really willing to port continuator to 0.9, it's just that i don't have time to do it. I don't even know how much work it would be, as i didn't have a look at the 0.9 SDK yet. I already offered to release the source code a (long) while ago but there seemed to be no interest back then. But i think now it's different and i'll upload the sources during this week.
bye.
Great! Once you upload the source code, I know that there are a lot of people who are interested in porting continuator to .9, and I am sure someone will step up and port it. Thanks and anxiously awaiting the source code.
I didn't know there was a crossfade alternative! And since crossfade hasn't been ported yet, I'd be happy to do this, actually.
I didn't know there was a crossfade alternative! And since crossfade hasn't been ported yet, I'd be happy to do this, actually.
This is not just an alternative. This is a glimpse of the Holy Grail of crossfading.
And as my beloved Dr. Klahn would say: You have our gratitude!
Go Cpt. Footure & G-Lite! :-)
This is the last .9 component I'll need....Thanks G-Lite for taking it on!
I would certainly appreciate that G-Lite. That's too bad Cpt. Footure is too busy, but yeah, let me know when it's working and I'll donate something for your efforts.
Capt. Footure & G-lite: while we're at it, would it be possible to port the Direct Sound 2.5 (foo_out_dsound_ex2) as well? I know the good captain mentioned that he simply modified the original dsound 2 output: is that possible again with the new foobar? It's the combo of those two plugs that makes for a truly seamless, musical crossfading environment. I have one small suggestion that maybe could be incorporated: you'll find it near the end of this thread: http://www.hydrogenaudio.org/forums/index...._out_dsound_ex2 (http://www.hydrogenaudio.org/forums/index.php?showtopic=22894&hl=foo_out_dsound_ex2)
Thanks and good luck.
ears
[Delete Me]
Hi guys,
i've uploaded the continuator (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator_src.rar) sources and also the DirectSound 2.5 (http://www.ewetel.net/~axel.behrens2/foo_out_dsound_ex2_src.rar) sources.
Enjoy.
[deleted]
Ooh... I actually didn't realize that output in foobar 0.9 didn't have crossfading. I too would like to see that one implemented, but for now, continuator is much more important.
When I use foobar2000 to DJ (playing background music, et al), continuator keeps the music going seamlessly, and the directsound 2 crossfading allows me to switch tracks and stuff in a way that sounds very smooth and natural, as if I were actually crossfading in a mixer.
(So that's my big secret... I use it when I'm too lazy to DJ for real )
Thanks for the sources. A couple of questions.
You seem to make use of XML to write what used to be a xml config file. However, that code doesn't seem to be used anymore. I get the feeling this used to be legacy code. If so, can we remove the entire XML parsing support from the code (and eliminate the need for IE5)?
You use a play_callback object to get notified when a seek occurs, but it no longer seems to be necessary. Is there some debug code that was removed (which needs to know when the track is seeking)?
Here's a direct port of the plugin, consider it beta:
http://stephan.kochen.nl/proj/foobar2000.html#continuator (http://stephan.kochen.nl/proj/foobar2000.html#continuator)
Technical note: taking care of the foobar related stuff was easy, but I encountered some STL errors related to vector iterators. There might be some more I haven't bumped into yet, but the plugin is working in both modes from what I've tested so far. Visual C++ 2005 has gotten alot more strict regarding STL.
This thing is also not using the preset interface yet. But it should work well enough for playback purposes.
Here's a direct port of the plugin, consider it beta:
http://stephan.kochen.nl/proj/foobar2000.html#continuator (http://stephan.kochen.nl/proj/foobar2000.html#continuator)
Thanks a bunch, but I'm unable to modify Fade-out curve, Fade-out length and Fade target: I see the options but disabled. Is this an issue with Win2000?
Alessandro
Thanks a bunch, but I'm unable to modify Fade-out curve, Fade-out length and Fade target: I see the options but disabled. Is this an issue with Win2000?
Alessandro
No, your Win2k has nothing to do with it. Uncheck "Disable track overlapping on seamless transition", and the options become available.
@G-Lite: Wow, that was fast!
No, your Win2k has nothing to do with it. Uncheck "Disable track overlapping on seamless transition", and the options become available.
Oops, yet another stupid post...
Thanks for your help.
Alessandro
When I use foobar2000 to DJ (playing background music, et al), continuator keeps the music going seamlessly, and the directsound 2 crossfading allows me to switch tracks and stuff in a way that sounds very smooth and natural, as if I were actually crossfading in a mixer.
Is it somehow possible to implement this "manual track skip crossfade" in Continuator? That would make it kind of an all-in-one fading device (Germans have a funny name for those which roughly translates to "egg-laying wool-milk-sow").
Is anyone interested in my update of the plugin? I've removed all level 4 warnings from the code (it may not actually fix anything, but it could help with troubleshooting that STL assert).
Cool ! YOur Continuator seems to work well !
Thanks !
I think this warrants a thread-split, or at least a new thread. This one's getting long, and offtopic.
I'm testing out the new port of continuator. Mostly it works well but there are a few issues. One of them is that when it pre-loads the next track at the specified buffer length, it starts counting time played on the next track, even if it hasn't started playing yet. (especially noticeable with the "power" checkbox off)
I still haven't tested if this causes other problems, like the track prematurely ending. (I've just been fast forwarding to right before the buffer length, which is set to 15s before the track end)
The other problem is that it doesn't always seem to buffer the amount of time specified in the preferences. Perhaps I'm just not aware of how it's supposed to work, but it usually seems like it pre-loads the next track quite a bit after it should.
Other than those problems, things seem to work very well, and it sounds great.
While Continuator is now very powerful regarding features, i think it has become a bit difficult to use.
For fb2k 0.8, there was a limitation regarding seamless-trackchange detection and fadeout-length. Is this still the case for 0.9?
Anways, here is my proposal on how it should work in an optimal world (please tell me if its technically possible):
PREFERENCES:
General options(always available): power, do nothing on seamless trackchange, Adjust Tracklength to CD-Blocksize
Overlap-Mode:
Look-ahead time (in ms)
Threshold (in dB)
Fade-Out (in ms - plus curve-style and checkbox to only apply if audio at the end)
Fade-In (in ms - plus curve-style)
Crossfade-Mode:
Look-ahead time (in ms)
Fade-Out (in ms - plus curve-style)
Fade-In (in ms - plus curve-style)
Automatically calculated:
Crossfade-Length (is always either the length of "Fade-Out" or "Fade-In" depending on which is larger)
Buffer length=fadeout/fadein(depending on which one is larger) plus Look-ahead time
(Yes, i am aware that this results in a minor feature-loss, but i think the simplification is worth it)
CONTINUATOR-TAG (backwards-compatible):
overlap (uses default preference-settings)
overlap,threshold_in_dB (uses default fade-lengths)
overlap,threshold_in_dB,fadelen_in_ms_for_both (sets fadelength for both fadeout and fadein - both will have the same value)
overlap,threshold_in_dB,fadeout_in_ms,fadein_in_ms
crossfade (uses default preference-settings)
crossfade,fadelen_in_ms_for_both (sets fadelength for both fadeout and fadein - both will have the same value)
crossfade,fadeout_in_ms,fadein_in_ms
gapkill (alias for "overlap,60")
off (disable continuator for this trackchange)
DROPPED FEATURES:
empty buffer at overlappoint (the user should not need to mess with this)
crossfade-time (minor feature-loss, but simplifies prefs and allows to make continuator-tag more useful)
UNSURE:
Should fade-in or fade-out be prioritized(order) in the preferences and continuator-tag? (needs to be decided now, because prefs should have the same order as continuator-tag because of consistency)
Ideas, questions, proposals, etc. welcome
- Lyx
Thx G-Lite, seems to work well, I have to turn the value up slightly high to get a effect, and maybe someone can tell me this but this plugin doesn't allow the track to fade out on hitting the "stop" button does it? That was directsound 2.5 wasent it? thx anyways.
i've uploaded continuator version 0.3.0 (http://www.ewetel.net/~axel.behrens2/foo_dsp_continuator.dll), which adds the following new features:...
...additional delay dependant on speed of volume drop, to give tracks with sudden ends some 'air', before the next track starts (currently not configurable)
Hmm... I'm not sure that I always like this behavior. It would be nice to have a checkbox or something to toggle this behavior.
I know this is old... due to the lack of built-in documentation for this plugin, I was reading old posts. That's another enhancement that could be made... have some context help, or at least tooltips to describe what some of the features do. Perhaps a button linking to an HTML page would be very helpful as well.
Another idea... that's too bad that fadeout has to be disabled if seamless track transition detection is on. Is there not some way of predetermining that before the song even starts? Or would that be terribly complex and well outside of the domain of this component? I guess you might be able to use the tag instead, if this were to happen.
Uhm... could you use the continuator tag to identify songs as seamless, so that continuator doesn't affect playback even if "seamless detection" is turned off?
Could someone please share his settings?
All that this plugin is missing, in my opinion, is the ability to beat match during crossfade.
Please make support auto disable crossfading for CUE audio files.
sorry my bad english
Please make support auto disable crossfading for CUE audio files.
An interesting feature proposition, but personally I don't only use cuesheets for seamless CDs (like DJ mix CDs, Live albums etc). I often rip a CD as one file with cuesheets just so I can preserve the exact layout of the CD, but the actual tracks aren't seamless.
It might be a handy switch to have in the options though, for many.
I found another bug in continuator that occurs when playing very tiny files.
I was using foobar2000 to listen to some small wav files (under 10KB) with a sampling rate of 22 KHz in mono. As soon as I attempt to play them, foobar crashes when using continuator.
I thought I should bring this to the attention of developers and such...
The two files causing the problem are here:
http://fullspec.ca/misc/sounds/ (http://fullspec.ca/misc/sounds/)
I'm quite aware of this error. It's basically caused by improper use of STL iterators, as mentioned in this previous post by G-Lite:
Technical note: taking care of the foobar related stuff was easy, but I encountered some STL errors related to vector iterators. There might be some more I haven't bumped into yet, but the plugin is working in both modes from what I've tested so far. Visual C++ 2005 has gotten alot more strict regarding STL.
I think the fix requires the iterators needing to be reinitialized after modification, but I haven't had the time to check or test yet.
Could the continuator be set up to emulate the behaviour
of the skip_silence plugin?
I mean, to have it start the next track when the current
sound level falls under a selected threshold, while also
stopping the current track instead of fading out?
Could the continuator be set up to emulate the behaviour
of the skip_silence plugin?
that would be pretty cool.
ive never used this plugin before, is there a way to set it up to just skip silence between tracks...so for instance it could play files seamlessly? i would think that would be the point of the plugin, but i cant find an option that sets any number below 10ms, but i might be reading the options wrong. that and the feature listed above would really make this a nice all in one silence manipulation plugin. well i guess itd have to have ability to add silence too but now im talkin crazy
G-Lite , can you do terminate port of continuator to foobar 0.9?
regards, melomane
G-Lite , can you do terminate port of continuator to foobar 0.9?
G-Lite offers 0.9 ports only.
Question to anybody:
Is the option "Disable track overlapping on seamless transition" working?I tested on lots of gapless classical stuff and, it's fading as hell. The option does not seem to work.
Squeller, port of continuator is not complete!
Look here (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=18703&view=findpost&p=381226)
and it is possible that is the reason so that "Disable track overlapping on seamless transition" not working.
Squeller, port of continuator is not complete!
Look here (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=18703&view=findpost&p=381226)
and it is possible that is the reason so that "Disable track overlapping on seamless transition" not working.
Correct. I did some testing on the same tracks/ with the same settings with the 0.9 and the latest 0.83 compile: They behave differently on the issue. 0.83 works fine, 0.9 doesn't.
Squeller, port of continuator is not complete!
Look here (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=18703&view=findpost&p=381226)
and it is possible that is the reason so that "Disable track overlapping on seamless transition" not working.
Correct. I did some testing on the same tracks/ with the same settings with the 0.9 and the latest 0.83 compile: They behave differently on the issue. 0.83 works fine, 0.9 doesn't.
I didn't change any of the dsp code, and the plugin should be equal in features with the 0.83. I don't know alot about dsp though, not sure I can fix that.
g-lite, without make any change to dsp code, can you make "preset interface " work?
same as you do for v-level.
it is possible this is the reason for different behavoir enter 0.83 and 0.9.
regards, melomane
it is possible this is the reason for different behavoir enter 0.83 and 0.9.
No
g-lite, can you make "preset interface " work?
if not , someone can?
Hey all,
I'm getting a crash when using the continuator. Towards the end of each song right when it's supposed to overlap with the next track I get an Application Error:
"foobar2000.exe - Application Error
The exception unknown software exception (ox000000d) occurred in the application at location 0x00b8c132.
Click on OK to terminate the program"
then when I click ok, foobar shuts down.
Any ideas why this might be happening? The only other DSP I have active is equalizer if that helps at all.
Any help would be greatly appreciated
I had something really happen once with continuator. It crossfaded into a song, but then it crossfaded into... itself or something. So I ended up hearing the song superimposed over a delayed version of itself. Stoping playback fixed it. It's like it kept filling the buffer, playing off the buffer, and forgot to change state.
I had something really happen once with continuator. It crossfaded into a song, but then it crossfaded into... itself or something. So I ended up hearing the song superimposed over a delayed version of itself. Stoping playback fixed it. It's like it kept filling the buffer, playing off the buffer, and forgot to change state.
Happened to me too. I disabled the three options at the bottom, in preferences (Empty buffer up..., Disable track overlapping..., Adjust track length...) and problems seem to have dissapeared.
I am not really sure, I've just been testing for a half of day
Happened to me too. I disabled the three options at the bottom, in preferences (Empty buffer up..., Disable track overlapping..., Adjust track length...) and problems seem to have dissapeared.
I am not really sure, I've just been testing for a half of day
I has happened to me a couple of times too. Didn't realise continuator was the cause.
This component is awesome, is there any way of being able to burn a playlist to a CD with the fade in/out included?
Just "convert" it to WAV, activate Continuator in the converter-DSP-settings, and then burn the WAVs to CDR.
Fantastic, thanks.
Just "convert" it to WAV, activate Continuator in the converter-DSP-settings, and then burn the WAVs to CDR.
only in 0.83
don't work in 0.9 because continuator isn't entirely ported.
I think I have to report a bug. On 0.9.1 with continuator only active, many songs do get skipped the last 10-15 seconds instead of being crossfaded.
Can anybody tell me why?
P.S.: I want foo_crossfade back
I think I have to report a bug. On 0.9.1 with continuator only active, many songs do get skipped the last 10-15 seconds instead of being crossfaded.
Can anybody tell me why?
P.S.: I want foo_crossfade back
Uncheck:
empty buffer up ...
disable track...
adjust track lenght to...
I think I have to report a bug. On 0.9.1 with continuator only active, many songs do get skipped the last 10-15 seconds instead of being crossfaded.
Can anybody tell me why?
P.S.: I want foo_crossfade back
Uncheck:
empty buffer up ...
disable track...
adjust track lenght to...
already done that, unless I wouldn't have reported it.
might it be something related to having to load mp3s across a LAN?
G-Lite, if u developing this plugin, our who develop it.
I suffer a problem, time by time, serveral time a week (while listening more over 1,000 songs), while crossfading to a new song - the song is double played in the same time with an offset.
I can't give any other clues, there is no link between the songs, the file propeties, and it seem to be randomize.
This is the properties window (note, the problem don't dissaper when i change some of the options):
(http://img135.imageshack.us/img135/9997/15001500148815131501yo8.th.jpg) (http://img135.imageshack.us/my.php?image=15001500148815131501yo8.jpg)
I haven't noticed this one yet. There are a few issues with the new port, but none that bad.
I dont know why this plugin doesnt work with my foobar 0.9.1.
I active this, use a normal setting, ie as ArielG's, and have no cross fader between tracks.
Any ideas how it works somelike DirectSound v2 in foobar 0.8.x?
have you put it in the active DSPs in the DSP manager?
Useless post caused by missunderstanding a sentence because of missreading a word lol.. slap me [Fixed typos..]
Hello
Could someone tell me if the continuator works (fades the two tracks) when for instance I use my hotkey button to jump to the next 'random' track and does it also works when foobar is set to the "random" mode and beginning the next random song?
Some monthes ago continuator was not able to do it (or maybe was it bad configured?)
That's why actually I'm using foobar v0.8.3 with the Kernel v2.5 output 'combined' with the continuator which allows me to do that trick...
Thanks
For me it only works when foobar changes track, no matter what playback order is set. But via hotkey it directly jumps to the new track.
That's why I'm still using the old foobar version cause DirectSound v2.5 has not been ported to the 0.9.x
It there a way to get things work?
Honestly I can't test it right now. But I have the impression, that it works for me on manual trackchange!
Continuator crashes with files that are less than 1 second long. Foobar 0.9.3.1
No message, no anything, just disappears.
Just "convert" it to WAV, activate Continuator in the converter-DSP-settings, and then burn the WAVs to CDR.
only in 0.83
don't work in 0.9 because continuator isn't entirely ported.
Continuator crashes with files that are less than 1 second long. Foobar 0.9.3.1
No message, no anything, just disappears.
Unfortunatelly I can't code but I would really like to have the few bugs that are there to be sorted out. Maybe someone is willing to step up and fix them?!
In the earlier foobar version I used this version alot to burn crossfaded cds. When thats fixed again I will be very happy!
Just "convert" it to WAV, activate Continuator in the converter-DSP-settings, and then burn the WAVs to CDR.
only in 0.83
don't work in 0.9 because continuator isn't entirely ported.
Continuator crashes with files that are less than 1 second long. Foobar 0.9.3.1
No message, no anything, just disappears.
Unfortunatelly I can't code but I would really like to have the few bugs that are there to be sorted out. Maybe someone is willing to step up and fix them?!
In the earlier foobar version I used this version alot to burn crossfaded cds. When thats fixed again I will be very happy!
Same goes for me... I would also be *very* happy if this great dsp is ported properly... can't burn crossfaded tracks!
Tom.
foo_dsp_continuator unfortunatelly seems to have problems with the latest foobar-beta 0.9.4 beta 1 (http://www.hydrogenaudio.org/forums/index.php?showtopic=48041).
Can you fix this?
Another request from another thread:
Now what would be awesome is if continuator could be modified so as to allow it to beat match between tracks predicated on the values of each track's BPM tag!
A great idea IMHO
Cpt. Footure Last Active 17th April 2006 - 10:29
G-Lite Last Active 24th June 2006 - 20:17
Afaics the development is discontinued, R.I.P.
But source is open, so if there are any c++ geeks out there...
Given the apparent demise of Continuator (which I really, really liked), can anyone recommend a successor?
This is one of the chief reasons I'm staying at foobar2000 v0.8.3.
I've been using G-Lite's port of Continuator on a 24/7 FB2K 0.9.4.1 instance for a while now without problems. I saw instability problems at the default settings, but once I coaxed fade-in length to 40 ms, it performed fine. I have some 1- to 5-second bumpers in the playlist and they don't cause any problems.
Is it possible to set it up to just overlap tracks? Appearently it wants to fade-in all tracks - It sounds weird.
0.4.1 (2007-04-11): Ported to Foobar2000 0.9.4.2 removed MSXML buggy runtime (caused crash on exit)
modified by XPiS & Alexey Kamaev aka STALK:ER (STALK_ER)
Download (http://www.crystalidea.com/?q=freeware)
thanks for the update - works fine so far
always liked to have a different fade-in length than crossfade length
when skipping through a track theres also no gap - nice
The http://www.crystalidea.com/?q=freeware (http://www.crystalidea.com/?q=freeware) is now the HOME page of this plug-in.
thank you!
crash when mode is crossfader and fade in lengh <20
no sound after crossfading when fade in lengh <40
please, can you add config page in dsp preset?
I have just been listening to some music and I had a wicked idea on how to improve continuator.
Continuator is great for playing a list of shuffled songs, however when i set playback mode to default and I listen to an album that is already mixed ie ministry of sound album it sound terrible as its like playing the same song twice at the same time only out of sync.
My idea into fixing this was to implement some logic into the program like this.
IF playback mode = defaut AND next track is in same album as currently playing THEN disable continuator ELSE enable continuator
Or another way of achieving it would be
IF next songs album = current songs album AND track number of next song = track number of current song +1 THEN disable continuator ELSE enable continuator.
I only just thought of this 30sec ago but it would be sweet if implemented because then my foobar would mix when mixing is needed and leave the already mixed songs be. Maybe one day I can work on this but in the mean time anyone feel free to beat me to it.
-vader897
IF playback mode = defaut AND next track is in same album as currently playing THEN disable continuator ELSE enable continuator
Or another way of achieving it would be
IF next songs album = current songs album AND track number of next song = track number of current song +1 THEN disable continuator ELSE enable continuator.
-vader897
That would only work if the album is an "already mixed" one. What if you play a "not mixed" album with default playback? According to your idea, that album would be played with disabled Continuator too. Bad idea... or am I getting something wrong?
Tom.
correct logic is:
crossfader is active when
playback mode is shuffle ( track)
or
next track isn't from same album track+1
more here (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=45709&view=findpost&p=403327)
correct logic is:
crossfader is active when
playback mode is shuffle ( track)
or
next track isn't from same album track+1
more here (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=45709&view=findpost&p=403327)
I agree. I would normally not prefer to mix when i listen to any album. I would really like this option too
I was testing the CONTINUATOR tag, but was unable to get it working (tried with "off", but it still faded, regardless of the "Override mode"). Anyone got it working?
Also, I think that it would be more powerful if you could implement the earlier proposed ability to specify both fadein
and fadeout settings. Bumping the old post:
CONTINUATOR-TAG (backwards-compatible):
overlap (uses default preference-settings)
overlap,threshold_in_dB (uses default fade-lengths)
overlap,threshold_in_dB,fadelen_in_ms_for_both (sets fadelength for both fadeout and fadein - both will have the same value)
overlap,threshold_in_dB,fadeout_in_ms,fadein_in_ms
crossfade (uses default preference-settings)
crossfade,fadelen_in_ms_for_both (sets fadelength for both fadeout and fadein - both will have the same value)
crossfade,fadeout_in_ms,fadein_in_ms
gapkill (alias for "overlap,60")
off (disable continuator for this trackchange)
Note that this is a proposal and not the actual syntax.
Is this plugin still being maintained by Ilya P?
If so, is it possible to get it to crossfade even when I change tracks manually? ( Like the SQR Advanced Crossfader for Winamp, http://www.sqrsoft.com.ar/ (http://www.sqrsoft.com.ar/) )
New version works witout erros on my foobar 0.9.4.3 with these settings:
(http://elektron.its.tudelft.nl/~dokter99/files/foobarcont.jpg)
But the fade between songs doesn't seem to work. What am I doing wrong?
It does work, just not really obvoius.
It does work, just not really obvoius.
Is that a response to my question??
Yes. I hear my songs crossfade at times, it's not *that* obvious.
But the fade between songs doesn't seem to work. What am I doing wrong?
If I have understood this rms drop in dB correctly the song must drop at least this many dBs before the fade will happen. If you decrease this value the fade should be more noticeable. Or you could switch to crossfade which always fades a specified amount of seconds.
Hope this helps.
But the fade between songs doesn't seem to work. What am I doing wrong?
If I have understood this rms drop in dB correctly the song must drop at least this many dBs before the fade will happen. If you decrease this value the fade should be more noticeable. Or you could switch to crossfade which always fades a specified amount of seconds.
Hope this helps.
It still does not work after adjusting the amount of dBs (decrease). It really does nothing at all! :S. I also switched back to foobar 0.8, since the COLUMNS_UI with newest foobar is not well functioning with my pc (vista-32). I cannot adjust the length of the fields (artist, title, etc..)
But the fade between songs doesn't seem to work. What am I doing wrong?
If I have understood this rms drop in dB correctly the song must drop at least this many dBs before the fade will happen. If you decrease this value the fade should be more noticeable. Or you could switch to crossfade which always fades a specified amount of seconds.
Hope this helps.
It still does not work after adjusting the amount of dBs (decrease). It really does nothing at all! :S. I also switched back to foobar 0.8, since the COLUMNS_UI with newest foobar is not well functioning with my pc (vista-32). I cannot adjust the length of the fields (artist, title, etc..)
For me the effect is really obvious if I use settings like CONTINUATOR crossfade[,6500]
I'm using continuator 0.4.1 with Foobar 0.9.4.3 on Windows XP Pro SP2.
Value "off" doesn't work and I haven't noticed that changing threshold value would have any effect.
I'm in trouble trying to figure if fade-in fade-out is fully supported. I have tried setting like:
crossfade[6500,6500] but next track on playlist doesn't really fade-in but overlaps with previous track instead. However, whatever value I have set for fade-in length in continuator control panel is applied.
I checked Wiki Talk page (http://wiki.hydrogenaudio.org/index.php?title=Foobar2000_Talk:0.9_Continuator_(foo_dsp_continuator)) and I think I'm either missing something obvious or something isn't working.
I really wish there would be "continuator for dummies" or any better documentation for this component. It's must have piece for me even without using CONTINUATOR tags. It would just make so much easier to make transitions between studio / live material or if playlist spans multiple genres of music (I'm a DJ).
It would really help usability a lot if override settings could be applied to file via button in continuator settings.
But the fade between songs doesn't seem to work. What am I doing wrong?
If I have understood this rms drop in dB correctly the song must drop at least this many dBs before the fade will happen. If you decrease this value the fade should be more noticeable. Or you could switch to crossfade which always fades a specified amount of seconds.
Hope this helps.
It still does not work after adjusting the amount of dBs (decrease). It really does nothing at all! :S. I also switched back to foobar 0.8, since the COLUMNS_UI with newest foobar is not well functioning with my pc (vista-32). I cannot adjust the length of the fields (artist, title, etc..)
Two things:
- I don't understand your choice for fade-in value (6815 ms). I found this value to touchy in my setup of the last Continuator release with FB2k 0.9.4.3. I use 40ms. This should produce an imperceptible fade-in of the new track, which is what I use Continuator for: threshold-based mixing without fades.
- Make sure you put Continuator at the top of your "Active DSPs" stack, so that the source files aren't being modified by other DSPs before Continuator gets a chance to look at them.
Sorry if i sound like a dummy but can anyone tell me the best settings for this plugin? i love trance music
It seems to make streamed content stutter a little when it starts playing. I guess it should be possible to fix by disabling it if track length is infinite...
Any developer awake - Somebody want to take over the development? The ported sourcecode (but somewhat buggy due to MSXML runtime) is available.
Hello!
I updated foo_dsp_continuator to version 0.5 with the following changes:
Fixed crash on exit, removed unnecessary MS XML config code.
Fixed warning (added type t_size_l, used t_size) and other type conversions.
Fixed STL begin(), end(), copy(), iterator crashes.
Fixed buggy string comparision: 3x e.g. pszFadeOutCurves[nCnt] != ""
Removed MS XML Header
Macros are safe with brackets.
Testcases which are ok:
Testcase 2 small files
Testcase: Fade in/fade out time: 10ms
You can download the new version under:
http://www.wiesinger.com/opensource/foobar...continuator.dll (http://www.wiesinger.com/opensource/foobar2000/foo_dsp_continuator/0.5/foo_dsp_continuator.dll)
You need the following DLLs (Microsoft Visual C++ 2005 Redistributable Package (x86)):
http://www.microsoft.com/downloads/details...;displaylang=en (http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en)
I've tested it with foobar2000 0.9.5Beta* without any problems.
Please let me know whether all the problems have been fixed.
When there are no problems reported I'll release the source code, too.
Wiesl
thanks for further development, works fine so far
I tried the new version, and it works with the latest stable foobar2000 v0.9 release! Here's my config:
(http://vault.meniailenko.com/permanent/foobar_v9_cont_configured.png)
The plug-in behavior in this configuration seems exactly the same as with the old version and foobar v0.8.
I will play around with this a little more, and I will probably finally switch to foobar v0.9. Without a stable and fully-functional cross-fader, foobar v0.9 was just not worth it to me.
Now I can have foobar in all its glory. Thank you so much!
Continuator-tag seem to work now
I had a single foobar-lockup (appearently when Continuator started to buffer). I'll update this post if it reoccurs.
Theres a few things that can be improved if someone takes over this amazing plugin:
1. Gapkill starting silence (to a given threshold) from the next playing track
2. Toggle this plugin on/off from a titleformatting function (I know it's deprecated, but it makes some automation easier)
3. Automatic disabling on live-streams (it makes them stutter at the beginning)
4. Extended Continuator-tag support, as proposed a few pages back.
5. One thing I thought of would be nice to have, is if the Continuator supported a way to cut off a given length of the beginning and end of a track. I have many tracks with interludes appended to a track - This could be a great way to chop these off when they are playing in shuffle-mode.
Continuator-tag seem to work now
I had a single foobar-lockup (appearently when Continuator started to buffer). I'll update this post if it reoccurs.
Theres a few things that can be improved if someone takes over this amazing plugin:
1. Gapkill starting silence (to a given threshold) from the next playing track
2. Toggle this plugin on/off from a titleformatting function (I know it's deprecated, but it makes some automation easier)
3. Automatic disabling on live-streams (it makes them stutter at the beginning)
4. Extended Continuator-tag support, as proposed a few pages back.
5. One thing I thought of would be nice to have, is if the Continuator supported a way to cut off a given length of the beginning and end of a track. I have many tracks with interludes appended to a track - This could be a great way to chop these off when they are playing in shuffle-mode.
What did the "lockup" look like?
Can you explain 1 and 2 a little bit more detailed?
Can't 5. be implemented in overlap mode with the threshold set?
Wiesl
2) if (expression=true) > continuator=on
for exemple:
$if($strcmp(%cwb_playback_order%,'Shuffle(tracks)'),continuator=on)
another plugin, gapless crossfader work in this way.
3) also can be done with titleformatting.
Continuator-tag seem to work now
I had a single foobar-lockup (appearently when Continuator started to buffer). I'll update this post if it reoccurs.
Theres a few things that can be improved if someone takes over this amazing plugin:
1. Gapkill starting silence (to a given threshold) from the next playing track
2. Toggle this plugin on/off from a titleformatting function (I know it's deprecated, but it makes some automation easier)
3. Automatic disabling on live-streams (it makes them stutter at the beginning)
4. Extended Continuator-tag support, as proposed a few pages back.
5. One thing I thought of would be nice to have, is if the Continuator supported a way to cut off a given length of the beginning and end of a track. I have many tracks with interludes appended to a track - This could be a great way to chop these off when they are playing in shuffle-mode.
What did the "lockup" look like?
foobar just freezed.
Can you explain 1 and 2 a little bit more detailed?
1. It seems that starting silence from the track fading to is not cropped - If there's a lot of silence (2-3 sec) it starts too late.
2. Implementing a command like $continuator(enable) to control if it should be set or which can be used with conditional formattings.
Can't 5. be implemented in overlap mode with the threshold set?
Not really. It's more a "very-nice-to-have" request, and I guess not many would benefit from it My idea was that a given time in a tag could make the plugin crop the track, regardless if theres music or not (as I mentioned with interludes appended to the track)
2) if (expression=true) > continuator=on
for exemple:
$if($strcmp(%cwb_playback_order%,'Shuffle(tracks)'),continuator=on)
another plugin, gapless crossfader work in this way.
3) also can be done with titleformatting.
I suppose you mean that 3. works if 2. are implemented? I'm not sure that it will have time to kick in before buffering.
Wiesl, the component is still not reliable for me, now I remember why. I often got sound glitches. Here's my settings and two problematic tracks (play them in order), maybe someone can confirm... At the end of the fading of track one I get a rather loud and short noise from track 1 again.
My Settings:
Mode: Crossfade. Override with tag: off. Buffer 5645, CF length 4582, fade-out linear, length 3625, fade-in linear, length 435, all bottom checkboxes off.
Hmm, the same if you only play track 2, in the end you also get a short peak...
Files are here. (http://www.hydrogenaudio.org/forums/index.php?showtopic=60215)
Wiesl, the component is still not reliable for me, now I remember why. I often got sound glitches. Here's my settings and two problematic tracks (play them in order), maybe someone can confirm... At the end of the fading of track one I get a rather loud and short noise from track 1 again.
My Settings:
Mode: Crossfade. Override with tag: off. Buffer 5645, CF length 4582, fade-out linear, length 3625, fade-in linear, length 435, all bottom checkboxes off.
Hmm, the same if you only play track 2, in the end you also get a short peak...
Files are here. (http://www.hydrogenaudio.org/forums/index.php?showtopic=60215)
Can you post more details:
track length of both tracks, maybe the song titles or how they begin/end (loudness).
What is your sound buffer size? (2000ms?)
Can you try a larger one (e.g. 4000-5000ms) under Preferences/Playback/Output/Buffer Length
I had similar problems with 2000ms sound buffer.
Wiesl
I uploaded the files, did you see?
1: Duration : 0:48.373 (2133264 samples)
2: Duration : 0:42.609 (1879040 samples)
Output buffer was 2000ms, problem remains also with 5000...
I uploaded the files, did you see?
1: Duration : 0:48.373 (2133264 samples)
2: Duration : 0:42.609 (1879040 samples)
Output buffer was 2000ms, problem remains also with 5000...
Ok, I analyzed the situation, and the plugin works correctly.
File1 has a "major loudness part" in the last 170ms (compared to the previous seconds) of the file and it is only gained by -35 to -45 dB. Since it is still very loud in the last 170ms you hear the "click".
When you use the db Scale, it is already down, that you don't hear it.
Wiesl
Hello!
I updated foo_dsp_continuator to version 0.6.1 (from 0.5.0) with the following changes:
===============================================
All Code is now distributed under the GPL license V2, Added GPL license
Added autoenable feature as discussed above:
2. Toggle this plugin on/off from a titleformatting function (I know it's deprecated, but it makes some automation easier)
3. Automatic disabling on live-streams (it makes them stutter at the beginning)
Fixed a lot of crashes.
===============================================
Code changes:
Refactored a lot of code
smooth_vector
on_endoftrack: Sizes must be unsigned when subtracted, validate .end() substraction
Added debug code.
Added correct virtual destructor.
Refactored fill_buffer, apply_gain
=> ifs => MAX/MIN
t_size_l => int where necessary (no functional change)
-0.0 dB are now 0.0dB
Updated Dialogs for autoenable feature.
Reorderd IDs, Removed duplicate entries.
Fixed warning (added type t_size_l, used t_size) and other type conversions.
Fixed STL begin(), end(), copy(), iterator crashes.
Fixed buggy string comparision: 3x e.g. pszFadeOutCurves[nCnt] != ""
Removed MS XML Header
Macro safe with brackets.
Testcase 2 small files: click.wav, popup.wav
Testcase: Fade in/fade out time: 10ms
===============================================
You can download the new version under:
http://www.wiesinger.com/opensource/foobar...continuator.dll (http://www.wiesinger.com/opensource/foobar2000/foo_dsp_continuator/0.6.1/foo_dsp_continuator.dll)
Source Code can be found at:
http://www.wiesinger.com/opensource/foobar...uator-0.6.1.zip (http://www.wiesinger.com/opensource/foobar2000/foo_dsp_continuator/0.6.1/src_foo_dsp_continuator-0.6.1.zip)
You need the following DLLs (Microsoft Visual C++ 2005 Redistributable Package (x86)):
http://www.microsoft.com/downloads/details...;displaylang=en (http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en)
I've tested it with foobar2000 0.9.5.1 without any problems.
Please let me know whether you like the new features and whether it is stable or not.
Wiesl
i like autoenable feature , thank you!
but i have a problem:
if continuator is later equalizer in dsp manager list,
when crossfader isn't enable , with seamless album (for exemple the wall pink floyd) i can hear a click or sometimes a gap when track change.
latest continuator foobar 0.5.1 vista
foo_dsp_crossfader have the same problem
i like autoenable feature , thank you!
but i have a problem:
if continuator is later equalizer in dsp manager list,
when crossfader isn't enable , with seamless album (for exemple the wall pink floyd) i can hear a click or sometimes a gap when track change.
latest continuator foobar 0.5.1 vista
foo_dsp_crossfader have the same problem
Can you post your exact settings.
BTW:
Some documentation on the autoenable feature:
You can use a string e.g.:
$if($strcmp(%album%,'My Album name'),on)
You can use all of the functions which are provided.
When it is on it is used otherwise not.
Wiesl
Thanks for developing this plugin! Maybe it's better thinking about another approach which makes handling way easier: I'm sure the most common idea behind automatically switching track fading is when people use shuffling. In other words: The wish for auto-changing the fading will most likely be caused by a change in the playback order. "Forcing" users to use Tagz for controlling the plugins behaviour just increases code mess.
I wholeheartedly recommend you to use a more easy approach, the same as in foo_rg_trn: A properties page where the user can decide per playback mode/with a radio button.
Pictures say more than thousand non native speakers words ->
Playback mode Continuator ON Continuator OFF
Default x
Shuffle (Tracks) x
Shuffle (Albums) x
...
Thanks for developing this plugin! Maybe it's better thinking about another approach which makes handling way easier: I'm sure the most common idea behind automatically switching track fading is when people use shuffling. In other words: The wish for auto-changing the fading will most likely be caused by a change in the playback order. "Forcing" users to use Tagz for controlling the plugins behaviour just increases code mess.
I wholeheartedly recommend you to use a more easy approach, the same as in foo_rg_trn: A properties page where the user can decide per playback mode/with a radio button.
Pictures say more than thousand non native speakers words ->
Playback mode Continuator ON Continuator OFF
Default x
Shuffle (Tracks) x
Shuffle (Albums) x
...
But's that is possible with the existing scheme (of course not so comfortable but much more flexible). You have to "program" an expression with and, or and not when the playback mode is queried with the function.
Maybe someone can help here.
Wiesl
$ifgreater(%cwb_queuelength%,0,,
$if($or($strcmp(%cwb_playback_order%,'Shuffle (tracks)'),
$strcmp(%cwb_playback_order%,'Random')),$puts(crossfader,1),))
$if($strcmp(%cwb_next_user1%$num(%cwb_next_user2%,3),
%album%$num($add(%tracknumber%,1),3)),,$puts(crossfader,1))
$ifgreater($get(crossfader),0,'on',)
this expression active crossfader when
random or shuffle track are selected playing mode and
with not sequential album tracks (default playing mode and queued tracks)
(use foo_cwb_hooks)
i like autoenable feature , thank you!
but i have a problem:
if continuator is later equalizer in dsp manager list,
when crossfader isn't enable , with seamless album (for exemple the wall pink floyd) i can hear a click or sometimes a gap when track change.
latest continuator foobar 0.5.1 vista
foo_dsp_crossfader have the same problem
Can you post your exact settings.
default setting for continuator, not a problem of config, same know problem (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=48524&view=findpost&p=475607) with gapless crossfader.
try with a gapless album
Playback mode Continuator ON Continuator OFF
Default x
Shuffle (Tracks) x
Shuffle (Albums) x
...
But's that is possible with the existing scheme (of course not so comfortable but much more flexible). You have to "program" an expression with and, or and not when the playback mode is queried with the function.
I know it's possible, I already do this with Acropolis' plugin... My goal was about improvement of usability
Thanks for the update! I've tested it in "Overlap" mode with the "Blackfield" album (which has a mix of fade-outs and seamless transitions) and it's working great.
So is it possible through any settings to use this plugin simply as a means to get rid of gaps, and not crossfading/overlapping?
Even with the fade-in curve down to 10ms, it still causes overlapping between some tracks. I'd rather just have the plugin remove gaps from tracks.
So is it possible through any settings to use this plugin simply as a means to get rid of gaps, and not crossfading/overlapping?
Even with the fade-in curve down to 10ms, it still causes overlapping between some tracks. I'd rather just have the plugin remove gaps from tracks.
I use:
Overlap
Buffer Length: 5008
Threshold: 40.4 (or 100)
Fade out curve: const db/s
Fade out length: 10
Fade target: 0
Fade in curve: const db/s
Fade in length: 10
Fade start: 0
Nothing checked except Power.
The maximum overlapping might be 10+10ms=20ms which should be acceptable.
Try it and let me know whether it works for you or not.
Wiesl
So is it possible through any settings to use this plugin simply as a means to get rid of gaps, and not crossfading/overlapping?
Even with the fade-in curve down to 10ms, it still causes overlapping between some tracks. I'd rather just have the plugin remove gaps from tracks.
I use:
Overlap
Buffer Length: 5008
Threshold: 40.4 (or 100)
Fade out curve: const db/s
Fade out length: 10
Fade target: 0
Fade in curve: const db/s
Fade in length: 10
Fade start: 0
Nothing checked except Power.
The maximum overlapping might be 10+10ms=20ms which should be acceptable.
Try it and let me know whether it works for you or not.
Wiesl
Will report back after some good usage with these settings, thanks.
OK, I wrote a small checklist and HOWTO:
1.) Check if you are using the lastest version from:
http://www.wiesinger.com/opensource/foobar...sp_continuator/ (http://www.wiesinger.com/opensource/foobar2000/foo_dsp_continuator/)
and have a look at the installation docs at
http://www.hydrogenaudio.org/forums/index....mp;#entry550561 (http://www.hydrogenaudio.org/forums/index.php?showtopic=18703&st=250&p=550561&#entry550561)
2.) Check if you added the plugin in the DSP Manager in the correct order . e.g.
http://www.wiesinger.com/opensource/foobar...dsp_manager.gif (http://www.wiesinger.com/opensource/foobar2000/foo_dsp_continuator/html/crossfader_dsp_manager.gif)
3.) For crossfade use e.g. this settings:
http://www.wiesinger.com/opensource/foobar...r_crossfade.gif (http://www.wiesinger.com/opensource/foobar2000/foo_dsp_continuator/html/crossfader_crossfade.gif)
4.) For overlap use e.g. this settings:
http://www.wiesinger.com/opensource/foobar...der_overlap.gif (http://www.wiesinger.com/opensource/foobar2000/foo_dsp_continuator/html/crossfader_overlap.gif)
Hope it helps.
Please let me know if you still have problems.
Wiesl
I updated foo_dsp_continuator to version 0.6.1 (from 0.5.0) with the following changes:
===============================================
All Code is now distributed under the GPL license V2, Added GPL license
I've just seen this now, so sorry for bringing it up so late:
- Have you rewritten the complete source code, or have you asked the previous contributors for permission to change the license?
- Do you realize that the GPL is incompatible with the foobar2000 SDK license? If you own all the rights to the source code, you can of course release it under the GPL, but anyone else who creates a derived version from the GPL code and releases it would technically be violating the GPL (since loading a plugin at runtime constitutes linking against the (non-GPL) foobar2000 core).
I updated foo_dsp_continuator to version 0.6.1 (from 0.5.0) with the following changes:
===============================================
All Code is now distributed under the GPL license V2, Added GPL license
I've just seen this now, so sorry for bringing it up so late:- Have you rewritten the complete source code, or have you asked the previous contributors for permission to change the license?
- Do you realize that the GPL is incompatible with the foobar2000 SDK license? If you own all the rights to the source code, you can of course release it under the GPL, but anyone else who creates a derived version from the GPL code and releases it would technically be violating the GPL (since loading a plugin at runtime constitutes linking against the (non-GPL) foobar2000 core).
Since there was no license agreement at all I have no glue under which term of license the origianl code is published. But I don't have any problems to change it to another license. Currently I removed the source code after that change at all.
BTW:
IHMO foobar2000.exe is also violating the GPL license (except the developers own a commercial license from Nero).
http://www.foobar2000.org/license.html (http://www.foobar2000.org/license.html)
FAAD2 - Freeware Advanced Audio (AAC) Decoder including SBR decoding
Copyright © 2003-2005 M. Bakker, Nero Software AG, http://www.nero.com (http://www.nero.com)
And FAAD2 is also GPL. (http://www.audiocoding.com/faad2.html)
And:
If Foobar2000 is violating the GPL I'm also allowed to publish the code under the GPL.
Wiesl
Since there was no license agreement at all I have no glue under which term of license the origianl code is published. But I don't have any problems to change it to another license. Currently I removed the source code after that change at all.
Yes, that is an unfortunate situation. Your best options are to either just add your name in the source code without changing the (non-specified) license, or to contact the original contributor and ask if the agree to a license change.
IHMO foobar2000.exe is also violating the GPL license (except the developers own a commercial license from Nero).
http://www.foobar2000.org/license.html (http://www.foobar2000.org/license.html)
FAAD2 - Freeware Advanced Audio (AAC) Decoder including SBR decoding
Copyright © 2003-2005 M. Bakker, Nero Software AG, http://www.nero.com (http://www.nero.com)
And FAAD2 is also GPL. (http://www.audiocoding.com/faad2.html)
Peter has some agreement with Nero/Menno Bakker, he is not using FAAD2 under the GPL.
If Foobar2000 is violating the GPL I'm also allowed to publish the code under the GPL.
No, that's not how it works.
If Foobar2000 is violating the GPL I'm also allowed to publish the code under the GPL.
No, that's not how it works.
Under the assumption that foobar2000.exe would be GPL (Which is not the case as you stated):
IHMO it works that way because the GPL is virulent:
foobar2000 uses GPL code => foobar2000 must be GPL => SDK typically uses something from foobar2000 from GPL => SDK must be GPL => Some program uses SDK => program must be GPL.
The second thing is that you can not link non GPL code with GPL code (which is incompatible):
http://www.gnu.org/licenses/old-licenses/gpl-2.0.html (http://www.gnu.org/licenses/old-licenses/gpl-2.0.html)
2b:
You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
=> Derived work and all parts must be GPL.
BTW: There exist other plugins for foobar2000 which are GPL. I've read now the SDK license again and I don't see any license term which are conflicting with the GPL at all as far as the plugins are using only the documented API functions.
Wiesl
If Foobar2000 is violating the GPL I'm also allowed to publish the code under the GPL.
No, that's not how it works.
Let me clarify this. There are two points here:
- If some other software violates the GPL, that does not give you the right to violate the GPL as well.
- Software that violates the GPL is not the same as software that is released under the GPL.
The first one should be clear. The second is a consequence of the GPL itself (emphasis added):
2. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
Licensing software under the GPL is something that the respective author is responsible for, he or she has to
actively do it. Just using or deriving from software that is under the GPL does not make the GPL apply to the derived work. (This is one way to create a GPL violation.)
The second thing is that you can not link non GPL code with GPL code (which is incompatible):
Exactly, and loading a plugin into foobar2000
is linking. Some authors of GPL software think this form of dynamic linking is okay, others don't. (If I remember correctly, the official opinion of the FSF is that it's not allowed.) The foobar2000 SDK license contains no restrictions regarding linking with closed-source programs.
BTW: There exist other plugins for foobar2000 which are GPL. I've read now the SDK license again and I don't see any license term which are conflicting with the GPL at all as far as the plugins are using only the documented API functions.
Well, if their authors own the rights to the source code, they can choose to publish it under whatever license they wish. Unless they also give up their own rights to the source code, they are not bound by this license. However, it may be impossible for other people to create a foobar2000 plugin derived from this cde
and publish it without violating the license (be it the GPL or some other one). Admittedly, if you just don't want other people to use your code for a foobar2000 plugin there are simpler ways than using the GPL: You could use a simpler license that includes the clause "You may not use this source code to create and publish a foobar2000 plugin."
- Do you realize that the GPL is incompatible with the foobar2000 SDK license?
From your last post there is still no answer why the foobar2000 plugins released under GPL (e.g. of newly written code) should be incompatible with the foobar2000 SDK license. I can't find anything in the license terms which does not allow this combination.
Wiesl
- Do you realize that the GPL is incompatible with the foobar2000 SDK license?
From your last post there is still no answer why the foobar2000 plugins released under GPL (e.g. of newly written code) should be incompatible with the foobar2000 SDK license. I can't find anything in the license terms which does not allow this combination.
It's not that the Foobar license is against GPL plugins, it's that the GPL itself doesn't allow the plugin to be linked to Foobar since it's license is not GPL compatible.
The GPL guarantees (enforces?) some freedoms that Foobar's license doesn't, and since it also demands the same from the licenses of other code it's linked with, both are incompatible.
The "Usage restrictions" part of the SDK license alone makes it GPL incompatible, since the GPL is about being able to change the code any way you like provided you give others access to the code.
Peter has some agreement with Nero/Menno Bakker, he is not using FAAD2 under the GPL.
Are you sure a license agreement with Menno Bakker/Nero is enough?
As far as I saw in a quick review of FAAD2 2.6.1 copyright holders/authors are:
M. Bakker, Ahead Software AG
M. Bakker, Nero AG
M. Bakker
Alexander Kurpiers
Volker Fischer
Gian-Carlo Pascutto
John Edwards
VideoLAN
Bill May wmay@cisco.com
Quinnware
AudioCoding.com
As you previously discussed all copyright holders must accept the "license change" to proprietary software.
=================================================
Commercial non-GPL licensing of this software is possible.
For more info contact Nero AG through Mpeg4AAClicense@nero.com.
=================================================
Are you sure this is possible?
Wiesl
The GPL guarantees (enforces?) some freedoms that Foobar's license doesn't, and since it also demands the same from the licenses of other code it's linked with, both are incompatible.
Thanks for pointing that out.
Are you sure this is possible?
I'm sure the Nero lawyers to answer this better than me.
Anyway, I'll stop participating in this discussion now, since I've reached my goal to make you aware of the consequences of sticking the GPL on a foobar2000 plugin.
The GPL guarantees (enforces?) some freedoms that Foobar's license doesn't, and since it also demands the same from the licenses of other code it's linked with, both are incompatible.
Thanks for pointing that out.
Yes, but the linkage is NOT done by the author of a foobar2000 plugin. It is done by the user who uses the plugin and starts foobar2000.exe with the GPL plugin there. And since the SDK license IHMO doesn't forbid any GPL licensed foobar2000 plugins it is valid to distribute under the GPL. So the GPL is IHMO compatible with a foobar2000 plugin but you may not be allowed to start it within foobar2000.exe.
For example VMWARE in the Linux Kernel has the same issue:
You get some non GPLed software from VMWARE in binary form and some kernel dependend source files which are compiled and linked at runtime module into the GPLV2 kernel. Is this illegal, too?
Wiesl
Hello, can anybody post a functioning link to foo_dsp_continuator version 0.6.1?
Thank you,
EarlGrey
Hello, can anybody post a functioning link to foo_dsp_continuator version 0.6.1?
Yes, I'd love to have it too!!! Or email me a copy.
nm
continuator v 0.5 (http://www.hydrogenaudio.org/forums/index.php?act=Attach&type=post&id=4550)
continuator v 0.5 (http://www.hydrogenaudio.org/forums/index.php?act=Attach&type=post&id=4550)
I am getting a bit confused... what is the latest properly working version of the plugin? It's hard to follow here... thank you.
continuator v 0.5 (http://www.hydrogenaudio.org/forums/index.php?act=Attach&type=post&id=4550)
I am getting a bit confused... what is the latest properly working version of the plugin? It's hard to follow here... thank you.
Hello, can anybody post a functioning link to foo_dsp_continuator version 0.6.1?
Thank you,
EarlGrey
here (http://depositfiles.com/files/5739082)
This is ...
v 0.61 as licence problem:
http://www.hydrogenaudio.org/forums/index....st&p=554947 (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=18703&view=findpost&p=554947)
also the "Toggle plugin on/off from a titleformatting function" isn't allowed for foobar2000 0.9.5.3,
so the last "working" version of continuator for foobar 0.9.5.3 is 0.5 !
Any chance for a working link to 0.6.1?
foo_dsp_continuator 0.6.1
http://sharebee.com/1db87fab (http://sharebee.com/1db87fab)
I'm using this in foobar 0.9.5.5 with no problems.
foo_dsp_continuator 0.6.1
http://sharebee.com/1db87fab (http://sharebee.com/1db87fab)
I'm using this in foobar 0.9.5.5 with no problems.
Thank you! Just d/l 0.9.5.6 to try out also.
Detected malware "Worm.AutoIt.EA" [Virus]
Get this shit out of here !!!
Scanned with Virus Total, no reports
link (http://www.virustotal.com/analisis/e318a3e66d54e80b60d8ac9d766ee8a4)
I think foo_dsp_continuator is supposed to do what I want it to, but I'm having a little trouble actually getting it to work. What I want is to be able to mark certain pairs of songs to play seamlessly, even if I am otherwise crossfading. My understanding is that to accomplish this I should create a metadata tag called CONTINUATOR with a value of "off". But this does not seem to be working for me. For example, if I have five tracks, two of which have a CONTINUATOR tag (like so):
Track 1
Track 2 CONTINUATOR="off"
Track 3 CONTINUATOR="off"
Track 4
Track 5
then the finer points, such as what should happen between Tracks 1 and 2, or between Tracks 3 and 4, are sort of an open question, and I'm totally prepared to figure that out through experimentation. But I figure that at the very least Track 2 into Track 3 should play seamlessly, rather than following my Continuator crossfade settings. It's not working that way for me. Everything still crossfades. I do have the "Override mode with CONTINUATOR tag" box checked, and I have tried both versions 0.5 and 0.6.1. I am using foobar2000 9.6.1. I'm hoping that it's just something simple like that I am implementing the CONTINUATOR tag incorrectly. Do I have the right idea?
Can somebody please update this plugin for Foobar 1.1.x?
Can somebody please update this plugin for Foobar 1.1.x?
What needs to be updated?
Newer FB2K versions rely on newer SDKs, so....
Well 0.6.1 works fine here...
WORKING HERE (after enabling in DSP)
foo 1.1.10 + win7 64bit
Could anyone who has Continuator 0.61 kindly share it somehow?
Unfortunately I've lost mine and can't find this version, only 0.5
There (http://www.fileserve.com/file/u9nxKT4/foo_dsp_continuator.dll) you go.
HTH.
Alessandro
There (http://www.fileserve.com/file/u9nxKT4/foo_dsp_continuator.dll) you go.
Thank you so much!!!
I thought this version can never be found, so I'm very grateful to you!
I hope it will work in the future versions of foobar
as it does in current stable version (1.1.11). I have never heard smoother track transitions than that with Continuator!
Can anybody reupload 0.6.1 version of Continuator?, links drop dead soon enough.
Thanks.
Can anybody reupload 0.6.1 version of Continuator?
foo_dsp_continuator 0.6.1 (http://www.mediafire.com/?8eo0rqmio41q0dz)
The lowest part of all humans speaks or reads russian!
Could anyone please reup the 0.6.1 Sourcecode and (english) dll?
Thanks, h_o_m_e_r
The lowest part of all humans speaks or reads russian!
Should I assume you mean that only a minority of people understand Russian? This ambiguously phrased sentence might be interpreted in another way that is not so agreeable.
Can anybody reupload 0.6.1 version of Continuator?
foo_dsp_continuator 0.6.1 (http://www.mediafire.com/?8eo0rqmio41q0dz)
Thanks, but the english version of the dll would be more appreciated.
english version of the dll would be more appreciated.
Just in case: foo_dsp_continuator.dll 0.6.1 English (http://home.onego.ru/~vdx/foo_dsp_continuator_061_eng.7z).
does this plugin works with foobar 1.2.x ? I don't hear any difference when plugin enabled/disabled, what i'm doing not right?
does this plugin works with foobar 1.2.x ? I don't hear any difference when plugin enabled/disabled, what i'm doing not right?
Yes it works. You just need to set it up right, try this settings for a start and make sure to activate Continuator in the DSP Manager.
(http://i48.tinypic.com/2n87trn.jpg)
english version of the dll would be more appreciated.
Just in case: foo_dsp_continuator.dll 0.6.1 English (http://home.onego.ru/~vdx/foo_dsp_continuator_061_eng.7z).
Thanks!
The plugin works nicely for me with its default settings in Foobar2000 v1.2.3, but my configuration button is grayed out. Is this a known issue? Anything I can do to access the settings?
The plugin works nicely for me with its default settings in Foobar2000 v1.2.3, but my configuration button is grayed out. Is this a known issue? Anything I can do to access the settings?
What you have to do is look above the DSP Manager section in the tree thing, Continuator doesn't use the configure button to open the settings, it puts it's own page there right above the dSP settings under playback. Hope I'm explaining this well enough.
And now a question, I'm trying to achieve certain results with this. I want it to NOT adjust the volume at all until the output level at the end of a track reaches about -10 DB. In other words, wait until that happens and start a new track, and not to care in the slightest about how much time is left in the finishing track.
But here's the problem, I pretty much am trying to get the ending track to just quickly drop off the face of the earth as the new one comes in. I've tried editing various settings and can get the new tracks to start at the correct times however can't get the fading out tracks to actually fade out. They just end without actually fading, causing two tracks to play at once for a couple seconds in some cases if the end of the song doesn't fade.
If anyone can recommend any settings I'd appreciate it! Now I have:
Buffer length is 12000.
Threshold (rms drop in dB) is 15.0
Disable track overlapping on seamless transition is not checked.
Crossfade Length is 12,000.
Empty buffer up to overlap point on track change is checked.
Adjust track length to Audio CD blocksize (588 Samples) is checked, though I doubt this matters.
Mode is overlap.
Fade-out mode is Const dB/s.
Fade-out length is 4500.
Fade-in mode is Const dB/s.
Override mode with CONTINUATOR-tag is not checked (I have no clue what this is for).
Fade-out target (dB) is -48
Fade-in target DB is -6.
Only apply when audio is up to the end is checked.
Thanks for any help / suggestions!
VERY IMPORTANT THING: PUT THE CONTINUATOR IN THE END OF THE LIST OF ACTIVE DSPS OTHERWISE YOU CAN HEAR GLITCHES!
OUTPUT BUFFER LENGTH MUST BE 1000 MS!
NOW TRY THIS:
1) mode 1 (soft)
Mode: Overlap
Buffer lenght: 14000 ms
Threshold: 42 db
Disable track overlapping on seamsless transition is uncheked
Fade out curve - Linear
Fade out lenght - 11000 ms
Only apply when audio is up to the end is checked.
Fade in curve - Linear
Fade in length - 3000 ms
Empty buffer up to overlap point on track change is checked.
Adjust track leght to Audio Cd blocksize (588 samles) is checked.
2) mode 2 (advanced)
Mode: Overlap
Buffer lenght: 8000 ms
Threshold: 24 db
Disable track overlapping on seamsless transition is uncheked
Fade out curve - Const
Fade out lenght - 6000 ms
Fade target -54 db
Only apply when audio is up to the end is checked.
Fade in curve - S-curve
Fade in length - 2000 ms
Steepness - 0.33
Empty buffer up to overlap point on track change is checked.
Adjust track leght to Audio Cd blocksize (588 samles) is checked.
Foobar2000 2.0 x64 requires x64 version of DLL. Anyone, please?